This 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 OAM
actions with it. As an example, an active OAM entity can put
the remote OAM entity in a loopback state, where a passive OAM
entity cannot.
The default value of wwpOamMode is dependent on the type of
system on which this Ethernet like interface resides. The
default value should be 'active(1)' 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
wwpOamOperStatus was already operational(9).
Parsed from file WWP-OAM-MIB.mib
Module: WWP-OAM-MIB
Vendor: World Wide Packets
Module: WWP-OAM-MIB
[Automatically extracted from oidview.com]
wwpOamMode OBJECT-TYPE SYNTAX INTEGER { active(1), passive(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "This 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 OAM actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OAM entity cannot. The default value of wwpOamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(1)' 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 wwpOamOperStatus was already operational(9). " ::= { wwpOamEntry 3 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.1 | wwpOamAdminState | 0 | 0 | This object is used to provision the default administrative OAM mode for this interface. This object represents the desired sta… |
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.2 | wwpOamOperStatus | 0 | 0 | At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to deter… |
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.4 | wwpMaxOamPduSize | 0 | 0 | The largest OAMPDU that the OAM entity supports. OAM entities exchange maximum OAMPDU sizes and negotiate to use the smaller of … |
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.5 | wwpOamConfigRevision | 0 | 0 | The configuration revision of the OAM entity as reflected in the latest OAMPDU sent by the OAM entity. The config revision is us… |
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.6 | wwpOamFunctionsSupported | 0 | 0 | The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery … |
| 1.3.6.1.4.1.6141.2.400.1.2.1.1.7 | wwpOamPort | 0 | 0 | An Ethernet port on the switch. |