| slotID |
.1.3.6.1.4.1.9.10.26.1.2.1.1.1 |
|
Slot Identifier for the selected slot.
|
| slotType |
.1.3.6.1.4.1.9.10.26.1.2.1.1.2 |
|
The current type of card in the physical cage, as reported by
the system.
|
| slotStatus |
.1.3.6.1.4.1.9.10.26.1.2.1.1.3 |
|
The current status of the slot.
|
| slotSwVersion |
.1.3.6.1.4.1.9.10.26.1.2.1.1.4 |
|
The currently active firmware version number as a positive
whole number, e.g. 100.
|
| slotAlarmLevelChngCounter |
.1.3.6.1.4.1.9.10.26.1.2.1.1.5 |
|
Counter indicating change in the port alarm level. This is
needed as rising or clearing of an port level alarm may not
cause slotAlarmLevel to change. This counter, in such case helps
a manager application to recognize that the alarm levels below
slot level have changed without change in the slotAlarmLevel
(e.g. Say: a line card has two subscriber lines experiencing
Minor alarm condition. The slot alarm level will be minor alarm
in such case. Now if one of the port level minor alarms clear,
the port alarm level would become OK but slot alarm level will
stay as a minor alarm. Alarm level change includes rising or
clearing of a new alarm at slot/port level).
|
| slotCnfType |
.1.3.6.1.4.1.9.10.26.1.2.1.1.6 |
|
Card type, as provisioned by the operator used to compare
against card type reported by the system for monitoring
purposes. If slotType and slotCnfType do not match and
slotCnfType is not set to none, slotStatus is set to mismatch.
This condition only clears when operator corrects the
configuration to make them match.
The valid card type for each slot is as follows:
slot 1: oc3si, oc3mm, stm1si and stm1mm
slot 2: ctl
slot 3 & 4: none
slot 5 - 14: cap8 and dmt8
|
| slotSubscriberChngCounter |
.1.3.6.1.4.1.9.10.26.1.2.1.1.7 |
|
Counter indicating change in the subscriber table. This will
be incremented by the slot whenever any change is made at the
port level. This is used to avoid unneccessary polling at the
subscriber table level.
|
| slotAlarmLevel |
.1.3.6.1.4.1.9.10.26.1.2.1.1.8 |
|
This reflects the alarm level of the slot. It is the
aggregation of the port level alarms. Alarm levels supported at
the slot level are none, minor, major, critical and unknown.
|
| oCIAlarmLevel |
.1.3.6.1.4.1.9.10.26.1.3.1.1.2 |
|
The current alarm level on the optical interface, may be none,
major, critical or unknown. When the port is experiencing
equipment failure or any of the near end alarm condition, the
alarm level is marked critical. When the port is experiencing a
far end alarm condition, the alarm level is marked major. When
the port is in loopback mode, the alarm level is marked as
unknown.
|
| oCIEQF |
.1.3.6.1.4.1.9.10.26.1.3.1.1.3 |
|
Local equipment failure indication. Possible values are none or
critical. When this attribute is critical, all other alarm
conditions are unknown.
|
| oCILOS |
.1.3.6.1.4.1.9.10.26.1.3.1.1.4 |
|
Loss of signal indication. Possible values are none or
critical. When this attribute is critical, oCILOF, oCILOP, oCILAIS,
oCIPAIS, oCISLM, oCILRFI, oCIPRFI and oCILOCD are unknown.
|
| oCILOF |
.1.3.6.1.4.1.9.10.26.1.3.1.1.5 |
|
Loss of frame indication. Possible values are none, critical or
unknown. When this attribute is critical, oCILAIS, oCILOP,
oCIPAIS, oCISLM, oCILRFI, oCIPRFI and oCILOCD are unknown.
|
| oCILAIS |
.1.3.6.1.4.1.9.10.26.1.3.1.1.6 |
|
Line alarm indication signal. Possible values are none,
critical or unknown. When this attribute is critical, oCILOP and
oCISLM are unknown.
|
| oCILOP |
.1.3.6.1.4.1.9.10.26.1.3.1.1.7 |
|
Loss of pointer indication. Possible values are none, critical
or unknown. When this attribute is critical, oCIPAIS, oCISLM and
oCILOCD are unknown.
|
| oCIPAIS |
.1.3.6.1.4.1.9.10.26.1.3.1.1.8 |
|
Path alarm indication signal. Possible values are none,
critical or unknown. When this attribute is critical, oCISLM is
unknown.
|
| oCISLM |
.1.3.6.1.4.1.9.10.26.1.3.1.1.9 |
|
Signal label mismatch indication. Possible values are none,
critical or unknown.
|
| oCILRFI |
.1.3.6.1.4.1.9.10.26.1.3.1.1.10 |
|
Line remote failure indication. Possible values are none,
critical or unknown.
|
| oCIPRFI |
.1.3.6.1.4.1.9.10.26.1.3.1.1.11 |
|
Path remote failure indication. Possible values are none,
critical or unknown.
|
| oCILOST |
.1.3.6.1.4.1.9.10.26.1.3.1.1.12 |
|
Loss of synchronization indication. Possible values are none,
major or unknown.
|
| oCILOCD |
.1.3.6.1.4.1.9.10.26.1.3.1.1.13 |
|
Loss of cell delineation. Possible values are none, critical or
unknown.
|
| oCILoopMode |
.1.3.6.1.4.1.9.10.26.1.3.1.1.14 |
|
This parameter puts the optical interface of C6200 system in
facility (far end) loopback mode. It causes the node to loop all
the traffic received on the optical interface back to the
network. It does not generate any traffic or perform any kind of
testing locally. This mode affects services to all the users
connected through the node, so this facility must be used with
care. User must set it back to disable mode once the testing
completes. System will stay in loopback mode, if enabled, until
the user disables the loop mode through NMS Manager or the
system terminates - in which case loop mode is disabled
automatically.
It is only meaningful when the out of band management channel is
used for management. It may not be useful when the in-band
management channel is used for management traffic, as it causes
breakdown in the management communications channel.
The alarm level of the port is set to unknown while loopback
mode is enabled.
|
| oCPTxCellCount |
.1.3.6.1.4.1.9.10.26.1.3.2.1.1 |
|
Count of number of non-idle ATM cells inserted into the
transmit SONET payload since system start time. This is free
running counter and rolls back to zero when the value exceeds
2^32.
|
| oCPRxCellCount |
.1.3.6.1.4.1.9.10.26.1.3.2.1.2 |
|
Count of number of ATM cells received at SONET interface since
system start time. Idle cells and cells with uncorrectable
header errors are not included in the count. This is a free
running counter which rolls back to zero when the value exceeds
2^32.
|
| oCPHecErrCount |
.1.3.6.1.4.1.9.10.26.1.3.2.1.3 |
|
A count of uncorrectable header errors since system start time.
This is a free running counter which rolls back to zero when the
value exceeds 2^32.
|
| lineAlarmLevel |
.1.3.6.1.4.1.9.10.26.1.4.1.1.1 |
|
The current alarm level of the port. Refer to
TEXTUAL-CONVENTION section for details on AlarmLevel. Only
following values for the AlarmLevel are possible for this
attribute:
none - Everything is fine
minor - Local end or remote end is experiencing problems,
e.g.
(1) loss of Cell Delineation is observed on the
downstream direction.
(2) subscriberDwnLineRate and lineDwnLineRate do not
match.
(3) subscriberUpLineRate and lineUpLineRate do not
match.
(4) Both Up/down line rates do not match with the
subscriber requested rates.
(5) loss of signal is observed in the downstream
direction for DMT cards and the object
subscriberDMTLOSConfig is configured to alarm
this condition.
(6) loss of frame is observed in the downstream
direction for DMT cards.
unknown - Remote end is non-reachable. This could be
either due to power down at the CPE or due to break in
the connection between C6200 system and the CPE. This is
exhibited by the lineDMTUpLOS alarm.
|
| lineDwnSNRMargin |
.1.3.6.1.4.1.9.10.26.1.4.1.1.2 |
|
In db, the difference between the current downstream signal
to noise ratio and the SNR required for the selected line
rate. as seen by the cpe. This object must be divided by 10
to obtain the real value for CAP only. Following are the
possible values:
Negative number - bad SNR margin for the desired line rate.
0 - adequate SNR (no margin) for the desired line
rate.
Positive number - Good SNR margin for the desired line rate.
Higher number means better SNR margin and
better line quality.
|
| lineDwnLOCD |
.1.3.6.1.4.1.9.10.26.1.4.1.1.3 |
|
Downstream loss of cell delineation. It indicates that the cpe
received cells on the line do not contain a valid header error
check (HEC).
This object is no longer supported.
|
| lineDwnErrSecs |
.1.3.6.1.4.1.9.10.26.1.4.1.1.4 |
|
Downstream count of errored seconds received by the cpe. An error
second is a second with line quality problems due to a HEC error
in CAP cards or CRC, LOS or SEF events in DMT cards.
|
| lineDwnLineRate |
.1.3.6.1.4.1.9.10.26.1.4.1.1.5 |
|
Current downstream line rate in kbps. It is adapted by the line
card using rate adaptation logic.
|
| lineUpSNRMargin |
.1.3.6.1.4.1.9.10.26.1.4.1.1.6 |
|
In db, the difference between the current upstream signal to
noise ratio and the SNR required for the selected line rate as
seen by the co. This object must be divided by 10 to obtain
the real value for CAP only. Following are the possible values:
Negative number - bad SNR margin for the desired line rate.
0 - adequate SNR (no margin) for the desired line
rate.
Positive number - Good SNR margin for the desired line rate.
Higher number means better SNR margin and
better line quality.
|
| lineUpLOCD |
.1.3.6.1.4.1.9.10.26.1.4.1.1.7 |
|
Upstream loss of cell delineation. It indicates that the co
received cells on the line do not contain a valid header
error check (HEC). This alarm will be marked unknown if
lineDMTDwnLPR, lineDMTUpLOS or lineDMTUpLOF on a DMT card are
minor.
|
| lineUpErrSecs |
.1.3.6.1.4.1.9.10.26.1.4.1.1.8 |
|
Upstream count of errored seconds recieved by the co. An error
second is a second with line quality problems due to a HEC error.
or CRC, LOS or SEF events in DMT cards.
|
| lineUpLineRate |
.1.3.6.1.4.1.9.10.26.1.4.1.1.9 |
|
Current upstream line rate in kbps. This is adapted by the line
card using rate adaptation logic.
|
| lineRateAlarm |
.1.3.6.1.4.1.9.10.26.1.4.1.1.10 |
|
This parameter is the comparison between actual
(lineDwnLineRate/ lineUpLineRate) and the user requested line
rates (subscriberDwnLineRate/subscriberUpLineRate). User
requested rates are part of the subscriber section of the MIB.
Following is the list of possible values:
1 - both the line rates match user requested rates.
2 - Downstream line rate does not match user requested rate.
3 - Upstream line rate does not match user requested rate.
4 - Both rates do not match user requested rates.
|
| lineMode |
.1.3.6.1.4.1.9.10.26.1.4.1.1.11 |
|
This parameter shows current mode of the line. The possible
modes are as shown above. Normally line stays in active mode, if
everything is fine. If the line test fails, it goes into
training mode and tries to acquire next possible lower rate. The
line can also go into the training mode when the line card is
unable to communicate to the remote end. It does not come out of
the training mode until it is able to acquire a user requested
rate or a lower rate, if that is unattainable. This mode is
changed by the system to down, when the subscriber line is
administratively disabled.
|
| lineDMTDwnAttenuation |
.1.3.6.1.4.1.9.10.26.1.4.1.1.12 |
|
Measures downstream attenuation of the line reported by the CPE
for the DMT card only. The units for this value are in decibels
(dB). This object is instantiated for the CAP card.
|
| lineDMTUpAttenuation |
.1.3.6.1.4.1.9.10.26.1.4.1.1.13 |
|
Measures upstream attenuation of the line reported by the CO
for the DMT card only. The units for this value are in decibels
(dB). This object is instantiated for the CAP card.
|
| lineDMTDwnLPR |
.1.3.6.1.4.1.9.10.26.1.4.1.1.14 |
|
Downstream loss of power indicator reported by the CPE for
the DMT card only. Valid values are minor, unknown, or none.
When this alarm is minor, lineUpLOS, lineUpLOF and lineUpLOCD
are unknown. This object is instantiated for the CAP card.
|
| lineDMTUpLOS |
.1.3.6.1.4.1.9.10.26.1.4.1.1.15 |
|
Upstream loss of signal alarm indicator reported by the CO
for the DMT card only. Valid values are minor or none. When
this alarm is minor, lineDMTUpLOF and lineUpLOCD are unknown.
This object is instantiated for the CAP card.
|
| lineDMTUpLOF |
.1.3.6.1.4.1.9.10.26.1.4.1.1.16 |
|
Upstream loss of frame alarm indicator reported by the CO for
the DMT card only. Valid values are minor or none. When this
alarm is minor, lineUpLOCD is unknown. This alarm value is
unknown when lineDMTDwnLPR or lineDMTUpLOS is minor. This
object is instantiated for the CAP card.
|
| lineDMTLoopback |
.1.3.6.1.4.1.9.10.26.1.4.1.1.17 |
|
DMT supported ATM layer loopback. dslline loops all ATM
cells toward the CO modem back to the CPE. Local loops all
ATM cells sent by the ATM trunk card toward the ATM trunk
card. When this object is not set to none, lineMode will be
set to testing. This object is instantiated for the CAP
card.
|
| lineTxCellCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.1 |
|
Total cell count in the downstream direction (ATU-C->ATU-R)
reported by the CPE. The counter value does not include cells
with uncorrectable HEC errors. This is a free running counter
which rolls back to zero when the value exceeds 2^32.
|
| lineRxCellCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.2 |
|
Total cell count in the upstream direction (ATU-R->ATU-C)
reported by the CO. The counter value does not include cells
with uncorrectable HEC errors. This is a free running counter
which rolls back to zero when the value exceeds 2^32.
|
| lineHecErrCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.3 |
|
Total HEC error count in the upstream (ATU-R->ATU-C) direction
reported by the CO. This is a free running counter which rolls
back to zero when the value exceeds 2^32.
|
| lineDMTDwnFECCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.4 |
|
Downstream count of forward error correction (FEC) events
reported by the CPE for the DMT card only.
|
| lineDMTUpFECCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.5 |
|
Upstream count of forward error correction (FEC) events
reported by the CO for the DMT card only. This object is
instantiated for the CAP card.
|
| lineDMTDwnCRCCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.6 |
|
Downstream count of cyclical error correction (CRC) events
reported by the CPE for the DMT card only. This object is
instantiated for the CAP card.
|
| lineDMTUpCRCCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.7 |
|
Upstream count of cyclical error correction (CRC) events
reported by the CO for the DMT card only. This object is
instantiated for the CAP card.
|
| lineDMTDwnLOSCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.8 |
|
Downstream count of loss of signal (LOS) events reported by
the CPE for the DMT card only. This object is instantiated
for the CAP card.
|
| lineDMTUpLOSCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.9 |
|
Upstream count of loss of signal (LOS) events reported by the
CO for the DMT card only. This object is instantiated for the
CAP card.
|
| lineDMTDwnSEFCount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.10 |
|
Downstream count of severly errored frame (SEF) events
reported by the CPE for the DMT card only. This object is
instantiated for the CAP card.
|
| lineDMTUpRDICount |
.1.3.6.1.4.1.9.10.26.1.4.2.1.11 |
|
Upstream count of remote defect indication (RDI) events
reported by the CO for the DMT card only. This object is
instantiated for the CAP card.
|
| lineTestTrigger |
.1.3.6.1.4.1.9.10.26.1.4.3.1.1 |
|
Starts or stops (aborts) a test in progress. The agent will
only start a new test, if no test is active on the targeted
port. The user must set lineTestTimeIntvl to an appropriate
value before starting test by setting this parameter to start.
The System resets the value back to stop when the test
completes. This parameter value affects lineTestStatus as
following:
value current lineTestStatus new lineTestStatus
----- ---------------------- ------------------
start inactive/pass/fail/ active
aborted
stop active aborted
clear pass/fail/aborted inactive
The rest of the combinations will result in error.
Starting of the test may fail due to a line test already in
progress on the selected subscriber line.
Agent updates lineTestStartTime, when it accepts the line test.
Agent updates lineTestCmplTime, when the test completes or when
user aborts the test.
Stopping a test resets lineTestUpBitErrRate and
lineTestDwnBitErrRate.
Clearing a test resets lineTestStartTime, lineTestCmplTime,
lineTestUpBitErrRate, and lineTestDwnBitErrRate to zero.
lineTestTimeIntvl and lineTestBitErrRateLimit get set back to
their defaults. Finally, lineTestStatus is set to inactive.
Line test information only resets when the user sets this
parameter to clear, otherwise parameters from the previous run
of the test are preserved until system is rebooted. All of the
parameters are initialized on reboot.
|
| lineTestType |
.1.3.6.1.4.1.9.10.26.1.4.3.1.2 |
|
The type of the test to be performed. If capHardware test
is selected, time interval is determined by the system. Both
the test types are destructive: affects the service on that
line. The agent will only change lineTestType, if no test is
active on the targeted port.
For DMT cards, the DMTLocalTest is available. It is a
destructive test that affects service on that line.
|
| lineTestTimeIntvl |
.1.3.6.1.4.1.9.10.26.1.4.3.1.3 |
|
Time interval in minutes between 0 - 60 minutes. This
parameter is only meaningful, if test type is the line
quality test. Default value is 30 minutes. The agent will
only change lineTestTimeIntvl, if no test is active on the
targeted port.
|
| lineTestStatus |
.1.3.6.1.4.1.9.10.26.1.4.3.1.4 |
|
System changes values for this variable based on trigger value
as well as based on system reported result. When test completes,
system compares lineTestDwnBitErrRate and lineTestUpBitErrRate
to lineTestBitErrRateLimit in order to determine whether the
line test failed or passed. Agent sets this variable based on
this comparison.
|
| lineTestDwnBitErrRate |
.1.3.6.1.4.1.9.10.26.1.4.3.1.5 |
|
This is positive integer value representing a negative exponent
of 10 for the error rate in the downstream direction. It is only
meaningful when the line quality test is done on the affected
subscriber line. It is compared against lineTestBitErrRateLimit
to determine lineTestStatus value when the line quality test
completes. This value is interpreted as following:
< 10-7 - Bad line quality
10-7 - Acceptable line quality
> 10-7 - Better line quality
|
| lineTestUpBitErrRate |
.1.3.6.1.4.1.9.10.26.1.4.3.1.6 |
|
This is positive integer value representing a negative exponent
of 10 for the error rate in the upstream direction. It is only
meaningful when the line quality test is done on the affected
subscriber line. It is compared against lineTestBitErrRateLimit
to determine lineTestStatus value when the line quality test
completes. This value is interpreted as following:
< 10-7 - Bad line quality
10-7 - Acceptable line quality
> 10-7 - Better line quality
|
| lineTestStartTime |
.1.3.6.1.4.1.9.10.26.1.4.3.1.7 |
|
Time stamp in displayable format. This is the time when the
system starts the requested test.
|
| lineTestCmplTime |
.1.3.6.1.4.1.9.10.26.1.4.3.1.8 |
|
Time stamp in displayable format. This is the time when the
system completes the requested test or when the user aborts the
test.
|
| lineTestBitErrRateLimit |
.1.3.6.1.4.1.9.10.26.1.4.3.1.9 |
|
This is a positive integer representing a negative exponent
of 10. It represents bit error rate limit allowed for the
subscriber line quality test. The system compares the bit
error rates reported at the end of line quality test to this
limit to determine line quality. Allowable error rates are
between 10-3 and 10-10. The agent will only change
lineTestBitErrRateLimit, if no test is active on the targeted
port.
|
| subscriberName |
.1.3.6.1.4.1.9.10.26.1.5.1.1.1 |
|
The subscriber Id, free format string field. First character
can not be a space. Set this field to NULL string to delete a
subscriber entry from the database. The delete operation will
also disable the affected subscriber line. The system resets all
the subscriber information such as subscriberUpLineRate,
subscriberDwnLineRate, and subscriberLineState to default values
on the delete or for non assigned entries.
|
| subscriberUpLineRate |
.1.3.6.1.4.1.9.10.26.1.5.1.1.2 |
|
Desired maximum line rate. Actual rate may be lower following
training sequence to acquire that rate. Refer to system features
document for valid range. When this value is set to -1, system
automatically adapts to maximum available rate. Following are
the possible rates in kbps the CAP card:
1088, 952, 816, 680, 544, 408, 272 and 91.
For the DMT card, the rates range from 64 Kbps to 1024 Kbps in
increments of 32 Kbps.
|
| subscriberDwnLineRate |
.1.3.6.1.4.1.9.10.26.1.5.1.1.3 |
|
Desired maximum line rate. Actual rate may be lower following
training sequence to acquire that rate. Refer to system features
document for valid range. When this value is set to -1, system
automatically adapts to maximum possible rate. Following are the
possible rates in kbps for the CAP card:
7168, 6272, 4480, 2688, 2560, 2240, 1920, 1600, 1280, 960 and
640.
For the DMT card, the rates range from 64 Kbps to 8168 Kbps in
increments of 32 Kbps.
|
| subscriberLineState |
.1.3.6.1.4.1.9.10.26.1.5.1.1.4 |
|
This parameter reflects current state of the subscriber
line. It allows targeted subscriber line to be enabled or
disabled. Disabling the line cuts off services to the affected
subscriber. All the empty lines are disabled by the system. User
deletion, by setting subscriberName to NULL, also results in
disabling of the line.
|
| subscriberDMTLOSConfig |
.1.3.6.1.4.1.9.10.26.1.5.1.1.5 |
|
This value determines whether or not the LOS condition on the
subscriber line generates a minor alarm. By default, this value
is set to disabled which means that an alarm is not generated when
LOS is detected on the subscriber line.
|
