04-02-2019
Quote:
it depends on the layout of your FC fabric and it depends on your FC switches and how they are connected and zoned and, .... You see the problem?
Yes I see it and understand what you want to convey. By some reasons, I have not enough info to assess.
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 folks,
does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies
4. AIX
Can anyone recommend me some reading material surrounding how AIX handles LUNs:
- with and without MPIO installed
- with and without SDD or SDDPCM installed
Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed?
I guess... (0 Replies)
Discussion started by: apra143
0 Replies
5. AIX
On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem.
The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like
5.3 TL3 = IBM.MPIO 5.3.0.30
5.3... (0 Replies)
Discussion started by: clking
0 Replies
6. 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
7. AIX
Hello,
we are planning to deploy some of our databases on AIX/LPAR based servers (we didn't bought it yet ...). IBM's engineers says that if we want to boot them from SAN the hardware array has to be compatible with MPIO but they don't want to deliver any document with list of arrays supported... (5 Replies)
Discussion started by: andy55
5 Replies
8. 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
9. AIX
I have found failed mpio path on AIX and enabled that failed path as below
failed path on AIX
bash-3.2# lspath -l hdisk10
Enabled hdisk10 fscsi0
Enabled hdisk10 fscsi0
Failed hdisk10 fscsi3
Enabled hdisk10 fscsi3
Enabled failed path as below
chpath -l hdisk10 -p fscsi3 -s enable... (13 Replies)
Discussion started by: murali969
13 Replies
10. AIX
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies
LEARN ABOUT OSF1
volunroot
volunroot(8) System Manager's Manual volunroot(8)
NAME
volunroot - Remove Logical Storage Manager hooks for rootable volumes
SYNOPSIS
/usr/sbin/volunroot [-a | -A]
OPTIONS
Specifies that all volumes on the system disk be converted back to UNIX disk partitions, not just the root and swap volumes, rootvol and
swapvol. Forces removal of the private region unless it is the last one in the system.
DESCRIPTION
The volunroot script can be used to restore the accessibility of the root, swap, and other file systems on the boot disk directly through
disk partitions instead of through volume devices. The script also removes other changes that were made to enable booting of the system
from the root volume, so that the system will boot with no dependency on the Logical Storage Manager.
When used with no options, volunroot affects only the root and swap volumes, rootvol and swapvol.
For volunroot to work properly, only one plex must exist for each of the affected volumes. This plex must be the one created by volrootmir
or the original plex created when the root disk was encapsulated. This ensures that the underlying subdisks will have equivalent partitions
defined for them on the disk.
If these conditions are not met, the volunroot operation fails and none of the volumes are converted to disk partitions.
The unwanted plexes can be removed using either voledit or volplex.
SEE ALSO
volencap(8), voldiskadm(8), voledit(8), volintro(8), volplex(8), volrootmir(8)
volunroot(8)