71noptnms Am A

Coriant Training Services
7100 Nano Operations and

Provisioning using TNMS
for America Movil
DISCLAIMER
Coriant training materials may contain simplifications and are not to be considered as technical
documentation or product specifications. The materials are subject to change. Coriant Training Services
assumes no liability for any errors or discrepancies contained in the training materials.
The following trademarks and service marks are owned by Tellabs Operations, Inc., or its affiliates in the
TM
TM
United States and/or other countries: CORIANT , MTERA , TELLABS , TELLABS and T symbol , and
T symbol . Any other company or product names may be trademarks of their respective companies.
Copyright 2014. All rights reserved.
This training material is protected by U.S. and international copyright laws, conventions and treaties. Your
right to use this training material is subject to limitations and restrictions imposed by applicable licenses
and copyright laws. Unauthorized reproduction, modification, distribution, display or other use of this
training material may result in criminal and civil penalties.
CONFIDENTIAL & PROPRIETARY
Copyright Coriant 2014. All rights reserved.
7100 Nano Operations and Provisioning

using TNMS
for America Movil
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
CORIANT CONFIDENTIAL & PROPRIETARY
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
Course Introduction
05.5065.9039 Rev 11
00_71NOPTNMS-AM-A
System Architecture Management Description & Applications
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
The layers are built upon each other by the addition of Overhead Bits (OH).
Once enough overhead is in place to create an Optical Channel (OCH), Multiple Optical Channels
can be transmitted together depending on how many wavelengths the equipment can support.
Lastly, a single Optical Supervisory Channel (OSC) is added for communication between Network
Elements.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
In the slide, the facilities are mapped to an ODU as part of the provisioning process. The lower order
ODUs (ODUi and ODUj) are multiplexed into the higher order ODUs (ODUj and ODUk) with ODUk
being the highest order.
In both examples above, the ODUj and ODUk occur at the same level. However, that may not always be
the case, since the letters k,j,i etc. simply indicate a relationship based on order.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
In this slide, the facilities are again mapped to an ODU as part of the provisioning process. The lower
order ODUs (ODUj) are again multiplexed into the higher order ODUs (ODUk), with ODUk being the
highest order. Notice, however, that the capacity is dramatically different.
.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
10
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
11
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
12
Quad Small Form-Factor Pluggable Plus (QSFP+) modules offer customers a wide variety of highdensity 40 Gigabit Ethernet connectivity options for a variety of service provider transport applications.
QSFP+ modules have two connectivity options using either LC or MPO Connectors.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
13
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
14
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
15
The table above is from the 71M-FGTMCFP 40G Transponder Module - Enhanced (FGTM-E) tech doc.
Each Module Practice tech doc will have a similar table documenting the pluggable part number, type,
signal format, and power levels for that module.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
16
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
17
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
18
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
19
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
20
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
21
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
22
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
23
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
24
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
25
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
26
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
27
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
28
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
29
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
30
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
31
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
32
G1731 performance monitoring is supported in the Packet Subsystem.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
33
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
34
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
35
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
36
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
37
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
38
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
39
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
40
Additional transponder modules may be seated in slots 3 and 6 of each main shelf. This provides up to 8
additional slots for transponder modules.
Although the 7170x shelf is being shown in the slide, the 19 H shelves, which are discussed next, are
arranged in the same manner for an 8 degree configuration.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
41
The Primary parts and functionality of the Nano19H shelf are almost identical to the Nano 7170x. The
primary difference is that the Nano19H does not have the integrated Fiber trough. Therefore, depending
upon the required configuration, it can be further modified to accommodate a wide variety of installation
environments. As with the Nano 7170x shelf, a customer-provided 30Amp -48VDC breaker panel can be
used or the Power Distribution Unit (PDU). For a cabinet installation, there is also a High Redundancy
Dual Rectifier System Configuration available.
The high redundancy dual rectifier system uses two AC/DC rectifier shelves to supply redundant power
for up to three 7100N shelves. Each AC/DC Rectifier shelf supplies DC power to either the A-side power
or the B-side power for each of the supported 7100N shelves.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
42
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
43
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
44
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
45
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
46
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
47
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
48
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
49
The Primary SPMNs are connected in a ring for survivability, while the Standby SPMNs are connected
via a second ring.
CT-1 and CT-2 are RJ-45 Ethernet connectors on the SPM-N cards. The connectivity is referred to as
daisy-chained where CT1 of Shelf 1 connects to CT2 of Shelf 2. CT1 of Shelf 2 then connects to CT2 of
Shelf 3 and so on.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
50
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
51
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
52
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
53
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
54
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
55
The 7100N OTS supports four different versions of the Optical Add/Drop Mux (OADM) modules:
OADM88-xR
OADM88-xR is a two-slot module that combines input amplifier, output amplifier, interleaver, and
wavelength switch capabilities supporting up to 88 Channels and 4 degrees (A, B, C, and D) in a
7100N OTS.
OADM88-8D-xR
OADM88-8D-xR is a two-slot module that combines input amplifier, output amplifier, interleaver, and
wavelength switch capabilities supporting up to 88 Channels and 8 degrees (A, B, C, D, E, F, G, and
H) in a 7100N OTS.
OADMF8
OADMF8 is an optical multiplexer with 8 fixed add/drop channels (100 GHz spacing) and the ability to
pass through up to 44 channels and is used to support Fixed DWDM applications.
Directionless OADM (DXOADM)
The Directionless Solution for the 7100N uses the OADM88-8D modules as Degrees and the
DXOADM + OMD88 combination as Directionless Add/Drop terminals. Multiple Directionless
Add/Drop terminals are supported. Most common deployment will be 2 DXOADM terminals with up to
6 Degrees.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
56
Supported Span Loss

OADM88-IR = 0 dB to 18 dB
OADM88-LR = 14 dB to 26 dB
OADM88-ER = 25 dB to 35 dB
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
57
The OADM88-IR and supports span loss of 0 dB to 18 dB and a gain range of 3.4 dB to 22.3 dB.
The OADM88-LR supports span loss of 14 dB to 26 dB and a gain range of 17.2 dB to 29.2 dB.
The OADM88-ER supports span loss of 25 dB to 35 dB and a gain range of 29 dB to 39 dB.
Aggregate power is limited to +21.3 dBm maximum at the output of the amplifier assembly.
OADM88-IR maximum input power at DWDM Line In is 19.5 dBm.
OADM88-LR maximum input power at DWDM Line In is 5.5 dBm.
OADM88-ER maximum input power at DWDM Line In is -5.5 dBm.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
58
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
59
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
60
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
61
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
62
81.71188-IR Line Input Amplifier Module, Intermediate Reach Enhanced (LIAM-E88)
Supports Transport Spans with loss between 0 dB to 18 dB
Manual Gain adjustment +0 to +18 dB
81.71188-LR Long Reach Amplifier Module Enhanced (LRAM-E88)
81.71188-ER Extended Long Reach Amplifier Module Enhanced (ELRAM-E88)
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
63
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
64
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
65
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
66
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
67
The transponders support different maximum Line Side bit rates:

10 Gigabit per second
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
68
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
69
The Transponder families are discussed next. A transponders placement in a particular family does not
mean that it does not have the capability to also perform in another family. Its placement in a family is
due to the transponders primary function and also for ease of presentation.
It is also understood that your organization may not have all of these transponders in its network.
Therefore, the instructor make adjustments based on your comments and information provided when the
class is scheduled to only discuss those transponders deployed in your organizations network.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
70
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
71
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
72
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
73
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
74
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
75
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
76
At Feature Package 8.0, Tandem Connection Monitoring (TCM) is also supported and is an advanced
capability of Operations, Administration, Maintenance and Provisioning (OAM&P) providing End to End
performance monitoring, connectivity monitoring, and signal quality supervision of a signal through other
provider networks. TCM bytes are part of the ODUk overhead. In the OSM20, they are at the ODU2
level.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
77
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
78
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
79
TNMS supports:
Remote login - TNMS supports remote login from an external machine via TCP/IP.
SSO Login - TNMS allows you to automatically login using your operating system credentials (see
the Administration Manual for more information on SSO).
Automatic reconnection - An automatic reconnection to the NEs is supported in case of
communication loss. You can configure the retry interval.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
80
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
81
81
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
82
82
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
83
Server Application
The server provides the environment for running the software components, for example, EM/NE
management, Backup and Restore, or Mediator. All system information is held on the server. TNMS
uses an Oracle database for storing alarms, system messages, user data, DCN data and a security log.
Security authorization is handled via OpenDS. The server processes client requests by using the
mediation to communicate, via the DCN, with the NEs themselves. Information (for example, object type
and hierarchical status) is retrieved from the NEs and stored on a dedicated Oracle database. Another
database, OpenDS, keeps user data and is involved in users authentication.
Client Application
The client provides a network management GUI. All management functions, for example, provisioning of
end-to-end-services and invoking of element managers, are available through this GUI.
TNMS supports scalable configurations:
Large system
A large-system Server, whether running Oracle Solaris or Microsoft Windows, supports up to 32 Clients
under a standard, Coriant-defined load model, and up to 32 Clients under a simplified load model.
Medium system
A medium-system Server, whether running Oracle Solaris or Microsoft Windows, supports up to 16
Clients under a standard, Coriant-defined load model, and up to 48 Clients under a simplified load
model.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
84
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
85
85
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
86
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
87
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
88
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
89
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
90
The status bar lines the bottom of the main window and displays information about the systems
operating state.
Rest the mouse pointer on several items for short-form TNMS Client information.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
91
GCT or GUI Cut-Through allows you to launch, from within TNMS, a specific NEs element manager
application, also known as Local Craft Terminal, and is available from context menus in a number of
sources, for instance the NE under DCN Management, the NE symbol on the network map under
Topology Management or an alarm log record or entry under Log Management.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
92
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
93
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
94
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
95
Coriant equipment will be deployed as OTN network for Lineas Privadas project. The scope of this
project is to consolidate two networks, the international IP backbone and the international SDH lease
lines into one network.
On phase 1, the network will be deployed over nine countries: USA, Argentina, Brasil, Chile, Colombia,
Ecuador, Per, Mxico y Puerto Rico. Network management is going to take place at Mexicos office.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
96
The integration of both traffics will reduce the amount of lease lines contracted to third party service
providers and save a significant OPEX into the network. The consolidation of the two networks will take
place over an OTN backbone migrating STM64 leased lines to OTU2 leased lines transporting
IP/Ethernet and SDH over OTN.
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
97
TGLAN incoming traffic will be only 7.5gbs (48 VC4s), allowing the chance to multiplex 1GE or SDH
traffic (STM1/4/16).
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
98
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
99
99
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
100
100
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
101
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
102
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
103
05.5065.9039 Rev 11
01_71NOPTNMS-AM-A
104
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
For the purpose of this class, we will use the following username and password:
Username: administrator
Password: Coriant1$
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
Network Building
DCN Management window can be open using the DCN Management button or using the Network Menu.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
10
Network Building
In the DCN Management window:

1.
2.
Right click the desired Element Manager and click New NE

When the New Network Element list appears, select 7100 NANO FPX.x
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
11
Network Building
In the General tab of the New NE Properties window, type an ID name for the new NE.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
12
Network Building
In the TL1 Settings tab of the New NE Properties window enter the following parameters:
- IP
- TID
- User name
- Password
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
13
Network Building
When the New NE shows up under the Element Manager you are working with, enable the check box.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
14
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
15
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
16
Network Building
1. Click the New Topological container button.

2. After the cursor shows a cloud, click anywhere in the window.
3. When the New Topological Container window appears, enter a Container Name.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
17
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
18
Network Building
Double click the new Topological container and Drag and drop the desired NEs from the DCN
Management window to the Network map window.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
19
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
20
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
21
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
22
Network Building
1.
2.
Open the Network Map.

Right click the first endpoint (7100N) and select New Physical Trail.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
23
Network Building
3. Select the correct TTP in endpoint A. For SSM-X modules, a SPI-OS64-TTP (STM-64) must be
selected.
Note: In the case of the SSM-X, a STM-64 port facility in port 2 must be created previously.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
24
Network Building
4. Drag and drop End point Z.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
25
Network Building
5. Select the correct TTP in endpoint Z.

6. Click the Connect Bidirectional button.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
26
Network Building
When the Modify Physical Trail window pops up, you can Add/Edit the Attributes description and
comments.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
27
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
28
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
29
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
30
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
31
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
32
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
33
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
34
Network Building
Right click the desired physical trail and click Manage.

It is possible to rename the trail/service if necessary.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
35
Network Building
An Operation Successful message will pop up at the bottom of the screen.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
36
Network Building
1.
2.
Open the Network Map.

Right click the first endpoint (7100N) and select New Physical Trail.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
37
Network Building
3. Select the correct TTP in Endpoints A and Z. For OSM20 modules, an Optical-Gpi-OTU2-TTP must
be selected.
4. Click the Connect Bidirectional button.
Note: In the case of the OSM20, an OTU2 port facility must be created previously.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
38
Network Building
When the Modify Physical Trail window pops up, you can Add/Edit the Attributes description and
comments.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
39
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
40
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
41
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
42
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
43
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
44
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
45
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
46
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
47
Network Building
Right click on the NE and click Open.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
48
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
49
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
50
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
51
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
52
Network Building
To Run a query, select the desired one and click Run.

An asterisk next to a predefined query indicates that you have modified the query and have not yet
saved it.
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
53
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
54
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
55
Network Building
05.5065.9039 Rev 11
02_71NOPTNMS-AM-A
56
Provisioning Services
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
None of the ports are set by default. The type port depends on the SFP/XFP and the selection of the
user.
Port 2 will be provisioned as STM64 and line facilities must be created as required for the crossconnections.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
Two SSM-X are needed in order to map client traffic into the transport line.
One TGLAN client port with 48xVC4 (7.5G) will leave room for other SDH/Ethernet traffic.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
Client port creation step list:

1. Right-click the client SSM-X module, select create port facility and select create sonet/sdh
facility.
2. Select the Facility type and the appropriate Port Number.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
VC4 Termination point creation:

1. Right-click the SDH port, STM1 in this example. Select Termination Point and select create VC.
2. Select the Facility type and from the available list, select the amount of VC4s. In this example only
one VC4 is available for an STM1. Add with the arrow button.
3. When all the VC4 are added, click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
10
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
11
Client port creation step list:

1. Right-click the client SSM-X module, select create port facility and select create Ethernet/Data
facility.
2. The Facility type is set to ETH. The Port Number is related to the capacity: Port 2 up to 10G and
port 3-14 up to 1G. The capacity is set with the VCG Creation.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
12
Trail Termination point creation: represent the mapping endpoint.

1. Right-click the TTP entity, select Create TTP.
2. Select Facility Type for the needed structure.
3. Add the amount of TTPVC4 for the needed capacity. Consider total amount of client ports for the
TTP creation. Click the arrow button to add.
4. When all the TTPVC4 are added, click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
13
VCG creation: virtual grouping of the endpoints.

1. Right-click the VCG entity, select Create VCG. Fill the parameter at the attributes tab:
VCG application: EPL for physical relation between the port and VCG. If no VLAN aware
applications, this is the recommended option.
VCG type: Set manual (recommended) to assign TTPs or auto and the TTP will be created by
the tool.
VCG number: If EPL the match the physical port number to the VCG number.
VCAT Type: Select the type that matches the created TTP.
LCAS: Select On to be able to modify the capacity in the future.
2. Select the Members tab and assign the already created TTPs.
(Continued on next page)
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
14
3.
4.
5.
6.
Click Add TTP button.

Select the TTP members and click ok. Use Shift key or Ctrl key to select multiple TTPs at once.
Click Ok when done.
Click ok on the main window to finish VCG creation.
Click ok to confirm the creation.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
15
EVC creation: Associates the physical port to the VCG.

1. Under the VCG folder, search the VCG and right click on it. Select Create EVC.
2. With Browse button, search for the needed port and set the Source Facility.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
16
1.
2.
3.
4.
Review the Ethernet port.

Review the TTP.
Review the VCG.
Review the ETH PORT-VCG association.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
17
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
18
Line Facilities are the entities that allow us to cross-connect client traffic up to the line.
In this particular scenario, a second module is needed as line output because of capacity requirements.
1.
2.
3.
Right click on the STM64 on port 2, select Termination Point, select Create VC.
Choose the Facility Type structure and add from the available list to the Selected list with the
arrow button.
Click ok when done.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
19
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
20
Cross-connect window can be retrieved from several entities. The recommended is to:
1.
2.
3.
Right click the line Termination Point under the STM64 line port. Select Create VC Crossconnection.
The source square is fixed to the selected Termination point. The Destination square must be set
with the browse button.
Select the proper card, select Facility, select the client Termination point and click ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
21
For the STM1 cross-connection, fill the window as depicted.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
22
For the Ethernet cross-connection, fill the window as depicted. Notice that a cross-connection is only
possible on Termination Point one at a time. For example: if 1GE is created with 7xVC4, then 7
individual cross-connections are needed.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
23
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
24
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
25
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
26
None of the ports are set by default. The type port depends on the SFP/XFP and the selection of the
user.
Port 2 will be provisioned as OTU2 and line facilities must be created as required for the crossconnections.
The mapping from the Client port to the line port is done at OTN layer.
In OTN, when mapping a lower rate ODUj into a higher rate ODUk, the higher rate ODUk is divided into
1.25 Gbps tributary slots, which are allocated to carry the ODUjs. On the OSM20, up to 16 1.25G
tributary slots are supported on a single module. An OTU2/OCH-P interface uses eight 1.25G tributary
slots. An OTU1 interface uses two 1.25G tributary slots. For non-OTUk clients, the number of 1.25G
tributary slots used is based on the tributary slots required to carry the ODUj for which the client is
mapped.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
27
Two OSM20 are needed in order to map client traffic into the transport line.
One OTU2 will be the line port with ODU2 facility in any of OSM20s. The client ports could be any rate
until they reach the maximum of 16x1.25G Tributary slots on the other module. Cross-connections are
done across the backplane.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
28
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
29
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
30
OTN client port creation:

1. Right-click on the client module, select Create Port Facility, select Create Optical facility.
2. Set the Facility Type OTU1 and port Number.
3. Click Ok.
4. Click Ok to confirm.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
31
ODU client facility creation:

1. Right-click on the client module, select Create ODU.
2. Set the Facility Type and port Number that matches the client port, in this example ODU1.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
32
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
33
Ethernet client port creation:

1. Right-click on the client module, select Create Port Facility, select Create Ethernet/Data facility.
2. Set the Facility Type Ethernet and port Number.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
34

3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
35
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
36
SDH client port creation:

1. Right-click on the client module, select Create Port Facility, select Create Optical facility.
2. Set the Facility Type STM1and port Number.
3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
37

3. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
38
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
39
ODU line facility creation:

1. Right-click on the line module, select Create ODU.
2. Set the Facility Type ODU2 and port Number that matches with the OTU2 on port 1.
3. Select the Trib Size. In this example 1.25G.
4. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
40
ODU tributary facilities creation:

1. Right-click on the ODU2, select Create ODU.
2. Set the Facility Type ODU1 to match the ODU1 client facility.
3. For ODU1 select two Tributary Slots (1.25G) with the Arrow button.
4. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
41
ODU tributary facilities creation:

1. Right-click on the ODU2, select Create ODU.
2. Set the Facility Type ODU1 to match the ODU1 client facility.
3. For ODU1 select two Tributary Slots (1.25G) with the Arrow button.
4. Click Ok.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
42
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
43
Create ODU cross-connections:

1. Right click on the ODU to cross-connect and select Create ODU Cross-Connection.
2. Source will be set to the selected ODU. Browse the destination and select the proper card and
ODU.
3. Click ok when done.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
44
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
45
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
46
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
47
To open Micro topology view:

Right-click on any of the cross-connections and select View Microtopology.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
48
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
49
Use the Query button to retrieve information on cross-connections.

There is a big list of query sorts that can be run to show configurations. For example: port types,
termination points.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
50
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
51
The 8000 INM will display nominal optical power levels throughout the system and for each unit. Optical
power levels are also found in the 7100/7100N System Specifications Document and sometimes in the
transponder technical documents.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
52
To retrieve Optical values:

1. Right click on the module and select Measure Optical Power.
2. Select Signal Direction and Port Number, click ok to confirm.
The Report button can provide the information in a proper way to save or print.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
53
The third method of verifying connectivity is done at the SHD circuit level. This example will show an
STM16 circuit. You can enable or disable Receive Trace Monitoring and or Trace Generation.
1.
2.
3.
Expand a transponder and locate an SDH port such as the STM-16 above. Right click on SDH port
and select Properties from the drop down menu.
Enable Trace Monitoring and set a the Sent J0 Trace.
Click OK on the properties screen.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
54
54
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
55
1.
Open Node Manager for the desired Network Element.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
56
56
2.
3.
4.
Choose a transponder to perform a loopback on. Expand the transponder so ports displays. Right
click on the desired port and select Properties.
Click the radio button next to Out of Service (OOS). A loopback cannot be performed without taking
the facility out of service first.
Click OK.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
57
57
5.
6.
On the Navigation pane, right click the port.

Select Loopback and the type of loopback desired. In this example we will create Terminal
Loopback.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
58
58
7.
Click on the Yes button. The next slide displays the loopback.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
59
59
8.
9.
Click on the OK button.

Now observe the three different locations of loopback information indicated by the arrows. There is
a loopback icon next to the port, the word (Loopback) to the right of the port, and an alarm indication
describing the type of Loopback.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
60
60
1.
To Release a loopback, expand the transponder, and right-click on the Port or other facility that is in
loopback state, select Loopback and click on Release Loopback.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
61
61
2. Click OK on the Confirmation dialog screen.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
62
62
3.
4.
Observe that the loopback indications are now gone. Click on the OK button of the Success screen.
Now go back to the Properties screen of the OCH-P and put it back In Service.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
63
63
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
64
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
65
65
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
66
66
The PRBS Report includes:

Pattern Sync: whether the PRBS pattern is synchronized. (Pattern Sync indicates whether the
received PRBS pattern is the same as the one being transmitted).
Duration-time elapsed since PRBS was started.
Calculated Bit Error Rate (BER).
Bit Error Count: how many bit errors have been reported during the collection period.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
67
67
This activity will involve selecting an STM1 on a transponder in different network elements, removing it
from service, establishing a loopback, and then sending PRBS as a Bit Error Rate Test (BER).
1.
2.
In Node Manager, select a transponder to work with. Expand the transponder.

Right-click on the desired Port, select Properties and take the OCH-P out of service.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
68
68
3. Right-click on the OCH-P-2-2-1, select Loopback, then Operate Terminal.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
69
69
4.
5.
Observe the Terminal Loopback on the OCH-P.

Click OK on the Success screen.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
70
70
6. Right-click the OCH-P and select BER Measurement from the drop down menu choices.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
71
71
7. Click the Start buttons for Transmit PRBS and Receive PRBS.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
72
72
8.
You can Refresh the interval of BER polling if desired. Observe the Calculated BER, which in this
case is 0 and the Bit Error Count, which is also 0. Pattern Sync indicating INSYNC means that the
received PRBS pattern is the same as the transmitted PRBS pattern.
9.
When the test is completed, click on the Stop buttons for each direction of PRBS generation.
10. Release the loopback, and restore the OCH-P to an In Service state.
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
73
73
05.5065.9039 Rev 11
03_71NOPTNMS-AM-A
74
Control Plane Overview
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
Traditional transport networks can be seen as the interaction of two operating planes: a transport plane
and a management plane. In this idea, the transport plane carries the user data and comprises network
equipment, such as modules, switch fabrics, backplane, etc. Network operation, administration,
maintenance and provisioning is fully handled by the management plane, implemented by an EMS.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
The Control Plane is now deployed to sit between the management and transport planes. The control
plane moves some of the network intelligence down to he NEs. As a result, the NEs have access to
complete network topology and resource information, and can use this to plan, establish, and maintain
services.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
GMPLS is deployed from MPLS Apply MPLS control plane techniques to optical switches and IP
routing algorithms to manage light paths in an optical network.
GMPLS made some modifications on MPLS:
-
Separation of signaling and data channel

Support more types of control interface
GMPLS is proposed to support IP over DWDM.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
10
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
11
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
12
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
13
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
14
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
15
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
16
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
17
Signaling Communications Network (SCN)

The SCN is where the control plane components communicate with each other. Communications are
conducted through signaling and routing messages. Abstract messages are converted into protocol
messages by protocol controllers (PCs).
Routing protocols advertise the optical network topologies and the available bandwidth resources within
and between the network domains. Control plane uses signaling protocols for provisioning, maintaining,
and deleting connections.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
18
Routing Controller (a.k.a. OSPF routing instance) exists at the SCN (signaling) level and it is a process
associated with an OSPF area.
It is a virtual router which uses OSPF to manage link status, discover neighbors and advertise
interfaces.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
19
A routing domain is a set of routers that are all under the same administrative control, such as the same
routing protocol.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
20
Switching fabric is the combination of hardware and software that moves data coming in to a network
node out by the correct port (door) to the next node in the network. It is also used to mean collectively all
switching hardware and software in a network.
Switching fabric includes the switching units (individual boxes) in a node, the integrated circuits that they
contain, and the programming that allows switching paths to be controlled.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
21
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
22
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
23
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
24
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
25
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
26
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
27
Routing Controller
The router controller responds to requests for path (route) information needed to set up connections and
responds to requests for topology information for network management purposes. This information can
range from end-to-end path details to the next hop. The route can be computed by one or more
cooperating RCs. The secondary role is to respond to requests for topology information for the network
management purpose.
The role of routing controller is to:
Respond to requests for path (route) information needed to set up connections. This information can
range from end-to-end path details to a next hop. The route can be computed by one or more
cooperating RCs.
Respond to requests for topology information for network management purposes.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
28
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
29
Switching fabric is the combination of hardware and software that moves data coming in to a network
node out by the correct port (door) to the next node in the network. It is also used to mean collectively all
switching hardware and software in a network.
Switching fabric includes the switching units (individual boxes) in a node, the integrated circuits that they
contain, and the programming that allows switching paths to be controlled.
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
30
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
31
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
32
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
33
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
34
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
35
05.5065.9039 Rev 11
04_71NOPTNMS-AM-A
36

71noptnms Am A

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

71noptnms Am A

Transféré par

Droits d'auteur :

Formats disponibles

Coriant Training Services

7100 Nano Operations and

Copyright Coriant 2014. All rights reserved.

7100 Nano Operations and Provisioning

CORIANT CONFIDENTIAL & PROPRIETARY

CORIANT CONFIDENTIAL & PROPRIETARY

CORIANT CONFIDENTIAL & PROPRIETARY

CORIANT CONFIDENTIAL & PROPRIETARY

CORIANT CONFIDENTIAL & PROPRIETARY

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY

System Architecture Management Description & Applications

CORIANT CONFIDENTIAL & PROPRIETARY