PAIRGAIN-ETSI-HDSL-MIB
AI MIB Summary
Standard SNMP MIB module defining data structures for PAIRGAIN-ETSI-HDSL-MIB.
160
Objects
Active
Status
2
Dependencies
Imported Objects
Objects
160 total| Object Name |
|---|
IMPORTSThis table provides the 15-minute performance history monitoring
of the last 24 hours for all HDSL spans Errored Seconds (ES),
Severely Errored Seconds (SES) and Unavailable Seconds (UAS). SEQUENCE OF HdslSpan15mPerformanceEntry .1.3.6.1.4.1.927.1.7.1 |
hdslSpan24hPerformanceTableThis table provides 24-hour performance history monitoring of the
last 7 days for all HDSL spans Errored Seconds (ES), Severely Errored
Seconds (SES) and Unavailable Seconds (UAS). SEQUENCE OF HdslSpan24hPerformanceEntry .1.3.6.1.4.1.927.1.7.2 |
hdslSpan24hPerformanceEntryEntries of the HDSL span 24-hour performance table HdslSpan24hPerformanceEntry .1.3.6.1.4.1.927.1.7.2.1 |
hdslSpan24hSlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.1 |
hdslSpan24hSpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.2 |
hdslSpan24hHistoryIdIdentify the history ID within the 7 24-hour performance
history.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.3 |
hdsl24hESLoopANetHDSL 24-hour ES count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.4 |
hdsl24hESLoopBNetHDSL 24-hour ES count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.5 |
hdsl24hUASLoopANetHDSL 24-hour UAS count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.6 |
hdsl24hUASLoopBNetHDSL 24-hour UAS count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.7 |
hdsl24hSESLoopANetHDSL 24-hour SES count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.8 |
hdsl24hSESLoopBNetHDSL 24-hour SES count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.9 |
hdsl24hESLoopACustHDSL 24-hour ES count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.10 |
hdsl24hESLoopBCustHDSL 24-hour ES count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.11 |
hdsl24hUASLoopACustHDSL 24-hour UAS count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.12 |
hdsl24hUASLoopBCustHDSL 24-hour UAS count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.13 |
hdsl24hSESLoopACustHDSL 24-hour SES count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.14 |
hdsl24hSESLoopBCustHDSL 24-hour SES count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.2.1.15 |
hdslSpanCurr24hPerformanceTableThis table provides the current 24-hour performance history
monitoring for all HDSL spans Errored Seconds (ES), Severely
Errored Seconds (SES) and Unavailable Seconds (UAS). SEQUENCE OF HdslSpanCurr24hPerformanceEntry .1.3.6.1.4.1.927.1.7.3 |
hdslSpanCurr24hPerformanceEntryEntries of the HDSL span Current 24-hour PM counts table HdslSpanCurr24hPerformanceEntry .1.3.6.1.4.1.927.1.7.3.1 |
hdslSpanCurr24hSlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.1 |
hdslSpanCurr24hSpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.2 |
hdslCurr24hESLoopANetHDSL Current 24-hour ES count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.3 |
hdslCurr24hESLoopBNetHDSL 24-hour ES count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.4 |
hdslCurr24hUASLoopANetHDSL 24-hour UAS count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.5 |
hdslCurr24hUASLoopBNetHDSL 24-hour UAS count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.6 |
hdslCurr24hSESLoopANetHDSL 24-hour SES count on Loop A's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.7 |
hdslCurr24hSESLoopBNetHDSL 24-hour SES count on Loop B's Network side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.8 |
hdslCurr24hESLoopACustHDSL 24-hour ES count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.9 |
hdslCurr24hESLoopBCustHDSL 24-hour ES count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.10 |
hdslCurr24hUASLoopACustHDSL 24-hour UAS count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.11 |
hdslCurr24hUASLoopBCustHDSL 24-hour UAS count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.12 |
hdslCurr24hSESLoopACustHDSL 24-hour SES count on Loop A's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.13 |
hdslCurr24hSESLoopBCustHDSL 24-hour SES count on Loop B's Customer side of the span.ro INTEGER .1.3.6.1.4.1.927.1.7.3.1.14 |
hdslSpanStatisticsTableThis table lists statistics for margin, pulse attenuation and
state of the loop for all spans of the HDSL loop. SEQUENCE OF HdslSpanStatisticsEntry .1.3.6.1.4.1.927.1.7.4 |
hdslSpanStatisticsEntryEntries of the HDSL span statistics table HdslSpanStatisticsEntry .1.3.6.1.4.1.927.1.7.4.1 |
hdslStatisticsSlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.4.1.1 |
hdslStatisticsSpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.4.1.2 |
hdslLoopPairStateCurrent state on the HDSL loop of span:
0 - loop pair is normal
1 - loop pair is exchanged.ro Byte .1.3.6.1.4.1.927.1.7.4.1.3 |
hdslLoopATipRingReversalCurrent TIP/RING state on the HDSL loop A of span:
0 - TIP/RING on loop A is not reversed.
1 - TIP/RING on loop A is reversed.ro Byte .1.3.6.1.4.1.927.1.7.4.1.4 |
hdslLoopBTipRingReversalCurrent TIP/RING state on the HDSL loop B of span:
0 - TIP/RING on loop B is not reversed.
1 - TIP/RING on loop B is reversed.ro Byte .1.3.6.1.4.1.927.1.7.4.1.5 |
hdslLoopAUpStateCurrent loop state on loop A of the span:
0 - loop is up.
1 - loop is acquiring/converging.
2 - loop is signaling.ro Byte .1.3.6.1.4.1.927.1.7.4.1.6 |
hdslLoopBUpStateCurrent loop state on loop B of the span:
0 - loop is up.
1 - loop is acquiring/converging.
2 - loop is signaling.ro Byte .1.3.6.1.4.1.927.1.7.4.1.7 |
hdslMarginLoopANetCurrent Margin on Loop A's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.8 |
hdslMarginHighLoopANetHighest Margin on Loop A's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.9 |
hdslMarginLowLoopANetLowest Margin on Loop A's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.10 |
hdslMarginLoopBNetCurrent Margin on Loop B's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.11 |
hdslMarginHighLoopBNetHighest Margin on Loop B's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.12 |
hdslMarginLowLoopBNetLowest Margin on Loop B's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.13 |
hdslPulseAttenuationLoopANetPulse Attenuation on Loop A's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.14 |
hdslPulseAttenuationLoopBNetPulse Attenuation on Loop B's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.15 |
hdslMarginLoopACustCurrent Margin on Loop A's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.16 |
hdslMarginHighLoopACustHighest Margin on Loop A's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.17 |
hdslMarginLowLoopACustLowest Margin on Loop A's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.18 |
hdslMarginLoopBCustCurrent Margin on Loop B's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.19 |
hdslMarginHighLoopBCustHighest Margin on Loop B's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.20 |
hdslMarginLowLoopBCustLowest Margin on Loop B's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.21 |
hdslPulseAttenuationLoopACustPulse Attenuation on Loop A's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.22 |
hdslPulseAttenuationLoopBCustPulse Attenuation on Loop B's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.4.1.23 |
hdslSpanAlarmTableThis table provides the HDSL alarms indication on both loops
of the HDSL spans. SEQUENCE OF HdslSpanAlarmEntry .1.3.6.1.4.1.927.1.7.5 |
hdslSpanAlarmEntryEntries of the HDSL span alarm table HdslSpanAlarmEntry .1.3.6.1.4.1.927.1.7.5.1 |
hdslSpanAlarmSlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.5.1.1 |
hdslSpanAlarmSpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.5.1.2 |
hdslMarginAlarmLoopANetMargin Threshold Exceeded on loop A's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.3 |
hdslMarginAlarmLoopBNetMargin Threshold Exceeded on loop B's Network side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.4 |
hdslESAlarmLoopANetErrored Seconds threshold exceeded on loop A's Network side
of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.5 |
hdslESAlarmLoopBNetErrored Seconds threshold exceeded on loop B's Network side
of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.6 |
hdslUASAlarmLoopANetUnavailable Seconds threshold exceeded on loop A's Network
side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.7 |
hdslUASAlarmLoopBNetUnavailable Seconds threshold exceeded on loop B's Network
side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.8 |
hdslMarginAlarmLoopACustMargin Threshold Exceeded on loop A's Customer side of the
span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.9 |
hdslMarginAlarmLoopBCustMargin Threshold Exceeded on loop B's Customer side of the
span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.10 |
hdslESAlarmLoopACustErrored Seconds Exceeded on loop A's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.11 |
hdslESAlarmLoopBCustErrored Seconds Exceeded on loop B's Customer side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.12 |
hdslUASAlarmLoopACustUnavailable Seconds threshold exceeded on loop A's customer
side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.13 |
hdslUASAlarmLoopBCustUnavailable Seconds threshold exceeded on loop B's customer
side of the span.ro Byte .1.3.6.1.4.1.927.1.7.5.1.14 |
hdslLOSWAlarmLoopALoss of Sync Word (LOSW) occurred on loop A's Network side of the HDSL loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.15 |
hdslLOSWAlarmLoopBLoss of Sync Word (LOSW) occurred on loop B's Network side of
the HDSL loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.16 |
hdslPFOAlarmLoopAPower Feed Open (PFO) on loop A's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.17 |
hdslPFOAlarmLoopBPower Feed Open (PFO) on loop B's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.18 |
hdslPFSAlarmLoopAPower Feed Short (PFS) on loop A's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.19 |
hdslPFSAlarmLoopBPower Feed Short (PFS) on loop B's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.20 |
hdslBERAlarmLoopABit Error Rate (BER) on loop A's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.21 |
hdslBERAlarmLoopBBit Error Rate (BER) on loop B's Network side of the HDSL
loop.ro Byte .1.3.6.1.4.1.927.1.7.5.1.22 |
hdslSpanAlarmHistoryTableThis table provides the HDSL alarms history on both loops
of the HDSL spans. SEQUENCE OF HdslSpanAlarmHistoryEntry .1.3.6.1.4.1.927.1.7.6 |
hdslSpanAlarmHistoryEntryEntries of the HDSL span Alarm History table HdslSpanAlarmHistoryEntry .1.3.6.1.4.1.927.1.7.6.1 |
hdslSpanAlarmHistorySlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.1 |
hdslSpanAlarmHistorySpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - Span between LTU and REG is identified as 1.
Span between REG and NTU is identified as 2.
2 REGs - Span between LTU and REG #1 is identified as 1.
Span between REG #1 and REG #2 is identified as 2.
Span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.2 |
hdslMarginAlarmFirstLoopADate and time Margin threshold exceeded alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.3 |
hdslMarginAlarmLastLoopADate and time Margin threshold exceeded alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.4 |
hdslMarginAlarmCountLoopAThe number of times the Margin threshold exceeded alarm has occurred
on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.5 |
hdslMarginAlarmFirstLoopBDate and time Margin threshold exceeded alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.6 |
hdslMarginAlarmLastLoopBDate and time Margin threshold exceeded alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.7 |
hdslMarginAlarmCountLoopBThe number of times the Margin threshold exceeded alarm has occurred
on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.8 |
hdslESAlarmFirstLoopADate and time Errored Seconds threshold exceeded alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.9 |
hdslESAlarmLastLoopADate and time Errored Seconds threshold exceeded alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.10 |
hdslESAlarmCountLoopAThe number of times the Errored Seconds threshold exceeded alarm has
occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.11 |
hdslESAlarmFirstLoopBDate and time Errored Seconds threshold exceeded alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.12 |
hdslESAlarmLastLoopBDate and time Errored Seconds threshold exceeded alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.13 |
hdslESAlarmCountLoopBThe number of times the Errored Seconds threshold exceeded alarm has
occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.14 |
hdslUASAlarmFirstLoopADate and time Unavailable Seconds threshold exceeded alarm
first occurred on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.15 |
hdslUASAlarmLastLoopADate and time Unavailable Seconds threshold exceeded alarm
last occurred on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.16 |
hdslUASAlarmCountLoopAThe number of times the Unavailable Seconds threshold exceeded alarm
has occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.17 |
hdslUASAlarmFirstLoopBDate and time Unavailable Seconds threshold exceeded alarm
first occurred on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.18 |
hdslUASAlarmLastLoopBDate and time Unavailable Seconds threshold exceeded alarm
last occurred on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.19 |
hdslUASAlarmCountLoopBThe number of times the Unavailable Seconds threshold exceeded alarm
has occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.20 |
hdslLOSWAlarmFirstLoopADate and time the Loss of Sync Word alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.21 |
hdslLOSWAlarmLastLoopADate and time the Loss of Sync Word alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.22 |
hdslLOSWAlarmCountLoopAThe number of times the Loss of Sync Word alarm
has occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.23 |
hdslLOSWAlarmFirstLoopBDate and time the Loss of Sync Word alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.24 |
hdslLOSWAlarmLastLoopBDate and time the Loss of Sync Word alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.25 |
hdslLOSWAlarmCountLoopBThe number of times the Loss of Sync Word alarm
has occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.26 |
hdslPFOAlarmFirstLoopADate and time the Power Feed Open alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.27 |
hdslPFOAlarmLastLoopADate and time the Power Feed Open alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.28 |
hdslPFOAlarmCountLoopAThe number of times the Power Feed Open alarm
has occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.29 |
hdslPFOAlarmFirstLoopBDate and time the Power Feed Open alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.30 |
hdslPFOAlarmLastLoopBDate and time the Power Feed Open alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.31 |
hdslPFOAlarmCountLoopBThe number of times the Power Feed Open alarm
has occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.32 |
hdslPFSAlarmFirstLoopADate and time the Power Feed Short alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.33 |
hdslPFSAlarmLastLoopADate and time the Power Feed Short alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.34 |
hdslPFSAlarmCountLoopAThe number of times the Power Feed Short alarm
has occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.35 |
hdslPFSAlarmFirstLoopBDate and time the Power Feed Short alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.36 |
hdslPFSAlarmLastLoopBDate and time the Power Feed Short alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.37 |
hdslPFSAlarmCountLoopBThe number of times the Power Feed Short alarm
has occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.38 |
hdslBERAlarmFirstLoopADate and time the BER threshold exceeded alarm first occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.39 |
hdslBERAlarmLastLoopADate and time the BER threshold exceeded alarm last occurred
on Loop A of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.40 |
hdslBERAlarmCountLoopAThe number of times the BER threshold exceeded alarm
has occurred on Loop A of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.41 |
hdslBERAlarmFirstLoopBDate and time the BER threshold exceeded alarm first occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.42 |
hdslBERAlarmLastLoopBDate and time the BER threshold exceeded alarm last occurred
on Loop B of a spanro PgTimeStamp .1.3.6.1.4.1.927.1.7.6.1.43 |
hdslBERAlarmCountLoopBThe number of times the BER threshold exceeded alarm
has occurred on Loop B of a span.ro INTEGER .1.3.6.1.4.1.927.1.7.6.1.44 |
hdslSpanAlarmSeverityTableThe HDSL span alarm severity table provides severity settings
for HDSL alarms reporting and threshold settings for
Errored Second(ES), Margin(MAR), Unavailable Seconds(UAS) and
Bit Error Rate(BER). SEQUENCE OF HdslSpanAlarmSeverityEntry .1.3.6.1.4.1.927.1.7.7 |
hdslSpanAlarmSeverityEntryEntry in the hdslSpanAlarmSeverityTable HdslSpanAlarmSeverityEntry .1.3.6.1.4.1.927.1.7.7.1 |
hdslSpanAlarmSeveritySlotIdThe slot number of the HDSL loop whose
alarm severity or threshold we are setting.
The slots are numbered 1 through 16 from left to right.ro INTEGER .1.3.6.1.4.1.927.1.7.7.1.1 |
hdslSpanAlarmSeveritySpanIdThe span number of the HDSL loop whose
alarm severity or threshold we are setting.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .1.3.6.1.4.1.927.1.7.7.1.2 |
hdslSpanLOSWAlarmSettingSets the severity for Loss of Sync Word alarm.rw PgAlarmSeverityProtectionSwitchMode .1.3.6.1.4.1.927.1.7.7.1.3 |
hdslSpanPFOAlarmSettingSets the severity for Power Feed Open alarm.rw PgAlarmSeverityMode .1.3.6.1.4.1.927.1.7.7.1.4 |
hdslSpanPFSAlarmSettingSets the severity for Power Feed Short alarm.rw PgAlarmSeverityMode .1.3.6.1.4.1.927.1.7.7.1.5 |
hdslSpanMarginThresholdSets the HDSL Margin threshold value.rw Byte .1.3.6.1.4.1.927.1.7.7.1.6 |
hdslSpanMarginAlarmSettingSets the severity for Margin threshold exceeded alarm.rw PgAlarmSeverityProtectionSwitchMode .1.3.6.1.4.1.927.1.7.7.1.7 |
hdslSpanESThresholdSets the HDSL Errored Seconds threshold value.rw Byte .1.3.6.1.4.1.927.1.7.7.1.8 |
hdslSpanESAlarmSettingSets the severity for Errored Seconds threshold exceeded alarm.rw PgAlarmSeverityProtectionSwitchMode .1.3.6.1.4.1.927.1.7.7.1.9 |
hdslSpanUASThresholdSets the HDSL Unavailable Seconds threshold value.rw Byte .1.3.6.1.4.1.927.1.7.7.1.10 |
hdslSpanUASAlarmSettingSets the severity for UAS threshold exceeded alarm.rw PgAlarmSeverityMode .1.3.6.1.4.1.927.1.7.7.1.11 |
hdslSpanBERThresholdSets the HDSL BER threshold value.rw PgBERThreshold .1.3.6.1.4.1.927.1.7.7.1.12 |
hdslSpanBERAlarmSettingSets the severity for HDSL BER threshold exceeded alarm.rw PgAlarmSeverityMode .1.3.6.1.4.1.927.1.7.7.1.13 |
hdslSpan15mPerformanceEntryEntries of the HDSL span 15-min performance table HdslSpan15mPerformanceEntry .hdslSpan15mPerformanceTable.1 |
hdslSpan15mSlotIdIdentifies the HDSL line occupied in the chassis.
The slots are numbered 1 through 16 from left to right.ro INTEGER .hdslSpan15mPerformanceTable.1.1 |
hdslSpan15mSpanIdIdentifies the span of the HDSL line we are monitoring.
Depending on the number of regenerator(s) (REGs)
present in an HDSL loop, a span will be numbered as follows:
0 REG - only 1 span.
1 REG - span between LTU and REG is identified as 1.
span between REG and NTU is identified as 2.
2 REGs - span between LTU and REG #1 is identified as 1.
span between REG #1 and REG #2 is identified as 2.
span between REG #2 and NTU is identified as 3.ro INTEGER .hdslSpan15mPerformanceTable.1.2 |
hdslSpan15mHistoryIdIdentify the history ID within the 96 15-minute performance
history.ro INTEGER .hdslSpan15mPerformanceTable.1.3 |
hdsl15mESLoopANetHDSL 15-min ES count on Loop A's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.4 |
hdsl15mESLoopBNetHDSL 15-min ES count on Loop B's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.5 |
hdsl15mUASLoopANetHDSL 15-min UAS count on Loop A's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.6 |
hdsl15mUASLoopBNetHDSL 15-min UAS count on Loop B's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.7 |
hdsl15mSESLoopANetHDSL 15-min SES count on Loop A's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.8 |
hdsl15mSESLoopBNetHDSL 15-min SES count on Loop B's Network side of the span.ro Short .hdslSpan15mPerformanceTable.1.9 |
hdsl15mESLoopACustHDSL 15-min ES count on Loop A's Customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.10 |
hdsl15mESLoopBCustHDSL 15-min ES count on Loop B's Customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.11 |
hdsl15mUASLoopACustHDSL 15-min UAS count on Loop A's Customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.12 |
hdsl15mUASLoopBCustHDSL 15-min UAS count on Loop B's Customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.13 |
hdsl15mSESLoopACustHDSL 15-min SES count on Loop A's customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.14 |
hdsl15mSESLoopBCustHDSL 15-min SES count on Loop B's customer side of the span.ro Short .hdslSpan15mPerformanceTable.1.15 |
More MIBs from Pairgain
Browse all PairgainMIBs →PAIRGAIN-SDSL-MIB
The PAIRGAIN-SDSL-MIB enables monitoring and management of PairGain SDSL (Symmetric Digital Subscriber Line) access equipment, specifically tracking physical layer parameters such as line status, attenuation, noise margins, and data transmission rates. It provides standardized access to interface statistics, error counters, and configuration states required for maintaining SDSL circuit integrity and performance.
111 objects→
PG-BRIDGE-MIB
SNMP MIB module
88 objects→
PAIRGAIN-SDSLCELL-MIB
PAIRGAIN-SDSLCELL-MIB provides management access to PairGain SDSL (Single Digital Subscriber Line) hardware for monitoring cell-based transmission parameters, including physical layer status, error counters, and active session statistics. This module enables the tracking of line performance metrics such as CRC errors, cell loss, and synchronization states specific to the SDSL cell architecture.
81 objects→
PAIRGAIN-COMMON-HD-MIB
Standard SNMP MIB module defining data structures for PAIRGAIN-COMMON-HD-MIB.
63 objects→
PAIRGAIN-ETHERPHONE-MIB
Standard SNMP MIB module defining data structures for PAIRGAIN-ETHERPHONE-MIB.
60 objects→
PAIRGAIN-DSLAM-ALARM-SEVERITY-MIB
The PAIRGAIN-DSLAM-ALARM-SEVERITY-MIB configures and monitors alarm severity levels for PairGain DSLAM chassis components, including power supplies, fans, and HDSL/ADSL port states such as Loss of Frame (LOF), Loss of Signal (LOS), and Unavailable Seconds (UAS). It provides granular visibility into hardware and line-level fault conditions across ATUC/ATUR interfaces and specific card channels to facilitate rapid network fault isolation.
47 objects→