08-26-2010
In my case it takes some time for MPIO to rebuild path (VIO + N_portID). We got script that :
-lsdev (look for defined disk) & rmdev (if any)
-lspath (look for missing path) & rmpath
-cfgmgr
8 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
My product have around 10-15 programs/services running in the sun box, which together completes a task, sequentially. Several instances of the each program/service are running in the unix box, to manage the load and for risk-management reasons. As of now, we dont follow a strict strategy in... (2 Replies)
Discussion started by: Deepa
2 Replies
2. 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
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. High Performance Computing
Hi. I am IT manager/developer for a small organization. I have been doing as-needed linux server administration for several years and am by no means an expert. I've built several of my own servers, and our org is currently using hosting services for our servers and I am relatively happy.
We... (3 Replies)
Discussion started by: bsaadmin
3 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. Solaris
Dear Solaris Experts,
We are upgrading from sun4u to T4 systems and one proposal is to use LDOMs and also zones within LDOMs.
Someone advised using only zones and not LDOMs because the new machines have fewer chips and if a chip or a core fails then it doesn't impact the zones, but impacts... (3 Replies)
Discussion started by: User121
3 Replies
7. 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
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
LEARN ABOUT HPUX
vximportdg
vximportdg(1M) vximportdg(1M)
NAME
vximportdg - import a disk group into the Veritas Volume Manager configuration
SYNOPSIS
vximportdg daname new_dgname
DESCRIPTION
The vximportdg utility performs a temporary import of the disk group contained on the disk device specified by daname to the disk group
specified by new_dgname. As the persistent disk group information is not changed within the private partition of the affected disk, the
import is only valid for the duration of the bootload or until a vxdg deport is performed.
ARGUMENTS
daname Specifies the device name (disk access name) of one of the member disks of the disk group to be imported. The other members are
imported automatically.
new_dgname
Specifies the disk group to be imported.
USAGE
One reason to use the vximportdg utility is to import a second generation of the rootdg disk group so that its objects are available for
use while a system is running on a different rootdg. To prevent volumes on the second generation rootdg from having the same device minor
numbers as volumes (such as rootvol) on the active rootdg, the importation assigns temporary non-conflicting device minor numbers. If this
occurs, vximportdg outputs warning messages detailing the mapping of the minor numbers.
SEE ALSO
vxdg(1M)
VxVM 5.0.31.1 24 Mar 2008 vximportdg(1M)