Pillar Axiom 600 Storage System
 

PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
 

In this Document

Goal

Fix

Applies to:

Goal

This action plan is non-disruptive to data access
This action plan is intended for use by authorized Pillar field technicians.
Do not change any settings on the ESX server without consultation and guidance from the customer IT staff.

Fix

Pre-Requisites/Planning for Action
List:
 A host with network access to the Axiom GUI.
Console access of all ESX server nodes.
Perform the Action Steps
Identify all LUNs associated with ESX server nodes.
Log into the Axiom GUI.
Click on the Storage tab at the top of the window.
On the left hand side the Storage widow under SAN, click Host
Click on the first ESX server host from the list presented. The Modify Host Information sub window should appear
In the sub window, click the LUN Connections Tab  near the bottom
Record the names and LUN numbers of all LUNs listed.
Click Cancel

Repeat Step 1 for all remaining ESX server nodes.
Identify the owning node for all LUNs associated with ESX nodes.
In the Storage screen, on the left-hand side under SAN, click LUNs
Click on the name of the first LUN recorded in Step 1. The Modify LUN sub window should open
In the sub window under the LUN Assignment section, record the value of Current Slammer Location:
Click Cancel

Repeat Step 2 for all remaining LUNs recorded in Step 1.
Verify pathing configuration for all ESX nodes.

NOTE: This process can be accomplished through either CLI or VI Client application

      CLI Method:

On an ESX server node console, execute the following command:

i.      esxcfg-mpath

This command will produce an out similar to the following:

i.      Disk vmhba1:2:6 /dev/sds (191624MB) has 4 paths and policy of Fixed

 FC 28:0.0 500110a00017b4b0<->2100000b08043030 vmhba1:2:6 On active preferred
 FC 28:0.0 500110a00017b4b0<->2400000b08043030 vmhba1:3:6 On
 FC 28:0.1 500110a00017b4b2<->2300000b08043030 vmhba2:2:6 On
 FC 28:0.1 500110a00017b4b2<->2200000b08043030 vmhba2:3:6 On

Disk vmhba1:2:7 /dev/sdt (271424MB) has 4 paths and policy of Fixed
 FC 28:0.0 500110a00017b4b0<->2100000b08043030 vmhba1:2:7 On active preferred
 FC 28:0.0 500110a00017b4b0<->2400000b08043030 vmhba1:3:7 On
 FC 28:0.1 500110a00017b4b2<->2300000b08043030 vmhba2:2:7 On
 FC 28:0.1 500110a00017b4b2<->2200000b08043030 vmhba2:3:7 On

Disk vmhba1:2:8 /dev/sdu (293999MB) has 4 paths and policy of Fixed
 FC 28:0.0 500110a00017b4b0<->2100000b08043030 vmhba1:2:8 On active preferred
 FC 28:0.0 500110a00017b4b0<->2400000b08043030 vmhba1:3:8 On
 FC 28:0.1 500110a00017b4b2<->2300000b08043030 vmhba2:2:8 On
 FC 28:0.1 500110a00017b4b2<->2200000b08043030 vmhba2:3:8 On


ii.      The output highlighted in RED indicates the SCSI devices LUN number.

iii.      The output highlighted in BLUE indicates the SCSI devices pathing policy.

iv.      The output highlighted in VIOLET indicates the SCSI devices active path.

v.      The output highlighted in GREEN indicates the WWPNs of the SCSI devices paths.

Verify the pathing policy for all LUNs is set to fixed
Using information recorded in previous steps, match each LUN number of a SCSI device to its appropriate LUN name on the Axiom and verify that the Active/Preferred path is set to address a WWPN of the correct Slammer Node.

i.      At this time, PLEASE NOTE: All WWPNs beginning with 21 and 23 reside on CU0 of a SAN Slammer and all WWPNs beginning with 22 and 24 reside on CU1 of a SAN Slammer.
If any changes are needed, note them to bring to the attention of the ESX server administrator after the action plan is complete.
Repeat Step 3 for all remaining ESX server nodes.

      VI Client Method:
Alternatively, either the ESX Server or Virtual Center GUI can be used to verify path status.
Select the ESX Server you are modifying in the GUI
Select the Configuration Tab
Select Storage is the listed fields
Select the LUN you are working with
Select the hard to see Properites link on the far right side of the page
Select the Manage Paths button on the lower right of the pop up screen
See screenshot below
NOTE: This is also where the Data Store Name can be changed to match the LUN name.


Ensure the Policy is Fixed
Ensure the first two characters of the SAN Identifier match the owning Slammer node and port desired as verified above.
After all modifications are completed run GetLunPerf to confirm all NonOptimizedAccess issues have been resolved.

This solution has no attachment