IEEE
CSMA/CD Std 802.3-2008
Copyright © 2008 IEEE. All rights reserved.
19
information reflecting its local_par_action set to LB and its local_mux_action parameter set to DISCARD.
On the reception of an Information OAMPDU from the remote OAM client with updated state information,
the local OAM client sets the local_mux_action to FWD.
If an OAM client has sent a Loopback Control OAMPDU and is waiting for the peer DTE to respond with
an Information OAMPDU that indicates it is in OAM remote loopback mode, and that OAM client receives
an OAM remote loopback command from the peer device, the following procedures are recommended:
a) If the local DTE has a higher source_address than the peer, it should enter OAM remote loopback
mode at the command of its peer.
b) If the local DTE has a lower source_address than the peer, it should ignore the OAM remote
loopback command from its peer and continue as if it were never received.
If OAM clients do not follow these guidelines, it may be possible for two OAM clients to issue simultaneous
OAM remote loopback commands with indeterminate results.
57.2.11.2 During OAM remote loopback
This section elaborates on Figure 57–4 and describes the flow of frames within the local and remote DTEs
and across the link during OAM remote loopback mode. While in OAM remote loopback mode:
a) The local DTE transmits frames from the MAC client and OAMPDUs from the local OAM client or
OAM sublayer.
b) Within the remote OAM sublayer entity, every non-OAMPDU, including other Slow Protocol
frames, is looped back without altering any field of the frame.
c) OAMPDUs received by the remote DTE are passed to the remote OAM client.
d) Both DTEs are required to send OAMPDUs to the peer DTE in order to keep the Discovery process
from re-starting. Both are also permitted to send other OAMPDUs to the peer DTE.
e) Frames received by the local DTE are parsed by the OAM sublayer. OAMPDUs are passed to the
OAM client and all other frames are discarded.
57.2.11.3 Exiting OAM remote loopback
When the local DTE wishes to end the OAM remote loopback test, the local OAM client sets its
local_mux_action parameter to DISCARD. The local OAM client then sends a Loopback Control
OAMPDU with the Disable OAM Remote Loopback command. After receiving a Loopback Control
OAMPDU with the Disable OAM Remote Loopback command, the remote OAM client first sets the
local_par_action and local_mux_action parameters to FWD via the OAM_CTL.request service primitive
and then sends an Information OAMPDU with updated state information reflecting the local_par_action and
local_mux_action parameters set to FWD. After receiving an Information OAMPDU with local_par_action
and local_mux_action set to FWD, the local OAM client sets its local_par_action and local_mux_action
parameters to FWD via the OAM_CTL.request service primitive. The remote Parser resumes passing
received non-OAMPDUs up to the MAC client and the local Multiplexer resumes forwarding any frames
sourced by the local MAC client.
57.2.11.4 Loss of OAMPDUs during OAM remote loopback
There is the possibility of OAMPDU loss before, during and after OAM remote loopback tests. Of particular
interest to the operation of OAM remote loopback is the loss of Loopback Control OAMPDUs and
Information OAMPDUs. The local OAM client is able to determine whether or not the remote OAM client
received Loopback Control OAMPDUs by examining all received Information OAMPDUs. Since
Information OAMPDUs are continually sent to keep the OAM Discovery process from restarting, the
occasional loss of an Information OAMPDU should not adversely impact the operation of OAM remote
loopback mode.
Authorized licensed use limited to: Nokia Siemens Networks. Downloaded on June 29, 2009 at 09:15 from IEEE Xplore. Restrictions apply.