All MIBs › TMU-MIB › fibTmuMatchNoStationsListReason
fibTmuMatchNoStationsListReason
Module: TMU-MIB
OID (symbolic): TMU-MIB::fibTmuMatchNoStationsListReason
OID (numeric): 1.3.6.1.4.1.22.60.4.10
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Indication meaningful only if fibTmuStationsUpToDate above is not up-to-date. empty-reason - Either there is a list or the reason for the fact that there is no list is yet unknown. malloc-fail - System could not provide memory for this list. segment-unstable - Indications from the token ring chip sets were that the ring has not reached a stable state yet. no-chip-on-list - Chip set handling software could not indicate which of the Tmu chips is on the portion of token ring which is on the Tau ports. inconsistency - Inconsistent responses from low level token ring handler indicate ring is not yet stable. soft-01 - Software error. system could not retrieve a mac address related to a specified tr interface. soft-02 - Software error. system could not retrieve a mac address related to a specified tr interface. first-not-found - First chip set of Tmu could not be found on the list of addresses supplied by the token ring driver. Ring is not stable yet. second-not-found - Second chip set of Tmu could not be found on the list of addresses supplied by the token ring driver. Ring is not stable yet. found-twice - One chip set of Tmu was found twice on the list of addresses supplied by the token ring driver. Ring is not stable yet. no-tr-list - No configuration is currently available from the token ring driver. Ring is unstable or some sw error. See remark in fibTmuStationsListValid above.
What is fibTmuMatchNoStationsListReason?
This is meaningful only when fibTmuStationsUpToDate shows the data isn't current, and explains why, using the same set of reasons as fibTmuMatchNoMatchReason (empty-reason, malloc-fail, segment-unstable, no-chip-on-list) but for the Stations table. Admins read it to understand why fresh Stations data isn't available. For example, malloc-fail here would tell an admin the device is under memory pressure rather than experiencing a ring-topology problem.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22.60.4.10 snmpwalk -v2c -c public <target> TMU-MIB::fibTmuMatchNoStationsListReason
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.22.60.4.10.1 snmpget -v2c -c public <target> TMU-MIB::fibTmuMatchNoStationsListReason.1
Start monitoring Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the TMU-MIB::fibTmuMatchNoStationsListReason OID value, configure state conditions and alerts, and monitor any Legacy networking equipment, enterprise OID 22 fibronics (firmware inventory/fault-handling status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.22 | spartacus | CMU-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.22.60 | tmu | TMU-MIB |
| 1.3.6.1.4.1.22.60.4 | tmuStations | TMU-MIB |
| 1.3.6.1.4.1.22.60.4.10 | fibTmuMatchNoStationsListReason | TMU-MIB |