Professional Documents
Culture Documents
3AL61269BAAA - V1 - 1354RM Regional Network Manager For SDH and Optical Networks Rel.7.4F - User Guide (VOL II Advanced Provisioning)
3AL61269BAAA - V1 - 1354RM Regional Network Manager For SDH and Optical Networks Rel.7.4F - User Guide (VOL II Advanced Provisioning)
Rel.7.4F
Version 7.5.0
User Guide
3AL 61269 BAAA
Issue 5
April 2010
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent.
PREFACE......................................................................................................................................... 25
Preliminary Information.............................................................................................................. 25
Applicability................................................................................................................................. 26
Scope ........................................................................................................................................... 26
History.......................................................................................................................................... 27
Related Documents .................................................................................................................... 28
Handbook Structure ................................................................................................................... 29
General on Customer Documentation ...................................................................................... 30
1 WDM ............................................................................................................................................. 35
1.1 WDM description.................................................................................................................. 35
1.1.1 WDM Layer Overview ..................................................................................................... 35
1.1.2 WDM Terminology .......................................................................................................... 36
1.1.3 WDM Equipments managed by 1354RM........................................................................ 37
1.1.4 WDM NE configurations ................................................................................................. 37
1.1.5 Layering .......................................................................................................................... 40
1.1.6 Network construction ...................................................................................................... 41
1.1.7 Integrated management map view ................................................................................. 41
1.1.8 Circuit provisioning ......................................................................................................... 42
1.1.9 Raw connection .............................................................................................................. 43
1.1.10 Performance Monitoring ............................................................................................... 44
1.1.11 B1 based PM................................................................................................................. 44
1.1.12 Acronims ....................................................................................................................... 45
1.1.13 Topological Components .............................................................................................. 45
1.1.14 Physical Resources ...................................................................................................... 45
1.1.15 Transport Entities.......................................................................................................... 46
1.1.16 Reference Points .......................................................................................................... 46
1.2 G709 handling ...................................................................................................................... 47
1.2.1 G709 handling overview ................................................................................................. 47
1.2.2 G 709 Management ........................................................................................................ 49
1.2.3 Examples ........................................................................................................................ 49
1.2.4 Mapping logical / physical resources .............................................................................. 51
1.3 WDM Network....................................................................................................................... 53
1.3.1 OTS conn. navigation ..................................................................................................... 53
1.3.2 G.709 handling with support for OTU, ODU1, ODU2 layers ........................................... 58
1.3.3 Examples of OPS conn. navigation ................................................................................ 63
1.3.4 OTS and OMS protection (SNCP at OMS layer) ............................................................ 66
1.3.5 OCH protected trail management ................................................................................... 66
1.3.6 DS path bit rate .............................................................................................................. 69
1.4 WDM network create............................................................................................................ 69
1.5 Raw Connection................................................................................................................... 74
1.6 Completed raw connection ................................................................................................. 76
1.7 Optical Network Modify ....................................................................................................... 79
1.7.1 Adding a transponder on 1640WM ................................................................................. 79
1.7.2 Not Applicable Extension on 1686WM ........................................................................... 82
1.7.3 Adding an optical MUX/DEMUX on 1696MS (Metro Span) ............................................ 82
1.7.4 Adding an optical MUX/DEMUX on 1626LM .................................................................. 82
1.7.5 1640WM/1686WM OADM connectivity .......................................................................... 82
1.7.6 1696MS OADM connectivity ........................................................................................... 83
Preliminary Information
WARNING
ALCATEL makes no warranty of any kind with regards to this manual, and specifically disclaims the
implied warranties of merchantability and fitness for a particular purpose. ALCATEL will not be liable
for errors contained herein or for damages, whether direct, indirect, consequential, incidental, or spe-
cial, in connection with the furnishing, performance, or use of this material.
NOTICE
The product specification and/or performance levels contained in this document are for information
purposes only and are subject to change without notice. They do not represent any obligation on the
part of ALCATEL.
COPYRIGHT NOTIFICATION
The technical information of this manual is the property of ALCATEL and must not be copied, repro-
duced or disclosed to a third party without written consent.
TECHNICAL SUPPORT
Please contact your Local Alcatel Technical Assistance Center for questions reffered to the infor-
mation contained in this document.
To send your comments about this handbook please follow the indication on Customer Documen-
tation Feedback on page 571.
PRODUCT
1354RM
Scope
This document aims to describe the 135RM Subsystem functionalities to manage a Network of regional
entity.
The list of handbooks given here below is valid on the issue date of this
Handbook and can be changed without any obligation for ALCATEL to
update it in this Handbook.
Some of the handbooks listed here below may not be available on the
issue date of this Handbook.
The standard Customer Documentation in the English language for the equipment whose product–
release–version is stated in “Applicability” on page 26 consists of the following handbooks:
The first document (the document you are reading) contains the basic network management
description, it contains also the product overview and the graphical inteface description. The
main argument is the SDH network provisioning.
The second document describes particular network provisioning : WDM, ASON and Ethernet
provisioning.
This handbook is divided into the main topics described in the table of contents:
WDM This section describes the procedures to build and maintain the
WDM network
ASON This section describes the procedures to build and maintain the
ASON network
RM-NP FT interw The aim of this section is to describe the operations related to the
RM-NP interworking.
CUSTOMER DOCUMENTA- It contains info regarding customer opinions collection about this
TION FEEDBACK documentation.
A "product" is defined by the network hierarchical level where it can be inserted and by the whole of per-
formance and services for which it is meant.
A "product" evolves through successive "product–releases" which are the real products marketed for
their delivery at a certain "product–release" availability date.
So, a "product-release" defines a set of hardware components and a software package which, as a whole,
identify the possible network applications and the equipment performance which the specific "product–
release" has been designed, engineered and marketed for.
In some cases a "product–release" has further development steps, named "versions", that are born to
improve or add some performance (mainly software) with respect to the previous version, or for bug fixing
purposes.
A "product–release" has its own standard Customer Documentation, composed by one or more hand-
books.
A new "version" of a "product–release" may or may not produce a change in the status of the Customer
Documentation set, as described in “Handbook Updating” following part.
Handbooks are not automatically delivered together with the equipment they refer to.
The number of handbooks per type to be supplied must be decided at contract level.
Standard hardware and software documentation is meant to give the Customer personnel the possibility
and the information necessary for installing, commissioning, operating and maintaining the equipment
according to Alcatel Laboratory design choices.
In particular: the contents of the handbooks associated to the software applications focus on the expla-
nation of the man–machine interface and of the operating procedures allowed by it; maintenance is
described down to faulty PCB location and replacement.
Consequently, no supply to the Customers of design documentation (like PCB hardware design and pro-
duction documents and files, software source programs, programming tools, etc.) is envisaged.
The handbooks concerning hardware (usually the "Technical Handbook") and software (usually the
"Operator's Handbook") are kept separate in that any product changes do not necessarily concern their
contents.
For example, only the Technical Handbook might be revised because of hardware configuration
changes (e.g., replacing a unit with one having different P/N but the same function).
On the other hand, the Operator's Handbook is updated because of a new software version but which
does not concern the Technical Handbook as long as it does not imply hardware modifications.
However, both types of handbooks can be updated to improve contents, correct mistakes, etc..
The handbooks associated to the "product-release" are listed in “Related Documents” on page 28.
The edition and date of issue might change on future handbook versions for the following reasons:
– only the date changes (pointed out in the Table of Contents) when modifications are made to the edi-
torial system not changing the technical contents of the handbook.
– the edition, hence the date, is changed because modifications made concern technical contents. In
this case:
• the changes with respect to the previous edition are listed in History on page 27.;
• in affected chapters, revision bars on the left of the page indicate modifications in text and draw-
ings.
Changes concerning the technical contents of the handbook cause the edition number increase (e.g. from
Ed.01 to Ed.02). Slight changes (e.g. for corrections) maintain the same edition but with the addition of
a version character (e.g. from Ed.02 to Ed.02A). Version character can be used for draft or proposal edi-
tions.
Moreover, should the screen prints included in the handbook contain the product–release's
"version" marking, they are not replaced in the handbooks related to a subsequent version, if
the screen contents are unchanged.
Supplying updated handbooks to Customers who have already received previous issues is submitted to
commercial criteria.
By updated handbook delivery it is meant the supply of a complete copy of the handbook new issue (sup-
plying errata-corrige sheets is not envisaged).
A new product version changes the handbook P/N and the edition starts from 01.
In this case the modified parts of the handbook are not listed.
In most cases, a CD-ROM contains in read-only eletronic format the documentation of one product-
release(-version) and for a certain language.
In some other cases, the same CD-ROM can contain the documentation of different product-release(-ver-
sion)s for a certain language.
As a general rule:
• the documentation of system optional features that Customers could not buy from Alcatel
together with the main applicative SW.
• the documentation of system optional features (e.g. System Installation Handbooks related to
racks that Customers could not buy from Alcatel together with the main equipment).
A CD-ROM is obtained collecting various handbooks and documents in .pdf format. Bookmarks and
hyperlinks make the navigation easier. No additional information is added to each handbook, so that the
documentation present in the CD-ROMs is exactly the same the Customer would receive on paper.
The files processed in this way are added to files/images for managing purpose and a master CD-ROM
is recorded.
After a complete functional check, the CD-ROM image is electronically transferred to the archive of the
Production Department, so that the CD-ROM can be produced and delivered to Customers.
The CD-ROM starts automatically with autorun and hyperlinks from the opened “Index" document permit
to visualize the .pdf handbooks
Other hyperlinks permit to get, from the Technical handbooks, the specific .pdf setting documents.
In order to open the .pdf documents Adobe Acrobat Reader Version 4.0 (minimum) must have been
installed on the platform.
The CD-ROM doesn't contain the Adobe Acrobat Reader program. The Customer is in charge of getting
and installing it.
ReadMe info is present on the CD-ROM to this purpose.
Then the Customer is allowed to read the handbooks on the PC/WS screen, using the navigation and
zooming tools included in the tool, and to print selected parts of the documentation through a local printer.
2) and, internally, by the list of the source handbooks and documents (P/Ns and editions) by
whose collection and processing the CD-ROM itself has been created.
CD-ROM updating
The list of source handbook/document P/Ns-editions indicated in previous para. point 2) , in association
with the CD-ROM's own P/N-edition, is also loaded in the Alcatel-Information-System as a structured list.
Whenever a new edition of any of such handbooks/documents is released in the Alcatel archive system,
a check in the Alcatel-Information-System is made to identify the list of CD-ROMs that must be updated
to include the new editions of these handbooks/documents.
This causes the planning and creation of a new edition of the CD-ROM.
Updating of CD-ROMs always follows, with a certain delay, the updating of the single handbooks com-
posing the collection.
Since the availability of a network management system is a key feature for transport networks, the current
NML OS set of applications (packaged into the 1354RM product) has to face this new technology by intro-
ducing new functionality.
The digital client signal transported at WDM layer is identified in the OTN network by "Client" end points
of the paths managed at WDM level (named "Client path" - see Figure 1).
A "Client path" maps a logical physical connection in the SDH network in the WDM layer: typically the "Cli-
ent path" supports several SDH paths crossing the OTN network.
The "Client path" may also represent the transport end-service delivered by an operator, if only the OTN
network is managed by the NML OS or the specific terminating non DWDM NEs are managed by another
NML OS.
The "Client path" concept is therefore a way to define the generic server provided by the optical trans-
port network. NOTICE THE THE TRUE CLIENT IS THE SDH PATH.
When a SDH network is the client of the OTN network, the WDM "Client path" is the service provided
by the OTN to the SDH network, which will look at it as a physical connection joining the two SDH NEs
at the extremities of the WDM section (see Figure 1).
The WDM hierarchy represents the stages required by a digital client signal that has to be transported at
WDM layer:
· The signal must be "colored" (i.e. has to be transmitted with the wavelength that has been assigned
to its channel) .
This operation is performed by specific boards named "transponders" or WLA (WaveLength Adapter)
This operation may be not necessary if the signal source is already coloured in the client equipment
through "colored" interfaces (specific transmission boards).
· The Optical Channels that compose the WDM signals are multiplexed into the WDM signal.
The multiplexed signal belongs to the Optical Multiplex Section (OMS) layer
· The signal is transported along the optical fiber until it is extracted to upper layers.
The signal interfaced with the optical medium belongs to the Optical Transport Section (OTS) layer
As for the SDH network, the modeling of the OTN network in the NML OS is based on the concepts of
End Points (e.g. Ports), Physical Connection, Link Connection, Trail, and Path
A schematic representation of the layering of a "Client path" into the OTN network is shown in Figure Fig-
ure 9.on page 40.
When a single Optical Channel (without supervisory channel) is transported along the optical fiber, the
OMS layer is skipped and the OTS layer is named OPS0 (Optical Physical Section 0).
By extension of this concept, related to mono-lambda signals, in WDM layer the ports of WLA boards are
identified as OPS ports and the physical connections connecting SDH NE to WDM NE are identified as
OPS physical connections
– 1640WM
– 1686WM
– 1696MSPAN
– 1626LM
– OCP
· Line Terminal
The Line Terminal is where the client digital signal access/exit the OTN network and is multiplexed/demul-
tiplexed into the OTS level signal.
WLA boards are not necessary if the input signal is already "colored"
The In Line Amplifier configuration (also named as In Line Repeater) provides an optical amplification of
type OTS signal without any regeneration of the original signal.
The OADM configuration offers the possibility of inserting/extracting wavelength from the optical payload.
The number of wavelength added/dropped in OADM NEs is limited (typically 4-8 wavelengths)
Back-to-back Regenerator
Two NEs may be put in back-to-back configuration to offer regeneration capability for the OTS signal in
case of exceeding attenuation of the signal along the optical section.
This configuration allows to compensate the signal attenuation, the chromatic dispersion and to regen-
erate the signal (2R or 3R).
1660 OCP
They are pure switching equipments operating at the channel level (i.e. on a per wavelength basis).
OCP (Optical Channel Protection) offers the opportunity of introducing O-SNCP configuration in OTN net-
works where the WDM NEs don't support this feature (e.g. 1686WM and 1640WM).
1.1.5 Layering
The following figure shows the relationship between the network components and the model
· Upload from the EML OS the information about NEs and Ports
The introduction of the OPS physical connections implies that the ports in SDH NEs may be involved in
two different connections at the same time (each connection belonging to a different network view)
Because of this reason, ports in SDH NEs are fictitiously split into two objects when they are involved in
OPS connections: a second port of OPS type (a copy of the original SDH port) is used to set-up the OPS
connection with the WDM NE.
In WDM NEs OPS ports are related to WLA boards equipped in the NE or, in case of "colored" interfaces,
to the input/output board accepting Optical Channels (Mux/Demux boards).
1354RM offers the capability to manage SDH and WDM network domains both in integrated or separate
configuration (i.e. using two instances of RM).
In case of integrated management, a flat representation of the managed network is offered to the users:
both SDH and WDM NEs are shown in the same map.
A set of ADM NEs connected through an OTN network section, supported by WDM NEs.
Taking in account the splitting of the network representation in two different levels (SDH and WDM), the
full view of a co-hosted SDH-WDM network will offer this representation of the network topology:
Only the connections in color represent physical links (respectively OPS and OTS physical connection).
The gray connection is in practice a logical SDH connection ( conventionally called SDH physical con-
nection)
This connection is anyway the only connection seen by the NML OS at SDH network level and RM routing
algorithm will refer it when an SDH path crossing the two SDH NEs will be allocated.
The following sequence depicts a simple example of set up the OTN Network layout and on how Client
path is identified by RM.
RM has no knowledge of the fixed cross connections defined inside WDM NEs.
As soon as a physical connection is created, the TPs at the extremities are added in RM MIB.
The RM retrieves the fixed cross connection in the WDM NE creates an Incomplete Connection.
At this point the infrastructure supporting the client level services is ready.
3) The RM operator creates the first OPS connection between one of the SDH NE at the extrem-
ities of the Client Path and the adjacent WDM NE.
RM retrieve a second fixed cross connection, creates a second Incomplete Connection and merges it with
the previous one. The connection is still "incomplete"
4) At last, an OPS connection is created at the other extremity of the WDM transport link. Also in
this case the objects up to the Client Nap are created into the SDH NE.
RM recognizes that the connection is now complete (ending on two Client NAPs) and transforms it in a
Client Path.
WDM NEs currently managed by 1354RM offer a very limited flexibility in defining circuits at OTN level:
with few exceptions in 1696MSPAN, all the cross-connections defined in the NEs are either fixed or semi-
fixed (e.g. the pass-through connections in OADM NEs preset for channel Add/Drop).
An external management OS cannot control the fixed connections: they are "uploaded" by 1354RM from
the WDM NEs deployed in the managed network.
The "Client" path definition mechanism is based for 1354RM on the concept of "Raw Connection" (RC).
A "Raw Connection" represents a partial connectivity or connection that cannot be mapped in a path or
in a trail. It is composed by at least a link connection and a cross-connection and is terminated by two (or
more) TPs (CTP, NAP, CAP).
"Raw Connections" may exist both in the SDH and OTN network: at OTN network anyway they play a key
role in circuit design.
When a physical connection is created at OTN network level, during the network construction phase, the
Trails and Link Connections representing the WDM layering are automatically created inside the RM MIB.
The new link connections are analyzed by RM and correlated to the cross-connections stored in the MIB
to identify, if possible, new RCs. It may happen that two pre-existing RCs are merged in a longer RC as
a result of this analysis.
When both ends of the RC are not CTPs, the RC is defined as "complete".
If both the ends of a complete RC are of the same type, the RC is automatically promoted to optical path
(if end points are NAPs) or trail (if end points are CAPs). A Clint path is terminated by two Client NAPs,
contained in the SDH NEs (virtual, in case) accessing the WDM layer services.
Currently, the WDM NEs managed by 1354RM support only a limited set of monitorable information:
· B1 byte: a byte of the RS overhead of SDH signal (RSOH) allocated for both error and PM monitoring.
The basic concepts of PM management in RM (definition of a measure, correlation of TEs and TPs to it,
graphic and report interface) are kept unchanged for WDM.
1.1.11 B1 based PM
The B1 byte, as part of the RSOH will be accessible only in 3R transponders, where the overhead contents
may be accessed and analyzed.
The monitoring of the incoming signal permits to detect errors occurred in the section between the current
DWDM NE and the adjacent SDH/SONET NEs.
The monitoring of the outgoing signal permits to detect errors occurred in the DWDM Domain.
Although this kind of measurement is unidirectional, it could be used as acceptable approximation of the
QoS of unprotected optical path in pre-OTN context.
1.1.12 Acronims
In the following some simplified definitions of the resources managed by 1354RM (formal descriptions of
a lot them are available in G.803, G.805)
Subnetwork: It represents the second level of partitioning (i.e. a Network can be composed by more than
one sub-networks)
ET (Elementary Topology): It represents the third level of partitioning (i.e. usually ETs are contained in sub-
networks). The elementary topologies can be linear links, meshed sub-networks, rings)
Physical Connection: It is the logical representation of fibers and coaxial cables, between network ports
Example: The physical connection delimited by to network ports, e.g. two OTS physical ports.
· Network port: It represents the physical port where e.g. the fiber is connected.
Example:
A STM-16 port of a SDH NE.
An OTS port of a DWDM NE.
· Access port: It represents the physical port where the client signal is added/dropped.
Example:
A PDH port of a SDH NE.
The physical port of a Transponder in DWDM NE.
Example:
MS-Trail between two STM-n ports of two adjacent SDH NEs.
OMS-Trail between two OTS ports of two adjacent DWDM NEs.
· HO (Higher Order) Trail:
An HO Trail is a HO route (e.g. infrastructure pipe) between two (either adjacent or not) SDH
NEs. It is delimited by two CAPs (Client Access Points) and it can be configured to carry LO traffic.
Path: A path (can be at either HO or LO path layer) is a route established in the SDH/SONET network.
It is delimited by NAPs (Network Access Points).
Example:
A VC-12 path delimited by two VC-12 NAPs
A Client path delimited by two Client NAPs (RS-TTP for SDH signals)
Link Connection: It is an arc delimited by the two CTPs with the same timeslot and it is supported by the
same server Trail
Example:
An Au-4 Link Connection is delimited by two corresponding AU-4 CTPs and is supported by a MS-
Trail.
An OCh Link Connection is delimited by two corresponding OCH CTPs and is supported by an OMS
Trail
CAP (Client Access Point): It terminates a HO-Trail; one CAP can support Lower Order CTPs.
Example:
A VC-4 CAP can support TU-12 and/or TU-3 CTPs (depending how the payload has been config-
ured) it terminates VC-4 HO-Trail).
An OCH CAP supports a channel in OTS signal and terminates an OCH Trail
CTP (Connection Termination Point): It is an intermediate point and, depending on NE capabilities, it can
provide non-intrusive monitoring functionalities in term of alarms and Performance Monitoring.
Example:
An AU4-16c CTP delimits an AU4-16c link connection.
An OCH CTP delimits an OCH link connection
The related layers extend the transport control capabilities at OCh level. The capability for supporting
these layers is what makes the difference between the so-called "pre-OTN" (client signal directly mapped
into an OCh) and the actual OTH.
The OTH layers have been added taking "inspiration" from the SDH experience to provide:
– A new mapping method, which maps a client signal of any rate (up to payload capacity) into con-
tainers at predefined bit-rates. This also allows mapping a synchronous signal (SDH) into an asyn-
chronous one (WDM). Containers at predefined bit-rate bring to a client-independent networking.
– Embedded associated overhead information for management and networking purposes very similar
to the ones defined for SDH (monitoring capability, support of complex connectivity and protections).
– Capability to support important functional extensions such as hierarchical multiplexing and concat-
enation (scalability)
The layering in OTH architecture is defined as follows
The index k specifies the rate of the signal supported by each Optical Channel, according to the following
convention:
The OCh additional layers are introduced in OTH in order to support the network management and super-
vision functionality through the contents of the additional signal overhead (OH) of the Units.
The Optical Channels, mapped to the OCC structure, are transported into an information structure named
Optical Transport Module (OTM-n).
The so-called OTM-n with full functionality transports an additional overhead: the OTM Overhead Signal
(OOS). OOS contains overhead information, related to OCh, OMS and OTS sections.
The OSS information is mapped into a separate channel named Optical Supervisory Channel (OSC).
The index n in OTM-n specifies the number of OCC transported by the structure (not including the OSC).
OTM-n plays a role similar to STM-n in SDH architecture, the OCCs act as tributary slots within the OTM-
n structure.
The following ITU-T picture provides a mapping between the logical resources and the physical ones,
applicable to OTN network based on G.709 capabilities.
1.2.3 Examples
In next pages some 1354RM screenshots are described as examples.
In this picture the structure of an alarmed 10Gb/s OTU trail is show. The related ODU2 multiplexes 2
equipped ODU1 services; one of these 2 ODU1 services carries a faulty Client paths (DS).
In this picture the routing of the previous OTU trail is highlighted on the map
In this picture the routing of the faulty client path, mentioned in the first screenshot, is shown on the map;
it is terminated in 2 1670SM.
Figure 22.shows an example of WDM network interworking with SDH network. The navigation of OTS
conn. and OPS con is described in the paragraphs which follow.
Figure 22.shows an example of WDM network interworking with SDH network. To navigate from Netview
map:
a) Click twice on a OTS physical connection. The physical connection list is displayed.
b) Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed. See Figure 23.herebelow.
In the following are listed the allowed navigation for each layer:
OCH layer
– OCH trail => Routing Display
– OCH trail => OCH Trail Structure View (or Client Trail Structure View)
– OCH link connection => Client Trail Structure View
– OCH raw connection => OCH Raw Connection Routing Display
OTU layer
– OTU trail => Routing Display
– OTU trail => Client Trail Structure View
– OTU link connection => Server Trail View
– OTU link connection => Client Trail Structure View
ODU2/ODU1 layer
– ODU2/ODU1 raw connection => Raw Connection Routing Display
– ODU2/ODU1 trail => Trail Routing Display
– ODU2/ODU1 trail => Client Trail Structure View
– ODU2/ODU1 link connection => Server Trail View
– ODU2/ODU1 link connection => Client Trail Structure View
client trail structure view: starting from any layer (OTU, ODU2, ODU1 or DS), all the defined client
layers are shown (in terms of trails, CAPs, link connections and nodes)
server trail view: starting from any layer (OTU, ODU2, ODU1 or DS), the server trail up to the OCH
layer are shown. The server trails are shown up to the layer where the two end points of the trail are
the same of the trail/link connection of the starting layer.
The following figures show some scenarios related to these new views.
Figure 30. Client trail structure view (starting from OCH trail/link connection)
Figure 32. Server trail view (starting from ODU2 link connection)
Figure 22.shows an example of WDM network interworking with SDH network. To navigate from Netview
map:
a) Click twice on a OPS physical connection. The physical connection list is displayed.
b) Select the WDM physical connection and click on Physical connection structure button. The OTS
Physical connection structure is displayed. See figure herebelow.
c) Figures which follow show the attributes of the WDM port, equipped on the WDM node and of the
WDM port, shadow of the SDH port equipped on the SDH node
d) Click twice on the SDH Physical Connection icon; the SDH Physical connection structure is dis-
played.
During the physical connection implementation, the protected OMS trail is discovered and created in the
RM MIB.
The following figure describes a possible scenario for OMSP protection at OMS layer.
– management of the OPS physical connection between the OTS port of the WDM NE and the OPS
port of the OMSP board
– OPS ports belonging to the OMSP board are involved in a OMSP protection schema in order to per-
form compatibility checks during OPS physical connection creation
OCH TRAIL
SEQUENCE
a) Network Create
d) Create WDM NE
NOTES
If you select connection type=WDM, you will further select the WDM connection type between
OPS and OTS, where:
OTS ( Optical Transmission Section ) is used for connections between different WDM nodes.
OPS ( Optical Physical Section ) is used for connections within the same WDM node, originated
and terminated to the same node.
• the connection type for Generic Digital Client/WDM interworking is selected when connecting
to a virtual NE which represent Ethernet equipment.
N.B. The rate of the SDH to WDM transponder ( STM-1 / STM-4 / STM-16 ) is previously set at
1353NM level.
N.B. The rate of the SDH to DATA transponder ( STM-1 / STM-4 / STM-16 ) is previously set at
1353NM level.
– Before creating a connection between SDH equipment and 1696 equipment, it is required
to create on NM a (dummy) MCC board tuned to the desired lambda. Then execute a NE
synchronize from RM.
– Before creating a connection between SDH equipment and 1640 equipment, it is required
to create on NM a (dummy) TRB201 board tuned to the desired lambda. Then execute
a NE synchronize from RM. This operation is not required if the real board is present in
the equipment.
e) Create Connection. (step1 ) The example which follows details the WDM- OTS connection. Start
the Create Connection wizard from the originating Node. Step 1 of the wizard allows to select con-
nection type= WDM and WDM connection type=OTS. See following figure. Click on Next button.
f) Create connection- step-2 allows to select originating and terminating port to connect.
g) Create connection- step-3 contains the icons of the two ports to be connected. Click on Finish button
to confirm the creation. The OTS connection is created.
h) Implement the OTS physical connections. See Figure 53.on page 73.The optical client paths are
automatically discovered.
N.B. In case an OTS physical connections does not iclude its OCH-trail, as in the following figure,
where a raw connection is present, it is required to execute the payload setting of the raw con-
nection.
With reference to Figure 51.on page 72, select the raw connection and click on functional button PAY-
LOAD CONFIGURATION. The Payload Configuration dialog box is presented. See Figure 52.on page 73.
Click on button SETUP. The raw connection changes into an OCH-trail. At this point it is possible to imple-
ment the physical connection. See Figure 53.on page 73.
DEFINITION
The raw connection is terminated generically to a CAP, CTP, NAP. The raw connections between two
CAPs ( Connection Access Points ) and the raw connections between two NAPs ( Network Access Points
) are said complete raw connections; in particular the raw connection between two CAPs is a trail, while
a raw connections between two NAPs is a path.
TYPE OF CONNECTION
In particular, when an optical physical connection is implemented, the system discovers all related
fixed connections ( one per each optical link connection ). Two levels are available:
• Client
An example of routing display of a raw connection is shown in the figure which follows.
GENERAL OPERATION
a) During the implementation phase, the system uploads ( discovers ) the permanent ( fixed ) connec-
tions and constructs the raw connections, by taking into account the uploaded connections.
b) The raw connection userlabel is assigned automatically and makes use also of special characters
( e.g. $ )
c) Complete raw connections are automatically transformed to trails and paths, if all involved link con-
nections are implemented.
a) The deallocate of a path causes the identification of the permanent ( fixed ) connections and the re-
construction of the raw connection
CONSTRAINT
The raw connection can be used as constraint ( the only option Use Main is available )
The raw connection can be extended / shortened / splitted / promoted to path or trail / deleted.
By inserting new fixed connections within the NE, new raw connections are obtained.
NOTE 2 It is not possible to implement manually paths/trails derived from raw connections. The user must
configure the involved physical connection or configure a related trail in use by the path to obtain the auto-
matic implementation of the transport object.
a) To remove a connection in topology from a complete raw connection, point to the connection in topol-
ogy and issue Connectivity Management: Remove from Raw Connection
b) The raw connection is split into two parts. See figure which follows
a) To add a connection in topology to a raw connection, point to the connection in topology and issue
Connectivity Management: Add to Raw Connection. See figure which follows
The scope of this procedure is to add a new transponder to a 1640WM optical equipment.
CONDITIONS
SEQUENCE
Verify that the och-ctp (one per each lambda) passes from unequipped to equipped. From the Port
Structure view the unequipped och-ctp are displayed. Notice that the attribute Equipped Type of an
equipped och-ctp is equal to Equipped.
N.B. In case on a trail has been issued the command Configuration: Payload: No Client, it is
possible to modify the attribute to Client. See following figure.
c) Execute the payload configuration of the OTS physical connection. See following figure.
The scope of this procedure is to increase the size of the lambdas in the 1696WM optical equipment, i.e.
an optical MUX/DEMUX is added.
CONDITIONS
SEQUENCE
Verify that the och-ctp (one per each lambda) passes from unequipped to equipped.
Verify that the connectivity objects ( LC, trail..) have been correctly created.
The scope of this procedure is to increase the size of the lambdas in the optical equipment, i.e. an optical
MUX/DEMUX is added.
SEQUENCE
Verify that the och-ctp (one per each lambda) passes from unequipped to equipped.
Verify that the connectivity objects ( LC, trail..) have been correctly created.
1.7.7 2x1GbE
This is a new board developed for both 1696MS and 1626LM. The first NE release providing the visibility
of the board is the 1696MS R3.0.
To manage the inter-working with an SDH network (the inter-working is already possible with the 4xANY
and it is required for Wind in Italy), an object remapping has been designed.
For the 4xANY, RM was able to distinguish the port client side (gMAU – data port) from the STM-16 (osPI
– optical SDH port) and to complete the model with fictitious objects in its MIB
In order to perform the re-mapping for the 2x1GE board, RM is able to distinguish the Ethernet (client
side) and the STM16 ports (network side) from the ports of the other transponders, either during network
construction or when alarms/events are received.
The trigger provided at the Q3 interface by the NE to distinguish the ports of the 2x1GE board is the sup-
portableClientList attribute, filled with gMauCtp for the client Ethernet port and with genericDataTrCtp for
the STM-16 port.
Having this information RM creates a data port (for the ogPI client side) in the RM MIB and the Virtual-
Concatenation Model.
For the network side, when uploading the ogPI (supportableClientList=genDataTrCtp), an SDH port is cre-
ated in the RM MIB.
When setting-up a data path involving the NAP associated to the first drawer, the server VC TTP’s (CAP’s
in RM) are cross-connected with the AU4 CTP’ s (1 to 7) on the created SDH
When setting-up a data path involving the NAP associated to the second drawer, the server VC
TTP’s (CAP’s in RM) are cross-connected with the AU4 CTP’ s (8 to 14) on the created SDH port.
From the alarm management point of view, the specificProblem provided by the NE is used as a trigger
by RM to distinguish between alarms on the ochGdcCtp, network side, and the alarms received on the
ochgdcCtp, client side. The value of the specificProblem has semantic client side or network side.
The probable causes provided by the 2x1GE board on the ochGdcCtp are SSF, AIS (network side); LOF
(network side).
Upon SSF on NAP, the client data path is impacted with probable cause Transport Failure; upon AIS on
the NAP or LOF on the data port, the path is impacted with Client failure.
Requirements are:
• Single network construction view: client layers automatically notified about connectivity set-up
at server layer, to avoid inserting redundant information
• Simple way to get which client services are supported by a server layer: this allows simplifying
OAM andfault analysis (e.g., for the feature context, which Ethernet physical links are impacted
by a fault at WDMlayer)
• Fast identification of the root cause of a service fault: e.g. from a faulty Ethernet segment to the
faulty Ethernet cable in BM and then to the faulty WDM link in RM
Above requirements are already covered from the user point of view e.g. in case of SDH over WDM ser-
vices Currently the “Ethernet Physical on DWDM view” in RM/BM is the one depicted below:
This because:
• 1354RM doesn’t see the Ethernet interfaces on the 1850TSS-320: the operator needs to use
an external network to terminate the Digital Signal Path (DWDM domain) as a work-around.
There is no direct relation between the created External Network and the real Ethernet inter-
faces
• 1354BM doesn’t see the DWDM network: no relation between Ethernet layer managed by BM
and DWDM layer managed by RM. No simple way to navigate through different layers (difficult
fault localization and OAM planning)
– upload from 1850TSS-320 of local (GE) Ethernet interfaces (through SNMP interface) and store
them as Ethernet ports in RM MIB
– create (on user’s request), an ETH/WDM inter-working physical connection. The user is provided
with a list of Nodes supporting ports of “Ethernet” technology at one end and with the list of ports sup-
porting WDM/ops0 at the other end. The user selects the two nodes and the two ports.During phys-
ical connection creation, the Ethernet port is cloned into an OPS port with related optical NAP
– create the physical connection with technology=Ethernet in the RM MIB as soon as a Digital Signal
Path (ending on ports cloned from the Ethernet ports) is created/discovered. The physical connec-
tion is visible in the Ethernet Layer Map to impact the Ethernet physical connection upon reception
of alarms on the port (LOS probable cause)
The feature allows the management of the CWDM MUX boards, with the complete TPs chain provided
by the NE.
The OTS port related to a CWDM MUX, is characterized, in RM, with the information that it is a coarse
one (wdmBandIdent attribute of the “port” object). This information is retrieved from the NE by means of
the“otsBandIdentification” attribute of the otsTTPBid object (coarseBand value).
A coarse OTS port can only be connected to another coarse OTS port. The physical connection is char-
acterized with bandwidth “coarse band”.
The physical connection payload structure shows as equipped the eight lambdas provided by the current
CWDM MUX, that are: 1470, 1490, 1510, 1530, 1550, 1570, 1590 and 1610 nm. The other lambdas, not
managed by the NE but displayed in the physical connection payload structure, are: 1270, 1290, 1310,
1330, 1350, 1370, 1390,1410, 1430 and 1450 nm.
If the ctp is present on the NE, it is marked as equipped, otherwise is marked as bundle=och-ctp not
present on the NE but the associated lambda is passed through.
Bundle OCH-CTPs are put in fixed pass-through connections in RM, only if the corresponding OCH-CTP
with the same lambda on the other OTS port is Bundle. See following figure. The icon of a bundle OCH
is marked by a B letter.
N.B. NOT EQPD (not equipped) means och-ctp present in RM but not in NE due to the hardware
configuration.
1.9 Display of the correlation between WDM world and SDH world
SEQUENCE
a) Point to the wdm path icon and issue the Interworking: SDH Connection pop-up menu. The SDH
physical connection structure is displayed. See Figure 72.herebelow.
Note that the client path icon is marked by a smal raw connection mark. See figure herebelow.
On the other hand, in the Optical Physical connection view , the client path icon is marked by a raw con-
nection mark.
SEQUENCE
a) Point to the wdm raw connection icon and issue the Configuration: Convert in Path/Trail pop-up
menu item. The SDH physical connection structure is displayed. See figure herebelow.
A report is displayed, to verify if the action has been correctly executed. See below figure.
1.11.1 Introduction
The Connect/Disconnect tool is provided to the user to manually modify connectivities within the NE, i.e.
the x-conns w/o using the EML layer.
The scope of this procedure is to create a connection within an OADM by means of the connectivity tool.
SEQUENCE
b) From the Connectivity Tool wizard step 1 select Connect. Click on Next button.
c) If you click on Port selection, you will display the port list from which you can select the port to con-
nect. Click on CTP selection, you will display the CTP list from which you can select the CTP to con-
nect. Click on Next button.
d) From step 3 wizard you can select the 2nd CTP . Click on 2nd TP to connect selection button
and select the CTP from the list.
e) Click on Finish button. The connection is created. See the Connection create report on the figure
which follows.
The scope of this procedure is to delete a connection within an OADM by means of the connectivity tool.
SEQUENCE
a) From the map click twice on the OTS link, getting the physical connection list.
b) Select the WDM physical connection and click on Physical Connection Structure button. The OTS
Physical connection structure is displayed.
c) Optical paths and OCH trails must be removed to proceed in disconnecting the OTS connection.
Optical paths and OCH trails will become raw connections
d) Point to optical path (so called client) and issue Configuration: Conf. State Modification: Deimple-
ment. A warning dialog box alerts that the optical path is correlated to an implemented SDH logical
connection (so called physical connection). The optical path will be deimplemented but the SDH log-
ical connection will not be removed. See below figure.
f) Figure wich follows shows the routing display of the raw connection replacing the OCH trail
Connectivity tool. Step 1 is used to select the action, in this case DISCONNECT. Click on Next to pass
to step 2.
i) Connectivity tool. Step 2 allows to execute the following operations: (See Figure 87.)
– selection of the Port to disconnect. From the Port list select the port and click on Apply. The selected
port icon is shown in the wizard main window.
– selection of the CTP to disconnect. From the CTP list select the CTP and click on Apply. The selected
CTP icon is shown in the wizard main window.
j) Connectivity tool- Step 3 shows the data previously selected by the user, asking for confirmation.
Click on Finish button to continue deleting the connection.
As an example: If we select CTP-x sited in Milan, via the involved far end CTP-y sited in Bozen, it is pos-
sible to understand that the choice of CTP-x allows to realize a connection Bozen-Milano
The scope of this procedure is to modify a connection within an OADM by means of the connectivity tool.
CONDITIONS
SEQUENCE
a) From the Connectivity Tool wizard step 1 select Modify. Click on Next button.
b) From step 2 wizard you can select the Port and the CTP. Click on the PORT list button and select
the Port from the list. Click on the CTP list button and select the CTP from the list. Click on Next but-
ton.
c) From step 3 wizard you can select the connection type. See below figure. Click on Finish button to
render effective the change.
The Connect/Disconnect tool supports the user in the selection of TP' s involved in the connectivity, keep-
ing into account possible constraints present at NE level (e.g. OADM WDM NE' s).The Connect/Discon-
nect tool can be activated starting from one of the following cases:
3. Node selected
4. Port selected
5. CTP/CAP selected
6. NAP selected
Alternatively the cable can be described in cable-list using CT or NM and `upload connectivity' request
can be launched from 1354RM to automatically create the internal physical connection. See para 1.12.2
for other details.
Physical link between a 1696MS mux/demux and a colored interface SDH can be obtained in RM only
instancing a phantom MCC board on ne by NM.
The phantom MCC has to be associated to the involved mux/demux, the frequency has to be that of the
optical signal coming from SDH interface, the type has to be set according to the rate/type of the signal
that has to be transported.
This problem is due to ne software which didn't provide a GOC OPS port as interface to mux/demux.
Alarm (such as URU) on this false MCC has to be eventually inhibited by the user toward NM or CT (see
also point 14). Pay attention that an audit followed by a download from 1354RM will overwrite ASAP on
MCC and URU will reappear.
4xAny board connected to an OPC card or to an MCC board. phantom coupled MCC board are used to
visualize a pass-through between two mux/demux (see para 1.12.1.).
1.12.6 Upgrading 1696MS to add new lambdas management without loss of trafic
A special feature available on 1696MS allows to equip new lambdas adding other mux/demux board. This
operation can be done without trafic loss if done according to specific upgrade rules (see specific ne doc-
umentation).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new Och-Ctp over OTS port, then and a pay-
load configuration of physical link is needed to create transport object involving new equipped Och-Ctp(s).
When management of new lambdas is added to ne and OTS port of this ne are already assigned to
1354RM a global download action is needed in order to see new Och-Ctp over OTS port, then and a pay-
load configuration of physical link is needed to create transport object involving new equipped Och-Ctp(s).
These board are transparent at 1354RM level. The optical signals multiplexed by SPV_xxx boards are
seen in 1354RM as they are transported by different OPS physical links, while the OSC signal is never
managed in RM.
SEQUENCE
For creating the two OPS physical connections between External Network Element and 1626LM OPC
port:
b) The Create Physical Connection Wizard window opens : the connection type to select is Generic
DigitalClient/WDM Interworking.
d) Select the 1626LM NE and the Upload Tools to discover the network connectivity.
e) The physical connections between OCP board protected/ protecting ports and transponders are
uploaded and implemented checking the box on the wizard window.
Figure 99. Network map: the discovered Client path icon is displayed
Looking at physical connection structure, the discovered Client path icon is displayed.
Select the Routing Display Icon to view the protected path routing.
a) Create the ILA node. The node creation is the same operation performed for other type of nodes.
See section OPERATION for details.
b) Create the OTS physical connection, using OTS ports, of the involved NEs. The creation of Physical
connection is the procedure detailed in section OPERATION for OTS Physical connections.
d) One of the physical connections involving ILA NE is shown below. Notice that the displayed window
contains an additional routing display icon representing the OMS trail. In the fact the no. of hops may
be greater than one. It is obvious that the routing display of the OMS trail becomes available only
after the creation and implementation of the entire span, i.e. with all physical connections and ILA
nodes of the entire ILA chain comprised between the two WDM NEs.
OMS TRAIL
e) Clicking on this additional routing display icon, the OMS routing display is presented as displayed
in figure below
N.B. The ILA OTS ports can be connected either to NE line terminals/OADM or to another ILA NE,
according to network configuration. More ILA NEs can be used.
EXAMPLE
a) Starting in layer All Physical NO ILA, ( see above figure), the 1st physical connection has been cre-
ated. The OMS trail is not yet available. See figure below.
d) Select the icon Synchronize to display the map without ILA NEs.
e) Change the layer from All Physical NO ILA to All Physical. The connections involving the ILA node
are shown.
f) In addition, as a consequence of the implementation, the OMS trail icon is now available. See fol-
lowing figure.
The user may choose the layer All PhysicalNO ILA to avoid the display of the ILA nodes.
Notice that in the NO ILA layer, the number displayed above the Physical link line includes the direct link
between the two NEs (no ILA) and the link between the two NEs passing through ILA NEs. The user (see
figure above), can display all Physical connections between the two NEs, including those connecting ILA.
Figure which follows shows the physical connections contained in the WDM physical link including the
connections between ILA NEs.
N.B. The insertion of an ILA NE in a physical connection can be done via command split OTS phys-
ical connection too. (See Sect Operation: Join-Split Physical connection)
The scope of this procedure is to drive the user in creating the network to make use of the 9X1 GBE board.
The Concentrator board supports 9 client ports, i.e. 9GbE clients can be transported via a 10GbE signal,
with fixed connectivity.
When the user implements the physical connections, RM transport objects are created through the dis-
covering of the fixed connectivity in the NE.
In particular, the Digital Signal trail, multiplex of the 9 Digital Signal paths, is discovered and created in
RM MIB.
Figure below shows the target network. A DS path is highlighted from Ext Node 100 to Ext Node 200. This
1GB is de/multiplexed from/to the 10GBE port over STM-64 by the concentrator node 1626_3. This signal
enters in node A, is colored by the transponder and de/multiplexed (WDM) by the lambda mux. The signal
then crosses nodes B, node 4 and Ext200 which are respectively specular to nodes A, 3 and Ext100.
The Digital Signal trail, multiplex of the 9 Digital Signal paths, connects nodes 3 to node 4.
Note: Nodes A,B from Rel.3.0 on. Nodes 3,4 from Rel.4.0 on.
3 4
DS path
DS trail
3 4
A B
SEQUENCE
a) Setup of the Concentrator (for nodes 3 and 4 in this example) (NE Rel. 4.0 on)
b) Cross Connection Create (for nodes 3 and 4 in this example) (NE Rel. 4.0 on)
The scope of this procedure is to setup the hardware relevant to the concentrator.
a) From the equipment view select the slot (e.g. slot 12) and issue Concentrator: Equipment Set
d) Click twice on the board: the detail opens. Figure below shows the ETHC1000 board upper detail
e) Move down the scroll bar. Figure below shows the ETHC1000 board lower detail. Nine 1GB ports
and one 10GBE can be equipped.
g) In the 1 GB port type selection box select the board type (e.g. short haul) and click on OK. The 1
GB port is drawn in the port detail. Repeat the 1GB port creation for the remaining 1GB ports (max
of 9, including the first one)
i) In the 10 GB port type selection box select the board type and click on OK.
k) Figure which follows shows the ETHC1000 upper detail with the equipped 1GB TPs. Select menu
Configuration: Connectors/Cabling
n) The ports equipped in board 12 are listed. For each board expand the channels.
q) All channels are in service (marked by the lock). Click on button Trans Update, which creates the
ports in the NE
s) From browser select the involved NE and execute Synchronize: Synchronize NE. Ports are
uploaded from NE.
The scope of this procedure is to create the X-con within the OCH port. i.e. to create the OCH trail
a) From the detail of port 13 select Port: OCH: Cross connection: Create Cross connection
b) The Main Cross connection box is displayed. Click on button Choose Output
d) In the Main Cross connection box both input and output are specified. Click on OK to create the OCH
trail.
e) The OCH trail is now present. The OCH of port 13 is marked by the connection icon ( X )
f) To display the cross connection just created, select the OCH of port 13 and issue Port:Cross Con-
nection: Modify Cross Connection
g) The Cross Connection Management dialog box opens, displaying the cross connection just created.
The scope of this procedure is to complete the creation of the network, creating al the required physcons
CONDITIONS
The required nodes have been created and the aligment from EML layer to NML (RM) has already been
executed via commands of update and synchronize
SEQUENCE
b) In the port selection box, opened via the dedicated button, select the A-OTS port and click on Apply
c) With the same modality, select the B-OTS port and click on Apply. In fig below both ports are selected.
Click on button Finish.
f) The Create Physcon box opens. Select type=WDM and enter name= OPS_A_3
h) Create Physcon: port 13 selection. Select the port of node A. Select Yes for the pleonastic question
below the port selection area. Namely the bit rate is consistent. Click on Finish.
k) Create the physcon OPS_B_4 and implement it. See below figure
l) On implementation of the physcon OPS_B_4, RM transport objects are created through the dis-
covering of the fixed connectivity in the NE. In particular, the Digital Signal trail, multiplex of the 9 Dig-
ital Signal paths, is discovered and created in RM db. See implementation log herebelow.
m) The Digital Signal trail, multiplex of the 9 Digital Signal paths is represented by a dedicated icon in
the physcon structure
OCH DS
n) Clicking on OCH trail icon, the trail view is displayed. See below figure
p) In the Create Physcon box select type=Generic digital client and enter name= 1GB fst
r) Select the first 1GB port in the concentrator board. Click on Finish.
u) The 1 GB fst, implemented, is shown below. the raw conn icon is displayed beside the OCH trail
x) Select the first 1GB port in the concentrator board. Click on Finish
N.B. Per each 1GB connection the user must create the two physcons to EXT-100 and EXT200.
- Create XCO on the ETHC on both NE with the WDM connectivity tool. Refer to 1.11 on page 91
DS path
DS trail
1626-50-2 1626-40A-2
1626-50-2 1626-40A-2
TRBD TRBD
ETHC 1191 1191 ETHC
OMDX OMDX
CABLE CABLE CABLE CABLE
EXT EXT
The procedure is subdivided in the following subprocedures, which are described in the following:
The scope of this procedure is to remove client path and och trail
SEQUENCE
a) Click twice on the physical link. The list of the contained physcons is displayed.
c) From ots physical connection structure, point to the och trail crossed by a path and click on button
structure. The client trail structure view is shown below
d) From the trail structure view select the trail and issue Search: All related Items
e) Select Paths (with end points) and click on OK. The client path is present in the list (right-hand side
of below figure). The relevant path highlight view is shown inthe left -hand side of below figure
f) Remove client path, clicking on button Remove Transport.. A confirmation is required. click on OK
to confirm.
h) Set to "no client" the DS trail that's removes the 7 VCG created before.
i) Point to the trail and issue the menu Remove. A confirmation is required. click on OK to confirm.
j) The involved DS trail is removed and graphically replaced by the raw connection (allocated)
Figure 176. DS trail removed and graphically replaced by the raw connection
The scope of this procedure is to remove the X-con with connectivity tool.
SEQUENCE
b) The connectivity tool opens with the involved node already selected. Select option Disconnect. Click
on Next button
d) From the port list select port no. 13 (type OPS) and click on Apply button.
e) Port no. 13 is now present in the selection box. Click on icon of selectable CTPs
f) From the list of the selectable CTPs, select the CTP involved in the connection and click on Apply.
g) Both port and CTP have been selected. Click on Next button.
h) Step 3 of the wizard shows the detail of the cross connection being deleted
SEQUENCE
a) Select the involved node and click on tool button icon Ports, in order to get the list of the ports
b) The port list is show (see figure below). Notice that ports 01 and 101 appear both selected, Namely
we have to deimplement and remove the autodiscovered physcons connected to the transponder,
one on port 01 (B & W side), and the other on port 101 of the MUX (colored) side. Select one of them
e.g. point to port 01 (B & W side) and issue Search: All Related Items: Physical Connection structure
c) The physcon structure is shown below. Point to the autodiscovered physcon connected to port 01
(B & W) and issue Configuration: Deimplement
d) Remove the autodiscovered physcon connected to port 01 (B & W) by selecting menu Configura-
tion:Remove
e) From the port list point to port 101 (colored-MUX side) and issue Search: All Related Items: Physical
Connection structure
g) Point to the autodiscovered physcon connected to port 101 (colored-MUX side) and issue Config-
uration: Remove from RM
SEQUENCE
a) From the port list point to port 01 (B & W) and issue Search: All Related Items: Physical Connection
structure
b) From the I/W physcon structure view, point to the physcon and issue Configuration: Deimplement
SEQUENCE
a) Point to the node being deleted and select Node:Search All related Items
c) The list of the physcons connecting the node is displayed. Select all Physcons, except the OTS phy-
scon and select menu Configuration: Remove
SEQUENCE
a) From the OTS Physcon select the OTS Physcon and issue Configuration:Deimplement
SEQUENCE
The scope of this procedure is to drive the user in creating the network to make use of the 2X1 GBE board.
The 2xGE_FC unit is a concentrator which aggregates two Gigabit Ethernet client signals at 1.25Gbps
or two Fiber Channel client signals at 1.0625Gbps into a STM-16/OC-48 frame, via GFP mapping and Vir-
tual Concatenation.
It is optically connected, according to the provisioned interface, either to a TRBC (if B&W line interface)
or to a CMDX/OMDX (if WDM line interface).Four interfaces/ports are present on client side, but only two
can be used (U1 and U2 on the front plate).
The supported clients are Gigabit Ethernet (1.25 Gbps) with supports of jumbo frames (9.6kbytes) and-
Fiber Channel (1.0625 Gbps).
Clients mixing on the same board is not possible: only 2xGbE or 2xFC is possible in the same board.
– (VC-4-7v) is used for Gigabit Ethernet. The allocated VC-4s are listed herebelow:
– (VC-4-6v) is used for Fiber Channel. The allocated VC-4s are listed herebelow:
SEQUENCE
b) Setting modules FC
f) Create network
The scope of this procedure is to setup the 2x1 GB & STM-16 boards
SEQUENCE
b) From the Equipment folder issue Config: 2 GB (2x1 board) setting and click on Apply to confirm
c) From the Equipment folder issue Config: Config: STM_16 board and click on Apply to confirm.
SEQUENCE
a) Select the module from the left part of the view and click on folder Configuration in the right-bottom
part of the view. To convey FC signal select option 2FC_SX_DDM and click on Apply.
The scope of this procedure is to setup the 2x1 GB & STM-16 boards
SEQUENCE
SEQUENCE
a) From the Equipment folder issue Config: 2 GB (2x1 board) setting and click on Apply to confirm
Selection of FC or GBE
b) From the WDM folder select: General Information: GBE and click on Apply to confirm.
c) Equip the 2nd module via command Eqpmt: Config: 2 GBE_SX and click on Apply
d) From the WDM folder select: General Information: GBE and click on Apply to confirm.
SEQUENCE
b) The previously declared ports are uploaded. The port list from node is shown below.
c) The NAP upload command is not requested if during network creation the NAP automatic upload
has been previously selected
N.B. All procedures described above refer to node 1. The same procedures must be run for node
2 symmetricaly, and are not described here for aim of brevity.
The scope of this procedure is to create the network objects to carry the 2GBE boards
The network schema is shown below. The OTS physcon connects the two NEs, while IW and OPS phy-
scon are internal to the network element. IW joints the STM-16 port, acting as mux for the two 1GB mod-
ules, to the transponder B&W to colored. OPS physcon joints the colored out of the transponder to the
optical mux in, according to the mux presetting. In our case in p9 (1550 nm) is used. For more detail refer
to NE 1692 Technical Handbook
1692-1 1692-2
The Network schem with the transport objects is shown in figure which follows
physcon STM-16
DS path
1692-1 1692-2
SEQUENCE
SCOPE
The scope of this procedure is to create the OTS physcon betw WDM nodes
SEQUENCE
a) From the map select the two nodes and issue Create: Physical connection
b) In the Create Connection dialog box select type= WDM and WDM type=OTS, enter the name and
click on OK.
SCOPE
SEQUENCE
c) Select the node (the same node) and the port, according to the network schem previously shown.
e) The OPS physcon transponder_WDMmux is created and the physcon structure is shown below.
SCOPE
The scope of this procedure is to create the physcon SDH_WDM interworking (STM16_transponder)
SEQUENCE
c) On the same node select the 2nd port (the input of the transponder)
N.B. All procedures described above refer to node 1. The same procedures must be run for node
2 symmetricaly, and are not described here for aim of brevity.
g) Notice that after the implementation of the last physcon of the chain, on node 2, the client path is dis-
covered and the SDH transparent physcon is created. See below figure.
h) The implementation log, according to the schema of the transport objects, is shown below.
j) The SDH transparent physcon, STM-16, contains 16 AU4s (see below the SDH transparent physcon
structure). Notice the icon of the discovered client path.
k) In the map the physcon link now contains two physcons: the OTS and the SDH transparent.
SEQUENCE
b) In the Create step 1 select service type=Ethernet, service rate=1Gb GFP Transparent. Enter path
name=1Gb_1
f) Display the physcon list of the SDH transparent physcon. The 1 GB_1 path makes use of 7 con-
catenated AU4s
g) The 7 concatenated AU4 trails can also be displayed clicking on the trail list button from the routing
display.
h) Create the 2nd path 1 GB_2. Select nodes 1 and 2 and issue Create: Path.
i) In the Create step 1 select service type=Ethernet, service rate=1Gb GFP Transparent. Enter path
name=1Gb_2
k) The 7 concatenated AU4 trails can be displayed clicking on the trail list button from the routing dis-
play.
The Network setup to convey Fiber Channel paths is the same as per path 1 GBE. The only difference
is that in this case FC terminations are used.
path 1GB_FC
1692-1 1692-2
The Network schema with the transport objects is the same as per path 1 GBE.
SEQUENCE
b) Select the ports, according to the network schema and confirm the creation.
e) Select the ports, according to the network schema and confirm the creation.
After the implementation of the last OPS physcon, the raw connection is discovered
g) Create and implement the mirror OPS and interworking physcons on node 2
h) After the implementation of the last interworking physcon, the client path is discovered and the SDH
transparent physcon is created. See physcon structure
l) In addition, the physcon link contains the Transparent SDH physcon (for FC connections)
SEQUENCE
b) In the Create step 1 select service type=DATA, service rate=fiber channel GFP Transparent. Enter
path name=path_FC_1
c) Select terminating ports. Notice that ports must be selected according to the Network Schema of
Figure 251. In particular board 2 d1 of NE 1692_1 must be connected to board 2 d1 of NE 1692_2.
Complete path creation, clicking on Finish
e) From the routing display click on trail list. The list of 6 concatenated trails is shown below.
Figure 264. FC path routing display with 6 concatenated trails in the list
f) In the physcon structure of the SDH transparent physcon the 6 trails are shown.
g) Create FC path 2
h) Select the ports. Notice that ports must be selected according to the Network Schema of Figure 251.
In particular board 2 d2 of NE 1692_1 must be connected to board 2 d2 of NE 1692_2.
i) Create and implement path_FC_2. Figure which follows shows the trail allocation in the SDH trans-
parent physcon.
2xGE_FC connected to WLA with O-SCNP (WLA2M_OP / WLA3CDOP). See below figure
OPC connected to two 2xGE_FC (client side protection). See below figure
a) From Equipment folder set the board. Select 2xGE_FC board type
In case of 1696MS 3.2, using "Client Nature" menu select requested operation mode: Fiber Channel or
Gigabit Ethernet:
Board view is composed of 2 client modules called daughter#1, daughter#2 and output STM16 module
called daughter#6
c) From Equipment menu set the client modules (daughter#1 and daughter#2)
It is possible to setup output module with colored CWDM/DWDM SFP module. In this case it is possible
to select module frequency.
• Synchronize NE
• Upload NAPs
When MCC is configured in local configuration (i.e. associated to MUX board) the cross-con-
nection should be created between port#1-OCH of MCC and OCH-A port of MUX.
When MCC is configured in remote configuration (i.e. without associated MUX board), it is nec-
essary to create cross-connection between port#1-OCH of MCC and port#2 OGPIoch of MCC.
In remote configuration, fiber connection between MCC and MUX should be defined in cable
configuration. Then this link should be uploaded from 1354RM, using Upload Tool and imple-
mented.
Cross-connection can be done using 1353NM or with "WDM Connectivity Tool" on 1354RM.
Create and implement SDH/DWDM interworking physical connection between STM16 port of 2xGE_FC
(port#6) and B&W port of transponder (port#1) within the same node.
If the warning message "The bit rates of who involved ports are not compatible. Do you want to create
anyway the physical connection?" will appear, it means, that probably payload of MCC board was not set
correctly and it's suggested to verify settings from 1353NM, eventually synchronize NE and check "Phys-
ical Port Rate" attribute on the 1354RM.
When all OPS connection on both nodes will be implemented, RM should automatically discover optical
client path and corresponding SDH STM-16 connection, which connects port#6 of 2xGE_FC boards on
both sides.
The scope of this procedure is to realize the protecting network scheme depicted in figure which follows
path 1 Eth
DS path
SDH physcon
p2
p2 b8 b19
193600nm
SDH physcon
Ext 1 2xGbE Ext 2
2xGbE
DS path
path 2 Eth
1696-D 1696-U
DS path SNCP
p2 OPS p2
p1 p1
p3 p3 IW
IW
OPS
Ext-1 Ext-2
SEQUENCE
b) Automatically DS path1 (main) and DS path2 ( spare) are uploaded. See above figure and figure
which follows shows the highlight of DS path1
c) Create the 2 Generic Digital Client/WDM InterWorking physcons betw Ext and OPC (port p1, Reli-
able).
d) Create the OPS main physcon betw port p2 (unreliable) of the OPC
e) Create the OPS spare physcon betw port p3 (protecting) of the OPC
i) In the subsquent selection box select RM Object 1 + OK. The correlation window opens.
j) From browser, point to on one of the physcons, e.g. on the OTS physcon and issue Search: Related
Objects: Paths, to display DS1 path and DS 2 path
k) From the path list on the right-hand side of below figure, drag and drop DS1 path and DS 2 path to
the correlation area of the left-hand side of the figure. Click on Start correlation button.
l) A small icon (blue down arrow) is presented beside theSNCP path icon, meaning the path involved
in relation.
1.21 Multi-degree
SCOPE
The multi-degree arrangement allows to configure more than 2 OTS ports on each node 1626LM R.40A.
The CMDX board accomplishes up to 8 channels. The max capacity of the multidegree OTS port is then
96 channels.
SEQUENCE
j) Synchronize NE
p) DS path discovery
s1b8p101 s1b10p109
BMDX
TRBD1191
s1b16p1
s1b8p1
EXT1
NODE2
s1b2p1 s1b16 p1
s1b16p109
TRBD1191
BMDX
s1b8p1
s1b3 p1
EXT2
The BMDX board accomplishes up to 12 bands. Each band comprises 8 channels. The CMDX board
accomplishes up to 8 channels.
The network planner should consider also that the cost of the equipment required is less than that one
required for the classical R-OADM and T-ROADM.
SEQUENCE
b) In the Set equipment dialog bos select board CMDX1010 and the band, according to the network
schema
SEQUENCE
SEQUENCE
b) Select all relevant modules ( WDM in/out +8 modules) and click on Set to service
c) As a result, all modules + WDM terminations are INS (marked by a lock icon)
SEQUENCE
b) Select all relevant modules ( WDM in/out +12 modules) and click on Set to service
c) As a result, all modules + WDM terminations are INS (marked by a lock icon)
SCOPE
SEQUENCE
a) You can display CMDX modules in the board view (OTS and port 101 to port 108). See figure below.
b) Figure herebelow shows BMDX modules in the board view (OTS and port 101 to port 112)
Figure 299. BMDX modules in the board view (OTS and port 101 to port 112)
SEQUENCE
b) Notice that the CMDX board to be connected to the TRBD being created was assigned to band 9,
i.e. the lambda=12600
d) A subsequent window asks to select the channel. In this case select 192600 accordingly. click on
OK to confirm the creation.
Ì Since the CMDX was assigned band 9, for the TRBD being associated the user should select
one of the lambda belonging to band 9 (192.35-192.70)
e) If you select the TRBD just created, you can verify that the lambda involved is 192600.
The scope of this procedure is to set the STM64 for TRBD board.
SEQUENCE
a) Open (double click) the view of the TRBD board and issue Eqpt: Set
e) For the STM-64 board, select in and out and click on set to service
f) As a result, all modules + WDM terminations are INS (marked by a lock icon)
SCOPE
The scope of this procedure is to set the STM64 for TRBD board.
SEQUENCE
The scope of this procedure is to create the x-con in the TRBD board.
SEQUENCE
b) The Cross Connection: Create dialog box is displayed. Click on Choose button.
e) The internal cross connection is created and you can display the connection (marked by a X icon)
on the transmission view. See below figure
1.21.10 Synchronize NE
After the setting of the hardware components, it is strongly suggested a NE: Synchronize from RM
interface.
SCOPE
The scope of this procedure is to create OTS physcon between the two nodes
SEQUENCE
Two OTS physcon must be created. See network schema of Figure 288. In the following one example
is described
d) In the fact the 8 raw conns are the ones ensured by the CMDX board connected to the BMDX board.
Namely the BMDX board can carry up to 96=12X8 colored signals. Then, if we have already con-
nected a CMDX board, which carries up to 8 colored signals, the 8 raw conns are created and dis-
played. See below figures
The scope of this procedure is to create OTS physcon between BMDX and CMDX
SEQUENCE
This procedure should be separately executed for node 1 and node 2, according to the network schema.
a) Select the node ( see network schema of Figure 288. on page 219) and issue Create Physcon
b) Select A and Z ports. Figure which follows shows port selection=109 for channel 192600 on BMDX
side
d) After the selection of both ports, click on Finish to confirm the creation.
f) The OTS:BMDX-CMDX physcon structure shows the raw conn created for channel 192600
The scope of this procedure is to create OPS physcon between CMDX and TRBD
This procedure should be separately executed for node 1 and node 2, according to the network schema.
Ì The involved fiber cable should be connected carefully on the equipment, according to the
selected terminations.
SEQUENCE
a) Select the node ( see network schema of Figure 288. on page 219) and issue Create Physcon
b) Select port CMDX side. According to the schema should be s1b2p109 (for node 1)
c) Select port TRBD side. According to the schema should be s1b8p101 (for node 1). Click on Finish
to confirm. The Create OPS: CMDX-TRBD log is shown below
d) figure which follows shows the OPS physcon structure with the created raw conn
The creation and implementation of these connections ensures the completion of the multigrade arrange-
ment network schema, which provides the protection. See DS path discovery
WHEN TO USE
This procedure should be separately executed for node 1 and node 2, according to the network schema.
External nodes EXT1 and EXT2 are to separately connected to the transponders TRBD1191, respectively
to node1 and node 2.
SEQUENCE
b) Select port type=STM64 for the external node and the TRBD port according to the schema. Obvi-
ously the equipment setting has been completed previously in accordance.
e) The raw conn is now present in the SDH-WDM interworking physcon structure
·Upon lowBer alarm detection on clientMonitoringBoundary ctp, RM impacts the DS path with Trans-
port Incoming Failure. RM will no more generate Degraded protection (as for the previous release)
the case where the lowBer is detected egress due to a problem inside the WDM should be reported
through FEC TCA (FEC PM has to be manually enabled)
RM does not generate any elementary alarm on the mirrored TP on RM, i.e. on the reliable genCTP on
OPC in case of lowBer (neither ingress nor egress side).
1626LM provides the R-OADM functionality via flexible och cross-connections. R-OADM was already
present in R3.0A but it could be managed only via equipment domain and internal cabling and were
uploaded by RM to provide the WDM connectivity.
OPERATION
R-OADM (Reconfigurable Optical Add & Drop Multiplexer) functionality is depicted in the following picture.
From transmission point of view, the R-OADM offers the same functionality already available with 1696MS
and 1626LM OADM's but the hw of those OADM's was completely different and to reconfigure the network
in terms of lambda connectivity, not simple manual equipment operations were required by the user.
Figure 335. R-OADM (Reconfigurable Optical Add & Drop Multiplexer) functionality
The R-OADM is already available in R3.0A with an architecture based on two new units: the Wavelength
Manager (WMAN1 board featuring as Wavelength Blocker device) and the Optical Add&Drop Coupler
(OADC), combined as represented in the below pictures.
Moreover, the R-OADM is based on MUX/DMUX technology, implying that once the transponder is con-
nected to a port of a MUX/DMUX, the frequency on the Transponder sink is fixed by the coloured port of
the MUX/DMUX.
Each channel processed by R-OADM (2 degree Node) can be in one of five possible states:
-Add&drop on OTS1
-Add&drop on OTS2
-Add&drop on OTS1&2
N.B. OTS will be substituted with OMS for the future NE release that will provide OMS protection.
Each channel has the same state in both direction (i.e. R-OADM is a bidirectional NE).
N.B. The R-OADM functionality, Wavelength Blocker based, as above described, is not shown by
the 1626LM R3.0A with the proper transmission model at management interface, i.e. is not
shown in terms of OCH TP chain and flexible OCH cross-connections. So RM has managed
in a totally "transparent" way R-OADM for R3.0A, through discovery of cables between OPS
ports, set-up by CT/NM use.
N.B. Starting from 1626LM R5.0, the NE provides the capability to manage flexible OCH cross-con-
nections inside R-OADM (2 degree Node).
NETWORK CONSIDERATIONS
Not being the OCH flexibility inside R-OADM complete because, as above described, the frequency on
the Transponder is fixed by the MUX/DMUX port to which is cabled and moreover the association of a
given Transponder to the west or east OTS is also determined by cabling, for each OCH TP of the R-
OADM, the NE provides the list of the connectable TPs (two) where drop/insert or pass-through a channel.
This list of connectable TPs was already provided by the NE for OADM and is used by the RM connectivity
tool in the previous RM releases.
Starting from RM R7.4.9, considering that the WDM network provides more points of flexibility at OCH
layer (not only OADM but also R-OADM and T&R-OADM -see related paragraph), the OCH flexibility
offered by all the above types of OADMs will be managed through the new feature "OCH trail set-up by
user" (please refer to the dedicated paragraph).
This feature allows the user to provide the two end points of the OCH Trail, the needed constraints and
letting then the system set-up the OCH trail route and implement it inside the WDM NEs (through cross-
connection creation).
Without this feature, the user would still manually set-up (through NM or through RM Connectivity tool)
each single cross-connection inside each Node.
To keep anyway the capability, inside RM, to take in charge trails and supported client paths, if already
manually set-up by NM/CT USM, the "Management of flexible cross-connections during WDM port
assignment/deassignment" new feature is also introduced. in R7.4.9
Once taken in charge by RM, the discovered OCH trail will be then managed (e.g. de-implemented or
removed) through RM USM.
A more detailed description of R-OADM equipment and cable setting can be found in the dedicated doc-
umentation: 1626LM R.5.0 Technical Handbook and 1626LM User’s Guide.
r1s2b3
TRBD CM
DX BMDX
O
O 1000
r1s1b2
A
A
D
D
r1s1b3 C
C BMDX
1000
CM
DX TRBD
r1s1b18 r1s1b19
EQUIPMENT SETTING
2) Associate boards WMAN b3 and b16 by means of Board: Modify equipment configuration: con-
tradir
1) In each LOFA you need to put in service the ports, from "Connectors/Cabling" menu : Input/Out-
put 1st stage & Input/Output 2nd stage
For the LOFA declared as LOFA R it is necessary to put in service the OSC input .
For the LOFA declared as LOFA T it is necessary to put in service the OSC output .
In LOFA R the output 2nd stage is connected with input WDM of the BMDX
In LOFA T the input 1st stage is connected with output WDM of the BMDX
Close this menu and from the USM , navigate on the LOFA board .
From this view select the menu select the menu 'Board' -> 'Modify Equipement Configuration'.
After this configuration you can cable all the others boards from the cable connection menu.
CABLE SETTING
All cables, as shown in above figure, must be created via command Add Cable
50-2
add/drop
LINE 1
add/drop
B-OADM
40-A
pass-through
50-1 50-3
add/drop
add/drop
50-ILA
TASK
1) Navigate board WMAN b3 (click twice). In the board view issue Board: Modify equipment con-
figuration
4) In the connector configuration dialog box select board WMAN1100 s2b3 and click on Set in Ser-
vice
TASK
2) Execute the above described Add Cable operation for the reverse direction 3-WMAN-out to 35-
OADC-in.
In addition, moving the mouse pointer e.g. to WMAN Input you can read the performed cable.
Obviously you should have executed the material connection involved.
4) Execute the Add cable operation for all the involved cables.
TASK
1) Execute the upload of the cables for node 50-2 and 50-1, respectively
TASK
2) In the Create OCH Trail dialog box enter trail name and allocation=auto
6) Implement the OCH trail. Issue the routing display. The implementation creates all needed x-
cons (add/drop and pass-through)
SCOPE
The scope of this procedure is to display cross-connection, OCH trail and DS path.
TASK
1) From the equipment view of node 50-2 issue Configuration: Cross Connection management
3) The Cross connection list is shown below. The involved xcon is selected. This is the add/drop
x-con on node 50-2
4) At this point the OCH trail is fully payloaded, with the creation of ODU2, ODU1 and DS path.
Create an OCH trail from 40-A to 50-3 with pass-through xcon on node 50-2
TASK
2) In the OCH trail create step 1 dialog box enter userlabel: OCH_Trail_193250_Pass_Through.
Click on Next.
7) The pass-through x-con is created upon OCH trail implementation. The display of the x-con is
shown below.
The feature allows RM managing the new T&R-OADM functionality in 1626LM R5.0.
OPERATION
T&R-OADM (Tunable and Reconfigurable OADM) is an evolution of R-OADM because it adds the tun-
ability and the ability to interconnect in a flexible way more than 2 OTS ports (from 2 to 4 degree node).
The tunability is based on the concept of "free" Tx/Rx. Any Tributary in the R-OADM not transporting Add/
Drop traffic shall be logically connected to a "free" OCH, i.e. not connected through the overall cross-con-
nection matrix: this is a "free" Tx/Rx. Each "free" Tx/Rx is able to tune its Tx and Rx to any channel.
The above picture shows that the TRBd, receiving λ8 can be then tuned to λ9, even staying in the same
position.
To achieve this, the pass-through connectivity involving l9 inside OTS and the add/drop connectivity
involving λ8 inside OTS have to be removed; new pass-through connectivity involving λ8 and new add/
drop connectivity to the same TRBd, involving λ9, have to be set-up.
With respect to R-OADM, the T&R-OADM is based on Wavelength Manager featuring a Wavelength
Selective Switch device.
Each OTS has associated a WSS device, as represented in the following figure.
The following figure represents a Nx1 device: N input ports, 1 output port. Any combination/number of
inputs can be sent to the output. Individual blocking/attenuation is allowed
New boards are WMAN3 (WSS based), TDMX and OCNC. The TDMX is a unidirectional board playing
the tunable DEMUX role. The OCNC (Optical CoNnectivity Coupler) is a coupler needed to pass-through
the received channel on an OTS towards the other OTS.
Also for T&R-OADM the NE provides the capability to set-up flexible cross-connections through the man-
agement interface but in R5.0 the configuration in the hw is not performed automatically by the NE fol-
lowing the set-up of cross-connection at the management interface; the user has to manually perform the
required operations in the equipment domain to achieve the set-up cross-connection in the NE.
The T&R-OADM provides improved flexibility in terms of OCH connectivity, so the identified solution is
to manage in RM the routing at OCH layer across OADM, R-OADM, T&R-OADM (please refer to the new
feature "OCH trail set-up by user").
As well as for R-OADM, also for T&R-OADM, the NE provides, for each OCH CTP, the list of connectable
OCH CTP . While for OADM and R-OADM, the connectable TP are at most two, for T&R-OADM the list
is, for meaningful scenarios, more than two: this provides also a trigger to store in the RM MIB the infor-
mation that the CTP and the set-up cross-connection belongs to a T&R-OADM.
This information on cross-connection (as belonging to T&R-OADM) will be used by RM to alert the oper-
ator that the cross-connection has to be manually set-up consistently in the hw.
The following picture provides the transmission view for T&R-OADM, 3 and 4 degrees
The user may choose either the criterion of 1 rack per each line or 1 subrack per each line.
In addition, although there is no limitation, usually the same line no. is assigned to interconnected T & R
nodes.
A more detailed description of T & R-OADM equipment and cable setting can be found in the dedicated
documentation: 1626LM R.5.0 Technical Handbook and 1626LM User’s Guide.
LINE 2 (3 degrees)
to WMAN 3 line 3
to WMAN 3 line 1
r2s2b3
from NETWORK
TRBD OADC OCNC LOFA
TMDX
1100 1230
r2s2b6/8/10
r2s2b14 r1s2b27
TRBD r1s2b29 r2s2b10
OADC r2s2b2
1750
ADD1 ADD2
WMAN IN1
LOFA
from OCNC WMAN OUT OADC to NETWORK
line 3 WMAN3
0104
WMAN IN2 r1s2b25
from OCNC r1s2b14
line 1 r1s2b7
TASK
-TMDX1180 r2sr2b14
-OADC1750 r2sr2b2
N.B. (Only for LOFA). Navigate board (click twice). In the board view issue Board: Modify equipment
configuration. In the Modify equipment parameters dialog box (Contradir), enter the physical
coordinates of the other board. Click on OK to confirm.
3) In the connector configuration dialog box select one board and click on Set in Service
4) Expand (+ ) the view of the board in order to display all input/outputs of the board
TASK
2) Select cell Cable in correspondence to LOFA1110 on the left column. On the right column,
which appears as a consequence, select In 2nd stage (cell CABLE)
3) Execute the Add cable operation for all required cables. See list herebelow
27-OADC1100-out1 to 14 TMDX1180-Input
TASK
2) In the Upload Tools dialog box select Upload physical connectivity and click on Finish.
3) To verify the created physcons, with reference to below network, select, as an example, T &
R node 50-1 and click on icon Ports.
4) The port list is displayed. Navigate port r2s2b3p101-193.15, which will be the end point of the
trail being created
The scope of this procedure is to create the OCH trail for the Add/Drop case
TASK
9) Click on Finish to confirm the creation.The trail is created. The OCH trail routing display is pre-
sented.
11) The physcon structure involved shows that the DS path over 193.15 is not implemented. Select
the OCH trail and click on Client trail structure view
13) After the OCH trail implementation the Check connection flag is displayed in the routing display,
in correspondence to the crossconnection which is allocated. The missing x-con is betw r2 s2
b14 (TDMX) and r1 s2 b10 (LOFA). It is an add/drop x-con, because node 50-1 is equipped as
‘1 subrack per line’
TASK
2) DROP FUNCTION. Navigate board TMDX 1180 and issue Board: Configure TMDX1180
4) ADD FUNCTION. In the reverse direction the tuning must be executed on board WMAN3174.
Navigate board WMAN 3174 and issue Board: Configure WMAN 3x74
6) The DS path is now implemented, since the needed tuning has been made.
The x-con has been tuned manually.The scope is to clear check connection flag
2) In folder Status, attribute Check connection on NE must be SET to NORMAL. Click on Apply.
4) Select the OCH trail and click on client Trail structure view. This view is shown in the right-hand
side of the following figure
1) Create OCH trail between node 50-1 and 50-2. A passthrough connection is required on node
50-3.
4) To be noticed that the flag shown in fig. below, refers to a passthrough cross-connection
between the two racks, since the equipment is configured 1 rack per line
LINE2 LOFA
5) This pass-through x-con is created by RM, but must be tuned manually. Pass to eqpmt view
of node 50-3 .Select board WMAN3174 .
193300 IN1
9) The pass through connection in 50-3 has been created by the OCH trail implementation.
10) The same tuning operation must be executed on the WMAN board of line 3
1.27 40 Gb connection
SCOPE
Create a 40 Gb connection
TASK
7) After trail implementation the ODU3 layer is created, carrying the 40Gb connection.
Case 2 - The X-conn is not created by user on EML. Due to the fact that the X-conn is unique, RM creates
it as allocated.
Case 1) Create this X-conn via EML. Upon creation of the relevant physcon, the X-conn is uploaded as
implemented.
The DS path status depends on the statuses of the involved flexible X-conns.
SCOPE
TASK
a) From EML equipment view navigate to the transponder TRBD1191 board view
b) Navigate (click twice) to the port view. The view does not contain any connection.
c) Select the OCH block and issue Cross Connection: Create Cross Connections
e) The list of the connectable TPs is displayed (left-hand side of below figure). Only one TP can be
selected, for transponder TRBD1191. Click on OK to confirm the selection.
f) The selected TP (output) is present in the Create Cross Connections box. Click on OK to confirm
the creation.
g) The x-conn just created is drawn by a X mark in the OCH block of the port detail. You can display
the detail of the entire connection, by selecting the OCH block and issuing the menu Expand all lev-
els
h) In the following figures it is possible to see the complete chain from port 1 B & W (input of the tran-
sponder) to port 101 colored, towards the WDM network.
SCOPE
The scope of this procedure is to create physcon I/W from Ext-3 to 1626-50-3
TASK
b) From the Create physcon box select connection type=SDH-WDM interworking, enter the userlabel
(name) and click on Next button.
SCOPE
The scope of this procedure is to create OPS physcon from TRBD to OMDX
TASK
a) Launch the Create physcon. Enter name and select WDM type=OPS. Click on Next.
d) Both TPs have been selected. Click on Finish to confirm the creation.
e) The OPS physcon is created and the raw conn is created thru the OPS physcon.
TASK
a) Select node 1626-50-3 and issue: Search: All Related Items: cross connections
d) Issue cross connections details. The cross connection created via EML appears implemented.
SCOPE
TASK
a) Upon implementation of the entire chain from Ext-2 to Ext-3, i.e. on implementation of all physcons
involved in the chain, the DS path is automatically discovered. Path status is implemented, due to
the fact that flexible connections are implemented.
d) From the DS path: Routing Display you can see that, in correspondence to the flexible connection
within TRBD1191, the Flexibility level=flexible with fixed ends.
SCOPE
TASK
a) Select node 1626-50-3 and issue: Search: All Related Items: cross connections
b) Issue cross connections details. The usage of the cross connection created via EML is equal to path
Case 2) the X-conn is not created by user on EML. Due to the fact that the X-conn is unique, RM creates
it as allocated. In addition, after the complete network construction, RM uploads the entire DS path.
SCOPE
TASK
a) From EML equipment view on 1626-50-3 navigate to the transponder TRBD1191 board view
b) Navigate (click twice) to the port view. The view does not contain any connection.
c) From EML equipment view on 1626-40A navigate to the transponder TRBD1191 board view
d) Navigate (click twice) to the port view. The view does not contain any connection.
SCOPE
TASK
a) Create all physcons (with auto-implementation), as detailed in the previous procedures from 1.28.1.3
to 1.28.2.3
b) Upon implementation of the entire chain from Ext-2 to Ext-3, i.e. on implementation of all physcons
involved in the chain, the cross connection on TRBD is automatically discovered as allocated.
f) Upon implementation of the entire chain from Ext-2 to Ext-3, i.e. on implementation of all physcons
involved in the chain, the DS path is automatically discovered.
h) In the DS path routing display, the x-cons are allocated, flexible with fixed ends)
a) Select node and issue Search All Related Items: Cross Connections
b) The usage of the cross connection just created is path. Issue the cross connection detail.
e) You can see that the cross connections are created on the equipment upon path implementation
g) From the routing display you can see that the X-con flexibility level=flexible with fixed ends
b) The DS path becomes allocated and the cross connections are removed from the equipment
e) A raw connection is still present at DS layer within the client trail structure view.
1.28.5 Mixed situation: flex. X-con present on 40A-2, not present on 50-3
CONDITIONS
The X-con has not been created via EML on TRBD1191, node 1626-40A-2
The X-con has been created via EML on TRBD1191, on node 1626-50-3
SEQUENCE
a) Complete the network creation with the required steps, described in the previous procedure:
After the implementation of the network, i.e. after the implementation of the last physcon, the DS path is
automatically discovered. See following figure
b) The discovered DS path is partially implemented; this is due to the fact that Flexible connection sta-
tuses are respectively implemented on 50-3 and allocated on 40A-2
Two configurations without flexibility are described in the following. The user must create via EML the X-
con on NE, because the connection is not univocal, then RM is not able to create it.
The colored port of TRBD1191 slot b11 can be connected either to B & W port of TRBD1191 slot b11 or
to the colored port of the adjacent TRBD1191 slot b12
B&W
b11 b12
It is suggested the user on EML interface creates manually the desired X-conn
The line port (RS-TTP object) of slot 9 board ETHC can be connected either to line port (OCHrs object)
of slot 9 board ETHC or to the colored port of the adjacent TRBD1191 slot 10. See below figure
SEQUENCE
a) From the OTS physical connection structure verify if optical paths (so called client) are present.
b) Execute the deimplementation of the optical path by selecting the menu Configuration: Configuration
State Modification: Deimplement. A question box asks for confirmation. Enter YES.
c) Deallocate the optical path by issuing the command Configuration: Configuration State Modification:
Deallocate. The user can refresh manually the PhysCon structure view.
e) Remove the OTS optical physical connection. The OTS optical physical connection view remain
opened for a while.
The Trace Identifier, on the WDM NEs, can only be monitored (expected value). It can be provisioned (sent
value) only on the SDH NEs.
The Trace Identifier can be set both on the client path and on the related SDH physical connection. The
following has to be taken into account:
- It is not possible to set the Trace Identifier on the SDH physical connection if the client path is present
- If the Trace Identifier is set on the client path, the values are propagated on SDH ports, client NAPs and
on boundary WDM NEs (client CTPs)
- If a client path is created and the Trace Identifier is already set on the SDH port, the value is is propagated
on the client NAP. When the Trace Identifier management command is executed on the client path, the
values of the Trace Identifier present on the NAPs are presented to the user that can confirm or modify
them
– to fill the frequency attribute of a Coarse WDM and SDH coloured ports, the wavelength, expressed
in nm is used
– to calculate the wdmFrequency attribute (alias = position) of the RM objects (CTPs, CAPs and LCs)
related to a Coarse WDM port, the value of the wavelength, expressed in nm is used
When an OPS physical connection involving a port (client or WDM side) belongs to a 1660OADM is cre-
ated, the following steps are performed:
– starting from the assigned port, the TP chain up to the client CTP is discovered and the related
objects are created inside the RM MIB
– if the client CTP points to an other client CTP (by means the UCP/DCP pointer) already present
inside the RM MIB, the cross-connection between the two involved client CTPs is created inside the
RM MIB
The output port of this transponder (Coarse) is connected to a port of a Coarse Multiplex (in the same or
in an other NE). Then the Coarse signal is transported in the network through and terminated in a NE
bymeans the same type of transponder, as shown, as an example, in the following figure.
As the Coarse Multiplexes are not visible through the Optics-IM interface, it is not possible to describe in
RM the Coarse links. Due to this limitation, the user can only define a Coarse OPS physical connection
between the Coarse ports of the two transponders.
2.1 Introduction
This chapter covers the following topics:
– Overview
– ASON create
– ASON Client
– ASON path
– ASON Maintenance
– CLI connect
– Coloring
2.2.1 General
The feature allows the management of a distributed Control Plane based on GMPLS (Generalized Multi-
Protocol Label Switching)
ASON network NE's, involved in the network managed by RM are shared between RM and GMRE ( Dis-
tributed Restoration Manager ). Both systems (NMS) manage resources belonging to shared NEs. In par-
ticular, ports belonging to the physical links involved in the Legacy Network are the shared resources.
These physical links represent in RM the links of inter-working between the two managers for the paths
routed in ASON domain. The port at the end of the inter-working link and belonging to the shared NE rep-
resents the "shared" port.
The TPs on a shared port can either be completely managed by RM or managed by both RM and GMRE,
according to the routing of the path involving the TP.
Physical links and the NE's of the ASON network are represented in the RM as physical connections and
nodes.
RM provides to GMRE the description of the network belonging to the ASON domain and the links at the
boundary of that domain (inter-working links). These links connect shared ports.
ASON domain topology is described in each GMRE and RM user launches the automatic discovery of
the ASON domain physical connectivity by means of J0 string.
RM, for maintenance purposes, manages the physical and the Multiplex Section layers (linear MSP
included)
On the inter-working links, RM can apply the payload structure; in the ASON domain, the payload structure
is defined by the GMRE as a consequence of a SPC (Soft Permanent Connection) set up by RM.
RM user has anyway to perform the payload structure also on the internal links to allow path
allocation activities but the command is not propagated to GMRE.
On path set-up phase, RM provides to GMRE the set-up of the sub-network connection (SPC) contained
in the ASON domain, between the two TPs of the shared ports. GMRE will be in charge of restoring, upon
failures, that sub-network connection.
While the TPs ends of the above sub-network connection are chosen by RM, the other TPs involved in
the cross-connection inside the shared NE, are "moved" by GMRE according to its restoration purposes.
I.e., the set-up of the single cross-connections inside the NEs belonging to the ASON domain (included
the shared NEs) will be done by GMRE's. For all the other operations at path layer (POM, TCT, PM, path
trace): RM is the master for the TPs on the shared ports, while GMRE is the master for the TPs of the
ASON domain.
As a consequence: ports dedicated to the inter-working between RM and GMRE are marked as "shared" .
Each manager is able to distinguish between ports on which all the normal operations are allowed
because completely "assigned" to it and ports on which only specific operations can be performed
because "shared"
ASON domain is managed by RM as ASON NPA. In ASON NPA definition, the user must specify the role
of the physical connection as "internal" or "interworking": the involved port on the NE belonging to the
ASON NPA is marked as shared inside RM
In case the ASON network has already been set-up by the GMRE user (through CLI), the RM user, to build
the network, has to perform the following steps:
– provision the Trace Identifier on the SDH ports assigned to GMRE
– set the "download disabled" mode on the involved NEs
– For each node of the domain, performs the "Configuration/Upload connectivity" command. The com-
mand (based on J0) automatically creates in the RM DB the physical connections involving the node
selected by the user
– implement the uploaded physical connections
R R
por por
RM physcon
R R
por R
R por
interworking interworking
physcon physcon
J J
shared
por shared
por
J J
shared shared
1664SX por interworking por 1674LG
physcon
G$ G$
G$ G$
por por
por por
internal internal
physcon physcon
G$ G$
G$ G$
por por
internal internal
physcon physcon
G$ G$ G$ G$
por por por por
When the RM operator sets-up a path crossing (or terminating in) the ASON domain, the sub-network con-
nection at the ASON NPA level will be created and also the related cross-connection inside the Nodes.
These cross-connection will be marked in such a way that RM will not directly forward the cross-connec-
tion implementation to the NE but they will provided to the GMRE with the provisioning of the SPC nominal
route (the provisioning of the single cross-connections to the NE will be in charge of GMRE)
The controlPlaneDomain class represents the GMRE, i.e. the Control Plane instance contained in theNet-
work Element. Some important attributes are:
emsFactoryAddress: it indicates the GMRE Factory IOR for addressing the GMRE/Control Plane using
NMI Corba (not visible on the User Interface)
assignSt: it indicates if the Control Plane has been taken in charge by RM or not
userLabel
sncActiveSt: it specifies if the Sub-Network Connection has been implemented on the Nes by the GMRE
(not visible on the User Interface).
controlPlaneDomId: it is the Identifier of the Control Plane Domain (not visible on the User Interface)
The port sharing with GMRE is performed through the ACD set at Q3 interface. The ACD of the ports
shared between RM and GMRE is set by RM to "J$".
In the following only the specificity of the Q3 consistency for the involved objects are reported.
the consistency of the disconnectOnNE attribute of the client TPs is performed: in case a cross-connection
is discovered on the NE while no cross-connection is present on RM, the cross-connection on the NE is
removed only if the other port involved by the cross-connection is either assigned to RM or also "shared".
The consistency of the au4Structure attribute of the msCtpCap is not performed (this because the master
of the payload structure is the GMRE)
For cross-connections:
The consistency is not applied for the cross-connections with configuration state "implemented on CP"
where CP stands for Control Plane.
The configuration state attribute of the cross-connections belonging to an SPC is set "allocated" when the
SPC configuration state is set "allocated" and moved to "implemented on CP" when the SPC configuration
state is set "implemented" (i.e. during path implementation activity)
SEQUENCE
a) From the EML list select the EML which contains the NE belonging to GMRE control plane and issue
Actions: Synchronize: Synchronize EML
GMRE NEs are listed with attribute Control Plane different from 'Not Present'. The possible values
for this attribute are : 'Reachable', 'Not Reachable', ....
The symbol identifying a GMRE NE is also reported on the browser display as shown in the figure
below.
NE with GMRE control Planes are discovered . The control plane is not managed yet. The Control
plane status is Not Managed
c) From browser point to the ASON subnetwork and select Configuration: J0 definition. This configu-
ration is executed automatically by the NEs belonging to the subnetwork.
d) From browser, pointing to the subnetwork issue Subnetwork: Configuration: Upload Connectivity.
The physical connections are uploaded from GMREs and represented on RM database and interface.
e) Create the NPA of type=ASON. Figures which follow shows NPA Create step 2, which requires the
specification of the internal and interworking physical connections.
g) From NPA list point to Ason NPA and issue Configuration: Implement. The communication RM-
GMRE is started and, after a few seconds the Control Plane of each NE becomes reachable. On
GMRE systems the objects required for the routing and restoration functions are created.
– the type,
– the involved physical connections and, if applicable, their associated role (e.g. Working or Protection
for 4f-MS-SPRing, and Linear MS-P).
A SDH physical connection can belong only to one NPA with the following exceptions:
SEQUENCE
It is not considered for the spare that uses the same ring of the main.
oneToOne: N.A.
withSameRisk (standard ASON bundling rule): physcons with same linkType, linkProtection-
Type, cost and srgList are grouped in the same TELink.
In case of particular unbalanced configurations, if the NPA Usage Cost is not enough to avoid the ring
changing, the user needs to properly set the costs of physical connections
NPA highlight shows on the map the nodes connected by physical connections involved in the NPA.
SCOPE
A map of a topology containing at least a Node involved in a NPA (different from linear MS-P) visualizes
a flag with the type and the name of the NPA :
The flag placement is in charge of the user (e.g. close to the right Nodes)
From the flag it is possible to retrieve the NPA and its view.
NPAs of type ring (2F,4F,SNCP), if implemented, can be modified via join/split physical connection pro-
cedure.
A modify NPA affecting the ring map (2F, 4F), can be made only for DEFINED NPA.
The NPA of type ASON, MSP, FAST RESTORATION can be modified, when implemented, by adding/
removing physical connections. Detailed examples can be found in chapter RM-NP FTWORKING
ASON NPA can be modified adding and removing internal or interworking physical links
SCOPE
SEQUENCE
a) From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.
b) Select Create and click on Next button. The Step 2 dialog box is displayed.
c) Click on SRG type list and select from the list the desired type. Click on Apply to confirm.
N.B. srg probability change can be accomplished via Show/Set attrbute dialog box. see following fig-
ure
SCOPE
SEQUENCE
a) From the Domain icon select Shared Risk Group: Create/Remove. The SRG Create/Remove wizard
is presented.
b) Select Remove and click on Next button. The Step 2 dialog box is displayed.
c) Click on SRG list and select from the list the SRG to remove. Click on Apply to confirm.
SCOPE
SEQUENCE
a) From the Domain icon select Shared Risk Group: Correlate/Modify the set of SRGs. The Correlate/
Modify wizard is presented.
b) Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.
Figure 503. SRG (Shared Risk Group) Management: Correlate/Modify the set of SRGs
d) Click on SRG list button and from the list select the SRG to correlate. Click on Apply button and the
click on Finish on the main window.
SCOPE
The scope of this procedure is to launch SRG calculation for WDM server
CONDITIONS
The SDH TE-Link inheritated the SRG values assigned to the WDM physical connections which support
the SDH physical connection. This command resets the actual (previously inherited) value and
relaunches the calculation of the SDH physical connection SRG, based upon the actual WDM SRG struc-
ture.
SEQUENCE
a) From the Domain icon select Shared Risk Group: SDH SRGs calculation . The SDH SRGs calcu-
lation wizard is presented.
b) Click on Physical Connection list button and select from the list the Physical Connection to correlate.
Click on Apply to confirm.
Figure 506. Shared Risk Group: SDH SRGs calculation: Physcon selectrion
d) The step 2 of the dialog box opens. Click on SRG list. The SRG list opens. Select the SRG and click
on Apply button. Click on Next button.
Figure 508. Shared Risk Group: SDH SRGs calculation: launching the calculation
The Physical Connection: Administrative State menu is constituted by the following items:
– Set Unlock. This command forces in service the Physical Connection which was previously
Locked. The SNCs whose nominal path was crossing this Physical Connection and whose current
path was crossing a different route, revert to the nominal route.
– Set Shutting down. This command rquests to GMRE the out of service the Physical Connection
with a Make-before-break ( soft rerouting ), i.e. GMRE will define a sequence of operations by
which the new route is made before the shutting down route is turned down.
– Set Lock. This command forces out of service the Physical Connection
– Check. This command asks GMRE the Physical Connection status (typically after a Set Shutting
down operation.
The above described commands can be launched also via the Maintenance wizard. See below figures.
2.5.2.1 Introduction
A Traffic Engineer (TE) link is a bundle of transport entities equivalent from the routing point of view. Exam-
ples of TE link are:
A TE-Link has associated a cost and a list of Shared Risk Groups (SRG's).
The definition of the TE-Links inside RM applies only to ASON network. When the ASON NPA is built, the
related TE-Links are automatically created in RM and in the involved GMRE's.
TE-Links related to an ASON NPA are automatically created as a consequence of NPA implementation.
TE-Links are composed according to the value of the bundlingRule attribute of the NPA. In particular:
oneToOne: for each physical connection a different teLink is created. The linkMetric and the srgList
attributes of the created teLink object are set with the corresponding values of the physical connection
withSameRisk: the physical connection with the same linkType, linkProtectionType, cost and srgList are
grouped in the same teLink object. These attributes are set to the corresponding values of the physical
connection
The TE-Link can also be created as a consequence of the modification of the composition of an existing
TELink.
SCOPE
SEQUENCE
a) From NPA view click twice on TE-Link icon: the TE-Link list is displayed.
b) Select the TE-Link and issue Actions:Modification: Update TE-Link. The relevant dialog box is dis-
played.
SCOPE
To update the TE-Link: moving one/more physical connection/s to a new TE-Link, i.e. create a new TE-
Link
SEQUENCE
a) From NPA view click twice on TE-Link icon: the TE-Link list is displayed.
c) Select the physical connection and click on MOVE button. The physcon is displayed in the destina-
tion list.
d) You can also change SRG, by cliccking on SRG list button, selecting the SRG and confirming with
Apply button. See below figure.
SEQUENCE
a) From NPA view click twice on TE-Link icon: the TE-Link list is displayed.
b) Select the TE-Link and issue Actions:Modification: Move Physical connections. The relevant dialog
box is displayed. See below figure.
c) Click on DESTINATION button. The list of TE-Links having same origin and destination of the source
TE-Link is presented.
d) Select the TE-Link where to move the Physcon and click on Apply button. The icon of the selected
TE-Link is now present in the dialog bo under subarea DESTINATION ( right-hand side of the box)
– site name
Friendly name and IP address are used by the system to calculate the user label of the ASON client device
The user label of the ASON client device cannot be modified by the user.
The ASON client device is created with neType attribute = asonClient and imType attribute= virtual.
TNA address
These information are also used by the system to calculate the user label of the UNI (client) port of the
ASON client device. The user label of the UNI (client) port of the ASON client device cannot be modified
by the user. The UNI (client) port is created with the linkType attribute set to uni-n.
The physical connection is created and the UNI (network) port is assigned to RM. This port will be
assigned to the GMRE when the NPA to which the physical connection belongs will be implemented.
RM provides the information to create the connection between Ingress and Egress GMREs.
In general a transport entity belonging to the ASON domain is called SNC: SubNetwork Connection. SNC
types are:
– Switched Connection not created by RM, but by the clients (e.g. routers) of the GMPLS, between
two UNI ports
– spcOnCtrlPlane: it indicates that the SNC (fully initiated and terminated into the ASON domain) is
present on the ASON DB but not in the RM DB; i.e. the DBs are not aligned.
SEQUENCE
2) A SNC is created
1) RM, via Q3 interface, implements the cross connections belonging only to the Legacy domain
2) RM provides to the Ingress GMRE the command to implement the SNC and the routing of the
SNC
3) Each GMRE takes care to create the cross connection of each managed NE belonging to the
SNC routing
4) GMRE Ingress determines also a backup SNC: in case of failure automatically the Ingress
GMRE switches on the backup SNC taking care of the all operations;
The feature permits to create a path crossing a 2F MS-SPRing where it exists a NE (o more) belongs both
to a 2F MS-SPRing and to the ASON domain.
The calculation of the squelching table of the NE(s) belonging both to a 2F MS-SPRing and to the ASON-
domain is still in charge of RM.
RM calculates the squelching table of the NE containing the aEnd TP (Legacy domain) and of the Ingress
NE (ASON domain).
Ì With Interwork ASON-2F-MS-SPRing, path routing display does not show the true way
– defaultRerouting
– defaultPriority
If the path/trail doesnt cross the ASON domain these attributes are not managed.
If the path/trail crosses the ASON domain a SNC is created and these attribute are managed. SNC
attributes: rerouting and priority mirror the related attributes of the path/trail which belong to. Setting the
protType attribute of the path/trail entities (in definition phase) the homonymous attribute of the SNC
(belonging to the selected transport entity) get a value, but in this case it isnt a pure mirroring: the value
on the SNC depends on the result of the routing algorithm.
After the first highlight the operator can ask to view only a particular path route, i.e. main, spare or service.
A filter, (applied over the resource type of the link connection and the connection in topology) put on the
option menu, allows the operator to choose among one of the following values:
– Main
– Spare
– Service
– AllRes (defaul value)
The operator can also use another filter put ever on the option menu; this filter selects the route type of
the SNC.
This route filter (applied over two local attributes routeRole and statusOnConnec) allows the operator
tochoose among one of the following values:
Network, NEs and links related to the selected path (in the Legacy domain) are shown with
Some resources may contain resources of two different types; e.g. the two nodes containing the two naps
of a protected path. In this case the color will be the mix of the colors related to the resources type.
If a resource contains resources of three different types (e.g. a network containing a path protected with
a SNCP) the color will be white.
NAPs are shown with flags. The highlight of the SNC shows its resources with a color depending on the
route and on the resourceType.
C+N [current=nominal] Main Each route is shown with the related colors
C+N [current=nominal] Spare Each route is shown with the related colors
In case of not protected path colors are those related to the resorceType=Main.
The feature permits to retrieve some additional SPC details getting them by the GMRE UI.
The zoom-in on GRME UI is driven, i.e. the user cannot perform any command on the GMRE UI. Select-
ing, by the RM browser, a SPC and choosing the Show Details on GMRE the following operations are per-
formed:
– telnet to the GMRE host (the GMRE is related to the Ingress node);
– get/inventory of the additional details (the action is hidden to the user);
– GMRE UI action is: show lsp lsp_index lsp_index, where lsp_index is the ID of the selected SPC.
– close connection with GMRE UI.
The inventory starting from a physical connection provides the active path/trail crossing it. The new feature
provides others remote attributes:
– SNCuserLabel: is the user label of the SPC contained into the path crossing the selected physConn;
– ResourceType: indicates the resourceType of the path in case its protected (Main, Spare, Service);
– RouteRole: specifies if the SPC is Nominal or back-up
According to the possible scenarios retrieved on GMRE NEs the following combination are foreseen:
Active Nominal
NotActive Nominal
Active Back-up
Indeterminated Nominal
If the physical connection is not part of an ASON NPA, the role is always nominal.
– APortName/ZPortName: are the end points of the path/trail;
– PayloadPosition.
N.B. in case of SNC protected by SNCP, the output of the inventory with filter=active is both the main
andspare legs. ASON domain does not provide the active/noActive information in case of
SNCP protection.
EXAMPLE
a) From the Path list ( see Figure 519.herebelow), select the path and click on highlight button. The
highlight map view is displayed. See Figure 520.on page 371
b) Selecting the option route it is possible to display current, nominal and backup route.
2.7.3.1 Restoration
Priority P is used by GMRE network during restoration. I.e., in case of fault of SNC-A, crossed by path-
A of priority P=1, path-A could be rerouted on SNC2, actually crossed by path-B, having priority P=4, so
interrupting path-B.
2.7.3.2 Implementation
EXAMPLE 1
SNC-1 P= 1
SP= 5
FAULT
P=4
SNC-2
SP = 5
ASON DOMAIN
SEQUENCE
a) Execute the implementation of path 2 ( P=4, SP= 5 ), crossing SNC-2. The path 2 goes implemented.
If the standard priority mechanism were used, path 1, having priority P= 1 would override path 2 (
P=4 ), making use of SNC-2.
BUT
the system takes into account the SETUP PRIORITY: in phase of implementation the system makes
a comparison between SP of the path being implemented ( path 1 in this example ) and the standard
priority of the path being overriden ( path 2 in this example ). In our example SP of path 1 = 5, P of
path 2 = 4.
EXAMPLE 2
SNC-1 P= 1
SP= 1
FAULT
P=4
SNC-2
SP = 5
ASON DOMAIN
SEQUENCE
a) Execute the implementation of path 2 ( P=4, SP= 5 ), crossing SNC-2. The path 2 goes implemented.
If the standard priority mechanism were used, path 1, having priority P= 4 would not override path
2 ( P=4 ), making use of SNC-2.
BUT
the system takes into account the SETUP PRIORITY: in phase of implementation the system makes
a comparison between SP of the path being implemented ( path 1 in this example ) and the standard
priority of the path being overriden ( path 2 in this example ). In our example SP of path 1 = 1, P of
path 2 = 4.
The setup priority of path 1 = 1 is superior to the priority of path 2 = 4 ( highest priority is 1, lowest
priority is 5 ), then path 1 will override (or preempt) path 2, thus crossing SNC-2.
TASK
b) From the Control Plane list issue Auto-restoration: Deactivate. From this point on all SNCs starting
from that node will not be automatically restored, i.e. the user can execute a manual reroute by use
of the Maintenance wizard or via Add Protection command on the involved SNC.
The scope of this procedure is to activate the auto-restoration on a single NE on a priority base
TASK
a) From the map or from the involved list, select the NE/node and issue Search: Related Items: Control
Plane
b) From the Control Plane list issue Auto-restoration: activate. A priority selection dialog box is pre-
sented, allowing to select the priority.
The priority refers to the implementation of the spare route in case of fault.
Setting priority=5
If you select 5, the auto-restoration will be applied only to SNCs belonging to paths of priority=5.
SNCs belonging to paths of priority 1 to 4 should be manually restored.
Setting priority=3
If you select 3, the auto-restoration will be applied only to SNCs belonging to paths of priority=3, 4
and 5.
SNCs belonging to paths of priority 1 and 2 should be manually restored.
Setting priority=1
The feature allows to visualize to the user the protocol version the GMRE can be upgraded to and the
alarm raised in case of problem related to the protocol itself.
SEQUENCE
The scope of this procedure is to create a trail within/on the borders of the ASON network.
SEQUENCE
b) In the create step 1 dialog box enter the name (optionally) and the detailed parameters. See following
figures. Click on Next button.
c) Select the end points and click on Finish. See following figure
d) To display the trail, point to a node and issue Search: Relted Items: Starting/Ending HO trails
g) In this case the trail has been created without protection. You can add the protection. Figure
531.shows the view of the protected trail.
SEQUENCE
a) The Add/Remove Protection Tool can be launched by selecting the path and clicking on the relevant
icon. See following figure.
d) Click on A-CONN button. The path routing display ( nominal route ) is presented. Select the A-CON-
Nection in topology which will be the starting point of the nominal route change. Click on Select button
to confirm. The selected A-CONNection in topology icon is then present in in the main box ( left-hand
side of below figure)
e) Click on Z-CONN button. The path routing display ( nominal route ) is presented. Select the Z-CON-
Nection in topology which will be the terminating point of the nominal route change. Click on Select
button to confirm. The selected Z-CONNection in topology icon is then present in in the main box
(left-hand side of below figure)
CONDITIONS
SEQUENCE
a) From the routing display of the path select an SNC and issue Modify: Attributes pop-up menu.
b) You can modify the userLabel and the other rerouting attributes of the selected SNC
The switched connection can be removed by RM. Start from the path list, opened from the ASON view.
Routing display of a switched connection: the part of the route internal to ASON network is not known by
RM.
• From the map clicking twice on the physical connection, the Physical Connection list is dis-
played. See above Figure 546.
• From Physical Connection list click on Physical Connection structure. See figure which follows
a) The SNC Maintenance: Constraint Management command is launched from the path routing display,
pointing to the SNC icon, from the path routing display. See below figure.
c) From the snc list you can select the SNC to disjoin, as an example, in following figure, SAM1-SAM22
disjoined from SAM1-SAM21
d) It is needed also to create the constraint SAM1-SAM21 disjoined from SAM1-SAM22. See following
figure.
Figure 553. SNC Constraint management wizard with disjoin policy on TE-Link.
– case 1: the user has created a path protected "in Rings. In this case has to be taken into account
that in the ASON domain the SNCP protection is not created
– case 2: the user has created a path protected SNCP or D&C SNCP but there are not the conditions
for a end to end protection
– case 3: the user has created a path protected SNCP or D&C SNCP providing specific constraints
In particular, scenarios 1, 2 and 3 can be obtained with cases 1, 2 and 3, while scenarios 4, 5 and 6 can
be obtained with cases 2 and 3.
During the allocation phase of a path protected D&C SNCP if no D&C connections, except for the D&C
single node inside the ASON domain, are created, the protection type of the path is changed to SNCP.
Above scenarios can also be obtained modifying the path itself by means of the add/remove protection
on a part of the path.
N.B. The following operations take into account the following GMRE restriction: it is not possible
modify an SNC changing its end points.
N.B. In the following, what is said for a path is valid for the trail too.
Figure which follows represents, as an example, the Path routing view of a path described in Senario 4
of Figure 557. at page 393.
Clicking twice on the internal physcon link, the relevant Physical connection list is presented. See below
figure
The scope of this procedure is to launch a a soft rerouting to the nominal of the routes which are making
use of the selected SNCs
SEQUENCE
c) Click on Reload button. The list of SNC (subnetwork connections), whose path cannot revert to the
nominal route is displayed in in the bottom part of the window.
d) Select one or more connection/s and click on Apply button. As a result the ASON network executes,
if possible, a soft rerouting to the nominal of the routes which are making use of the selected SNCs
and the user is informed accordingly.
2.8.1 DESCRIPTION
The feature allows the management of a broadcast path within ASON domain. This represents an
improvement of an already supported feature. The main changes in the management are:
– use of the same resources for common route of different legs of the same path (broadcast connec-
tions within ASON domain are supported)
2.8.2 OPERATION
Both protected and not protected configurations are supported. The following definitions apply:
– broadcast path: it is an uni-directional path with one or two source points and more than one des-
tination points. The path can cross or not an ASON domain
– leg: it is a route that connects a source to a single destination (protected or not). A leg can cross or
not an ASON domain
Some possible scenarios are reported in the following figures. The following conventions apply:
SCENARIO 0
broadcast path (not protected) with five legs in the ASON domain and three distinct SNCs
Figure 565. Broadcast path (not protected) five legs in the ASON domain&three distinct SNCs
SCENARIO 1
broadcast path (not protected) with six legs in the ASON domain
Figure 566. broadcast path (not protected) with six legs in the ASON domain
Note: The path has six legs. SNC1 is from node 1 to node 4 (leg 1); SNC2 from node 1 to node 6 (leg
2); SNC3 from node 1 to node 3 (leg 3/4); SNC4 from node 1 to node 5 (leg 5); SNC5 from node 6 to
node 5 (leg 6).
Note: the number of SNC inside the ASON domain, concerning one ingress point (CTP), is equal to the
number of egressing nodes (3 SNCs for signal A, 1 SNC for signal B and 1 SNC for signal C).
Note: two, or more, end points on the same egressing node, concerning one ingress point (CTP), is rep-
resented as only one SNC (one SNC for signal A egressing node 3 and two SNCs for signal B and C
egressing node 5).
broadcast path (not protected) with two legs in the ASON domain sharing a link connection in two direc-
tions
Figure 567. (NOT ALLOWED) Broadcast path-two legs in ASON dom. sharing a LC in two dir
Note: The path has two legs. SNC1 is from node 1 to node 5 (leg 2). SNC2 is from node 1 to node 4 (leg 1).
Note: Due to a GMRE restriction, a resource (link connection) inside the ASON domain cannot be, at the
same time, used in two directions. This restriction is true for both protected and not protected path (see
scenario 2).
broadcast path (not protected) with two legs in the ASON domain
Figure 568. broadcast path (not protected) with two legs in the ASON domain
Note: The path has two legs. SNC1 is from node 1 to node 4 (leg 1); SNC2 from node 1 to node 4 (leg 2).
Note: If two legs enter on the same point (CTP) and are ended on the same node, their routes have to
be the same. This restriction is true for both protected and not protected path.
Note: The path has two (protected) legs. SNC1 from node 1 to node 4 (leg 1); SNC2 from node 1 to node
5 (leg 2).
Note: Resources are shared between spare of leg 1 and spare of leg 2
SCENARIO 5
Note: The path has two (one protected and the other no) legs. SNC1 is from node 1 to node 4 (leg 1); SNC2
from node 1 to node 5 (leg 2).
Note: Resources are shared between two legs with different resource type (spare of leg 1 and leg 2)
Note: The path has two legs. SNC1 from node 1 to node 4 (leg 1 main); SNC2 from node 1 to node 7 (leg
2 main); SNC3 from node 2 to node 6 (leg 1 spare); SNC4 from node 2 to node 4 (leg 2 spare).
Note: If main and spare of a leg enter in ASON domain in two different CTPs, they have to exit the ASON
domain in two different CTPs.
Figure 572. (not allowed) protection starting from ASON ingressing CTP
Note: The path has two legs. SNC1 from node 1 to node 4 (leg 1 main); SNC2 from node 1 to node 7 (leg
2 main); SNC3 from node 1 to node 6 (leg 1 spare); SNC4 from node 1 to node 5 (leg 2 spare).
Note: If main and spare of a leg enter in ASON domain in one CTP, they have to exit the ASON domain
in only one CTP.
N.B. The SNCP ring closure is not supported either in ingress and in egress direction
– remove leg
– add protection
This alarm, "Failed Z Ends", is managed and correlated to the path/trail (see MAINTENANCE section for
more detail).
In addition, an attribute has been added to SNC to report the status of the SNC, related to the raised alarm
(allowed value is normal / failed)
The scenario of this feature (MAXIS-Malaysia) includes rings of 1670SM connected to 1678MCC of an
ASON network, i.e. the link between 2 MCCs crosses 1670SM NEs belonging to the ring. The band
between MCCs is reserved for ASON network. Sometimes part of the band is assigned to the ring.
a) Select the termination nodes (from the node list or from the map). In the create connection wizard
select connection type=SDH Compound Link, STM type and enter the connection name. Click on
Next button.
c) Create another physical connection (can be at different rate), with connection type=SDH Com-
pound Link and same allocation cost. See below figure
h) The Add Physical Connection wizard is presented. Select from the list the other physcon. Click on
Finish.
b) Point at a single link connection of the physcon and issue Compound link management: Not available
for ASON
d) It is possible, via the command Compound link management: available for ASON to revert to the ini-
tial conditions.
SEQUENCE
a) From the ASON Physical Connection pop-up menu issue Ason: Maintenance. The ASON Mainte-
nance wizard is displayed. See Figure 589.
b) In the ASON Maintenance wizard select the ASON administative state=shutting down. From this
point on, the newly created traffic will not be routed on this Physical Connection.
c) Click on Reload button. See below figure. The list of SNC (subnetwork connections) present on this
phisical connection, is displayed in in the bottom part of the window.
d) Select one or more connection/s and click on Apply button. As a result the ASON network executes,
if possible a soft rerouting of the routes which are making use of the selected SNCs and when the
list is empty, the ASON administrative state becomes LOCKED.
e) Click on CHECK button. An audit on the ASON network in performed and the user is informed
accordingly.
f) After the execution of the manual maintenance, select ASON administative state=unlocked.
The scope is to execute a connection to the 1678MCC local terminal (CLI) and launch a show operation
on ASON connections.
SEQUENCE
a) From the map click on the Control Plane icon associated to the involved node, as per Figure 591.her-
ebelow. The CLI terminal is displayed. See Figure 592.
b) On the CLI terminal it is possible to launch the 1st level help simply by typing question mark ?. The
1st level command options are displayed: ( see Figure 593.)
– Script. Allows the execution of a number of CLI commands as defined in the script file
– Exit
– Quit
The complete description of CLI commands/options can be found in 1678MCC CLI documentation.
c) Enter Show, followed by the question mark, to launch the 2nd level help on the show command. The
2st level command options are displayed: ( see Figure 594.)
– Interface. Returns a list of all or specific type interfaces available at the GMRE withe the high level
attributes.
– Label. Label
– NotificationHistory. Displays the last n event notifications as issued by GMRE ordered in chrono-
logical order from newest to oldest.
e) Enter Show LSP followed by the question mark, to launch the 3rdnd level help on the show com-
mand. The 2st level command options are displayed: ( see Figure 596.herebelow )
– TNA. Returns a list of all LSPs for which the TNA address is registered in Generalized UNI object.
-TE Link
-path/trail
-SNC
This class mark can be applied to subdivide the network into n disjointed networks.
To do this, the system allows to define separately the color of the resources (TE-Links) and the color of
the transport (e.g. the path).
In this manner, the involved path can be allocated only to the consistent TE-Link.
b) The Color profile list is displayed. The list contains the following columns:
• Color Profile ID
• Userlabel
• Colors. The value is written as decimal number. Anyway it is to be considered the binary nota-
tion.
• Comment
SEQUENCE
. /usr/Systems/1354RM_<inst_id>/.snmlrc
/snml<inst_id>/rmtools/bin $ coloring.pl
c) In the Color profile creator, as an example, click on bit 4. In the first row (Color bits), the bit no.4 is
set to 1and the second row (Colors), now contains the corresponding decimal value, 16 in this case.
d) Create, as an example, a second color profile, named Purple and Blue. Click on bit no. 1 (decimal
value=2) and bit no. 4 (decimal value=16).
e) Click on tool button Refresh in the Color Profile list. The list now contains the two profiles which have
been just created.
a) From the ASON NPA select the list of the TE Links. See below figure. To each TE Link the attribute
Color Profile name is associated.
b) From the ASON NPA select the list of the Paths. See below figure. To each path the attributes
Include/Exclude any colors are associated.
d) With reference to the above Reference network, select the TE Link from node E3 to node E4 and
issue Modifications: Update TE Link.
e) In the Update TE Link wizard the Color Profile is No Color like in the TE Link list.
f) Click on Selectable color profiles. From the list select blue (in this example).
g) The Color profile blue is now present in the selection box. Click on Finish to confirm.
h) From the TE Link link list you may see that TE Link E3/E4 has color profile name=blue.
SEQUENCE
a) From the path list select the involved path test coloring and click on button Show/Set Attributes (the
lens).
b) In the Show/Set Attributes box select folder Routing. Select operation Set for attributes Exclude Any
Color Name and Include Any Color Name. For these attributes enter respectively NoColor and
Blue. Cick on Apply to confirm.
d) The reason is that we entered Include Any Color Name=Blue , with the capital letter, instead of
the small, as written in the Color Profile list ( see below figure ).
Issue again the relevant Path Show/Set Attributes entering the correct values:
f) Issue path highlight on the map. Path test coloring is crossing the blue resource (only).
An other way to change the color of the TE Link is the use of menu Move Physical Connection
SEQUENCE
c) The Move Physical Connection allows to move a physcon towards an existing TE Link or to a new
TE Link. The selection button is present in the upper left-hand region of the window.
1) If you select move to an existing TE Link, you will select the destination TE Link within the
involved list. In this case SRG and color profile of the destination TE Link will be assigned to
the physcon being moved.
2) If you select move to a new TE Link, you will select the destination TE Link within the involved
list. In this case the user will select the SRG and the color profile.
As above mentioned, the parameters needed to implement the Coloring feature, are:
The matching rule is the one that, if met, allows to execute the allocation of the ‘colored’ path to the ‘col-
ored’ resource.
CONDITIONS
1) (TE Link color) AND (Path Exclude Any Color) = 0 where AND is a logic AND bit X bit
2) 2nd condition
b) ( Path Include Any Color ) AND (TE Link color) DIFFERENT from 0 where: AND is an
AND bit X bit
EXAMPLE 1
path include any color name = NoColor path include any color ID = 1 color= 000000...
path exclude any color name = AllColors path exclude any color ID = 2 color= 11111111...(
you see color =268435455 which is all ones on 28 bits). Used bits are 28 because of hw limitation, instead
of 32.
TE LINK Color Profile name = NoColor TE LINK Color Profile ID = 1 color = 0000000...
CONDITIONS : IF
CONDITIONS
1) (TE Link color) AND (Path Exclude Any Color) = 0 where AND is a logic AND bit X bit
2) 2nd condition
OR as an alternative:
b) ( Path Include Any Color ) AND (TE Link color) DIFFERENT from 0 where: AND is an
AND bit X bit
RESULT : THEN
EXAMPLE 2
path include any color name = blue path include any color ID = 10
path exclude any color name = No Color TE LINK Color Profile ID = 1 color=00000000...
TE LINK Color Profile name = blue TE LINK Color Profile ID = 102 color= ...00000010
color= 2 in decimal notation)
CONDITIONS : IF
1) (TE Link color) AND (Path Exclude Any Color) = 0 where AND is a logic AND bit X bit
2) 2nd condition
OR as an alternative:
b) ( Path Include Any Color ) AND (TE Link color) DIFFERENT from 0 where: AND is an
AND bit X bit
RESULT : THEN
This command applies only to Physical Connections with link type = i-nni. It is used to modify the Wait
Time to Restore. The feature allows GMRE to wait a restore time before PTP (Port Termination Point)
becomes operational again after alarm clear.
SEQUENCE
a) From the Physcon list select the relevant physcon and issue the command Change WTR
b) A selection box opens, which allow to select 0 - 1m... nm,...nhours, ... up to 48 hours.
The feature allows GMRE soft-reroute in case of SD alarm at MS layer, through the provisioning of SD
enabling/disabling on a ptp through setTPData.
To activate the Restoration on signal degrade select the relevant Physcon and issue Ason: Restoration
on SD: Enable.
In case of external SNCP two drop TPs exist. Both drop TPs can be used to address the SNC.
RM implementation
We manage only internal switch. In case both internal and external swithes are present together (e.g. PRC
+ ring closure), commands on internal switches only are provided.
- connection in topology: the user selects the head or tail bridge & switch and this command is applied
only to that connection
- transport object (path or trail): the user selects the transport object and this command is applied to all
the bridge & switch connections, both the ones internal to ASON and outside it
- force main
- force spare
- manual main
- manual spare
- release
3.1 Introduction
This chapter deals about RM-NP interworking with Flow Through feature.
This chapter lists only macro steps of the procedures. For detailed descriptions refer to 1354RM (this
handbook) and 1354NP Operator's Handbook
- TOPOLOGY MANAGEMENT
- PATH MANAGEMENT
- Introduction to Navigation
This is due to the fact that the migration procedure from NP stand alone allows to describe on RM the same
network configuration already present on NP.
This procedure implies the automatic creation on RM of the relevant NPA type Fast Restoration.
In addition, the migration procedure includes a dedicated procedure to insert the flow-through feature,
both on RM side and NP side.
After the migration, RM becomes the manager of NP network, i.e. the NPOS operator, as far it is con-
cerned path provisioning, will be able to execute only supervision tasks. Anyway it is to be noted that topo-
logical changes subsequent to the migration must be executed separately on both systems RM and NP.
In case of add/remove boards/ports, the relevant hardware provisioning procedures must be previously
executed on 1353NM accordingly.
N.B. Restriction: Broadcast paths cannot be set up within NP domain. A possible solution is to set
up the bridges outside the NP domain.
N.B. To enable the Flow Through operation in the System Configuration the user must enable the
subsystem NP-RMPA. The detailed description can be found in the NP Installation Guide. An
example is given in the following figure
Figure which follows shows the RM Process Monitoring view with Proxy NP agent active.
Configuring the RM-Rmnpa Subsystem (RM-NPProxyAgent), insert the IP addresses of the NP Servers
(without 0 after each . ), for example a correct address is 151.98.46.171; a non correct address is
151.098.046.171
PROXY NP
N.B. Verify on NP side that the communication link to RM is active. Issue Show on the star icon which
summarizes RM status. See following figure
Figure 624. shows that the Fast Restoration NPA is not alarmed. If the NPA list is not already open, from
the network icon you can issue Search: Related Items: NPAs.
With ref. to the following figure, point to the Fast Restoration NPA and issue Search: Related Items: Con-
trol Planes.
a) Figure below shows the NP map. Issue the pop-up Detail of the Compound TE Link Milano-Roma.
c) Issue the pop-up detail of TE-Link with suffix 08. This view is shown in figure herebelow.
a) Figure below shows the network map. Click twice on subnetwork icon NPOS.
b) The subnetwork map is shown in figure which follows. The icon NPA Fast Restoration is present in
the map.
c) With ref. to the following figure, select Search: Main Related Items of the link SDH between nodes
1678A-NP and 1678B-NP, which corresponds to NP Compound Link Milano-Roma.
e) Issue the Physical Connection Structure of Physcon NP_A-B_16-4. See following figure
a) From the list of Physical Connections, select the Physcon to remove and issue Maintenance: ASON.
See figure which follows
c) With ref. to above Figure 637., select ASON Admin. State=LOCKED and click on SET button.
d) Figure which follows shows the status change to LOCKED, the relevant logger messages and the
changes reflected on NP map: NEs involved in OPT (operator) state (yellow), Compound link in
MAJOR alarm.
e) Let us examine in detail how changes affect NP network. With ref. to fig. below, issue the detail of
Compound Link MI-RO.
f) The detail is presented. See figure below. Select the pop-up detail of TE Link s12 MI-RO-04
g) The detail of TE Link s12 MI-RO-04 is presented. Issue a Show of the port (see following figure)
h) The port has been removed (Status=UNV=unavailable for traffic) and the Domain (ACD) turned to
NPOS (1354NP)
i) Assign the port to department (see Figure 644. below). This command must be executed for both
ports of the TE link
m) The list of the interconnected ports is presented. See following figure. Select the couple of ports and
click on OK.
q) In Figure 652. you can verify that the TE-Link is no more present
r) On the painting of Figure 653. it is possible to check that the port previously involved in the connec-
tion is in OPT status (yellow). This painting has been displayed by following the chain of the hardware
details, from NE(prev.TS) thru rack, subrack and board.
s) From the list of Physical Connections which form the link, point to the Physcon to delete and issue
Npa: Remove from NPA
u) The Remove from NPA Fast Restoration has been successfully completed. Notice that the ASON
Admin. State=X= don’t care. See following figure
v) In addition, from the list of NPAs, point to NP and get the NPA view, via command Search: Related
Items. See fig. below.
w) In the NPA view, select icon Physical Connections. In the list, the removed physcon is no more
present.
a) Insert (physically) the new STM-4 port in board equipped in slot 5, network element 1678A, port 13.
Figure which follows shows the NM equipment view
b) On the board detail ( see fig. below ), the mismatch is in port 13.
f) On NP the port is Assigned to Department and not available in the network session, colored in black
g) On the Dept session the port is colored in Yellow. See picture below: the detail of the board is on the
left-hand side of the picture
k) Figure which follows shows that ACD=NP. The port usage is now SPAre and will become BKB (back-
bone) when the port will be part of an internal(RM naming) connection.
A prerequisite to this procedure is the creation of the involved ports. See procedure 3.2.2 on page 455.
a) With ref. to the following figure, six TE Links are included in Compound TE Link Milano-Roma.
b) In the Dept session create the TE Link (prev. BSG), via the pull-down menu TE-Link: Create: Phys-
ical.
d) The system, on the message line, asks to select the network element where the TE Link originates.
Select on the map (left click) the originating node. Its icon is blinking.
e) The system asks to select the network element where the TE Link terminates. See below figure.
f) The system asks to select the cable (SRG) originating on the previously selected originating network
element. See below figure.
g) Select the cable. In this example the new TE Link will cross only one SRG (cable) and the system
asks for confirmation of the creation. See figure which follows.
h) In the NP map, as a consequence of the creation of the new TE Link, the Compound TE Link changed
status to operator (Yellow). Point to this Compound TE Link and issue Detail. See following figure.
i) The new TE Link is UNV (unavailable=yellow) and not connected. Select the pop-up menu Connect
Ports.
j) The TE Link: Connect Ports dialog box is presented. Select the hierarchy and the port pair. Click on
OK.
k) In the detail of TE-Link-NEW, the ports are connected by the created link connections. Point to the
originating port and issue Assign to Network. A confirmation is required. See following figure
l) Execute the Restore to service of the port. The port goes INS-ACT (green). See figure
p) After the restore, all links (link connections) of the TE-Link, go INS-ACT.
a) From RM map point to the originating node and issue Create: Physical Connection. See below figure
b) In the Create Connection wizard step 1 select connection type=SDH, STM type=STM-16 and enter
the userlabel.
g) The implementation log is shown in the following figure. Till now, obviously, the ASON state is not
significant.
h) Figure 691.shows the detail of TE-Link_NEW. Its creation has been separately executed by NP oper-
ator on NP. See procedure Create TE Link on NP.
i) With ref. to Figure 692. issue Port: Show. The relevant dialog box is presented in Figure 693. . Port
usage is BKB as a consequence of the TE-Link creation, status goes from INS-ACT to UNV-LOA
(Unavailable-Local Operator Assignment), due to the implementation by R;M. Namely
ACD=1354RM.
k) The Add Physical Connection wizard is presented. See Figure 695. Select the NPA of type NP. Using
the usual selection modality, click on the selection list of the internal physcons, select the physcon
to add and click on Apply. See Figure 696. Click on Finish.
m) With ref. to the following figure, the new physcon is LOCKED (ASON Admin State).
n) Point to the new TE-Link and issue Maintenance: ASON. See figure below
o) The maintenance wizard is presented. See following figure. Select status=UNLOCKED and click on
SET.
p) The status changes to UNLOCKED (see Figure 701.) and on NP map the lc (LINK) statuses go INS-
ACT. See Figure 702.
q) Issue a Port: Show of one of the involved ports. See Figure 703.
N.B. The procedure to add a physcon type interworking is analogous, with the exception:
c) With ref to fig. below, in Folder CP Restoration, select Restoration Mode=No Restoration and Default
Priority=4
d) Create the path (Click on Finish), Allocate and Implement path NP-1.
e) From Circuit list, issue Circuit:Show. The priority=4 is the one entered at above point in Folder CP
Restoration, and suffix 01 of the circuit (snc) NP_1 01 means that only one SNC is required to accom-
plish path NP-1.
b) Clicking twice on the highlighted physcon-link (the compound), on the list of the Physcons, the
involved physcon is highlighted and marked as M/C. (main/current).
This means that the main (nominal) and the current route are the same. See Figure 712. herebelow
Move the Show dialog box below the map. The relevant SNC is highlighted on NP map. See Figure
713. The Path button, if selected, opens the path route/s show dialog box.
Circuit Route (Current on Nominal, selectable by a button), is highlighted in the network session win-
dow. Clicking on the highlighted parent object, opens the relevant child map. (E.g. if you clIck on the
NE, the NE detail is opened; if you click on the TE-Link, the TE-Link detail is opened, and so on...).
– for a 1+1 protected circuit the ports carrying actually traffic are marked by a (*) wildcard character
in brackets.
Note that the ports belonging the spare route are marked as (1+1)
– for a concatenated circuit, only the leader CTP/TTP is listed in the multicolumn list, marked by a +
(plus).
If you click on the + sign, the system displays the remaining CTP/TTPs too, while the leader is now
marked by a – (minus) sign, which allows to shrink the list to the default view.
– circuits virtually concatenated can be individually highlighted but are grouped graphically in the cir-
cuit list.
d) Click on the highlighted compound TE-Link. The detail is presented, the crossed/nominal link is high-
lighted.
b) After the execution of the Deimplement command, the circuit is no longer present on NP. See fig.
below.
b) The NPA list is displayed. Point to the fast Restoration NPA and issue Search: Related Items: NPA
view. See fig. below
d) In the SNC list of NPA called NP, the SNC called NP_3 01 is the mirror of circuit NP_3 01 in the NPOS
environment. See fig. below
e) The SNC list retrieved from the network is shown in fig. which follows.
b) Selection the ports in step 2 and in step 3 ( see Figure 724.) in Folder CP Restoration, select Res-
toration Mode=Precalculated and Reversion=Automatic
c) Create the path (Click on Finish), Allocate and Implement path NP-2. The procedure is the same as
described for Case 1 Path: Create
d) Notice that from Circuit. Show (see below figure), the resulting NP protection is automatic , i. e. NP
will use the precomputed paths table (k-paths) first to reroute the circuit, then as extrema ratio will
run the Djistra algorithm. So the path is not protected outside NP domain and protected inside.
In addition you see that the reversion type in NP is automatic.
a) In the Path Create wizard step1 select service=SDH, Rate=AU4. Enter name (NP_3 in this case) and
select Protection=None
b) Selection the ports in step 2 and in step 3, in Folder CP Restoration, select Restoration Mode=Upon
Failure
c) The behaviour of the system is the same as per above case 2
a) In the Path Create wizard step1 select service=SDH, Rate=AU4. Enter name (NP_4 in this case) and
select Protection=None
b) Selection the ports in step 2 and in step 3, in Folder CP Restoration, select Restoration Mode=Pre-
calculated, Reversion mode=manual. The selected parameters are shown in the following figure
e) Reversion type=manual implies that, in case of rerouting of the circuit NP-4 (due to a fault, e.g.), the
circuit goes INS-PRO (in service protected) and will remain in this status, without operator interven-
tion. See below figure
f) From Circuit: Show, the current route is highlighted; see fig. below
h) The reversion mode is manual, then the circuit remains on the protection route. To revert to the nom-
inal route, issue the command Path: Control Plane Restoration: Switch to Nominal. See fig. below
i) A confirmation is required. Click on Yes. The circuit reverts to the nominal and its status is now INS-
ACT. See fig. below.
a) Figure which follows shows oneof the two nodes housing the boards P4 x GE
b) Clicking twice on the board, you can get the board detail
c) Clicking twice on the port, you can get the port detail
– Service Type=Ethernet
– userlabel
– total concatenation level. Enter a number from 1 to 64. In this example we enter 33.
j) After path definition, the involved ports are structured with 33 AU4s, at both ends, according to the
request.
k) Figure which follows shows the path list, with path EPL_NP
r) In the involved ports, structured with 33 AU4s, at both ends, the 33 VC4s are connected (marked
with X)
scroll-up scroll-down
t) The ISA port configuration dialog box, which is shown below, shows the port no., the concatenation
level (33 in this case), the signal(VC-4-nV), the active TPs (33).
c) In the Bandwidth Modification dialog box enter: the action ( Decrease bandwidth in this case )
If you select Decrease bandwidth you will enter:
d) De-activate trails
In our example we selected to deactivate and remove 13 trails. See deimplement trails log in fig. which
follows
f) Bandwidth decrease can be seen on RM trail list and on NM and NP. See below figure
j) The list of the Server Trails is displayed. Twenty trails are present and implemented.
b) Click on Finish. Trails are created and allocated. See log below.
e) The ISA port configuration dialog box lists all significant info: the concatenation level (25=20+5 in
this case), the signal(VC-4-nV), the active TPs (25)
c) To highlight a trail, click twice on the trail row. The trail row is highlighted in blue and the trail is high-
lighted on the map. Select the highlighted Physcon on the map; the list of the trails crossing the phy-
scon is displayed. In particular, for the highlighted trail the role is M/C main/current.
e) Each trail is seen by NP as a single circuit. All trails virtually concatenated are grouped by a graphical
parenthesis. Issue the Show command of one virtually concatenated circuit
f) Moving below the dialog box, you can see the highlight on the map
g) Clicking on the highlighted compound, you will get the detail, with the highlighted TE-Link (BSG)
h) Clicking on the highlighted BSG, you will get the detail, with the highlighted bearer
a) From the path list and from circuit list, path NP2 includes circuit NP2 02
b) Circuit: Show dialog box is displayed below: the circuit NP2 is protected
c) From the Route list, the nominal and the current are the same
d) The Circuit highlight, at level of compound TE-Link is shown in fig. which follows
e) Clicking on the compound TE-Link, from the detail, the crossed TE-Link is TE-Link MI-RO-16-5
g) Click on the highlighted physcon link: the detail is shown below: the crossed physcon is physcon NP-
A_B-16-5
b) In the maintenance dialog box select status=Shutting-down and click on SET button.
d) In the NP map, the compound TE Link which contains the Shutting-down TE-Link is alarmed.
f) Figure which follows shows the detail of TE-Link MI-RO-16-5. Circuit NP2 has been rerouted (soft
rerouting) and its status is now INS-PRO. Issue a Port: Show.
k) In RM path list, the involved path NP2 has a warning alarm. Click on Show Elementary alarms.
l) The relevant alarm log opens: the path has been rerouted
m) The new current route can be displayed also via highlight on RM map. See below figure
n) Click twice on the highlighted physcon link. In the below list, physcon NP-A_B-16-4 is the one
crossed, while NP-A_B-16-5 is in maintenance.
c) In the NP map, the compound TE Link which contains the Unlocked TE-Link reverts INS (in service)
and the log (bottom of following figure) alerts that the auto restore of the involved circuit is in progress.
d) After a timeout (default 1 minute), because the path default reverse mode=automatic, the circuit
goes back INS-ACT.
– Circuit: Restore
a) From the path list select the path and click on Add Constraints button.
b) Setup the constraints in the Path Constraints dialog box and click on Finish.
b) In the Path: Modification Tool select option Reroute and click on Next button.
c) In the Path Modification Tool step2 dialog box click on button Get Routing Display
d) In the Routing display select the A connection. Only the selectable connections are highlighted. After
the choice of the connection, click on Select button.
e) Click on Get Routing display for the Z connection. See below figure
f) In the Routing display select the Z connection. Only the selectable connections are highlighted. After
the choice of the connection, click on Select button.
g) In the following figure A connection and Z connection are selected. Click on Finish button.
i) From Circuit:Show, route list (see below figure), notice that the nominal route changed
a) From the Circuit list point to the rerouted circuit and select Restore to the nominal route
c) As a consequence of the restore the circuit is again INS-ACT and in the path list the alarm ceased
d) As a consequence of the restore, from the route list it can be seen that the nominal route=current,
as a consequence of the reroute, the route changed
To add a protection route to an unprotected path, it is available also the command (pop-up menu item of
path) Modification: Add Protection: Spare. If the user selects this command, the terminations are selected
automatically by RM.
b) The list of the possible alternative routes is presented. As an example, select the first choice. The
route is highlighted on the map
c) Click on OK to confirm the selection. The circuit is soft-rerouted on the selected route (INS_PRO sta-
tus). From circuit show the reversion status =Rerouted by operator: automatic reversion not in effect
b) In Path Create step2 select the terminations. In this case only one virtual NE is involved, then ports
must be selected, with the desired rate, where the instrument will be connected.
c) Enter the Additional Information and click on Finish. The path routing display is shown in figures
which follow.
N.B. This type of circuit can be managed by NPOS operator RM_BYPASS, interconnecting Local
Drop ports. These local drop ports are shared, i.e. belonging to a physcon type interworking of
the Fast Restoration NPA.
c) Click on Add Backup buttons (lower part of the dialog box). Select the backup terminations
The creation of this path implies on NP network the set-up of a main route and a spare route, both inter-
connected to a Local Drop + a SPUR port. The circuit will be protected both at level of port and at level
of route.
Another NP operator, whose name is RM_BYPASS, is provided as default, which has the priviledge
RM_BYPASS. Only this NP operator can perform actions on connectivity.
b) The operator list is displayed. Select operator RMBYPASS and issue Operator: Show
c) The RMBYPASS Operator: Show dialog box is in fig. which follows. Notice that the priviledge
RM_BYPASS is included in the priviledge list (left lower part of following figure)
d) The SIR28C Operator: Show dialog box is in fig. which follows. Notice that the priviledge
RM_BYPASS is NOT included in the priviledge list (left lower part of following figure)
h) is rejected
NPA creation is included in the procedure of migration from NP standalone to NP + RM, then is
described here only as a reference.
CREATE NPA ( ON RM )
1) Create NPA type Fast Restoration e.g. from the 2nd level subnetwork map select Actions: Cre-
ate: NPA
2) In the step1 NPA wizard select NPA type=Fast Restoration, enter NPA cost reduction, NPA
usage cost and NPA name (userlabel) and click on Next button.
3) In the step2 NPA wizard select the internal (internal to the NP network) and interworking phys-
ical connections to assign to this NPA.
5) From the create report dialog box select button Implement and clixk on OK.
For interworking physical connection the following ACD values are setup: ACD=RM for the port controlled
by RM, sharedRM+NP for the boundary port.
For internal physical connection the following ACD values are setup: ACD=NP for both ports.
– path/trail. It opens on RM screen the NPOSCA graphical interface displaying the associated circuit
– subnetwork connection. It opens on RM screen the NPOSCA graphical interface displaying the
related NP circuit
– physical connection. It opens on RM screen the NPOSCA graphical interface displaying the related
TE-link
/usr/Systems/1354RM_<nms_instance>/conf/np_host_conf
tlvu13 xxx.yy.zz.ww
tlvu15 xxx.yy.zz.ww
the first string is the mnemonic name, the IP address is used as navigation command parameter.
SEQUENCE
a) Point to path/trail to correlate and issue the menu Related objects: Edit. The correlation selection
dialog box is presented.
b) Select 1353NP and click on OK. The correlation dialog box is displayed. See following figure.
c) Enter the name of the NPOS circuit to correlate to the path/trail and click on OK. The correlation is
then created.
a) Point to the path/trail and issue Search: Related. The WS selection dialog box is presented.
b) Click on dictionary button. From dictionary selection box select the WS and click on OK.
c) The WS address is now present in the WS selection dialog box. Click on OK. NPOSCA graphical
interface opens displaying the associated Circuit: Show view.
PHYSICAL CONNECTION
a) Point to the Physical Connection and issue Show: Details on NP. The WS selection dialog box ( see
above figure) is presented with the relevant WS already selected. Click on OK.
NP system alarms
Circuit alarms
N.B. For more detailed information on NP object status refer to NP Operator’s Handbook
N.B. Multiplex Section Protection internal to the backbone network or interworking are defined via
1353NM. 1354RM does not receive any notification.
ABBREVIATION MEANING
AP Access Point
AS Alarm Surveillance
AU Administrative Unit
BN Backbone Network
CAP Client Access Point. It represents a point where a client layer can
access a server layer ( i.e. a VC-4 that is configured to carry lower
order signals is a HO-CAP)
CI Communication Infrastructure
CT Craft Terminal
DS Degraded Signal
EML domain A set of NEs that are maintained by the same EML-OS.
FM FM Fault Management
IM Information Manager
LSP "Link single fault protection" index (LSP). The LSP index is deter-
mined (in a way similar to NSP for nodes) taking into account of
both the number (C) of archs belonging to the main route and the
number (D) of archs belonging to the main and spare routes.
Map Set of related objects , backgrounds,symbols and submaps
that provides a graphical and hierarchical representation of the
network.
MS Multiplex Section
NE Network Element
NSP "Node single fault protection" index (NSP). The NSP index is deter-
mined taking into account of both the number (A) of Nodes belong-
ing to the main route and the number (B) of Nodes belonging to the
main and spare routes, except the end nodes.
OH OverHead
OS Operation System
Physical Connection A Physical Connection connects two SDH ports in the network.
These two ports belong to different NEs and must have the same
transmission rate.
PM Performance Monitoring
PI Physical Interface
RC Raw Connection
RS Regenerator Section
SA Section Adaptation
SD Signal Degrade
SF Signal Failure
TF Transmit Fail
TM Terminal Mode
TN Telecommunications Network
TP Termination Point
TU Transport Unit
VC Virtual Container
XC Cross-Connect
Administrator:
A user who has access rights to all the Management Domains of the SDH Manager product. He has
access to the whole network and to all the management functionalities.
Alarm:
An alerting indication to a condition that may have an immediate or potentially negative impact on the state
of an equipment or the OS. An alarm is characterized by an alarm begin and an alarm end.
Alarm Status:
Identifies the type and severity of an occurring alarm.
Administrative Unit:
Entity composed of a high order virtual container (VC4) to which is added a pointer indicating the position
of the virtual container in the STM-N frame.
Board:
A board is part of an NE. They are electronic cards that fit into slots in the NE.
Craft Terminal:
Workstation or Personal computer (PC) from which local address to an NE is possible. It can be used to
configure or perform monitoring tasks on the NE.
Cross-connect (XC)
Cross-Connects provide the network with the Routing Capabilities, this is the possibility of routing one sig-
nal to a particular destination.
Degraded Signal:
Alarm sent when the number of errors detected in a received signal frame exceeds a certain threshold.
Filter:
Flushing:
This deals with logs. When a log is flushed, all its records are deleted.
Information Manager:
Processes used by the SDH Manger that are the functional part of the SDH Manager applications.
Line Terminal:
A line terminal is the end point of a communication link. it is used to transmit or receive signals. They can
undertake signal conversion functions (adapting a signal to two different transmission media) or multi-
plexing/demultiplexing functions.
Logs:
Logs are files used to store history data concerning the incoming notifications, operator commands and
system alarms. The size of the log can be configured.
Loss Of Frame:
Alarm linked to the regenerator section termination functional block, associated with the loss of signal
frame.
Loss Of Pointer:
Alarm linked to the section adaptation functional block, associated with the loss of a pointer in an admin-
istrative unit.
Loss Of Signal:
Alarm linked to the physical interfaces, associated with the absence of a received signal.
Multiplexer:
Equipment used to combine several signals to produce a single signal at a higher transmission rate and
to decompose it back to the smaller rate signals.
Multiplex Section:
In general, represents the section containing the multiplexed signals.
Network Element:
Either a telecommunication equipment or groups parts of a Telecommunication Network. Have charac-
teristics compliant with CCITT recommendations.
Notification:
Spontaneous data received by the system concerning an NE.
Operation System:
A system dedicated to the supervision of NEs in a standard way, using protocols and interfaces. it offers to
the operator a set of functions necessary to supervise the NEs. The SDH Manager is an Operation System.
Operator:
The end-user of the SDH Manager. He supervises a part of the network that is dependant on his user profile.
Physical Interface:
Electrical transformers that decouple the line signals and adapt the form of signal for further transmission.
This functional block also manages clock extraction, signal loss monitoring and loopback functions.
Port:
A physical point at which the Network Element can be attached to a transmission medium. A port is either
a termination point or an origination point.
Regeneration Section:
When there is at least one repeater between two interconnected equipments, each part of the line section
between two repeaters or between a repeater and an line system is called a regenerator section.
Repeater:
Equipment used to regenerate a signal when it has travelled a long distance.
Section Adaptation:
Synchronizes the incoming higher order virtual container (VC 4) or the incoming STM-1 signal to the out-
going STM-1 frame or the outgoing high order virtual container.
Severity:
Linked to alarms, severities indicate the magnitude related to the failure.
Session:
A session is a temporary association between an operator and the SDH Manager. A session always
begins with the identification and authentication of the operator (the login phase) and ends with the exit
of the operator from the SDH Manager (the logout phase). A session generally lasts a few hours.
Transmit Fail:
Alarm that indicate a dysfunction in the transmission of the signal.
Telecommunication Network:
Describes the network to be managed. Provides the transmission, the transport and the switching sup-
ports to the interconnected Network Elements.
Terminal Point:
Describes either the origin or the termination of a signal in an equipment. Is related to a port.
Thresholding:
This is the assignment of a specified value to monitored parameters ( for example BIt Error Rates) that,
when exceeded, generate trouble indications.
Tributary Unit:
Entity composed of a virtual container to which is added a pointer that indicates the position of the con-
tainer in the STM-N frame.
User Profile:
Identifies the functionalities of the SDH Manager to which a user has access. A finite number of predefined
user profiles is determined by a fixed set of FADs.
Virtual Container:
Virtual Containers are managed by the SDH Manager. Entity composed of an information signal to which
a path overhead has been added. The path overhead is used in the management of the information signal.
Different types of virtual containers exist depending on the rate of the information signal. Lower and Higher
order virtual containers exist. The SDH norm identifies VC11, VC12, VC2, VC3 and VC4 virtual containers
named from the lowest (VC11) to the highest (VC4) container capacity.
Wrapping:
Wrapping is the technique that enables the most recent entries in a file to replace the oldest when a file
is full.
Scope of this activity is the improvement and innovation of customer documentation through the under-
standing of customer needs.
You can send them to your Local Alcatel Technical Assistance Center.
The following form supplies an example only of useful info, as a guide of the type of expected feedback.
It is possible fill part of the form, add other data and so on.
• copying the example form, filling it and sending it to your Local Alcatel Technical Assistance
Center. In this case handbook data are already available at the page bottom.
• using the same form available as a file in the relevant documentation CD-ROM, saving, filling
and sending it by e-mail to your Local Alcatel Technical Assistance Center.
• creating a dedicated form on paper or file and sending it to your Local Alcatel Technical Assis-
tance Center.
We reserve to modify consequently the handbook according to the corretness and congruence of the sug-
gestion and requests.
How to deepen:
Other comments/suggestions
Errors Identified
Reader Info
Name:
Company:
Address:
E-mail:
Phone:
www.alcatel-lucent.com