Table of Contents
Advertisement
User Guide
C:\more C:\Users\Administrator\Desktop\mpclaim_output.txt
c. Verify that the output from the mpclaim_output.txt output appears similar to the following
example.
0000000077010524 Active/Optimized 001|005|036|000 0 Adapter: Avago
Adapter, SAS3 3008 Fury -StorPo... (B|D|F:
134|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active)
0000000077000431 Active/Optimized 000|004|049|000 0 Adapter: Avago
Adapter, SAS3 3008 Fury -StorPo... (B|D|F:
132|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active)
MPIO Disk98: 02 Paths, Least Blocks, ALUA Not Supported SN:
5000CCA2532558CC
Supported Load Balance Policies: FOO RR RRWS LQD WP LB Path ID
State SCSI
Address Weight
-----------------------------------------------------------
0000000077010523 Active/Optimized 001|005|035|000 0 Adapter: Avago
Adapter, SAS3 3008 Fury -StorPo... (B|D|F:
134|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active)
0000000077000430 Active/Optimized 000|004|048|000 0 Adapter: Avago
Adapter, SAS3 3008 Fury -StorPo... (B|D|F:
132|000|000) Controller: 46616B65436F6E74726F6C6C6572 (State: Active)
MPIO Disk97: 02 Paths, Least Blocks, ALUA Not Supported SN:
5000CCA253255E9C
Supported Load Balance Policies: FOO RR RRWS LQD WP LB Path ID
State SCSI
Address Weight
-----------------------------------------------------------
...
4.3.8 Non-Automatic Firmware Activation in Windows
Step 1 : Ensure Windows MPIO can see all paths to the drives.
a. Execute the following command:
C:\mpclaim –v C:\Users\Administrator\Desktop\mpclaim_output.txt
b. Verify that there are two paths to each drive by executing the following command:
C:\more C:\Users\Administrator\Desktop\mpclaim_output.txt
Note: It could take the OS several minutes to rebuild all the paths to the
drives depending on the workload on the drives and how busy the host is.
Multipathing may have to be verified several times to ensure that all paths are
in an optimal state following the reset of IOM A.
Note: This should be completed before beginning the firmware upgrade
procedure.
4. Management
4.3 Firmware Upgrade
209
Advertisement
Table of Contents
