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 HPUX
vxreattach
vxreattach(1M) vxreattach(1M)
NAME
vxreattach - reattach disk drives that have once again become accessible
SYNOPSIS
/etc/vx/bin/vxreattach [-br ] [accessname...]
/etc/vx/bin/vxreattach -c accessname
DESCRIPTION
The vxreattach utility reattaches disks to the disk group they were in and retains the same media name.
This operation may be necessary if a disk has a transient failure, or if Veritas Volume Manager (VxVM) starts with some disk drivers
unloaded and unloadable. Disks then enter the failed state. If the problem is fixed, vxreattach may be able to reattach the disks without
plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started.
vxreattach tries to find a disk in the same disk group with the same disk ID for the disk(s) to be reattached. The reattach operation may
fail even after finding the disk with the matching disk ID if the original cause (or some other cause) for the disk failure still exists.
vxreattach is usually invoked by vxdiskadm when performing disk recovery. It is not intended to be run directly by an administrator.
OPTIONS
-b Performs the reattach operation in the background.
-c Checks if a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the
disk can be reattached is displayed.
-r Tries to recover stale plexes of any volumes on the failed disk. It does this by calling vxrecover.
EXIT CODES
A zero exit status is returned if the reattach is performed; non-zero is returned otherwise.
See vxintro(1M) for a list of standard exit codes.
EXAMPLES
Check if reattachment of disk c1t2d0 is possible:
/etc/vx/bin/vxreattach -c c1t2d0
If reattachment is possible, vxreattach returns with an exit status of 0 and displays the disk group name and disk media name. If reat-
tachment is not possible, vxreattach returns an exit status of 2 and displays an error.
Attempt to reattach the disk in the foreground and try to recover stale plexes of any volumes on the disk:
/etc/vx/bin/vxreattach -r c1t2d0
If the reattachment is successful, vxreattach returns an exit status of 0. Otherwise, if an error occurs, vxreattach returns a non-zero
exit code as defined on vxintro(1M).
FILES
/etc/default/vxplex Standard defaults file that can be used to determine whether FastResync is used when attaching plexes. See vxplex(1M)
for details.
SEE ALSO
vxdiskadm(1M), vxintro(1M), vxplex(1M), vxrecover(1M)
VxVM 5.0.31.1 24 Mar 2008 vxreattach(1M)