—dar0—

User array name = ‘CUSTOMERSOFT’ dac0 ACTIVE dac5 ACTIVE

Disk DAC LUN Logical Drive utm 127 hdisk7 dac5 6 beastie1_oracle hdisk14 dac5 13 beastie2_datavg hdisk15 dac0 14 beastie3_datavg hdisk2 dac0 1 beastie3_rootvg hdisk3 dac0 2 beastie4_rootvg hdisk4 dac5 3 beastie5_rootvg hdisk5 dac5 4 beastie2_rootvg hdisk6 dac0 5 bakup hdisk8 dac0 7 customer1 hdisk9 dac0 8 customer3 hdisk10 dac5 9 customer6 hdisk11 dac0 10 customer14 hdisk12 dac5 11 beastie2_db2 hdisk13 dac0 12 beastie3_scheduler hdisk16 dac0 15 customer9 hdisk17 dac0 16 customer8

It is necessary to perform a bosboot before rebooting the system in order to incorporate this change into the boot image.

In order to change to the new driver, either a reboot or a full unconfigure and reconfigure of all devices of the type changed must be performed.

shutdown –Fr

[…]

Here is a simple procedure switching from a RDAC/fcparray management mode to a MPIO multipath mode for SAN disks presented from an IBM DSXX00 array.

Verification of the current monopath configuration:

# manage_disk_drivers
1: DS4100: currently RDAC; supported: RDAC/fcparray, MPIO
2: DS4300: currently RDAC; supported: RDAC/fcparray, MPIO
3: DS4500: currently RDAC; supported: RDAC/fcparray, MPIO
4: DS4700/DS4200: currently RDAC; supported: RDAC/fcparray, MPIO
5: DS4800: currently RDAC; supported: RDAC/fcparray, MPIO

Listing of the disks from the array:

# fget_config -vA