NRC-MultiGate: View SNMP OID List / Download MIB

The MAC address used by this bridge when it must be referred to in a unique fashion. It is recommended that this be the numerically smallest MAC address of all ports that belong to this bridge. However it is only required to be unique. When concatenated with dot1dStpPriority a unique BridgeIdentifier is formed which is used in the Spanning Tree Protocol.

The number of ports controlled by this bridging entity.

Indicates what type of bridging this bridge can perform. If a bridge is actually performing a certain type of bridging this will be indicated by entries in the port table for the given type. Enumeration: 'unknown': 1, 'transparent-only': 2, 'srt': 4, 'sourceroute-only': 3.

A table that contains generic information about every port that is associated with this bridge. Transparent, source-route, and srt ports are included.

A list of information for each port of the bridge.

The port number of the port for which this entry contains bridge management information.

The value of the instance of the ifIndex object, defined in [4,6], for the interface corresponding to this port.

For a port which (potentially) has the same value of dot1dBasePortIfIndex as another port on the same bridge, this object contains the name of an object instance unique to this port. For example, in the case where multiple ports correspond one- to-one with multiple X.25 virtual circuits, this value might identify an (e.g., the first) object instance associated with the X.25 virtual circuit corresponding to this port. For a port which has a unique value of dot1dBasePortIfIndex, this object can have the value { 0 0 }.

The number of frames discarded by this port due to excessive transit delay through the bridge. It is incremented by both transparent and source route bridges.

The number of frames discarded by this port due to an excessive size. It is incremented by both transparent and source route bridges.

The total number of Forwarding Database entries, which have been or would have been learnt, but have been discarded due to a lack of space to store them in the Forwarding Database. If this counter is increasing, it indicates that the Forwarding Database is regularly becoming full (a condition which has unpleasant performance effects on the subnetwork). If this counter has a significant value but is not presently increasing, it indicates that the problem has been occurring but is not persistent.

The timeout period in seconds for aging out dynamically learned forwarding information.

A table that contains information about unicast entries for which the bridge has forwarding and/or filtering information. This information is used by the transparent bridging function in determining how to propagate a received frame.

Information about a specific unicast MAC address for which the bridge has some forwarding and/or filtering information.

A unicast MAC address for which the bridge has forwarding and/or filtering information.

Either the value '0', or the port number of the port on which a frame having a source address equal to the value of the corresponding instance of dot1dTpFdbAddress has been seen. A value of '0' indicates that the port number has not been learned but that the bridge does have some forwarding/filtering information about this address (e.g. in the dot1dStaticTable). Implementors are encouraged to assign the port value to this object whenever it is learned even for addresses for which the corresponding value of dot1dTpFdbStatus is not learned(3).

The status of this entry. The meanings of the values are: other(1) : none of the following. This would include the case where some other MIB object (not the corresponding instance of dot1dTpFdbPort, nor an entry in the dot1dStaticTable) is being used to determine if and how frames addressed to the value of the corresponding instance of dot1dTpFdbAddress are being forwarded. invalid(2) : this entry is not longer valid (e.g., it was learned but has since aged-out), but has not yet been flushed from the table. learned(3) : the value of the corresponding instance of dot1dTpFdbPort was learned, and is being used. self(4) : the value of the corresponding instance of dot1dTpFdbAddress represents one of the bridge's addresses. The corresponding instance of dot1dTpFdbPort indicates which of the bridge's ports has this address. mgmt(5) : the value of the corresponding instance of dot1dTpFdbAddress is also the value of an existing instance of dot1dStaticAddress. Enumeration: 'learned': 3, 'other': 1, 'self': 4, 'invalid': 2, 'mgmt': 5.

A table that contains information about every port that is associated with this transparent bridge.

A list of information for each port of a transparent bridge.

The port number of the port for which this entry contains Transparent bridging management information.

The maximum size of the INFO (non-MAC) field that this port will receive or transmit.

The number of frames that have been received by this port from its segment. Note that a frame received on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function.

The number of frames that have been transmitted by this port to its segment. Note that a frame transmitted on the interface corresponding to this port is only counted by this object if and only if it is for a protocol being processed by the local bridging function.

Count of valid frames received which were discarded (i.e., filtered) by the Forwarding Process.

The rptrGroupCapacity is the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range from 1 to rptrGroupCapacity. Some groups may not be present in the repeater, in which case the actual number of groups present will be less than rptrGroupCapacity. The number of groups present will never be greater than rptrGroupCapacity. Note: In practice, this will generally be the number of field-replaceable units (i.e., modules, cards, or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to numbers marked on the physical enclosure.

The rptrOperStatus object indicates the operational state of the repeater. The rptrHealthText object may be consulted for more specific information about the state of the repeater's health. In the case of multiple kinds of failures (e.g., repeater failure and port failure), the value of this attribute shall reflect the highest priority failure in the following order: rptrFailure(3) groupFailure(4) portFailure(5) generalFailure(6). Enumeration: 'generalFailure': 6, 'ok': 2, 'groupFailure': 4, 'portFailure': 5, 'other': 1, 'rptrFailure': 3.

The health text object is a text string that provides information relevant to the operational state of the repeater. Agents may use this string to provide detailed information on current failures, including how they were detected, and/or instructions for problem resolution. The contents are agent-specific.

Setting this object to reset(2) causes a transition to the START state of Fig 9-2 in section 9 [IEEE 802.3 Std]. Setting this object to noReset(1) has no effect. The agent will always return the value noReset(1) when this object is read. This action does not reset the management counters defined in this document nor does it affect the portAdminStatus parameters. Included in this action is the execution of a disruptive Self-Test with the following characteristics: a) The nature of the tests is not specified. b) The test resets the repeater but without affecting management information about the repeater. c) The test does not inject packets onto any segment. d) Packets received during the test may or may not be transferred. e) The test does not interfere with management functions. As a result of this action a rptrResetEvent trap should be sent. Enumeration: 'reset': 2, 'noReset': 1.

Setting this object to selfTest(2) causes the repeater to perform a agent-specific, non- disruptive self-test that has the following characteristics: a) The nature of the tests is not specified. b) The test does not change the state of the repeater or management information about the repeater. c) The test does not inject packets onto any segment. d) The test does not prevent the relay of any packets. e) The test does not interfere with management functions. After performing this test the agent will update the repeater health information and send a rptrHealth trap. Setting this object to noSelfTest(1) has no effect. The agent will always return the value noSelfTest(1) when this object is read. Enumeration: 'noSelfTest': 1, 'selfTest': 2.

This object returns the total number of ports in the repeater whose current state meets all three of the following criteria: rptrPortOperStatus does not have the value notPresent(3), rptrPortAdminStatus is enabled(1), and rptrPortAutoPartitionState is autoPartitioned(2).

Table of descriptive and status information about the groups of ports.

An entry in the table, containing information about a single group of ports.

This object identifies the group within the repeater for which this entry contains information. This value is never greater than rptrGroupCapacity.

A textual description of the group. This value should include the full name and version identification of the group's hardware type and indicate how the group is differentiated from other groups in the repeater. Plug-in Module, Rev A' or 'Barney Rubble 10BASE-T 4-port SIMM socket Version 2.1' are examples of valid group descriptions. It is mandatory that this only contain printable ASCII characters.

The vendor's authoritative identification of the group. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides a straight-forward and unambiguous means for determining what kind of group is being managed. For example, this object could take the value 1.3.6.1.4.1.4242.1.2.14 if vendor 'Flintstones, Inc.' was assigned the subtree 1.3.6.1.4.1.4242, and had assigned the identifier 1.3.6.1.4.1.4242.1.2.14 to its 'Wilma Flintstone 6-Port FOIRL Plug-in Module.'

An object that indicates the operational status of the group. A status of notPresent(4) indicates that the group is temporarily or permanently physically and/or logically not a part of the repeater. It is an implementation-specific matter as to whether the agent effectively removes notPresent entries from the table. A status of operational(2) indicates that the group is functioning, and a status of malfunctioning(3) indicates that the group is malfunctioning in some way. Enumeration: 'underTest': 5, 'malfunctioning': 3, 'resetInProgress': 6, 'operational': 2, 'other': 1, 'notPresent': 4.

An object that contains the value of sysUpTime at the time that the value of the rptrGroupOperStatus object for this group last changed. A value of zero indicates that the group's oper status has not changed since the agent last restarted.

The rptrGroupPortCapacity is the number of ports that can be contained within the group. Valid range is 1-1024. Within each group, the ports are uniquely numbered in the range from 1 to rptrGroupPortCapacity. Note: In practice, this will generally be the number of ports on a module, card, or board, and the port numbers will correspond to numbers marked on the physical embodiment.

Table of descriptive and status information about the ports.

An entry in the table, containing information about a single port.

This object identifies the group containing the port for which this entry contains information.

This object identifies the port within the group for which this entry contains information. This value can never be greater than rptrGroupPortCapacity for the associated group.

Setting this object to disabled(2) disables the port. A disabled port neither transmits nor receives. Once disabled, a port must be explicitly enabled to restore operation. A port which is disabled when power is lost or when a reset is exerted shall remain disabled when normal operation resumes. The admin status takes precedence over auto- partition and functionally operates between the auto-partition mechanism and the AUI/PMA. Setting this object to enabled(1) enables the port and exerts a BEGIN on the port's auto-partition state machine. (In effect, when a port is disabled, the value of rptrPortAutoPartitionState for that port is frozen until the port is next enabled. When the port becomes enabled, the rptrPortAutoPartitionState becomes notAutoPartitioned(1), regardless of its pre-disabling state.) Enumeration: 'disabled': 2, 'enabled': 1.

The autoPartitionState flag indicates whether the port is currently partitioned by the repeater's auto-partition protection. The conditions that cause port partitioning are specified in partition state machine in Section 9 [IEEE 802.3 Std]. They are not differentiated here. Enumeration: 'notAutoPartitioned': 1, 'autoPartitioned': 2.

This object indicates the port's operational status. The notPresent(3) status indicates the port is physically removed (note this may or may not be possible depending on the type of port.) The operational(1) status indicates that the port is enabled (see rptrPortAdminStatus) and working, even though it might be auto-partitioned (see rptrPortAutoPartitionState). If this object has the value operational(1) and rptrPortAdminStatus is set to disabled(2), it is expected that this object's value will change to notOperational(2) soon after. Enumeration: 'notPresent': 3, 'notOperational': 2, 'operational': 1.

The value 'enabled' indicates that the HUB should auto partition ports. The value 'disabled' will disable this feature. Enumeration: 'disabled': 2, 'enabled': 1.

The value 'enabled' indicates that the HUB will reconnect an auto partitioned port if the HUB receives a packet from a partitioned port. The value 'disabled' indicates that the HUB will reconnect a partitioned port if there is any traffic to or from the port. Enumeration: 'disabled': 2, 'enabled': 1.

A value of 'enabled' will cause Out Of Window Collisions to be counted along with In Window Collisions (as defined by IEEE 802.3) when determining if the collision count has exceeded hub1CollisionLimit and a port should be auto partitioned. A value of 'disabled' indicates that Out Of Window Collisions should NOT be counted when determining if the collision count has exceeded hub1CollisionLimit and a and a port should be auto partitioned. Enumeration: 'disabled': 2, 'enabled': 1.

A value of 'enabled' will cause the HUB to automatically partition a port where a lack of loopback from the transeiver is detected. A value of 'disabled' will disable this feature. Note: Setting this variable will only effect HUB operation when hub1PortType value equals 'thinNet-10Base2'. For all other hub1PortType values, a value of 'enabled' will have no effect. Enumeration: 'disabled': 2, 'enabled': 1.

If consecutive collisions exceeding the value of this variable are detected on a port, the port will be auto partitioned 31 is the IEEE 802.3 consecutive collision limit. Enumeration: 'high': 63, 'low': 31.

Time to recover carrier. A value of 'short' will use 3 bit times (IEEE 802.3 specification). A value of 'long' will use 5 bit times. Enumeration: 'short': 3, 'long': 5.

A bit mask indicating which error types will cause an increment in the hub1PortEventCount Counter. Each bit has the following significance where each bit is listed from most significant bit of the first octet, to least significant bit of the second octet. High (first) Octet bit 8 - not used - 7 - not used - 6 Out Of Window Collision Count Enable 5 Receive Collision Count Enable 4 Transmit Collision Count Enable 3 - not used - 2 - not used - 1 - not used - Low (second) Octet bit 8 Bad Link Count Enable 7 Partition Count Enable 6 Receive Count Enable 5 Pygmy Packet Enable 4 Non SFD Enable 3 Phase Lock Error Enable 2 Elasticity Buffer Error Enable 1 Jabber Enable When setting the value of this variable, the entire bit mask must be specified and the '-not used-' bits must not be set.

A bit mask indicating which error types will cause corresponding bits in hub1PortEventRecordValue to be set when an error is detected. Each bit has the following significance where bits are listed from most significant bit to least significant bit. bit 8 Bad Link Enable 7 Partition Enable 6 Out Of Window Collision Enable 5 Pygmy Packet Enable 4 Non SFD Enable 3 Phase Lock Error Enable 2 Elasticity Buffer Error Enable 1 Jabber Enable When a particular bit is set, all ports will start to log the specified error in the hub1PortEventRecordValue column of the port's row of the hub1PortTable. For example, if bit 1 (Jabber Enable) is set, then for every port, a detected Jabber Error would cause bit 1 of hub1PortEventRecordValue to be set. When setting the value of this variable, the entire bit mask must be specified. When this mask is set, hub1PortRecordValue for all ports is cleared.

Operational mode of the bridge: bridging Packets are being selectively forwarded according to the internal dynamically built tables. bypass All packets are being repeated between the backbone and the repeater ports. The bridge logic is disabled. After setting this variable the HUB must be reset for the new value to take effect. NOTE: FOIRL Hubs can only have the value 'bypass' for this variable. Attempts to set this variable to 'bridging' on FOIRL hubs will be rejected. Enumeration: 'bridging': 1, 'bypass': 2.

Filtering Mode of the Hub: off The protocol filtering logic is disabled. filter The protocol filtering logic is enabled and packets with the protocol types indicated in hubFilterProtocols will not be forwarded by the bridge. pass The packet filtering logic is enabled and packets with the protocol types indicated in hubFilterProtocols will be the ONLY packets that the bridge will forward. Enumeration: 'filter': 2, 'off': 1, 'pass': 3.

Protocol types to be filtered or passed by the bridging logic. This is a variable length array of between 0 and 16 2-byte entries, each entry containing the 2-byte protocol identifier as seen in the Ethernet header. Attempts to configure this variable with an OCTET STRING of odd length will be rejected.

The baud rate of the console port. Legal values are 9600, 4800, 2400, and 1200.

Setting this object to 'reset' will cause the Hub1 to perform a hardware reset within approximately 5 seconds. Setting this object to 'no-reset will have no effect. The value 'no-reset will be returned whenever this object is retrieved. The primary purpose for including this variable in the Hub1 MIB is to allow SNMP managers to modify the operational mode of the Hub1. Changing the variable hub1BridgingMode has no effect on the Hub until the Hub is reset. Enumeration: 'reset': 2, 'no-reset': 1.

The version of software running on the Hub. On versions of the Hub that support dynamic download, this variable may be set to cause a new version of the software to be loaded the next time the Hub is reset (as in setting the variable hub1Reset or power cycling the unit). The version should be specified in the following format: 'MM.mm.rr' Where MM is the major number, mm is the minor number, and rr is the revision level (for example 2.0.16). On versions of the Hub that do not support dynamic download, setting this variable will result in an error.

A table of port specific information for the NRC HUB 1 product. This table supplements the Repeater MIB Ports Table.

A list of information for every port.

Port number that corresponds to the index value in the Repeater MIB variable rptrPortIndex.

Setting this variable to the value 'force- reconnect' will cause the port to be reconnected assuming that it is currently in the 'Partition' state. If the port is not in a 'Partition' state, setting variable to the value 'force-reconnect' will not have any effect. Setting this variable to anything other than 'force- reconnect will and an undefined effect. When retrieving this variable, the value 'idle' will always be returned. Enumeration: 'idle': 1, 'force-reconnect': 2.

Reason for port being in the partitioned state. If the port is currently not partitioned, this variable will have the value 'not-partitioned'. Enumeration: 'consecutive-collision-limit': 3, 'data-loopback-failure': 5, 'excessive-len-of-collision-limit': 4, 'other': 2, 'process-forced-reconnection': 6, 'not-partitioned': 1.

This variable's meaning varies depending on the type of HUB: 10Base2 Not Applicable. A value of 'unknown' will always be returned. 10BaseT Link Test is being received ('up') or not being received ('down'). Fiber Light Monitoring (LMON) is being detected ('up') or not being detected ('down'). Enumeration: 'down': 3, 'unknown': 1, 'up': 2.

Enabling this variable has the following effect depending on the type of HUB: 10Base2 No Effect 10BaseT Link Test Enabled Fiber LMON Test Enabled Enumeration: 'disabled': 2, 'enabled': 1.

Current port Polarity status. NOTE: a value of 'ok' will always be returned for 10Base2 and FOIRL HUBs Enumeration: 'reversed': 2, 'ok': 1.

Administrator assigned ASCII port name.

Counter of all error events that were detected on this port and at the same time were marked for collection in the hub1EventCounterFlags variable. This is a 16 bit wrapping counter.

Bit Mask that has bits set for each error event that was detected on this port and at the same time was marked for collection in the hub1EventRecordFlags variable. Each bit has the following meaning, where the bits are listed from most significant to least significant: bit 8 Bad Link Count Error 7 Partition Count Error 6 Receive Count Error 5 Pygmy Packet Error 4 Non SFD Error 3 Phase Lock Error 2 Elasticity Buffer Error 1 Jabber Error Each read of this variable causes the variable to be cleared.

The type of port Enumeration: 'thinNet-10Base2': 3, 'twistedPair-10BaseT': 2, 'other': 1, 'fiber-FOIRL': 4.

A table that contains HUB 1 specific supplements to the MIB-II interfaces table.

Entries in the HUB 1 supplement table.

Interface index that corresponds to ifIndex in the interfaces table from MIB II.

The number of alignment errors detected by this interface.

The number of CRC errors detected by this interface.

The number of collisions detected by this interface.

The number of frames discarded by this interface on receive due to an excessive size.

The number of frames discarded by this interface because they were less than the Ethernet minumum frame size of 64 bytes.

The number of frames discarded by this interface due to a LAN Controller FIFO overflow on receive.

The number of frames which had to be retransmitted by this interface due to a LAN Controller FIFO underrun error on transmit.

The number of times Carrier Transmit Sense (CTS) was lost on this interface during frame transmission. The hub will attempt to retransmit frames when transmission fails due to lost CTS.

The number of times Carrier Receive Sense (CRS) was lost on this interface during frame transmission. The hub will attempt to retransmit frames when transmission fails due to lost CRS.

The number of frames discarded by this interface on transmit due to an excessive size.

The number of collisions detected by this interface while attempting to transmit a packet.

Utilization statistics for the last 60 seconds of operation of the bridging logic associated with this interface. The OCTET STRING is a series of 45 16-bit words, each word representing the percentage utilization for a 1.33 second sample period. The first 16 bit word in this series represents the oldest sample. Percentages are calculated by passing each 16 bit sample through the following equation: ((Sample) * 100) / 0xffff to yield the percent channel utilization (a number ranging from 0 to 100).

The last error that caused a Hub failure. A value of zero (0) indicates that there has not been a Hub failure since the novram was last erased. A non-zero value indicates the reason for the last Hub failure. A normal Hub reset or power cycle will not change the value of this variable (it will still indicate the reason for the last known failure.