07-01-2011
Migrating hdisks from vscsi to NPIV with powerpath
Hi All,
I'm preparing to migrate some servers from vscsi to pass-thru NPIV. I am planning to have the SAN team move the exact LUNs from vio1/vio2 to those two VWWN through NPIV.
My question is on the partition itself.. right now, let's say I have hdisk0/1/2/3/4 that are part of datavg. They are virtual SCSI drives with two paths (vio1 / vio2).
I have installed powerpath and EMC ODM defs (those are symmetrix luns). When I varyoff/exportvg the old LUNs, and discover the new ones through NPIV, they will show up as "hdiskpower" devices.
Will the importvg actually recognize the data on hdiskpower devices or will it try and import the "hdisk" devices under the hdiskpower?
Or is there a specific migration path to follow?
Thanks for your help!
Frank.
10 More Discussions You Might Find Interesting
1. Solaris
How to change the following values in power path from SP B to SP A ?
Owner: default=SP B, current=SP B
this is excerpt from powermt display dev=all (3 Replies)
Discussion started by: fugitive
3 Replies
2. AIX
Is anyone here using NPIV with AIX? If you are, what type of switch are you connected to? Also, please share some impressions of NPIV over traditional port-to-port LUN assignments. We are looking to move to NPIV and need some convincing argume... I mean information. (2 Replies)
Discussion started by: kah00na
2 Replies
3. AIX
Hi,
I want to change from vscsi to npiv. Is it possible to use both on the same adapter, so we can change the systems one by one, or must we place a second FC adapter in the VIO servers?
Thanks,
Ronald (2 Replies)
Discussion started by: ronaldm60
2 Replies
4. AIX
Hello,
I have a VIOS System and would like to do mapping some hdisks, hdisk160 until hdisk165 to a vSCSi Adapter. I try to do this in the oem_setup_env like the following:
for i in $(lspv | grep hdisk* | awk {'print $1'};
do
mkdev -V $i -p vhost20
done
There where a mapping with... (4 Replies)
Discussion started by: torsten163
4 Replies
5. AIX
Hello all I hope someone can help me with this. I have a single LPAR which is supplied a rootvg and datavg disk set from a dual VIO server configuration. I see dual path disks for all the datavg disks but only see one path for the rootvg disks.
The client LPAR has the following:
fcs0 ... (3 Replies)
Discussion started by: johnf
3 Replies
6. AIX
Hi All :)
i would like to know if i can customize the WWN of the new VFC (NPIV).
Or, if i must move the LPAR on another server with another FCS, i have to change the zoning??
Thanks in advance.
Mario
---------- Post updated 09-21-12 at 02:51 AM ---------- Previous update was 09-20-12 at... (1 Reply)
Discussion started by: Zio Bill
1 Replies
7. AIX
Please forgive me here as I don't fully understand what I am talking about here so if I use the wrong terminology please overlook me.
We have multiple AIX LPARs on the managed system with two VIO Servers. A Co-Worker and I are trying to set up a new LPAR client (The guy that knows this is out)... (14 Replies)
Discussion started by: juredd1
14 Replies
8. AIX
If you're familiar with vscsi mappings thru a VIO Server, you are probably aware, on an AIX 6.1 Client LPAR, that:
print cvai | kdbcan provide useful information to you.... like VIO Server name & vhost #. But, "cvai" does not appear to be part of the Kernel Debugger in AIX 5.3.
My question is... (3 Replies)
Discussion started by: The Doctor
3 Replies
9. AIX
Hello Friends,
My question/problem is that I noticed 2 servers in my environment vscsi is showing up as defined (not available) or is defined and not showing the path to both vscsi's when ruining lspath command. I am new to AIX admin, work alone, and work in an small environment. My question is,... (12 Replies)
Discussion started by: Adnans2k
12 Replies
10. AIX
Hello,
When I assigned CDROM from IVM (VIOS) to LPAR and then running cfgmgr i get the following message on the client lpar
#cfgmgr
cfgmgr: 0514-621 WARNING: The following device packages are required for device support but are not currently installed.
devices.vscsi.disk
searching... (0 Replies)
Discussion started by: filosophizer
0 Replies
LEARN ABOUT HPUX
st_san_safe
st_san_safe(5) OBSOLETED st_san_safe(5)
NAME
st_san_safe - determine whether access to tape device special files without the no-rewind-on-close option is allowed (OBSOLETED)
VALUES
Failsafe
Default
Allowed values
Recommended values
or
DESCRIPTION
Note: this tunable is obsoleted and has been renamed to beginning with release HP-UX 11i v3.
This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When
this tunable is on the tape driver will fail any open on a tape device special file without the no-rewind-on-close option (that is, or with
a status of
The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files
without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from
HP-UX systems via standard tape commands like which would corrupt a backup in process.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Tunable Be Turned On?
This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration.
What Are the Side Effects of Turning the Tunable On?
The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This
behavior prevents the usage of any tape device special file without the no-rewind-on-close option.
When Should the Tunable Be Turned Off?
This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not
function unless it has access to device special files without the no-rewind-on-close option.
What Are the Side Effects of Turning the Tunable Off?
A rewind may be issued from this system accidentally on close possibly corrupting a backup being issued from another system on the SAN.
What Other Tunables Should Be Changed at the Same Time?
None.
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 Hewlett-Packard.
SEE ALSO
norewind_close_disabled(5), scsi_tape(7), scsimgr_estape(7).
Tunable Kernel Parameters st_san_safe(5)