A3COM0304-RESILIENTLINKS

All MIBs › A3COM0304-RESILIENTLINKS

Category: VLAN and Bridging, Vendor: 3Com

Description:

Handles configuration of resilient (redundant) links on 3Com switches, enabling automatic failover from a primary to a backup uplink port.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC-1215

TRAP-TYPE

From RFC1155-SMI

enterprises

From RFC1213-MIB

DisplayString

What Is A3COM0304-RESILIENTLINKS?

A3COM0304-RESILIENTLINKS is a legacy 3Com proprietary MIB (enterprise OID 43) implementing Resilient Links, a main/standby port-pair failover feature on 3Com switches/hubs. Its resilience table records the main slot/port and its state, the standby slot/port and its state, overall pair state, pair modification status, a manual pair-action trigger, pair enable, pair mode, and pair name, while a standby-map table associates a standby port back to its main port, and a flush table clears learned state. As a configuration/status MIB it lets an administrator confirm which port is currently active in a resilient main/standby pair and manually trigger a failover. It is deployed on legacy 3Com switches/hubs with Resilient Links. Engineers can download the A3COM0304-RESILIENTLINKS file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in A3COM0304-RESILIENTLINKS. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

main/standby resilient link pair state

Supported Devices

Legacy 3Com switches/hubs (Resilient Links)

Monitoring Examples

An administrator checks resPairState to confirm whether the main or standby port is currently active in a 3Com Resilient Links pair after a cable fault.

OIDs

OID symbolic	OID numeric	Type	Access	Description
a3Com	1.3.6.1.4.1.43
generic	1.3.6.1.4.1.43.10
mrmResilience	1.3.6.1.4.1.43.10.15
INT resFlushTable	1.3.6.1.4.1.43.10.15.3	INTEGER	read-write	This parameter causes all entries in the resilience table to be flushed. Flushing the resilience table does not affect the state of any of the resilient links or ports. Once the table has been flushed , NO resilient links are configured. This parameter is used to ensure that the resilient link table is empty , before new resilient links are configured.
INT resMainPort	1.3.6.1.4.1.43.10.15.1.1.3	INTEGER	read-only	This is the final, key used to index entries in this table. It is the port number of the main port in the pair.
INT resMainSlot	1.3.6.1.4.1.43.10.15.1.1.2	INTEGER	read-only	This is the second key in the index to this table. This is the slot number of the main port in this pair.
INT resMainState	1.3.6.1.4.1.43.10.15.1.1.4	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
INT resPairAction	1.3.6.1.4.1.43.10.15.1.1.10	INTEGER	read-write	This is object allows the state of a resilient pair to be modified. The create(1) operation configures the resilient port from this table entry. The delete(2) operation removes the resilient definitions from this table and terminates operation of resilience on this pair of ports. The togglePort(3) operation allows the current active port to be changed to the other port. This second operation will only take affect if the state of the currently non- active port is ok(2).
INT resPairEnable	1.3.6.1.4.1.43.10.15.1.1.11	INTEGER	read-write	This parameter controls whether the resilient pair is enabled or not. In the disable(2) state , both ports of the resilient pair are disabled. The default value of this parameter is enable(1).
INT resPairMode	1.3.6.1.4.1.43.10.15.1.1.12	INTEGER	read-write	This parameter controls the rules that determine the operation of the resilient pair. The value no-switch-back(1) means that both ports are treated equally. The value switch-back-to-main(2) means that when it is operational, precedence is always given to the main port. If the main port has been stable for 1 minute, then the pair will automatically switch the active port to main. The default value of this parameter is no-switch-back(1).
INT resPairModificationStatus	1.3.6.1.4.1.43.10.15.1.1.9	INTEGER	read-write	This parameter must be set to under-modification(1) before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable.
STR resPairName	1.3.6.1.4.1.43.10.15.1.1.13	DisplayString	read-write	The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's `console'. The default value of this parameter is a zero length string.
INT resPairState	1.3.6.1.4.1.43.10.15.1.1.8	INTEGER	read-only	Each row in the table is in one of two states, invalid(1) or operational(2). If the state is invalid(1), the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the device configuration. If the parameters in the row are all valid then the pair becomes operational(2).
INT resRepeater	1.3.6.1.4.1.43.10.15.1.1.1	INTEGER	read-only	A resilient pair must be attached to one of the repeaters in the chassis. This is part of the index value required to access this table.
NTF resResilienceSwitch	1.3.6.1.4.1.43.0.43			This trap is generated when a change of state of one of the ports in a resilient pair results in a switch of active port, or when there was no active port and a port has now become active.
INT resSbMainPort	1.3.6.1.4.1.43.10.15.2.1.6	INTEGER	read-only	This is the port number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resSbMainSlot	1.3.6.1.4.1.43.10.15.2.1.5	INTEGER	read-only	This is the slot number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resSbPort	1.3.6.1.4.1.43.10.15.2.1.3	INTEGER	read-only	Third index on this table.
INT resSbRepeater	1.3.6.1.4.1.43.10.15.2.1.1	INTEGER	read-only	The repeater index of the port being accessed. This is the first of three indices on this table.
INT resSbSlot	1.3.6.1.4.1.43.10.15.2.1.2	INTEGER	read-only	Second index on this table.
INT resSbType	1.3.6.1.4.1.43.10.15.2.1.4	INTEGER	read-only	This attribute specifies whether the port indexed is a main or standby port in the resilient pair table. If the port is neither then there will not be a row in this table indexed for that port.
resStandbyMapTable	1.3.6.1.4.1.43.10.15.2		not-accessible
resStandbyMapTableEntry	1.3.6.1.4.1.43.10.15.2.1		not-accessible	This table is read-only. If provides shortcut information to allow for the translation of a port number to a corresponding main port number. This value can then be used to access the main resilience table. Each resilient pair has two entries in this table, one for the main port and one for the standby port. The entry for the main port returns the same port, the entry for the standby port returns the corresponding main port.
INT resStandbyPort	1.3.6.1.4.1.43.10.15.1.1.6	INTEGER	read-write	This is the port number of the standby port.
INT resStandbySlot	1.3.6.1.4.1.43.10.15.1.1.5	INTEGER	read-write	This is the slot number of the standby port for this pair.
INT resStandbyState	1.3.6.1.4.1.43.10.15.1.1.7	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
NTF resStateChange	1.3.6.1.4.1.43.0.44			This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated.
resTable	1.3.6.1.4.1.43.10.15.1		not-accessible
resTableEntry	1.3.6.1.4.1.43.10.15.1.1		not-accessible	An device may be configured to contain a number of 'resilient pairs'. These are to point connections, e.g. UTP, that allow two repeaters/switches to be connected together in a resilient configuration. In such a configuration one of the two ports is nominated the 'main' port while the other is the 'standby' port. One of these two ports is enabled and is the current active port. The other is present in case of failure of the active port. Such a failure is detected by the device and a switch performed. In the case of repeaters, there are a couple of rules that must apply to a resilient pair definition before that definition becomes a valid resilient pair. Firstly both ports must be on the same repeater. Secondly the standby port must be configured to be 'disabled on boot'. That is it must recover from a power failure in a disabled state. This prevents loops in the network. There are two modes of operation. These are defined by the resPairMode object. See that object for a full description. Several tables control the resilient configuration for the device. This is the first. This is the main table and allows the creation and deletion of pairs and provides status control and information. The information in this table is indexed on the repeater number, the slot (or unit) and the port location of the main port. To create a new resilient pair simply write any writeable object indexed on the main port. This will create a new entry in the table which has the state invalid(1) (read resPairState). Having created the row, write to the other parameters specifying valid information. When all the parameters are valid and 'resPairModificationStatus' is set to 'stable(2)', then resPairState will become operational(2). In this state the pair will correctly operate as a resilient pair. If any of the attributes in the table change so that the pair in no linger valid this will be reflected in the resPortState parameter. To delete a resilient pair, write delete(2) to resPairAction.

OID symbolic	OID numeric	Type	Access	Description
a3Com	1.3.6.1.4.1.43
NTF resResilienceSwitch	1.3.6.1.4.1.43.0.43			This trap is generated when a change of state of one of the ports in a resilient pair results in a switch of active port, or when there was no active port and a port has now become active.
NTF resStateChange	1.3.6.1.4.1.43.0.44			This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated.
generic	1.3.6.1.4.1.43.10
mrmResilience	1.3.6.1.4.1.43.10.15
resTable	1.3.6.1.4.1.43.10.15.1		not-accessible
resTableEntry	1.3.6.1.4.1.43.10.15.1.1		not-accessible	An device may be configured to contain a number of 'resilient pairs'. These are to point connections, e.g. UTP, that allow two repeaters/switches to be connected together in a resilient configuration. In such a configuration one of the two ports is nominated the 'main' port while the other is the 'standby' port. One of these two ports is enabled and is the current active port. The other is present in case of failure of the active port. Such a failure is detected by the device and a switch performed. In the case of repeaters, there are a couple of rules that must apply to a resilient pair definition before that definition becomes a valid resilient pair. Firstly both ports must be on the same repeater. Secondly the standby port must be configured to be 'disabled on boot'. That is it must recover from a power failure in a disabled state. This prevents loops in the network. There are two modes of operation. These are defined by the resPairMode object. See that object for a full description. Several tables control the resilient configuration for the device. This is the first. This is the main table and allows the creation and deletion of pairs and provides status control and information. The information in this table is indexed on the repeater number, the slot (or unit) and the port location of the main port. To create a new resilient pair simply write any writeable object indexed on the main port. This will create a new entry in the table which has the state invalid(1) (read resPairState). Having created the row, write to the other parameters specifying valid information. When all the parameters are valid and 'resPairModificationStatus' is set to 'stable(2)', then resPairState will become operational(2). In this state the pair will correctly operate as a resilient pair. If any of the attributes in the table change so that the pair in no linger valid this will be reflected in the resPortState parameter. To delete a resilient pair, write delete(2) to resPairAction.
INT resRepeater	1.3.6.1.4.1.43.10.15.1.1.1	INTEGER	read-only	A resilient pair must be attached to one of the repeaters in the chassis. This is part of the index value required to access this table.
INT resMainSlot	1.3.6.1.4.1.43.10.15.1.1.2	INTEGER	read-only	This is the second key in the index to this table. This is the slot number of the main port in this pair.
INT resMainPort	1.3.6.1.4.1.43.10.15.1.1.3	INTEGER	read-only	This is the final, key used to index entries in this table. It is the port number of the main port in the pair.
INT resMainState	1.3.6.1.4.1.43.10.15.1.1.4	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
INT resStandbySlot	1.3.6.1.4.1.43.10.15.1.1.5	INTEGER	read-write	This is the slot number of the standby port for this pair.
INT resStandbyPort	1.3.6.1.4.1.43.10.15.1.1.6	INTEGER	read-write	This is the port number of the standby port.
INT resStandbyState	1.3.6.1.4.1.43.10.15.1.1.7	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
INT resPairState	1.3.6.1.4.1.43.10.15.1.1.8	INTEGER	read-only	Each row in the table is in one of two states, invalid(1) or operational(2). If the state is invalid(1), the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the device configuration. If the parameters in the row are all valid then the pair becomes operational(2).
INT resPairModificationStatus	1.3.6.1.4.1.43.10.15.1.1.9	INTEGER	read-write	This parameter must be set to under-modification(1) before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable.
INT resPairAction	1.3.6.1.4.1.43.10.15.1.1.10	INTEGER	read-write	This is object allows the state of a resilient pair to be modified. The create(1) operation configures the resilient port from this table entry. The delete(2) operation removes the resilient definitions from this table and terminates operation of resilience on this pair of ports. The togglePort(3) operation allows the current active port to be changed to the other port. This second operation will only take affect if the state of the currently non- active port is ok(2).
INT resPairEnable	1.3.6.1.4.1.43.10.15.1.1.11	INTEGER	read-write	This parameter controls whether the resilient pair is enabled or not. In the disable(2) state , both ports of the resilient pair are disabled. The default value of this parameter is enable(1).
INT resPairMode	1.3.6.1.4.1.43.10.15.1.1.12	INTEGER	read-write	This parameter controls the rules that determine the operation of the resilient pair. The value no-switch-back(1) means that both ports are treated equally. The value switch-back-to-main(2) means that when it is operational, precedence is always given to the main port. If the main port has been stable for 1 minute, then the pair will automatically switch the active port to main. The default value of this parameter is no-switch-back(1).
STR resPairName	1.3.6.1.4.1.43.10.15.1.1.13	DisplayString	read-write	The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's `console'. The default value of this parameter is a zero length string.
resStandbyMapTable	1.3.6.1.4.1.43.10.15.2		not-accessible
resStandbyMapTableEntry	1.3.6.1.4.1.43.10.15.2.1		not-accessible	This table is read-only. If provides shortcut information to allow for the translation of a port number to a corresponding main port number. This value can then be used to access the main resilience table. Each resilient pair has two entries in this table, one for the main port and one for the standby port. The entry for the main port returns the same port, the entry for the standby port returns the corresponding main port.
INT resSbRepeater	1.3.6.1.4.1.43.10.15.2.1.1	INTEGER	read-only	The repeater index of the port being accessed. This is the first of three indices on this table.
INT resSbSlot	1.3.6.1.4.1.43.10.15.2.1.2	INTEGER	read-only	Second index on this table.
INT resSbPort	1.3.6.1.4.1.43.10.15.2.1.3	INTEGER	read-only	Third index on this table.
INT resSbType	1.3.6.1.4.1.43.10.15.2.1.4	INTEGER	read-only	This attribute specifies whether the port indexed is a main or standby port in the resilient pair table. If the port is neither then there will not be a row in this table indexed for that port.
INT resSbMainSlot	1.3.6.1.4.1.43.10.15.2.1.5	INTEGER	read-only	This is the slot number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resSbMainPort	1.3.6.1.4.1.43.10.15.2.1.6	INTEGER	read-only	This is the port number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resFlushTable	1.3.6.1.4.1.43.10.15.3	INTEGER	read-write	This parameter causes all entries in the resilience table to be flushed. Flushing the resilience table does not affect the state of any of the resilient links or ports. Once the table has been flushed , NO resilient links are configured. This parameter is used to ensure that the resilient link table is empty , before new resilient links are configured.

DisplayString (1)
STR resPairName	1.3.6.1.4.1.43.10.15.1.1.13	DisplayString	read-write	The textual name of the interface. The value of this object should be the name of the interface as assigned by the local device and should be suitable for use in commands entered at the device's `console'. The default value of this parameter is a zero length string.
INTEGER (19)
INT resFlushTable	1.3.6.1.4.1.43.10.15.3	INTEGER	read-write	This parameter causes all entries in the resilience table to be flushed. Flushing the resilience table does not affect the state of any of the resilient links or ports. Once the table has been flushed , NO resilient links are configured. This parameter is used to ensure that the resilient link table is empty , before new resilient links are configured.
INT resMainPort	1.3.6.1.4.1.43.10.15.1.1.3	INTEGER	read-only	This is the final, key used to index entries in this table. It is the port number of the main port in the pair.
INT resMainSlot	1.3.6.1.4.1.43.10.15.1.1.2	INTEGER	read-only	This is the second key in the index to this table. This is the slot number of the main port in this pair.
INT resMainState	1.3.6.1.4.1.43.10.15.1.1.4	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
INT resPairAction	1.3.6.1.4.1.43.10.15.1.1.10	INTEGER	read-write	This is object allows the state of a resilient pair to be modified. The create(1) operation configures the resilient port from this table entry. The delete(2) operation removes the resilient definitions from this table and terminates operation of resilience on this pair of ports. The togglePort(3) operation allows the current active port to be changed to the other port. This second operation will only take affect if the state of the currently non- active port is ok(2).
INT resPairEnable	1.3.6.1.4.1.43.10.15.1.1.11	INTEGER	read-write	This parameter controls whether the resilient pair is enabled or not. In the disable(2) state , both ports of the resilient pair are disabled. The default value of this parameter is enable(1).
INT resPairMode	1.3.6.1.4.1.43.10.15.1.1.12	INTEGER	read-write	This parameter controls the rules that determine the operation of the resilient pair. The value no-switch-back(1) means that both ports are treated equally. The value switch-back-to-main(2) means that when it is operational, precedence is always given to the main port. If the main port has been stable for 1 minute, then the pair will automatically switch the active port to main. The default value of this parameter is no-switch-back(1).
INT resPairModificationStatus	1.3.6.1.4.1.43.10.15.1.1.9	INTEGER	read-write	This parameter must be set to under-modification(1) before any changes are made to an existing configuration. Changes are not applied until this parameter is set to stable.
INT resPairState	1.3.6.1.4.1.43.10.15.1.1.8	INTEGER	read-only	Each row in the table is in one of two states, invalid(1) or operational(2). If the state is invalid(1), the resilient pair represented by this row is not active. There are several reasons why this may be the case. Firstly during the row creation process, not all information necessary may have been provided. Secondly an operational pair may become invalid because the resilient pair rules are no longer met because of a change in the device configuration. If the parameters in the row are all valid then the pair becomes operational(2).
INT resRepeater	1.3.6.1.4.1.43.10.15.1.1.1	INTEGER	read-only	A resilient pair must be attached to one of the repeaters in the chassis. This is part of the index value required to access this table.
INT resSbMainPort	1.3.6.1.4.1.43.10.15.2.1.6	INTEGER	read-only	This is the port number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resSbMainSlot	1.3.6.1.4.1.43.10.15.2.1.5	INTEGER	read-only	This is the slot number of the main port for the pair in which the indexed port participates. NOTE if the index port is the main port of a pair (resSbType is 'main') this value will be the same as the index.
INT resSbPort	1.3.6.1.4.1.43.10.15.2.1.3	INTEGER	read-only	Third index on this table.
INT resSbRepeater	1.3.6.1.4.1.43.10.15.2.1.1	INTEGER	read-only	The repeater index of the port being accessed. This is the first of three indices on this table.
INT resSbSlot	1.3.6.1.4.1.43.10.15.2.1.2	INTEGER	read-only	Second index on this table.
INT resSbType	1.3.6.1.4.1.43.10.15.2.1.4	INTEGER	read-only	This attribute specifies whether the port indexed is a main or standby port in the resilient pair table. If the port is neither then there will not be a row in this table indexed for that port.
INT resStandbyPort	1.3.6.1.4.1.43.10.15.1.1.6	INTEGER	read-write	This is the port number of the standby port.
INT resStandbySlot	1.3.6.1.4.1.43.10.15.1.1.5	INTEGER	read-write	This is the slot number of the standby port for this pair.
INT resStandbyState	1.3.6.1.4.1.43.10.15.1.1.7	INTEGER	read-only	Each port in a pair is constantly monitored for signs of failure. Failure information is used to automatically change the active port from main to standby or vice-versa. Each port may be in one of three states. Failed(1) indicates there is a loss of signal on this port. A port in this state cannot be active. Secondly ok(2). This state indicates that the port is capable of carrying traffic but is at the moment acting in the role of backup link. The other port in this pair will be in the Ok-and-active(3) state. Ok-and-active(3) means what it says, this port is capable of carrying traffic and is so doing at the time this parameter has been read.
No type (9)
a3Com	1.3.6.1.4.1.43
generic	1.3.6.1.4.1.43.10
mrmResilience	1.3.6.1.4.1.43.10.15
NTF resResilienceSwitch	1.3.6.1.4.1.43.0.43			This trap is generated when a change of state of one of the ports in a resilient pair results in a switch of active port, or when there was no active port and a port has now become active.
resStandbyMapTable	1.3.6.1.4.1.43.10.15.2		not-accessible
resStandbyMapTableEntry	1.3.6.1.4.1.43.10.15.2.1		not-accessible	This table is read-only. If provides shortcut information to allow for the translation of a port number to a corresponding main port number. This value can then be used to access the main resilience table. Each resilient pair has two entries in this table, one for the main port and one for the standby port. The entry for the main port returns the same port, the entry for the standby port returns the corresponding main port.
NTF resStateChange	1.3.6.1.4.1.43.0.44			This trap is generated when a change of state of one of the ports in a resilient pair does not result in a switch of active port. If such a switch were to occur the resResilienceSwitch would be generated.
resTable	1.3.6.1.4.1.43.10.15.1		not-accessible
resTableEntry	1.3.6.1.4.1.43.10.15.1.1		not-accessible	An device may be configured to contain a number of 'resilient pairs'. These are to point connections, e.g. UTP, that allow two repeaters/switches to be connected together in a resilient configuration. In such a configuration one of the two ports is nominated the 'main' port while the other is the 'standby' port. One of these two ports is enabled and is the current active port. The other is present in case of failure of the active port. Such a failure is detected by the device and a switch performed. In the case of repeaters, there are a couple of rules that must apply to a resilient pair definition before that definition becomes a valid resilient pair. Firstly both ports must be on the same repeater. Secondly the standby port must be configured to be 'disabled on boot'. That is it must recover from a power failure in a disabled state. This prevents loops in the network. There are two modes of operation. These are defined by the resPairMode object. See that object for a full description. Several tables control the resilient configuration for the device. This is the first. This is the main table and allows the creation and deletion of pairs and provides status control and information. The information in this table is indexed on the repeater number, the slot (or unit) and the port location of the main port. To create a new resilient pair simply write any writeable object indexed on the main port. This will create a new entry in the table which has the state invalid(1) (read resPairState). Having created the row, write to the other parameters specifying valid information. When all the parameters are valid and 'resPairModificationStatus' is set to 'stable(2)', then resPairState will become operational(2). In this state the pair will correctly operate as a resilient pair. If any of the attributes in the table change so that the pair in no linger valid this will be reflected in the resPortState parameter. To delete a resilient pair, write delete(2) to resPairAction.

RFC description

Manages resilient (redundant) link configuration on 3Com switches, providing automatic failover between primary and backup uplink ports.

Start monitoring Legacy 3Com switches/hubs with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download A3COM0304-RESILIENTLINKS

This MIB depends on

Related MIBs

What Is A3COM0304-RESILIENTLINKS?

What Can Be Monitored

Supported Devices

Monitoring Examples

RFC description