The auto-partition algorithm protects the network from certain
fault conditions which can halt all LAN communications. A media
short or break, a faulty connector, or faulty or missing media
termination, are examples of such conditions. If a repeater
detects such faults on any of its ports, it isolates the faulty
segment from the network.
A repeater does not respond to input received from an
auto-partitioned port, except to determine if the fault
condition has been removed. A repeater continues to transmit
data to an auto-partitioned port.
Setting this object to standard(1) causes the repeater to
implement the IEEE 802.3 standard auto-partitioning algorithm.
If the repeater detects any of the following conditions on a
given port, this algorithm isolates that port from the network.
1. Excessive length collision
2. Excessive number of consecutive collisions
Setting this object to enhanced(2) causes the repeater to
implement an augmented auto-partitioning algorithm. This option
protects the LAN from a greater range of fault conditions. If
the repeater detects any of the following conditions on a given
port, this algorithm isolates that port from the network.
1. Excessive length collision
2. Excessive number of consecutive collisions
3. No receive activity during transmission (no
carrier loop back)
4. Excessive length input message (jabber)
5. Transmit carrier drop (one or more lapses in the
input message during a single output message
without a collision)
6. Internal detectable port failures
Some implementations may not support setting this object to all
defined enumerated values. A badValue error is returned if an
attempt is made to set this object to an unsupported value.
Note: The state of this object is preserved when the repeater
undergoes a power-up reset.
Parsed from file DECrepeater900.mib.txt
Company: None
Module: DECHUB900-ERPTR-MIB-V3-0
The auto-partition algorithm protects the network from certain
fault conditions which can halt all LAN communications. A media
short or break, a faulty connector, or faulty or missing media
termination, are examples of such conditions. If a repeater
detects such faults on any of its ports, it isolates the faulty
segment from the network.
A repeater does not respond to input received from an
auto-partitioned port, except to determine if the fault
condition has been removed. A repeater continues to transmit
data to an auto-partitioned port.
Setting this object to standard(1) causes the repeater to
implement the IEEE 802.3 standard auto-partitioning algorithm.
If the repeater detects any of the following conditions on a
given port, this algorithm isolates that port from the network.
1. Excessive length collision
2. Excessive number of consecutive collisions
Setting this object to enhanced(2) causes the repeater to
implement an augmented auto-partitioning algorithm. This option
protects the LAN from a greater range of fault conditions. If
the repeater detects any of the following conditions on a given
port, this algorithm isolates that port from the network.
1. Excessive length collision
2. Excessive number of consecutive collisions
3. No receive activity during transmission (no
carrier loop back)
4. Excessive length input message (jabber)
5. Transmit carrier drop (one or more lapses in the
input message during a single output message
without a collision)
6. Internal detectable port failures
Some implementations may not support setting this object to all
defined enumerated values. A badValue error is returned if an
attempt is made to set this object to an unsupported value.
Note: The state of this object is preserved when the repeater
undergoes a power-up reset.
Parsed from file DECHUB900-ERPTR-MIB-V3-0.mib
Module: DECHUB900-ERPTR-MIB-V3-0
Vendor: DEC
Module: DECHUB900-ERPTR-MIB-V3-0
[Automatically extracted from oidview.com]
erptrAutoPartitionAlg OBJECT-TYPE SYNTAX INTEGER { standard(1), enhanced(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The auto-partition algorithm protects the network from certain fault conditions which can halt all LAN communications. A media short or break, a faulty connector, or faulty or missing media termination, are examples of such conditions. If a repeater detects such faults on any of its ports, it isolates the faulty segment from the network. A repeater does not respond to input received from an auto-partitioned port, except to determine if the fault condition has been removed. A repeater continues to transmit data to an auto-partitioned port. Setting this object to standard(1) causes the repeater to implement the IEEE 802.3 standard auto-partitioning algorithm. If the repeater detects any of the following conditions on a given port, this algorithm isolates that port from the network. 1. Excessive length collision 2. Excessive number of consecutive collisions Setting this object to enhanced(2) causes the repeater to implement an augmented auto-partitioning algorithm. This option protects the LAN from a greater range of fault conditions. If the repeater detects any of the following conditions on a given port, this algorithm isolates that port from the network. 1. Excessive length collision 2. Excessive number of consecutive collisions 3. No receive activity during transmission (no carrier loop back) 4. Excessive length input message (jabber) 5. Transmit carrier drop (one or more lapses in the input message during a single output message without a collision) 6. Internal detectable port failures Some implementations may not support setting this object to all defined enumerated values. A badValue error is returned if an attempt is made to set this object to an unsupported value. Note: The state of this object is preserved when the repeater undergoes a power-up reset." REFERENCE "Reference IEEE 802.3 Std, 9.6.6 Auto-Partitioning/Reconnection." ::= { erptrRptrInfo 1 }
erptrAutoPartitionAlg OBJECT-TYPE SYNTAX INTEGER { standard(1), enhanced(2) } ACCESS read-write STATUS mandatory DESCRIPTION "The auto-partition algorithm protects the network from certain fault conditions which can halt all LAN communications. A media short or break, a faulty connector, or faulty or missing media termination, are examples of such conditions. If a repeater detects such faults on any of its ports, it isolates the faulty segment from the network. A repeater does not respond to input received from an auto-partitioned port, except to determine if the fault condition has been removed. A repeater continues to transmit data to an auto-partitioned port. Setting this object to standard(1) causes the repeater to implement the IEEE 802.3 standard auto-partitioning algorithm. If the repeater detects any of the following conditions on a given port, this algorithm isolates that port from the network. 1. Excessive length collision 2. Excessive number of consecutive collisions Setting this object to enhanced(2) causes the repeater to implement an augmented auto-partitioning algorithm. This option protects the LAN from a greater range of fault conditions. If the repeater detects any of the following conditions on a given port, this algorithm isolates that port from the network. 1. Excessive length collision 2. Excessive number of consecutive collisions 3. No receive activity during transmission (no carrier loop back) 4. Excessive length input message (jabber) 5. Transmit carrier drop (one or more lapses in the input message during a single output message without a collision) 6. Internal detectable port failures Some implementations may not support setting this object to all defined enumerated values. A badValue error is returned if an attempt is made to set this object to an unsupported value. Note: The state of this object is preserved when the repeater undergoes a power-up reset." REFERENCE "Reference IEEE 802.3 Std, 9.6.6 Auto-Partitioning/Reconnection." ::= { erptrRptrInfo 1 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.1.0 | erptrAutoPartitionAlg | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.2 | erptrAutoPartitionReconnectAlg | 1 | 1 | The auto-partition reconnection algorithm defines the criteria for determining that a malfunction on an auto-partitioned port has… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.3 | erptrJamBits | 1 | 1 | When a repeater detects a collision on any of the ports to which it is transmitting, it transmits a jam signal to all of the port… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.4 | erptrHealthTextChanges | 1 | 1 | erptrHealthtextChanges |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.5 | erptrTotalPortEvents | 1 | 1 | The total number of times any port in the repeater became not operational or auto-partitioned, or the media for any ports' MAUs b… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.6 | erptrTotalRptrErrors | 1 | 1 | The total number of errors which have occured on all the groups in a repeater. This object is a summation of the values of the r… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.7 | erptrJabberProtectionAdminStatus | 1 | 1 | The jabber protection function automatically disables a port whenever it detects a very long input event (or jabber) on that port… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.8 | erptrTotalPorts | 1 | 1 | The total number of front panel ports in the repeater. This object is summation of rptrPortCapacity as defined in RFC1516 for eac… |
| 1.3.6.1.4.1.36.2.18.11.5.1.1.1.1.9 | erptrPMDCarrierCardType | 1 | 1 | The value unknown(1) indicates card that connects to MOD-PMDs are not present. The value type10Base (2) indicates card that conne… |