11-14-2008
I have gone through one of the doc here and able to grasp the above points
Hope we need to shed some more light to get ur things done
Volume groups other than rootvg normally use virtual SAN disks called vpaths.
The system-side SAN attachment is done through 2 Fibre Channel PCI adapters, connected to 2 independent SAN fabrics. The logical disks on the SAN are attached to each fabric via 2 storage paths, totaling to 4 paths from the host to each LUN.
Each path to a LUN is seen by AIX as a fiber channel disk device
The Subsystem Device Driver (SDD) groups all paths to the same LUN into a multipath virtual device (vpath) which is accessible for IO operations [MPIO] as long as at least one of the component paths is available.
Nivas P
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
LEARN ABOUT CENTOS
papi_native_avail
papi_native_avail(1) PAPI papi_native_avail(1)
NAME
papi_native_avail - papi_native_avail utility.
file native_avail.c
NAME
papi_native_avail - provides detailed information for PAPI native events.
Synopsis
Description
papi_native_avail is a PAPI utility program that reports information about the native events available on the current platform. A native
event is an event specific to a specific hardware platform. On many platforms, a specific native event may have a number of optional
settings. In such cases, the native event and the valid settings are presented, rather than every possible combination of those settings.
For each native event, a name, a description, and specific bit patterns are provided.
Options
o --help, -h print this help message
o -d display detailed information about native events
o -e EVENTNAME display detailed information about named native event
o -i EVENTSTR include only event names that contain EVENTSTR
o -x EVENTSTR exclude any event names that contain EVENTSTR
o --noumasks suppress display of Unit Mask information
Processor-specific options
o --darr display events supporting Data Address Range Restriction
o --dear display Data Event Address Register events only
o --iarr display events supporting Instruction Address Range Restriction
o --iear display Instruction Event Address Register events only
o --opcm display events supporting OpCode Matching
o --nogroups suppress display of Event grouping information
Bugs
There are no known bugs in this utility. If you find a bug, it should be reported to the PAPI Mailing List at ptools-perfapi@ptools.org.
Version 5.2.0.0 Tue Jun 17 2014 papi_native_avail(1)