ALM-3276800020 Indicates that I2C abnormal 68080
Description
SRM/3/ENTITYINVALID: OID [OID] I2C is abnormal. (EntityPhysicalIndex=[INTEGER1], BaseTrapSeverity=[INTEGER2], BaseTrapProbableCause=[INTEGER3], BaseTrapEventType=[INTEGER4], EntPhysicalContainedIn=[INTEGER5], EntPhysicalName=[OCTET1], RelativeResource=[OCTET2], ReasonDescription=[OCTET3])
The I2C was faulty.
Attribute
Alarm ID |
Alarm Severity |
Alarm Type |
---|---|---|
3276800020 |
Minor |
Equipment alarm |
Parameters
Name |
Meaning |
---|---|
OID |
Indicates the MIB object ID of the alarm. |
EntityPhysicalIndex |
Indicates the index of an entity. |
BaseTrapSeverity |
Indicates the alarm severity. |
BaseTrapProbableCause |
Indicates the possible causes of an alarm. |
BaseTrapEventType |
Indicates the type of an alarm. |
EntPhysicalContainedIn |
Indicates the index of a parent entity. |
EntPhysicalName |
Indicates the name of an entity. |
RelativeResource |
Indicates the entity-related resources. |
ReasonDescription |
Indicates the reason description of an alarm. |
Impact on the System
One or more interfaces do not work normally.
Possible Causes
The I2C has failed.
Procedure
- Switch services from the interfaces affected by the I2C failure to interfaces that can work normally. If you still want to use an affected interface, rectify the I2C fault, and then run the clear configuration interface interface-type interface-num command to clear interface configuration and reconfigure the interface.
- If the fault cannot be rectified and services cannot be switched to normal interfaces, replace the device.
Related Information
None
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot