LS100-MIB Table View

Table-centric layout grouping table, row, and column objects.

Tables
4
Rows
4
Columns
47

nodeIfConfTable

table mandatory
.1.3.6.1.4.1.119.2.3.14.3.1.2 · 1 row entry · 4 columns
Uses the nec variant from /opt/observium/mibs/nec.
Command help
Walk nodeIfConfTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LS100-MIB' -M '/opt/observium/mibs/nec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LS100-MIB::nodeIfConfTable'
The configuration of the line cards.
nodeIfConfEntry row .1.3.6.1.4.1.119.2.3.14.3.1.2.1
The configuration of a line card.
Indexes
Column Syntax OID
The index of the table. Same as ifIndex.
Integer32
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.1.2.1.1
The PMD/physical layer format of the line card.
Enumeration
Enumerated Values:
1other
2sar
3taxi100M
4oc3cSMF
5oc3cMMF
6ds3PlcpScramble
7ds3PlcpNoScramble
8relay6Mcell
9ds3Scramble
10ds3NoScramble
11e3PlcpScramble
12e3PlcpNoScramble
13e3Scramble
14e3NoScramble
15utp5
16leasedLine3M
17leasedLine4M
18leasedLine6M
19utp5classB
20oc3cSmfShaper
21taxi140M
99notInstalled
.1.3.6.1.4.1.119.2.3.14.3.1.2.1.2
nodeIfConfRevmandatory
The revision of the line cards.
DisplayString
Type Constraints:
range: 0..255
.1.3.6.1.4.1.119.2.3.14.3.1.2.1.3
Operational status of the line card.
Enumeration
Enumerated Values:
1other
2inService
3outOfService
4testing
5localLoopBack
6remoteLoopBack
99notInstalled
.1.3.6.1.4.1.119.2.3.14.3.1.2.1.4

linfStatusTable

table mandatory
.1.3.6.1.4.1.119.2.3.14.3.2.1 · 1 row entry · 5 columns
Uses the nec variant from /opt/observium/mibs/nec.
Command help
Walk linfStatusTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LS100-MIB' -M '/opt/observium/mibs/nec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LS100-MIB::linfStatusTable'
Status of the line cards including ATM specific information.
linfStatusEntry row .1.3.6.1.4.1.119.2.3.14.3.2.1.1
Status of a line card including ATM specific information.
Indexes
Column Syntax OID
linfIndexmandatory
Same as ifIndex
Integer32
Constraints:
range: 1-64
.1.3.6.1.4.1.119.2.3.14.3.2.1.1.1
linfStatusmandatory
Status of line interface
Enumeration
Enumerated Values:
1normal
2los
3lof
4loc
5ais
6yellowLine
7yellowPath
8lop
9idle
10yellowAlarm
11plcpLOF
12plcpYellow
13maFERF
14rai
15payloadAllOnes
99notInstalled
.1.3.6.1.4.1.119.2.3.14.3.2.1.1.2
linfConfmandatory
Line card type.
Enumerationr/w
Enumerated Values:
1publicUNI
2privateUNI
3privateNNI
99others
.1.3.6.1.4.1.119.2.3.14.3.2.1.1.3
The amount of bandwidth (Mbps) available/unallocated in
the forward (incoming) direction.
Integer32
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.2.1.1.4
The amount of bandwidth (Mbps) available/unallocated in
the backward (outgoing) direction.
Integer32
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.2.1.1.5

connPvcTable

table mandatory
.1.3.6.1.4.1.119.2.3.14.3.3.3 · 1 row entry · 24 columns
Uses the nec variant from /opt/observium/mibs/nec.
Command help
Walk connPvcTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LS100-MIB' -M '/opt/observium/mibs/nec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LS100-MIB::connPvcTable'
The table containing information on current PVC/SVCs.
Currently, only PVCs are represented in this table.
The table is also used to establish and delete PVCs.
          
1. PVC establishment procedure
          
(1) Read connPvcIndexNext. This value is used as the
value of connPvcIndex for the new connection.
          
(2) Determine the value of connPvcHighIfIndex.  When
creating a new point-to-multipoint connection,
connPvcHighIfIndex must identify the first leaf.
When creating a new point-to-point connection,
connPvcHighIfIndex normally identifies the interface
with the higher value of ifIndex.
          
(3) Set connPvcRowStatus to 'createAndWait' using the
values of connPvcIndex and connPvcHighIfIndex as indexes.
This causes the switch to create the new row with some
objects being set to default values.  The parameters for
which there is no reasonable default are set to 0xffffffff.
          
    Object                Default
    connPvcTopology       bidirectionalVCC(2)
    connPvcTrafficType    trafficUBR(4)
    connPvcLowIfIndex     0xffffffff
    connPvcLowVPI         0xffffffff
    connPvcLowVCI         0xffffffff
    connPvcLowUpcParam    512
    connPvcLowUpc         pass(1)
    connPvcLowThroughput  0
    connPvcHighVPI        0xffffffff
    connPvcHighVCI        0xffffffff
    connPvcHighUpcParam   512
    connPvcHighUpc        pass(1)
    connPvcHighThroughput 0
          
The switch then sets the value of connPvcRowStatus to
'notReady'.  The default values can be read by the NMS.
          
(4) The values of the above objects which are set to
 0xffffffff must be modified, and the values of any other
 objects can be changed.  When establishing a VP connection,
 connPvcLowVCI and connPvcHighVCI should be set to 0.
When connPvcTrafficType is set to trafficUBR, the values
of connPvcLowThroughput and connPvcHighThroughput are
ignored. When all parameters have acceptable values, the
switch sets connPvcRowStatus to 'notInService'.
          
(5) When the NMS sets connPvcRowStatus to 'active', the
switch validates each parameter's value, and tries to 
establish the connection.  If this operation fails, the
the cause of the failure is indicated by the value of
connPvcCause.
          
At present, the switch allows connPvcRowStatus to have a
value of notReady or notInService for only one row at a
time.
          
2. Adding a new leaf to an existing pt-to-mpt connection
          
(1) Determine the value of connPvcIndex for the existing
point-to-multipoint connection to which a new leaf is
to be added.  
          
(2) Determine the value of connPvcHighIfIndex as the
ifIndex value of the interface to be used for the new leaf.
          
(3) Set connPvcRowStatus to 'createAndWait' using the
values of connPvcIndex and connPvcHighIfIndex as indexes.
This causes the switch to create the new leaf with some
objects being set to default values.  The parameters for
which there is no reasonable default are set to 0xffffffff.
          
     Object                Default
     connPvcHighVPI        0xffffffff
     connPvcHighVCI        0xffffffff
     connPvcHighUpcParam   512
     connPvcHighUpc        pass(1)
     connPvcHighThroughput 0
          
The switch then sets the value of connPvcRowStatus to
'notReady'.  The default values can be read by the NMS.
          
(4) The NMS must modify the values of connPvcHighVPI and
connPvcHighVCI, and can modify the values of connPvcHighUpc,
connPvcHighUpcParam and connPvcHighThroughput.  When
establishing a VP connection, connPvcHighVCI should
be set to 0.  The NMS should not change the values of
the following objects:
          
     connPvcTopology
     connPvcTrafficType
     connPvcLowIfIndex
     connPvcLowVPI
     connPvcLowVCI
     connPvcLowUpcParam
     connPvcLowUpc
     connPvcLowThroughput
          
 When all parameters have acceptable values, the switch
 sets connPvcRowStatus to 'notInService'.
          
 (5) When the NMS sets connPvcRowStatus to 'active', the
 switch validates each parameter's value, and tries to add
 the new leaf to the original connection.  If this operation
 fails, the cause of the failure is indicated by the value
 of connPvcCause.
          
3. PVC deletion  procedure
          
(1) Set the connPvcRowStatus to 'destroy'.
If the row exists but is impossible to delete, the cause
of the failure is indicated by the value of connPvcCause.
If the deletion is successful, the row is deleted 
(including the instance of connPvcCause for that row).
          
Notes:
 - a row representing a terminating VP will not have
instances of the following objects: connPvcLowUpc,
connPvcLowUpcParam, connPvcLowThroughput, connPvcHighUpc,
connPvcHighUpcParam, connPvcHighThroughput,
connPvcLowOutCells, connPvcHighInCells,
connPvcHighUpcViolatedCells, connPvcLowInCells,
connPvcHighOutCells, and connPvcLowUpcViolatedCells.
          
 - a row representing a connection between the
gateway-PAD (the switch's internal port) and a line
interface will not have instances of the following
objects: connPvcLowUpc, connPvcLowUpcParam,
connPvcLowThroughput, connPvcHighUpc, connPvcHighUpcParam,
connPvcHighThroughput, connPvcHighOutCells,
connPvcHighInCells, and connPvcHighUpcViolatedCells.
connPvcEntry row .1.3.6.1.4.1.119.2.3.14.3.3.3.1
A row in the table is used to show the current PVC/SVCs.
Column Syntax OID
connPvcIndexmandatory
A unique value to identify this point-to-point
or point-to-multipoint connection.
A point-to-multipoint connection has multiple
rows in this table, one for each leaf, each
one having the same value of this object.
Integer32
Constraints:
range: 0-8191
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.1
Topology of the connection.
Enumerationr/w
Enumerated Values:
1uniDirectionalVCC
2biDirectionalVCC
3uniDirectionalVPC
4biDirectionalVPC
5broadcastVPC
6broadcastVCC
7gateway
8vpterm
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.2
Traffic Type.
Enumerationr/w
Enumerated Values:
1trafficCBR
2trafficVBR
4trafficUBR
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.3
The line interface number (ifIndex) of the low port.
Normally, the low port has a lower ifIndex value than
the high port. However, for point-to-multipoint
connections, the root is always the low port, regardless
of whe…
Integer32r/w
Constraints:
range: 1-16
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.4
connPvcLowVPImandatory
VPI value of the connection on the low port.
Integer32r/w
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.5
connPvcLowVCImandatory
VCI value of the connection on the low port.
Integer32r/w
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.6
Number of cells allowed to be sent in the unit cell
time (512 cell times).
Integer32r/w
Constraints:
range: 0-512
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.7
connPvcLowUpcmandatory
The action to take on a UPC violation for this connection
on the low port. The tagging action is not supported by
current hardware.
Enumerationr/w
Enumerated Values:
1pass
2discard
3tagging
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.8
Average rate of the connection (Mbps). Direction is from
the low port to high port. This parameter is valid
for the connection whose traffic type is CBR or VBR.
Integer32r/w
Constraints:
range: 0-622
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.9
The line interface number (ifIndex) of the high port.
Normally, the high port has a higher ifIndex value than
the low port. However, for point-to-multipoint
connections, the root is always the low port, regardless
of w…
Integer32
Constraints:
range: 1-17
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.10
The VPI value of the connection on the high port.
Integer32r/w
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.11
The VCI value of the connection on the high port.
Integer32r/w
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.12
Number of cells allowed to be sent in the unit cell
time (512 cell times).
Integer32r/w
Constraints:
range: 0-512
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.13
The action to take on a UPC violation for this connection
on the high port. The tagging action is not supported by
current hardware.
Enumerationr/w
Enumerated Values:
1pass
2discard
3tagging
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.14
Average rate of the connection (Mbps). Direction is from
the high port to low port. This parameter is valid
for the connection whose traffic type is CBR or VBR.
Integer32r/w
Constraints:
range: 0-622
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.15
Number of incoming cells on this connection on low port.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.16
Number of outgoing cells on this connection on the high
port.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.17
Number of incoming cells on this connection on high port.
(Valid for bi-direction connections only).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.18
Number of outgoing cells on this connection on the low.
port. (Valid for bi-direction connections only).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.19
Number of UPC violation cells incoming from the low
port.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.20
Number of UPC violation cells incoming from the high
port. (Valid for bi-direction connections only).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.21
The status of this row.

'active' indicates that the connection is in use.

'notInService' indicates that the row exists but
the connection is not established.

'notRea…
Enumerationr/w
Enumerated Values:
1active
2notInService
3notReady
5createAndWait
6destroy
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.22
connPvcCausemandatory
The result of the PVC establishment/deletion.
Enumeration
Enumerated Values:
1existing
2vpivciBusy
3vpivciOutOfRange
4rateOverFlow
5upvpOutOfRange
6broadcastTableFull
7inconsistentVPVC
8lineDiagnosis
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.23
connPvcKindmandatory
This object identifies the connection is SVC or PVC.
Enumeration
Enumerated Values:
1pvc
2svc
.1.3.6.1.4.1.119.2.3.14.3.3.3.1.24

perfIfTable

table mandatory
.1.3.6.1.4.1.119.2.3.14.3.4.2 · 1 row entry · 14 columns
Uses the nec variant from /opt/observium/mibs/nec.
Command help
Walk perfIfTable
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'LS100-MIB' -M '/opt/observium/mibs/nec:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'LS100-MIB::perfIfTable'
Table of performance monitoring information.
perfIfEntry row .1.3.6.1.4.1.119.2.3.14.3.4.2.1
Performance monitoring information for a specific line.
Indexes
Column Syntax OID
perfIfIndexmandatory
Line interface number. Same as ifIndex.
Integer32
Type Constraints:
range: -2147483648..2147483647
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.1
perfIfLcvsmandatory
Line Code Violation. This object is valid only for
DS3/E3.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.2
Number of B1 (BIP) errors(OC-3c, UTP-5),
Number of C-bit parity violation(DS3),
Number of CRC-6 violation(DS1).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.3
Number of B2 (BIP) errors(OC-3c, UTP-5),
Number of P-bit parity violation(DS3).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.4
Number of B3 (BIP) errors(OC-3c, UTP-5),
Number of PLCP BIP violation(DS3).
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.5
Number of HEC errors detected.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.6
Number of misdelivered cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.7
Number of cells discarded due to buffer overflow.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.8
Number of received CBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.9
Number of transmitted CBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.10
Number of received VBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.11
Number of transmitted VBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.12
Number of received UBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.15
Number of transmitted UBR cells.
RFC1155-SMICounter
Type Constraints:
range: 0..4294967295
.1.3.6.1.4.1.119.2.3.14.3.4.2.1.16