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.
Parsed from file fibr_FR9230.mib.txt
Company: None
Module: TMU-MIB
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.
Parsed from file TMU-MIB.mib
Module: TMU-MIB
Vendor: Fibronics
Module: TMU-MIB
[Automatically extracted from oidview.com]
fibTmuMatchNoMatchReason OBJECT-TYPE SYNTAX INTEGER { empty-reason(1), malloc-fail(2), segment-unstable(3), no-chip-on-list(4), inconsistency(5), soft-01(6), soft-02(7), first-not-found(8), second-not-found(9), found-twice(10), soft-03(11), ports-gt-stations(12), stations-gt-ports(13), no-tr-list(14) } ACCESS read-only STATUS mandatory 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." ::= { tmuMatch 10 }
fibTmuMatchNoMatchReason OBJECT-TYPE SYNTAX INTEGER { empty-reason(1), malloc-fail(2), segment-unstable(3), no-chip-on-list(4), inconsistency(5), soft-01(6), soft-02(7), first-not-found(8), second-not-found(9), found-twice(10), soft-03(11), ports-gt-stations(12), stations-gt-ports(13), no-tr-list(14) } ACCESS read-only STATUS mandatory 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." ::= { tmuMatch 10 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.22.60.3.10.0 | fibTmuMatchNoMatchReason | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.22.60.3.1 | fibTmuMatchUpdateTime | 1 | 1 | Time [in sys timer units] from startup at which the table below has been updated. See remark in fibTmuMatchListValid below. |
| 1.3.6.1.4.1.22.60.3.2 | fibTmuMatchNumEntries | 1 | 1 | Number of meaningful entries in the match array. The index of the last meaningful entry is num_entries. See remark in fibTmuMatchL… |
| 1.3.6.1.4.1.22.60.3.3 | fibTmuMatchNumTmuEntries | 1 | 1 | Number of meaningful entries in the match array which belong to stations attached to the tmu via tau ports. This does not include… |
| 1.3.6.1.4.1.22.60.3.4 | fibTmuMatchFirstChipIndex | 1 | 1 | The index in the match table at which the the first chipset is located (order of stations on match table is downstream, i.e. in t… |
| 1.3.6.1.4.1.22.60.3.5 | fibTmuMatchSecondChipIndex | 1 | 1 | The index in the match table at which the the second chipset is located (order of stations on match table is downstream, i.e. in … |
| 1.3.6.1.4.1.22.60.3.6 | fibTmuMatchActMonIndex | 1 | 1 | The index in the match table at which the active monitor is located (order of stations on match table is downstream, i.e. in the d… |
| 1.3.6.1.4.1.22.60.3.7 | fibTmuMatchConfigChipIndex | 1 | 1 | The index in the match table from which the information for the configuration was collected (order of stations on match table is d… |
| 1.3.6.1.4.1.22.60.3.8 | fibTmuMatchListValid | 1 | 1 | Flag indicating whether the information in the tmuMatch group is valid or not. If information is not valid, ALL objects will retur… |
| 1.3.6.1.4.1.22.60.3.9 | fibTmuMatchUpToDate | 1 | 1 | Flag. If set '1' then the information in All objects of tmuMatch group is not up to date any more: Some changes have occurred and … |
| 1.3.6.1.4.1.22.60.3.20 | fibTmuMatchTable | 1 | 6 | fibTmuMatchtable |