Pillar Axiom: How to modify LUN AutoAssign Attribute for APM and Non-APM Hosts
(Doc ID 1604031.1)
Last updated on AUGUST 29, 2019
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
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.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Modifying the LUN attribute for non APM hosts|
|Modifying LUN attribute for APM hosts|