Overview and Notes:

Please read this entire procedure in advance before attempting so you are familiar with the process and concepts.

This procedure includes both the VMware console CLI and GUI methods of determining ESX Path Policy and settings.

• 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’s IT staff.

Pre-Requisites/Planning for Action:

1.  A host with network access to the Axiom GUI.
2. Console access of all ESX server nodes.

Perform the Action Steps

1. Identify all LUNs associated with ESX server nodes.
1. Log into the Axiom GUI.
2. Click on the “Storage” tab at the top of the window.
3. On the left hand side the Storage widow under SAN, click “Hosts”
4. Click on the first ESX server host from the list presented. The “Modify Host Information” sub window should appear
5. In the sub window, click the “LUN Connections” tab near the bottom
6. Record the names and LUN numbers of all LUNs listed.
7. Click “Cancel”
8. Repeat Step 1 for all remaining ESX server nodes.
2. Identify the owning node for all LUNs associated with ESX nodes.
1. In the Storage screen, on the left-hand side under SAN, click “LUNs”
2. Click on the name of the first LUN recorded in Step 1. The “Modify LUN” sub window should open
3. In the sub window under the “LUN Assignment” section, record the value of “Current Slammer Location:”
4. Click “Cancel”
5. Repeat Step 2 for all remaining LUNs recorded in Step 1.

      3.             Verify pathing configuration for all ESX nodes. NOTE: This process can be accomplished through either CLI or VI Client application CLI Method:

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

                        i.   esxcfg-mpath –l

2. 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 device’s LUN number.

                                        iii.    The output highlighted in BLUE indicates the SCSI device’s pathing policy.

                                        iv.    The output highlighted in VIOLET indicates the SCSI device’s active path.

                                         v.    The output highlighted in GREEN indicates the WWPNs of the SCSI device’s paths.

3. Verify the pathing policy for all LUNs is set to fixed
4. 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.

5. If any changes are needed, note them to bring to the attention of the ESX server administrator after the action plan is complete.
6. Repeat Step 3 for all remaining ESX server nodes.

      “VI” Client Method:

4. Alternatively, either the ESX Server or Virtual Center GUI can be used to verify path status.
1. Select the ESX Server you are modifying in the GUI
2. Select the Configuration Tab
3. Select Storage is the listed fields
4. Select the LUN you are working with
5. Select the hard to see “Properties” link on the far right side of the page
6. 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.

Here is the Manage Paths screenshot.

7. Ensure the Policy is “Fixed”
8. 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.