Oam Configuration; Enabling Oam On Local Ports; Table 35: Oam Operation State - Edge-Core ECS3510-28T Management Manual

OAM C
ONFIGURATION
E OAM
NABLING ON
L P
OCAL ORTS
The switch provides OAM (Operation, Administration, and Maintenance)
remote management tools required to monitor and maintain the links to
subscriber CPEs (Customer Premise Equipment). This section describes
functions including enabling OAM for selected ports, loopback testing, and
displaying remote device information.
Use the Administration > OAM > Interface page to enable OAM
functionality on the selected port. Not all CPEs support operation and
maintenance functions, so OAM is therefore disabled by default. If a CPE
supports OAM, this functionality must first be enabled on the connected
port to gain access to the configuration functions provided under the OAM
menu.
CLI R
EFERENCES
"OAM Commands" on page 1353
◆
P
ARAMETERS
These parameters are displayed:
Port – Port identifier. (Range: 1-28/52)
◆
Admin Status – Enables or disables OAM functions.
◆
(Default: Disabled)
Operation State – Shows the operational state between the local and
◆
remote OAM devices. This value is always "disabled" if OAM is disabled
on the local interface.

Table 35: OAM Operation State

State
Disabled
Link Fault
Passive Wait
Active Send Local
Send Local And Remote The local OAM entity has discovered the peer but has not yet
Send Local And Remote
OK
OAM Peering Locally
Rejected
OAM Peering Remotely
Rejected
– 549 –
| Basic Administration Protocols
C 14
HAPTER
Description
OAM is disabled on this interface via the OAM Admin Status.
The link has detected a fault or the interface is not operational.
This value is returned only by OAM entities in passive mode and
indicates the OAM entity is waiting to see if the peer device is
OAM capable.
This value is used by active mode devices and indicates the
OAM entity is actively trying to discover whether the peer has
OAM capability but has not yet made that determination.
accepted or rejected the configuration of the peer.
OAM peering is allowed by the local device.
The local OAM entity rejects the peering.
The remote OAM entity rejects the peering.

OAM Configuration