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
LEARN ABOUT HPUX
st_ats_enable
st_ats_enable(5) File Formats Manual st_ats_enable(5)
NAME
st_ats_enable - determine whether to reserve a tape device on open
VALUES
Default
Allowed values
Recommended values
DESCRIPTION
Note: this tunable was named in releases prior to HP-UX 11i v3.
This tunable notifies the stape or estape driver whether it needs to reserve a tape device on open and subsequently release it on close.
When this tunable is on, the stape or estape driver will attempt to reserve any tape device on open. The driver has a few tape devices
flagged as suitable devices for this functionality including: DLT 8000, DLT 7000, STK 9840, HP Ultrium, and others. DDS drives are not
flagged for this functionality.
The tunable allows the safe sharing of tape devices in multinode configurations like MC/ServiceGuard's Advanced Tape Sharing. The auto-
matic reserve and release protects the tape device from being accessed from multiple nodes, which would corrupt a backup. If the reserve
portion of the stape or estape driver's open routine fails, a status of is returned.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately and are used during the next open or close.
When Should the Tunable Be Turned On?
This tunable should be turned on if the system is going to be used in an MC/ServiceGuard's Advanced Tape Sharing configuration or the user
wants the stape or estape driver to use automatic reserve and release on open and close for multinode manageability.
What Are the Side Effects of Turning the Tunable On?
A reserve is sent to the tape device by the stape or estape driver on open and a release is sent on close. No other initiator or HBA will
be able to access the tape device while it is opened on another initiator or HBA.
When Should the Tunable Be Turned Off?
This tunable should be turned off for any SAN tape sharing solution configuration other than ATS. Most multinode backup applications (for
example, Omniback) manage device reservation themselves, and any interference by the stape or estape driver may produce problems. This
tunable should also be turned off for any multiplatform SAN configuration to keep tape access across platforms more uniform.
What Are the Side Effects of Turning the Tunable Off?
Unauthorized access from another initiator might interfere with any current tape operation.
What Other Tunables Should Be Changed at the Same Time?
None.
EXAMPLES
Query the current value of the tunable:
Set the value of the tunable to
To save the value of the tunable across reboots:
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
SEE ALSO
scsi_tape(7), scsimgr_estape(7).
Tunable Kernel Parameters st_ats_enable(5)