Quantum| Host Connectivity |
This page answers these questions:
IOBs keep a record of all HBAs (initiator ports) that have logged in to their target ports. This login happens when an HBA is in the same zone as an IOB target port, or when the HBA is direct-connected to a port. Depending on the OS, the server may need to do some type of Fibre Channel discovery to log in to the blade. Windows, Solaris, HPUX, AIX, Linux, and other OSs each have ways of discovering Fibre Channel devices. How to force discovery for each OS is beyond the scope of this material. It is important that the port settings (speed and topology) on the IOB and switch be correct. in order for initiators to log in to IOBs.
VPS Overview
When an intiator port first logs in to an IOB, an entry is created in the blade's VPS (Virtual Private San) map. In the i2K GUI, you can see a page that lists these entries by selecting Setup > Device > Access > FC Hosts. Each line epresents one HBA (or one HBA port if multiport FC HBAs are used) that is logged into one IOB. These entries contain information maintained by the blade about that HBA.
The same information can be found in the supportDump.log. In the "vpsShow" section of a blade's supportDump.log there is a subsection for each HBA in the Setup > Device > Access > FC Hosts page associated with that blade.
Here is a picture of that screen, followed by the section from the supportDump that shows the information for the line selected in the GUI (crosby).
Figure 5
In Figure 5, we see:
To find this information in a support dump, we identify the correct supportDump.log file for blade 1,1,1,1,3, as described earlier in File Naming Conventions, then find the "vpsShow" section in that file and look for the Host Index associated with the HBA that has a WWN of 210000e0:8b1191e4. Doing that brings us to Host Index 2: in the supportDump found in var\log\adic\I000000\.
Here is the information from that support dump:
Host Index 2: 'crosby' WWN = 210000e0:8b1191e4
Host State: Online, OS Type = 12, Flags = 0x0d000001
Host Type: 'LINUX'
Device Id: 'unknown'
In-band Access: Self : -w | 3rd Party : --
Registration Period = 0
Interface Type = 3, iCtrl = 0x0x1911c3cc, iChan = 1
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
1, 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
2, 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
3, 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
This section of the supporDump.log will be covered in detail following Figure 6.
Here is a picture of the LUN map screen for the line selected in Figure 5, followed by the section from the supportDump that describes the information in Figure 5 and Figure 6.
Figure 6
Host Index 2: 'crosby' WWN = 210000e0:8b1191e4
Host State: Online, OS Type = 12, Flags = 0x0d000001
Host Type: 'LINUX'
Device Id: 'unknown'
In-band Access: Self : -w | 3rd Party : --
Registration Period = 0
Interface Type = 3, iCtrl = 0x0x1911c3cc, iChan = 1
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
1, 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
2, 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
3, 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
Figure 6 shows the LUN map for the line selected in Figure 5. That information is also shown in the support dump under "Host Index 2:" above.
Here is a description of the lines shown as they relate to the screenshots:
Host Index 2: 'crosby' WWN = 210000e0:8b1191e4
Host State: Online, OS Type = 12, Flags = 0x0d000001
Here we are interested in the first value after "Host State:". That state informtation can be Online, Logout, or Offline. If it is online or logout, it will show in the FC Hosts table (Figure 5) as Online, and if it is offline it will show as Offline. The meaning of these states is described later in this section.
Host Type: 'LINUX'
Information displayed in the Type field of the FC Host table; shows what OS was entered for that HBA.
Device ID: 'unknown'
Information displayed in the Port field of the FC Host table.
In-band Access: Self : -w | 3rd Party : --
This field isn't used by field service.
Registration Period = 0
This field isn't used by field service.
Interface Type = 3, iCtrl = 0x0x1911c3cc, iChan = 1
The useful value in this line is "iChan = 1". The iChan number describes which target port (FCAL 1 or FCAL 2) the HBA is logged into, and is described later in this section.
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
1, 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
2, 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
3, 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
This reflects all the information presented from the LUN mapping screen (Figure 6) and will be described in the "What devices (physical and logical) are presented to each HBA from each blade?" section.
NOTE: When using a snapshot to reconstruct the configuration of the library in a SAN, field engineers will not have screen shots available. In the above example, Figure 5 and Figure 6 were used to describe the information in the "Host Index" sections of a support dump, as they relate to what is seen from the user interface. The practical application of the information in the "vpsShow" section of a snapshot requires that the engineer use this information to understand which devices from each IOB are presented to which HBAs when troubleshooting problems where servers cannot communicate reliably with devices.
The rest of this section goes into more detail about the "vpsShow" section of support dumps. It is intended to help field engineers reconstruct a picture or map of the library as it exists in the customer SAN, to troubleshoot host-to-device connectivity issues.
vpsShow:
The information about what initiators are currently logged in or have logged in to an IOB is in the supportDump.log in the "vpsShow" section. In that section there is a "Host Index" assigned to each HBA, followed by information about that host. To find out which HBAs have logged in, find all instances of "Host Index" in the supportDump.log file for the blade you are interested in.
Here is an example:
Host Index 1: 'rofl5d-tarkin-2' WWN = 10000000:c962b415
Host Index 2: 'ql9k01' WWN = 2ffc00c0:dd0d3472
Host Index 3: 'ql9k02' WWN = 2ffc00c0:dd0d344a
Host Index 4: 'rofl5d-tarkin-1' WWN = 10000000:c96311b3
This blade has four initiators listed in its VPS map. This lists the HBA's that have logged in to the blade at some point, but it doesn't show the current status of each HBA.
Viewing the Current Status of an HBA:
To see the current status of an HBA, look at the line immediately below the "Host Index:" line, the "Host State" line:
Host Index 1: 'rofl5d-tarkin-2' WWN = 10000000:c962b415
Host State: Online, OS Type = 12, Flags = 0xcf000001
Here, "Online" means that the HBA is currently logged in to the blade. You could say that the blade "sees" the HBA, or that the HBA "sees" the IOB.
Host State Meanings:
NOTE: Sometimes, Fibre Channel switch ports will log in to an IOB, so there may be entries for switches in the VPS map. You will need to identify all logged-in devices by WWPN to know what each logged in device is. The switch port "Host State" can be Online, Offline, or Logout without causing any problems.
If a host is connected to an IOB (Host State of "Online" or "Logout", but not "Offline") at the time the snapshot is taken, you can tell which target port it is connected to.
The following examples are for the same HBA, logged into two different blades on the same system:
6404 blade:
Host Index 1: 'rofl5d-tarkin-2' WWN = 10000000:c962b415
Host State: Online, OS Type = 12, Flags = 0xcf000001
Host Type: 'LINUX'
Device Id: 'P2,D3-5-3,D4-6-4'
In-band Access: Self : -w | 3rd Party : -w
Registration Period = 0
Interface Type = 3, iCtrl = 0x0x18aff1f8, iChan = 2
For a 6404 blade, look at the iChan value. In the above example, "iChan = 2", so this HBA is logged in to FCAL-2 of this IOB.
7404 blade:
Host Index 10: 'rofl5d-tarkin-2' WWN = 10000000:c962b415
OS Type = 12, Flags = 0x00000001
Host Type: 'LINUX'
Device Id: 'P2,D51-5-23,D52-6-24'
In-band Access: Self : -- | 3rd Party : --
Registration Period = 0
Chan = 2 Host State: Online
Interface Type = 3, iCtrl = 0x0x7e66fd0
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 ADIC FC IOB 5931 AMP016791-0335
23, 3 5 0 0 IBM ULTRIUM-TD3 93G0 F001C1612D
24, 5 6 0 0 IBM ULTRIUM-TD3 93G0 F001C16133
For a 7404 blade, look at the Chan value. In the above example, "Chan = 2", so this HBA is also logged into FCAL-2 of this IOB.
NOTE: For 7404 blades, if an HBA is zoned to see both FCAL-1 and FCAL-2 and logs in to both ports, you will see that in the "vpsShow" section of the supportDump under "Host Index", as shown here:
Host Index 1: 'ATL_48K' WWN = 21fd0005:1e36173a
OS Type = 7, Flags = 0xbb800001
Host Type: 'SWITCH'
Device Id: 'unknown'
In-band Access: Self : -w | 3rd Party : rw
Registration Period = 0
Chan = 1 Host State: Logout
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 ADIC FC IOB 5821 AMP018000-0076
Chan = 2 Host State: Logout
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 ADIC FC IOB 5821 AMP018000-0076
NOTE: For 6404 blades, if an HBA is zoned to see both FCAL-1 and FCAL-2, it will not show that in the vpsShow section under the Host Index. It will only show one iChan connection. You may be able to tell if an HBA is logged in to both ports of a 6404 by looking in several places, as in the following example:
Host Index 7: 'usto-pdpx-vt005_2a' WWN = 210000e0:8b14776a
Host State: Online, OS Type = 8, Flags = 0x84000001
Host Type: 'GENERIC'
Device Id: 'st'
In-band Access: Self : -- | 3rd Party : --
Registration Period = 0
Interface Type = 3, iCtrl = 0x0x191363bc, iChan = 1
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 ADIC FC IOB 4462 AMP011015-0293
1, 10 0 0 29 ADIC Scalar i2000 500A ADIC203101685_LL1
2, 5 4 0 0 IBM ULTRIUM-TD3 69U3 F001A84007
3, 7 5 0 0 IBM ULTRIUM-TD3 69U3 F001A8400D
4, 8 6 0 0 IBM ULTRIUM-TD3 69U3 F001A84013
This shows that the HBA with WWPN 210000e0:8b14776a is connected to FCAL-1, because it says "iChan = 1". Because this is a 6404 blade, we don't know if that HBA may also be logged in to port 2.
The following section continues this example and shows how to see if that HBA is also logged in to port 2.
Logged in HBAs can show up in the "fcShow 2" section of the supportDump.log (for both 6404s and 7404s).
Find "fcShow 2" in the supportDump.log and scroll down past the "Fibre Channel Controllers" section to the first instances of "Fibre Channel Controller 1" and "Fibre Channel Controller 2". You will see the WWPN of the logged in HBAs.
************ fcShow 2 ************
---------------------------------------------------------------------------------------------
Fibre Channel Controllers
---------------------------------------------------------------------------------------------
Ctlr : PCI Addr : ISP : Firmware : Firmware : Loop : Fabric : Port : Ext. : Link
Id : Bs Dv Fn : Type : State : Version : ID : Attached : Mode : FIFO : Speed
---------------------------------------------------------------------------------------------
1 : 00 01 00 : 2312 : Ready : 3.03.19 : PtoP : Yes : Targ : None : 2 Gbps
2 : 00 01 01 : 2312 : Ready : 3.03.19 : PtoP : Yes : Targ : None : 2 Gbps
3 : 00 02 00 : 2312 : Ready : 3.03.19 : 1 : No : Init : None : 2 Gbps
4 : 00 02 01 : 2312 : Ready : 3.03.19 : 1 : No : Init : None : 2 Gbps
5 : 00 03 00 : 2312 : Ready : 3.03.19 : 1 : No : Init : None : 2 Gbps
6 : 00 03 01 : 2312 : Ready : 3.03.19 : 1 : No : Init : None : 2 Gbps
---------------------------------------------------------------------------------------------
--------------------------------------------------------------
Fibre Channel Controller 1
--------------------------------------------------------------
Loop : Node : Node : Port : Port
Id : Type : Name : Name : ID
--------------------------------------------------------------
1 : 0000 : 20000000.c94ac797 : 10000000.c94ac797 : 38000b
2 : 0002 : 20000000.c94a791d : 10000000.c94a791d : 37000e
4 : 0002 : 500a0980.00009f8b : 210000e0.8b14776a : 371700
--------------------------------------------------------------
--------------------------------------------------------------
Fibre Channel Controller 2
--------------------------------------------------------------
Loop : Node : Node : Port : Port
Id : Type : Name : Name : ID
--------------------------------------------------------------
1 : 0002 : 500a0980.00009f8b : 210000e0.8b14776a : 371700
--------------------------------------------------------------
In the two sectoins shown above, you can see the same WWPN: 210000e0:8b14776a (except that the colon is replaced with a period, so it shows as 210000e0.8b14776a0 (a very important distinction if you are using a text search program) logged in to both ports 1 and 2. This is an example where for a 6404 IOB, although the HBA is logged in to both FCAL-1 and FCAL-2, the "Host Index" information in the "vpsShow" area of the support dump only shows the HBA connected to iChan = 1.
There is one other place with information about what port of an IOB an HBA is logged into:
For 7404s, only look for fcDevDisplayHosts:
************ fcDevDisplayHosts(1) ************
Host Table for Port = 1
Ind WWNN WWPN SID InId Valid InitIdSet
0 20000000:c9518a5b 10000000:c9518a5b 0x14800 0x0 1 1
1 20000000:c950eedd 10000000:c950eedd 0x14900 0x100 1 1
2 20000000:c98661fd 10000000:c98661fd 0x14a00 0x1 1 1
3 20000000:c970ec0f 10000000:c970ec0f 0x14b00 0x101 1 1
4 20000000:c96311b3 10000000:c96311b3 0x14c00 0x2 1 1
That's All the information
************ fcDevDisplayHosts(2) ************
Host Table for Port = 2
Ind WWNN WWPN SID InId Valid InitIdSet
0 20000000:c950740b 10000000:c950740b 0x24800 0x0 1 1
1 20000000:c950ec03 10000000:c950ec03 0x24900 0x100 1 1
2 20000000:c96240d3 10000000:c96240d3 0x24a00 0x1 1 1
3 20000000:c970ebd5 10000000:c970ebd5 0x24b00 0x101 1 1
4 20000000:c962b415 10000000:c962b415 0x24c00 0x2 1 1
This provides the WWNN (World Wide Node Name) and WWPN (World Wide Port Name) of each HBA logged in to the blade at the time of the snapshot.
There are two places in a supportDump where you can find out which devices are presented to which HBAs for each IOB. This is the information normally configured and viewed through the LUN mapping screen discussed earlier.
The two places are:
There is a difference between these two:
|
vpsShow |
Only provides LUN mapping information for hosts that are in an "Online" or "Logout" state. LUN mapping information is not shown for hosts that are "Offline". |
| vpsMapShow | Shows LUN mapping information for all hosts that have devices mapped to them, whether or not the host is offline. |
This is important because if a snapshot is taken while a host is powered down, that HBA might show up as offline, and if the "vpsShow" section is used to see the LUN map, it wouldn't show any devices in the LUN map. However, it would show the LUN map for that HBA under "vpsMapShow".
There are two places to look at for this information. As shown in the previous section, find the "Host Index" instance for the HBA that you want to see.
We will use the example from before:
Figure 7
Here is the corresponding LUN map information, as seen in "vpsShow" and "vpsMapShow":
vpsShow:
Host Index 2: 'crosby' WWN = 210000e0:8b1191e4
Host State: Online, OS Type = 12, Flags = 0x0d000001
Host Type: 'LINUX'
Device Id: 'unknown'
In-band Access: Self : -w | 3rd Party : --
Registration Period = 0
Interface Type = 3, iCtrl = 0x0x1911c3cc, iChan = 1
Host Int.
LUN, LUN Chan Id Lun Vendor Product Rev SN
--- ---- ---- -- --- ------ ------- --------
0, 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
1, 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
2, 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
3, 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
Here are the field definitions:
LUN[1]: The LUN number presented to the HBA for this device
LUN[2]: The Internal LUN used by the IOB, not useful to us
CHAN: = 0 for virtual devices (CC LUN or Logical Library); otherwise the FCAL port that this device is connected to
ID: Not useful
Lun: Not useful to field service, used by the blade
Vendor: Vendor/manufacturer
Product: What the device is
Rev: Firmware version of the device
SN: Serial number of the device, as presented to the IOB
In the example above, We see that ths host, 'crosby', sees:
This is the same information we see in the screenshot.
Reminder: This LUN map information will only be present for hosts that are not in the "Offline" state when the snapshot was taken.
vpsMapShow
The LUN map information is present in the "vpsMapShow" section of the support dump, even if an HBA is offline. The "vpsShow" information is still needed, however, to use "vpsMapShow".
In order to make use of the data in "vpsMapShow", you must find each instance of "Host Index" from "vpsShow" to interpret the information. We will continue using the example above, for host, 'crosby' on blade 1,1,1,1,3.
Steps:
1) Find all instances of the "Host Index" in the supportDump.log file for 1,1,1,1,3. For example:
Host Index 1: 'messier' WWN = 210000e0:8b12da27
Host Index 2: 'crosby' WWN = 210000e0:8b1191e4
Host Index 3: 'brocade_stickcheck' WWN = 20fd0060:6951d129
Host Index 4: 'makita' WWN = 10000000:c93b4d1e
Host Index 5: 'esposito' WWN = 210000e0:8b0fbf71
2) Note the "Host Index" number of the host under investigation (crosby = 2).
3) Find the section: "vpsMapShow".
************ vpsMapShow ************
Host Lun Internal Chan Id Lun Vendor Product Rev SN
---- --- ------- ---- -- --- ------ ------- --------
1 0 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
1 1 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
1 2 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
1 3 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
2 0 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
2 1 3 0 0 3 ADIC Scalar i2000 595A ADIC203100207_LL0
2 2 1 3 0 0 IBM ULTRIUM-TD2 93T0 F001436001
2 3 2 4 0 0 IBM ULTRIUM-TD2 93T0 F001436007
3 0 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
4 0 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
4 1 11 0 0 8 ADIC Scalar i2000 595A ADIC203100207_LL1
4 2 9 5 0 0 IBM ULTRIUM-TD3 88M0 F00143600D
4 3 10 6 0 0 IBM ULTRIUM-TD3 88M0 F001436013
5 0 0 0 0 0 QUANTUM Scalar i2000 4462 AMP008215-0121
5 1 11 0 0 8 ADIC Scalar i2000 595A ADIC203100207_LL1
5 2 9 5 0 0 IBM ULTRIUM-TD3 88M0 F00143600D
5 3 10 6 0 0 IBM ULTRIUM-TD3 88M0 F001436013
4) Use the information from all lines under the "Host" column with a value of "2" (crosby's host index = 2) to find out what devices are presented to crosby.
5) Interpret the fields as follows:
Host: The "Host Index" value, as shown in the "vpsShow" section for each HBA
Lun[1]: LUN number presented to the HBA for this device
Internal: Internal LUN used by the IOB, not useful to us
Chan: = 0 for virtual devices (CC LUN or Logical Library); otherwise the FCAL port this device is connected to
Id: Not useful
Lun[2]: Not useful to field service, used by the blade.
Vendor: Vendor/manufacturer
Product: What the device is
Rev: fFrmware version of the device
SN: Serial number of the device, as presented to the IOB.
Looking at all the lines where the Host is 2, we get the same information as we did earlier from the "vpsShow" section: We see that this Host 2 sees:
| Notes |
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |