Each ring builder has two external trunk connections by which
a ring builder may be connected to other token ring devices
capable of supporting a backup path, e.g. another ring
builder. Each external connection attaches to a dual ring
cable. One of the rings is used to carry traffic in a fault
free network. The other ring is used as a backup. If an
error should be detected on the main ring then suitable
stations can wrap the active path onto the backup. The ring
builder is such a device. The fault recovery is handled at
the ring in and ring out ports.
Each of these two connections may be placed in one of the
following states:
openRing (1):-
This external connection is configured to be
connected to the external ring.
NOTE: In this mode if there is no external ring
the ring will be broken.
wrapRing (2):-
This external connection is configured to be
isolated from the remote ring such that the
external ring in/out port is looped from main
to backup ring.
failSafe (3):-
In this mode the ring builder monitors the ring
in signal for a phantom voltage. If this is
present then the external connection is placed
into OPEN state. If the phantom voltage is not
present then the external connection is placed
in WRAP state. In this mode the actual state of
the connection can be obtained by reading the
state parameter.
Note that not all devices support the generation of a
phantom voltage and so the failSafe mode may not be
appropriate.
Parsed from file lbhub-msh.mib.txt
Company: None
Module: LBHUB-MSH-MIB
Each ring builder has two external trunk connections by which
a ring builder may be connected to other token ring devices
capable of supporting a backup path, e.g. another ring
builder. Each external connection attaches to a dual ring
cable. One of the rings is used to carry traffic in a fault
free network. The other ring is used as a backup. If an
error should be detected on the main ring then suitable
stations can wrap the active path onto the backup. The ring
builder is such a device. The fault recovery is handled at
the ring in and ring out ports.
Each of these two connections may be placed in one of the
following states:
openRing (1):-
This external connection is configured to be
connected to the external ring.
NOTE: In this mode if there is no external ring
the ring will be broken.
wrapRing (2):-
This external connection is configured to be
isolated from the remote ring such that the
external ring in/out port is looped from main
to backup ring.
failSafe (3):-
In this mode the ring builder monitors the ring
in signal for a phantom voltage. If this is
present then the external connection is placed
into OPEN state. If the phantom voltage is not
present then the external connection is placed
in WRAP state. In this mode the actual state of
the connection can be obtained by reading the
state parameter.
Note that not all devices support the generation of a
phantom voltage and so the failSafe mode may not be
appropriate.
Parsed from file LBHUB-MSH-MIB.mib
Module: LBHUB-MSH-MIB
Vendor: 3Com
Module: LBHUB-MSH-MIB (lbhub-msh.mib)
Type: TABULAR
Access: read-write
Syntax: INTEGER
Automatically extracted from www.mibdepot.com
rbRingInMode OBJECT-TYPE SYNTAX INTEGER { openRing (1), wrapRing (2), failSafe (3) } ACCESS read-write STATUS mandatory DESCRIPTION "Each ring builder has two external trunk connections by which a ring builder may be connected to other token ring devices capable of supporting a backup path, e.g. another ring builder. Each external connection attaches to a dual ring cable. One of the rings is used to carry traffic in a fault free network. The other ring is used as a backup. If an error should be detected on the main ring then suitable stations can wrap the active path onto the backup. The ring builder is such a device. The fault recovery is handled at the ring in and ring out ports. Each of these two connections may be placed in one of the following states: openRing (1):- This external connection is configured to be connected to the external ring. NOTE: In this mode if there is no external ring the ring will be broken. wrapRing (2):- This external connection is configured to be isolated from the remote ring such that the external ring in/out port is looped from main to backup ring. failSafe (3):- In this mode the ring builder monitors the ring in signal for a phantom voltage. If this is present then the external connection is placed into OPEN state. If the phantom voltage is not present then the external connection is placed in WRAP state. In this mode the actual state of the connection can be obtained by reading the state parameter. Note that not all devices support the generation of a phantom voltage and so the failSafe mode may not be appropriate." ::= { ringBuilderTableEntry 4 }
rbRingInMode OBJECT-TYPE SYNTAX INTEGER { openRing (1), wrapRing (2), failSafe (3) } ACCESS read-write STATUS mandatory DESCRIPTION "Each ring builder has two external trunk connections by which a ring builder may be connected to other token ring devices capable of supporting a backup path, e.g. another ring builder. Each external connection attaches to a dual ring cable. One of the rings is used to carry traffic in a fault free network. The other ring is used as a backup. If an error should be detected on the main ring then suitable stations can wrap the active path onto the backup. The ring builder is such a device. The fault recovery is handled at the ring in and ring out ports. Each of these two connections may be placed in one of the following states: openRing (1):- This external connection is configured to be connected to the external ring. NOTE: In this mode if there is no external ring the ring will be broken. wrapRing (2):- This external connection is configured to be isolated from the remote ring such that the external ring in/out port is looped from main to backup ring. failSafe (3):- In this mode the ring builder monitors the ring in signal for a phantom voltage. If this is present then the external connection is placed into OPEN state. If the phantom voltage is not present then the external connection is placed in WRAP state. In this mode the actual state of the connection can be obtained by reading the state parameter. Note that not all devices support the generation of a phantom voltage and so the failSafe mode may not be appropriate." ::= { ringBuilderTableEntry 4 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.43.14.3.1.1.1 | rbServiceId | 0 | 0 | This identifies one of potentially several ring builders within the chassis. |
| 1.3.6.1.4.1.43.14.3.1.1.3 | rbRingInMedia | 0 | 0 | This object identifies the physical media to which the Ring In port of the Ring Builder is, or could be, connected. |
| 1.3.6.1.4.1.43.14.3.1.1.5 | rbRingInState | 0 | 0 | Each ring builder has two external trunk connections by which a ring builder may be connected to other token ring devices capable… |
| 1.3.6.1.4.1.43.14.3.1.1.6 | rbRingOutMedia | 0 | 0 | This object identifies the physical media to which the Ring Out port of the Ring Builder is, or could be, connected. |
| 1.3.6.1.4.1.43.14.3.1.1.7 | rbRingOutMode | 0 | 0 | Each ring builder has two external trunk connections by which a ring builder may be connected to other token ring devices capable… |
| 1.3.6.1.4.1.43.14.3.1.1.8 | rbRingOutState | 0 | 0 | Each ring builder has two external trunk connections by which a ring builder may be connected to other token ring devices capable… |
| 1.3.6.1.4.1.43.14.3.1.1.9 | rbMode | 0 | 0 | As well as providing control over network connection at the ring in and ring out ports, the Ringbuilder has three modes that also… |
| 1.3.6.1.4.1.43.14.3.1.1.10 | rbTest | 0 | 0 | Setting this object to test(2) causes the Ringbuilder to execute a test by transmitting a frame to itself and checking that it is… |
| 1.3.6.1.4.1.43.14.3.1.1.11 | rbDRIState | 0 | 0 | Distributive Recovery Interface ( DRI ) allows the Active MAU to determine which of its stations are beaconing or causing problem… |