MIB Discovery
1930 modules enregistr├ęs
Chemin
MIX : 1 (iso). 3 (org). 6 (dod). 1 (internet). 4 (private). 1 (enterprises). 9 (cisco). 10 (ciscoExperiment). 136 (cdot3OamMIB). 1 (cdot3OamObjects). 3 (cdot3OamLoopbackTable). 1 (cdot3OamLoopbackEntry). 1 (cdot3OamLoopbackStatus)
OID : 1.3.6.1.4.1.9.10.136.1.3.1.1
TXT : iso. org. dod. internet. private. enterprises. cisco. ciscoExperiment. cdot3OamMIB. cdot3OamObjects. cdot3OamLoopbackTable. cdot3OamLoopbackEntry. cdot3OamLoopbackStatus
Enfants
Pas d'enfants disponibles pour cet OID
D├ętails
OID1.3.6.1.4.1.9.10.136.1.3.1.1
Module CISCO-DOT3-OAM-MIB (CISCO)
Nomcdot3OamLoopbackStatus
Accesreadwrite
Statuscurrent
Description The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). The values initiatingLooopback(2) and terminatingLoopback(4) can be read or written. The other values can only be read - they can never be written. Writing initiatingLoopback causes the local OAM entity to start the loopback process with its peer. This value can only be written when the status is noLoopback(1). Writing the value initiatingLoopback(2) in any other state has no effect. When in remoteLoopback(3), writing terminatingLoopback(4) causes the local OAM entity to initiate the termination of the loopback state. Writing terminatingLoopack(4) in any other state has no effect. If the OAM client initiates a looopback and has sent an Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgement that the remote OAM entity has received its loopback command request. If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14], with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5). The unknown(6) status indicates the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist. The values of this attribute correspond to the following values of the local and remote parser and multiplexer states. value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination ***
SyntaxeEnumeration (1-noLoopback, 2-initiatingLoopback, 3-remoteLoopback, 4-terminatingLoopback, 5-localLoopback, 6-unknown)