Asset ID: |
1-72-1428443.1 |
Update Date: | 2012-08-26 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1428443.1
:
Pillar Axiom: Storage Pool Reached Allocation Limit
Related Items |
- Pillar Axiom 500 Storage System
|
Related Categories |
- PLA-Support>Sun Systems>DISK>Pillar Axiom>SN-DK: Ax600
- .Old GCS Categories>Sun Microsystems>Storage - Disk>Pillar Axiom
|
In this Document
Created from <SR 3-5402503021>
Applies to:
Pillar Axiom 500 Storage System - Version Not Applicable and later
Information in this document applies to any platform.
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
--- Goal ---
What is the significance of receiving an Axiom Callhome event for "Storage Pool Reached Allocation Limit" ?
This 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 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:
RelativePriority TotalSystemCapacity UsedSystemCapacity FreeSystemCapacity
Premium 0 0 0
High 4466 4466 0
Medium 8932 8932 0
Low 4466 4466 0
Archive 4466 4337 129
Attachments
This solution has no attachment