11-17-2008
So if I got it right, MPIO recognizes by itself which paths are available and makes the single volume visible/usable. There is nothing to do with mkpatch, chpath or lspath to configure like load balancing or failover or anything?
I thought you needed those commands to configure something 1st or whatever.
Edit: Also if there is a lot of different paths / SAN volumes visible, maybe I just don't want to handle all of them with MPIO (automatically if that is the case from the writings above). Do I have a choice?
Last edited by zaxxon; 11-17-2008 at 08:42 AM..
Reason: Added a thought/demand
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies
2. AIX
Hi
I would like to ask what the benefits are of changing from RDAC to MPIO when connecting to a DS4000 on AIX 5.3? I have heard that IBM MPIO "might" support more than 1 active path to a LUN when connecting to a DS4800 through more than 1 host connection on the same AIX client. I understand that... (8 Replies)
Discussion started by: kimyo
8 Replies
3. AIX
Hi,
I was trying to uninstall the native MPIO driver on the AIX 6.1 machine we have in our lab and ran into a whole bunch dependent filesets initially. I deleted the disks, fcsX, fscsiX, fcnetX and tried again, but ran into the same error.
Subsequently, I figured out that the OS disks in... (4 Replies)
Discussion started by: ronykris
4 Replies
4. AIX
Hi,
we have a vew boxes using MPIO and they are connected to some virtualization software managing some disk subsystems, offering volumes to the AIX boxes.
Sometimes when a cable has been plugged out for a test or when a real problem occurs, using lspath to show the state of the paths shows... (8 Replies)
Discussion started by: zaxxon
8 Replies
5. AIX
We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC.
Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers.
My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies
6. AIX
Hello,
Getting this very strange error, made tar/zip through gnu tar
GNU Tar ( successful tar and zip without any errors )
/opt/freeware/bin/tar cvf - /oraapp| gzip > /backup/bkp_15_6_16_oraapp.tgz
GNU unTar error
root@test8:/>gunzip < /config1/bkp_15_6_16_oraapp.tgz |... (5 Replies)
Discussion started by: filosophizer
5 Replies
7. AIX
The company I work for has various AIX servers that I've recently migrated to AIX 7.1 (from 6.1). Some are powerHA clusters some are not. Likewise, the systems engineer that I replaced had net-snmp installed on said clustered systems. Long story short I am re-invoking AIX's native SNMP (v3) for... (1 Reply)
Discussion started by: davix
1 Replies
8. AIX
Hello,
I have some concerns over the disk management of my AIX system.
For example server1
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c vg_2 active
hdisk2 00c1cc14d6de272b ... (6 Replies)
Discussion started by: Phat
6 Replies
9. AIX
Hello,
I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system
/ > lspv
hdisk0 00fa6d1288c820aa rootvg active
hdisk1 00fa6d1288c8213c None
hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies
10. UNIX for Beginners Questions & Answers
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
vgchgid(1M) vgchgid(1M)
NAME
vgchgid - modify the Volume Group ID (VGID) on a given set of physical devices
SYNOPSIS
PhysicalVolumePath [PhysicalVolumePath] ...
DESCRIPTION
The command is designed to change the LVM Volume Group ID (VGID) on a supplied set of disks. will work with any type of storage, but it is
primarily targeted at disk arrays that are able to create "snapshots" or "clones" of mirrored LUNs. accepts a set of raw physical devices
and ensures that they all belong to the same volume group, before altering the VGID (see section).
The same VGID is set on all the disks and it should be noted that in cases of multi-PV volume groups, all the physical volumes should be
supplied in a single invocation of the command.
Options
recognizes the following options and arguments:
PhysicalVolumePath The raw devices path name of a physical volume.
Background
Some storage subsystems have a feature which allows a user to split off a set of mirror copies of physical storage (termed or just as LVM
splits off logical volumes with the command. As the result of the "split," the split-off devices will have the same VGID as the original
disks. is needed to modify the VGID on the BCV devices. Once the VGID has been altered, the BCV disks can be imported into a new volume
group by using
WARNINGS
Once the VGID has been changed, the original VGID is lost until a disk device is re-mirrored with the original devices. If is used on a
subset of disk devices (for example, two out of four disk devices), the two groups of disk devices would not be able to be imported into
the same volume group since they have different VGIDs on them. The solution is to re-mirror all four of the disk devices and re-run on all
four BCV devices at the same time, and then use to import them into the same new volume group.
If a disk is newly added to an existing volume group and no subsequent LVM operations has been performed to alter the structures (in other
words, operations which perform an automated vgcfgbackup(1M)); then it is possible a subsequent will fail. It will report that the disk
does not belong to the volume group. This may be overcome by performing a structure changing operation on the volume group (for example,
using
It is the system administrator's responsibility to make sure that the devices provided in the command line are all Business Copy volumes of
the existing standard physical volumes and are in the ready state and writable. Mixing the standard and BC volumes in the same volume
group can cause data corruption.
RETURN VALUE
returns the following values:
0 VGID was modified with no error
1 VGID was not modified
EXAMPLES
An example showing how might be used:
1. The system administrator uses the following commands to create the Business Continuity (BCV or BC) copy:
1) For EMC Symmetrix disks, the commands are and
2) For XP disk array, the commands are and
Three BCV disks are created.
2. Change the VGID on the BCV disks.
3. Make a new volume group using the BCV disks.
This step can be skipped as the group file will be created automatically. If the file is manually created it will have different major
and minor numbers (see lvm(7)).
4. Import the BCV disks into the new volume group.
5. Activate the new volume group.
6. Backup the new volume group's LVM data structure.
7. Mount the associated logical volumes.
SEE ALSO
vgimport(1M), vgscan(1M), vgcfgbackup(1M).
vgchgid(1M)