Differences between manually extended ECC and automatically extended ECC

Question: How many NEs can be interconnected using automatically extended ECC at a site? Analysis: At many sites, all NEs are interconnected using automatically extended ECC. As a result, there is a large number of NEs using this function for interconnection, and NEs are frequently unreachable by the NMS. Answer: 1. If an Ethernet is used to establish an extended ECC channel for communication, at most four extended ECC channels are required. With manually extended ECC, a server can be connected to at most 7 clients, and each client can be further connected as a server. Hubs (or switches) can be cascaded, which is related to the network scale limit only. The basic principle applies to each product and is related to the platform. 2. The method of cascading metro WDM devices using ETHERNET1 and ETHERNET2 ports does not apply to a long-haul WDM system. For long-haul WDM devices, the ETHERNET2 port is not used for ECC communication. In addition, you are advised to cascade at most eight network ports in a metro WDM system.

In the automatic mode of the extended ECC, you do not need to manually specify the server and client. The IP addresses of NEs can be automatically generated on the same network segment. In manual mode, you need to manually specify the server and client.

You can use the NMS or run the :cm-set-lanautoecc:open command to enable the automatic extended ECC. You can run the :cm-get-lanautoecc command to check whether the extended ECC is successfully enabled.

The NM_ETH port of a slave subrack is disabled by default and is not used for inter-NE communication. Inter-NE communication is implemented only through the NM_ETH port of a master subrack.

Yes. Transport network products support inter-product extended ECC.