Sponsored Content
Full Discussion: DISK and MPIO
Operating Systems AIX DISK and MPIO Post 303033185 by bakunin on Monday 1st of April 2019 07:26:21 AM
Old 04-01-2019
Quote:
Originally Posted by Phat
--> the disks marked with Defined mean that they are not available?
Exactly. AIX stores information about devices generally in the ODM. Since this is updated only by a run of cfgmgr (in fact that is the very purpose of this command) it might be that a device is still defined in the ODM (because once it was available but is not any more now) describes a device that is already removed (or not working for some other reason). These devices will be in state "Defined". Re-plung them in and they become "Available" automatically. Delete them from the ODM (via rmdev and they will be gone forever - only to return after being replugged and cfgmgr is run again.

Quote:
Originally Posted by Phat
We can opt to select the mpio method sddpcm, AIX PCM for whatever disk we want?
You need to use a driver that works (duh! ;-)) ). It does not only depend on a disk if a driver works or not but also on the nature of the connection LUN<->host system, the storage subsystem involved the type of fabric you use and so on.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX MPIO and EMC

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

AIX 5.3 MPIO vs RDAC on DS4000 range

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

AIX native MPIO

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

SDD SDDPCM MPIO lspath Jargon

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

MPIO Driver

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

MPIO reliability

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

MPIO - list of supported arrays

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

Upgrading from native MPIO to SDDPCM AIX 6.1

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

Failed mpio path on AIX5.3

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

Need Help with SDD / SDDPCM / MPIO

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
cfgmgr_set_status(9r)													     cfgmgr_set_status(9r)

NAME
cfgmgr_set_status - General: Reports failure to the cfgmgr framework SYNOPSIS
int cfgmgr_set_status( char *driver_name ); ARGUMENTS
Specifies the name of the device driver for which you want to report an associated failure. This name is a string that matches the string you specified for the entry_name item in the /etc/sysconfigtab database. Typically, third-party driver writers specify the driver name (followed by a colon) in the sysconfigtab file fragment, which gets appended to the /etc/sysconfigtab database during the driver product installation. DESCRIPTION
The cfgmgr_set_status routine reports to the cfgmgr framework that a failure has occurred during static configuration. If the specified device driver is in the static configuration state, it does not know that the configuration operation is complete until all register call- back requests (routines) have successfully completed. Therefore, a device driver calls cfgmgr_set_status to report a possible failure dur- ing static configuration to the cfgmgr framework. Specifically, cfgmgr_set_status performs the following failure operations: Adjusts the state of the specified device driver Unconfigures the specified device driver from the cfgmgr framework The cfgmgr_set_status routine calls the device driver's configure routine at its CFG_OP_UNCONFIGURE entry point as part of these failure operations. The code associated with the CFG_OP_UNCONFIGURE entry point is responsible for determining how to deallocate any allocated resources during these failure operations. The cfgmgr_set_status routine does not notify the operator of a configuration failure. Part of the code associated with the CFG_OP_UNCON- FIGURE entry point could include an error logging operation to record the fact that a failure has occurred. The reason for doing this is that the cfgmgr framework's task is to accomplish the unconfigure operation of a statically configured device driver. You call the cfgmgr_set_status routine in the device driver's callback routine when the static configuration operation fails. You register a callback routine by calling the register_callback routine. RETURN VALUES
Upon successful completion, cfgmgr_set_status returns the value ESUCCESS. This success value indicates that cfgmgr_set_status adjusted the state of the device driver and caused the cfgmgr framework to unconfigure the driver. Otherwise, cfgmgr_set_status returns one of the fol- lowing error constants defined in /usr/sys/include/sys/sysconfig.h and /usr/sys/include/sys/errno.h: The device driver that you specified in the driver_name argument does not exist. In this case, cfgmgr_set_status cannot adjust the state and unconfigure the device driver. The device driver that you specified in the driver_name argument was not statically configured. The device driver that you specified in the driver_name argument is not in the static configuration state. EXAMPLES
See Writing Device Drivers: Tutorial for a code example of the cfgmgr_set_status interface. SEE ALSO
Routines: cfgmgr_get_state(9r), register_callback(9r) cfgmgr_set_status(9r)
All times are GMT -4. The time now is 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy