The following are ETH-CFM configuration guidelines:
The 7210 SAS platforms support only ingress MIPs in some services or bidirectional MIPs (that is, ingress and egress MIPs) in some services. Table: ETH-CFM support matrix for 7210 SAS-D, Table: ETH-CFM support matrix for 7210 SAS-Dxp, Table: ETH-CFM support matrix for 7210 SAS-K 2F1C2T, Table: ETH-CFM support matrix for 7210 SAS-K 2F6C4T, and Table: ETH-CFM support matrix for 7210 SAS-K 3SFP+ 8C list the MIP and MEP support for different services on different platforms.
On the 7210 SAS-D and 7210 SAS-Dxp, Up MEPs cannot be created by default on system bootup. Before Up MEPs can be created, the user must first use the configure>system>resource-profile context to explicitly allocate hardware resources for use with this feature. The software will reject the configuration to create an Up MEP and generate an error until resources are allocated. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Basic System Configuration Guide for more information.
On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, no explicit resource allocation is required before configuring Up MEPs.
On the 7210 SAS-K 2F1C2T, 7210 SAS-K 2F6C4T, and 7210 SAS-K 3SFP+ 8C, all MIPs are bidirectional. A MIP responds to OAM messages that are received from the wire and also responds to OAM messages that are being sent out to the wire. MIP support for SAP, SDP bindings, and services varies. See the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Services Guide for more information.
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.
This behavior is applicable to all 7210 SAS platforms where the feature supported has been added in both access-uplink mode and network mode of operation. See the 7210 SAS Software Release Notes 22.x.Rx for more information about which platform and MEPs or MIPs support this feature.
To enable DMM version 1 message processing on the 7210 SAS-D (access-uplink mode) and 7210 SAS-Dxp (access-uplink mode) platforms, the configure>eth-cfm>system>enable-dmm-version-interop command must be used.
To achieve better scaling on the 7210 SAS-D and 7210 SAS-Dxp, Nokia recommends that the MEPs are configured at specific levels. The recommended levels are 0, 1, 3, and 7.
Ethernet rings are not configurable under all service types. Any service restrictions for the MEP direction or MIP support will override the generic capability of the Ethernet ring MPs. For more information about Ethernet rings, see the 7210 SAS-D, Dxp, K 2F1C2T, K 2F6C4T, K 3SFP+ 8C Interface Configuration Guide.
The supported minimum CCM transmission interval values vary depending on the MEP type and 7210 SAS platform. The following table lists the supported minimum CCM timer values.
Platform |
G.8032 down MEP |
Service down MEP |
Service up MEP |
|---|---|---|---|
7210 SAS-D |
100 ms |
100 ms |
1 s |
7210 SAS-Dxp |
10 ms |
1 s |
1 s |
7210 SAS-K 2F1C2T |
10 ms |
1 s |
1 s |
7210 SAS-K 2F6C4T |
10 ms |
1 s |
1 s |
7210 SAS-K 3SFP+ 8C |
10 ms |
1 s |
1 s |
Sender-ID TLV processing is supported only for service MEPs. It is not supported for G.8032 MEPs.