resTableEntry
A3COM0304-RESILIENTLINKS ·
.1.3.6.1.4.1.43.10.15.1.1
Object
row
mandatory
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.
Context
- MIB
- A3COM0304-RESILIENTLINKS
- OID
.1.3.6.1.4.1.43.10.15.1.1- Type
- row
- Status
- mandatory
- Parent
- resTable
- Table
- resTable
- Children
- 13
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Child Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| resRepeater mandatory 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. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.1 |
| resPairAction mandatory 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 … | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.10 |
| resPairEnable mandatory 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 paramete… | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.11 |
| resPairMode mandatory 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-… | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.12 |
| resPairName mandatory 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… | column | OctetString | .1.3.6.1.4.1.43.10.15.1.1.13 |
| resMainSlot mandatory This is the second key in the index to this table. This is
the slot number of the main port in this pair. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.2 |
| resMainPort mandatory This is the final, key used to index entries in this table.
It is the port number of the main port in the pair. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.3 |
| resMainState mandatory 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 po… | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.4 |
| resStandbySlot mandatory This is the slot number of the standby port for this pair. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.5 |
| resStandbyPort mandatory This is the port number of the standby port. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.6 |
| resStandbyState mandatory 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 po… | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.7 |
| resPairState mandatory 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 seve… | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.8 |
| resPairModificationStatus mandatory 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. | column | Enumeration | .1.3.6.1.4.1.43.10.15.1.1.9 |
Indexes
| Object | Type | Syntax | OID |
|---|---|---|---|
| resRepeater mandatory 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. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.1 |
| resMainSlot mandatory This is the second key in the index to this table. This is
the slot number of the main port in this pair. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.2 |
| resMainPort mandatory This is the final, key used to index entries in this table.
It is the port number of the main port in the pair. | column | Integer32 | .1.3.6.1.4.1.43.10.15.1.1.3 |