Sponsored Content
Operating Systems AIX Migrating hdisks from vscsi to NPIV with powerpath Post 302543505 by zxmaus on Monday 1st of August 2011 03:43:08 AM
Old 08-01-2011
Hi,

of course importvg will recognize the data on the hdiskpower devices, the two 'hdisks' on emc are only paths to the same physical disk.

We did this kind of migrations in both directions - from powerpath to vio and the other way round - and haven't seen any issues so far.

Regards
zxmaus
This User Gave Thanks to zxmaus For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

change SP value in powerpath

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

Anyone using NPIV?

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

Vscsi and npiv on same adapter

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

hdisk mapping to a vSCSi Adapter

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

NPIV mapping problem

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

NPIV custom WWN

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

VIOS FC Mapping/NPIV questions

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

Kdb - vscsi disk mapping from AIX 5.3 CLIENT side

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

How to put vscsi in available state?

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

Devices.vscsi.disk ?

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
UDISKS(7)							      udisks								 UDISKS(7)

NAME
udisks - Storage Management DESCRIPTION
udisks provides an interface to enumerate storage devices and perform operations on them. Any application can access the org.freedesktop.UDisks service on the system message bus. Some operations (such as formatting disks etc.) is restricted using polkit. DEVICE INFORMATION
On Linux, udisks relies on recent versions of udev(7) and the kernel. Influential device properties in the udev database include: UDISKS_PRESENTATION_HIDE If set to 1 this is a hint to presentation level software that the device should not be shown to the user. UDISKS_PRESENTATION_NOPOLICY If set to 1 this is a hint to presentation level software that the device should not be automounted or autoassembled (for e.g. components of a multi-disk device). UDISKS_DISABLE_POLLING If set to 1 this will disable the polling of drives for media changes, for devices which do not send out media notifications by themselves (this mostly affects CD drives). Some CD drives cause bad effects such as very high CPU usage when being polled. UDISKS_PRESENTATION_NAME The name to user for the device when presenting it to the user. UDISKS_PRESENTATION_ICON_NAME The icon to use when presenting the device to the user. If set, the name must follow the freedesktop.org icon theme specification. The ID_DRIVE_* properties are used to describe what kind of physical media can be used in a device. These are typically set on the main block device (e.g. /dev/sdb) and more than one these properties can be set if the device supports multiple kinds of media. ID_DRIVE_EJECTABLE Whether the media in the drive is physically ejectable. Only set this to 1 (or 0) if the drive truly uses (or doesn't) ejectable media. In particular, it is not necessary to set this for e.g. iPod or Kindle devices where it is necessary to send a command via eject(1) since the desktop user session will offer this option for removable devices regardless of whether they are ejectable. If this property is not set, a heuristic will be used to determine if the media is ejectable (drives using optical, Zip or Jaz media are considered ejectable). ID_DRIVE_DETACHABLE Whether the device is detachable. It is only meaningful to set this to 0 (to avoid marking a device as detachable) since the code for detaching the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive is detachable (currently only devices connected through USB are detachable). ID_DRIVE_CAN_SPINDOWN Whether the device can spin down. It is only meaningful to set this to 0 (to avoid marking a device as being capable of spinning down) since the code for spinning down the device is part of udisks itself. If this property is not set, a heuristic will be used to determine if the drive can spin down (currently only ATA devices, including those USB devices with a SAT layer) can be spun down). ID_DRIVE_FLASH The device is compatible with flash. ID_DRIVE_FLASH_CF The device is compatible with Compact Flash. ID_DRIVE_FLASH_MS The device is compatible with Memory Stick. ID_DRIVE_FLASH_SM The device is compatible with SmartMedia. ID_DRIVE_FLASH_SD The device is compatible with SecureDigital. ID_DRIVE_FLASH_SDHC The device is compatible with High-Capicity SecureDigital. ID_DRIVE_FLASH_MMC The device is compatible with MultiMediaCard. ID_DRIVE_FLOPPY The device is compatible with floppy disk. ID_DRIVE_FLOPPY_ZIP The device is compatible with Zip. ID_DRIVE_FLOPPY_JAZ The device is compatible with Jaz. The ID_DRIVE_MEDIA_* properties describe the current media in a device. As with the ID_DRIVE_* properties, these properties are typically set on the main block device (e.g. /dev/sdb). Typically only one of these properties are set. ID_DRIVE_MEDIA_FLASH The physical media currently inserted into the device is flash. ID_DRIVE_MEDIA_FLASH_CF The physical media currently inserted into the device is Compact Flash. ID_DRIVE_MEDIA_FLASH_MS The physical media currently inserted into the device is Memory Stick. ID_DRIVE_MEDIA_FLASH_SM The physical media currently inserted into the device is SmartMedia. ID_DRIVE_MEDIA_FLASH_SD The physical media currently inserted into the device is SecureDigital. ID_DRIVE_MEDIA_FLASH_SDHC The physical media currently inserted into the device is High-Capicity SecureDigital. ID_DRIVE_MEDIA_FLASH_MMC The physical media currently inserted into the device is MultiMediaCard. ID_DRIVE_MEDIA_FLOPPY The physical media currently inserted into the device is floppy disk. ID_DRIVE_MEDIA_FLOPPY_ZIP The physical media currently inserted into the device is Zip. ID_DRIVE_MEDIA_FLOPPY_JAZ The physical media currently inserted into the device is Jaz. REMOTE CLIENTS
TODO: write me. AUTHOR
Written by David Zeuthen david@fubar.dk with a lot of help from many others. BUGS
Please send bug reports to either the distribution bug tracker or the upstream bug tracker at http://bugs.freedesktop.org/enter_bug.cgi?product=udisks. SEE ALSO
udev(7), polkit(8), udisks-daemon(8), udisks-tcp-bridge(1), udisks(1) udisks March 2008 UDISKS(7)
All times are GMT -4. The time now is 05:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy