IEH 620 Section 500 1350 OMS Cascaded OT Provisioning

GCD Networks
Global Delivery Readiness
IEH 620, Section 500

July, 2013
Alcatel-Lucent
INSTALLATION ENGINEERING HANDBOOK 620
1830 Photonic Service Switch (PSS) 32/16
1350 OMS and 1830PSS Optical Transponder Cascaded Configuration

Procedures
Table of Contents
General......................................................................................................... 3
Description.................................................................................................. 3
Intended Audience......................................................................................... 3
Feedback.................................................................................................... 3
Related Versions........................................................................................... 3
1830 PSS Client Interface Configuration...................................................................4
Pre-requisites............................................................................................... 4
Configure& Verify Client Interface Technology Type.................................................5
OT Cascading................................................................................................... 8
OT Cascading Introduction................................................................................8
11DPM12- Cascaded using 43STX4P (43STX4).............................................................9
11DPM12 Optical Transponder...........................................................................9
43STX4P Optical Transponder............................................................................9
OTUk Configuration Pre-requisites.....................................................................10
Required Network Element Configuration............................................................10
43STX4P OTU3 Trail Creation...........................................................................13
11DPM12- Client Configuration.........................................................................21
11DPM12- Client Configuration and DSR Creation- Using Direct ODUk mapping................25
4DPA4 FLEX MUX- Cascaded using 11STMM10............................................................30
4DPA4 Flex Mux Optical Transponder..................................................................30
OTUk Configuration Pre-requisites.....................................................................30
Required Network Element Configuration............................................................31
11STMM10 trail creation.................................................................................34
4DPA4 ODU1 and Client Connection...................................................................42
Gigabit Ethernet DSR and Client Port creation.......................................................46
STM (n) DSR and Client Port creation..................................................................51
Alcatel-Lucent – Internal
Proprietary – Use pursuant to Company instruction
IEH 620, Section 500 1350 OMS and 1830PSS Optical Transponder Cascaded Configuration
Procedures
List of Tables
Table 1: Product Releases............................................................................................. 3
2 Alcatel-Lucent – Internal July, 2013

1350 OMS and 1830PSS Optical Transponder Cascaded Configuration Procedures
General
Description This section provides the field engineers of 1830 PSS systems with the knowledge for
understanding Generalized Multi-Protocol Label Switching (GMPLS) applications and
deployment in the 1830 PSS Wavelength Division Multiplexing (WDM) network.
Intended The audience should have a basic knowledge of 1350 OMS Operation, DWDM technology,
Audience 1830 PSS product portfolio, and completed at least Level 2 Certification program conducted
by the Alcatel-Lucent University. As such, this document is intended for:
 Alcatel-Lucent (ALU) Field Engineers
 ALU-Accredited 3rd Party Installers
 ALU Technical Project Managers (TPM)
 ALU Customer-Facing Project Managers (CFPM)
Feedback Address any feedback to: gpec.optics@alcatel-lucent.com
Related This document was developed in support to the official product manuals, for which release
Versions versions are listed in the table below and should remain as the official references sources:
Table 1: Product Releases
Product Name Release

1830 PSS-32 5.1
1830 PSS-16 5.1
1830 PSS-4 5.1
EPT (Engineering & Planning Tool) 5.1
1350 OMS 10.2
July, 2013 Alcatel-Lucent – Internal 3

Procedures
1830 PSS Client Interface Configuration
Pre-requisites Prior to any tasks outlined within this MOP, the following 1350 OMS configuration tasks must
be completed
 Network elements have been commissioned.
 Network elements have been configured using CPB.
 Network Elements have been standalone tested to ensure correct internal fibre topology
connectivity.
 Power commissioning is complete.
 All client interfaces have been allocated on network elements.
 All required network elements are supervised from the 1350 OMS.
 All network element parameters have been uploaded into the 1350 OMS.
 OTS Physical Topology has been constructed.
 OMS sections for all OTS physical connections have been imported into OTN.
 All physical connection and port information has been synchronized into OTN.
 Network elements are alarm free.
Continued on next page

1830 PSS Client Interface Configuration, Continued
Configure& To ensure correct configuration of the OTUk trails/paths which will be configured using the
Verify Client 1350 OMS, it is good practice to always assign the required client ports prior to the required
Interface OMS activities.
Technology There are several different options for trail and path construction, which do allow for creation
Type of the client ports from the OMS, but for the purposes of this MOP, all client ports (unless
otherwise indicated) will be assigned using OMS WebUI prior to the construction of the
required infrastructure.
To configure the client ports and synchronize these into the OMS, please use the following
procedure,
Step Action
1 From 1350 OMS management view, to generate a WebUI session,
Select,
 Search
 Physical
 Nodes
Using the generated node list, select

 Highlight required network element
 Right click
 Search
 Physical
 Equipment view

Procedures
Configure&
Verify Client
Step Action
Interface
Technology 2 The OMS will generate a WebUI session of the required network element
Type
(continued)
Using the WebUI GUI, navigate to the required interface and set the client
interface parameters.
Assign all client interface all required NE’s

3 The newly configured ports need to be uploaded into the OMS, from
previously generated node list, select
 Highlight required node
 Right click
 Actions
 Physical
 Synchronize
 Ports
Repeat for all network elements

Configure&
Verify Client
Step Action
Interface
Technology 4 To Verify port upload on both nodes
Type  Highlight required node
(continued)  Right click
 Search
 OTN
 Ports
From the generated port list, verify that the ports have been correctly uploaded
into the OMS

Procedures
OT Cascading
OT Cascading The Dual Stage Multiplexing (or Cascading) is a configuration where a low bit rate client signal
Introduction multiplexed onto the line port of an OT is then added to the client port of a second higher-rate
OT.
The following table summarizes the applicable cascade configurations
High rate OT Cascaded OT

43STX4P 11DPM12
43SCX4 11DPM12
112SCX10 11DPM12
11QPEN4 11STMM10
11DPM12
11DPE12E
11STMM10, 11DPM12 4DPA4
11STMM10 4DPA2
NOTE:
Not all cascaded configurations are included in the document, the procedure outlined for the
43STX4P-11DPM12 Cascaded configuration can be applied to all High rate Optical
Transponders (43STX4P, 43SCX4, 112SCX10, 11QPEN4, 11STMM10 and 11DPM12) and all
ODU2 clients (11STMM10 11DPM12 and 11DPE12E)
The procedure outlined for the 11STMM10-4DPA4 Cascaded configuration can be applied to
High rate Optical Transponders (11STMM10 and 11DPM12) and all ODU1 clients (4DPA2))

11DPM12- Cascaded using 43STX4P (43STX4)
11DPM12 The 11DPM12 transponder is a single slot wide, full height card supporting dual pluggable line
Optical ports with flexible any-rate client signal aggregation, add/drop, and pass through.
Transponder With two line ports and flexible traffic configuration, the 11DPM12 OT can provide ADM and E-
SNCP functionalities.
All client signals can be transported in a bit-transparent or character-transparent manner over
OTN. The 10G pluggable line port of the 11DPM12 supports 88 channels when configured
with a tunable XFP and 44 channels when configured with a fixed channel XFP.
The 11DPM12 card supports the following features:

 Twelve client interfaces with B&W or CWDM PTM optics (SFPs)
Support for the following client type are supported on the 11DPM12 OT:
 OC3/STM1
 OC12/STM4
 OC48/STM16
 1GbE
 FE
 FC100
 FC200
 FC400
 HDSDI
 SDSDI
 3GSD
 OTU1
InfiniBand SDR
43STX4P The 43STX4/43STX4P module provides up to four multi-rate and multi-protocol client
Optical interfaces, capable of multiplexing 10GbE, OC-192, STM-64 or G.709 OTU2 client
Transponder Signal types on to the OTU-3 line.
The 43STX4 supports DPSK, and the 43STX4P supports PDPSK modulation on the 40G line.
This is the only functional difference between the modules.
The 43STX4 and 43STX4P are identical except for the following functionalities:
 43STX4 supports DPSK, modulation on the 40G line
 43STX4 line side supports 44 even channels
 43STX4P supports PDPSK modulation on the 40G line.

 43STX4P supports 88 channels
 43STX4P includes a NRZ-PDPSK transponder.
43STX4P OT supports eVOA management and WT encoding functions.

Procedures
11DPM12- Cascaded using 43STX4P (43STX4), Continued
OTUk Prior to OTUk trail creation, the following 1350 OMS configuration tasks must be completed
Configuration  All required network elements supervised from the 1350 OMS
Pre-requisites
 Network elements have been commissioned
 All network element parameters have been uploaded into the 1350 OMS
 OTS Physical Topology has been constructed
 OMS sections for all OTS physical connections have been imported into OTN
 All physical connection and port information has been synchronized into OTN
Cascade Configuration Specific pre-requisites

 43STX4P client port assigned for OTU2
 Physical Topology defined between 43STX4P Client port and 4DPA4 Line port
Required The following parameters need to be defined on the network elements which have the
Network 11DPM12 OT and 43STX4Pinstalled
Element
Configuration
Step Action
1 Configure 11DPM12 LINE port and time slot using OMS WebUI
Define the following parameters

 Define pluggable module type
 Set transmit frequency as defined in network design
 Set Receive frequency as defined in network design
 Click Submit
NOTE:
In a cascaded configuration, the Voa ports are not used

Required
Network
Step Action
Element
Configuration 2 Configure 43STX4P Client Port
(continued)

 Define Signal Rate as OTU2
 Primary state as in Service, AINS
 Click submit
 Set frequency as defined in network design
 Click Submit
3 Define the Physical Topology between the 43STX4P Client port and the
11DPM12 line port
4 Repeat for both nodes involved in cascaded configuration

Procedures
Required
Network
Step Action
Element
Configuration 5 Using OMS management view, select
(continued)  Search
 Physical
 Nodes
From generated Node list,
 Select the required nodes
 Right click
 Actions
 Synchronize
 Full
To upload the network element configuration into the OTN database

43STX4P OTU3 To create a OTU3 trail terminating on a 43STX4P Optical Transponder, use the following
Trail Creation procedure
NOTE:
For the first part of the procedure, a 10Gb Ethernet interface has been allocated using WebUI
to the C1 port of each network element
Step Action
1 From 1350 OMS Management view,
Select,
 Actions
 OTN
 Create Trail
Define the following configuration parameters:

 Connection rate: OTU3
 Connection Name: as defined in customer NMS naming convention
 Connection Alias: as defined in customer NMS naming convention
 Click next
NOTE:
For the purposes of the MOP, all other parameters will be left as default, for
further information regarding these setting, please refer to the 1350 OMS OTN
Provisioning guide

Procedures
43STX4P OTU3
Trail Creation
Step Action
(continued)
2 The end point screen allows for allocation of the required nodes and OTUk
trail end points,
To select ‘From’ End Point 1 Network element and required port,

 click on the select icon alongside ‘From NE1 block’
- From generated node list, select required NE and click ok
 Click on the select icon alongside’ From Port ID1’
- From generated port list, select required port and click ok
To select ‘To’ End Point 1 Network element and required port,

 click on the select icon alongside ‘To NE1 block’
 Click on the select icon alongside’ To Port ID1’
Verify network element and port information

Click next

43STX4P OTU3
Trail Creation
Step Action
(continued)
3 The transmission screen allows for configuration of the transmission
parameters of the OTUk trail
To modify parameters,
 Click on Edit Parameters
The Modify Connection Transmission Parameters screen will be displayed
Click on required parameter to be altered

 Select value from drop down list
 Click apply
 Modify Connection Transmission Parameters screen will close
 Verify change on Transmission screen
Click next

Procedures
43STX4P OTU3
Trail Creation
Step Action
(continued)
4 The Routing screen defines the routing parameters for the OTUk trail,
Select
 Walker
 Walker Mode- Link Connection Based
 Focus node will be already allocated
 Define Neighbor node, click on select icon and from generated node list
select the required Neighbor node
NOTE:
If the OTUk trail passes through intermediate nodes, then neighbour node will
be the next directly connected node, the configuration must be added hop by
hop until the routing from the A node to the Z node has been completely
defined
Select connection
 Choose the require OMS section from the generated list
Select Link connection by clicking on the select icon

 Choose allocated frequency determined by EPT and subsequent
configuration on the network element
Verify Information
Click next

43STX4P OTU3
Trail Creation
Step Action
(continued)
5 The Assurance screen defines the alarm hanling and Performace Monitoring
parameters for the OTUk trail,
 Define required parameters

Click next
6 The wave key screen defines the the wavekey allocation parameters for the
OTUk trail, unles required by the customer, leave this value as default of
Automatic

Procedures
43STX4P OTU3
Trail Creation
Step Action
(continued)
7 The Order screen allows for how/when the configuration of the OTUk trail will
be constructed on the 1350 OMS
Unless otherwise instructed, leave all as default values except

 Uncommissioned links – set to yes
Click Apply
Result:
When the banner at the top of the screen goes green, the trail has been
created in the OTN manager, the status of the OTUk, ODUk and DSR need to
be checked to ensure successful implementation onto the network elements
8 A graphical view of the OTU3 trail will be automatically generated

43STX4P OTU3
Trail Creation
Step Action
(continued)
9 To verify correct configuration of the OTU3 clients (ODU2 and DSR,),
Highlight the OTU3 Icon
 Right hand click
 Search
 Clients
The OTU3 client list will be generated, this will detail the ODU2 and DSR,
ensure both are in commissioned status for order step

Procedures
43STX4P OTU3
Trail Creation
Step Action
(continued)
10 To view a routing display of the ODU2 or DSR,
Highlight required entity
 Search
 Routing display
The 1350 OMS will generate the requested routing display

11DPM12- To define the 11DPM12 client type for the network element, use the following procedure
Client
Configuration
Step Action
1 Using WebUI, navigate to required 11DPM12 port and configure the port
parameters for the required technology type
2 Gigabit Ethernet Client Interface
 Assign client interface
 Assign Container granularity (ODU0)
 Repeat for all network elements
Perform Port Synchronisation on OMS

Procedures
11DPM12-
Client
Step Action
Configuration
(continued) 3 SDH/SONET Client Interface directly mapped into an ODU0
 Assign Container granularity (ODU0)

11DPM12-
Client
Step Action
Configuration
(continued) 4 OPTSG ODU1 required configuration:
Assign 2 x ODU0 Containers to be used for ODU1 access to the OPTSG

 Highlight required Line/OTU2 port
 Select timeslots tab
 Assign two ODU0 containers as detailed in screen shot
 Apply
NOTE:
ODU0 allocation for ODU1 access must be configured in contiguous pairs,
L1 odu0#1+2 associated with ODU1PTF#1

Procedures
11DPM12-
Client
Step Action
Configuration
(continued) 5 SDH/SONET Client Interface using OPTSG container and timeslot allocation
 Assign Container granularity (OPTSG)

11DPM12- NOTE:
Client Prior to starting this procedure, please ensure that the client interface and ODU0 mapping has
Configuration been correctly defined as detailed in the 11DPM12 client Configuration section above
and DSR
Creation- Using
Direct ODUk To create a Gigabit Ethernet DSR path within the OMS, please use the following procedure
mapping
Step Action
1 To Create the DSR, from 1350 OMS management view, select
 Actions
 OTN
 Create Path

 Connection rate: DSR
 Service Rate: Ethernet
 Click next
NOTE:
Provisioning guide

Procedures
11DPM12-
Client
Step Action
Configuration
and DSR 2 The end point screen allows for allocation of the required nodes and DSR path
Creation- Using end points,
Direct ODUk
mapping To select ‘From’ End Point 1 Network element and required port,
(continued)
- From generated port list, select required Client port
- Select required Client port
 click ok

- Select required client port
 click ok
Click Next

11DPM12-
Client
Step Action
Configuration
and DSR 3 The transmission screen allows for configuration of the transmission
Creation- Using parameters of the DSR path
Direct ODUk
mapping
(continued)
 Modify required parameters
 Container – ODU0
 Signal type- 1Gbe
 Click apply
 Verify information
Click Next

Procedures
11DPM12-
Client
Step Action
Configuration
and DSR 4 The Routing screen defines the routing parameters for the DSR path,
Creation- Using Select
Direct ODUk  Walker
mapping
 Walker Mode- select Link Connection based
(continued)
Define Neighbor node,
 click on select icon and from generated node list select the required
Neighbor node
 Connection- select configured ODU2 defined between 11DPM12’s
 Select Link connection by clicking on the select icon

 The available ODU0 timeslots encapsulated within an ODU2 will be
displayed, select timeslot which is required for Gigabit Ethernet transmission
Click Next

11DPM12-
Client
Step Action
Configuration
and DSR 5 Step through to order screen and click apply
Creation- Using
Direct ODUk
mapping
(continued)
Result:
created in the OTN manager, the status of the DSR will need to be checked to
ensure successful configuration.
6 A graphical view of the DSR trail will be automatically generated

Procedures
4DPA4 FLEX MUX- Cascaded using 11STMM10
4DPA4 Flex Mux The 4DPA4 is a half-height, single-wide card that accepts up to four client signals via SFP
Optical optics, and performs non-blocking multiplexing into one or both line ports.
Transponder The 4DPA4 has dual pluggable OTU1 line ports that support B&W, CWDM, or DWDM line
signals and supports a variety of sub-ODU1 client signals with extremely flexible transponder
Mappings.
OTUk Prior to OTUk trail creation, the following 1350 OMS configuration tasks must be completed
Configuration  All required network elements supervised from the 1350 OMS
Pre-requisites
 Network elements have been commissioned
 All network element parameters have been uploaded into the 1350 OMS
 OTS Physical Topology has been constructed
 OMS sections for all OTS physical connections have been imported into OTN
 All physical connection and port information has been synchronized into OTN
Cascade Configuration Specific pre-requisites

 11STMM10 client port assigned for OTU1
 Physical Topology defined between 11STMM10 Client port and 4DPA4 Line port

4DPA4 FLEX MUX- Cascaded using 11STMM10, Continued
Required The following parameters need to be defined on the network elements which have the 4DPA4
Network OT installed
Element
Configuration
Step Action
1 Configure 11STMM10 client port and time slot using OMS WebUI

 Define Client port1 as client type OTU1
 Apply
 Click Submit
Click on Time slot tab
 Select tick in first box for required ODU1 timeslot (all boxes in chosen ODU1
will be ticked as all timeslots will be allocated for ODU1 client type)
 Click submit

Procedures
Required
Network
Step Action
Element
Configuration 2 Configure 4DPA4 Line port
(continued)

 Define Operational Mode- Add Drop
 Click Submit
3 Define the Physical Topology between the 11STMM10 C port and the 4DPA4
line port
4 Repeat for both nodes involved in cascaded configuration

Required
Network
Step Action
Element
Configuration 5 Using OMS management view, select
(continued)  Search
 Physical
 Nodes
From generated Node list,
 Select the required nodes
 Right click
 Actions
 Synchronize
 Full
To upload the network element configuration into the OTN database

Procedures
11STMM10 trail To create a OTU2 using the 11STMM10 Optical Transponder, use the following procedure
creation NOTE:
For the first part of the procedure, a CBR2G5 interface has been allocated using WebUI to the
C1 port of each network element and this has been mapped into the first ODU1 timeslot
Step Action
1 From 1350 OMS Management view,
Select,
 Actions
 OTN
 Create Trail

 Connection rate: OTU2
 Click next
NOTE:
Provisioning guide

11STMM10 trail
creation
Step Action
(continued)
2 The end point screen allows for allocation of the required nodes and OTUk
trail end points,


 click on the select icon alongside ‘To NE1 block’
 Click on the select icon alongside’ To Port ID1’
Verify network element and port information

Click next

Procedures
11STMM10 trail
creation
Step Action
(continued)
3 The transmission screen allows for configuration of the transmission
parameters of the OTUk trail
Click on required parameter to be altered

 Select value from drop down list
 Verify OTUk FEC mode is aligned with FEC type allocated by EPT during
network design
 Click apply
 Modify Connection Transmission Parameters screen will close
 Verify change on Transmission screen
Click next

11STMM10 trail
creation
Step Action
(continued)
4 The Routing screen defines the routing parameters for the OTUk trail,
Select
 Walker
NOTE:
If the OTUk trail passes through intermediate nodes, then neighbour node will
be the next directly connected node, the configuration must be added hop by
hop until the routing from the A node to the Z node has been completely
defined
Select connection
 Choose the require OMS section from the generated list

 Choose allocated frequency determined by EPT and subsequent
configuration on the network element
Verify Information
Click next

Procedures
11STMM10 trail
creation
Step Action
(continued)
5 The Assurance screen defines the alarm hanling and Performace Monitoring
parameters for the OTUk trail,
 Define required parameters

Click next
6 The wave key screen defines the the wavekey allocation parameters for the
OTUk trail, unles required by the customer, leave this value as default of
Automatic

11STMM10 trail
creation
Step Action
(continued)
7 The Order screen allows for how/when the configuration of the OTUk trail will
be constructed on the 1350 OMS
Unless otherwise instructed, leave all as default values except

 Uncommissioned links – set to yes
Click Apply
Result:
created in the OTN manager, the status of the OTUk, ODUk and DSR need to
be checked to ensure successful implementation onto the network elements
8 A graphical view of the OTU2 trail will be automatically generated

Procedures
11STMM10 trail
creation
Step Action
(continued)
9 To verify configuration of the OTU2 clients (ODU2, ODU1 and DSR,)
Highlight the OTU2 Icon in routing display
 Search
 Clients
The OTU2 client list will be generated, this will detail the ODU2, ensure the
ODU2 is in commissioned status for order step

11STMM10 trail
creation
Step Action
(continued)
10 To view a routing display of the ODU2.
Highlight required entity in OTU2 client list
 Search
 Routing display
The 1350 OMS will generate the requested routing display

Procedures
4DPA4 ODU1 To add additional Client interfaces using the 1350 OMS, there is a 2 step approach
and Client 1- Create an ODU1
Connection
2- Create the client DSR (which assigns the interface directly on the network element)
Step Action
1 To Create the ODU1, from 1350 OMS management view, select
 Actions
 OTN
 Create Trail

 Connection rate: ODU1
 Click next
NOTE:
Provisioning guide

4DPA4 ODU1
and Client
Step Action
Connection
(continued) 2 The end point screen allows for allocation of the required nodes and OTUk
trail end points,

- From generated port list, select required Line port
- Select required ODU1 timeslot
 click ok

- From generated port list, select required Line port
- Select required ODU1 timeslot
 click ok
Click Next
Step through to the Routing screen leaving options as default on Transmission

and SNC screens

Procedures
4DPA4 ODU1
and Client
Step Action
Connection
(continued) 3 The Routing screen defines the routing parameters for the ODUk trail,
Select
 Walker
 Walker Mode- select Link Connection based
NOTE:
The ODU1 has to be routed over 3 connections
1- OTU1 between 11STMM10 Client port and 4DPA Line port in Node 2
2- ODU2 between Node 2 and Node 4 (timeslot required from ODU2)
3- OTU1 between 11STMM10 Client port and 4DPA Line port in Node 4

 Choose required ODU2 from generated list
Click Next

4DPA4 ODU1
and Client
Step Action
Connection
(continued) 4 Step trough to order screen and click Apply
Result:
created in the OTN manager, the status of the ODUk will need to be checked
to ensure successful configuration.
5 A routing display of the ODU1 trail will be automatically displayed

Procedures
Gigabit To create a Gigabit Ethernet Port on the network elements and an DSR path within the OMS,
Ethernet DSR please use the following procedure
and Client Port
creation Step Action
 Actions
 OTN
 Create Path

 Service Rate: Ethernet
 Click next
NOTE:
Provisioning guide

Gigabit
Ethernet DSR
Step Action
and Client Port
creation 2 The end point screen allows for allocation of the required nodes and DSR
(continued) pathl end points,

 click ok

 click ok
Click Next

Procedures
Gigabit
Ethernet DSR
Step Action
and Client Port
creation 3 The transmission screen allows for configuration of the transmission
(continued) parameters of the DSR path.
 Click on required parameter to be altered
 Select value from drop down list- 1 Gbe
Select Timeslot tab
Click on icon, from timeslot pop up window, select required (STM1/OC3

equivalent timeslots) for client port rate being configured, for GigE select 8
timeslots
NOTE:
For GigE applications on 4DPA4, the user must select the following timeslots
Option 1- 1,3,5,7,9,11.13.15
Option 2- 2,4.6.8.10.12.14.16
 Click apply
Click next

Gigabit
Ethernet DSR
Step Action
and Client Port
creation 4 The Routing screen defines the routing parameters for the DSR,
(continued) Select
 Walker
 Walker Mode- select Trail based
Neighbor node
 Connection- select previously configured ODU1
 Select Link connection by clicking on the select icon

 Select the timeslot
Click Next

Procedures
Gigabit
Ethernet DSR
Step Action
and Client Port
creation 5 Step through to order screen and click apply
(continued)
Result:
6 A routing display will be automatically generated
To check the status of the DSR, from 1350 OMS management view, select
 Search
 OTN
 All Paths (OTN)
 Ensure Gigabit Ethernet Path is commissioned in the order step column


STM (n) DSR To create a STM(n) Port on the network elements and an DSR path within the OMS, please
and Client Port use the following procedure
creation
Step Action
 Actions
 OTN
 Create Path

 Service Rate: Undetermined
 Click next
NOTE:
Provisioning guide

Procedures
STM (n) DSR

and Client Port
Step Action
creation
(continued) 2 The end point screen allows for allocation of the required nodes and DSR
pathl end points,

 click ok

 click ok
Click Next

STM (n) DSR

and Client Port
Step Action
creation
(continued) 3 The transmission screen allows for configuration of the transmission
parameters of the DSR path.
 Click on required parameter to be altered
 Select value from drop down list- OC-3
Select Timeslot tab
Click on icon, from timeslot pop up window, select required (STM1/OC3

equivalent timeslots) for client port rate being configured, for OC3 select 1
timeslot
 Click apply
Click next

Procedures
STM (n) DSR

and Client Port
Step Action
creation
(continued) 4 The Routing screen defines the routing parameters for the DSR,
Select
 Walker
 Walker Mode- select Trail based

Neighbor node
 Connection- select previously configured ODU1
Click Next

STM (n) DSR

and Client Port
Step Action
creation
(continued) 5 Step through to order screen and click apply
Result:
6 A routing display will be automatically generated
To check the status of the DSR, from 1350 OMS management view, select
 Search
 OTN
 All Paths (OTN)
 Ensure Gigabit Ethernet Path is commissioned in the order step column


IEH 620 Section 500 1350 OMS Cascaded OT Provisioning

Uploaded by

Document Information

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

IEH 620 Section 500 1350 OMS Cascaded OT Provisioning

Uploaded by

Copyright:

Available Formats

GCD Networks

Global Delivery Readiness

IEH 620, Section 500

1350 OMS and 1830PSS Optical Transponder Cascaded Configuration

Table 1: Product Releases............................................................................................. 3

2 Alcatel-Lucent – Internal July, 2013

Feedback Address any feedback to: gpec.optics@alcatel-lucent.com

Table 1: Product Releases

Product Name Release

July, 2013 Alcatel-Lucent – Internal 3

1830 PSS Client Interface Configuration

Continued on next page

4 Alcatel-Lucent – Internal July, 2013

1830 PSS Client Interface Configuration, Continued

Using the generated node list, select

Continued on next page

July, 2013 Alcatel-Lucent – Internal 5

1830 PSS Client Interface Configuration, Continued

Assign all client interface all required NE’s

Repeat for all network elements

Continued on next page

6 Alcatel-Lucent – Internal July, 2013

1830 PSS Client Interface Configuration, Continued

July, 2013 Alcatel-Lucent – Internal 7

The following table summarizes the applicable cascade configurations

High rate OT Cascaded OT

8 Alcatel-Lucent – Internal July, 2013

11DPM12- Cascaded using 43STX4P (43STX4)

The 11DPM12 card supports the following features:

 43STX4P supports PDPSK modulation on the 40G line.

Continued on next page

July, 2013 Alcatel-Lucent – Internal 9

11DPM12- Cascaded using 43STX4P (43STX4), Continued

Cascade Configuration Specific pre-requisites

Define the following parameters

Continued on next page

10 Alcatel-Lucent – Internal July, 2013

11DPM12- Cascaded using 43STX4P (43STX4), Continued

Define the following parameters

4 Repeat for both nodes involved in cascaded configuration

Continued on next page

July, 2013 Alcatel-Lucent – Internal 11

11DPM12- Cascaded using 43STX4P (43STX4), Continued

To upload the network element configuration into the OTN database

Continued on next page

12 Alcatel-Lucent – Internal July, 2013

11DPM12- Cascaded using 43STX4P (43STX4), Continued

Define the following configuration parameters:

Continued on next page

July, 2013 Alcatel-Lucent – Internal 13

11DPM12- Cascaded using 43STX4P (43STX4), Continued

To select ‘From’ End Point 1 Network element and required port,

To select ‘To’ End Point 1 Network element and required port,

Verify network element and port information

Continued on next page

14 Alcatel-Lucent – Internal July, 2013

11DPM12- Cascaded using 43STX4P (43STX4), Continued

Click on required parameter to be altered

Continued on next page

July, 2013 Alcatel-Lucent – Internal 15

11DPM12- Cascaded using 43STX4P (43STX4), Continued

Select Link connection by clicking on the select icon

Continued on next page

16 Alcatel-Lucent – Internal July, 2013