LS100-R2-MIB

All MIBs › LS100-R2-MIB

Category: Device Management

Description: Revision 2 SNMP MIB for LS100 series devices with updated management objects for device monitoring and control.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is LS100-R2-MIB?

LS100-R2-MIB is a NEC-specific SNMP MIB (revision 2) for the NEC LS100 series switching node, part of the "nec-mib" enterprise tree under necProductDepend. It exposes overall node operational status, a per-interface configuration table (physical type, revision, admin/oper status), fan health, and traffic-management parameters such as UPC (usage parameter control) window size and best-effort/guaranteed buffer sizing and thresholds. It is explicitly used for hardware and software status monitoring of the switch: nodeOperStatus reports whether the node is up, and nodeFanStatus reports the health of cooling fans, both essential for detecting hardware faults before they cause outages. As a vendor-specific product-dependent MIB, it builds on NEC's shared enterprise MIB tree conventions rather than standard IETF MIBs, though it is used alongside interface configuration data much like the standard IF-MIB. It is deployed on NEC LS100 series switching equipment within carrier or enterprise backbone networks. Network engineers evaluating or troubleshooting this functionality can download the LS100-R2-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in LS100-R2-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

NEC LS100 series switch

Monitoring Examples

An operator would poll nodeOperStatus and nodeFanStatus together to detect whether the LS100 node itself is down and whether a cooling fan failure might be the cause, since fan failures often precede thermal shutdowns. Walking nodeIfConfTable/nodeIfConfEntry by nodeIfConfIndex shows each interface's physical type, hardware revision, and status, letting an admin spot a port stuck in a non-operational nodeIfConfStatus. Monitoring nodeBestEffortBufferSize against nodeBestEffortBufferThreshold reveals when best-effort traffic buffers are approaching exhaustion, an early indicator of congestion.

What Can Be Monitored

node operational status
fan status
per-interface physical type and status
UPC window size
best-effort buffer utilization and threshold
guaranteed buffer size

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
enterprises

OIDs

OID symbolic	OID numeric	Type	Access	Description
nec	1.3.6.1.4.1.119
nec_mib	1.3.6.1.4.1.119.2
necProductDepend	1.3.6.1.4.1.119.2.3
atomis_mib	1.3.6.1.4.1.119.2.3.14
m5core_mib	1.3.6.1.4.1.119.2.3.14.3
node	1.3.6.1.4.1.119.2.3.14.3.1
INT nodeOperStatus	1.3.6.1.4.1.119.2.3.14.3.1.1	INTEGER	read-only	Operational status of the LS100.
nodeIfConfTable	1.3.6.1.4.1.119.2.3.14.3.1.2		not-accessible	The configuration of the line cards.
nodeIfConfEntry	1.3.6.1.4.1.119.2.3.14.3.1.2.1		not-accessible	The configuration of a line card.
INT nodeIfConfIndex	1.3.6.1.4.1.119.2.3.14.3.1.2.1.1	INTEGER	read-only	The index of the table. Same as ifIndex.
INT nodeIfConfPhysType	1.3.6.1.4.1.119.2.3.14.3.1.2.1.2	INTEGER	read-only	The PMD/physical layer format of the line card.
STR nodeIfConfRev	1.3.6.1.4.1.119.2.3.14.3.1.2.1.3	DisplayString	read-only	The revision of the line cards.
INT nodeIfConfStatus	1.3.6.1.4.1.119.2.3.14.3.1.2.1.4	INTEGER	read-only	Operational status of the line card.
INT nodeFanStatus	1.3.6.1.4.1.119.2.3.14.3.1.3	INTEGER	read-only	Operational status of the Fan.
INT nodeUpcWindowSize	1.3.6.1.4.1.119.2.3.14.3.1.4	INTEGER	read-write	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.
INT nodeBestEffortBufferSize	1.3.6.1.4.1.119.2.3.14.3.1.5	INTEGER	read-write	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.
INT nodeGuaranteedBufferSize	1.3.6.1.4.1.119.2.3.14.3.1.6	INTEGER	read-write	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.
INT nodeBestEffortBufferThreshold	1.3.6.1.4.1.119.2.3.14.3.1.7	INTEGER	read-write	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.
INT nodeGuaranteedBufferThreshold	1.3.6.1.4.1.119.2.3.14.3.1.8	INTEGER	read-write	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.
INT nodeSaveConf	1.3.6.1.4.1.119.2.3.14.3.1.9	INTEGER	read-write	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).
INT nodeSaveResult	1.3.6.1.4.1.119.2.3.14.3.1.10	INTEGER	read-only	Show the result of the save command issued from NMS. The result is either success/temporary failure/notReady.
INT nodeReset	1.3.6.1.4.1.119.2.3.14.3.1.11	INTEGER	read-write	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).
linf	1.3.6.1.4.1.119.2.3.14.3.2
linfStatusTable	1.3.6.1.4.1.119.2.3.14.3.2.1		not-accessible	Status of the line cards including ATM specific information.
linfStatusEntry	1.3.6.1.4.1.119.2.3.14.3.2.1.1		not-accessible	Status of a line card including ATM specific information.
INT linfIndex	1.3.6.1.4.1.119.2.3.14.3.2.1.1.1	INTEGER	read-only	Same as ifIndex
INT linfStatus	1.3.6.1.4.1.119.2.3.14.3.2.1.1.2	INTEGER	read-only	Status of line interface
INT linfConf	1.3.6.1.4.1.119.2.3.14.3.2.1.1.3	INTEGER	read-write	Line card type.
INT linfFwdAvailableBandWidth	1.3.6.1.4.1.119.2.3.14.3.2.1.1.4	INTEGER	read-only	The amount of bandwidth (Mbps) available/unallocated in the forward (incoming) direction.
INT linfBkwdAvailableBandWidth	1.3.6.1.4.1.119.2.3.14.3.2.1.1.5	INTEGER	read-only	The amount of bandwidth (Mbps) available/unallocated in the backward (outgoing) direction.
conn	1.3.6.1.4.1.119.2.3.14.3.3
INT connPvcIndexNext	1.3.6.1.4.1.119.2.3.14.3.3.1	INTEGER	read-only	The next available index for a row of the connPvcTable.
INT connPvcIndexEnable	1.3.6.1.4.1.119.2.3.14.3.3.2	INTEGER	read-write	When read, this object is the current minimum value of an index in the connPvcTable. Writing this value has no effect.
connPvcTable	1.3.6.1.4.1.119.2.3.14.3.3.3		not-accessible	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 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. 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). Note: 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	1.3.6.1.4.1.119.2.3.14.3.3.3.1		not-accessible	A row in the table is used to show the current PVC/SVCs.
INT connPvcIndex	1.3.6.1.4.1.119.2.3.14.3.3.3.1.1	INTEGER	read-only	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.
INT connPvcTopology	1.3.6.1.4.1.119.2.3.14.3.3.3.1.2	INTEGER	read-write	Topology of the connection.
INT connPvcTrafficType	1.3.6.1.4.1.119.2.3.14.3.3.3.1.3	INTEGER	read-write	Traffic Type.
INT connPvcLowIfIndex	1.3.6.1.4.1.119.2.3.14.3.3.3.1.4	INTEGER	read-write	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.
INT connPvcLowVPI	1.3.6.1.4.1.119.2.3.14.3.3.3.1.5	INTEGER	read-write	VPI value of the connection on the low port.
INT connPvcLowVCI	1.3.6.1.4.1.119.2.3.14.3.3.3.1.6	INTEGER	read-write	VCI value of the connection on the low port.
INT connPvcLowUpcParam	1.3.6.1.4.1.119.2.3.14.3.3.3.1.7	INTEGER	read-write	Number of cells allowed to be sent in the unit cell time (512 cell times).
INT connPvcLowUpc	1.3.6.1.4.1.119.2.3.14.3.3.3.1.8	INTEGER	read-write	The action to take on a UPC violation for this connection on the low port. The tagging action is not supported by current hardware.
INT connPvcLowThroughput	1.3.6.1.4.1.119.2.3.14.3.3.3.1.9	INTEGER	read-write	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.
INT connPvcHighIfIndex	1.3.6.1.4.1.119.2.3.14.3.3.3.1.10	INTEGER	read-only	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).
INT connPvcHighVPI	1.3.6.1.4.1.119.2.3.14.3.3.3.1.11	INTEGER	read-write	The VPI value of the connection on the high port.
INT connPvcHighVCI	1.3.6.1.4.1.119.2.3.14.3.3.3.1.12	INTEGER	read-write	The VCI value of the connection on the high port.
INT connPvcHighUpcParam	1.3.6.1.4.1.119.2.3.14.3.3.3.1.13	INTEGER	read-write	Number of cells allowed to be sent in the unit cell time (512 cell times).
INT connPvcHighUpc	1.3.6.1.4.1.119.2.3.14.3.3.3.1.14	INTEGER	read-write	The action to take on a UPC violation for this connection on the high port. The tagging action is not supported by current hardware.
INT connPvcHighThroughput	1.3.6.1.4.1.119.2.3.14.3.3.3.1.15	INTEGER	read-write	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.
CTR connPvcLowInCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.16	Counter	read-only	Number of incoming cells on this connection on low port.
CTR connPvcHighOutCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.17	Counter	read-only	Number of outgoing cells on this connection on the high port.
CTR connPvcHighInCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.18	Counter	read-only	Number of incoming cells on this connection on high port. (valid for bi-direction connection only).
CTR connPvcLowOutCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.19	Counter	read-only	Number of outgoing cells on this connection on the low. port (valid for bi-direction connection only).
CTR connPvcLowUpcViolatedCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.20	Counter	read-only	Number of UPC violation cells incoming from the low port.
CTR connPvcHighUpcViolatedCells	1.3.6.1.4.1.119.2.3.14.3.3.3.1.21	Counter	read-only	Number of UPC violation cells incoming from the high port. (Valid for Bi-direction connection only)
INT connPvcRowStatus	1.3.6.1.4.1.119.2.3.14.3.3.3.1.22	INTEGER	read-write	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.
INT connPvcCause	1.3.6.1.4.1.119.2.3.14.3.3.3.1.23	INTEGER	read-only	The result of the PVC establishment/deletion.
INT connPvcKind	1.3.6.1.4.1.119.2.3.14.3.3.3.1.24	INTEGER	read-only	This object identifies the connection is SVC or PVC.
perf	1.3.6.1.4.1.119.2.3.14.3.4
INT perfTrapEnable	1.3.6.1.4.1.119.2.3.14.3.4.1	INTEGER	read-write	The status of performance monitoring traps.
perfIfTable	1.3.6.1.4.1.119.2.3.14.3.4.2		not-accessible	Table of performance monitoring information.
perfIfEntry	1.3.6.1.4.1.119.2.3.14.3.4.2.1		not-accessible	Performance monitoring information for a specific line.
INT perfIfIndex	1.3.6.1.4.1.119.2.3.14.3.4.2.1.1	INTEGER	read-only	Line interface number. Same as ifIndex.
CTR perfIfLcvs	1.3.6.1.4.1.119.2.3.14.3.4.2.1.2	Counter	read-only	Line Code Violation. This object is valid only for DS3/E3.
CTR perfIfParitySections	1.3.6.1.4.1.119.2.3.14.3.4.2.1.3	Counter	read-only	Number of B1 (BIP) errors(OC-3c, UTP-5), Number of C-bit parity violation(DS3), Number of CRC-6 violation(DS1).
CTR perfIfParityLines	1.3.6.1.4.1.119.2.3.14.3.4.2.1.4	Counter	read-only	Number of B2 (BIP) errors(OC-3c, UTP-5), Number of P-bit parity violation(DS3).
CTR perfIfParityPaths	1.3.6.1.4.1.119.2.3.14.3.4.2.1.5	Counter	read-only	Number of B3 (BIP) errors(OC-3c, UTP-5), Number of PLCP BIP violation(DS3).
CTR perfIfHecErrors	1.3.6.1.4.1.119.2.3.14.3.4.2.1.6	Counter	read-only	Number of HEC errors detected.
CTR perfIfMisDelivdCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.7	Counter	read-only	Number of misdelivered cells.
CTR perfIfOverFlowCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.8	Counter	read-only	Number of cells discarded due to buffer overflow.
CTR perfIfInCBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.9	Counter	read-only	Number of received CBR cells.
CTR perfIfOutCBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.10	Counter	read-only	Number of transmitted CBR cells.
CTR perfIfInVBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.11	Counter	read-only	Number of received VBR cells.
CTR perfIfOutVBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.12	Counter	read-only	Number of transmitted VBR cells.
CTR perfIfInUBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.15	Counter	read-only	Number of received UBR cells.
CTR perfIfOutUBRCells	1.3.6.1.4.1.119.2.3.14.3.4.2.1.16	Counter	read-only	Number of transmitted UBR cells.

RFC description

Vendor-private product MIB for managing the LS100-R2 network device, provides device configuration and operational monitoring.

Start monitoring NEC LS100 series switch with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download LS100-R2-MIB

What Is LS100-R2-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description