To update the displayed settings, click the Refresh button.
Slot Displays the slot number and the card description.
Status
Port |
A unique value for each interface. |
Oper Status |
Indicates the operational status of this Ethernet port. |
Admin Status |
The administrative status of the interface. Up: The interface is enabled and up, and the status of the interface should become standby or operational. Down: The interface is disabled and down, and the status of the interface whould become shutdown. |
OAM Oper Status |
At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OAM sublayer. This value is always disabled(1) if OAM is disabled on this interface via the Admin State. If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault. Also, if the interface is not operational (if OperStatus is not up), linkFault is returned. Note that the Oper Status may not be up as a result of link failure or administrative action (if Admin State being down or testing3. The passiveWait state is returned only by OAM entities in passive mode (Mode) and reflects the state in which the OAM entity is waiting to see if the peer device is OAM capable. The activeSendLocal value is used by active mode devices (dot3OamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination. The state sendLocalAndRemote reflects that the local OAM entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowedby the local device, the state moves to sendLocalAndRemoteOk. Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected. Note that both the sendLocalAndRemoteOk and oamPeeringRemotelyRejected(8)states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAMPDU (reflected in the a OAMRemoteFlagsField of 30.3.6.1.11). When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5]. Since Ethernet OAM functions are not designed to work completely over half-duplex interfaces, the value nonOperHalfDuplex(10) is returned whenever Ethernet OAM is enabled (Admin State is enabled), but the interface is in half-duplex operation. Values: disabled linkFault passiveWait activeSendLocal sendLocalAndRemote sendLocalAndRemoteOk oamPeeringLocallyRejected oamPeeringRemotelyRejected operational nonOperHalfDuplex |
OAM Admin State |
This object is used to provision the default administrative OAM mode for this interface. This object represents the desired state of OAM for this interface. The Admin State always starts in the disabled state until an explicit management action or configuration information retained by the system causes a transition to the enabled state. When enabled, Ethernet OAM will attempt to operate over this interface. |
OAM Assignment |
Whether this interface has OAM enabled. |
Mode |
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 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 dOper Status was already operational. Values: passive active |
Max OAM PDU Size |
The largest OAMPDU that the OAM entity supports. OAM entities exchange maximum OAMPDU sizes and negotiate to use the smaller of the two maximum OAMPDU sizes between the peers. This value is determined by the local implementation. In octets. |
Configuration Revision |
The configuration revision of the OAM entity as reflected in the latest OAMPDU sent by the OAM entity. The config revision is used by OAM entities to indicate that configuration changes have occurred, which might require the peer OAM entity to re-evaluate whether OAM peering is allowed. |
Functions Supported |
The OAM functions supported on this Ethernet-like interface. OAM consists of separate functional sets beyond the basic discovery process that is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs. Setting 'unidirectionalSupport' indicates that the OAM entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport' indicates that the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport' indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting 'variableSupport(3)' indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs. Values: unidirectionalSupport loopbackSupport eventSupport variableSupport |
January 22, 2011