TWI bus has failed.
What Caused the Problem?
This problem is caused by a failed midplane or midplane element within a drive tray or a controller drive tray. When you turn on the power to a tray or hot-plug a component, the storage array checks for compatibility among components such as controllers, power supplies, drive trays, and controller-drive trays. To support the check, data is transmitted across three Two Wire Interface (TWI) busses. Two of the TWI busses are used to read data from and write data to two electrically erasable programmable read-only memory (EEPROM) chips on the midplane. If communication on both of these TWI busses fails, both controllers lock down.
Important Notes
During a lockdown for an TWI bus failure, the controllers are in a Suspended state, the Controller and Summary Fault LEDs come on, and the seven-segment display shows the code
Ln
.
If only one TWI bus fails, the Major Event Log records data about the problem, but the controller does not lock down.
Recovery Steps for a Failed TWI Bus
1 | Select the Advanced >> Troubleshooting >> Support Data >> Collect menu option from the Array Management Window, and take the appropriate steps to save the support data to a .zip file. |
2 | Contact your technical support representative, and indicate that a "Failed TWI Bus" problem is being reported. The support representative will ask you to send the file that you saved. |
3 | The technical support representative will help you obtain the appropriate midplane replacement kit or drive cage replacement kit. The procedures for replacing the midplane may differ for different trays. Follow the instructions that come with the replacement kit. |
| Target | IBMStorageSubsystem.StorageSubsystem | ||
| Parent Monitor | IBMStorageSubsystem.StorageSubsystemAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | IBMStorageSubsystem.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="IBMStorageSubsystem.FailureID_0380_Monitor" Accessibility="Internal" Enabled="true" Target="IBMStorageSubsystem.StorageSubsystem" ParentMonitorID="IBMStorageSubsystem.StorageSubsystemAvailability" Remotable="true" Priority="Normal" TypeID="IBMStorageSubsystem.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="IBMStorageSubsystem.REC_FAILED_TWI_BUS_AlertMessageResourceID">
<AlertOnState>Error</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Error</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Property[@Name='FailureDescription']$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="IBMStorageSubsystem.StateIdF0DB363DEC9C511B3531BDB04EE59949" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="IBMStorageSubsystem.StateId3C421DA7E4EA014A4D06B06548754138" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>380</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>