ETH-CFM configuration guidelines

Up MEPs and bidirectional MIPs are not created by default on system bootup, and additional resources must be allocated to enable Up MEP and bidirectional MIP functionality. By default, no resources are allocated. Before Up MEPs and bidirectional MIPs can be created, the user must first use the configure>system>resource-profile context to explicitly allocate hardware resources for use with these features. The software will reject the configuration to create an Up MEP or bidirectional MIP and generate an error until resources are allocated. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.

7210 SAS platforms support functionality for ingress and egress MIPs. In most services, only ingress MIPs are supported. Some services also support both ingress and egress MIPs, also called bidirectional MIPs. An ingress MIP or a Down MIP processes messages in the ingress direction when the OAM message is received on ingress of the SAP or port (subject to other checks). An egress MIP or an UP MIP refers to a MIP that processes messages in the egress direction when the OAM message is being sent out of the SAP/port. See Table: ETH-CFM support matrix for the 7210 SAS-T (network mode), Table: ETH-CFM support matrix for the 7210 SAS-T (access-uplink mode), Table: ETH-CFM support matrix for 7210 SAS-Mxp Devices, Table: ETH-CFM support matrix for 7210 SAS-R6 and 7210 SAS-R12 devices, Table: ETH-CFM support matrix for 7210 SAS-Sx/S 1/10GE devices, and Table: ETH-CFM support matrix for 7210 SAS-Sx 10/100GE devices for more information about ingress MIP, egress MIP, and bidirectional MIP support for service entities.

On 7210 SAS platforms, Ethernet Linktrace Response (ETH-LTR) is always sent out with priority 7.

7210 SAS platforms, send out all CFM packets as in-profile. Currently, there is no mechanism in the SAA tools to specify the profile of the packet.

On the 7210 SAS-R6 and 7210 SAS-R12, and on the 7210 SAS-Sx/S 1/10GE operating in the standalone-VC mode, before configuring bidirectional MIPs for an Epipe SAP or Epipe SDP binding, resources must be allocated to both Down MEPs and Up MEPs. That is, bidirectional MIPs in an Epipe service use the resources from both the Down MEP and Up MEP resource pools. By default, no resources are allocated for bidirectional MIPs, and configuration attempts before resource allocation are not permitted by the system and will generate a system error/log. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Basic System Configuration Guide for more information.

Sender ID TLV processing (insertion and reception) is not supported for CCM messages for MEPs that are implemented in hardware; that is, on 7210 SAS-T Down MEPs in access-uplink mode. For these MEPs, Sender ID TLV processing is supported only for LTM and LBM messages.

Sender ID TLV processing is supported only for service MEPs. It is not supported for G.8032 MEPs.

Facility MEPs are not supported on the 7210 SAS. G8032 MEPs are supported on the 7210 SAS.

Ethernet rings are not configurable under all service types. Any service restrictions for MEP direction or MIP support will override the generic capability of the Ethernet ring MPs. See the 7210 SAS-Mxp, R6, R12, S, Sx, T Interface Configuration Guide for more information about Ethernet rings.

On 7210 SAS devices, when two bidirectional MIPs are configured in an Epipe service on both the service entities and endpoints (for example, on both the SAP and SDP configured in the Epipe service), only the MIP ingressing in the direction of linktrace messages responds. This is applicable to 7210 SAS platforms that support both ingress and egress MIPs (also referred to as bidirectional MIPs).