An I2C bus
connected to one of the Storage Bridge Bay (SBB) EEPROMs has failed.
What Caused the Problem?
A failed midplane or midplane element within a drive tray or a controller drive tray has been detected. The Recovery Guru Details area provides specific information you will need as you follow the recovery steps.
Important Notes
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 Inter-IC (I2C) busses. Two of the I2C 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 I2C busses fails, both controllers lock down.
During a lockdown for an I2C 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 I2C bus fails, the Major Event Log records data about the problem, but the controller does not lock down.
Recovery Steps
1 | Select the Monitor > Health > Collect Support Data Manually 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 I2C Bus" problem is being reported. The representative will ask you to send the file that you saved. |
3 | The 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 | NetAppSANtricity.StorageArray | ||
| Parent Monitor | NetAppSANtricity.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppSANtricity.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home<UnitMonitor ID="NetAppSANtricity.FailureID_0115_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppSANtricity.StorageArray" ParentMonitorID="NetAppSANtricity.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppSANtricity.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppSANtricity.REC_FAILED_I2C_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="NetAppSANtricity.StateIdC4E6E82011EDB583244CD9BE09AEE178" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppSANtricity.StateIdA7BEDD2AED2FF51F121727821BED4EA4" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>115</FailureID>
<IntervalSeconds>361</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>