Figure 316: Transmitting Link Trace Messages; Transmitting Loop Back Messages - Edge-Core ECS4620-28T Quick Start Manual

28/52-port l3 stackable gigabit ethernet switch

Hide thumbs Also See for ECS4620-28T:

Table of Contents

| Basic Administration Protocols

Connectivity Fault Management

Transmitting Loop

Back Messages

Figure 316: Transmitting Link Trace Messages

Use the Administration > CFM (Transmit Loopback) page to transmit Loopback

Messages (LBMs). These messages can be used to isolate or verify connectivity

faults by submitting a request to a target node (i.e., a remote MEP or MIP) to echo

the message back to the source.

Command Usage

Loopback messages can be used for fault verification and isolation after

automatic detection of a fault or receipt of some other error report. Loopback

messages can also used to confirm the successful restoration or initiation of

connectivity. The receiving maintenance point should respond to the loop back

message with a loopback reply.

The point from which the loopback message is transmitted (i.e., a local DSAP)

and the target maintenance point must be within the same MA.

If the continuity check database does not have an entry for the specified

maintenance point, an error message will be displayed.

When using the command line or web interface, the source MEP used by to

send a loopback message is chosen by the CFM protocol. However, when using

SNMP, the source MEP can be specified by the user.

These parameters are displayed:

MD Index – Domain index. (Range: 1-65535)

MA Index – MA identifier. (Range: 1-2147483647)

Source MEP ID – The identifier of a source MEP that will send the loopback

message. (Range: 1-8191)

Show Quick Links

Table of Contents