SDDPCM and AIXPCM switching

If possible, it is a good idea to add the recommended values to the

Predefined attributes in ODM. These values should be applied BEFORE

Rebooting your system into AIXPCM mode.

Examples:

# chdef -a queue_depth=32 -c disk -s fcp -t mpioosdisk

queue_depth changed

# chdef -a reserve_policy=no_reserve -c disk -s fcp -t mpioosdisk

reserve_policy changed

# chdef -a algorithm=shortest_queue -c disk -s fcp -t mpioosdisk

algorithm changed

>> For DS8K:

# chdef -a queue_depth=32 -c disk -s fcp -t aixmpiods8k

queue_depth changed

# chdef -a reserve_policy=no_reserve -c disk -s fcp -t aixmpiods8k

reserve_policy changed

# chdef -a algorithm=shortest_queue -c disk -s fcp -t aixmpiods8k

algorithm changed

The "NO_OVERRIDE" option indicates that the configuration is not overridden

By manage_disk_drivers, and so the device family is configured based on the

available ODM to match that family.

The ODM supplied by SDDPCM takes precedence over the AIX default PCM ODM.
So, a value of "NO_OVERRIDE" indicates that SDDPCM is used to configure devices of

That family if SDDPCM is installed. If SDDPCM is not installed, then the AIX default PCM is used.

By selecting the "AIX_AAPCM" option, the administrator can instruct AIX to use the

AIX default PCM even if SDDPCM is installed. The AIX LPAR must be rebooted in order for the disks to be
reconfigured to use the AIX PCM.

Once AIX is rebooted, SDDPCM is no longer in use for the disk family specified in the
manage_disk_drivers command. If no disks are using SDDPCM, then the SDDPCM and devices.fcp
.disk.ibm.mpio.rte filesets may be uninstalled using SMIT or running the installp -ug command
Example of using the manage_disk_drivers command to switch from SDDPCM to AIXPCM

For a system that is using IBM SVC 2145 or DS8K disks.

a) Confirm the system is using SDDPCM for MPIO.

# manage_disk_drivers -l | grep -i svc

# manage_disk_drivers -l | grep -i 2107ds8k

IBMSVC NO_OVERRIDE NO_OVERRIDE,AIX_AAPCM,non_MPIO

2107DS8K NO_OVERRIDE NO_OVERRIDE,AIX_AAPCM,AIX_non_MPIO

# pcmpath query device

Total Dual Active and Active/Asymmetric Devices : 2

DEV#: 3 DEVICE NAME: hdisk2 TYPE: 2145 ALGORITHM: Load Balance

SERIAL: 60050768017F00362000000000000346 VENDOR: IBM SIZE: 30.00 GB

==========================================================================

Path# Adapter/Path Name State Mode Select Errors

0* fscsi0/path0 OPEN NORMAL 50 0

1 fscsi0/path1 OPEN NORMAL 9343 0

2* fscsi1/path2 OPEN NORMAL 51 0

3 fscsi1/path3 OPEN NORMAL 9236 0

DEV#: 4 DEVICE NAME: hdisk3 TYPE: 2145 ALGORITHM: Load Balance

SERIAL: 60050768017F00362000000000000347 VENDOR: IBM SIZE: 2.00 TB

==========================================================================

Path# Adapter/Path Name State Mode Select Errors

0 fscsi0/path0 OPEN NORMAL 117 0

1* fscsi0/path1 OPEN NORMAL 36 0

2 fscsi1/path2 OPEN NORMAL 121 0

3* fscsi1/path3 OPEN NORMAL 36 0

>> The AIX PCM lsmpio command does not return anything, as SDDPCM is in control at this time.

# lsmpio -are => Blank output

# lsdev -Cc disk

hdisk2 Available 42-T1-01 MPIO FC 2145

hdisk3 Available 42-T1-01 MPIO FC 2145

# lspath

Enabled hdisk2 fscsi0

Enabled hdisk3 fscsi0

Enabled hdisk2 fscsi0

Enabled hdisk3 fscsi0

Enabled hdisk2 fscsi1

Enabled hdisk3 fscsi1

Enabled hdisk2 fscsi1

Enabled hdisk3 fscsi1

b) Run the manage_disk_drivers command to switch to AIX PCM and reboot the system.

# manage_disk_drivers -d IBMSVC -o AIX_AAPCM

Or

# manage_disk_drivers -d 2107DS8K -o AIX_AAPCM

******* ATTENTION *******

For the change to take effect the system must be rebooted

# shutdown -Fr

After the reboot, AIX PCM is now in control of MPIO on this system.

# manage_disk_drivers -l | grep -i svc

IBMSVC AIX_AAPCM NO_OVERRIDE,AIX_AAPCM,AIX_non_MPIO

Now confirm AIX_PCM is in control i.e. output from lsmpio.

# lsmpio

name path_id status path_status parent connection

hdisk2 0 Enabled Non fscsi0 50050768011006c4,0

hdisk2 1 Enabled Opt fscsi0 500507680110062b,0

hdisk2 2 Enabled Non fscsi1 50050768011006c4,0

hdisk2 3 Enabled Sel,Opt fscsi1 500507680110062b,0

hdisk3 0 Enabled Opt fscsi0 50050768011006c4,1000000000000

hdisk3 1 Enabled Non fscsi0 500507680110062b,1000000000000

hdisk3 2 Enabled Sel,Opt fscsi1 50050768011006c4,1000000000000

hdisk3 3 Enabled Non fscsi1 500507680110062b,1000000000000

# lsmpio -are

Adapter Driver: fscsi0 -> AIX PCM

Adapter WWPN: c0507607e05e0078

Link State: Up

Connection Errors

Last 10 Minutes: 0

Last 60 Minutes: 0

Last 24 Hours: 0

Total Errors: 0

Connection Errors

Last 10 Last 60 Last 24

Minutes Minutes Hours

50050768011006c4 0 0 0

500507680110062b 0 0 0

Adapter Driver: fscsi1 -> AIX PCM

Adapter WWPN: c0507607e05e007a

 Link State: Up

Connection Errors

Last 10 Minutes: 0

Last 60 Minutes: 0

Last 24 Hours: 0

Total Errors: 0

Connection Errors

Last 10 Last 60 Last 24

Minutes Minutes Hours

50050768011006c4 0 0 0

500507680110062b 0 0 0

# pcmpath query device

No device file found

>> Now you can easily remove the sddpcm installed along with devices.fcp.disk.ibm.mpio.rte fileset:

# smitty deinstall

Remove Installed Software

Type or select values in entry fields.

Press Enter AFTER making all desired changes.

[Entry Fields]

* SOFTWARE name [devices.fcp.disk.ibm.mpio.rte devices.sddpcm.72.rte]

PREVIEW only? (remove operation will NOT occur) yes +

REMOVE dependent software? yes +

EXTEND file systems if space needed? no +

DETAILED output? +

FILESET STATISTICS

------------------

2 Selected to be deinstalled, of which:

 2 Passed pre-deinstall verification

2 Total to be deinstalled

ADDITIONAL INFORMATION

----------------------

One or more of the selected filesets will cause a bosboot to be performed.

The bosboot command will rebuild the boot image. As a result it may

be necessary to reboot your system for the changes to take effect.

It is recommended that you run the bosboot command to ensure success

before rebooting It is recommended that you reboot the system as soon

as possible after completing this task to avoid any disruption to the environment.

Name Level Part Event Result

-------------------------------------------------------------------------------

devices.sddpcm.72.rte 2.7.1.0 ROOT DEINSTALL SUCCESS

devices.sddpcm.72.rte 2.7.1.0 USR DEINSTALL SUCCESS

devices.fcp.disk.ibm.mpio.r 1.0.0.25 USR DEINSTALL SUCCESS

# lslpp -l | grep sddpcm

# pcmpath query device

ksh: pcmpath: not found

Example of using the manage_disk_drivers command to switch from AIXPCM to SDDPCM

To roll back to SDDPCM simply run the manage_disk_drivers command again and select NO_OVERRIDE.

Of course, this implies you have not de-installed the SDDPCM device drivers

[You have it installed or you just installed it].

# manage_disk_drivers -d IBMSVC -o NO_OVERRIDE

Or

# manage_disk_drivers -d 2107DS8K -o NO_OVERRIDE

******* ATTENTION *******

For the change to take effect the system must be rebooted

# shutdown -Fr

After reboot, SDDPCM should be in control of MPIO again.

# manage_disk_drivers -l | grep -i svc

# manage_disk_drivers -l | grep -i 2107DS8K

IBMSVC NO_OVERRIDE NO_OVERRICE,AIX_AAPCM,AIX_non_MPIO

2107DS8K NO_OVERRIDE NO_OVERRICE,AIX_AAPCM,AIX_non_MPIO

# pcmpath query device

Total Dual Active and Active/Asymmetric Devices : 2

DEV#: 3 DEVICE NAME: hdisk2 TYPE: 2145 ALGORITHM: Load Balance

SERIAL: 60050768017F00362000000000000346 VENDOR: IBM SIZE: 30.00 GB

==========================================================================

Path# Adapter/Path Name State Mode Select Errors

0* fscsi0/path0 OPEN NORMAL 50 0

1 fscsi0/path1 OPEN NORMAL 9637 0

 2* fscsi1/path2 OPEN NORMAL 51 0

3 fscsi1/path3 OPEN NORMAL 9674 0

DEV#: 4 DEVICE NAME: hdisk3 TYPE: 2145 ALGORITHM: Load Balance

SERIAL: 60050768017F00362000000000000347 VENDOR: IBM SIZE: 2.00 TB

==========================================================================

Path# Adapter/Path Name State Mode Select Errors

0 fscsi0/path0 OPEN NORMAL 144 0

1* fscsi0/path1 OPEN NORMAL 36 0

2 fscsi1/path2 OPEN NORMAL 109 0

3* fscsi1/path3 OPEN NORMAL 36 0

AIX PCM lsmpio does not return any information when SDDPCM is in control.

# lsmpio => Blank output

Ahmed (Mash) Mashhour

[email protected]
[email protected]