06-10-2015
Is the HPUX in question v2 or v3 ?
If the answer is v3, the operation can be online, since on v3, every lun has a WWID.
Just do it port by port, rescan and check paths after each, should not be any issues.
If you want to do it offline, do a vgexport preview (to a file not actual export) of all volume groups on the system using SAN disks (just to be safe do it anyway in each scenario) and deactivate the volume group.
Since the VG info is actually written on disks, even if everything changes (disk names etc.) you will be able to import the volume group using a file you created earlier. There are also other methods (vgscan), but this one is most trivial.
Commands you will require are
scsimgr -> to check lunmap and paths before and after.
ioscan -> to rescan after port change.
This assumes you are using hpux native multipath, not other multipath solutions.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
2. Solaris
Using Solaris 10 with Veritas Storage Foundation running. I want to copy all contents from DISKA LUN1 to DISKB LUN2. What would be the command syntax to do this? (0 Replies)
Discussion started by: soupbone38
0 Replies
3. Solaris
I have a general question regarding Zone Migration.
I have an older system that is currently running a zone configured with ProFTPD & SSL.
If I want to migrate or clone that zone to another (much newer) system, will I still have to setup & configure ProFTPD & SSL on the new system? (3 Replies)
Discussion started by: em23
3 Replies
4. Red Hat
Hey everyone.
I am working on designing a logging solution for a deployment we have going out in a few months. Right now we have a single storage head end, connected via fibre to a SAN. Basically the plan is to create a number of smaller LUNs on the SAN, and then use LVM2 to handle concatenating... (5 Replies)
Discussion started by: msarro
5 Replies
5. HP-UX
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies
6. Solaris
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
7. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
8. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
9. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
10. Solaris
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
fp(7d) Devices fp(7d)
NAME
fp - Sun Fibre Channel port driver
DESCRIPTION
The fp driver is a Sun fibre channel nexus driver that enables fibre channel topology discovery, device discovery, fibre channel adapter
port management and other capabilities through well-defined fibre channel adapter driver interfaces.
The fp driver requires the presence of a fabric name server in fabric and public loop topologies to discover fibre channel devices. In pri-
vate loop topologies, the driver discovers devices by performing PLOGI to all valid AL_PAs, provided that devices do not participate in
LIRP and LILP stages of loop initialization.
CONFIGURATION
The fp driver is configured by defining properties in the fp.conf file. The fp driver supports the following properties:
mpxio-disable
Solaris I/O multipathing is enabled or disabled on fibre channel devices with the mpxio-disable property. Specifying mpxio-disable="no"
activates I/O multipathing, while mpxio-disable="yes" disables the feature.
Solaris I/O multipathing may be enabled or disabled on a per port basis. Per port settings override the global setting for the specified
ports. The following example shows how to disable multipathing on port 0 whose parent is /pci@8,600000/SUNW,qlc@4:
name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0
mpxio-disable="yes";
manual_configuration_only
Automatic configuration of SCSI devices in the fabric is enabled by default and thus allows all devices discovered in the SAN zone to be
enumerated in the kernel's device tree automatically. The manual_configuration_only property may be configured to disable the default
behavior and force the manual configuration of the devices in the SAN. Specifying manual_configuration_only=1 disables the automatic con-
figuration of devices.
FILES
/kernel/drv/fp
32-bit ELF kernel driver (x86)
/kernel/drv/amd64/fp
64-bit ELF kernel driver (x86)
/kernel/drv/sparcv9/fp
64-bit ELF kernel driver (SPARC)
/kernel/drv/fp.conf
fp driver configuration file.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|mpxio-disable |Unstable |
+-----------------------------+-----------------------------+
|manual_configuration_only |Obsolete |
+-----------------------------+-----------------------------+
|Availability |SUNWfctl |
+-----------------------------+-----------------------------+
SEE ALSO
cfgadm_fp(1M), prtconf(1M), stmsboot(1M), driver.conf(4), attributes(5), fcp(7D), fctl(7D), scsi_vhci(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Generic Services (FC-GS-2) Project 1134-D
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Protocol for SCSI (FCP) ANSI X3.269-1996
SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Loop Attachment (FC-FLA), NCITS TR-20:1998
SunOS 5.10 2 Dec 2004 fp(7d)