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). 1 (dot3OamTable). 1 (dot3OamEntry). 3 (dot3OamMode)
OID : 1.3.6.1.2.1.158.1.1.1.3
TXT : iso. org. dod. internet. mgmt. mib-2. dot3OamMIB. dot3OamObjects. dot3OamTable. dot3OamEntry. dot3OamMode
Enfants
Pas d'enfants disponibles pour cet OID
Détails
OID1.3.6.1.2.1.158.1.1.1.3
Module DOT3-OAM-MIB (ietf)
Nomdot3OamMode
Accesreadwrite
Statuscurrent
DescriptionThis object configures the mode of OAM operation for this Ethernet-like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OA actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OA entity cannot. The default value of dot3OamMode is dependent on the type of system on which this Ethernet-like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9).
SyntaxeEnumeration (1-passive, 2-active)
Module DOT3-OAM-MIB (Alcatel)
Nomdot3OamMode
Accesreadwrite
Statuscurrent
DescriptionThis object configures the mode of OAM operation for this Ethernet-like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OA actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OA entity cannot. The default value of dot3OamMode is dependent on the type of system on which this Ethernet-like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9).
SyntaxeEnumeration (1-passive, 2-active)