Pillar Axiom 300 Storage System
 
Pillar Axiom 600 Storage System
 
Pillar Axiom 500 Storage System
 

PLA-Support>Sun Systems>DISK>Axiom>SN-DK: Ax600
 
_Old GCS Categories>Sun Microsystems>Storage - Disk>Pillar Axiom
 

Applies to:

Symptoms

An Axiom will generate a Warning Event, and subsequent Callhome with this Subject Line.

Cause

The Axiom has reached the max threshold allowed for the particular StoragePoolType.

Solution

What is the significance of receiving an Axiom Callhome event for "Storage Pool Reached Allocation Limit"  or "Storage Reached Allocation Limit" ?

The Storage "Pool Reached Allocation Limit" event is triggered when a StoragePoolType has exceeded the threshold set for it. The Event will indicate which StoragePoolType is affected, and the user will need to address this issue through either moving, deleting Storageobjects (LUNs, Filesystems) from; or adding more Bricks to that StoragePoolType.

The "Storage Reached Allocation Limit" message will appear when all the storage pools have exceeded there 95% usage watermark giving you a higher level of alert.

The "STORAGE_POOL_NEARING_ALLOCATION_LIMIT" is triggered at 90% utilization.

The example below shows the PriorityBandUsage of an Axiom that ran into this event (and the values are reported in GB). This threshold is triggered once the 95% watermark has been exceeded, and is informational to the customer:

The example below shows usage of available media type in a Axiom Storage System:

The Storage Class feature allows you to specify the preferred storage media to use for a logical volume.
A Storage Class is defined as:  A categorization of physical storage, each category having distinct characteristics with regard to performance characteristics of data access.

Example Storage Classes in a Pillar Axiom system are serial ATA (SATA), Fibre Channel (FC), and solid state drive (SSD). Pillar Axiom systems allow an administrator to explicitly manage volume placement within the overall system storage pool, first by Storage Domain, then by Storage Class, and finally by relative priority level within that Storage Class.

Pillar Axiom systems support the following three Storage Classes:
 SATA
 FC
 SSD SLC (solid state drive, single-level cell)

Note: Which Storage Classes are available on a particular Pillar Axiom system depends on the types of Brick storage enclosures you have installed on the system.
A Storage Class has these attributes:
- A newly created logical volume is associated with a single Storage Class.
- The Pillar Axiom Storage Services Manager graphical user interface (GUI) shows the capacity available within each Storage Class.
- The system will not create a logical volume when the available space for the associated Storage Class is insufficient to accommodate the capacity requested for the volume.

For FC and SATA Storage Classes, the striping of a logical volume is across a number of drives in a collection of RAID groups. The number of drives depends on the Quality of Service (QoS) priority setting for the volume. For the SSD SLC Storage Class, striping for a volume is across all available drives, regardless of the priority setting.

Optimum number of RAID groups for best performance:

Priority level

SATA

standard redundancy

SATA 
double redundancy

FC 
standard redundant

FC 
double redundancy

Note: When the selected Storage Class is SSD, all available SSD drives are striped across, regardless of the priority level chosen.

A RAID group is defined as:
A collection of physical drives within a Brick that stores user data. Fibre Channel (FC) Bricks provide one RAID group, which consists of 11 drives. Serial ATA (SATA) and solid‑state drive (SSD) Bricks provide two RAID groups, each of which consists of 6 drives.

Storage Administrator should always consider given optimum number of RAID groups for best performance while doing migration or adding bricks. For example adding one FC brick to High performance storage pool will result bad performance.

If customer has available space on other storage pools then moving LUNs to other pool will give some extra space to manage storage.

Please check Doc ID 1495080.1 : Pillar Axiom: How to migrate LUNs from one storage domain to another  for more information.

If the LUN should remain in same storage pool with same QoS settings then user should add new bricks to system. Bricks can be added online to live Axiom Storage System.

Please contact customer Account Team to buy and install new brick(s) to Pillar Axiom Storage System.

If customer do not need any of the LUNs anymore then LUN can be deleted to make available it's used space for storage pool.

For more information please check administration guides of related release documentation on  Pillar Axiom 600 Storage System Documentation Library.

References

This solution has no attachment