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 OPENSOLARIS
fp
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. The fp driver also discovers devices in N_Port point-to-point topologies.
CONFIGURATION
The fp driver is configured by defining properties in the fp.conf file. Note that you must reboot the system to have any changes you make
to fp.conf take effect. 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 mul-
tipathing 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 configuration of devices.
pwwn-lun-blacklist
Allows you to specify target port WWNs and LUN numbers you do not want configured. LUN numbers are interpreted as decimals. White spa-
ces and commas (',') can be used in the list of LUN numbers.
#
# pwwn-lun-blacklist=
# "target-port-wwn,lun-list"
#
# To prevent LUNs 1 and 2 from being configured for target
# port 510000f010fd92a1 and target port 510000e012079df1, set:
#
# pwwn-lun-blacklist=
# "510000f010fd92a1,1,2",
# "510000e012079df1,1,2";
#
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 |Uncommitted |
+-----------------------------+-----------------------------+
|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
NOTES
In N_Port point-to-point topologies, FCP error recovery does not work across events such as link bounce/cable pull. I/O to devices with
FCP-2/FCP-3 support (for example, FC tape drives) will be disrupted by such events.
SunOS 5.11 10 Jan 2008 fp(7d)