tokenRingMLStatsIndex
1.3.6.1.2.1.16.1.2.1.1
Integer32 (1..65535)
The value of this object uniquely identifies this tokenRingMLStats entry.
2001-03-02
Remote network monitoring devices, often called monitors or probes, are instruments that exist for the purpose of managing a network. This MIB defines objects for managing remote network monitoring devices.
Download TOKEN-RING-RMON-MIB.txt Open TOKEN-RING-RMON-MIB.txt in a new tab
END OF TOC
1.3.6.1.2.1.16.1.2
Index: tokenRingMLStatsIndex
A list of Mac-Layer Token Ring statistics entries.
1.3.6.1.2.1.16.1.2.1.1
Integer32 (1..65535)
The value of this object uniquely identifies this tokenRingMLStats entry.
1.3.6.1.2.1.16.1.2.1.2
OBJECT IDENTIFIER
This object identifies the source of the data that this tokenRingMLStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in the IF-MIB [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all error reports on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingMLStatsStatus object is equal to valid(1).
1.3.6.1.2.1.16.1.2.1.3
Counter32
The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. This value is the same as the corresponding tokenRingPStatsDropEvents.
1.3.6.1.2.1.16.1.2.1.4
Counter32
The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network (excluding framing bits but including FCS octets).
1.3.6.1.2.1.16.1.2.1.5
Counter32
The total number of MAC packets (excluding packets that were not good frames) received.
1.3.6.1.2.1.16.1.2.1.6
Counter32
The total number of times that the ring enters the ring purge state from normal ring state. The ring purge state that comes in response to the claim token or beacon state is not counted.
1.3.6.1.2.1.16.1.2.1.7
Counter32
The total number of ring purge MAC packets detected by probe.
1.3.6.1.2.1.16.1.2.1.8
Counter32
The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) from a non-beaconing state. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
1.3.6.1.2.1.16.1.2.1.9
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
The total amount of time that the ring has been in the beaconing state.
1.3.6.1.2.1.16.1.2.1.10
Counter32
The total number of beacon MAC packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.11
Counter32
The total number of times that the ring enters the claim token state from normal ring state or ring purge state. The claim token state that comes in response to a beacon state is not counted.
1.3.6.1.2.1.16.1.2.1.12
Counter32
The total number of claim token MAC packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.13
Counter32
The total number of NAUN changes detected by the probe.
1.3.6.1.2.1.16.1.2.1.14
Counter32
The total number of line errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.15
Counter32
The total number of adapter internal errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.16
Counter32
The total number of burst errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.17
Counter32
The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.18
Counter32
The total number of abort delimiters reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.19
Counter32
The total number of lost frame errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.20
Counter32
The total number of receive congestion errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.21
Counter32
The total number of frame copied errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.22
Counter32
The total number of frequency errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.23
Counter32
The total number of token errors reported in error reporting packets detected by the probe.
1.3.6.1.2.1.16.1.2.1.24
Counter32
The total number of soft error report frames detected by the probe.
1.3.6.1.2.1.16.1.2.1.25
Counter32
The total number of ring poll events detected by the probe (i.e. the number of ring polls initiated by the active monitor that were detected).
1.3.6.1.2.1.16.1.2.1.26
OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING
The entity that configured this entry and is therefore using the resources assigned to it.
1.3.6.1.2.1.16.1.2.1.27
EntryStatus1 = valid2 = createRequest3 = underCreation4 = invalidThe status of a table entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant EntryStatus object. An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances with default values to complete a conceptual row in this table. Because the creation of these default objects is entirely at the option of the agent, the manager must not assume that any will be created, but may make use of any that are created. Immediately after completing the create operation, the agent must set this object to underCreation(3). When in the underCreation(3) state, an entry is allowed to exist in a possibly incomplete, possibly inconsistent state, usually to allow it to be modified in multiple PDUs. When in this state, an entry is not fully active. Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. An entry in the valid(1) state is fully configured and consistent and fully represents the configuration or operation such a row is intended to represent. For example, it could be a statistical function that is configured and active, or a filter that is available in the list of filters processed by the packet capture process. A manager is restricted to changing the state of an entry in the following ways: To: valid createRequest underCreation invalid From: valid OK NO OK OK createRequest N/A N/A N/A N/A underCreation OK NO OK OK invalid NO NO NO OK nonExistent NO OK NO OK In the table above, it is not applicable to move the state from the createRequest state to any other state because the manager will never find the variable in that state. The nonExistent state is not a value of the enumeration, rather it means that the entryStatus variable does not exist at all. An agent may allow an entryStatus variable to change state in additional ways, so long as the semantics of the states are followed. This allowance is made to ease the implementation of the agent and is made despite the fact that managers should never exercise these additional state transitions. · Integer32
The status of this tokenRingMLStats entry.
1.3.6.1.2.1.16.1.3
Index: tokenRingPStatsIndex
A list of promiscuous Token Ring statistics entries.
1.3.6.1.2.1.16.1.3.1.1
Integer32 (1..65535)
The value of this object uniquely identifies this tokenRingPStats entry.
1.3.6.1.2.1.16.1.3.1.2
OBJECT IDENTIFIER
This object identifies the source of the data that this tokenRingPStats entry is configured to analyze. This source can be any tokenRing interface on this device. In order to identify a particular interface, this object shall identify the instance of the ifIndex object, defined in IF- MIB [17], for the desired interface. For example, if an entry were to receive data from interface #1, this object would be set to ifIndex.1. The statistics in this group reflect all non-MAC packets on the local network segment attached to the identified interface. This object may not be modified if the associated tokenRingPStatsStatus object is equal to valid(1).
1.3.6.1.2.1.16.1.3.1.3
Counter32
The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not necessarily the number of packets dropped; it is just the number of times this condition has been detected. This value is the same as the corresponding tokenRingMLStatsDropEvents
1.3.6.1.2.1.16.1.3.1.4
Counter32
The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets.
1.3.6.1.2.1.16.1.3.1.5
Counter32
The total number of non-MAC packets in good frames received.
1.3.6.1.2.1.16.1.3.1.6
Counter32
The total number of non-MAC good frames received that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
1.3.6.1.2.1.16.1.3.1.7
Counter32
The total number of non-MAC good frames received that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
1.3.6.1.2.1.16.1.3.1.8
Counter32
The total number of non-MAC good frames received that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.9
Counter32
The total number of non-MAC good frames received that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.10
Counter32
The total number of non-MAC good frames received that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.11
Counter32
The total number of non-MAC good frames received that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.12
Counter32
The total number of non-MAC good frames received that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.13
Counter32
The total number of non-MAC good frames received that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.14
Counter32
The total number of non-MAC good frames received that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.15
Counter32
The total number of non-MAC good frames received that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.16
Counter32
The total number of non-MAC good frames received that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.17
Counter32
The total number of non-MAC good frames received that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.1.3.1.18
OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING
The entity that configured this entry and is therefore using the resources assigned to it.
1.3.6.1.2.1.16.1.3.1.19
EntryStatus1 = valid2 = createRequest3 = underCreation4 = invalidThe status of a table entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant EntryStatus object. An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances with default values to complete a conceptual row in this table. Because the creation of these default objects is entirely at the option of the agent, the manager must not assume that any will be created, but may make use of any that are created. Immediately after completing the create operation, the agent must set this object to underCreation(3). When in the underCreation(3) state, an entry is allowed to exist in a possibly incomplete, possibly inconsistent state, usually to allow it to be modified in multiple PDUs. When in this state, an entry is not fully active. Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. An entry in the valid(1) state is fully configured and consistent and fully represents the configuration or operation such a row is intended to represent. For example, it could be a statistical function that is configured and active, or a filter that is available in the list of filters processed by the packet capture process. A manager is restricted to changing the state of an entry in the following ways: To: valid createRequest underCreation invalid From: valid OK NO OK OK createRequest N/A N/A N/A N/A underCreation OK NO OK OK invalid NO NO NO OK nonExistent NO OK NO OK In the table above, it is not applicable to move the state from the createRequest state to any other state because the manager will never find the variable in that state. The nonExistent state is not a value of the enumeration, rather it means that the entryStatus variable does not exist at all. An agent may allow an entryStatus variable to change state in additional ways, so long as the semantics of the states are followed. This allowance is made to ease the implementation of the agent and is made despite the fact that managers should never exercise these additional state transitions. · Integer32
The status of this tokenRingPStats entry.
1.3.6.1.2.1.16.2.3
Index: tokenRingMLHistoryIndex · tokenRingMLHistorySampleIndex
A list of Mac-Layer Token Ring statistics entries.
1.3.6.1.2.1.16.2.3.1.1
Integer32 (1..65535)
The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
1.3.6.1.2.1.16.2.3.1.2
Integer32 (1..2147483647)
An index that uniquely identifies the particular Mac-Layer sample this entry represents among all Mac-Layer samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
1.3.6.1.2.1.16.2.3.1.3
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
1.3.6.1.2.1.16.2.3.1.4
Counter32
The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
1.3.6.1.2.1.16.2.3.1.5
Counter32
The total number of octets of data in MAC packets (excluding those that were not good frames) received on the network during this sampling interval (excluding framing bits but including FCS octets).
1.3.6.1.2.1.16.2.3.1.6
Counter32
The total number of MAC packets (excluding those that were not good frames) received during this sampling interval.
1.3.6.1.2.1.16.2.3.1.7
Counter32
The total number of times that the ring entered the ring purge state from normal ring state during this sampling interval. The ring purge state that comes from the claim token or beacon state is not counted.
1.3.6.1.2.1.16.2.3.1.8
Counter32
The total number of Ring Purge MAC packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.9
Counter32
The total number of times that the ring enters a beaconing state (beaconFrameStreamingState, beaconBitStreamingState, beaconSetRecoveryModeState, or beaconRingSignalLossState) during this sampling interval. Note that a change of the source address of the beacon packet does not constitute a new beacon event.
1.3.6.1.2.1.16.2.3.1.10
TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32
The amount of time that the ring has been in the beaconing state during this sampling interval.
1.3.6.1.2.1.16.2.3.1.11
Counter32
The total number of beacon MAC packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.12
Counter32
The total number of times that the ring enters the claim token state from normal ring state or ring purge state during this sampling interval. The claim token state that comes from the beacon state is not counted.
1.3.6.1.2.1.16.2.3.1.13
Counter32
The total number of claim token MAC packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.14
Counter32
The total number of NAUN changes detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.15
Counter32
The total number of line errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.16
Counter32
The total number of adapter internal errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.17
Counter32
The total number of burst errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.18
Counter32
The total number of AC (Address Copied) errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.19
Counter32
The total number of abort delimiters reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.20
Counter32
The total number of lost frame errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.21
Counter32
The total number of receive congestion errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.22
Counter32
The total number of frame copied errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.23
Counter32
The total number of frequency errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.24
Counter32
The total number of token errors reported in error reporting packets detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.25
Counter32
The total number of soft error report frames detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.26
Counter32
The total number of ring poll events detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.3.1.27
Integer32
The maximum number of active stations on the ring detected by the probe during this sampling interval.
1.3.6.1.2.1.16.2.4
Index: tokenRingPHistoryIndex · tokenRingPHistorySampleIndex
A list of promiscuous Token Ring statistics entries.
1.3.6.1.2.1.16.2.4.1.1
Integer32 (1..65535)
The history of which this entry is a part. The history identified by a particular value of this index is the same history as identified by the same value of historyControlIndex.
1.3.6.1.2.1.16.2.4.1.2
Integer32 (1..2147483647)
An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyControlEntry. This index starts at 1 and increases by one as each new sample is taken.
1.3.6.1.2.1.16.2.4.1.3
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of day, it should start the first sample of the history at a time such that when the next hour of the day begins, a sample is started at that instant. Note that following this rule may require the probe to delay collecting the first sample of the history, as each sample must be of the same interval. Also note that the sample which is currently being collected is not accessible in this table until the end of its interval.
1.3.6.1.2.1.16.2.4.1.4
Counter32
The total number of events in which packets were dropped by the probe due to lack of resources during this sampling interval. Note that this number is not necessarily the number of packets dropped, it is just the number of times this condition has been detected.
1.3.6.1.2.1.16.2.4.1.5
Counter32
The total number of octets of data in good frames received on the network (excluding framing bits but including FCS octets) in non-MAC packets during this sampling interval.
1.3.6.1.2.1.16.2.4.1.6
Counter32
The total number of non-MAC good frames received during this sampling interval.
1.3.6.1.2.1.16.2.4.1.7
Counter32
The total number of non-MAC good frames received during this sampling interval that were directed to an LLC broadcast address (0xFFFFFFFFFFFF or 0xC000FFFFFFFF).
1.3.6.1.2.1.16.2.4.1.8
Counter32
The total number of non-MAC good frames received during this sampling interval that were directed to a local or global multicast or functional address. Note that this number does not include packets directed to the broadcast address.
1.3.6.1.2.1.16.2.4.1.9
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 18 and 63 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.10
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 64 and 127 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.11
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 128 and 255 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.12
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 256 and 511 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.13
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 512 and 1023 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.14
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 1024 and 2047 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.15
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 2048 and 4095 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.16
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 4096 and 8191 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.17
Counter32
The total number of non-MAC good frames received during this sampling interval that were between 8192 and 18000 octets in length inclusive, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.2.4.1.18
Counter32
The total number of non-MAC good frames received during this sampling interval that were greater than 18000 octets in length, excluding framing bits but including FCS octets.
1.3.6.1.2.1.16.10.1
Index: ringStationControlIfIndex
A list of ringStation table control entries.
1.3.6.1.2.1.16.10.1.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device from which ringStation data is collected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF- MIB [17].
1.3.6.1.2.1.16.10.1.1.2
Integer32
The number of ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
1.3.6.1.2.1.16.10.1.1.3
Integer32
The number of active ringStationEntries in the ringStationTable associated with this ringStationControlEntry.
1.3.6.1.2.1.16.10.1.1.4
INTEGER1 = normalOperation2 = ringPurgeState3 = claimTokenState4 = beaconFrameStreamingState5 = beaconBitStreamingState6 = beaconRingSignalLossState7 = beaconSetRecoveryModeState · Integer32
The current status of this ring.
1.3.6.1.2.1.16.10.1.1.5
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The address of the sender of the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
1.3.6.1.2.1.16.10.1.1.6
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The address of the NAUN in the last beacon frame received by the probe on this ring. If no beacon frames have been received, this object shall be equal to six octets of zero.
1.3.6.1.2.1.16.10.1.1.7
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The address of the Active Monitor on this segment. If this address is unknown, this object shall be equal to six octets of zero.
1.3.6.1.2.1.16.10.1.1.8
Counter32
The number of add and delete events in the ringStationOrderTable optionally associated with this ringStationControlEntry.
1.3.6.1.2.1.16.10.1.1.9
OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING
The entity that configured this entry and is therefore using the resources assigned to it.
1.3.6.1.2.1.16.10.1.1.10
EntryStatus1 = valid2 = createRequest3 = underCreation4 = invalidThe status of a table entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant EntryStatus object. An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances with default values to complete a conceptual row in this table. Because the creation of these default objects is entirely at the option of the agent, the manager must not assume that any will be created, but may make use of any that are created. Immediately after completing the create operation, the agent must set this object to underCreation(3). When in the underCreation(3) state, an entry is allowed to exist in a possibly incomplete, possibly inconsistent state, usually to allow it to be modified in multiple PDUs. When in this state, an entry is not fully active. Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. An entry in the valid(1) state is fully configured and consistent and fully represents the configuration or operation such a row is intended to represent. For example, it could be a statistical function that is configured and active, or a filter that is available in the list of filters processed by the packet capture process. A manager is restricted to changing the state of an entry in the following ways: To: valid createRequest underCreation invalid From: valid OK NO OK OK createRequest N/A N/A N/A N/A underCreation OK NO OK OK invalid NO NO NO OK nonExistent NO OK NO OK In the table above, it is not applicable to move the state from the createRequest state to any other state because the manager will never find the variable in that state. The nonExistent state is not a value of the enumeration, rather it means that the entryStatus variable does not exist at all. An agent may allow an entryStatus variable to change state in additional ways, so long as the semantics of the states are followed. This allowance is made to ease the implementation of the agent and is made despite the fact that managers should never exercise these additional state transitions. · Integer32
The status of this ringStationControl entry. If this object is not equal to valid(1), all associated entries in the ringStationTable shall be deleted by the agent.
1.3.6.1.2.1.16.10.2
Index: ringStationIfIndex · ringStationMacAddress
A list of ring station entries. An entry will exist for each station that is now or has previously been detected as physically present on this ring.
1.3.6.1.2.1.16.10.2.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF-MIB [17].
1.3.6.1.2.1.16.10.2.1.2
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The physical address of this station.
1.3.6.1.2.1.16.10.2.1.3
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The physical address of last known NAUN of this station.
1.3.6.1.2.1.16.10.2.1.4
INTEGER1 = active2 = inactive3 = forcedRemoval · Integer32
The status of this station on the ring. A value of active(1) indicates the station is actively participating in ring poll. A value of inactive(2) indicates the station is not participating in ring poll and a value of forcedRemoval(3) indicates the station was forced off the ring by a network management operation.
1.3.6.1.2.1.16.10.2.1.5
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time this station last entered the ring. If the time is unknown, this value shall be zero.
1.3.6.1.2.1.16.10.2.1.6
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time the probe detected that this station last exited the ring. If the time is unknown, this value shall be zero.
1.3.6.1.2.1.16.10.2.1.7
Counter32
The number of times this station experienced a duplicate address error.
1.3.6.1.2.1.16.10.2.1.8
Counter32
The total number of line errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.9
Counter32
The total number of line errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
1.3.6.1.2.1.16.10.2.1.10
Counter32
The total number of adapter internal errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.11
Counter32
The total number of burst errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.12
Counter32
The total number of burst errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
1.3.6.1.2.1.16.10.2.1.13
Counter32
The total number of AC (Address Copied) errors reported in error reporting packets sent by the nearest active downstream neighbor of this station and detected by the probe.
1.3.6.1.2.1.16.10.2.1.14
Counter32
The total number of abort delimiters reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.15
Counter32
The total number of lost frame errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.16
Counter32
The total number of receive congestion errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.17
Counter32
The total number of frame copied errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.18
Counter32
The total number of frequency errors reported by this station in error reporting packets detected by the probe.
1.3.6.1.2.1.16.10.2.1.19
Counter32
The total number of token errors reported by this station in error reporting frames detected by the probe.
1.3.6.1.2.1.16.10.2.1.20
Counter32
The total number of beacon frames sent by this station and detected by the probe.
1.3.6.1.2.1.16.10.2.1.21
Counter32
The total number of beacon frames detected by the probe that name this station as the NAUN.
1.3.6.1.2.1.16.10.2.1.22
Counter32
The number of times the probe detected this station inserting onto the ring.
1.3.6.1.2.1.16.10.3
Index: ringStationOrderIfIndex · ringStationOrderOrderIndex
A list of ring station entries for stations in the ring poll, ordered by their ring-order.
1.3.6.1.2.1.16.10.3.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF-MIB [17].
1.3.6.1.2.1.16.10.3.1.2
Integer32 (1..2147483647)
This index denotes the location of this station with respect to other stations on the ring. This index is one more than the number of hops downstream that this station is from the rmon probe. The rmon probe itself gets the value one.
1.3.6.1.2.1.16.10.3.1.3
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The physical address of this station.
1.3.6.1.2.1.16.10.4
Index: ringStationConfigControlIfIndex · ringStationConfigControlMacAddress
A list of ring station configuration control entries.
1.3.6.1.2.1.16.10.4.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF-MIB [17].
1.3.6.1.2.1.16.10.4.1.2
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The physical address of this station.
1.3.6.1.2.1.16.10.4.1.3
INTEGER1 = stable2 = removing · Integer32
Setting this object to `removing(2)' causes a Remove Station MAC frame to be sent. The agent will set this object to `stable(1)' after processing the request.
1.3.6.1.2.1.16.10.4.1.4
INTEGER1 = stable2 = updating · Integer32
Setting this object to `updating(2)' causes the configuration information associate with this entry to be updated. The agent will set this object to `stable(1)' after processing the request.
1.3.6.1.2.1.16.10.5
Index: ringStationConfigIfIndex · ringStationConfigMacAddress
A list of configuration entries for stations on a ring monitored by this probe.
1.3.6.1.2.1.16.10.5.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device on which this station was detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF-MIB [17].
1.3.6.1.2.1.16.10.5.1.2
MacAddressRepresents an 802 MAC address represented in the `canonical' order defined by IEEE 802.1a, i.e., as if it were transmitted least significant bit first, even though 802.5 (in contrast to other 802.x protocols) requires MAC addresses to be transmitted most significant bit first. SIZE (6) · OCTET STRING · hint 1x:
The physical address of this station.
1.3.6.1.2.1.16.10.5.1.3
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime at the time this configuration information was last updated (completely).
1.3.6.1.2.1.16.10.5.1.4
OCTET STRING SIZE (4)
The assigned physical location of this station.
1.3.6.1.2.1.16.10.5.1.5
OCTET STRING SIZE (10)
The microcode EC level of this station.
1.3.6.1.2.1.16.10.5.1.6
OCTET STRING SIZE (4)
The low-order 4 octets of the group address recognized by this station.
1.3.6.1.2.1.16.10.5.1.7
OCTET STRING SIZE (4)
the functional addresses recognized by this station.
1.3.6.1.2.1.16.10.6
Index: sourceRoutingStatsIfIndex
A list of source routing statistics entries.
1.3.6.1.2.1.16.10.6.1.1
InterfaceIndexA unique value, greater than zero, for each interface or interface sub-layer in the managed system. It is recommended that values are assigned contiguously starting from 1. The value for each interface sub-layer must remain constant at least from one re-initialization of the entity's network management system to the next re-initialization. (1..2147483647) · Integer32 · hint d
The value of this object uniquely identifies the interface on this remote network monitoring device on which source routing statistics will be detected. The interface identified by a particular value of this object is the same interface as identified by the same value of the ifIndex object, defined in IF-MIB [17].
1.3.6.1.2.1.16.10.6.1.2
Integer32
The ring number of the ring monitored by this entry. When any object in this entry is created, the probe will attempt to discover the ring number. Only after the ring number is discovered will this object be created. After creating an object in this entry, the management station should poll this object to detect when it is created. Only after this object is created can the management station set the sourceRoutingStatsStatus entry to valid(1).
1.3.6.1.2.1.16.10.6.1.3
Counter32
The count of frames sent into this ring from another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.4
Counter32
The count of frames sent from this ring to another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.5
Counter32
The count of frames sent from another ring, through this ring, to another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.6
Counter32
The total number of good frames received that were All Routes Broadcast.
1.3.6.1.2.1.16.10.6.1.7
Counter32
The total number of good frames received that were Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.8
Counter32
The count of octets in good frames sent into this ring from another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.9
Counter32
The count of octets in good frames sent from this ring to another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.10
Counter32
The count of octets in good frames sent another ring, through this ring, to another ring that were not All Routes Broadcasts or Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.11
Counter32
The total number of octets in good frames received that were All Routes Broadcast.
1.3.6.1.2.1.16.10.6.1.12
Counter32
The total number of octets in good frames received that were Single Route Broadcast.
1.3.6.1.2.1.16.10.6.1.13
Counter32
The total number of frames received which had no RIF field (or had a RIF field that only included the local ring's number) and were not All Route Broadcast Frames or Single Route Broadcast Frames.
1.3.6.1.2.1.16.10.6.1.14
Counter32
The total number of frames received whose route had 1 hop, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.15
Counter32
The total number of frames received whose route had 2 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.16
Counter32
The total number of frames received whose route had 3 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.17
Counter32
The total number of frames received whose route had 4 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.18
Counter32
The total number of frames received whose route had 5 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.19
Counter32
The total number of frames received whose route had 6 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.20
Counter32
The total number of frames received whose route had 7 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.21
Counter32
The total number of frames received whose route had 8 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.22
Counter32
The total number of frames received whose route had more than 8 hops, were not All Route Broadcast Frames or Single Route Broadcast Frames, and whose source or destination were on this ring (i.e. frames that had a RIF field and had this ring number in the first or last entry of the RIF field).
1.3.6.1.2.1.16.10.6.1.23
OwnerStringThis data type is used to model an administratively assigned name of the owner of a resource. Implementations must accept values composed of well-formed NVT ASCII sequences. In addition, implementations should accept values composed of well-formed UTF-8 sequences. It is suggested that this name contain one or more of the following: IP address, management station name, network manager's name, location, or phone number. In some cases the agent itself will be the owner of an entry. In these cases, this string shall be set to a string starting with 'monitor'. SNMP access control is articulated entirely in terms of the contents of MIB views; access to a particular SNMP object instance depends only upon its presence or absence in a particular MIB view and never upon its value or the value of related object instances. Thus, objects of this type afford resolution of resource contention only among cooperating managers; they realize no access control function with respect to uncooperative parties. SIZE (0..127) · OCTET STRING
The entity that configured this entry and is therefore using the resources assigned to it.
1.3.6.1.2.1.16.10.6.1.24
EntryStatus1 = valid2 = createRequest3 = underCreation4 = invalidThe status of a table entry. Setting this object to the value invalid(4) has the effect of invalidating the corresponding entry. That is, it effectively disassociates the mapping identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries currently not in use. Proper interpretation of such entries requires examination of the relevant EntryStatus object. An existing instance of this object cannot be set to createRequest(2). This object may only be set to createRequest(2) when this instance is created. When this object is created, the agent may wish to create supplemental object instances with default values to complete a conceptual row in this table. Because the creation of these default objects is entirely at the option of the agent, the manager must not assume that any will be created, but may make use of any that are created. Immediately after completing the create operation, the agent must set this object to underCreation(3). When in the underCreation(3) state, an entry is allowed to exist in a possibly incomplete, possibly inconsistent state, usually to allow it to be modified in multiple PDUs. When in this state, an entry is not fully active. Entries shall exist in the underCreation(3) state until the management station is finished configuring the entry and sets this object to valid(1) or aborts, setting this object to invalid(4). If the agent determines that an entry has been in the underCreation(3) state for an abnormally long time, it may decide that the management station has crashed. If the agent makes this decision, it may set this object to invalid(4) to reclaim the entry. A prudent agent will understand that the management station may need to wait for human input and will allow for that possibility in its determination of this abnormally long period. An entry in the valid(1) state is fully configured and consistent and fully represents the configuration or operation such a row is intended to represent. For example, it could be a statistical function that is configured and active, or a filter that is available in the list of filters processed by the packet capture process. A manager is restricted to changing the state of an entry in the following ways: To: valid createRequest underCreation invalid From: valid OK NO OK OK createRequest N/A N/A N/A N/A underCreation OK NO OK OK invalid NO NO NO OK nonExistent NO OK NO OK In the table above, it is not applicable to move the state from the createRequest state to any other state because the manager will never find the variable in that state. The nonExistent state is not a value of the enumeration, rather it means that the entryStatus variable does not exist at all. An agent may allow an entryStatus variable to change state in additional ways, so long as the semantics of the states are followed. This allowance is made to ease the implementation of the agent and is made despite the fact that managers should never exercise these additional state transitions. · Integer32
The status of this sourceRoutingStats entry.