MIBs Depot

LS100-MIB

Namespace
cisco
Source file
LS100-MIB
Digest
sha256:d9e8b6b552c0f547c939ff05620c6f0f3aab36fa1375b3a9592b57aed3aadb61

Imports

FromSymbols
SNMPv2-CONFMODULE-COMPLIANCE, NOTIFICATION-GROUP
SNMPv2-SMICounter32, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, OBJECT-TYPE, enterprises, iso
SNMPv2-TCDisplayString, TEXTUAL-CONVENTION

Imported by

Nothing in this corpus imports this module.

Load order

Every file a consumer needs in order to load this module, dependencies first.

LS100-MIB
SNMPv2-CONF
SNMPv2-SMI
SNMPv2-TC

Textual conventions

NameOIDSyntaxAccessStatus
DisplayString
type

Objects

NameOIDSyntaxAccessStatus
nec
OBJECT-IDENTITY
1.3.6.1.4.1.119
nec_mib
OBJECT-IDENTITY
1.3.6.1.4.1.119.2
necProductDepend
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3
atomis_mib
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14
m5core_mib
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14.3
node
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14.3.1
nodeOperStatus
OBJECT-TYPE
Operational status of the LS100.
1.3.6.1.4.1.119.2.3.14.3.1.1INTEGER {down(1), active(2), offLine(3), testing(4), initializing(5)}read-onlymandatory
nodeIfConfTable
OBJECT-TYPE
The configuration of the line cards.
1.3.6.1.4.1.119.2.3.14.3.1.2not-accessiblemandatory
nodeIfConfEntry
OBJECT-TYPE
The configuration of a line card.
1.3.6.1.4.1.119.2.3.14.3.1.2.1not-accessiblemandatory
nodeIfConfIndex
OBJECT-TYPE
The index of the table. Same as ifIndex.
1.3.6.1.4.1.119.2.3.14.3.1.2.1.1INTEGERread-onlymandatory
nodeIfConfPhysType
OBJECT-TYPE
The PMD/physical layer format of the line card.
1.3.6.1.4.1.119.2.3.14.3.1.2.1.2INTEGER {other(1), sar(2), taxi100M(3), oc3cSMF(4), oc3cMMF(5), ds3PlcpScramble(6), ds3PlcpNoScramble(7), relay6Mcell(8), ds3Scramble(9), ds3NoScramble(10), e3PlcpScramble(11), e3PlcpNoScramble(12), e3Scramble(13), e3NoScramble(14), utp5(15), leasedLine3M(16), leasedLine4M(17), leasedLine6M(18), utp5classB(19), oc3cSmfShaper(20), taxi140M(21), notInstalled(99)}read-onlymandatory
nodeIfConfRev
OBJECT-TYPE
The revision of the line cards.
1.3.6.1.4.1.119.2.3.14.3.1.2.1.3DisplayStringread-onlymandatory
nodeIfConfStatus
OBJECT-TYPE
Operational status of the line card.
1.3.6.1.4.1.119.2.3.14.3.1.2.1.4INTEGER {other(1), inService(2), outOfService(3), testing(4), localLoopBack(5), remoteLoopBack(6), notInstalled(99)}read-onlymandatory
nodeFanStatus
OBJECT-TYPE
Operational status of the Fan.
1.3.6.1.4.1.119.2.3.14.3.1.3INTEGER {up(1), down(2)}read-onlymandatory
nodeUpcWindowSize
OBJECT-TYPE
UPC window size. Integer Wi represents Wi X 512 cell time. Wi=1 correspond to 1.4msec. Wi=120 correspond to 168msec. It is not allowed to change window size when any PVC exists.
1.3.6.1.4.1.119.2.3.14.3.1.4INTEGER (1..120)read-writemandatory
nodeBestEffortBufferSize
OBJECT-TYPE
Input buffer capacity for Best Effort traffic(Bb). The number of cells stored in the buffer is Bb X 128. The default value is 8. The sum of the buffer capacity is 2047 cells.
1.3.6.1.4.1.119.2.3.14.3.1.5INTEGER (0..16)read-writemandatory
nodeGuaranteedBufferSize
OBJECT-TYPE
Input buffer capacity for Guaranteed traffic(Bg). The number of cells stored in the buffer is Bg X 128. The default value is 0. The sum of the buffer capacity is 2047 cells.
1.3.6.1.4.1.119.2.3.14.3.1.6INTEGER (0..16)read-writemandatory
nodeBestEffortBufferThreshold
OBJECT-TYPE
Threshold buffer capacity for Best Effort traffic. If the number of cells stored in the buffer exceeds this threshold, cells with CLP=1 and traffic defined as UBR will be discarded.
1.3.6.1.4.1.119.2.3.14.3.1.7INTEGER (0..16)read-writemandatory
nodeGuaranteedBufferThreshold
OBJECT-TYPE
Threshold buffer capacity for Guaranteed traffic. If the number of cells stored in the buffer exceeds this threshold, cells with CLP=1 and traffic defined as VBR will be discarded.
1.3.6.1.4.1.119.2.3.14.3.1.8INTEGER (0..16)read-writemandatory
nodeSaveConf
OBJECT-TYPE
Save system configuration information including the PVC table to the non-volatile memory. Writing a value of save(1) saves the configiration data. Writing the value noOperation(2) has no effect. When read, this object always has the value noOperation(2).
1.3.6.1.4.1.119.2.3.14.3.1.9INTEGER {save(1), noOperation(2)}read-writemandatory
nodeSaveResult
OBJECT-TYPE
Indicates the result of the save command issued from NMS. The result is either success/temporary failure/notReady.
1.3.6.1.4.1.119.2.3.14.3.1.10INTEGER {temporaryFailure(1), notReady(2), ready(3), success(4), nearend(5)}read-onlymandatory
nodeReset
OBJECT-TYPE
Writing the value reset(1) resets the system. Writing the value noOperation(2) has no effect. When read, this object always has the value noOperation(2).
1.3.6.1.4.1.119.2.3.14.3.1.11INTEGER {reset(1), noOperation(2)}read-writemandatory
linf
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14.3.2
linfStatusTable
OBJECT-TYPE
Status of the line cards including ATM specific information.
1.3.6.1.4.1.119.2.3.14.3.2.1not-accessiblemandatory
linfStatusEntry
OBJECT-TYPE
Status of a line card including ATM specific information.
1.3.6.1.4.1.119.2.3.14.3.2.1.1not-accessiblemandatory
linfIndex
OBJECT-TYPE
Same as ifIndex
1.3.6.1.4.1.119.2.3.14.3.2.1.1.1INTEGER (1..64)read-onlymandatory
linfStatus
OBJECT-TYPE
Status of line interface
1.3.6.1.4.1.119.2.3.14.3.2.1.1.2INTEGER {normal(1), los(2), lof(3), loc(4), ais(5), yellowLine(6), yellowPath(7), lop(8), idle(9), yellowAlarm(10), plcpLOF(11), plcpYellow(12), maFERF(13), rai(14), payloadAllOnes(15), notInstalled(99)}read-onlymandatory
linfConf
OBJECT-TYPE
Line card type.
1.3.6.1.4.1.119.2.3.14.3.2.1.1.3INTEGER {publicUNI(1), privateUNI(2), privateNNI(3), others(99)}read-writemandatory
linfFwdAvailableBandWidth
OBJECT-TYPE
The amount of bandwidth (Mbps) available/unallocated in the forward (incoming) direction.
1.3.6.1.4.1.119.2.3.14.3.2.1.1.4INTEGERread-onlymandatory
linfBkwdAvailableBandWidth
OBJECT-TYPE
The amount of bandwidth (Mbps) available/unallocated in the backward (outgoing) direction.
1.3.6.1.4.1.119.2.3.14.3.2.1.1.5INTEGERread-onlymandatory
conn
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14.3.3
connPvcIndexNext
OBJECT-TYPE
The next available index for a row of the connPvcTable.
1.3.6.1.4.1.119.2.3.14.3.3.1INTEGER (0..8191)read-onlymandatory
connPvcIndexEnable
OBJECT-TYPE
When read, this object is the current minimum value of an index in the connPvcTable. Writing this value has no effect.
1.3.6.1.4.1.119.2.3.14.3.3.2INTEGER (0..8191)read-writedeprecated
connPvcTable
OBJECT-TYPE
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.
1.3.6.1.4.1.119.2.3.14.3.3.3not-accessiblemandatory
connPvcEntry
OBJECT-TYPE
A row in the table is used to show the current PVC/SVCs.
1.3.6.1.4.1.119.2.3.14.3.3.3.1not-accessiblemandatory
connPvcIndex
OBJECT-TYPE
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.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.1INTEGER (0..8191)read-onlymandatory
connPvcTopology
OBJECT-TYPE
Topology of the connection.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.2INTEGER {uniDirectionalVCC(1), biDirectionalVCC(2), uniDirectionalVPC(3), biDirectionalVPC(4), broadcastVPC(5), broadcastVCC(6), gateway(7), vpterm(8)}read-writemandatory
connPvcTrafficType
OBJECT-TYPE
Traffic Type.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.3INTEGER {trafficCBR(1), trafficVBR(2), trafficUBR(4)}read-writemandatory
connPvcLowIfIndex
OBJECT-TYPE
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 whether it is greater or smaller than the port numbers of individual leaves.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.4INTEGER (1..16)read-writemandatory
connPvcLowVPI
OBJECT-TYPE
VPI value of the connection on the low port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.5INTEGERread-writemandatory
connPvcLowVCI
OBJECT-TYPE
VCI value of the connection on the low port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.6INTEGERread-writemandatory
connPvcLowUpcParam
OBJECT-TYPE
Number of cells allowed to be sent in the unit cell time (512 cell times).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.7INTEGER (0..512)read-writemandatory
connPvcLowUpc
OBJECT-TYPE
The action to take on a UPC violation for this connection on the low port. The tagging action is not supported by current hardware.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.8INTEGER {pass(1), discard(2), tagging(3)}read-writemandatory
connPvcLowThroughput
OBJECT-TYPE
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.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.9INTEGER (0..622)read-writemandatory
connPvcHighIfIndex
OBJECT-TYPE
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 whether it is greater or smaller than the port numbers of individual leaves. Line interface number 17 corresponds to gateway (the switch's internal port).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.10INTEGER (1..17)read-onlymandatory
connPvcHighVPI
OBJECT-TYPE
The VPI value of the connection on the high port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.11INTEGERread-writemandatory
connPvcHighVCI
OBJECT-TYPE
The VCI value of the connection on the high port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.12INTEGERread-writemandatory
connPvcHighUpcParam
OBJECT-TYPE
Number of cells allowed to be sent in the unit cell time (512 cell times).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.13INTEGER (0..512)read-writemandatory
connPvcHighUpc
OBJECT-TYPE
The action to take on a UPC violation for this connection on the high port. The tagging action is not supported by current hardware.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.14INTEGER {pass(1), discard(2), tagging(3)}read-writemandatory
connPvcHighThroughput
OBJECT-TYPE
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.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.15INTEGER (0..622)read-writemandatory
connPvcLowInCells
OBJECT-TYPE
Number of incoming cells on this connection on low port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.16Counterread-onlymandatory
connPvcHighOutCells
OBJECT-TYPE
Number of outgoing cells on this connection on the high port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.17Counterread-onlymandatory
connPvcHighInCells
OBJECT-TYPE
Number of incoming cells on this connection on high port. (Valid for bi-direction connections only).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.18Counterread-onlymandatory
connPvcLowOutCells
OBJECT-TYPE
Number of outgoing cells on this connection on the low. port. (Valid for bi-direction connections only).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.19Counterread-onlymandatory
connPvcLowUpcViolatedCells
OBJECT-TYPE
Number of UPC violation cells incoming from the low port.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.20Counterread-onlymandatory
connPvcHighUpcViolatedCells
OBJECT-TYPE
Number of UPC violation cells incoming from the high port. (Valid for bi-direction connections only).
1.3.6.1.4.1.119.2.3.14.3.3.3.1.21Counterread-onlymandatory
connPvcRowStatus
OBJECT-TYPE
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. 'notReady' indicates that the row exists in the agent, but is missing information necessary in order to be established. 'createAndWait' supplied by a management station wishing to create a new row. 'destroy' supplied by a management station wishing to delete the row.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.22INTEGER {active(1), notInService(2), notReady(3), createAndWait(5), destroy(6)}read-writemandatory
connPvcCause
OBJECT-TYPE
The result of the PVC establishment/deletion.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.23INTEGER {existing(1), vpivciBusy(2), vpivciOutOfRange(3), rateOverFlow(4), upvpOutOfRange(5), broadcastTableFull(6), inconsistentVPVC(7), lineDiagnosis(8)}read-onlymandatory
connPvcKind
OBJECT-TYPE
This object identifies the connection is SVC or PVC.
1.3.6.1.4.1.119.2.3.14.3.3.3.1.24INTEGER {pvc(1), svc(2)}read-onlymandatory
perf
OBJECT-IDENTITY
1.3.6.1.4.1.119.2.3.14.3.4
perfTrapEnable
OBJECT-TYPE
The status of performance monitoring traps. Its value does not affect other traps, such as coldStart.
1.3.6.1.4.1.119.2.3.14.3.4.1INTEGER {enable(1), disable(2)}read-writemandatory
perfIfTable
OBJECT-TYPE
Table of performance monitoring information.
1.3.6.1.4.1.119.2.3.14.3.4.2not-accessiblemandatory
perfIfEntry
OBJECT-TYPE
Performance monitoring information for a specific line.
1.3.6.1.4.1.119.2.3.14.3.4.2.1not-accessiblemandatory
perfIfIndex
OBJECT-TYPE
Line interface number. Same as ifIndex.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.1INTEGERread-onlymandatory
perfIfLcvs
OBJECT-TYPE
Line Code Violation. This object is valid only for DS3/E3.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.2Counterread-onlymandatory
perfIfParitySections
OBJECT-TYPE
Number of B1 (BIP) errors(OC-3c, UTP-5), Number of C-bit parity violation(DS3), Number of CRC-6 violation(DS1).
1.3.6.1.4.1.119.2.3.14.3.4.2.1.3Counterread-onlymandatory
perfIfParityLines
OBJECT-TYPE
Number of B2 (BIP) errors(OC-3c, UTP-5), Number of P-bit parity violation(DS3).
1.3.6.1.4.1.119.2.3.14.3.4.2.1.4Counterread-onlymandatory
perfIfParityPaths
OBJECT-TYPE
Number of B3 (BIP) errors(OC-3c, UTP-5), Number of PLCP BIP violation(DS3).
1.3.6.1.4.1.119.2.3.14.3.4.2.1.5Counterread-onlymandatory
perfIfHecErrors
OBJECT-TYPE
Number of HEC errors detected.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.6Counterread-onlymandatory
perfIfMisDelivdCells
OBJECT-TYPE
Number of misdelivered cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.7Counterread-onlymandatory
perfIfOverFlowCells
OBJECT-TYPE
Number of cells discarded due to buffer overflow.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.8Counterread-onlymandatory
perfIfInCBRCells
OBJECT-TYPE
Number of received CBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.9Counterread-onlymandatory
perfIfOutCBRCells
OBJECT-TYPE
Number of transmitted CBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.10Counterread-onlymandatory
perfIfInVBRCells
OBJECT-TYPE
Number of received VBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.11Counterread-onlymandatory
perfIfOutVBRCells
OBJECT-TYPE
Number of transmitted VBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.12Counterread-onlymandatory
perfIfInUBRCells
OBJECT-TYPE
Number of received UBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.15Counterread-onlymandatory
perfIfOutUBRCells
OBJECT-TYPE
Number of transmitted UBR cells.
1.3.6.1.4.1.119.2.3.14.3.4.2.1.16Counterread-onlymandatory