LUMINOUS-TOPOLOGY-MIB: View SNMP OID List / Download MIB

VENDOR: LUMINOUS NETWORKS, INC


 Home MIB: LUMINOUS-TOPOLOGY-MIB
Download as:   
SNMPv2-CONF, SNMPv2-SMI, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 luminous 1.3.6.1.4.1.4614
           lumADM 1.3.6.1.4.1.4614.1
               lumTopologyMIB 1.3.6.1.4.1.4614.1.3
The Luminous Topology MIB contains information related to the Luminous Ring Topology.
                   lumRingCommands 1.3.6.1.4.1.4614.1.3.1
                       lumTopoDiscoveryGroup 1.3.6.1.4.1.4614.1.3.1.1
                           lumTopoDiscoveryRetries 1.3.6.1.4.1.4614.1.3.1.1.1 integer32 read-write
Initially set to 3.
                           lumTopoNeighborInfoTimer 1.3.6.1.4.1.4614.1.3.1.1.2 integer32 read-write
The Neighbor Information Timer sets the amount of time between periodic sends of the neighbor information message from each node on each egress link.
                           lumTopoDiscoveryConvergenceTimer 1.3.6.1.4.1.4614.1.3.1.1.3 integer32 read-write
The topology convergence timer sets the amount of time during which no messages indicating a change of topology have been received before the topology can be considered to have converged. If the topology convergence timer has not reached the required value for convergence, the topology discovery timer is reset.
                           lumTopoDiscoveryTimer 1.3.6.1.4.1.4614.1.3.1.1.4 integer32 read-write
The topology discovery timer sets the total amount of time until the topology convergence timer is checked. If the topology convergence timer has not reached the required value for convergence, the topology discovery timer is reset.
                           lumTopoDiscovery 1.3.6.1.4.1.4614.1.3.1.1.5 integer read-write
Setting this field to doDiscover(2) has the effect of starting the Ring Topology Discovery. The Retries and Timers in the fields above in order for them to have effect should be set before attempting to start discovery. Upon Discovery completion this field is set by the SNMP Agent to either none(1) or ,if failed to discoveryFailed(4). stopDiscovery(3) is for the future. Setting to discoveryFailed(4) is not allowed by SNMP Agent. discoveryFailed(4) can be also the outcome of topology discovery performed by the ring management without NMS requesting it. Enumeration: 'stopDiscover': 3, 'none': 1, 'doDiscover': 2, 'discoveryFailed': 4.
                           lumTopoDiscoveryFailedNode 1.3.6.1.4.1.4614.1.3.1.1.6 ipaddress read-only
The node that causes the the Topology Discovery failure. Valid only if lumTopoDiscovery is discoveryFailed(4).
                       lumRingCommand 1.3.6.1.4.1.4614.1.3.1.2 integer read-write
Setting this field to clearAll(2) has the effect of clearing all lumLinkAdminStatus (setting it to 0). This clears all externally initiated commands. Setting this field to lockoutOfProtection(3) results in all traffic on the ring returning to the shortest-hop available path. This sets all LinkAdminStatus values to 16000 (standard operational link). Setting this field to switchToRevertiveMode(4), has the effect of switching from non-revertive mode to revertive mode fot the whole ring. commandFailed(5) cannot be set. The lumRingCommand is set to this value by SNMP Agent when requested command fails. Enumeration: 'none': 1, 'clearAll': 2, 'commandFailed': 4, 'lockoutOfProtection': 3.
                       lumRingRevertiveMode 1.3.6.1.4.1.4614.1.3.1.3 integer read-write
Setting this field to revertiveMode(1), has the effect of switching from non-revertive mode to revertive mode for the whole ring. Likewise setting this field to nonRevertiveMode(2), has the effect of switching from revertive mode to non-revertive mode fot the whole ring. Enumeration: 'revertiveMode': 1, 'nonRevertiveMode': 2.
                       lumProtectionSwitchHysteresis 1.3.6.1.4.1.4614.1.3.1.4 integer32 read-only
Hysteresis factor. This factor prevents ping-ponging in protection switching when a link's measured status is varying with time. Valid values are between 5 and 100.
                   lumProtectionSwitchingTable 1.3.6.1.4.1.4614.1.3.2 no-access
The Luminous Protection Switching Table.
                       lumProtectionSwitchingEntry 1.3.6.1.4.1.4614.1.3.2.1 no-access
Each entry represents connection information of current node to other nodes on the ring.
                           lumProtDestinationIP 1.3.6.1.4.1.4614.1.3.2.1.1 ipaddress read-only
This is the address of the destination node.
                           lumProtMeasDestCost 1.3.6.1.4.1.4614.1.3.2.1.2 integer32 read-only
This is the cumulative measured cost per destination for each egress interface of a node.
                           lumProtNonRevDestCost 1.3.6.1.4.1.4614.1.3.2.1.3 integer32 read-only
This is the non-revertive cost per destination for each egress interface of a node. This is used only for non-revertive protection switching.
                           lumProtMeasPrefDir 1.3.6.1.4.1.4614.1.3.2.1.4 integer32 read-only
This is the interface number corresponding to the preferred direction for data from this node to lumProtDestinationIP based on measured costs.
                           lumProtNonRevPrefDir 1.3.6.1.4.1.4614.1.3.2.1.5 integer32 read-only
This is the interface number corresponding to the preferred direction for data from this node to lumProtDestinationIP based on non-revertive costs.
                   lumRingLinkTable 1.3.6.1.4.1.4614.1.3.3 no-access
The Luminous Ring Topology Table.
                       lumRingLinkEntry 1.3.6.1.4.1.4614.1.3.3.1 no-access
Each entry represents connection information of every ingress to every ingress node on the ring
                           lumLinkIngressNodeIP 1.3.6.1.4.1.4614.1.3.3.1.1 ipaddress read-only
This is the address of the ingress link node.
                           lumLinkEgressNodeIP 1.3.6.1.4.1.4614.1.3.3.1.2 ipaddress read-only
This is the address of the egress link node.
                           lumLinkIngressInterface 1.3.6.1.4.1.4614.1.3.3.1.3 integer32 read-only
This is the interface number (slot number) of the ring transition card connected to the link at the ingress node.
                           lumLinkEgressInterface 1.3.6.1.4.1.4614.1.3.3.1.4 integer32 read-only
This is the interface number (slot number) of the ring transition card connected to the link at the egress node.
                           lumLinkOperStatus 1.3.6.1.4.1.4614.1.3.3.1.5 integer32 read-only
This is the latest measured operational status of the link. It is reported from the ring applications to the shelf manager to the NMS. Currently, traffic congestion is not taken into account in status computations. A bit error rate of a * 10 ^ (-b), where a is greater or equal to 1 and less than 10 and has 3 significant digits, is represented to NMS as 1000*b + 100*(10 - a). The minimum value of lumLinkOperStatus is 1000 to show that the link is down, and the maximum value of lumLinkOperStatus is 16000 to show a standard operational link.
                           lumLinkNonRevStatus 1.3.6.1.4.1.4614.1.3.3.1.6 integer32 read-only
This is the minimum value of link operational status reported since the last Revert-To-Measured-Oper-Status command from the NMS. This field is used only for non-revertive protection switching, e.g. lumLinkNonRevStatus will differ from lumLinkOperStatus if a link goes down and then comes back up, since the operator must reactivate a link under such conditions. For revertive protection switching, this field is equal to lumLinkOperStatus. This value is set by the ring applications and reported to EMS via the shelf manager.
                           lumLinkAdminStatus 1.3.6.1.4.1.4614.1.3.3.1.7 integer32 read-write
This is the latest administrative status of the link set by the operator. It is reported to the ring applications via the shelf manager. There are several options for this field. If the value of lumLinkAdminStatus is set to 0 by the operator, it is ignored by the ring applications, e.g. the ring applications use lumLinkOperStatus and lumLinkAdminStatus for all decision- making. If lumLinkAdminStatus is set to a valid lumLinkOperStatus value by the operator, the link is considered to have that bit error rate irrespective of the actual lumLinkOperStatus value. It is expected that the 'a' value of BER need only have one significant digit when entered by the operator.
                           lumLinkSyncOperStatus 1.3.6.1.4.1.4614.1.3.3.1.8 integer32 read-only
This is a single indicator of whether a link is an active part of a synchronization path. This value is set by the ring itself and reported to NMS.
                           lumLinkSyncNonRevStatus 1.3.6.1.4.1.4614.1.3.3.1.9 integer32 read-only
.
                           lumLinkSyncAdminStatus 1.3.6.1.4.1.4614.1.3.3.1.10 integer32 read-write
This is the latest administrative status of the link for synchronization set by the operator. It is to be set by NMS.
                   lumRingThresholdTable 1.3.6.1.4.1.4614.1.3.4 no-access
The Luminous Ring Threshold Table.
                       lumRingThresholdEntry 1.3.6.1.4.1.4614.1.3.4.1 no-access
Each entry represents threshold values per threshold window on the ring.
                           lumRingThresholdWindow 1.3.6.1.4.1.4614.1.3.4.1.1 integer32 read-write
This is the threshold window size.
                           lumRingThresholdValue 1.3.6.1.4.1.4614.1.3.4.1.2 integer32 read-write
This is the threshold value for this window.
                           lumRingThresholdStatus 1.3.6.1.4.1.4614.1.3.4.1.3 rowstatus read-write
This object is used to create and delete rows in the Threshold Table.