LUM-SYSINFO-MIB
The LUM-SYSINFO-MIB module enables monitoring of system resource utilization, specifically CPU load and RAM memory consumption, on Lumensys hardware devices via SNMP. This module provides the necessary OID definitions for tracking real-time performance metrics to assess device health and capacity planning.
Imported Objects
Objects
45 total| Object Name |
|---|
lumSysinfoMIBModuleContains information about CPU utilization, RAM memory etc. MODULE-IDENTITY .1.3.6.1.4.1.8708.1.1.71 |
lumSysinfoConfs OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.1 |
lumSysinfoGroups OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.1.1 |
lumSysinfoCompl OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.1.2 |
lumSysinfoMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.2 |
sysinfoBoardStartupList OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.2.1 |
sysinfoBoardStartupTableThe board startup list. SEQUENCE OF SysinfoBoardStartupEntry .1.3.6.1.4.1.8708.2.71.2.1.1 |
sysinfoBoardStartupEntryAn entry in the board startup list. SysinfoBoardStartupEntry .1.3.6.1.4.1.8708.2.71.2.1.1.1 |
sysinfoBoardStartupIndexAn arbitrary index assigned to each board entry.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.1.1.1.1 |
sysinfoBoardStartupNameObject name, [boardName]:[subrack]:[slot]ro MgmtNameString .1.3.6.1.4.1.8708.2.71.2.1.1.1.2 |
sysinfoBoardStartupUptimeUptime since boot. Syntax (same as 'uptime' and 'top' linux commands):
- 'mm min', example: '23 minutes', or
- 'hh:mm', example: '14:08', meaning 14 hours and 8 minutes, or
- 'days, mm min', example: '36 days and 48 min' or
- 'days, hh:mm' example: '36 days, 11:32' meaning 36 days, 11 hours and 32 minutesro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8708.2.71.2.1.1.1.3 |
sysinfoBoardStartupUptimeSecondsUptime since boot expressed in seconds.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.1.1.1.4 |
sysinfoBoardStartupRebootReasonReason for the last reboot.
Possible reasons are:
- Software upgrade (SWU) function
- Watchdog reboot due to a nonrecoverable failure condition
- FW activation
- Nonrecoverable configuration mismatch between controller and traffic unit
- Nonrecoverable failure during bootup of board
- Unknown. Could be:
- Upgrade from a release prior to XTM_30.1
- Reboot from bash
- Power cyclero DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8708.2.71.2.1.1.1.5 |
sysinfoBoardLoadList OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.2.2 |
sysinfoBoardLoadTableThe board load average list. SEQUENCE OF SysinfoBoardLoadEntry .1.3.6.1.4.1.8708.2.71.2.2.1 |
sysinfoBoardLoadEntryAn entry in the board list. One entry for each board. SysinfoBoardLoadEntry .1.3.6.1.4.1.8708.2.71.2.2.1.1 |
sysinfoBoardLoadIndexAn arbitrary index assigned to each board entry.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.2.1.1.1 |
sysinfoBoardLoadNameObject name, [boardName]:[subrack]:[slot]ro MgmtNameString .1.3.6.1.4.1.8708.2.71.2.2.1.1.2 |
sysinfoBoardLoadLoad1MinSystem load averages is the average number of processes that are
either in a runnable or uninterruptable state. A process in a
runnable state is either using the CPU or waiting to use the CPU. A
process in uninterruptable state is waiting for some I/O access, eg
waiting for disk. Load averages are not normalized for the number of CPUs
in a system, so a load average of 1 means a single CPU system is
loaded all the time while on a 4 CPU system it means it was idle 75%
of the time.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.2.1.1.3 |
sysinfoBoardLoadLoad5MinSystem load averages is the average number of processes that are
either in a runnable or uninterruptable state. A process in a
runnable state is either using the CPU or waiting to use the CPU. A
process in uninterruptable state is waiting for some I/O access, eg
waiting for disk. Load averages are not normalized for the number of CPUs
in a system, so a load average of 1 means a single CPU system is
loaded all the time while on a 4 CPU system it means it was idle 75%
of the time.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.2.1.1.4 |
sysinfoBoardLoadLoad15MinSystem load averages is the average number of processes that are
either in a runnable or uninterruptable state. A process in a
runnable state is either using the CPU or waiting to use the CPU. A
process in uninterruptable state is waiting for some I/O access, eg
waiting for disk. Load averages are not normalized for the number of CPUs
in a system, so a load average of 1 means a single CPU system is
loaded all the time while on a 4 CPU system it means it was idle 75%
of the time.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.2.1.1.5 |
sysinfoBoardMemoryList OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.2.3 |
sysinfoBoardMemoryTableThe board memory list. SEQUENCE OF SysinfoBoardMemoryEntry .1.3.6.1.4.1.8708.2.71.2.3.1 |
sysinfoBoardMemoryEntryAn entry in the board list. One entry for each board. SysinfoBoardMemoryEntry .1.3.6.1.4.1.8708.2.71.2.3.1.1 |
sysinfoBoardMemoryIndexAn arbitrary index assigned to each board entry.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.3.1.1.1 |
sysinfoBoardMemoryNameObject name, [boardName]:[subrack]:[slot]ro MgmtNameString .1.3.6.1.4.1.8708.2.71.2.3.1.1.2 |
sysinfoBoardMemoryTotalMemTotal usable memory.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.3.1.1.3 |
sysinfoBoardMemoryFreeMemThe amount of physical memory not used by the system.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.3.1.1.4 |
sysinfoBoardMemoryAvailableMemAn estimate of how much memory is available for starting new applications, without swapping.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.3.1.1.5 |
sysinfoBoardMemoryUsageMemPercentMemory utilization expressed as a percentage. Based on available memory.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.3.1.1.6 |
sysinfoBoardProcessList OBJECT IDENTIFIER .1.3.6.1.4.1.8708.2.71.2.4 |
sysinfoBoardProcessTableThe board process list. SEQUENCE OF SysinfoBoardProcessEntry .1.3.6.1.4.1.8708.2.71.2.4.1 |
sysinfoBoardProcessEntryAn entry for each process per board. SysinfoBoardProcessEntry .1.3.6.1.4.1.8708.2.71.2.4.1.1 |
sysinfoBoardProcessIndexAn arbitrary index assigned to each board entry.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.4.1.1.1 |
sysinfoBoardProcessNameObject name, [boardName]:[subrack]:[slot]:[localIndex]ro MgmtNameString .1.3.6.1.4.1.8708.2.71.2.4.1.1.2 |
sysinfoBoardProcessProcessNameProcess name. Child processes are displayed within brackets ().ro MgmtNameString .1.3.6.1.4.1.8708.2.71.2.4.1.1.3 |
sysinfoBoardProcessPidProcess ID.ro Integer32 .1.3.6.1.4.1.8708.2.71.2.4.1.1.4 |
sysinfoBoardProcessVmSizeVirtual memory size.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.4.1.1.5 |
sysinfoBoardProcessVmRSSResident set size.ro Unsigned32 .1.3.6.1.4.1.8708.2.71.2.4.1.1.6 |
sysinfoBoardProcessSetReferenceSets the reference values for virtual memory size
and resident set sizerw Enumeration .1.3.6.1.4.1.8708.2.71.2.4.1.1.7 |
sysinfoBoardProcessVmSizeReferenceVirtual memory size reference value.ro Unsigned32WithNA .1.3.6.1.4.1.8708.2.71.2.4.1.1.8 |
sysinfoBoardProcessVmRSSReferenceResident set size reference value.ro Unsigned32WithNA .1.3.6.1.4.1.8708.2.71.2.4.1.1.9 |
sysinfoBoardProcessVmSizeDiffDifference between the current virtual memory size
and its reference value.ro Integer32WithNA .1.3.6.1.4.1.8708.2.71.2.4.1.1.10 |
sysinfoBoardProcessVmRSSDiffDifference between the current resident set size
and its reference value.ro Integer32WithNA .1.3.6.1.4.1.8708.2.71.2.4.1.1.11 |
sysinfoBoardProcessReferenceTimeTime where reference values were saved.ro DisplayString (SNMPv2-TC) .1.3.6.1.4.1.8708.2.71.2.4.1.1.12 |
More MIBs from Infinera
Browse all InfineraMIBs →The LUM-WDM-MIB module facilitates the monitoring and management of WDM trunk interfaces, passive optical interfaces, and associated protection groups within optical transport networks. It provides granular visibility into interface status, signal parameters, and protection switching states to ensure the integrity of wavelength division multiplexing infrastructure.
The LUM-REG MIB module provides the global OID namespace registration for Transmode hardware and software platforms, enabling the monitoring of proprietary device-specific metrics such as optical transceiver parameters, line interface states, and system resource utilization. This module serves as the foundational registry for Transmode's SNMP agents, allowing network management systems to access standardized and vendor-specific data points for operational telemetry and fault isolation.
The LUM-EQUIPMENT-MIB module provides SNMP-based monitoring and configuration of Lumex hardware infrastructure, specifically tracking subrack status, board states, power supply health, fan operation, and slot occupancy. This MIB enables granular visibility into physical layer components and environmental conditions for telecommunications or industrial networking equipment.
The LUM-OA-MIB module enables monitoring and configuration of optical amplifier interfaces within Lumentum optical transport equipment, exposing performance metrics such as input/output optical power, gain levels, pump laser currents, and alarm states for amplifier health assessment.
The LUM-IFPERF-MIB module enables SNMP-based monitoring and configuration of physical and data-link layer performance metrics, specifically tracking Forward Error Correction (FEC), G.826 error rates, and Layer 0 through Layer 2 statistics on optical transport interfaces. It provides uni-directional and general attribute tables to manage time-stamped performance data for interface administration and error analysis.
The LUM-SYSTEM-MIB module provides granular monitoring and configuration of system node parameters, date/time synchronization, license status, and authentication settings (RADIUS/TACACS+) for Lumex or LUM-series network appliances. It exposes specific metrics for user account management, authentication server configurations, and system licensing data to facilitate centralized identity and access control auditing.