How to handle the SDH discrete service?

After trail search, discrete services are usually caused by the following factors, which are unsatisfied trail search criteria, U2000 trail search restrictions, incomplete or wrong configuration of cross-connections, and existence of SDH NNI services.

• Method 1:
  1. Perform a consistency check to check whether the data on the U2000 and the data on the NEs are consistent or not. If not, upload the configuration data to the U2000.
  2. Verify that the fiber connections created on the U2000 are consistent with the actual fiber connections, and that there are no errors like wrong fiber connection on the U2000.
  3. Search for protection subnets. Verify that all the protection subnets are searched. Check whether the parameters for protection subnets and the logical system of each node are set correctly, and whether SDH NNIs are created for SDH NNI services.
  4. Perform a trail search on the U2000.
  5. If discrete services are found, analyze and handle them according to the causes displayed on the U2000 and the handling measures that are given above. It is recommended that you handle the discrete services at add/drop tributaries first, then handle those SDH NNI discrete services, and finally the pass-through discrete services.
• Method 2: Convert discrete services to mono nodal trails. For detailed operations, see Converting SDH Discrete Services to Mono Nodal Trails.
• Method 3: Create different protection subnets for different NEs. For example, for WDM NEs, choose Service > WDM Protection Subnet from the menu. For SDH NEs, choose Service > SDH Protection Subnet from the main menu.