- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
02-HH3C-PPP-OVER-SONET-MIB | 79.04 KB |
Contents
HH3C-PPP-OVER-SONET-MIB
About this MIB
Use this MIB to configure the POS-related configuration.
MIB file name
hh3c-ppp-over-sonet.mib
Notifications
hh3cPosB1TCAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.19.2.0.15 |
The B1 bit error rate exceeds the threshold. |
Error |
Minor |
1.3.6.1.4.1.25506.2.19.2.0.14 (hh3cPosNormalAlarm) |
ON |
Notification triggers
The B1 bit error rate exceeds the threshold.
Possible reasons are:
· The attenuation of the Rx signals is high.
· The transmitter of the remote end fails.
· The optical fiber is unclean or the connector is incorrect, or the fiber ages.
· The receiver of the local end fails.
System impact
Transmission over the link fails. Normal service traffic transmission will be impacted.
Status control
ON
· CLI: Use the threshold b1-tca command.
· MIB: Set hh3cPosB1TCAEnable to enable(1).
OFF
· CLI: Use the undo threshold b1-tca command.
· MIB: Set hh3cPosB1TCAEnable to disable(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Interface index |
ifIndex |
InterfaceIndex |
Integer32 (1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Interface description |
ifIndex |
DisplayString |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1. Verify that the optical fiber is firmly installed. Identify whether the alarm is cleared.
2. Verify that the physical link is normal.
3. Execute the display interface command to identify whether the Rx power of the transceiver module of the interface that fails is within the normal range.
4. Identify whether the negotiation mode, clock mode, and scrambling mode (link protocol, clock, and scramble) are the same on both ends. If they are different, adjust the negotiation mode configuration on both ends to make them consistent. Identify whether the alarm is cleared.
5. If the issue persists, contact H3C Support.
hh3cPosB2TCAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.19.2.0.16 |
The B2 bit error rate exceeds the threshold. |
Error |
Minor |
1.3.6.1.4.1.25506.2.19.2.0.14 (hh3cPosNormalAlarm) |
ON |
Notification triggers
The B2 bit error rate exceeds the threshold.
Possible reasons are:
· The attenuation of the Rx signals is high.
· The transmitter of the remote end fails.
· The optical fiber is unclean or the connector is incorrect, or the fiber ages.
· The receiver of the local end fails.
System impact
Transmission over the link fails. Normal service traffic transmission will be impacted.
Status control
ON
· CLI: Use the threshold b2-tca command.
· MIB: Set hh3cPosB2TCAEnable to enable(1).
OFF
· CLI: Use the undo threshold b2-tca command.
· MIB: Set hh3cPosB2TCAEnable to disable(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Interface index |
ifIndex |
InterfaceIndex |
Integer32 (1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Interface description |
ifIndex |
DisplayString |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1. Verify that the optical fiber is firmly installed. Identify whether the alarm is cleared.
2. Verify that the physical link is normal.
3. Execute the display interface command to identify whether the Rx power of the transceiver module of the interface that fails is within the normal range.
4. Identify whether the negotiation mode, clock mode, and scrambling mode (link protocol, clock, and scramble) are the same on both ends. If they are different, adjust the negotiation mode configuration on both ends to make them consistent. Identify whether the alarm is cleared.
5. If the issue persists, contact H3C Support.
hh3cPosB3TCAlarm
Basic information
OID |
Event |
Type |
Severity |
Recovery notification |
Default status |
1.3.6.1.4.1.25506.2.19.2.0.17 |
The B3 bit error rate exceeds the threshold. |
Error |
Minor |
1.3.6.1.4.1.25506.2.19.2.0.14 (hh3cPosNormalAlarm) |
ON |
Notification triggers
The B3 bit error rate exceeds the threshold.
Possible reasons are:
· The attenuation of the Rx signals is high.
· The transmitter of the remote end fails.
· The optical fiber is unclean or the connector is incorrect, or the fiber ages.
· The receiver of the local end fails.
System impact
Transmission over the link fails. Normal service traffic transmission will be impacted.
Status control
ON
· CLI: Use the threshold b3-tca command.
· MIB: Set hh3cPosB3TCAEnable to enable(1).
OFF
· CLI: Use the undo threshold b3-tca command.
· MIB: Set hh3cPosB3TCAEnable to disable(2).
Objects
OID (object name) |
Description |
Index nodes |
Type |
Value range |
1.3.6.1.2.1.2.2.1.1 (ifIndex) |
Interface index |
ifIndex |
InterfaceIndex |
Integer32 (1..2147483647) |
1.3.6.1.2.1.2.2.1.2 (ifDescr) |
Interface description |
ifIndex |
DisplayString |
OCTET STRING (0..255) |
Recommended action
To resolve this issue:
1. Verify that the optical fiber is firmly installed. Identify whether the alarm is cleared.
2. Verify that the physical link is normal.
3. Execute the display interface command to identify whether the Rx power of the transceiver module of the interface that fails is within the normal range.
4. Identify whether the negotiation mode, clock mode, and scrambling mode (link protocol, clock, and scramble) are the same on both ends. If they are different, adjust the negotiation mode configuration on both ends to make them consistent. Identify whether the alarm is cleared.
5. If the issue persists, contact H3C Support.