Configuration Notes and Constraints

When configuring EFM OAM, pay attention to the following notes:

An EFM connection cannot be established between two EFM OAM entities that are both in passive mode.
Only the active mode end can run commands ethernet-oam remote-loopback start interface <interface-name> or ethernet-oam remote-loopback stop interface <interface-name> to start | stop EFM OAM remote loopback tests.
Before starting the EFM OAM remote loopback tests, make sure:
- The EFM OAM connection has been established successfully.
- Users have to configure command set protocols ethernet-oam interface <interface-name> remote-loopback supported on the responding end to enable reactions to loopback control OAMPDUs from peers.

Configuring EFM OAM

Step 1 Enable EFM OAM function on both end of the link.

set protocols ethernet-oam interface <interface-name> enable <true | false>

Step 2 Configure the EFM mode for this Ethernet port. By default, the EFM OAM interface works in active mode.

set protocols ethernet-oam interface <interface-name> mode <active | passive>

Step 3 Enable reactions to loopback control OAMPDUs from peers.

set protocols ethernet-oam interface <interface-name> remote-loopback supported

Step 4 (Optional) Configure EFM OAM timeout values.

set protocols ethernet-oam interface <interface-name> remote-loopback timeout <loopback-timeout>

set protocols ethernet-oam interface <interface-name> timeout <oam-timeout>

Step 5 Enable EFM OAM remote loopback tests on the specified port.

NOTEs:

The commands ethernet-oam remote-loopback start interface and ethernet-oam remote-loopback stop interface are operational mode commands which should be executed under the prompt “admin@PICOS>”.
Only the active mode end can run commands ethernet-oam remote-loopback start interface <interface-name> or ethernet-oam remote-loopback stop interface <interface-name> to start| stop EFM OAM remote loopback tests.
Before starting the EFM OAM remote loopback tests, make sure:
- The EFM OAM connection has been established successfully.
- Users have to configure command set protocols ethernet-oam interface <interface-name> remote-loopback supported on the responding end to enable reactions to loopback control OAMPDUs from peers.
It is not allowed to modify EFM OAM mode when remote loopback function is implemented.

ethernet-oam remote-loopback start interface <interface-name>

Step 6 Stop EFM OAM remote loopback tests on the specified port.

ethernet-oam remote-loopback stop interface <interface-name>

Step 7 Commit the configuration.

commit

Step 8 View EFM OAM configuration information, session status and interface statistics.

run show ethernet-oam [interface <interface-name>]

run show ethernet-oam statistics [interface <interface-name>]

Example for Configuring EFM OAM

Networking Requirements

Figure 1. EFM OAM Configuration Example

As shown in Figure 1, the link between Switch C to Switch A is a newly deployed network. The administrator hopes to achieve the following network management:

Test network connectivity and quality before enabling the new network.
Dynamically monitor the link quality after the link is properly enabled.

Follow the configuration roadmap below to configure EFM function:

1. Configure EFM basic functions on Switch A and Switch C devices to achieve automatic detection of link connectivity.

2. Configure EFM remote loopback on Switch A and Switch C to conduct link connectivity and performance testing.

Procedure

Step 1 Configure EFM basic function.

a) Enable EFM OAM function on interface ge-1/1/1 on Switch A.

admin@SwitchA# set protocols ethernet-oam interface ge-1/1/1 enable true

b) Configure the EFM OAM mode for this Ethernet port.

admin@SwitchA# set protocols ethernet-oam interface ge-1/1/1 mode active
admin@SwitchA# commit

c) Enable EFM OAM function on interface ge-1/1/1 on Switch C.

admin@SwitchC# set protocols ethernet-oam interface ge-1/1/1 enable true

d) Configure the mode of EFM OAM mode for this Ethernet port.

admin@SwitchC# set protocols ethernet-oam interface ge-1/1/1 mode passive
admin@SwitchC# commit

e) Verify the Configuration.

If the EFM configurations of Switch A and Switch C are correct, a connection will be established between them after successful negotiation in the Discovery phase. Run the command run show ethernet-oam on Switch A or Switch C, you can see that the EFM OAM protocol status of interface ge-1/1/1 is SEND_ANY.

admin@SwitchC# run show ethernet-oam
Interface ge-1/1/1
Local client
    Admin state:       enable
    OAM Mode:          passive
    OAM timeout:       30 seconds
    Loopback timeout:  3 seconds
    Loopback status:   no loopback
    PDU revision:      3
    OAM status:        SEND_ANY
    PDU:               ANY
Remote client
    MAC address:       18:5a:58:5c:8c:21
    OUI:               48:6e:73
    PDU revision:      3
    OAM Mode:          active
    Unidirection:      not supported
    Link monitor:      not supported
    Remote loopback:   not supported
    MIB retrieval:     not supported
    Mtu size:          1500

Step 2 Enable remote loopback.

a) Enable reactions to loopback control OAMPDUs from peers on Switch C.

admin@SwitchC# set protocols ethernet-oam interface ge-1/1/1 remote-loopback supported
admin@SwitchC# commit

b) Start EFM OAM remote loopback tests on interface ge-1/1/1 on Switch A.

NOTEs:

The commands ethernet-oam remote-loopback start interface and ethernet-oam remote-loopback stop interface are operational mode commands which should be executed under the prompt “admin@PICOS>”.
Before starting the EFM OAM remote loopback tests:
- The EFM OAM connection has been established successfully.
- Users have to configure command set protocols ethernet-oam interface <interface-name> remote-loopback supported on the responding end to enable reactions to loopback control OAMPDUs from peers.

admin@SwitchA> ethernet-oam remote-loopback start interface ge-1/1/1

c) Verify the Configuration.

After successfully configuring EFM remote loopback, run the command run show ethernet-oam, and you can see that the loopback status is local loopback on Switch C and remote loopback on Switch A.

admin@SwitchC# run show ethernet-oam
--------------------------------------------------
Interface ge-1/1/1
Local client
    Admin state:       enable
    OAM Mode:          passive
    OAM timeout:       30 seconds
    Loopback timeout:  3 seconds
    Loopback status:   local loopback
    PDU revision:      3
    OAM status:        SEND_ANY
    PDU:               ANY
Remote client
    MAC address:       18:5a:58:5c:8c:21
    OUI:               48:6e:73
    PDU revision:      3
    OAM Mode:          active
    Unidirection:      not supported
    Link monitor:      not supported
    Remote loopback:   not supported
    MIB retrieval:     not supported
    Mtu size:          1500
--------------------------------------------------

admin@SwitchA# run show ethernet-oam interface ge-1/1/1
--------------------------------------------------
Interface ge-1/1/1
Local client
    Admin state:       enable
    OAM Mode:          active
    OAM timeout:       30 seconds
    Loopback timeout:  3 seconds
    Loopback status:   remote loopback
    PDU revision:      3
    OAM status:        SEND_ANY
    PDU:               ANY
Remote client
    MAC address:       18:5a:58:03:35:81
    OUI:               48:6e:73
    PDU revision:      3
    OAM Mode:          passive
    Unidirection:      not supported
    Link monitor:      not supported
    Remote loopback:   supported
    MIB retrieval:     not supported
    Mtu size:          1500

View the statistics information of EFM OAMPDU packets, we can see the number of received Loopback Control OAMPDU packet is 1 on Switch C.

admin@SwitchC# run show ethernet-oam statistics interface ge-1/1/1
Packets statistics for interface ge-1/1/1
Packet type                       OAM Tx Count     OAM Rx Count
--------------------------------------------------------------------
OAMInformation                   11365            11372
OAMLoopbackControl               0                1
OAMUnsupported                   0                0

Step 3 Stop EFM remote loopback.

admin@SwitchC> ethernet-oam remote-loopback stop interface ge-1/1/1

Step 4 Verify the Configuration.

Run the command run show ethernet-oam, and you can see that the loopback status is no loopback on Switch C and Switch A.

admin@SwitchC# run show ethernet-oam
--------------------------------------------------
Interface ge-1/1/1
Local client
    Admin state:       enable
    OAM Mode:          passive
    OAM timeout:       30 seconds
    Loopback timeout:  3 seconds
    Loopback status:   no loopback
    PDU revision:      3
    OAM status:        SEND_ANY
    PDU:               ANY
Remote client
    MAC address:       18:5a:58:5c:8c:21
    OUI:               48:6e:73
    PDU revision:      3
    OAM Mode:          active
    Unidirection:      not supported
    Link monitor:      not supported
    Remote loopback:   not supported
    MIB retrieval:     not supported
    Mtu size:          1500
--------------------------------------------------

View the statistics information of EFM OAMPDU packets, we can see the number of received Loopback Control OAMPDU packet is 2 on Switch C.

admin@SwitchC# run show ethernet-oam statistics interface ge-1/1/1
Packets statistics for interface ge-1/1/1
Packet type                       OAM Tx Count     OAM Rx Count
------------------------------------------------------------------
OAMInformation                   18770            18792
OAMLoopbackControl               0                2
OAMUnsupported                   0                0