HWECC Configuration Process

This section describes how to configure an HWECC network.

Figure 1 shows the configuration process for an HWECC network.

Figure 1 Configuration process for an HWECC network

No.	Procedure		Remarks
1	Locally configure NE communication data. NOTE: In this procedure, you must configure each NE for a site after powering on the NE at the site. The reference data for configuration is the network planning outputs.	Configure basic attributes for each NE, including information provided in the following topics: Changing an NE ID Setting NE Communication Parameters	Mandatory These topics describe how to configure basic attributes for each NE, including NE IDs and IP addresses. In some cases, you need to set the subnet masks and default gateways according to the external DCN information.
		Configuring Extended ECC Communication	Optional When the number of Huawei NEs that communicate with each other through extended ECC exceeds four, it is recommended to configure extended ECC in specified mode. Ensure that each HWECC subnet is a ring so that the DCN channel for each network segment can be backed up and protected. Therefore, the routes can be protected when a fiber is broken or an NE in the subnet is faulty. To achieve this goal, configure extended ECC in specified mode for the NE that is connected to the NMS on each adjacent network segment.
		Dividing a Network into ECC Subnets	Optional When the number of NEs in a network is beyond the limit, it is required to divide the network into subnets. This operation disables or deletes the DCN port on the edge NEs in each subnet. Specifically, this operation disables or deletes the edge port DCC/GCC channels of OSC or ESC boards on the edge NEs.
		Configuring Transparent Transmission of DCC Channels	Optional If the subnet division compromises the ECC route protection capability, perform this operation to ensure that DCC/GCC bytes of one DCN subnet are transparently transmitted over other DCN subnets. This operation restores the ECC route protection capability.
2	Manage NEs using the NMS.	Configuring Primary and Secondary GNEs	Mandatory After a network is divided into subnets or if there are multiple GNEs, configure primary and secondary GNEs for each non-GNE.
3	Verify DCN communication on the NMS.	Viewing the ECC Route for an NE	Mandatory Perform this operation to check the ECC routes planned for GNEs, and ensure that the following conditions are met: An ECC route is available between each GNE and each non-GNE managed by the GNE. No ECC route exists between each GNE in one DCN subnet and each NE in other DCN subnets. If the actual ECC routes for NEs are fewer than the planned ECC routes, manually add the missing ECC routes.
		Checking NE communication status	Mandatory After configuring NE communication data and creating NEs on the NMS, query the NE communication status on the NMS to ensure that all NEs are reachable by the NMS.
		Testing the Communication Between the Web LCT and the GNE	Optional The verification and test of the ECC routes include ECC protection tests, subnet checks, and connectivity tests.
4	Configure inter-subnet communication on the NMS (optional).	Configuring Edge NEs	Optional When inter-subnet communication is required, enable or create a DCC or GCC at an edge NE in each subnet. It is recommended that you enable the DCC or GCC with higher bandwidth and change Protocol Type to HWMAC.
4	Configure inter-subnet communication on the NMS (optional).	Adding the Manual ECC Route for an NE	Optional When inter-subnet communication is required, configure static routes from edge NEs to non-edge NEs in other subnets.