| United States-English |
|
|
|
![]() |
Communicator e3000 MPE/iX Release 7.5 (Software Release C75.00): HP e3000 MPE/iX Computer Systems > Chapter 4 Fibre Channel Device and Adapter Support on
HP e 3000 SystemsConfiguration Examples for Fibre Channel Adapters and Devices |
|
Device configuration for FC adapter cards on N-Class and A-Class systems is accomplished using the same tools (SYSGEN, IOCONFIG) as existing HP e3000 Systems. Your MPE/iX 7.5 Release software has default configuration files like CONFACL1, CONFNCL1, etc. These configuration files provide the minimum set of devices necessary to boot the system and start the installation process. You will need to modify your configuration file to connect additional Fibre Channel devices to your system. This article will provide a step by step description of configuring both FC Device Adapter cards and attached FC peripherals on an N-Class System. The A-Class's interface will be similar enough to allow a System Manager experienced in configuring hardware to apply this N-Class example to an A-Class system. The steps discussed in this article for configuring FC devices cover only the configuration of device LUNs on MPE/iX. Other procedures like connecting the device and performing device-specific configuration (like LUN creation) are beyond the scope of this article. These details can be found in the Configuration Guide for the respective fibre channel device being used. Such procedures are expected to be completed before attempting to configure the device LUNs on MPE/iX.
The following operations are accomplished while the system is "down," e.g., not running MPE/iX. Start by entering a Control-B at the system console. You may be prompted for a logon ID and password, each of which currently defaults to a single Carriage Return. At the GSP> prompt enter an RS or TC command, confirm it and acknowledge any prompts that are presented. You should soon find yourself at the main Boot Command Handler (BCH) menu (If you have problems please refer to the MPE/iX System Software Maintenance Manual for this Release which should include a more complete description of rebooting your system): Console Display #1:
From the Main menu, proceed to the Information menu: Console Display #2:
For the purposes of this article we are only interested in the I/O information for this system. The "I/O" function will provide two sets of information in two sections. The first section is the listing of the System and Local Bus Adapters; the Local Bus Adapters with slot numbers 1-12 are potential Device Adapter locations. The second section is the listing of PCI Device Adapters that are actually present on the system. These controllers are either Device Adapter Cards or the embedded functions of the Core I/O Card. Console Display #3:
The hardware path can loosely be interpreted as:
Each path marked "SCSI bus cntlr" represents a separate SCSI Bus. Each path marked "Fibre channel" represents a separate fibre channel port. The Vendor ID, Device ID, Path and Bus/Slot information may be used to uniquely identify each Fibre Channel Device Adapter Card type. The Vendor and Device IDs of Fibre Channel Adapter card supported are listed in Table 4-2 “Supported Fibre Channel Adapter Card with Vendor ID and Device ID”. Table 4-2 Supported Fibre Channel Adapter Card with Vendor ID and Device ID
As a reference for our example, the list of supported PCI-SCSI adapter cards with Vendor ID and Device ID is also listed in Table 4-3 “Supported PCI-SCSI Adapter Cards with Vendor ID and Device ID” . Table 4-3 Supported PCI-SCSI Adapter Cards with Vendor ID and Device ID
From the information previously gathered from the Information Menu, I/O Function, we can see that the system has the following cards connected: Example #1: Correlating Path and Card Type Table 4-4 Title not available (Determining the Type of Cards in Your System)
The N-Class system has a built in function that will search for SCSI devices attached to the system. This function is available on the Main Menu as the Search command. It is to be noted that this Search command is helpful only in finding the devices attached to SCSI adapter cards and not for the devices attached to Fibre Channel adapter cards. The procedure to determine FC devices connected to FC adapter cards is covered in a later section. Console Display #4:
Note that the Search command shows the FC card 0/8/0/0 as "0/8/0/0.8 Random access media". This is not an actual FC device path but just a hint that there could possibly be random access media devices under this card. We will see later how to identify the FC devices connected to the card. One piece of configuration data that is missing is the actual hardware device IDs. At this time the only source for this information is the ISL utility, ODE MAPPER2. MAPPER2 is the 64-bit version of the MAPPER program used for previous HP e3000 platforms. For more complete information on ODE MAPPER2, please see the MPE/iX System Software Maintenance Manual for this Release. It is highly recommended that your configured device IDs match the actual device IDs returned by ODE MAPPER2. For the purposes of this article we'll assume some arbitrary but legal device IDs. The next part of your configuration must be done while the system is "up" and running MPE/iX. This will cover the detailed steps for configuring Fibre channel adapter card and Fibre channel devices. The configuration of SCSI devices on PCISCSI adapters is accomplished with the same exact steps as followed in MPE/iX 7.0 on N- and A-Class HP e3000 systems and is not discussed here. The steps needed in SYSGEN to configure a Fibre Channel adapter card, i.e., one at path 0/8/0/0. As with the SCSI adapter, start by configuring System Bus Location equal to zero ("0"). Then configure Local Bus Number equal to eight ("8"), PCI Device equal to zero ("0"), and PCI Function equal to zero ("0"). In most cases, the System Bus component and Local Bus number component may already be configured. If so, directly proceed to configure the PCI Device component.
Checking that the FC Device Adapter Card is properly configured:
Note that the PMGR should be set to "FC_DAM," which is the new manager software for FC device adapter card. Before identifying fibre channel devices connected to the adapter, let us understand about Fibre Channel device hardware path format used in MPE/iX. Unlike a SCSI device path, a Fibre Channel device path is interpreted differently. The path format used in MPE/iX for a fibre channel device is given below:
Note that the second to last component here is "FC Nport" whereas in case of SCSI devices it would have been a "SCSI Target". The FC Nport represents a "fibre channel node port" which represents the connection point for a fibre channel device. Under the FC Nport, there can be multiple LUNs of the FC device, which are accessible in the same way as SCSI LUNs. A single FC device can support multiple Nports and each Nport can have varying number of LUNs under it. This is analogous to multiple SCSI LUNs under a SCSI Target. The last component in the FC path represents an "FC LUN" while in a SCSI device path it would be a "SCSI LUN". Although the FC LUN is functionally the same as a SCSI LUN, it is termed differently to signify that it can take on much larger values. There is no way in the Boot Command Handler (BCH) Main Menu to identify the FC devices connected to an FC adapter card. Running ODE MAPPER2 from ISL does help to identify some FC devices but even this may not list out all FC LUNs under the FC devices. But for configuring in MPE/iX we ultimately need the FC LUN paths. In order to assist the System Administrator in identifying the FC devices and LUNs accessible from a FC adapter card, MPE/iX 7.5 comes with a new utility called FCSCAN. This utility is present in the system as "FCSCAN.PUB.SYS". Before using this utility to identify FC devices/LUNs under a FC adapter, you need to configure the FC adapter in SYSGEN using the steps mentioned above and reboot the system. (If the FC card is configured online using online configuration tool IOCONFIG instead of SYSGEN, the reboot is not required). When the system is rebooted with FC adapter configured, the software driver for the FC adapter card initializes the card and identifies FC devices connected to the card. At this time, a message appears on the system console saying:
The appearance of this message indicates that the card has been initialized successfully and the software identified the FC devices connected to this adapter card. To get the list of FC devices connected to the card, you can run the utility FCSCAN from the MPE/iX CI prompt. A sample output on running the FCSCAN utility is shown below:
The output from FCSCAN shows the list of FC adapter cards and devices present in the system. The hardware paths printed by FCSCAN can be directly used in SYSGEN to configure the corresponding device. The output from FCSCAN utility shows the following information:
The above sample output shows that there is a Fibre Channel Adapter card configured in the system at path 0/8/0/0. Under this card, there are some devices listed. Path 0/8/0/0.0 shows an FC N_Port (Node Port) which indicates the fibre channel port of a device connected to the card. FC N_port is required to be configured in SYSGEN while configuring devices. The output also shows three disks of type HP OPEN-3 shown with paths 0/8/0/0.0.0, 0/8/0/0.0.1 and 0/8/0/0.0.105. The last components of these paths refer to the LUN number of these disks. The type HP OPEN-3 usually refers to an XP512 disk array. Since the hardware paths of these three disks come under Nport 0/8/0/0.0, they all fall under the same Nport in the XP512. Path 0/8/0/0.95 shows another FC N_Port (Node Port) indicating another device is connected to the card. Under this N_Port, there are four disk LUNs of type HP A6188A shown with paths 0/8/0/0.95.0, 0/8/0/0.95.5, 0/8/0/0.95.10 and 0/8/0/0.95.50. The type HP A6188A refers to a VA7100 disk array. Thus FCSCAN utility shows all device N_Ports and LUNs connected to the adapter card. The next section describes how this information can be used to configure them in SYSGEN. More details on FCSCAN utility are covered in a separate article in this Communicator document. Since the FC adapter card at path 0/8/0/0 has already been configured, now go on to configure the FC devices. For this we should first configure the FC Nport paths and then the FC device LUNs. FC NPort should be configured in SYSGEN with the standard ID "FC_NPORT".
To check that the FC N_Port is properly configured:
Note that the PMGR will be set to "FCP_NM", Fibre Channel Protocol Nport Manager, which is the new manager software for FC device adapter card. This is one significant difference between configuring a FC device and a SCSI device. For a SCSI device usually the path component at this level is configured in SYSGEN with "id = pseudo" to indicate a pseudo manager. But for FC devices, this path component level has a real software manager called FCP_NM. After configuring the Nport, the next step is to configure the FC device LUNs. For this too, we can use the hardware paths of the LUNs as printed in FCSCAN output. The ID to be used while configuring any of the FC device LUNs is HPDARRAY.
To check that the FC device LUNs are properly configured:
Note that the PMGR will be set to "SCSI_DISK_AND_ARRAY_DM". This software manager is the same that is used for SCSI disk LUNs. At this point we have successfully configured the LUNs under the FC device XP512. To configure the LUNs under the FC device A6188A:
At this point, we have successfully configured the disk LUNs under both FC devices connected to the FC adapter card 0/8/0/0. To use one of the disks under a Fibre Channel device as LDEV-1, it is necessary to first note down the long format path of the disk. This long format path is the one printed by FCSCAN utility as "BOOT MENU PATH". For our discussion, let us take the FCSCAN output from the previous example:
Given the above setup of FC devices, assume that we want to use the disk at path 0/8/0/0.95.5 as our new LDEV-1. Before going on to install this disk, first remember to note down the long format path for this disk. As we can see, the long format path for this disk is 0/8/0/0.8.0.95.0.0.5. Now we can shutdown the system and come back to the Boot Command Handler Main Menu. From the Main menu, set the primary path of the system to the long format path of the FC disk, which we had noted down earlier. Console Display #5:
Follow the usual procedure to do INSTALL from the tape. When the installation is over, the system can be rebooted with the primary path remaining as above. On booting from the FC disk as LDEV-1, follow the usual procedure in SYSGEN to modify the configuration for LDEV-1. During this time, the hardware path to be used to modify LDEV-1 should be the shorter path format and not the longer one. While setting up the SYSGEN configuration for the above disk as LDEV-1, use 0/8/0/0.95.5 as the hardware path.
To verify the changes done in the configuration:
The main point to note while using an FC disk as LDEV-1 is that the long format path is to be used only for primary path setting in the Main Menu. In SYSGEN, the shorter path format should be used to configure the disk as LDEV-1.
In order to use FC devices as LDEV-1, there are certain minimum version requirements on the PDC firmware in HP e3000 systems. If the PDC firmware is less than the versions mentioned below, HP e3000 systems will not support booting from FC devices.
MPE/iX 7.5 Release software comes with four new default configuration groups which can be used while configuring an FC disk connected through the FC adapter card as LDEV-1. These new groups are:
For details on Core I/O cards I and II, refer to the article titled "HP e3000 PA-8700 A-Class and N-Class Core I/O Card" in this Communicator. From the previous section it is clear that to use an FC disk as LDEV-1, we need the long format path of the disk to specify as the primary path. The long format path can be obtained by running FCSCAN utility. It must be remembered that FCSCAN utility is being introduced only with MPE/iX 7.5. If the existing release on your HP e3000 system is MPE/iX 7.0 and you wish to start using an FC adapter card with one of the FC device disks as LDEV-1, it will involve multiple steps to achieve this.
When the installation is complete, your HP e3000 system is ready to be booted using the FC disk as LDEV-1. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||