MIB Discovery
1930 modules enregistrés
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 2 (mgmt). 1 (mib-2). 158 (dot3OamMIB). 1 (dot3OamObjects). 3 (dot3OamLoopbackTable)
OID : 1.3.6.1.2.1.158.1.3
TXT : iso. org. dod. internet. mgmt. mib-2. dot3OamMIB. dot3OamObjects. dot3OamLoopbackTable
Enfants
Détails
OID1.3.6.1.2.1.158.1.3
Module DOT3-OAM-MIB (ietf)
Nomdot3OamLoopbackTable
Statuscurrent
DescriptionThis 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.
Module DOT3-OAM-MIB (Alcatel)
Nomdot3OamLoopbackTable
Statuscurrent
DescriptionThis 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.