The T2000 V2R5C01B01C network management system (NMS) and four OSN3500 220.127.116.11P01 network elements (NEs) consist of an automatically switched optical network (ASON).
Before the ASON is tested, an ASON trail is created and the trail name is 12121212. After SDH path search, it is found that the names of the SDH path and ASON trail are different on the path management interface. For example, the name of the created ASON trail is 12121212, while the searched SDH path name is NE9-1-NE9-3-VC4-4C-0001 (the SDH path name is automatically generated and can be changed). In addition, the name of the corresponding ASON cross-connect trail on the service configuration interface of a single site is null. This case exists, no matter whether there are static services in the ASON.
Information on the screen snapshots related to some operations can be seen in the attachment.
You are recommended to enter a name.
The searched SDH path name is automatically generated according to the naming rules.
ASON trails are only a part of an SDH path. One or more ASON trails, other static cross-connect trails, and fiber cables are involved in path search, and they together form an SDH path. Therefore, there is no way to simply assign the ASON trail name to the searched SDH.
On the service configuration interface of a single site, the SDH path function ignores the automatically generated cross-connect (the path search function concerns only static cross-connect trails and ASON circuits, instead of ASON cross-connect trails). Therefore, ASON cross-connect trails have no trail name on the service configuration interface.