S5-ETH-MULTISEG-TOPOLOGY-MIB: View SNMP OID List / Download MIB

5000 Ethernet Multi-segment MIB Copyright 1993-2004 Nortel Networks, Inc. All rights reserved. This Nortel Networks SNMP Management Information Base Specification (Specification) embodies Nortel Networks' confidential and proprietary intellectual property. Nortel Networks retains all title and ownership in the Specification, including any revisions. This Specification is supplied 'AS IS,' and Nortel Networks makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.

An IP address of the agent. This is used to fill in the IP address field of transmitted SONMP packets. The agent should be reachable through this IP address.

Indicates if the agent is participating in multi-segment topology. The values are: topOn(1)....topology is on topOff(2)...topology is off When the value is topOff(2) the status of topology table entries is undefined. However, the agent should make its best attempt when the value is changed to topOff(2) to remove all existing instances of topology MIB objects. The agent must save the setting of this object in nonvolatile memory (i.e., save across reboots). Enumeration: 'topOff': 2, 'topOn': 1.

The value of sysUpTime the last time an entry in the NMM topology table was added, deleted, or modified. If the NMM topology table has not changed since cold/warm start of the agent, then the value is zero.

The value of sysUpTime the last time an entry in the bridge topology table was added, deleted, or modified. If the bridge topology table has not changed since cold/warm start of the agent, then the value is zero.

The maximum number of entries in the NMM topology table.

The current number of entries in the NMM topology table.

The maximum number of entries in the bridge topology table.

The current number of entries in the bridge topology table.

A table of topology information from each topology agent that sends out NMM topology messages, and that has been heard by the reporting topology agent. The number of entries is determined by the number of distinct topology messages received. A topology message is identified by a combination of the IP address and segment-identifier contained in the message, and the slot-port on which it is received. Entries in the table are created by reception of a 'new' NMM topology message. An entry is removed from the table after no messages are received from the corresponding topology agent in the required time interval. NOTE: there is an entry for the reporting agent with the values of slot and port set to zero.

A row in the NMM topology table. Entries in the table can not be created or deleted via SNMP.

The slot on which the topology message was received. NOTE: There is an artificial 'row' for the reporting agent with slot and port equal to zero. NOTE: Non-modular devices that do not have multiple slots should set this value to 1.

The port on which the topology message was received. NOTE: there is an artificial 'row' for the reporting agent with slot and port equal to zero.

The IP address of the sender of the topology message.

The 'segment identifier' of the segment from which the remote agent sent the topology message. The value is extracted from the received topology message. Different devices may use different methods for representing the segment identifier. For example, system 5000 NMMs that run multi-segment autotopology use the SrcIndx of the segment as the segment identifier; switches use a computed a value equal to '(256 * s) + p' where 's' is the board, card or slot number and 'p' is the port number on and as seen by the switch sending the topology message; system 3000 NMMs use the lower three bytes of the MAC address of the NMM as the segment identifier. In any case, the 'segment identifier' uniquely identifies the network segment in the remote device from which the topology message was sent.

The MAC address of the sender of the topology message.

The chassis type of the device that sent the topology message.

The backplane type of the device that sent the topology message.

Indicates if the sender of the topology message is on the same Ethernet segment (i.e., NOT across a bridge) as the reporting agent. Enumeration: 'false': 2, 'true': 1.

The current state of sender of the topology message. The values are: topChanged(1)...topology information has recently changed heartbeat(2)....topology information unchanged new(3)..........sending agent is in new state. Enumeration: 'topChanged': 1, 'new': 3, 'heartbeat': 2.

The current size of a 'row' in the table s5EnMsTopNmmEosTable. This allows applications to be able to break apart 'rows' in the table.

A table of encoded octet strings of entries in table s5EnMsTopNmmTable. The number of entries is determined by packing of 'rows' from s5EnMsTopNmmTable.

A row in the table of encoded octet strings for table s5EnMsTopNmmTable. Instance returned in Response PDU: On GETs: instance specified is the instance returned. On GET-NEXTs: instance returned is the instance of the last record contained in the octet string. Entries in the table can not be created or deleted via SNMP.

An encoded octet string. On reads it contains an integral number of 'rows' from table s5EnMsTopNmmTable. All 'rows' are the same size which is defined by object s5EnMsTopNmmEosSize.

A table of topology information from each Bridge in the network that is sending bridge topology messages that have been heard by the reporting agent. The number of entries is determined by the number of detected (and active) bridges. Entries in the table are created by reception of a topology message from a 'new' bridge. An entry is removed from the table after no messages are received from the corresponding bridge in the required time interval.

A row in the bridge topology table. Entries in the table can not be created or deleted via SNMP.

The slot on which the topology message was received. NOTE: Non-modular devices that do not have multiple slots should set this value to 1.

The port on which the topology message was received.

The IP address of the bridge that sent the topology message.

The 'Bridge Number' of the bridge that sent the topology message. This is the IEEE 802.1 bridge number.

The MAC Address of the bridge that sent the topology message.

The 'kind of bridge' that sent the topology message. The values are: other(1).....unknown or other type locSyn(2)....local SynOptics bridge remSyn(3)....remote SynOptics bridge kalpana(4)...Kalpana bridge(switch) Enumeration: 'kalpana': 4, 'other': 1, 'localSyn': 2, 'remoteSyn': 3.

The number of ports on the bridge.

The current operational status from the bridge that sent the topology message. The values are: other(1).....unknown or other active(2)....bridge is active standby(3)...bridge is in standby A value of standby(3) means that at least ONE port is in standby mode. A value of active(2) means NO port is in standby mode. Enumeration: 'active': 2, 'standby': 3, 'other': 1.

The port number used by the bridge to send the topology message. This port may or may not be in standby mode.

The type of the port used by the bridge to send the topology message. The values are: other(1)...other or unknown type eth(2).....ethernet tok4(3)....4 Mbit token ring tok16(4)...16 Mbit token ring fddi(5)....fddi t1(6)......t1 Note: These enumerations were done for 'completeness'. No other value than eth(2) should ever be received by an ethernet agent. Enumeration: 'tok4': 3, 'tok16': 4, 't1': 6, 'other': 1, 'eth': 2, 'fddi': 5.

The status of the port used by the bridge to send the topology message. The values are: other(1).....unknown or other active(2)....port is active standby(3)...port is in standby Enumeration: 'active': 2, 'standby': 3, 'other': 1.

The first MAC address of a companion bridge of the bridge that sent the topology message. The value is 00:00:00:00:00:00 for local bridges (since there is no companion bridge) and also when the companion MAC address is unknown for remote bridges.

The second MAC address of a companion bridge of the bridge that sent the topology message. The value is 00:00:00:00:00:00 for local bridges (since there is no companion bridge) and also when the companion MAC address is unknown for remote bridges.

The current size of a 'row' in the table s5EnMsTopBdgEosTable. This allows applications to be able to break apart 'rows' in the table.

A table of encoded octet strings of entries in table s5EnMsTopBdgTable. The number of entries is determined by packing of 'rows' from s5EnMsTopBdgTable.

A row in the table of encoded octet strings for table s5EnMsTopBdgTable. Instance returned in Response PDU: On GETs: instance specified is the instance returned. On GET-NEXTs: instance returned is the instance of the last record contained in the octet string. Entries in the table can not be created or deleted via SNMP.

An encoded octet string. On reads it contains an integral number of 'rows' from table s5EnMsTopBdgTable. All 'rows' are the same size which is defined by object s5EnMsTopBdgEosSize.

A table describing the source MAC addresses that the agent uses to transmit topology messages on different segments in the device. The MAC addresses are preallocated and remain unchanged for the agent. However, the mapping between a MAC address and segment may change, since it can depend on the current physical and/or logical configuration of the device. Implementation of this group is required for those devices that use different source MAC addresses to transmit topology messages on different segments. Implementation of this group is optional otherwise.

A row in the table of MAC address-to-segment mappings. Entries in the table can not be created or deleted via SNMP.

The MAC address used to transmit topology messages.

The 'segment-identifier' of the segment on which topology messages were transmitted.

The value of sysUpTime when an entry in the table s5EnMsTopSrcMacAddrTable was last changed. If no changes have been done since cold/warm start of the agent, then the value is zero.

A table of topology statuses for each port on the unit. This provides a way to make different topology settings for each port, instead of having global topology settings for the entire unit

an entry in the s5EnMsTopPortTable table. There is one such entry for every port

Indicates port on which to configure topology.

Indicates if the agent is participating in multi-segment topology on this port. The values are: topActive(1)....topology mode is active topPassthru(2)...topology mode is passive (transparent) When the value is topActive, the agent sends out topology packets and also interprets any topology packets received and updates the topology table accordingly. When the value is topPassthru(2) the unit does not generate and send out topology packets and forwards whatever topology packets it receives. Enumeration: 'topPassthr': 2, 'topActive': 1.