Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1604031.1
Update Date:2018-04-25
Keywords:

Solution Type  Technical Instruction Sure

Solution  1604031.1 :   Pillar Axiom: How to modify LUN AutoAssign Attribute for APM and Non-APM Hosts  


Related Items
  • Pillar Axiom 500 Storage System
  •  
  • Pillar Axiom 600 Storage System
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
  •  




In this Document
Goal
 AutoAssign Overview:
Solution
 Modifying the LUN attribute for non APM hosts
  
 Modifying LUN attribute for APM hosts


Applies to:

Pillar Axiom 600 Storage System - Version All Versions to All Versions [Release All Releases]
Pillar Axiom 500 Storage System - Version All Versions to All Versions [Release All Releases]
Axiom System Operating Software

Goal

AutoAssign Overview:

The auto_assign attribute can be set from the Axiom GUI "automatically assign slammer" option as a LUN is created, but is not available for modification using the GUI for an existing LUN. The AutomaticallyAssignSlammer flag is contained in the callhome header file of a test, periodic, event driven, or manual callhome. It is also visible in the output of the pdscli request GetLUNDetails for each LUN.

On Axiom releases R1 thru R4, the Axiom will rebalance all LUNs on any Cold Start by QoS band across all Slammers and all CUs on the Slammers. It performs this by taking all LUNs that are configured as auto_assign and moving them to Slammers and CUs to balance the total load, which includes both auto_assign and explicitly assigned LUNs. This may cause problems in a fabric that is zoned by Slammer and will definitely cause problems (Non-Optimized Access) for all LUNs where the host does not have Axiom Path Manager installed or is not fully ALUA compliant.

As of R5, the Axiom still offers the ability to let the Axiom assign LUNs automatically, but this is only done as the LUN is created. Once the LUN has been assigned, it will not be moved on a cold start.

Solution


Modifying the LUN attribute for non APM hosts

For non-APM hosts the LUN assignment must be set to Manual (False) for hosts like ESX and IPStor. If the LUN was inadvertently created with the ”automatically assign slammer” option, the LUN AutoAssign attribute will be set as Auto (True) which is incorrect.

As mentioned previously, the LUN Auto Assignment attribute is not available for modification using the GUI, but it can be modified using the cli tool pdscli.exe

Download the pdscli.exe from the Axiom GUI:  go to the Support tab, click on Command Line Interface.

The following pdscli commands can be used to verify and modify the LUN assignments: The example provided here is used for LUNNAME – LUN1

1.    Get a listing of all LUNs

pdscli.exe sub -u administrator -p <password> -H <pilot-ip-address> GetAllLUNs

2.    Get LUN details (to see the auto assignment attribute of a particular LUN):

pdscli.exe sub -u administrator -p <password> -H <pilot-ip-address> GetLUNDetails ID[1]=/LUN1

 

Look for:

SlammerAssignment

SlammerID:                     ID0a350b65-d21d-b211-8b5d-000e0cc0059f

SlammerFQN:                    /Slammer1

SlammerName:                   Slammer1

ControlUnitNumber:             1

AutomaticallyAssignSlammer:    true

 

3.    To keep the LUN1 assignment to Slammer1 CU1 and to disable the auto-assign attribute (i.e. set it from True to False) run the following pdscli.exe command:

pdscli.exe sub -u <username> -p <password> -H <pilot-ip-address> ModifyLUN LUN=/LUN1 Slammer=/Slammer1 ControlUnitNumber=1 AutomaticallyAssignSlammer=0

 

NOTE: (0 sets the auto assignment attribute to false)

 

4.    Get LUN details again (as in step 2) to verify that the auto assignment attribute has changed.

Look for:

SlammerAssignment

SlammerID:                     ID0a350b65-d21d-b211-8b5d-000e0cc0059f

SlammerFQN:                    /Slammer1

SlammerName:                   Slammer1

ControlUnitNumber:             1

AutomaticallyAssignSlammer:    false

NOTE: If any additional non APM host LUNs are found to have the true attribute setting, please use this procedure again to also change those LUNs to false.

 

Modifying LUN attribute for APM hosts

Axiom Path Manager communicates with the Axiom on port 26004 to ensure the communication paths are optimal: i.e. the host will access the LUN using the optimal path by directly communicating with the control unit ports that owns the LUN

If the path chosen by the host was to communicate via the other control unit ports, then a performance hit would be encountered and it would be necessary to manually set the preferred path.

However Axiom Path Manager can switch paths automatically to ensure the optimal communication path is always used. In this case the LUN auto assignment attribute must be set to Automatic (True) to allow Axiom Path Manager to control that function.

For APM hosts the LUN assignment must be set to Auto (True) for all hosts. If the LUN was inadvertently created without the ”automatically assign slammer” option and manually set to use a default control unit, the LUN AutoAssign attribute will be set as Manual (False) which is incorrect.

As mentioned previously, the LUN Auto Assignment attribute is not available for modification using the GUI, but it can be modified using the cli tool pdscli.exe

Download the pdscli.exe from the Axiom GUI:  go to the Support tab, click on Command Line Interface.

The following pdscli commands can be used to verify and modify the LUN assignments: The example provided here is used for LUNNAME – LUN1

1.    Get a listing of all LUNs

pdscli.exe sub -u administrator -p <password> -H <pilot-ip-address> GetAllLUNs

 

2.    Get LUN details (to see the auto assignment attribute of a particular LUN):

pdscli.exe sub -u administrator -p <password> -H <pilot-ip-address> GetLUNDetails ID[1]=/LUN1

 

Look for:

SlammerAssignment

SlammerID:                     ID0a350b65-d21d-b211-8b5d-000e0cc0059f

SlammerFQN:                    /Slammer1

SlammerName:                   Slammer1

ControlUnitNumber:             1

AutomaticallyAssignSlammer:    False

 

3.    To keep the LUN1 assignment to Slammer1 CU1 and to disable the auto-assign attribute (i.e. set it from False to True) run the following pdscli.exe command:

pdscli.exe sub -u <username> -p <password> -H <pilot-ip-address> ModifyLUN LUN=/LUN1 Slammer=/Slammer1 ControlUnitNumber=1 AutomaticallyAssignSlammer=1

 

NOTE: (1 sets the auto assignment attribute to true)

 

4.    Get LUN details again (as in step 2) to verify that the auto assignment attribute has changed.

 

Look for:

SlammerAssignment

SlammerID:                     ID0a350b65-d21d-b211-8b5d-000e0cc0059f

SlammerFQN:                    /Slammer1

SlammerName:                   Slammer1

ControlUnitNumber:             1

AutomaticallyAssignSlammer:    True

NOTE: If any additional APM host LUNs are found to have the false attribute setting, please use this procedure again to also change those LUNs to true.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback