Pillar Axiom: Both Slammer Control Units Fail at Identical Time for Similar Reason
(Doc ID 1393811.1)
Last updated on JULY 15, 2019
Applies to:Pillar Axiom 600 Storage System - Version Not Applicable to Not Applicable [Release N/A]
Information in this document applies to any platform.
Problem Reported: Slammer CU0 Failed, LUN offline
Both CUs failed and the Axiom performed a self initiated restart. The entire Axiom was unavailable.
2009-03-18 11:21:08 MCC received event 83, SlammerControlUnitFailed, Internal event code:3000e from AGENT on 0x2xxxxxxxxxxxxxx2
2009-03-18 11:21:38 MCC received event 83, SlammerControlUnitFailed, Internal event code:3000e from AGENT on 0x2xxxxxxxxxxxxxxa
2009-03-18 11:22:08 Rebooting active pilot NOW...
2009-03-18 11:24:38 Processing request: ColdStartSoftware
2009-03-18 11:25:25 **** MCC COLD START COMPLETED SUCCESSFULLY
2009-03-18 11:25:31 AdminAction Added: FQN: /LUNOffline/VMFS_0 Type: LUNOffline
2009-03-18 11:52:03 Processing request: PerformClearLostData
PSG_NMQ PANIC_ASSERT: buf pointer is NULL
Both CUs failed almost at almost the same time and for the same reason, a software issue fixed in current releases.
As soon as the second CU failed, the Axiom went into a self initiated full system restart, since both Slammer CUs were offline.
All LUNs would be unavailable from the time the second CU failed until the full system restart completed. This would be roughly 30 minutes from the times in the log entry.
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