1830 PSS OTN Layer Management

06.07.
2017 1830 PSS OTN layer management
1830 PSS OTN layer management
Contents
1. Purpose
2. 13. 1830 PSS optical trail management
2.1. Purpose
2.2. OTN — Introduction
2.2.1. Overview
2.2.1.1. OTN
2.2.1.2. Forward error correction
2.2.1.3. OTN layers
2.3. OTN trail management
2.3.1. Workflow to manage OTN trails from the 5620 SAM
2.3.1.1. Workflow
2.3.1.2. Process
2.3.2. Manage OTN trails from the 5620 SAM
2.3.2.1. OTN layer navigation using the 5620 SAM
2.3.2.2. Force XC creation
2.3.2.3. Delay measurement for OTH path
2.4. Optical trail configuration procedures
2.4.1. Procedure 131: To configure an ODU trail
2.4.1.1. Steps
2.4.2. Procedure 132: To discover services associated with ODU trails
2.4.2.1. Steps
2.4.3. Procedure 133: To configure path constraints for ODU trails
2.4.3.1. Steps
2.4.4. Procedure 134: To modify the protection and route of an ODU trail
2.4.4.1. Steps
2.4.5. Procedure 135: To configure an ODUCTP
2.4.5.1. Steps
2.4.6. Procedure 136: To configure an OTU trail
2.4.6.1. Steps
2.4.7. Procedure 137: To autodiscover an OTU trail
2.4.7.1. Steps
2.4.8. Procedure 138: To discover client trails from an OTU trail
2.4.8.1. Steps
2.4.9. Procedure 139: To configure an OCH trail
2.4.9.1. Steps
2.4.10. Procedure 1310: To autoconfigure an OMS trail
2.4.10.1. Steps
2.4.11. Procedure 1311: To view an OTS trail
2.4.11.1. Steps
2.4.12. Procedure 1312: To discover optical trails
2.4.12.1. Steps
2.4.13. Procedure 1313: To view the optical channel usage
2.4.13.1. Steps
3. 14. 1830 PSS OTH facility management
3.1. Purpose
3.2. OTH facility
3.2.1. Overview
3.2.1.1. Autoconfigured OTH facilites
3.2.1.2. Transmitted trail trace identifier
3.2.1.3. OTUk facility
3.2.1.4. ODUk and NIM facilities
3.2.1.5. ODUPTF facility
3.2.1.6. OMS, OTS, OMSOCH, and OMSOCHIF facilities
3.2.1.7. OCH, GBE, and OCN facilities
3.3. ODUk and virtual OCH crossconnections
3.3.1. ODUk crossconnection
3.3.1.1. Overview
3.3.2. Virtual OCH crossconnections
3.3.2.1. Overview
3.3.3. Procedure 141: To configure ODUk crossconnects
3.3.3.1. Steps
3.3.4. Procedure 142: To substructure ODUk timeslots
3.3.4.1. Steps
3.4. ODUk protection groups
3.4.1. Overview
3.4.1.1. Introduction
3.4.2. Procedure 143: To configure ingress path overhead monitoring
3.4.2.1. Steps
3.4.3. Procedure 144: To configure ODUk protection groups
3.4.3.1. Steps
3.4.4. Procedure 145: To configure 1:N ODUk protection groups
3.4.4.1. 1:N ODUk protection groups
3.4.4.2. Steps
https://infocenter.alcatellucent.com/public/5620SAM130R6A/advanced/print.jsp?topic=/SAM_OUG/html/qzx68.html&cp=10_8 1/20
06.07.2017 1830 PSS OTN layer management
3.4.5. Procedure 146: To configure protection switching
3.4.5.1. Steps
Part VI: 1830 PSS OTN layer management Previous
Overview
Purpose
This chapter describes the OTN layer and OTH facility management from the 5620 SAM.
Contents
Chapter 13, 1830 PSS optical trail management
Chapter 14, 1830 PSS OTH facility management
2. Chapter 13: 1830 PSS optical trail management Previous
Overview
Purpose
This chapter describes the OTN layer management from the 5620 SAM.
Contents
OTN — Introduction
OTN trail management
Workflow to manage OTN trails from the 5620 SAM
Manage OTN trails from the 5620 SAM
Optical trail configuration procedures
Procedure 131: To configure an ODU trail
Procedure 132: To discover services associated with ODU trails
Procedure 133: To configure path constraints for ODU trails
Procedure 134: To modify the protection and route of an ODU trail
Procedure 135: To configure an ODUCTP
Procedure 136: To configure an OTU trail
Procedure 137: To autodiscover an OTU trail
Procedure 138: To discover client trails from an OTU trail
Procedure 139: To configure an OCH trail
Procedure 1310: To autoconfigure an OMS trail
Procedure 1311: To view an OTS trail
Procedure 1312: To discover optical trails
Procedure 1313: To view the optical channel usage
2.2. OTN — Introduction Previous
Overview
2.2.1. Overview Previous
OTN
OTN is an ITUT standard (G.709) that describes a method for wrapping signals of different protocols for transport across
an optical network. OTN provides transport, multiplexing, routing, management, supervision, and survivability functions
for optical channels that carry client signals.
OTN has the following advantages over SDH and SONET:
stronger forward error correction mechanisms
more levels of tandem connection monitoring
transparent transport of client signals
switching scalability
Forward error correction
Forward error correction is a method to lower the BER of an optical line signal by adding redundant information, which can
be used to correct bit errors that occur when the signal is transmitted over long distances.
The 5620 SAM allows the following forward error correction options for 1830 PSS devices:
SDFEC RSFEC
AFEC EFEC
UFEC EFEC2
SDFEC provides higher error correction when compared to AFEC. The 130SCX10 OT card supports configuration of SDFEC
on the line port.
The latency on the 11DPE12A, 11OPE8, 11QCE12X, and 11QPE24 cards is optimized by setting the FEC Mode parameter to
No FEC under the Port Specifics tab of the respective Physical Port (Edit) forms.
OTN layers
The following layers are defined in OTN.
OPU—information structure that is used to encapsulate client information for transport over an optical channel.
ODU—consists of the OPU information payload and the ODUspecific overhead.
OTU—information structure that is required to transport an ODU over an optical channel.
OCH—an optical channel that transports a digital client signal between reamplification, reshaping, and retiming (3R)
regeneration points.
OMS—provides multiplexing of several wavelengths.
OTS—provides transmission of optical signals across various types of optical media.
2.3. OTN trail management Previous
Workflow to manage OTN trails from the 5620 SAM
Manage OTN trails from the 5620 SAM
2.3.1. Workflow to manage OTN trails from the 5620 SAM Previous
Workflow
The workflow to manage the OTN trails is described in this topic.
Process

1 Configure the ODU trails; see Procedure 131: To configure an ODU trail .
If required:
discover the services associated with the ODU trails; see Procedure 132: To discover services associated with
ODU trails .
configure the path constraints for ODU trails; see Procedure 133: To configure path constraints for ODU trails .
change the protection type of the ODU trails; see Procedure 134: To modify the protection and route of an ODU
trail .
configure the ODUCTPs; see Procedure 135: To configure an ODUCTP .
2 Configure the OTU trails; see Procedure 136: To configure an OTU trail .
If required:
autodiscover the OTU trails; see Procedure 137: To autodiscover an OTU trail .
discover the client trails from the OTU trails; see Procedure 138: To discover client trails from an OTU trail .
3 Configure the OCH trails; see Procedure 139: To configure an OCH trail .
4 Autoconfigure the OMS trails; see Procedure 1310: To autoconfigure an OMS trail .
5 View the OTS trails; see Procedure 1311: To view an OTS trail .
6 If required, discover the optical trails; see Procedure 1312: To discover optical trails .
7 If required, view the optical channel usage; see Procedure 1313: To view the optical channel usage .
2.3.2. Manage OTN trails from the 5620 SAM Previous
OTN layer navigation using the 5620 SAM
The optical trail configuration forms allow you to create optical trails in the 5620 SAM. You can access the optical trail
configuration forms from the Create menu or the Manage menu. Figures Figure 131, Optical trail configuration form
navigation from Create menu and Figure 132, Optical trail configuration form navigation from Manage menushow both
methods of accessing optical trail configuration forms.
Figure 131: Optical trail configuration form navigation from Create menu
Figure 132: Optical trail configuration form navigation from Manage menu
The navigation tree of an optical trail configuration form lists the sites, termination points, and trail paths that are
configured for the optical trail.
Table 131, Navigation tree objects describes the objects on the navigation tree of the optical trail configuration form,
which the 5620 SAM allows you to create and manage.
Table 131: Navigation tree objects
Object Description
Sites Contains the Site A and Site Z attribute information
Site A End Child objects of the Sites object
Site Z End
Termination Point Located under the Site A End and Site Z End objects.
Contains the termination point attribute information.
Termination Point Working Child objects of the Termination Point object.
Trail Paths Contains the optical trail path attribute information.
<ODU/OTU/OCH> Trail Path, Mode: Working Child object of the Trail Paths object.
<ODU/OTU/OCH> Trail Path, Mode: Protection
Figure 133, Optical trail navigation tree objects shows the navigation tree objects that you can manage in the optical trail
configuration forms.
Figure 133: Optical trail navigation tree objects
The 5620 SAM allows you to navigate to the underlying OTN layers from the Service or Trail Paths of the Optical Transport
Service, Multipoint Transport Service, ODU Trail, and OTU Trail configuration forms. Figure 134, OTN layer navigation
from Optical Transport Service form shows the trail hierarchy on the navigation tree of the Optical Transport Service form
and Figure 135, OTN layer navigation from trail ODU Trail form shows the trail hierarchy on the navigation tree of the
ODU Trail form.
Figure 134: OTN layer navigation from Optical Transport Service form
Figure 135: OTN layer navigation from trail ODU Trail form
Force XC creation
The 5620 SAM allows you to create OCH XCs even while the power commissioning is in progress. This option is available
during the configuration of:
OTU trails
ODU trails
OCH trails
optical transport service
multipoint transport service
During a service or trail configuration, you can enable the Force Create OCH XC check box on the configuration forms and
bypass the check to ensure that the OCH XCs are successfully power commissioned.
Note: The 5620 SAM displays a deployment error if you attempt to configure a service or an optical trail when the power
commissioning is in progress. The deployment error will not halt service or trail creation.
After a service or trail configuration, you can enable the Force Create OCH XC check box on the configuration forms and
click Complete service or Complete Trail to complete the service or trail configuration.
Delay measurement for OTH path
The 5620 SAM allows you to initiate an ondemand delay measurement for an ODU trail. The following OTs can perform an
ondemand delay measurement of ODU trails:
11QPA4 130SCX10
11QPEN4 130SNX10
112SDX11 260SCX2
To initiate a delay measurement, click More Actions on the ODU Trail (Edit) form and choose Delay Measurement→Start.
Upon retrieval of the delay measurement values, the DM Current Status and the DM Current Value (us) parameters are
updated in the ODU Trail (Edit) form.
To stop the delay measurement, click More Actions on the ODU Trail (Edit) form and choose Delay Measurement→Stop.
The line ports also display the following delay measurement parameters on the General tab of the Physical Port (Edit)
form:
Connection Monitoring End Point Mode
DM Current Status
DM Current Value (us)
The Connection Monitoring End Point Mode parameter can be set to ByPass, Source, or Destination. The value is set to
ByPass by default.
2.4. Optical trail configuration procedures Previous
Procedure 131: To configure an ODU trail
Procedure 132: To discover services associated with ODU trails
Procedure 133: To configure path constraints for ODU trails
Procedure 134: To modify the protection and route of an ODU trail
Procedure 135: To configure an ODUCTP
Procedure 136: To configure an OTU trail
Procedure 137: To autodiscover an OTU trail
Procedure 138: To discover client trails from an OTU trail
Procedure 139: To configure an OCH trail
Procedure 1310: To autoconfigure an OMS trail
Procedure 1311: To view an OTS trail
Procedure 1312: To discover optical trails
Procedure 1313: To view the optical channel usage
2.4.1. Procedure 131: To configure an ODU trail Previous
Before you begin
Ensure that the rate and transmit frequency are configured before creating the ODU trail.
Steps

1 Choose Create→OTN→ODU Trail from the 5620 SAM main menu. The ODU Trail (Create) form opens.
2 Select a customer in the Customer panel and configure the required parameters.
Note: The Trail ID parameter is configurable when the AutoAssign ID parameter is disabled.
If you configure the Protection Type parameter as Segment Protected, the Path Search Option parameter is set to
User Defined by default and cannot be configured.
If you configure the Protection Type parameter as Segment Protected, the path constraints need to be configured.
See Step 12 .
3 Configure the Wave Key Assign Mode parameter in the OTU/OCH Details panel.
4 Configure the required parameters in the ODUk Attributes panel.
5 Configure the required parameters in the TTI Attributes panel.
Note: Configure the AZ Source Tx TTI, ZA Source Tx TTI, AZ Destination Tx TTI, and ZA Destination Tx TTI
parameters for OCS nodes.
Configure the AZ Transmitted TTI, ZA Transmitted TTI, AZ Expected TTI, and ZA Expected TTI parameters for
WDM nodes.
6 Configure the Administrative State parameter in the States panel.
7 Rightclick on the Sites object on the navigation tree and choose Create Trail Site. The Select Network Elements
ODU Trail form opens with a list of 1830 PSS WDM and OCS devices.
8 Select two sites and click OK. The site objects appear on the navigation tree.
9 Rightclick on the Site A End object on the navigation tree and choose Create Trail Termination Point. The Select
Termination Point ODU Trail form opens.
10 Choose the termination point and click OK. The termination point objects appear on the navigation tree.
11 Repeat Step 9 to Step 10 to configure the Site Z End.
12 Configure the path constraints, if required. See Procedure 133: To configure path constraints for ODU trails .
13 Click Apply. The form name changes to ODU Trail (Edit) form.
14 Expand the Trail Paths object on the navigation tree and click on the ODU Trail Path object to view the properties of
the ODU trail.
15 Close the ODU Trail (Edit) form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.2. Procedure 132: To discover services associated with ODU Previous
trails
Steps

1 Choose Manage→OTN→OTN Trails from the 5620 SAM main menu. The Manage OTN Trails form opens.
2 Choose ODU Trail (Optical Management) from the object dropdown menu. A list of ODU trails appears.
3 Choose an ODU trail and click Properties. The ODU Trail (Edit) form opens.
4 Click on the Transported Services tab and click Discover Services. The service is listed in the ODU Trail (Edit) form
and the Used By a Service check box of the Manage OTN Trails Form is selected.
5 Close the Manage OTN Trails form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.3. Procedure 133: To configure path constraints for ODU Previous
trails
Steps

1 Perform one of the following:
a. To configure path constraints during an optical trail configuration:
1. Configure an ODU trail. See Procedure 131: To configure an ODU trail .
2. Click on the Path Constraints tab on the ODU Trail (Create) form.
b. To configure path constraints for an existing ODU trail:
1. Choose Manage→OTN→OTN Trails from the 5620 SAM main menu. The Manage OTN Trails form opens.
2. Choose ODU Trail (Optical Management) from the object dropdown menu. The OTU trails are listed.
3. Choose an ODU trail and click Properties. The OTU/ODU/OCH Trail (Edit) form opens.
4. Click on the Path Constraints tab.
2 Click Create. The Optical Path Constraint (Create) form opens.
3 Configure the required parameters.
Choose Exclusion to exclude the constraint element from the trail path and choose Inclusion to include the constraint
element in the trail path.
ODUk Rate is applicable only when the Constraint Element is ODUk Timeslot.
To apply the direction for a path constraint, configure the Direction parameter.
4 Configure the Service Path Type parameter for the Protected ODU trail.
a. If the constraint element is a port:
1. Select a site on the Site panel.
2. Select a port on the Port panel.
b. If the constraint element is a site, select a site on the Site panel.
c. If the constraint element is a trail, select a trail on the Trail panel.
d. If the constraint element is an ODUk timeslot:
1. Configure the ODUk Rate parameter.
3. Select an ODUk Timeslot on the ODUk Timeslot panel.
e. If the constraint element is an optical link:
2. Select an optical link on the Optical Link panel.
6 Click OK. The Optical Path Constraint (Create) form closes and the ODU Trail (Edit) form reappears.
7 Click Apply to save the changes.
8 Expand the Trail Paths object on the navigation tree and expand the ODU Trail Path object.
9 Click on the Hops A to Z tab to verify the inclusion or exclusion of the path constraint.
10 Close the form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.4. Procedure 134: To modify the protection and route of an
ODU trail
Note:
The 5620 SAM supports the following modifications of protection and route of the HOODU and LOODU trails:
unprotected to SNCN protected
SNCN protected to unprotected
unprotected to SNCNC protected
SNCNC protected to unprotected
unprotected to segment protected
segment protected to unprotected
route modification for HOODU (OCS to OCS and OCS to 1830 PSS32 in the intermediate nodes only)
route modification for LOODU (OCS to OCS and OCS to 1830 PSS32)
Steps

2 Choose ODU Trail (Optical Management) from the object dropdown menu.
3 Choose an ODU trail and click Properties. The ODU Trail (Edit) form opens.
5 Configure the Protection Type parameter depending on the conversion from protected to unprotected or unprotected
to protected.
Note: The modification of the Protection Type parameter results in the deletion of the APS groups.
6 Perform one of the following.
a. Convert a segment protected, SNCN protected, or SNCNC protected ODU trail to an unprotected ODU trail,
configure the Path Preference parameter to indicate the path that needs to be retained as the unprotected path.
b. Convert an unprotected ODU trail to an segment protected, SNCN protected, or SNCNC protected ODU trail:
1. Right click on the Site A End and choose Create Trail Termination Point. The Select Termination Point ODU
Trail form with a list of termination points opens.
2. Choose a termination point from the list and click OK. The Select Termination Point ODU Trail form closes
and the termination point is added to the ODU Trail navigation tree.
3. Perform 1 and 2 on Site Z End and add termination point, as required.
7 Configure path constraints, as required. See Procedure 133: To configure path constraints for ODU trails for more
information about configuring the path constraints.
8 Click Apply.
9 Expand the Trail Paths object on the navigation tree to view the trail path attributes.
When you convert a protected ODU trail to an unprotected ODU trail, only the unprotected path object appears
instead of the working and protection path objects
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.5. Procedure 135: To configure an ODUCTP
Steps

1 On the equipment tree, expand Network→1830 PSS→Shelf→Card→Line Port→ODU.
2 Rightclick on the ODU object and choose Properties. The Odu Ctp (Edit) form opens.
3 Configure the required parameters in the ODUk Attributes panel.
Note: You can enter the Transmitted TTI and Expected TTI values up to 15 characters for 1830 PSS devices and up to
64 characters for other devices.
5 Save your changes and close the form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.6. Procedure 136: To configure an OTU trail
Before you begin
Perform the following before creating an OTU trail:
Configure the rate and frequency of the terminating sites.
Create optical links between the terminating sites.
Note:
The OTU trail is created automatically, when you configure an optical link between two OT line ports.
Steps

1 Choose Create→OTN→OTU Trail from the 5620 SAM main menu. The OTU Trail (Create) form opens.
3 Configure the required parameters in the OCH panel.
Note: Configure the AZ Source Tx TTI, ZA Source Tx TTI, AZ Destination TTI, and ZA Destination TTI parameters
for OCS nodes.
Configure the AZ Transmitted TTI, ZA Transmitted TTI, AZ Expected TTI, and ZA Expected TTI parameters for
WDM nodes.
OTU Trail form opens with a list of 1830 PSS devices.
7 Choose two sites from the list and click OK. The site objects appear on the navigation tree.
8 Rightclick on the Site A End object and choose Create Trail Termination Point. The Select Termination Point form
opens.
9 Choose the termination point and click OK. The Termination Point object appears on the navigation tree below the Site
A End object.
11 Expand the Site A End and Site Z End objects on the navigation tree, to view the termination points added on the
navigation tree.
12 Click Apply to save the changes. The form name changes to OTU Trail (Edit) form.
13 Expand the Trail Paths object on the navigation tree and click on the OTU Trail Path object to view the properties of
the OTU trail.
14 Close the OTU Trail (Edit) form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.7. Procedure 137: To autodiscover an OTU trail
Steps

1 Configure internal topological links between the line port of a hybrid card (OCS) or OT card (WDM) and an SFC
channel port. See Procedure 922: To configure an OCS topological link for more information about configuring
topological links.
2 Configure an external topological link between the OMD ports of the participating OCS SFC cards. See Procedure 9
22: To configure an OCS topological link for more information about configuring topological links.
4 Click Discover Optical Trails. The Discover Optical Trails form opens with a list of equipment groups.
5 Choose a equipment group and click OK. The OTN trails are listed in the Manage OTN Trails form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.8. Procedure 138: To discover client trails from an OTU trail
Note: When an OTU trail exists between the client port of a 130SCX10 card and a line port of a 11DPM12 card on the
same device, you can discover the client trail from the OTU Trail (Edit) form.
Steps

2 Choose OTU Trail (Optical Management) from the object dropdown list. A list of OTU trails appears.
3 Choose the required OTU trail and click Properties. The OTU Trail (Edit) form opens.
4 Click on the OTU Trail object on the navigation tree of the OTU Trail (Edit) form.
5 Click Discover Client Trails and click on the HOODU Trails tab. The discovered ODU trail is listed on the HOODU Trails
tab.
6 Close the OTU Trail (Edit) form. The Manage OTN Trails form reappears.
7 Choose ODU Trail (Optical Management) from the object dropdown list. A list of ODU trails appears. The ODU trail
discovered on the OTU Trail form is displayed in the list.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.9. Procedure 139: To configure an OCH trail
Before you begin
The following points should be considered before creating the OCH trail:
Configure the rate, transmit frequency, and receive frequency of the terminating sites.
Create optical links between the terminating sites.
Steps

1 Choose Create→OTN→OCH Trail from the 5620 SAM main menu. The OCH Trail (Create) form opens.
3 Configure the required parameters in the OCH panel.
OCH Trail form opens.
6 Choose two sites from the list and click OK. The site objects are added on the navigation tree.
7 Right click on the Site A End object on the navigation tree and choose Create Trail Termination Point. The Select
Termination Point OCH Trail form opens.
8 Choose the termination point and click OK. The termination point objects appear on the navigation tree.
10 Click Apply. The form names changes to OCH Trail (Edit) form.
11 Expand the Trail Paths object on the navigation tree and click on the OCH Trail Path object to view the properties of
the OCH trail.
12 Close the OCH Trail (Edit) form.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.10. Procedure 1310: To autoconfigure an OMS trail
Steps

1 Configure an internal topological link between the line port of a hybrid card in the OCS device and an SFC channel
port in the same OCS device. See Procedure 922: To configure an OCS topological link for more information about
configuring topological links.
2 Configure one of the following to autoconfigure an OMS trail:
a. an external topological link from the OMD port of the participating SFC card in the OCS device to the OMD port of
an SFC card in another OCS device. See Procedure 922: To configure an OCS topological link for more
information about configuring topological links.
b. an external topological link from the OMD port of the participating SFC card in the OCS device to the OMD port of
an SFC card in a WDM device. See Procedure 922: To configure an OCS topological link for more information
about configuring topological links.
3 To view the autoconfigured OMS trail, choose Manage→OTN→OTN Trails from the 5620 SAM main menu. The Manage
OTN Trails form opens.
4 Choose OMS Trail (Optical Management) from the object dropdown menu. The autocreated OMS trail is listed.
Note: The OMS trails are deleted when the external topological links configured in Step 2 are deleted.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.11. Procedure 1311: To view an OTS trail
Steps

2 Choose OTS Trail (Optical Management) from the object dropdown menu. A list of OTS trails appears.
3 Choose an OTS trail and click Properties. The OTS Trail (Edit) form opens.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.12. Procedure 1312: To discover optical trails
Steps

2 Click Discover Optical Trails. The Discover Optical Trails form opens with a list of equipment groups.
3 Choose a equipment group and click OK. A list of optical trails in the group appears.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
2.4.13. Procedure 1313: To view the optical channel usage
Steps

2 Choose Optical Channel Usage (Optical Management) from the object dropdown menu. The optical channel usage list
appears.
3 Choose a channel and click Properties. The Optical Channel Usage (View) form opens.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3. Chapter 14: 1830 PSS OTH facility management
Overview
Purpose
This chapter provide information about the OTH facilities.
Contents
OTH facility
ODUk and virtual OCH crossconnections
ODUk crossconnection
Virtual OCH crossconnections
Procedure 141: To configure ODUk crossconnects
Procedure 142: To substructure ODUk timeslots
ODUk protection groups
Procedure 143: To configure ingress path overhead monitoring
Procedure 144: To configure ODUk protection groups
Procedure 145: To configure 1:N ODUk protection groups
Procedure 146: To configure protection switching
3.2. OTH facility
Overview
3.2.1. Overview
Autoconfigured OTH facilites
The 5620 SAM supports autoconfiguration of the following OTH facilities:
OTUk ODUPTF
ODUk OMS
OCH OMSOCH
GBE OMSOCHIF
OCN OTS
Transmitted trail trace identifier
The 5620 SAM supports configuration of the following TTI parameters for the OTH facilities.
Transmit SAPI—transmit source access point identifier, valid for terminated TCM only.
Expected SAPI—expected incoming source access point identifier, valid for termination and nonintrusive monitoring.
Transmit DAPI—transmit destination access point identifier, valid for terminated TCM only.
Expected DAPI—expected incoming destination access point identifier, valid for termination and nonintrusive
monitoring.
Note: The NIM facility objects only have Expected SAPI and Expected DAPI.
The configurations of the TTI parameters can be performed using hexadecimal string format or quoted ASCII string
format.
Hexadecimal string format consists of 31 ASCII characters, that is, X followed by 30 hexadecimal characters. The 15
byte TTI encodes into 30 halfbyte characters in hexadecimal format. The string starts after the allzero header byte
generated by the device.
Quoted ASCII string format consists of 015 ASCII valid input characters. If the value consists of all ASCII NULLs,
then 15 "." characters is displayed. See AlcatelLucent 1830 Photonic Service Switch TL1 Commands and Messages
Guide for more information.
When the Region parameter on the Network Element (Edit) form is set to ETSI, the TTI parameters can be configured
without any restrictions.
When the Region Parameter is set to ANSI and the Command Mode parameter is set to Normal on the Network Element
(Edit) form, the TTI parameters cannot be configured. The Command Mode parameter needs to be set to Forced to
configure the TTI parameters.
The STMN (STM1, STM4, STM16, STM64) facilities can be configured for the ETSI region nodes. The OCN facilities can be
configured for the ANSI region nodes.
OTUk facility
The 5620 SAM autoconfigures the OTUk facility object when the OTUk signal rate is configured on the line or client ports.
ODUk and NIM facilities
An ODUk entity is used for nonintrusive monitoring (NIM). NIM is a method for reporting defects and performance
monitoring for an intermediate path on nonterminated adddrop and through connections.
The 5620 SAM supports the following ODUk facility objects in the physical and virtual planes of the OCS device as listed in
Table 141, ODU facility objects on the 1830 PSS device. The facilities in the physical plane are associated with an OT or
client/line card. The facilities in the virtual plane are associated with the internal shelf matrix. The object IDs for these
facilities have slot number as 71.
Table 141: ODU facility objects on the 1830 PSS device
ODU facility object GUI naming convention Example
Nonterminated HOODUs in the physical OTUODUk<shelf>/<slot>/<port> OTUODU23/3/H1

plane
Nonterminated LOODUs in the virtual plane ODUmODUn<shelf>/71/<HOODU#><LO ODU4ODU11/71/13

ODU#>
Clienttransparent ODUs ODUk<shelf>/<slot>/<client port> ODU11/2/C1
Terminated HOODUs in the virtual plane ODUk<shelf>/71/<ODU#> ODU42/71/1
Nonterminated ODUs
The 5620 SAM supports the following types of nonterminated ODU facilities:
HOODU in the physical plane—OTUODUn
The 5620 SAM autoconfigures the HOODU facility object below the OTU facility object on the navigation tree, when
the port is configured.
LOODU in the virtual plane—ODUmODUn(1xx)(1xx)
The 5620 SAM autoconfigures the ODU facility when the terminated HOODU is autoconfigured as a result of a cross
connect between a nonterminated HOODU and an ODUPOOL.
The 5620 SAM supports autoconfiguration of the following NIM facilities when the signal rates of the I/O card ports are
configured:
130SCUP, 130SCUPB, or 130SCUPC—OTU4 with an unterminated higher order ODU4 (higher order ODU4 NIM)
11QCUPC—OTU2 with an unterminated higher order ODU2 (higher order ODU2 NIM)
43SCUP—OTU3e2 with an unterminated higher order ODU3e2 (higher order ODU3e2 NIM)
10AN10G—OTU2 with an unterminated higher order ODU2 (higher order ODU2 NIM)
4AN10G—OTU2 with an unterminated higher order ODU2 (higher order ODU2 NIM).
Terminated ODUs
The 5620 SAM supports the following types of terminated ODU facilities:
Client transparent ODU—ODUk
The 5620 SAM autoconfigures the ODU facility in the physical plane when a nonOTN port is configured.
HOODU in the virtual plane—ODUk(1xx)
The 5620 SAM autoconfigures the ODU facility in the virtual plane when a crossconnect is configured between a non
terminated HOODU and an ODUPOOL.
ODUPTF facility
The 5620 SAM autoconfigures the ODUPTF when a crossconnect is configured between a nonterminated ODUn and an
ODUPOOL.
The 5620 SAM autoconfigures the ODUPTF facility when a transparently transported GBE10, STM64, OC192, STM16,
OC48, GBE is created.
OMS, OTS, OMSOCH, and OMSOCHIF facilities
The 5620 SAM autoconfigures the OMSOCHIF on the SFC8 channel port when an internal bidirectional optical link is
configured from a 10AN10G or a 4AN10G line port to the SFC8 channel port.
The 5620 SAM autoconfigures the OMS, OTS, and OMSOCH facilities on the OMD port of the SFC8 OMD port when an
internal bidirectional optical link is configured from a 10AN10G or a 4AN10G port to an SFC8 channel port and an external
optical link is configured from the OMD port of the same SFC card to an SFC8 OMD port of a WDM or an OCS node.
OCH, GBE, and OCN facilities
The 5620 SAM autoconfigures the OCH facility when the OCH signal rate is configured on the line or client ports.
The 5620 SAM autoconfigures the GBE facility when 1, 10, or 100 GbE signal rates are configured on the line or client
ports.
The 5620 SAM autoconfigures the OCN facility when OC3, OC12, OC48, or OC192 signal rates are configured on the line
or client ports.
3.3. ODUk and virtual OCH crossconnections
ODUk crossconnection
Virtual OCH crossconnections
Procedure 141: To configure ODUk crossconnects
Procedure 142: To substructure ODUk timeslots
3.3.1. ODUk crossconnection
Overview
The 5620 SAM allows you configure the ODUk crossconnect from:
manage menu—parameter values are not inherited
shelf object—the site and shelf parameter values are inherited from the current device
For more information about configuring an ODUk crossconnect, see Procedure 141: To configure ODUk crossconnects .
The 5620 SAM autoconfigures the HOODUs in the virtual plane when the crossconnects are configured between the non
terminated HOODUs and the ODUPOOLs. The ODUs are listed in the Virtual Plane tab of the Shelf (Edit) form. The 5620
SAM supports substructuring of the ODUs. See Procedure 142: To substructure ODUk timeslots for more information
about substructuring the ODUs.
3.3.2. Virtual OCH crossconnections
Overview
The 5620 SAM autoconfigures a virtual OCH crossconnection when an internal topological link is configured from a line
port of the clientline card to a channel port of an SFC8 card. The virtual crossconnections that are autoconfigured for an
OCS node are listed on the OCH CrossConnects tab on the Network Element (Edit) form. You can choose an entry and
click Properties to open the Virtual Cross Connect (Edit) form.
The 5620 SAM autoconfigures working and protection virtual OCH crossconnections during trail (OCH, OTU, or ODU) or
service configuration or discovery, involving:
OPSA card that is configured with the OCHP mode and located in one node with the OPSA A and B ports connected to
the filter card in an another node
OPSA card that is configured with the OMSP mode and located in one node with the OPSA A and B ports connected to
the OPSA A and B ports on another node.
3.3.3. Procedure 141: To configure ODUk crossconnects
Steps

1 Perform one of the following to open the ODUk Cross Connect (Create) form.
a. From the 5620 SAM main menu.
1. Choose Manage→OTN→ODUk Cross Connects. The Manage ODUk Cross Connects form opens.
2. Click Create. The ODUk Cross Connect (Create) form opens.
3. Go to Step 2 .
b. From the Shelf object on the navigation tree.
1. On the equipment tree, expand Network→NE→Shelf.
2. Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3. Click on the ODUk Cross Connects tab.
4. Click Create. The ODUk Cross Connect (Create) form opens.
5. Go to Step 4 .
2 Select a site for the ODUk cross connect in the Site panel.
3 Select a shelf for the ODUk cross connect in the Shelf panel.
5 If A or Z end needs to terminate on the ODU pool, configure the Termination on ODUPOOL parameter for A or Z end.
6 Select an HOODU facility in the AEnd and ZEnd panels.
7 Save your changes and close the forms.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3.3.4. Procedure 142: To substructure ODUk timeslots
Steps

1 On the equipment tree, expand Network→NE→Shelf.
2 Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
3 Click on the Virtual Plane tab. The HOODUks are listed.
Note: The HOODUk is autoconfigured in the virtual plane when a crossconnect is configured between an ODUPOOL
and a nonterminated HOODU. See Procedure 141: To configure ODUk crossconnects for more information about
configuring ODUk crossconnects.
4 Choose an HOODUk from the list and click Properties. The ODU Path Termination (Edit) form opens.
5 Click on the ODU Structure tab.
6 Choose the LOODUs based on the timeslot mapping in Table 142, ODUk timeslot mapping and click Bind Timeslots.
The LOODUk Configuration form opens.
Table 142: ODUk timeslot mapping
Autoconfigured Rate No of LOODUs to bind No of timeslots Size of the tributary

HOODUk timeslots slot
ODU2 ODU0 1 ODU0 1 1.25G
ODU1 2 ODU0s 2 1.25G
1 ODU01 1 2.5G
ODU3e2 ODU0 1 ODU0 1 1.25G
ODU2 8 ODU0s or 4 ODU1s 8 1.25G
ODU2e 8 ODU0s or 4 ODU1s 8 1.25G
ODU3 32 ODU0s, 16 ODU1s, or 4 ODU2s 32 1.25G
ODU4 ODU0 ODU0 1 1.25G
ODU2 8 ODU0s or 4ODU1s 8 1.25G
ODU2e 8 ODU0s or 4ODU1s 8 1.25G
ODU3 31 ODU0s 31 1.25G
7 Configure the required parameters and click OK.
8 Scroll to the bottom of the list to view the newly created timeslot.
9 Choose a bound timeslot and click Collapse Timeslots to retrieve the initial timeslots.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3.4. ODUk protection groups
Overview
Procedure 143: To configure ingress path overhead monitoring
Procedure 144: To configure ODUk protection groups
Procedure 145: To configure 1:N ODUk protection groups
Procedure 146: To configure protection switching
3.4.1. Overview
Introduction
The 5620 SAM supports the configuration of the ODUk protection groups. The ODUk protection group represents a path
protected crossconnection in the 5620 SAM. The ODUk protection group can be configured for the rate facilities:
ODUPOOL
ODUk NIM
client transparent ODUk
The ODUPOOL path terminated entity is configured as the client facility of the ODUk protection group.
The protected and protecting ingress POMs (Path Overhead Monitoring) needs to be enabled when the ODUk protection
group is configured using the ODUk NIM entities. See Procedure 143: To configure ingress path overhead monitoring for
more information about configuring the POMs.
The working and protecting facilities must be configured as the client transparent ODUk facilities, to configure an SNCNC
protection type of ODUk protection group. The client transparent facilities can be configured as working and protecting, if
they are configured with the SDH or SONET signals rates.
The 5620 SAM allows you configure the ODUk protection groups from the:
manage menu
OCS device object
shelf object (by choosing the unprotected crossconnect)
port object
ODU facility object
For more information about configuring a protection group, see Procedure 144: To configure ODUk protection groups .
The 5620 SAM supports configuration of protection switching to configure either the working or protection path as active
or standby. See Procedure 146: To configure protection switching for more information about configuring a protection
switch.
3.4.2. Procedure 143: To configure ingress path overhead
monitoring
Steps

1 On the equipment tree, expand Network→1830 PSS→Shelf→Port.
2 Rightclick on the port object and choose Properties. The Physical Port (Edit) form opens.
3 Click on the OTUODUk tab, then on the NIM tab. The OTUODU2 source and sink entries are listed.
4 Choose the sink and click Properties. The ODU NIM Point (Edit) form opens.
5 Select the Path Overhead Monitoring checkbox and click OK.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3.4.3. Procedure 144: To configure ODUk protection groups
Steps

1 Perform one of the following to open the ODUk Protection Group (Create) form.
1. Choose Manage→OTN→ODUk Protection Groups. The Manage ODUk Protection Groups form opens.
2. Click Create. The ODUk Protection Group (Create) form opens.
3. Go to Step 2 .
b. From the equipment tree.
1. On the equipment tree, expand Network→1830 PSS.
2. Rightclick on the 1830 PSS object and choose Properties. The Network Element (Edit) form opens.
3. Click on the APS Groups tab.
4. Click Create and choose ODUk APS Group. The ODUk Protection Group (Create) form opens.
5. Go to Step 3 .
c. From the list of ODUk crossconnects on a shelf object or an ODU facility object.
1. On the equipment tree, expand Network→NE→Shelf object or Network→NE→Shelf→Card→Port→ODU facility
object.
2. Perform one of the following:
Rightclick on the Shelf object and choose Properties. The Shelf (Edit) form opens.
Rightclick on the ODUk object and choose Properties. The ODU Path Termination (Edit) form opens.
Rightclick on the OTUODUk object and choose Properties. The ODU NIM (Edit) form opens.
3. Click on the ODUk Cross Connects tab.
4. Choose an unprotected ODUk crossconnect and click Protect. The ODUk Protection Group (Create) form
opens.
5. Go to Step 6 .
d. From the port object on the navigation tree.
1. On the equipment tree, expand Network→1830 PSS→Shelf→Port.
2. Rightclick on the port object and choose Properties. The Physical Port (Edit) form opens.
4. Click Create and choose ODUk APS Group. The ODUk Protection Group (Create) form opens.
e. From the ODU facility object on the navigation tree.
1. On the equipment tree, expand Network→NE→Shelf→Card→Port→ODU object.
Note:
Ensure that the selected facilities are SONET or SDH rates, if you are configuring client transparent
facilities for the working and protection parameters.
Note:
Ensure that the ingress POM is configured before configuring the ODUk protection group for the ODUk NIM
entities. See Procedure 143: To configure ingress path overhead monitoring for more information about
configuring the ingress POM.
3. Click on the APS Group tab.
4. Click Create. The ODUk Protection Group (Create) form opens.
2 Select a site in the Site panel.
3 Select a shelf in the Shelf panel.
a. Configure the Client on ODUPOOL parameter. Go to Step 5 .
b. Select a client in the Client panel.
5 Select a facility object in the Working panel.
Note: Configure the working facility as HOODU NIM, if the Client on ODUPOOL parameter is configured.
6 Select a facility object in the Protection panel.
Note: Configure the protection facility as HOODU NIM, if the Client on ODUPOOL parameter is configured.
7 Configure the Protection Method parameter in the Working and Protection panels, as required.
Note: Configure the Protection Method parameter as PNIM if the protection type is SNCN or SNCNC.
Configure the Protection Method parameter as PADAPT for SNCI protection type.
8 Configure the required parameters in the APS Configuration panel.
Note: Configure the Protection Type parameter as SNCNC, if client transparent ODU facilities are configured as
working and protection facilities.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3.4.4. Procedure 145: To configure 1:N ODUk protection groups
1:N ODUk protection groups
The 5620 SAM supports the configuration of 1:N ODUk protection groups on the ODUk facility objects of the following
cards with ODU2 or ODU2e rates:
4AN10G
10AN10G
10OTH10G
Bidirectional and revertive protection switching is supported. The Extra Traffic parameter is disabled by default.
Before you begin
Before configuring a 1:N ODUk protection group, configure a TCM entity on the required ODUk facility object on the 1830
PSS OCS device. See the AlcatelLucent 1830 PSS User Provisioning Guide for more information about provisioning a TCM
entity.
Steps

Open the 1:N ODUk Protection Group form from the equipment tree.
2. Rightclick on the OCS device object and choose Properties. The Network Element (Edit) form opens.
3. Click on the 1:N ODUk Protection Group tab and click Create. The 1:N ODUk Protection Group (Create) form
opens.
Rightclick on the required OCS device object on the physical topology map and choose Add 1:N ODUk Protection
Group. The 1:N ODUk Protection Group (Create) form opens.
2 Select the required shelf in the Shelf panel.
3 Configure the Rate parameter.
4 Configure ODUk working and protection members on the Oduk Protection Members panel.
1. Click Create. The ODUk Protection Member (Create) form opens.
2. Select the ODUk facility object in the Odu Facility Pointer panel.
3. Configure the required parameters.
You can configure a maximum of 14 working group members and one protection group member.
The value of the ID parameter for the working group members must be unique for an ODUk protection group.
4. Click OK. The ODUk working and protection members are listed in the Oduk Protection Members panel.
5. Click Apply on the 1:N ODUk Protection Group (Create) form.
5 Configure protection switching.
1. Configure the Protection Switch parameter on the Protection Management panel. See the AlcatelLucent 1830 PSS
Product Information and Planning Guide for more information about the options available for the Protection Switch
parameter.
2. Select the source ODUk facility in the Source panel.
Note:
When Path Overhead Monitoring is enabled on an ODUk protection facility and the Extra Traffic parameter is
disabled, you cannot configure a 1:N ODUk protection group.
When an external command is active on a 1:N ODUk protection group, you cannot delete the 1:N ODUk protection
group.
The status of the source and protection ports is displayed in the Source Port Status and Protection Port Status panels.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬
3.4.5. Procedure 146: To configure protection switching
Steps

1 Perform one of the following to open the ODUk Protection Group (Edit) form.
1. Choose Manage→OTN→ODUk Protection Groups. The Manage ODUk Protection Groups form opens.
2. Choose a protection group and click Properties. The ODUk Protection Group (Edit) form opens.
b. From the 1830 PSS device object on the equipment tree.
2. Rightclick on the 1830 PSS object and choose Properties. The Network Element (Edit) form opens.
4. Choose an entry and click Properties. The ODUk Protection Group (Edit) form opens.
c. From the port object on the equipment tree.
1. On the equipment tree, expand Network→1830 PSS→Shelf→Port.
2. Rightclick on the port and choose Properties. The Physical Port (Edit) form opens.
d. From the ODU facility object on the equipment tree.
1. On the equipment tree, expand Network→NE→Shelf→Card→Port→ODU object.
3. Click on the APS Group tab.
2 Configure the required parameters in the Protection Management panel.
Note: Configure the Request For parameter to specify the path that needs to be switched.
E‫�ـ‬Ԁ� Ā蕀� ‫�݀�܀‬Ā蚀�‫�܀‬

1830 PSS OTN Layer Management

Uploaded by

Copyright:

Available Formats

1830 PSS OTN Layer Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1830 PSS OTN Layer Management

Uploaded by

Copyright:

Available Formats

06.07.

ODU facility object GUI naming convention Example

Non­terminated HO­ODUs in the physical OTUODUk­<shelf>/<slot>/<port> OTUODU2­3/3/H1

Non­terminated LO­ODUs in the virtual plane ODUmODUn­<shelf>/71/<HO­ODU#>­<LO­ ODU4ODU1­1/71/1­3

Client­transparent ODUs ODUk­<shelf>/<slot>/<client port> ODU1­1/2/C1

Terminated HO­ODUs in the virtual plane ODUk­<shelf>/71/<ODU#> ODU4­2/71/1

Auto­configured Rate No of LO­ODUs to bind No of timeslots Size of the tributary

ODU2 ODU0 1 ODU0 1 1.25G

ODU1 2 ODU0s 2 1.25G

ODU3e2 ODU0 1 ODU0 1 1.25G

ODU1 2 ODU0s 2 1.25G

ODU2 8 ODU0s or 4 ODU1s 8 1.25G

ODU2e 8 ODU0s or 4 ODU1s 8 1.25G

ODU3 32 ODU0s, 16 ODU1s, or 4 ODU2s 32 1.25G

ODU4 ODU0 ODU0 1 1.25G

ODU1 2 ODU0s 2 1.25G

ODU2 8 ODU0s or 4ODU1s 8 1.25G

ODU2e 8 ODU0s or 4ODU1s 8 1.25G

ODU3 31 ODU0s 31 1.25G

You might also like

Nonterminated HOODUs in the physical OTUODUk<shelf>/<slot>/<port> OTUODU23/3/H1

Nonterminated LOODUs in the virtual plane ODUmODUn<shelf>/71/<HOODU#><LO ODU4ODU11/71/13

Clienttransparent ODUs ODUk<shelf>/<slot>/<client port> ODU11/2/C1

Terminated HOODUs in the virtual plane ODUk<shelf>/71/<ODU#> ODU42/71/1

Autoconfigured Rate No of LOODUs to bind No of timeslots Size of the tributary