IManager U2000 Discrete Service Handling - 02

iManager U2000 Discrete Service Handling INTERNAL
Document Code Product Name U2000
Intended Reader Optical Network Engineer Product Version V100R001C00
Optical Network Product

Edited by Document Version 02
Service Dept.
iManager U2000 Discrete Service

Handling
Drafted by Zhong Jianjuan Date May 30, 2009
Reviewed by Date
Reviewed by Date
Approved by Date
Huawei Technologies Co., Ltd.
2009-10-23 Huawei Confidential. No disclosure without permission. Page 1 of 30

All Rights Reserved.

Revision History
Date Issue Author Description
Completed the first draft. The

Jun 26, 2009 01 Wang Haitao document is for the V100R001C00
version.
Modified the product and document

Oct 23, 2009 02 Wang Haitao names. The document is for the
V100R001C00SPC001 version.

iManager U2000 Discrete Service Handling Table of Contents
Table of Contents
Chapter 1 Overview......................................................................................................................... 6
1.1 Basic Concepts.................................................................................................................... 6
1.1.1 Discrete Service......................................................................................................... 6
1.1.2 Trail............................................................................................................................ 6
1.2 Causes of Discrete Services................................................................................................8
1.2.1 Unsatisfied Trail Search Conditions...........................................................................8
1.2.2 U2000 Trail Search Restrictions................................................................................8
1.2.3 Incomplete or Incorrect Configuration of Cross-Connections....................................9
1.2.4 Existence of SDH NNI Services.................................................................................9
1.3 Impacts of Discrete Services................................................................................................9
1.3.1 SDH Discrete Service Management Function on the U2000...................................11
Chapter 2 Procedure for Clearing Discrete Services..................................................................15

2.1 Preparing for Handling Discrete Services...........................................................................15
2.2 Collecting Statistics and Analyzing Generation Causes of Discrete Services in a Simulated
Environment and Developing Solution of Clearing Discrete Services......................................15
2.3 Clearing and Verifying Discrete Services According to Clearance Solution on the U2000 of
the Customer............................................................................................................................ 17
2.4 Guiding the Customer to Use Trail Management After Clearance to Avoid New Discrete
Services................................................................................................................................... 18
Chapter 3 Guide of Analyzing Discrete Services........................................................................20

3.1 Handling the Discrete Service Caused by Incomplete or Incomplete Configuration of
Actual Services on an NE......................................................................................................... 20
3.1.1 Cross-Connection of Protection Trail Is Not Configured..........................................20
3.1.2 Incomplete Trail Caused by Incorrect SNCP Service Configuration........................21
3.1.3 Cross-Connection of the Protection Trail Is Incorrect...............................................22
3.1.4 Redundant or Incomplete Service Configuration.....................................................23
3.2 Handling the Discrete Service Caused by the Existence of NNI Services..........................24
3.3 Junk Service....................................................................................................................... 25
Chapter 4 Discrete Service Analysis Practice..................................................................................27

iManager U2000 Discrete Service Handling List of Figures
List of Figures
Figure 1-1 Fully unidirectional trail........................................................................................... 7
Figure 1-2 Partly unidirectional trail.......................................................................................... 8
Figure 1-3 SDH NNI services................................................................................................... 9
Figure 3-1 Cross-connection of the protection trail is not configured.....................................20
Figure 3-2 Incorrect SNCP service configuration...................................................................21
Figure 3-3 Configuring a service on a per-NE basis...............................................................22
Figure 3-4 Incorrect cross-connection of the protection trail..................................................23
Figure 3-5 Broadcast trail....................................................................................................... 23
Figure 3-6 SDH NNI services.................................................................................................24
Figure 3-7 Junk services........................................................................................................ 25
Figure 4-1 Networking............................................................................................................ 28

Key word
Discrete service
Summary
This document describes the concepts, generation causes, and impacts of the
discrete service and the function of managing SDH discrete services that the U2000
provides. This document mainly explains the procedure for clearing discrete services
and methods of analyzing on discrete services on the U2000 V2. This document aims
to help engineers to understand the discrete service and its generation causes better
and learn the methods of analyzing and clearing discrete services.
Acronyms and abbreviations
None
Reference
None

iManager U2000 Discrete Service Handling OverviewOverview
Chapter 1 Overview
1.1 Basic Concepts
 Note:
After trail search, a cross-connection on the U2000 becomes a discrete service, or it
forms a trail with other cross-connections. It cannot be a discrete service and forms a
trail with other cross-connections at the same time.
1.1.1 Discrete Service
The cross-connections which do not form trails after trail searching in the U2000 are
called discrete services. Discrete services locate at the U2000 network layer and are
a defined concept for the cross-connections by Huawei.
 Note:
Cross-connections locate on the NE side or NE layer of NMS. Herein, the cross-
connections are the services in SDH NEs. Service level in SDH NEs includes
VC4_64C, VC4_16C, VC4_8C, VC4_4C, VC4, VC3, and VC12.
Discrete service level in SDH NEs includes VC4_64C, VC4_16C, VC4_8C, VC4_4C,
VC4, VC3, and VC12.
To manage the discrete services, make sure U2000 license supports end-to-end SDH
trail management function.
1.1.2 Trail
Trail is a type of transmission entity. It consists of a pair of "unidirectional trail" which

transfer messages simultaneously on the contrary directions from input to output.
"Unidirectional trail" is also a type of transmission entity. The main responsibility is to

transfer messages from the input of the trail source to the output of the trail sink and
to monitor the full messages. Trail can be considered the end-to-end connections
comprising the terminal functions which take charge of the integrality when the
messages are transferred on the client layer network.
Features of the trail are as follows:
End-to-end connection
There are source and sink for the trail and the cross-connections between them can
be serial linked.
Trail is terminative
In terms of the trail formative condition, a trail (VC4, VC3, or VC12 trail) ends on a
tributary board, an NNI or a virtual NE. In terms of the trail concept, it ends at its
source or sink.
Trail is integrated
Trails are complete. Incomplete cross-connections become discrete services. See

Figure 1.1 and Figure 1.2.
 Note:
Unidirectional trail: consisting of working and protection trails. The protection trail is
formed or configured according to the self-healing network.
Bidirectional trail: two unidirectional trails which have the reversed sources and sinks.
Figure 1.1 Fully unidirectional trail

Figure 1.2 Partly unidirectional trail
1.2 Causes of Discrete Services
After the trail search, discrete services are usually caused by the following factors,
which are unsatisfied trail search conditions, U2000 trail search restrictions,
incomplete or incorrect configuration of cross-connections, and existence of SDH NNI
services.
1.2.1 Unsatisfied Trail Search Conditions
The data on the U2000 is inconsistent with the data on NEs.
The fibers created on the U2000 do not match actual fiber connections.
Protection subnets are not created or cannot be searched.
The NE data configuration is incorrect. For example, a non-protection chain service is

created on the protection ring, the NE logic system of the service does not belong to
any protection subnet, or the protection subnet configuration is incorrect.
1.2.2 U2000 Trail Search Restrictions
If the VC4 server trail is created between two NEs but the lower order (VC12 and
VC3) trails are not created, the services are not sent to NEs. In this case, when
another U2000 performs the trail search on these two NEs, the VC4 server trail
cannot be searched out.
In a VC4 server trail with multiple sources and multiple sinks, if some sources or sinks
are on SDH NNIs and others are on common optical and electrical interfaces, the trail
cannot be searched out.

1.2.3 Incomplete or Incorrect Configuration of Cross-Connections
The timeslot for the protection route is not configured. This often happens in a PP or
SNCP protection subnet.
The timeslot configured for the protection route is incorrect.
The SNCP service configuration is incorrect, which results in an incomplete protection

route. The configuration methods for SNCP services are different on 4.0 and 5.0 NEs.
For this reason, the incorrect SNCP services may have been configured.
The service configuration is incomplete. Check whether incomplete services are

configured in the station-by-station mode, for example, pass-through services may
not be configured on pass-through NEs. You should complete this service
configuration and search for the trails again.
1.2.4 Existence of SDH NNI Services
If there are SDH NNI services in the network, but SDH NNIs are not created or SDH
NNI services pass through the network, the cross-connections configured on each NE
cannot be searched out as trails. See Figure 1.3.
Figure 1.3 SDH NNI services
The U2000 manages NE1 through NE4, but is not able to manage T1 through T3
(equipment of other vendors). NE1 and NE2 have the S1 and S2 services to T1
respectively. IN addition, the S3 service exists between T2 and T3. Cross-connections
on the NE1, NE2, and NE4 that are related to S1, S2, and S3 are discrete services.
1.3 Impacts of Discrete Services
When a service is found to be a discrete service, it does not necessarily indicate that
the service cannot run properly on an NE. Discrete services have the following
impacts on network configuration and management:

On trail configuration:
In end-to-end service configuration (by trail), when selecting the source, sink, route
and timeslot of a trail, the U2000 regards the timeslots occupied by discrete services
as free timeslots and may allocate them to other services. Thus the trail creation fail s.
In this case, an error message of timeslot conflicted is displayed on the U2000.
If there are lots of discrete services, the success probability of trail creation on the
U2000 is lowered.
 Note:
the server\nml\nmlsdh\conf\cfg\ nmlsdh.cfg file contains the configuration items of
creating trails, selecting the source and sink, computing the route and specifying
timeslots, and whether to consider timeslots used by discrete services.
bConsiderDiscreteServiceSlot = 0
The value of 0 means to use the timeslots used by discrete services, and 1 means
not to use the timeslots used by discrete services.
By default, the timeslots used by discrete services are used. That is, timeslots used
by discrete services are regarded as idle timeslots. During trail creation, these
timeslots are considered during source and sink selection, route computation, and
timeslot specification.
If the configuration item is enabled, that is, bConsiderDiscreteServiceSlot = 1,
discrete services are not used, and the timeslots used by discrete services are
regarded as used timeslots, not idle. During trail creation, timeslots, source and sink
ports of discrete services are not considered during source and sink selection, route
computation, and timeslot specification.
On trail resource query:
If not all trails are found, the trail query result for a tributary board may also be
incomplete. Trail resources cannot be queried correctly by using the trail management
function.
On other systems:
Due to the incomplete trail search result, the resource statistics provided by the
U2000 is not accurate and therefore, it cannot serve as a data source for other
systems (such as the service products, including the NMS for VIP customers, the
resource system, the performance analysis system, and the network assessment
system).

On timeslot allocation diagram:
The timeslot allocation diagram of the U2000 is based on trails. Only when there are
trails on a node in the protection subnet, the trail timeslots used on this node are
displayed in the timeslot allocation diagram. The timeslots used by discrete services
cannot be displayed in the timeslot allocation diagram.
For services that are do not form trails, the trail-based management and
troubleshooting are not available on the U2000.
Some discrete services are not required and can waste the network resources.
1.3.1 SDH Discrete Service Management Function on the U2000
Cross-connections that exist only on an NE and cannot form a trail at the network
layer are called discrete services. How to view the discrete SDH services are
described.
Choose Service > SDH Trail > Discrete Service Management from the Main Menu.
A dialog box is displayed.
Click OK. The Set Discrete Service Browse Filter Conditions dialog box is
displayed.

Specify the filter criteria and click Filter.
You can view the detailed information of the discrete services and creation reasons in
the dialog box displayed.
 Note:
Cause analysis of discrete service is a new function of discrete service management
of the U2000 V2. This function displays existing discrete services, and also displays
generation causes of the discrete services by group. It supports analysis to some
extent. The U2000 V1 does not support analyzing the causes of discrete services. It
only displays existing discrete services.

You can click Save As to save the discrete services to a text file. By default, the file is
saved to the report directory of the client. (\U2000\client\report)
During the analysis on the generation cause of a discrete service, you can fast query
relevant information of the discrete service in the route view of the discrete service,
such as switching to the NE Explorer or service configuration, or querying relevant
fiber.
During the analysis of a discrete service, you can add the analyzed causes and
solutions to the Remarks field. The information can be exported together with other
information of the discrete service. For an analyzed discrete service, you can right-
click it and choose Acknowledge from the shortcut menu to add a flag to the discrete
service.

 Note:
 Navigation path of remarks and acknowledgement: In the Discrete Service
Management user interface, right-click a discrete service and choose the
corresponding items from the shortcut menu.
 To add remarks, enter necessary information in the dialog box and click OK.
 You can use the acknowledgement function to add flags to analyzed discrete
services. This helps the analysis in the future. In the Discrete Service
Management user interface, right-click an analyzed discrete service and choose
Acknowledge or Cancel Acknowledgement from the shortcut menu.
 The system supports performing operations such as adding remarks,
acknowledging or cancelling acknowledgement on multiple discrete services at the
same time. You can select several discrete services and perform any of these
operations in batches. You can press Ctrl + A or the arrow keys to select several
discrete services, but the number of services should not be more than 1000.
 Acknowledging discrete services is controlled by using a configuration item in
\U2000\ client\bin\config.ini file. By default, the function is enabled. To enable
the acknowledgement function, refer to Step 2 in section 2.2"Collecting Statistics
and Analyzing Generation Causes of Discrete Services in a Simulated
Environment and Developing Solution of Clearing Discrete Services".

Procedure for Clearing Discrete Services
iManager U2000 Discrete Service Handling Procedure for Clearing Discrete Services
Chapter 2 Procedure for Clearing Discrete

Services
This document explains the procedure for and process of clearing discrete services
from the aspect of technology.
The process of clearing discrete services is complicated. During the process, you
need to analyze according to the generation cause of each discrete service, and set
proper solution according to the analysis result.
2.1 Preparing for Handling Discrete Services

 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.
 Verify that the fiber connections created on the U2000 are consistent with the
actual fiber connections, and that there are no errors like incorrect fiber
connection on the U2000.
 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.
 Perform a trail search on the U2000.
 Search for discrete services by using the U2000 and save them to a text file
(SDH Disp XC_NM1.txt). Write down the time at which discrete services are
saved.
 Back up the U2000 data, including MO data, database and exported script files.
 Use the trail management function to configure services during this time because
services configured in this way cannot form discrete services.
2.2 Collecting Statistics and Analyzing Generation Causes

of Discrete Services in a Simulated Environment and
Developing Solution of Clearing Discrete Services
Step 1 Prepare an experimental condition for analysis and elimination (U2000).

Estimate the time to handle the discrete services.

Step 2 Check whether the function of acknowledging discrete services is enabled. By

default, the function is enabled.
 Note:
 Open the file of \U2000\ client\bin\config.ini and find the following configuration
item:
[disxcDo]
easy = value(0)
[\disxcDo]
 Change the value of the item from 0 to 1 and save the modification. (If the value is
already set to 1, skip this step.)
[disxcDo]
easy = value(1)
[\disxcDo]
The value of the configuration item is as follows: 0 means disabled, and 1 means
enabled.
Step 3 Start the U2000 client and server.
Step 4 Restore the U2000 data of the customer to the computer for simulation.
Step 5 Search for protection subnets and SDH trails.
Step 6 Search for discrete services by using the U2000 and save them to a text file
(SDH Disp XC_NEW.txt). Write down the time at which discrete services are saved.
Step 7 Compare the data of discrete services searched out from the simulated
environment SDH Disp XC_NEW.txt with the data of discrete services searched out
from the U2000 of the customer SDH Disp XC_NM1.txt. Open the two files in
Microsoft Excel and use the filter function of the Excel to compare. Normally, the two
files are consistent. If they are inconsistent, analyze the reason. For convenience,
save the txt files as Excel files.
Step 8 Analyze and handle the discrete services in experimental condition and work
out a planning scheme. You could change the NEs to preconfigured NEs in the
U2000. Then perform the planning scheme to check the correctness of it.

 Note:
 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 the SDH NNI discrete services, and finally the pass-through discrete
services.
 For the analysis method, refer to Chapter 3 "Guide of Analyzing Discrete
Services".
Step 9 Use the discrete service remarks function of theU2000 to add the solutions of
discrete services to the remarks. Add the flag of acknowledgement to the analyzed
discrete services, for distinguishing.
Step 10 After discrete services are analyzed, confirm and check the solutions and
measurements, especially the information of discrete services that are regarded as
junk services, with the customer. Optimize the measurements of handling discrete
services according to the result. Set the final solution of clearing discrete services.
Step 11 Export the data of discrete services that have analysis handling results from
the U2000 in the simulated environment, open the data in the Excel, and save it as an
Excel file. Use the filtering and find functions of the Excel to map the discrete services
in the Excel file to discrete services in the network of the customer, to simplify the
handling.
 Note:
Analyze and verify discrete services in the simulated environment. When necessary,
send the discrete services that have no analysis results to the library of Huawei R&D
Dept. for analysis.
2.3 Clearing and Verifying Discrete Services According to

Clearance Solution on the U2000 of the Customer
According to the simulated environment, set the solution of clearing discrete services,
analyze the operation risks, set the protection measurements against risks, and
simplify the procedure. The operations that have potential risks should be performed
in the period of 0:00 to 4:00.

Set solutions of clearing discrete services and relevant details with the customer, set
protection measurements against risks, and avoid affecting services of the customer.
Clear discrete services that exist on the U2000 of the customer.
Caution:
 Before and after a service is deleted, the service department should confirm the
service usage situation
 Before you delete a service, deactivate it. Then, view alarms. If there is no alarm
such as PS or TU-AIS, the service is a junk service. If there are alarms, the
analysis result may be incorrect. In this case, you need to promptly activate the
service.
 Keep a standby U2000 on site. When an error occurs during the service
clearance, use the standby U2000 to restore.
After clearance, verify that discrete services are cleared, trail management is realized
in the entire network, and there is no abnormal alarm.
According to the clearance result, supplement and optimize the original clearance
solution, consolidate and share the experience of service clearance.
2.4 Guiding the Customer to Use Trail Management After

Clearance to Avoid New Discrete Services
Use the trail management function to configure services whenever possible. This is
because services configured in this way do not form discrete services.
To avoid the recurrence of many discrete services, before the customer configures
services, guide the customer to read the online Help or Operator Guide of the U2000,
and help them to learn the standard and requirements of service configuration in each
networking.
When a discrete service is found, handle it as soon as possible so that it does not
affect subsequent service configuration.

 Note:
For the standard and guide of service configuration, refer to the descriptions of
managing SDH networks by using the trail management function and managing SDH
networks on a per-NE basis in the online Help or Operator Guide of the U2000.

Guide of Analyzing Discrete ServicesGuid
iManager U2000 Discrete Service Handling e of Analyzing Discrete Services
Chapter 3 Guide of Analyzing Discrete Services
The personnel of analyzing discrete services should meet the following requirements:
 Be familiar with operations on the U2000. Know the concept and generation
cause of the discrete service.
 Have clear understanding of trail configuration in each protection subnet and
cross-connection configuration on a per-NE basis. These requirements ensure
the analysis on the integrity of service configuration.
3.1 Handling the Discrete Service Caused by Incomplete or

Incomplete Configuration of Actual Services on an NE
This is the common cause of the discrete service, and is also the most confusing
cause. Usually, services in a real network run normally, but a cross-connection on the
U2000 is a discrete service and does not form a trail. This trail is incomplete, that is
the working or protection route is incomplete.
3.1.1 Cross-Connection of Protection Trail Is Not Configured
This situation usually exists on a ring such as a PP or SNCP ring. See Figure 1.4.
ADM2, which is a node on the ring, is not configured with a pass-through service. As
a result, the protection route is incomplete and the trail cannot be formed.
Cause: There is a node without service configuration thus the protection trail is
incomplete and the trail could not come into being.
Figure 1.4 Cross-connection of the protection trail is not configured

Method: Configure the protection service on the U2000 and then perform trail search.
3.1.2 Incomplete Trail Caused by Incorrect SNCP Service Configuration
Cause: The service at ADM 3 of SNCP ring is not an SNCP service. As a result, the
protection trail is incorrect and the trail cannot be formed. See Figure 1.5.
Figure 1.5 Incorrect SNCP service configuration
The cause is that node ADM3 is configured with a normal service, not an SNCP
service. See Figure 1.6. Use the function of configuring a service on a per-NE basis
to configure the service on node ADM3. If you click Create, a normal service is
created. In this example, when you create the service on a per-NE basis on node
ADM3, you should click Create SNCP Service to create an SNCP service.

Figure 1.6 Configuring a service on a per-NE basis
Method: Delete the old cross-connection, configure an SNCP service at NM, and
perform trail search.
3.1.3 Cross-Connection of the Protection Trail Is Incorrect
Network: See Figure 1.7. ADM 2 forms PP ring with ADM 1 and ADM 3 by 11-SL4-1
and 12-SL4-1. But the cross-connection at ADM 2 is 11-SL4-1-VC4-1 ->> 13-SL4-1-
VC4-1.
Cause: The service should be 11-SL4-1-VC4-1 ->> 12-SL4-1-VC4-1 so the cross-

connection is incorrect.

Figure 1.7 Incorrect cross-connection of the protection trail
Method: Delete the incorrect cross-connection, configure the correct service on the
U2000, and perform trail search.
3.1.4 Redundant or Incomplete Service Configuration
Broadcast trail (one source and several sinks) consists of several trails. If one trail is
not completed, the whole broadcast trail can not come into being and all the cross-
connections at NM are discrete services.
Cause: See Figure 1.8. For the broadcast trail, if node Sink1 has no pass-through
service, trails Source-Sink3 and Source-Sink4 are incomplete. As a result, the
broadcast trail cannot be formed.
Figure 1.8 Broadcast trail
Method: Configure a unidirectional pass-through service on node Sink1 and perform

trail search again.

3.2 Handling the Discrete Service Caused by the Existence

of NNI Services
Because the trail of an NNI service is not terminated in the network that the U2000
manages, the U2000 cannot form the trail. As a result, discrete services occur. For
easy trail management, you need to form a trail by using the part of the service that is
on the U2000. To form a trail, you can configure an NNI optical interface or a virtual
(preconfigured) NE. See Figure 1.9.
Figure 1.9 SDH NNI services
The U2000 manages NE1 through NE4, but is not able to manage T1 through T3
(equipment of other vendors). NE1 and NE2 have the S1 and S2 services to T1
respectively. IN addition, the S3 service exists between T2 and T3.
To search for three services as trails, do as follows:
For the S1 service, if NE2 is of release 4.0, you need to create SDH NNIs at NE2 for
SDH NNI services and then search trails. In this way, the cross-connections on NE1
and NE2 can be searched out as a trail between NE1 and NE2.
For the S2 service, create T1 as a preconfigured NE or a release 5.0 virtual NE. You
should also create the fiber between T1 and NE2, and then create the subnet
consisting of T1 and NE2. Configure the single-station service on T1 in association
with the service on NE2. Perform the trail search to search the trail between NE1 and
T1.
For the S3 service, create T2 and T3 as preconfigured NEs or release 5.0 virtual NEs,
create the fibers between T2/T3 and NE4, and then create the subnet consisting of
T2, NE4 and T3. Configure single-station services on T2 and T3 respectively. Perform
the trail search to search the trail between T2 and T3.

 Note:
 Create several virtual NEs or preconfigured NEs, create fiber connections and a
protection subnet, configure cross-connections on a per-NE basis, and then
perform trail search.
 Virtual NEs and preconfigured NEs do not use the number of managed NEs
defined in the license. The data (protection groups and services) of a virtual NE
should be configured according to the rules of release 5.0 NE.
3.3 Junk Service
Discrete services that are not in use are called junk services. Deleting junk services
does not affect the normally running of the NE. Usually the junk services come into
being because the cross-connections are not deleted in time when capacity
expansion or services adjustment.
You can also analyze whether a discrete service is a junk service. For this, the
concept of landing (or termination) is introduced. The previous description focuses on
the integrity of the trail. Another focus is the landing (termination) of the trail. The
source and sink of a VC4, VC3, or VC12 trail should be terminated on a tributary
board, an NNI, or a virtual NE. See Figure 1.10. One end of the service is not landed
(terminated), so the service is a discrete service.
Figure 1.10 Junk services
Method: You can delete discrete services that are regarded as junk services, after
checking and confirming with the customer.

 Note:
Before deleting cross-connections, you can deactivate them and wait for a moment. If
there are new alarms like PS, TU-AIS, or AU-AIS, activate cross-connections
immediately. Otherwise, you could delete the cross-connections and perform trail
search.

Discrete Service Analysis PracticeDiscret
iManager U2000 Discrete Service Handling e Service Analysis Practice
Chapter 4 Discrete Service Analysis Practice
This section describes the method of analyzing discrete services and the
corresponding handling measurements by analyzing the actual discrete services.
 Requirement
Searching out all the trail resources and there are no discrete services by importing to
U2000.
 Practice material
Script files: U2000Discrete Service Practice Script.rar.
U2000 Discrete
Service Practice Script.rar
Network: 9-SL4-1 and 14-SL4-1 of NE70 form PP ring with NE188 and NE199 which
are out of the NM.

Figure 1.11 Networking
 Trail resource list (total 21 trails)
No. Source Sink Direction
1 NE71-PD1-1-1 NE70-PD1-1-1 bidirectional
2–11 NE188-2-PD1-(1-10) NE199-3-PD1-(1-10) bidirectional
12 NE70-2-PD1-1 NE188-2-PD1-11 bidirectional
NE82-1-PD1-1
17 NE81-1-PD1-1 broadcast trail
NE83-1-PD1-1

No. Source Sink Direction
NE84-1-PD1-2
19 NE83-1-PD1-2 broadcast trail
NE85-1-PD1-2
 Discrete service analysis practice
Refer to the U2000 Discrete Service Analysis Practice.ppt.
U2000 Discrete
Service Analysis Practice.ppt

IManager U2000 Discrete Service Handling - 02

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

IManager U2000 Discrete Service Handling - 02

Caricato da

Copyright:

Formati disponibili

iManager U2000 Discrete Service Handling INTERNAL

Document Code Product Name U2000

Intended Reader Optical Network Engineer Product Version V100R001C00

Optical Network Product

iManager U2000 Discrete Service

Drafted by Zhong Jianjuan Date May 30, 2009

Huawei Technologies Co., Ltd.

2009-10-23 Huawei Confidential. No disclosure without permission. Page 1 of 30

All Rights Reserved.

2009-10-23 Huawei Confidential. No disclosure without permission. Page 2 of 30

Date Issue Author Description

Completed the first draft. The

Modified the product and document

2009-10-23 Huawei Confidential. No disclosure without permission. Page 3 of 30

Chapter 2 Procedure for Clearing Discrete Services..................................................................15

Chapter 3 Guide of Analyzing Discrete Services........................................................................20

Chapter 4 Discrete Service Analysis Practice..................................................................................27

2009-10-23 Huawei Confidential. No disclosure without permission. Page 4 of 30

Figure 1-1 Fully unidirectional trail........................................................................................... 7

Figure 1-2 Partly unidirectional trail.......................................................................................... 8

Figure 1-3 SDH NNI services................................................................................................... 9

Figure 3-1 Cross-connection of the protection trail is not configured.....................................20

Figure 3-2 Incorrect SNCP service configuration...................................................................21

Figure 3-3 Configuring a service on a per-NE basis...............................................................22

Figure 3-4 Incorrect cross-connection of the protection trail..................................................23

Figure 3-5 Broadcast trail....................................................................................................... 23

Figure 3-6 SDH NNI services.................................................................................................24

Figure 3-7 Junk services........................................................................................................ 25

Figure 4-1 Networking............................................................................................................ 28

2009-10-23 Huawei Confidential. No disclosure without permission. Page 5 of 30

2009-10-23 Huawei Confidential. No disclosure without permission. Page 6 of 30

1.1 Basic Concepts

1.1.1 Discrete Service

Trail is a type of transmission entity. It consists of a pair of "unidirectional trail" which

2009-10-23 Huawei Confidential. No disclosure without permission. Page 7 of 30

Features of the trail are as follows:

Trails are complete. Incomplete cross-connections become discrete services. See

Figure 1.1 Fully unidirectional trail

2009-10-23 Huawei Confidential. No disclosure without permission. Page 8 of 30

Figure 1.2 Partly unidirectional trail

1.2 Causes of Discrete Services

1.2.1 Unsatisfied Trail Search Conditions

The data on the U2000 is inconsistent with the data on NEs.

Protection subnets are not created or cannot be searched.

The NE data configuration is incorrect. For example, a non-protection chain service is

1.2.2 U2000 Trail Search Restrictions

2009-10-23 Huawei Confidential. No disclosure without permission. Page 9 of 30

1.2.3 Incomplete or Incorrect Configuration of Cross-Connections

The timeslot configured for the protection route is incorrect.

The SNCP service configuration is incorrect, which results in an incomplete protection

The service configuration is incomplete. Check whether incomplete services are

1.2.4 Existence of SDH NNI Services

Figure 1.3 SDH NNI services

1.3 Impacts of Discrete Services

2009-10-23 Huawei Confidential. No disclosure without permission. Page 10 of 30

On trail resource query:

2009-10-23 Huawei Confidential. No disclosure without permission. Page 11 of 30

On timeslot allocation diagram:

1.3.1 SDH Discrete Service Management Function on the U2000

2009-10-23 Huawei Confidential. No disclosure without permission. Page 12 of 30

Specify the filter criteria and click Filter.

2009-10-23 Huawei Confidential. No disclosure without permission. Page 13 of 30

2009-10-23 Huawei Confidential. No disclosure without permission. Page 14 of 30