No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


FAQ-Method Used to Upgrade an NG SDH Device to an ASON NE

Publication Date:  2019-04-15 Views:  104 Downloads:  0

Issue Description

Method used to upgrade an NG SDH device to an ASON NE


The NE software version and NMS version must support the ASON feature, and active and standby system control boards must be configured in the master subrack.

The ASON feature is controlled by a license on the NMS. You can enable the ASON feature only after you have applied for and purchased an ASON feature license or obtained special approval from Huawei.

To configure an ASON NE, perform the following steps:

Check the consistency between the logical and physical boards.

If the types of the logical and physical boards are inconsistent, the board cannot work normally, which affects services. Therefore, you need to check whether the logical board is consistent with the physical board before commissioning the service.

1. Set the DCC working mode.
Before starting the ASON software, you need to query the DCC working mode of the NE and set the DCC working mode again.

2. Modify the node ID.
The node ID, NE ID, and NE IP address are independent of each other. On the ASON network, each ASON NE has a unique node ID across the network. Node IDs must be planned during network planning.

3. Enable the ASON feature.
The ASON feature is available only after the ASON feature is enabled. The ASON feature is disabled by default.

4. Upload NE configuration data.
During device commissioning, NE data already exists on the NMS. After the ASON feature is enabled on an ASON NE, the NE cannot be initialized and data cannot be downloaded to the NE. After the ASON feature is enabled or disabled, upload NE configuration data to ensure that the data on the NMS is consistent with that on the NE.

5. Create an ASON domain.
The NMS manages ASON networks based on ASON domains. Generally, ASON domains are created automatically. If some NEs fail to be added to ASON domains due to certain factors during NE data uploading, manually create ASON domains and add all ASON NEs on the same ASON network to the same ASON domain.

6. Synchronize ASON NEs.
Network synchronization is performed on the active NE to automatically discover other ASON NEs on the network.

7. Set the active and standby NEs.
On an ASON network, each ASON NE can obtain the topology information of the entire network. The active NE communicates with the NMS. It obtains ASON control plane information and reports ASON events to the NMS. To improve reliability, you can configure a standby NE, which functions as a backup of the active NE. If the active NE fails, the standby NE takes over and communicates with the NMS. Usually, a GNE is used as the active or standby NE to save ECC bandwidth.

8. Synchronize network-wide control links.
Synchronize control links to ensure that the control link data on the NMS is consistent with the control link data on NEs on the ASON network.

9. Synchronize TE links.
Query network-wide link data from the active NE, and synchronize TE link data so that the link data on the NMS side is consistent with that on the ASON network.

10. Automatically create fibers.
The NMS automatically creates fibers between ASON NEs.