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 DEBIAN
atapicam
ATAPICAM(4) BSD Kernel Interfaces Manual ATAPICAM(4)
NAME
atapicam -- CAM XPT (transport) module for ATAPI devices
SYNOPSIS
To compile this driver into the kernel, place the following lines in your kernel configuration file:
device scbus
device ata
device atapicam
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
atapicam_load="YES"
DESCRIPTION
The ATAPI/CAM module allows ATAPI devices (CD-ROM, CD-RW, DVD drives, floppy drives such as Iomega Zip, tape drives) to be accessed through
the SCSI subsystem, cam(4).
ata(4) and scbus(4) must be configured in the kernel as well. The SCSI target drivers (cd(4), da(4), or st(4)) can then be used to access
the devices. The generic passthrough device, pass(4), can also be used to send SCSI commands directly to the devices through the CAM API.
A separate CAM bus is created for each ATA bus in the system. On each of these buses, target ID 0 is assigned to the master device, and ID 1
is assigned to the slave (provided they are ATAPI devices).
IMPLEMENTATION NOTES
Some SCSI commands are intercepted by the driver, and undergo special processing in order to work around limitations of ATAPI devices. Such
limitations can be consequences of the ATAPI specification. For example, ATAPI devices do not implement the 6-byte versions of MODE_SELECT,
MODE_SENSE, READ, or WRITE. They can also be common bugs, such as hanging when queried for extended INQUIRY information.
EXAMPLES
device ata
device atapicam
device scbus
device cd
device pass
Add the atapicam driver to the kernel.
camcontrol devlist
Print the list of all devices available through CAM.
mount -t cd9660 /dev/cd0 /mnt
Mount a CD-ROM from an ATAPI CD-ROM drive (the command above assumes that the ATAPI drive is the only CD-ROM unit).
SEE ALSO
ata(4), cam(4), scsi(4), atacontrol(8), camcontrol(8)
HISTORY
The ATAPI/CAM driver first appeared in FreeBSD 4.8 and FreeBSD 5.0.
AUTHORS
The ATAPI/CAM driver was written by Thomas Quinot <thomas@FreeBSD.org>.
BUGS
atapicam and ATAPI-specific target drivers (acd(4), ast(4), and afd(4)) can be configured in the same kernel. Simultaneous access to the
same device through the SCSI generic drivers and the ATAPI-specific drivers may cause problems and is strongly discouraged.
BSD
October 22, 2009 BSD