dot3OamLoopbackTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OamLoopbackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This table contains controls for the loopback state of the
local link as well as indicates the status of the loopback
function. There is one entry in this table for each entry in
dot3OamTable that supports loopback functionality (where
dot3OamFunctionsSupported includes the loopbackSupport bit
set).
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this
state, at the remote entity, \normal\ traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly.
"
View at oid-info.com
This table contains controls for the loopback state of the
local link as well as indicates the status of the loopback
function. There is one entry in this table for each entry in
dot3OamTable that supports loopback functionality (where
dot3OamFunctionsSupported includes the loopbackSupport bit
set).
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly.
Parsed from file rfc4878-OAM-Functions-on-Ethernet-Like-Interfaces.mib.txt
Company: None
Module: DOT3-OAM-MIB
This table contains controls for the loopback state of the
local link as well as indicates the status of the loopback
function. There is one entry in this table for each entry in
dot3OamTable that supports loopback functionality (where
dot3OamFunctionsSupported includes the loopbackSupport bit
set).
Loopback can be used to place the remote OAM entity in a state
where every received frame (except OAMPDUs) is echoed back
over the same interface on which they were received. In this
state, at the remote entity, 'normal' traffic is disabled as
only the looped back frames are transmitted on the interface.
Loopback is thus an intrusive operation that prohibits normal
data flow and should be used accordingly.
Parsed from file DOT3-OAM-MIB.mib
Module: DOT3-OAM-MIB
Automatically extracted from RFC4878
dot3OamLoopbackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamLoopbackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains controls for the loopback state of the local link as well as indicates the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set). Loopback can be used to place the remote OAM entity in a state where every received frame (except OAMPDUs) is echoed back over the same interface on which they were received. In this state, at the remote entity, 'normal' traffic is disabled as only the looped back frames are transmitted on the interface. Loopback is thus an intrusive operation that prohibits normal data flow and should be used accordingly. " ::= { dot3OamObjects 3 }
dot3OamLoopbackTable OBJECT-TYPE SYNTAX SEQUENCE OF Dot3OamLoopbackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains controls for the loopback state of the local link as well as indicates the status of the loopback function. There is one entry in this table for each entry in dot3OamTable that supports loopback functionality (where dot3OamFunctionsSupported includes the loopbackSupport bit set). Loopback can be used to place the remote OAM entity in a state where every received frame (except OAMPDUs) is echoed back over the same interface on which they were received. In this state, at the remote entity, 'normal' traffic is disabled as only the looped back frames are transmitted on the interface. Loopback is thus an intrusive operation that prohibits normal data flow and should be used accordingly. " ::= { dot3OamObjects 3 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.158.1.3.1 | dot3OamLoopbackEntry | 2 | 2 | An entry in the table, containing information on the loopback status for a single Ethernet-like interface. Entries in the table … |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.158.1.1 | dot3OamTable | 1 | 7 | This table contains the primary controls and status for the OAM capabilities of an Ethernet-like interface. There will be one ro… |
| 1.3.6.1.2.1.158.1.2 | dot3OamPeerTable | 1 | 8 | This table contains information about the OAM peer for a particular Ethernet-like interface. OAM entities communicate with a sin… |
| 1.3.6.1.2.1.158.1.4 | dot3OamStatsTable | 1 | 18 | This table contains statistics for the OAM function on a particular Ethernet-like interface. There is an entry in the table for … |
| 1.3.6.1.2.1.158.1.5 | dot3OamEventConfigTable | 1 | 17 | Ethernet OAM includes the ability to generate and receive Event Notification OAMPDUs to indicate various link problems. This tabl… |
| 1.3.6.1.2.1.158.1.6 | dot3OamEventLogTable | 1 | 13 | This table records a history of the events that have occurred at the Ethernet OAM level. These events can include locally detect… |