hpnicfDot3OamMode
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. 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 hpnicfDot3OamOperStatus was already operational(9).
Details
| 1 | active |
| 2 | passive |
[802.3ah], 30.3.6.1.3
Table columns
6 objects| Oid | Name | Access | Type |
|---|---|---|---|
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.1 | hpnicfDot3OamAdminState | readwrite | disabled(1), enabled(2) |
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.2 | hpnicfDot3OamOperStatus | readonly | disabled(1), linkfault(2), passiveWait(3), activeSendLocal(4), sendLocalAndRemote(5), sendLocalAndRemoteOk(6), oamPeeringLocallyRejected(7), oamPeeringRemotelyRejected(8), operational(9) |
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.3 | hpnicfDot3OamMode | readwrite | active(1), passive(2) |
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.4 | hpnicfDot3OamMaxOamPduSize | readonly | Unknown |
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.5 | hpnicfDot3OamConfigRevision | readonly | Unsigned32 |
| 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.1.1.6 | hpnicfDot3OamFunctionsSupported | readonly | Unknown |
Used by conformance groups
1 objects- 1.3.6.1.4.1.11.2.14.11.15.2.42.3.2.1.1 hpnicfDot3OamControlGroup