Dear friend!
This is entirely achievable. However, pay attention to the following four points:
1. When managing shared NEs, the two NMSs use different NE accounts. For example, NMS1 uses root to manage NE1, and NMS2 uses LCT to manage NE1.
2. For shared NEs, synchronize NE-side data configurations on the NMS at any time (once a day is recommended). Otherwise, timeslot conflicts may occur during service configuration. As a result, the configuration fails. For example, NMS1 configures a timeslot cross-connection on NE2. When NMS2 configures a timeslot cross-connection on NE2, NMS2 does not know that some idle timeslots are occupied and uses the same timeslot again. As a result, the configuration command fails to be delivered. It is recommended that the two companies negotiate in the early stage of network construction to specify the ownership of timeslots and link resources.
3. To ensure network security, each NMS uses its own NE account password for non-shared NEs. Do not use the default password. Do not allow the other company to manage its own NEs without the authorization of Huawei.
4. Pay attention to the management of discrete services. The timeslot cross-connections configured on NMS1 on the shared NE are regarded as discrete services on NMS2. The solution is to create virtual NEs, and cross-connections of each other from complete trails.
Thank you!