All MIBs › TMU-MIB › fibTmuMatchNoMatchReason
fibTmuMatchNoMatchReason
Module: TMU-MIB
OID (symbolic): TMU-MIB::fibTmuMatchNoMatchReason
OID (numeric): 1.3.6.1.4.1.22.60.3.10
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-only
Description: Indication meaningful only if fibTmuMatchUpToDate 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. soft-03 - Software indicated a match could be found but could not supply the actula list. Internal sw error. ports-gt-stations - Number of ports was fould to be higher than the number of stations. This is only reason for not construction the 'match' table. stations-gt-ports - Number of stations was fould to be higher than the number of ports. This is only reason for not construction the 'match' table. no-tr-list - No configuration is currently available from the token ring driver. Ring is unstable or some sw error. See remark in fibTmuMatchListValid above.
What is fibTmuMatchNoMatchReason?
This is meaningful only when fibTmuMatchUpToDate shows the data isn't current, and explains why: empty-reason (unknown or no list yet), malloc-fail (out of memory), segment-unstable (the ring hasn't reached a stable state), or no-chip-on-list (chipset software couldn't determine which Tmu chip is on the Tau-port portion of the ring). Admins read it to understand why fresh topology data isn't available rather than just seeing a stale flag. For example, segment-unstable would tell an admin to simply wait for the ring to settle rather than treat it as a hardware fault.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.22.60.3.10 snmpwalk -v2c -c public <target> TMU-MIB::fibTmuMatchNoMatchReason
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.22.60.3.10.1 snmpget -v2c -c public <target> TMU-MIB::fibTmuMatchNoMatchReason.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::fibTmuMatchNoMatchReason 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.3 | tmuMatch | TMU-MIB |
| 1.3.6.1.4.1.22.60.3.10 | fibTmuMatchNoMatchReason | TMU-MIB |