A transceiver module
(GBIC or SFP) has failed.
What Caused the Problem?
A Small Form-factor Pluggable (SFP) transceiver on either the controller tray or the drive tray has failed, is inserted incorrectly, or the protocol type and/or maximum transmission speed do not match what is supported on the controller tray or drive tray. The Recovery Guru Details provides specific information you will need as you follow the recovery steps.
Caution: Electrostatic discharge can damage sensitive components. Always use proper antistatic protection when handling components. Touching components without using a proper ground may damage the equipment.
Important Notes
If there is only one SFP failure, the storage array is still operational.
Even though the storage array is still operational, a level of path redundancy has been lost. An additional SFP failure could result in the failure of the affected trays.
If the Recovery Guru Summary area is reporting any other problems, fix those problems first before attempting to fix this problem.
If the SFP is connected between two drive trays, the Bypass indicator lights on both drive trays are lit.
If the SFP is connected between a controller tray and a drive tray, the Bypass indicator light on the drive tray is lit.
You can replace the SFP while the storage array is in use.
Recovery Steps
1 | Select the Monitor > Reports > Storage Array Profile menu option in the Array Management Window, and then select the Trays tab. | ||||||||||||
2 | Locate and check the status for the affected SFPs associated with the tray, and apply the status to the table below.
| ||||||||||||
3 | Check your documentation to be sure you are using a recommended cabling configuration.
| ||||||||||||
4 |
| ||||||||||||
5 | Replace the failed SFP (identified in the Details area). | ||||||||||||
6 | Click the Recheck button to rerun the Recovery Guru. The failure should no longer appear in the Summary area. If the failure appears again, contact your Technical Support Representative. |
| Target | NetAppESeries.StorageArray | ||
| Parent Monitor | NetAppESeries.StorageArrayAvailability | ||
| Category | Custom | ||
| Enabled | True | ||
| Alert Generate | True | ||
| Alert Severity | Error | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | NetAppESeries.FailureUnitMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Machine generated entity |
Home
<UnitMonitor ID="NetAppESeries.FailureID_0037_Monitor" Accessibility="Internal" Enabled="true" Target="NetAppESeries.StorageArray" ParentMonitorID="NetAppESeries.StorageArrayAvailability" Remotable="true" Priority="Normal" TypeID="NetAppESeries.FailureUnitMonitorType" ConfirmDelivery="true" Comment="Machine generated entity">
<Category>Custom</Category>
<AlertSettings AlertMessage="NetAppESeries.REC_FAILED_TRANSCEIVER_MODULE_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="NetAppESeries.StateId6AE74CA920D6BDE545833735BD82505E" MonitorTypeStateID="NoIssue" HealthState="Success"/>
<OperationalState ID="NetAppESeries.StateIdF04209B4D474DD425D5CA020E492E816" MonitorTypeStateID="IssueFound" HealthState="Error"/>
</OperationalStates>
<Configuration>
<FailureID>37</FailureID>
<IntervalSeconds>59</IntervalSeconds>
<TimeoutSeconds>300</TimeoutSeconds>
<Trace>0</Trace>
</Configuration>
</UnitMonitor>