- Table of Contents
- Related Documents
-
Title | Size | Download |
---|---|---|
04-HH3C-PPP-OVER-SONET-MIB | 98.90 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
Root object
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hh3c(25506).hh3cCommon(2).hh3cPos(19)
Tabular objects
hh3cPosParamTable
About this table
This table configures the POS interface configuration.
Support for operations
Create |
Edit/Modify |
Delete |
Read |
Not supported |
Supported |
Not supported |
Supported |
Columns
The table index is ifIndex.
This table supports standard POS interfaces and POS subinterfaces.
Object (OID) |
Access |
Syntax |
Value range |
Description |
Implementation |
hh3cPosCRC (1.3.6.1.4.1.25506.2.19.1.1.1.1) |
read-write |
INTEGER |
crc32(1) crc16(2) |
CRC length for a POS interface. |
As per the MIB. |
hh3cPosMTU (1.3.6.1.4.1.25506.2.19.1.1.1.2) |
read-write |
Integer32 |
Standard MIB values. |
MTU value for the POS interface. |
Range: 128 to 1650. |
hh3cPosScramble (1.3.6.1.4.1.25506.2.19.1.1.1.3) |
read-write |
TruthValue |
true(1) false(2) |
Payload scrambling for the POS interface. |
As per the MIB. |
hh3cPosClockSource (1.3.6.1.4.1.25506.2.19.1.1.1.4) |
read-write |
INTEGER |
system(1) line(2) |
Clock mode for the POS interface. |
This object is supported only on standard POS interfaces. |
hh3cPosSdhFlagJ0 (1.3.6.1.4.1.25506.2.19.1.1.1.5) |
read-write |
DisplayString |
OCTET STRING (0..15) |
J0 byte for SDH frames. |
This object is supported only on standard POS interfaces. Implementation varies by product. |
hh3cPosSdhFlagJ1 (1.3.6.1.4.1.25506.2.19.1.1.1.6) |
read-write |
DisplayString |
OCTET STRING (0..15) |
J1 byte for SDH frames. |
Implementation varies by product. |
hh3cPosSonetFlagJ0 (1.3.6.1.4.1.25506.2.19.1.1.1.7) |
read-write |
Integer32 |
Integer32 (0..255) |
J0 byte for SONET frames. |
This object is supported only on standard POS interfaces. The default value is 1. |
hh3cPosSonetFlagJ1 (1.3.6.1.4.1.25506.2.19.1.1.1.8) |
read-write |
DisplayString |
OCTET STRING (0..62) |
J1 byte for SONET frames. |
Implementation varies by product. |
hh3cPosFlagC2 (1.3.6.1.4.1.25506.2.19.1.1.1.9) |
read-write |
Integer32 |
Integer32 (0..255) |
C2 byte. |
As per the MIB. |
hh3cPosFrameType (1.3.6.1.4.1.25506.2.19.1.1.1.10) |
read-write |
INTEGER |
sdh(1) sonet(2) |
Framing format for the POS interface. |
This object is supported only on standard POS interfaces. When the value of this object changes, the values of hh3cPosSdhFlagJ0, hh3cPosSonetFlagJ0, hh3cPosSdhFlagJ1, and hh3cPosSonetFlagJ1 are restored to their respective defaults. |
hh3cPosEncapsulation (1.3.6.1.4.1.25506.2.19.1.1.1.12) |
read-write |
INTEGER |
ppp(1) hdlc(2) fr(3) mfr(4) |
Encapsulation type for the POS interface. |
As per the MIB. |
hh3cPoskeepaliveTimeout (1.3.6.1.4.1.25506.2.19.1.1.1.13) |
read-write |
Integer32 |
Integer32 (0..32767) |
Keepalive interval for PPP, HDLC, Frame Relay, and MFR. |
The default value is 10. |
hh3cPosFlagJ0Type (1.3.6.1.4.1.25506.2.19.1.1.1.21) |
read-write |
INTEGER |
sdh(1) sonet(2) |
Framing format for the J0 byte on POS interface. |
This object has been replaced by hh3cPosFrameType. |
hh3cPosFlagJ1Type (1.3.6.1.4.1.25506.2.19.1.1.1.22) |
read-write |
INTEGER |
sdh(1) sonet(2) |
Framing format for the J1 byte on POS interface. |
This object has been replaced by hh3cPosFrameType. |
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.