set port oam remote-loopback (S-, 7100-Series)

Use this command to enable or disable OAM remote loopback for the specified port.

Syntax

set port oam port-string remote-loopback {enable | disable}

Parameters

port-string Specifies the port(s) to enable or disable remote loopback. For a detailed description of possible port-string values, refer to Port String Syntax Used in the CLI in the S-, K-, and 7100 Series Configuration Guide.
enable | disable Enables or disables OAM remote-loopback for the specified port(s). The default value is disable.

Defaults

None.

Mode

All command modes.

Usage

This command:

  • Instructs the remote OAM client to initiate, if enabled, or terminate, if disabled, the remote loopback process.
  • Is a volatile configuration option that does not persist across reboots, and is not displayed in the show config port output.

Port OAM must be configured for active mode, the OAM client must have completed the discovery process with the remote OAM client, and that client must indicate that it supports loopback in order to initiate the loopback process. A client which has been put into loopback mode will re-transmit all traffic that has been received on that port (with the exception of OAM PDUs) back towards the sender.

A client which has put its peer into loopback mode will discard all received traffic (with the exception of OAM PDUs) on that port. Be aware that OAM remote loopback is a disruptive test state intended to aid in the diagnosis of network issues, and will interfere with the normal operation of other network protocols and data flows over that link.

Caution must be used when placing an OAM enabled port in remote loopback. When requesting the remote OAM enabled port to be placed in loopback, the loopback mode of the remote port must be set to process using “set port oam loopback-rx” on page 20-28. OAM remote loopback‘s behavior is “fire and forget”. If for any reason, including OAM mode set to ignore, or the loopback request or remote response should be lost in transit, remote loopback will remain in either an initiating or terminating loopback state. The potential for harm to the network exists where one end of the link believes remote loopback is in effect, and the other does not.

Should the loopback request PDU be lost in transit or the remote end be set to ignore the PDU, the loopback session will be left in a bad state, and the port will be prevented from both sending and receiving data until OAM is administratively disabled and then enabled on both ends of the link.

The default value for OAM remote loopback is disable.

Example

This example shows how to enable remote loopback on port ge.1.3:

System(rw)->set port oam ge.1.3 remote-loopback enable