HP P10000 HP 3PAR HP-UX 11i v2, v3 Implementation Guide (QL226-96021, August 2 - Page 39

if usingthe A6795 or AH402A HBA in the examples below. The example, The driver for AB379A

Page 39 highlights

NOTE: Refer to HP documentation at http://docs.hp.com for complete information on using the PVLinks feature to manage device paths. 2. If the VERITAS Volume Manager's DMP driver is to be used, make the newly-registered VLUNs visible to the DMP layer using the following command, which causes VxVM to rebuild its view of the device nodes: # vxdctl enable NOTE: LVM and VxVM may coexist on the same system but should not be used to manage the same devices. NOTE: Remember to create raw and block device paths for the exported VLUNs using HP-UX's ioscan and insf commands before executing any LVM and VxVM commands for the new devices. NOTE: The driver for AB379A, AD194A is fcd and driver for A6795A, AH402A is td. Replace fcd to td if using the A6795 or AH402A HBA in the examples below. The example below is for the AD194A HBA. 3. The fcmsutil utility can be used to display important information about each HBA port using the port's /dev/fcd device node. The fcd instance number is shown in the output of the ioscan -fun command. # ioscan -fun Class I H/W Path Driver S/W State H/W Type Description fc 0 0/0/8/1/0 fcd CLAIMED INTERFACE HP AD194-60001 2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1) NOTE: Topology will be PRIVATE_LOOP for Direct connect and PTTOPT_FABRIC for Fabric connect. The example below is for Fabric. # fcmsutil /dev/fcd0 (for Fabric connect) Vendor ID is = 0x001077 Device ID is = 0x002312 PCI Sub-system Vendor ID is = 0x00103c PCI Sub-system ID is = 0x0012ba PCI Mode = PCI-X 133 MHz ISP Code version = 3.3.153 ISP Chip version = 3 Topology = PTTOPT_FABRIC Link Speed = 2Gb Local N_Port_id is = 0x050200 Previous N_Port_id is = 0x050200 N_Port Node World Wide Name = 0x50060b00001d5845 N_Port Port World Wide Name = 0x50060b00001d5844 Switch Port World Wide Name = 0x200200051e3534c9 Switch Node World Wide Name = 0x100000051e3534c9 Driver state = ONLINE Hardware Path is = 0/0/8/1/0 Maximum Frame Size = 2048 Driver-Firmware Dump Available = NO Driver-Firmware Dump Timestamp = N/A Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver B.11.23.04 /ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Oct 18 2005,08:21:11 Using the ioscan Command with Multipathing Software to Verify HBA Connections 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48

NOTE:
Refer to HP documentation at
h
t
tp://doc
s
.hp
.co
m
for complete information on using
the PVLinks feature to manage device paths.
2.
If the VERITAS Volume Manager's DMP driver is to be used, make the newly-registered VLUNs
visible to the DMP layer using the following command, which causes VxVM to rebuild its view
of the device nodes:
# vxdctl enable
NOTE:
LVM and VxVM may coexist on the same system but should not be used to manage
the same devices.
NOTE:
Remember to create raw and block device paths for the exported VLUNs using
HP-UX's
ioscan
and
insf
commands before executing any LVM and VxVM commands for
the new devices.
NOTE:
The driver for AB379A, AD194A is fcd and driver for A6795A, AH402A is td.
Replace
fcd
to
td
if usingthe A6795 or AH402A HBA in the examples below. The example
below is for the AD194A HBA.
3.
The fcmsutil utility can be used to display important information about each HBA port using
the port's
/dev/fcd<instance>
device node. The fcd instance number is shown in the
output of the
ioscan -fun
command.
# ioscan -fun
Class I H/W Path Driver S/W State H/W Type Description
==============================================================================
fc
0 0/0/8/1/0 fcd
CLAIMED
INTERFACE HP AD194-60001
2Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
NOTE:
Topology will be PRIVATE_LOOP for Direct connect and PTTOPT_FABRIC for Fabric
connect. The example below is for Fabric.
# fcmsutil /dev/fcd0 (for Fabric connect)
Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012ba
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.153
ISP Chip version = 3
Topology = PTTOPT_FABRIC
Link Speed
= 2Gb
Local N_Port_id is = 0x050200
Previous N_Port_id is = 0x050200
N_Port Node World Wide Name = 0x50060b00001d5845
N_Port Port World Wide Name = 0x50060b00001d5844
Switch Port World Wide Name = 0x200200051e3534c9
Switch Node World Wide Name = 0x100000051e3534c9
Driver state = ONLINE
Hardware Path is = 0/0/8/1/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available
= NO
Driver-Firmware Dump Timestamp = N/A
Driver Version = @(#) libfcd.a HP Fibre Channel ISP 23xx & 24xx Driver
B.11.23.04/ux/core/isu/FCD/kern/src/common/wsio/fcd_init.c:Oct18
2005,08:21:11
Using the ioscan Command with Multipathing Software to Verify HBA Connections
39