Unsolved
This post is more than 5 years old
105 Posts
0
4562
HP-UX ii1 v1/v2 and VNX
We have several HP-UX ii1 v1 and v2 systems hooked to cx4 or cx3-20f clariions. We are attempting to migrate the, to VNX by prresenting new luns and having them LVM migrated. When we zone the hosts to the VNX it loses paths from VNX and CX without even putting the host in storage group. We updated drivers on this per EMC and actually EMC is doing the presnetation and cannot get iit to work.
sac3scott
105 Posts
0
December 22nd, 2011 12:00
fcmsutil output from one:
These are A6795A HBAs on lawhchapp
***********************************
# ioscan -funC fc
Class I H/W Path Driver S/W State H/W Type Description
========================================================================
fc 0 0/2/1/0/4/0 fcd CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
/dev/fcd0
fc 1 0/3/1/0/4/0 fcd CLAIMED INTERFACE HP A9784-60001 PCI/PCI-X Fibre Channel FC/GigE Combo Adapter (FC Port 1)
/dev/fcd1
root@lawhchdb:/root
#
Status output from the state of the HBAs
*****************************************
# /opt/fcms/bin/fcmsutil /dev/fcd0
Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012c7
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.175
ISP Chip version = 3
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x180700
Previous N_Port_id is = 0x180700
N_Port Node World Wide Name = 0x50060b00003770b9
N_Port Port World Wide Name = 0x50060b00003770b8
Switch Port World Wide Name = 0x200700051e35e0eb
Switch Node World Wide Name = 0x100000051e35e0eb
Driver state = ONLINE
Hardware Path is = 0/2/1/0/4/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.11.16 /ux/kern/kisu/FCD/src/common/wsio/fcd_init.c:Jun 11 2008,13:35:21
root@lawhchdb:/root
#
# /opt/fcms/bin/fcmsutil /dev/fcd1
Vendor ID is = 0x001077
Device ID is = 0x002312
PCI Sub-system Vendor ID is = 0x00103c
PCI Sub-system ID is = 0x0012c7
PCI Mode = PCI-X 133 MHz
ISP Code version = 3.3.175
ISP Chip version = 3
Topology = PTTOPT_FABRIC
Link Speed = 2Gb
Local N_Port_id is = 0x190500
Previous N_Port_id is = None
N_Port Node World Wide Name = 0x50060b0000386d1b
N_Port Port World Wide Name = 0x50060b0000386d1a
Switch Port World Wide Name = 0x200500051e35fafc
Switch Node World Wide Name = 0x100000051e35fafc
Driver state = ONLINE
Hardware Path is = 0/3/1/0/4/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.11.16 /ux/kern/kisu/FCD/src/common/wsio/fcd_init.c:Jun 11 2008,13:35:21
root@lawhchdb:/root
#
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 12:00
Failover mode 1 ?
sac3scott
105 Posts
0
December 22nd, 2011 12:00
Yes 1 - enabled - HP no auto trepass are the settings on vnx...just as soon as it is zoned to vnx it seems to drop hba connectivity on one fabric...
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 12:00
how's each HBA zoned ?
sac3scott
105 Posts
0
December 22nd, 2011 12:00
all single initiator single target...4 paths..A5/B6 on one fabric A6/B5 on another for example....
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 13:00
what kind of fiber channel switch are you using ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 13:00
the system is using PowerPath or Native PVLinks ?
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 13:00
if hba 1 is zoned to SPA5 , can you zone hba 2 to SPA6 ..do you see issues then ? Or it only happens when SPB is introduced ? What's in the OS log when this happens ?
sac3scott
105 Posts
0
December 22nd, 2011 13:00
EMC did that and it can see the disks ok with one..it is when the second is introduced that issues arise on VNX and CX4.
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 22nd, 2011 13:00
can you zone one HBA to one port only ..curious what happens.
sac3scott
105 Posts
0
December 22nd, 2011 14:00
Powerpath. Brocade 4900 switch
Sent from Blackberry
dynamox
2 Intern
2 Intern
•
20.4K Posts
0
December 23rd, 2011 18:00
what's in the system log when it experiences disconnect ?
AlfonsoC
2 Posts
0
December 27th, 2011 15:00
Maybe I'm asking for something that has been done, but... have you modified zoning to show the targets of the vnx on the same existing CX <-> HPUX zone? or you're creating a completely independent new zone for the VNX ports?
sac3scott
105 Posts
0
December 27th, 2011 18:00
New zones. We only use single initiator single target normally
Sent from Blackberry
AlfonsoC
2 Posts
0
December 28th, 2011 06:00
I'm assuming that each FC goes to one different and independent fabrics (fabric A and B).
For LVM migration of data (pvadd/pvmove/pvreduce...) you need to have all two storage systems on the same initiator (one port from the CX4, one port of the VNX and the FC hba) on the same zone. Take into account that all LVM operations could be done transparently when host is running (watch for system load). Been there, done that for several TB's 'on the fly'.
Your zoning for that particular host should be like:
Fabric A: fc0 / CX4 host port / VNX host port (painted lines in yellow).
Fabric B: fc1 / CX4 host port / VNX host port (painted lines in red).
If quantity of data is not very big you could do it with only one fc, but thinking that you're migrating it's better to do it on the two FC ports, setup them and remove old storage from zoning when done.
Look for the attachment I did.
HTH.
P.S: Sorry for the sh*tty diagram, but for taking a general idea should suffice.