- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: VMAX FE port change and impact on LUN paths
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-26-2018 03:41 AM - edited тАО01-26-2018 03:42 AM
тАО01-26-2018 03:41 AM - edited тАО01-26-2018 03:42 AM
Hi
Running HPUX B.11.31, we are currently connected to customer SAN via 2 x HBA cards and have 4 paths to 4 LUNS. Customer has advised us that they are going to change 2 of the FE ports. I am concerned that this will lose 2 paths for every LUN and we will have to recreate these but I have also read that HPUX B.11.31 using agile paths, this will sort itself out. Below are the outputs of various commands. Wondering if anyone could shed some light on this and outline what we would have to do to recreate the paths if half of them disappear after the FE port change?
ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=====================================================================
disk 19 0/3/0/0/0/0.23.11.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c13t0d1 /dev/rdsk/c13t0d1
disk 20 0/3/0/0/0/0.23.11.0.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c13t0d2 /dev/rdsk/c13t0d2
disk 21 0/3/0/0/0/0.23.11.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c13t0d3 /dev/rdsk/c13t0d3
disk 41 0/3/0/0/0/0.23.11.0.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c13t0d4 /dev/rdsk/c13t0d4
disk 22 0/3/0/0/0/0.23.20.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c15t0d1 /dev/rdsk/c15t0d1
disk 23 0/3/0/0/0/0.23.20.0.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c15t0d2 /dev/rdsk/c15t0d2
disk 24 0/3/0/0/0/0.23.20.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c15t0d3 /dev/rdsk/c15t0d3
disk 42 0/3/0/0/0/0.23.20.0.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c15t0d4 /dev/rdsk/c15t0d4
disk 25 0/6/0/0/0/0/2/0/0/0.24.9.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c17t0d1 /dev/rdsk/c17t0d1
disk 26 0/6/0/0/0/0/2/0/0/0.24.9.0.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c17t0d2 /dev/rdsk/c17t0d2
disk 27 0/6/0/0/0/0/2/0/0/0.24.9.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c17t0d3 /dev/rdsk/c17t0d3
disk 38 0/6/0/0/0/0/2/0/0/0.24.9.0.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c17t0d4 /dev/rdsk/c17t0d4
disk 28 0/6/0/0/0/0/2/0/0/0.24.23.0.0.0.1 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c19t0d1 /dev/rdsk/c19t0d1
disk 29 0/6/0/0/0/0/2/0/0/0.24.23.0.0.0.2 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c19t0d2 /dev/rdsk/c19t0d2
disk 30 0/6/0/0/0/0/2/0/0/0.24.23.0.0.0.3 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c19t0d3 /dev/rdsk/c19t0d3
disk 39 0/6/0/0/0/0/2/0/0/0.24.23.0.0.0.4 sdisk CLAIMED DEVICE EMC SYMMETRIX
/dev/dsk/c19t0d4 /dev/rdsk/c19t0d4
disk 0 0/6/0/0/0/0/4/0/0/0.0.0 sdisk CLAIMED DEVICE HP LOGICAL VOLUME
/dev/dsk/c2t0d0 /dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s1 /dev/rdsk/c2t0d0 /dev/rdsk/c2t0d0s3
/dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0s1
disk 2 255/1/0.0.0 sdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0
root@dr:/dev> fcmsutil /dev/fcd0
Vendor ID is = 0x1077
Device ID is = 0x2532
PCI Sub-system Vendor ID is = 0x103C
PCI Sub-system ID is = 0x3262
PCI Mode = PCI Express x8
ISP Code version = 5.4.4
ISP Chip version = 2
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x179e00
Previous N_Port_id is = 0x189e00
N_Port Node World Wide Name = 0x500143801209d579
N_Port Port World Wide Name = 0x500143801209d578
Switch Port World Wide Name = 0x209e00051e363342
Switch Node World Wide Name = 0x100000051e363342
N_Port Symbolic Port Name = ccslivdr_fcd0
N_Port Symbolic Node Name = ccslivdr_HP-UX_B.11.31
Driver state = ONLINE
Hardware Path is = 0/3/0/0/0/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
TYPE = PFC
NPIV Supported = YES
Driver Version = @(#) fcd B.11.31.1203%372 Jan 7 2012
root@dr:/dev> fcmsutil /dev/fcd1
Vendor ID is = 0x1077
Device ID is = 0x2532
PCI Sub-system Vendor ID is = 0x103C
PCI Sub-system ID is = 0x3262
PCI Mode = PCI Express x8
ISP Code version = 5.4.4
ISP Chip version = 2
Topology = PTTOPT_FABRIC
Link Speed = 4Gb
Local N_Port_id is = 0x189e00
Previous N_Port_id is = 0x179e00
N_Port Node World Wide Name = 0x500143801209d561
N_Port Port World Wide Name = 0x500143801209d560
Switch Port World Wide Name = 0x209e00051e363002
Switch Node World Wide Name = 0x100000051e363002
N_Port Symbolic Port Name = ccslivdr_fcd1
N_Port Symbolic Node Name = ccslivdr_HP-UX_B.11.31
Driver state = ONLINE
Hardware Path is = 0/6/0/0/0/0/2/0/0/0
Maximum Frame Size = 2048
Driver-Firmware Dump Available = NO
Driver-Firmware Dump Timestamp = N/A
TYPE = PFC
NPIV Supported = YES
Driver Version = @(#) fcd B.11.31.1203%372 Jan 7 2012
root@dr:/dev> vgexport -s -p -v -m vg01.mapfile /dev/vg01 - 1Tb /cncop_data /cncop_recov
Beginning the export process on Volume Group "/dev/vg01".
/dev/dsk/c15t0d3
/dev/dsk/c13t0d3
/dev/dsk/c17t0d3
/dev/dsk/c19t0d3
vgexport: Preview of vgexport on volume group "/dev/vg01" succeeded.
root@ccslivdr:/dev> vgexport -s -p -v -m vg03.mapfile /dev/vg03 - 512Gb /backup /shared /oracel_diag /RMAN_backups
Beginning the export process on Volume Group "/dev/vg03".
/dev/dsk/c15t0d2
/dev/dsk/c13t0d2
/dev/dsk/c17t0d2
/dev/dsk/c19t0d2
vgexport: Preview of vgexport on volume group "/dev/vg03" succeeded.
root@ccslivdr:/dev> vgexport -s -p -v -m vg05.mapfile /dev/vg05 - 128Gb /trn_recov /trn_data /trn_oracle_diag /trn_RMAN_backups /trn_backup
Beginning the export process on Volume Group "/dev/vg05".
/dev/dsk/c15t0d1
/dev/dsk/c13t0d1
/dev/dsk/c17t0d1
/dev/dsk/c19t0d1
vgexport: Preview of vgexport on volume group "/dev/vg05" succeeded.
root@ccslivdr:/dev> vgexport -s -p -v -m vg07.mapfile /dev/vg07 - 300Gb /archive
Beginning the export process on Volume Group "/dev/vg07".
/dev/dsk/c17t0d4
/dev/dsk/c19t0d4
/dev/dsk/c13t0d4
/dev/dsk/c15t0d4
vgexport: Preview of vgexport on volume group "/dev/vg07" succeeded.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2018 10:56 PM
тАО01-30-2018 10:56 PM
SolutionHello Lufc,
Greetings !!!
As I understand that, you are not using agile DSF. Hence, there might be chances of losing the path if there are any changes in the SAN / Switch.
1) convert the legacy DSF to agile -
# vgdsf -c vg01
2) The path to the above command is /usr/contrib/bin/vgdsf
3) Perform the above command for all the VGs.
4) Take the back up of map files and verify if it has the agile DSF.
# vgexport -p -v -s -m /tmp/vg01.map /dev/vg01
5) While restoring from the map files use -N for agile DSF.
# vgimport -v -s -N -m /tmp/vg01.map /dev/vg01
6) Having map files before and after SAN changes will help us in restoring the VG, if there are any surprises while performing SAN changes.
7) Apart from map files, please take the backup of /etc/lvmtab, /etc/lvmtab_p and /etc/lvmconf
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-05-2018 03:25 AM - edited тАО02-07-2018 02:29 AM
тАО02-05-2018 03:25 AM - edited тАО02-07-2018 02:29 AM
Re: VMAX FE port change and impact on LUN paths
Hi
Thanks for your response - one issue I have is that we have a 2 node active/passive cluster and a DR server. In a DR scenario we shut down the cluster and then after the SAN LUNs have been moved to the DR site we would activate the volume groups on the DR server.
Currently the cluster is active and it seems that to run the vgdsf command on the DR server would need the vgchange -a y command executed for every volume group on the DR server, but as these volume groups are already active on the active cluster node what would be the impact of making them active on the DR server even for a short time?
Found that vgchange -a r does not allow vgdsf to work. After speaking to SAN team they informed that the LUNa assigned in read only mode so went ahead with the vgdsf. Port changes happen early Tuesday morning so will check after that.
Teh port changes were made and as expect 8 of the paths were showing NO_HW. I ran ioscan and this created 4 new devices. I ran ioscan again but the missing 4 devices never appeared. I rebooted the server and the 4 new devices appeared and all the old devices showing as NO_HW disappeared.
I activated teh volume groups in read-only mode and confirmed the size and configuation of each one agaisnt those activated on the live server and all looked OK.
Is this what would be expected? Is there anythng else I would need to do? We are due to failover to this server on 8th to enable Brocade switch changes on the live site to take place.
Thanks