OP00090-V-1-SG-Ed1 - PDF

Available
as PDF
NFM-T R.18 Managed plane Network

construction with 1830 PSS
operations
Student Guide
OP00090-V-1-SG-Ed1
©
1 Nokia 2018 Nokia Confidential
Disclaimer
The information in this document applies solely to the hardware/software product (“Product”) specified herein, and
only as specified herein. Reference to “Nokia” later in this document shall mean the respective company within
Nokia Group of Companies with whom you have entered into the Agreement (as defined below).
The contents of this document are proprietary related specifications or other documentation. accuracy, reliability or contents of this
This document
and confidential is intended
property of Nokia.for
This use by Nokia's customers
Accordingly, if the user of (“You”)
this documentonly,
givesand it document.
may not beSHALL
NOKIA used NOTexcept for the
BE RESPONSIBLE
purposes defined in the agreement
document is provided subject to confidentiality
obligations of the applicable agreement(s).
between You and Nokia (“Agreement”)
Nokia Feedback on the contents of this
document, Nokia may freely use, disclose,
under which this document
IN ANY EVENT FOR ERRORS IN THIS DOCUMENT
or for
is
distributed. No part of this document may be used,
reproduce, license,copied, reproduced,
distribute and otherwise modified
any loss ofor
datatransmitted in any form or
or income or any special,
means without the prior written permission
This document is intended for use of Nokia’s
customers and collaborators only for the
of Nokia. If You have not entered
commercialize the feedback in any Nokia
product, technology, service, specification or
into an Agreement applicable to the
incidental, consequential, indirect or direct
damages howsoever caused, that might arise
Product,
purpose orforifwhich
thatthisAgreement has expired
document is submitted otherordocumentation.
has been terminated, You mayfrom nottheuse
use ofthis document
this document or any in any manner
contents
and You are obliged to return
by Nokia. No part of this document may be
it to
reproduced or made available to the public or to
Nokia and destroy or delete
Nokia operates a policy of ongoing
any copies thereof. The
of this document.
document has been
prepared
any thirdtoparty
beinused
any form byor means
professional
without the and properlyNokia
development. trained
reservespersonnel,
the right to makeand You Thisassume
document and fulltheresponsibility when using
product(s) it describes
it. Nokia welcomes your comments as part
prior written permission of Nokia. This
document is to be used by properly trained
of the process of continuous development
changes and improvements to any of the
products and/or services described in this
and improvement of the
are protected by copyright according to the
applicable laws.
documentation.
professional personnel. Any use of the contents document or withdraw this document at any
in this document is limited strictly to the use(s) time without prior notice. Nokia is a registered trademark of Nokia
This document and
specifically created itsapplicable
in the contents are provided as a convenience to You. Any Corporation. information Other or statements
product and company concerning
the suitability, capacity, fitness for purpose
agreement(s) under which the document is
submitted. The user of this document may
or performance of the Product are
The contents of this document are provided "as
is". Except as required by applicable law, no
given solely on an “as is” and “as
names mentioned herein may be trademarks or
trade names of their respective owners.
available” basis
voluntarily insuggestions,
provide this document,
comments orand Nokia reserves
warranties of any kind,the right
either toorchange
express implied, any such information and statements
without notice. Nokia has made
other feedback to Nokia in respect of the
contents of this document ("Feedback"). Such
all reasonable efforts to ensure
including, but not limited to, the implied
that
warranties of merchantability and fitness for a
the content of this document is adequate and
free of material
Feedback may be errors and
used in Nokia omissions,
products and and Nokia
particular will correct
purpose, are made inerrors
relation tothat
the You identify in this document. Nokia's total
liability for any errors in the document is strictly limited to the correction of such error(s). Nokia does not warrant
that the© use
2 Nokia 2018 of the software in the Product will be uninterrupted Nokia Confidential or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY OF
AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE, IS MADE IN RELATION TO THE CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE
LIABLE FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS
INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE
INFORMATION IN IT, EVEN IN THE CASE OF ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and confidential information, which may not be distributed or disclosed to any
third parties without the prior written consent of Nokia. Nokia is a registered trademark of Nokia Corporation.
Other product names mentioned in this document may be trademarks of their respective owners.
Copyright © 2018 Nokia. All rights reserved.
Important notice on product safety

This product may present safety risks due to laser, electricity, heat, and other sources of danger.
Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only
after having carefully read the safety information applicable to this product.
The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental
Information” part of this document or documentation set.
Nokia is continually striving to reduce the adverse environmental effects of its products and services. We would like
to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please
recycle product packaging and follow the recommendations for power use and proper disposal of our products and
their components.
If you should have questions regarding our Environmental Policy or any of the environmental services we offer,
please contact us at Nokia for any additional information.
RA4707EN16GLA00
Export Control Marks: N / 5E991X
This course is subject to the European Export Control Restrictions.
Copyright © 2018 Nokia. All rights reserved.
The reproduction, transmission or use of this document or its contents is not permitted without express written
authority.
Offenders will be liable for damages. All rights, including rights created by patent grant or registration of utility
model or design, are reserved.
Technical modifications possible.
Course outline
Welcome to NFM-T R.18 Managed plane Network construction with 1830 PSS
operations
1. Network construction
1. Course introduction
2. NFM-T graphical interfaces
3. NE creation and supervision
4. EQM and Map creation
5. Network construction
6. 1830VWM CPRI management
2. Appendix
1. Commissioning and Power Balancing for 1830 PSS WDM
Course objectives
NFM-T R.18 Managed plane Network construction with 1830 PSS operations
Upon completion of this course, you should be able to:
• Use the NMF-T Graphical interface

• Create NE and supervise 1830 PSS WDM and OCS equipment
• Construct a network representing the physical one
Course introduction
OP00090SG01915C - V_Ed1
©
1 Nokia 2018 Nokia Confidential 1
© Nokia 2018 - Nokia Confidential

Learning objectives
Upon completion of this module, you should be able to:
• Describe the general course outline and prerequisites
• Explain how to locate related customer documentation
©

ToC Slide
Table of contents
Introduction 4
Course overview 5
Prerequisites 6
Student introductions 7
Classroom materials 8
Customer documentation 9
Related training NokiaEDU 12
NokiaEDU support 13
Related videos 14
Wrap-up 15
©

Introduction
©

Course overview
OP00090 provides the foundation The intended audience for this

needed to represent a network course are Nokia customers who
construction of 1830 PSS WDM and are in charge of remote
management of network
OCS equipment operations in the constructed by 1830 PSS using
Nokia Network Services Platform NSP NFM-T managed plane
Network Functions Manager for platform.
Transport (NSP NFM-T) OTN managed
plane application.
Important: This course includes only the management of 1830 PSS NEs within a managed plane
environment.
©
NFM-T manages 1830 PSS networks, SDH management for 1830 TDMx (E1)/ DH GW, 1626LM
(R14.2 parity), and 1850 TSS.

Prerequisites
The prerequisites for attending this course are:

• TOP18075W: WDM Technology
• TOP54048W: Optical Transport Hierarchy (OTH) Introduction
• TOP54079W: 1830 PSS Introduction
• TOP54067: 1830 PSS OCS Operations and Maintenance
• TOP30003: 1830 PSS SWDM Operations and Maintenance
• TOP30016: 1830 PSS-4 Operation and Maintenance
• TOP51001: 1830 PSS-8/16II Operation and Maintenance
• TOP54114K: 1830 PSS SWDM Delta
Expected Foundation Knowledge:
• Participants must have knowledge of Wavelength Division Multiplexing (WDM) and Optical Transport
Network (OTN) concepts.
• Participants must have a good working knowledge of 1830 PSS DWDM and OCS products.
©
Optional prerequisite training for L2 services:

• OP00095: NFM-T ESM O&M
Note: WBT and O&M are alternate trainings. TOP30003 or TOP51001 are trainings that depend
on the equipment availability on the network.

Student introductions
Introductions and student information:

• Your name
• Current position and job function
• How long have you worked in the telecommunications industry?
• What is your experience with SONET/SDH, DWDM, CWDM
and Ethernet technologies, routers and related systems?
©

Classroom materials
Review student materials and classroom guidelines:

• Student Guide and customer documentation
• Classroom and lab setup, questions, breaks
©

Customer documentation
How to get information?

OnLine Customer Support (OLCS)
https://support.alcatel-lucent.com/portal/web/support
©
1. The website provides access to the OnLine Customer Support (OLCS) website.
2. You will need a user name and password to access the Order Management and Customer
Support features.
3. Once you have registered, enter your user name and password.

Customer documentation [cont.]
©
10Nokia 2018 Nokia Confidential 10
4. From the Product Information, select the product from the drop-down menu.
5. Select Manuals and Guides.

Customer documentation [cont.]
©
6. Select the Release, manually enter the name of the document, and press the Enter key.
7. On the Search Results screen, click the document link to download the document.
Note: Refer to the NFM-T Administration Guide: Common GUI Functions to get Windows PCs
and server hardware and software requisites.

Related training NokiaEDU
Web-Based Training (WBT) Instructor-Led Training (ILT)
• TOP54048W OTH Overview • OP00091 NFM-T GMPLS Network

• TOP54079W 1830 PSS Introduction construction
• TOP54080W WDM Architecture and • OP00092 NFM-T Provisioning and Network
Hardware Maintenance – managed plan
• TOP54081W OCS Architecture and • OP00093 NFM-T Provisioning and Network
Hardware maintenance -GMPLS L0 (WDM)
• OP00094 NFM-T Provisioning and Network
maintenance -GMPLS L1
• OP00095 NFM-T ESM O&M
• OP00100 NFM-T R 17 to NFM-T R18 Delta
©

NokiaEDU support
Available product training classes, course descriptions, and schedules for most of the products
can be accessed through the following URL:
https://nokialearn.csod.com (Global catalog, search by product)
©
Available product training classes, course descriptions, and schedules for most of the products
can be accessed through the URL displayed on the slide.

Related videos
The related videos for the course OP00090 are:

• How to login and use the graphical interfaces
• Use the EQM
• Create a map
• Create the NE and start the supervision
• Create an example of network construction
©

Wrap-up
In this module we have covered the following items:
• Describe the general course outline and prerequisites
• Explain how to locate related customer documentation
©

NFM-T graphical
interfaces
OP00090SG02576B - V_Ed1
©

Learning objectives
• Describe the interworking and setting of NFM-T applications
• Explain the NFM-T system scope
• Explain how to log in, log out, and start the NFM-T
• Explain the launch of NFM-T applications
• Identify the function of Web-User Interface (WebUI)
©

ToC Slide
Table of contents
NFM-T overview 4
PSS WDM and OCS management 5
High level work flow and related menu 6
Login & logout 7
Preliminary setting 8
Web browser 9
Web desktop 10
Log out from NFM-T 11
NFM-T WebUI 12
Main points 13
Preferences 14
Design 15
Deploy 16
Operate 17
Administer 18
Data tables 19
Overview 20
Data table features 21
Lab exercise 23
Wrap-up 24
©

NFM-T overview
©

PSS WDM and OCS management
The NFM-T Optical Transport Network (OTN) application provides a single network manager
for optical layer (L0) and electrical layer 1 (L1) switching that enables end-to-end
connection setup across WDM/photonic and OCS/switching nodes:
• The managed networks are composed by the 1830 PSS NE family.
• PSS WDM + OCS are seen as a single node (creation and inventory).
1830 PSS-64
OTN/DWDM Core
10GE/40GE/100GE/WDM
1830 PSS-64
1830 PSS-32
1830 PSS-32
1830 PSS-16
1830 PSS-4
WDM 1830 PSS-32
Metro Aggregation
©
The NFM-T OTN, which is an application of the NFM-T, is a network management level
management system that is fully compliant with the ITU-T Recommendation G.709, which is the
Optical Transport Network (OTN) standard for the transparent transport of services over optical
wavelengths in WDM systems.
Operators can configure networks and services, troubleshoot alarms, and execute performance
monitoring for PSS NEs completely within the Managed Plane of the NFM-T OTN.

High level work flow and related menu
Network Supervision
and Node Setup
EML Operator
MENU
Network Construction
NPR
Provisioning on 1830
PSS
OTN
Operation and
Maintenance
EML; OTN
©
The work flow for creating and managing the network from the NFM-T foresees four high level
steps:
1. Network Supervision and node steup (through Commission and Power Balance and
eventually, through Equipment Manager). This step is in charge of the EML.
2. Network Construction step is in charge of NPR.
3. Trails and Services Provisioning step is in charge of new OTN physical connection.
4. Operation and maintenance step is in charge for any operation.

Login & logout
©

Preliminary setting
1.Select the following folder:

C:\Windows\System32\drivers\etc
2.Edit the hosts file
3. Insert the IP address and

hostname of all the VMs
4. Save the file and exit
©
Note: Previous Java versions (for example 1.4) are not supported.
Java 1.7 64-bit or later versions are supported.
Note: Internet Explorer 11 is supported on Windows 7.
To gain full access to the NFM-T options, the PC must be configured so that the NFM-T
applications can be reached using the VM’s hostname. If the Domain Name Server (DNS) is
configured on the PC, it should be configured so that the VM’s hostnames are managed.
If such a configuration is not feasible, the “VM’s hostname”  “IP address” association must
be manually inserted in the following file:
• C:\WINDOWS\system32\drivers\etc\hosts in case the PC runs the Windows operating
system
• /etc/hosts in case PC runs the PC-Linux operating system
• Set “Control Panel  Java  Network Settings” to “Direct connection”
• Select JAVA version R1.7 or 1.8, not both together

Web browser
1. Open a Web browser and type the How to login and
server’s IP address in the address bar. use the graphical
interfaces
©

Web desktop
2.Enter Username and Password,
and then click SIGN IN.
3.Dashboard window
is displayed.
©
The user password is subject to the following constraints:

• A password must not be empty.
• A password must contain uppercase and lowercase characters.
• A password must contain a minimum of one number.
• A password must contain a minimum of one special character, such as the asterisk, *.
• A password must contain a minimum of 8 characters.
• A password must not resemble a string that is similar or the same as the user ID of the user.
• A password must not be repeated.

Log out from NFM-T
Click the icon to log out of the NFM-T.
©

NFM-T WebUI
©

Main points
• The NFM-T WebUI is a web-based user interface that is used to provision and manage
the NFM-T network.
• After logging in, the dashboard is automatically displayed (the default window can be
changed). By clicking on this icon, users can
specify Preferences to customize his
views of the window arrangement.
The provisioning model is
based on the DESIGN,
DEPLOY, OPERATE, and
ADMINISTER phases.
©
The WebUI provides users with a consolidated NML/EML view, simplified provisioning through
the use of templates and layers, an integrated control plane and managed plane, and nodes
(rather than) NEs being main objects.

Preferences
Preferences window can be opened by selecting ADMINISTER  Preferences.
©

Design
• The Design phase enables users to create their own templates to suit the connection
requirements of a particular network site.
• In the Design phase, template creation includes every parameter specification needed to
provision an infrastructure or service except for the variables that make every
connection unique, which include the From/To end point specifications and the names of
the connection and customer.
Connection template
PM Templates
©
User has to select one template already available and save as to create a new one that will be
available in the list of My Template.

Deploy
The Deploy phase enables users to access a template, provide the From/To end point
specifications and the names of the connection and customer, and to make OTN physical
connection, an infrastructure or service connection.
©

Operate
The Operate phase enables users to access the NFM-T WebUI Dashboard, Network Map, and
all the other function for operate the network.
To visualize all
the active alarms
For network and
services provisioning of
different types (1830
PSS, 16x6, L2 services)
For maintenance
network operations
For ASON
network
configuration For Nodes & boards
management
For WDM network

configuration
©
Note: 16x6 nodes are out of the scope of this training.

Administer
The Administer phase includes performing functions, such as setting preferences and logs,
which typically affect other provisioning model phases.
©

Data tables
©

Overview
A Data table is a WebUI structure in which data is systematically displayed, for a

user-requested object, in row and column format, which is referred to as a list.
Physical Connection list Users can view data tables

for a variety of objects
Node list
©

Data table features
Users can mouse over a field in a data
table to view the meaning of the
particular icon, which is particularly
helpful for any graphical indication.
When users mouse over certain column

headings, the system displays buttons
that, when clicked, enable users to
search for a particular named item in
the column.
©
All applied filters can be removed and reset the view to a full, unfiltered list, without going back
through and removing each filter individually.

Data table features [cont.]
Users can click the plus sign that is

located in the upper right corner of the
data table to customize the columns
that are displayed in the data table.
Users can select an item in a data

table, right-click the item, and view
a list of additional NFM-T WebUI
navigation options for that item.
©

Lab exercise
1. Log in to NFM-T with the login credentials provided by the Instructor

2. Go to the Design phase screens and explore the different options
3. Go to the Deploy phase screens and explore the different options
4. Go to the Operate phase screens and explore the different options
5. Go to the Administer phase screens and explore the different options
6. Log out of NFM-T
©

Wrap-up
• Describe the interworking and setting of NFM-T applications
• Explain the NFM-T system scope
• Explain how to log in, log out, and start the NFM-T
• Explain the launch of NFM-T applications
• Identify the function of Web-User Interface (WebUI)
©

NE creation and
supervision
OP00090SG03FE99 - V_Ed1
©
Nokia internal use

Learning objectives
• Create manually the network elements by setting the required parameters
• Supervise the Network Elements
• Delete the Network Elements
©
Nokia internal use

ToC Slide
Table of contents
Creating and addressing 1830 PSS 5

Procedure 6
Network reachability: Connectivity details 7
Network reachability: Examples 8
Communications network IP addressing example 9
Add a Node/NE 10
Configure a managed Node: WDM Node information 14
Configure a managed Node: OCS Node information 15
Node discovery 16
Partner creation for compound NE 17
Configure a 1830VWM 21
Configure a 1830 PSI-2T 23
Configure a 1830 PSD 25
Add an external Node 28
Modify a Node/NE 29
NE supervision and deletion 30
Communication state: NE reachability 31
Ping a Node/NE 32
©
Nokia internal use

ToC Slide
Table of contents [cont.]
Supervision state 33
Starting supervision on a Node/NE 34
Stopping supervision 35
Delete a Node/NE 36
View 360°of the Node 37
Displaying NE attributes 39
Alignment state 40
Node scalability 41
Compound Node 42
Cluster Association 43
NE time and NTP 47
Network time protocol 48
NTP configuration 49
Getting the NE time 50
Setting NE time 51
Add/Remove NTP Servers 52
Lab exercise 53
Wrap-up 54
©
Nokia internal use

Creating and addressing 1830 PSS
©
Nokia internal use

Procedure
Preliminary NE configuration by means of Craft Terminal (CT):

• The System Identifier (SID) of the Local NE must be configured.
• The following IP addresses must be configured in the NE:
− OAMP address and Loopback IP address (together with their subnet masks) in case of Gateway NE.
• All the necessary routing settings must be configured for assuring the network reachability.
EML configuration:
• Preliminary if needed, configure the routing settings necessary to make the NE reachable
from the EML/OTNE:
− Check the EML configuration and process status.
− Create and address the Node.
Refer to NE documentation for the address configuration of a PSS-32 NE and PSS OCS ZIC configuration.
©
Nokia internal use

Network reachability: Connectivity details
-
Optical Supervisory Channel (OSC) connectivity:
• Uses 1510 nm optical channel, multiplexed onto C-Band traffic channels by OSC module on amplifier card
• Provides ~155 Mbps connection between NEs
• Supports OSPF so that full management connectivity is maintained during fiber cut
NFM-T
Static route
through DCN
Inter-NE
Communication (OSC)
DCN
IP
Gateway Network Element (GNE) connectivity:
• Connects to a customer data network through its OAMP port NFM-T
supervises the network through the GNE
• Uses Ethernet cables
• Requires a default route between the NE and the neighbor router
©
Nokia internal use

Network reachability: Examples
NFM-T Client PC
Example 1: Direct connection through the OAMP LAN port:
• Each NE is connected to the management network through the
OAMP LAN port.
• Configure the following attributes on each NE: Example 1
− OAMP IP address
− OAMP IP address mask
− Default router IP address DCN IP 1
DCN IP 2 DCN IP 3
− NE loopback IP address and mask
NFM-T Client PC
Example 2: Single GNE with static route
Gateway NE configuration:
• OAMP IP address and mask
Example 2
• Default route (which is redistributed)
• NE loopback IP address and mask configuration of other NEs
• NE loopback IP address and mask
Router configuration:
• Static route for the NE loopback IP address subnet
Note: In both the examples the loopback IP of the Nodes must be

reachable from EML and OTN instances.
©
Nokia internal use
The OAMP LAN port supports 10/100 Mbps and auto-negotiates accordingly.

Communications network IP addressing example
1830 Node loopback IP 1830 Node GMRE or notify IP
addresses addresses
NMS Server NMS Router 10.10.0.2 10.10.0.3 10.255.0.1 10.255.0.3
152.148.66.xxx 152.148.66.xxx
CIT port
172.16.0.1
NMS Server
Local Craft
GNE Router Node #2 Node #3 PC:
152.148.66.xxx WebUI/CLI
NMS
Client/ DHCP-assigned
WebUI (typically
DCN Router(s)
172.16.0.2)
NMS Client and/or
WebUI
152.148.66.xxx
Node #1 Node #4
Management
Network OAM LAN port
152.148.66.xxx
NTP Server 10.10.0.1 10.10.0.4
152.148.66.xxx 1830 Node loopback IP
NTP addresses
Server
10.255.0.1 10.255.0.4
1830 Node GMRE or notify IP addresses
©
Nokia internal use
Example shows the various IP addresses assigned in the 1830 network for the external
management system.

Add a Node/NE
Create the NE
Users can display a list of created Nodes/Network Elements, managed and start the
supervision
by the NFM-T. 1. From the OTN WebUI,
select Operate  Nodes
Node list
NE list
A Node represents a Network
Element or a group of Network
Elements. A Network Element is
commonly referred to as an NE.
©
Nokia internal use

Add a Node/NE [cont.]
• NFM-T (EML) interacts with the NEs by means of the EML-IM (Information Manager) processes.
• 1830 PSS is managed through EMLIMSNA.
1. Click the Add Node icon ( ).
©
Nokia internal use
EML-IM is a Network Adapter (NA) based on TL1 interface.
Preliminary EML configuration:

• If needed, configure the routing settings necessary to make the NE reachable from the
EML:
− Step 1: Check the EML configuration and process status
− Step 2: Create and address the Node

1. Select the Node type
from drop down 2. If Advanced Node is
selected, the system
displays the appropriate
information
©
Nokia internal use
The external Node represents a Node or a network not managed by the NFM-T. It is used to
create physical connections, path, trails, with Nodes managed by NFM-T.
NFM-T now supports separate TID and user label for 1830 PSS OCS and 1830 PSS PHN NEs. The
user-label can be used as a further description of the TID.
If the node type is simplified, a Node/NE can be created by selecting a template and inserting
address.

3. User has to check:

• PHN (Photonic) for PSS WDM Nodes
• OCS (Optical Core Switching) for OCS Nodes
• Both fields for compound Node
• The system displays the appropriate general information for Node/NE type for your selection.
Check the notes and the next slide for further information on the other fields to be filled.
©
Nokia internal use
Type: Select the 1830 PSS NE that you want to add.

Release: Select the appropriate release number of the Node/NE that you want to add from the
drop-down list.
EML: Select OTNE_1, which is the default domain.
EMLIM: Select the appropriate EMLIM for the Node. If the operator does not select the
supervision area and the EML domain, the above procedure leads to an automatic choice of the
supervision area and EML-IM made by the EML. In this case, the system takes into account each
available “EMLIMSNA” EML-IM trying to make their load homogeneous.
ACD: Select unknown, which is the default.
User Label: Enter a string of characters to identify the Node/NE. The string of characters can be
a combination of alphanumeric and special characters. The system checks the maximum length
of the user label and prevents duplication. The 1830 PSS OCS and 1830 PSS PHN NEs support a
maximum of 20 characters in the User Label.
Location: Enter a string of characters that identifies the geographic location where the Node/NE
resides.
Shared User Name: Check or uncheck the shared username field. If you check it, the system
activates the user name and password fields for both PHN and OCS NE.

Configure a managed Node: WDM Node information
Secondary address (optional) Loopback IP address
Add partner address (OCS Node

address) in case of compound Node V2C SNMP Version
V3 SNMP Version
Click Create to complete the procedure

©
Nokia internal use
Address: Enter an IP address for the PHN Node/NE.

Partner Address: Enter the address of the OCS Node/NE that is partnered with the PHN
Node/NE, in case of compound Node. In case of stand alone WDM, add 0.0.0.0.
User Name: Enter a name to be used to access the Node.
Password: Enter the password to be used to access the Node.
SNMP Version:
• If the SNMP Version is V2C, in the Read Community and Write Community, enter the
appropriate private information by typing over the security dots.
• If the SNMP Version is V3, the security level field is automatically set to authorization privacy
(communication with authentication and privacy).
USM user: The USM user (user-based security model) provides authentication and privacy
(encryption) functions and operates at the message level. Select v3DefaultUser, which is the
default.
USM authentication password: Enter the appropriate private information by typing over the
security dots.
USM privacy password: Enter the appropriate private information by typing over the security
dots:
• Authentication method: Select a method from the drop-down list. Options are HMAC-MD5
(the default) or HMAC-SHA. HMAC is a keyed-hash message authentication code. MD5 and
SHA are cryptographic hash functions that can be used to calculate an HMAC; the MAC
algorithm is called HMAC-MD5 or HMAC-SHA.
Privacy Method: Select a method from the drop-down list. Options are AES-128 (Advanced
Encryption Standard, the default) or AES-256.

Configure a managed Node: OCS Node information
Add partner address (WDM Node

address) in case of compound Node
Click Create to complete the procedure
©
Nokia internal use
Target Identifier (TID): Specify the TID for the Node/NE being added.
Address: Enter an IP address for the OCS Node/NE.
Partner Address: Enter the address of the WDM Node/NE that is partnered with the OCS
Node/NE in case of compound Node. Enter 0.0.0.0 in case of “stand alone” OCS Node.
User Name: Enter a name to be used to access the Node.
Password: Enter the password to be used to access the Node.
Secure Communication (TL1): Select none or SSH2 from the drop-down list. If Secure
Communication (TL1) is SSH2, the system activates the Public Key field.
Public Key File: Select DEFAULT, which is the default, from the drop-down list.

Node discovery
2. Under Best Practices select a node, right

click the template and select Network Scan
1. Select Deploy  New Nodes
3. Fill the details, From IP and To IP.

4. Select Deploy.
©
Nokia internal use
The node discovery using NFM-T is enhanced with the introduction of scan a range of IP address
for the nodes. In this method, the user can enter the start and end of a range of IP addresses.
All the nodes in the range are checked. The nodes that match the parameters in the chosen
node template are added and the nodes that do not match are rejected.

Partner creation for compound NE
1 2 3 4
Stop Set Partner NE Start NEs
Create Partner NE address Supervision
Supervision
©
Nokia internal use

Partner creation for compound NE [cont.]
1 Stop Supervision 2 Create Partner NE
1. From the EML NE list, select the

supervised NE and right-click
Supervision  Stop
2. From the EML NE list, select

the supervised NE and
right-click Modify Node
It is necessary to stop the supervision of already supervised NE (PHN in this example) to allow the address setup update.
©
Nokia internal use

Window obtained from the EML NE list by
3 Right-clicking one of the two compound
Set Partner NE address NEs  Modify Node
Fields automatically
populated by the NE
3. Change Partner IP
Address from 0.0.0.0 to
the just added NE
address
4. Click Modify
©
Nokia internal use
Set Partner NE Address notes:

• Partner NE Address window can be launched by one of the two NEs: Updated address will
be applied on both companion NEs.

Start NEs From the EML NE list, select the

4 Supervision supervised NE and right-click
Supervision  Start
©
Nokia internal use

Configure a 1830VWM
2. From Node Type,

select Advanced
3. From Type, select 1830VWM
©
Nokia internal use

Configure a 1830VWM [cont.]
4. Select release and add name
5. Enter the required fields 6. Click Create
©
Nokia internal use

Configure a 1830 PSI-2T

2. From Node Type,
select Advanced
3. From Type,
select 1830PSI-2T
©
Nokia internal use

Configure a 1830 PSI-2T [cont.]
Select release and add name
Enter the required fields
Click Create
©
Nokia internal use
Type: Select the 1830 PSI-2T in this case.

Release: Select the appropriate release number of the Node/NE that you want to add from the
drop-down list.
EML: Select OTNE_1, which is the default domain.
EMLIM: Select the appropriate EMLIM for the Node. If the operator does not select the
supervision area and the EML domain, the above procedure leads to an automatic choice of the
supervision area and EML-IM made by the EML.
ACD: Select unknown, which is the default.
Name: Enter a string of characters to identify the Node/NE. The string of characters can be a
combination of alphanumeric and special characters. The system checks the maximum length of
the user label and prevents duplication.
Location: Enter a string of characters that identifies the geographic location where the Node/NE
resides.

Configure a 1830 PSD
From Node Type, select Advanced 1. Click the Add Node icon ( ).
From the Type list,

select the 1830PSD
Enter the required fields
Click Create
©
Nokia internal use
The PSD release R1.0 has to be supported for all domains (EML, OTN, Alarm management, PM, EQM, and ESM).

Configure a 1830 PSD [cont.]
Right click on node and select Enter the Click Submit

Configure SSH and SNMP required fields
©
Nokia internal use

Configure a 1830 PSD [cont.]
After clicking Submit,

Operation status will change
©
Nokia internal use

Add an external Node
1. From drop down select External
2. Enter the appropriate

information and click Create
to complete the procedure
©
Nokia internal use

Modify a Node/NE
1. Select a Node
or NE in the list 2. Right click on Node and select
Modify Node (or click the icon)
If the Node is not Supervised:

• The majority of attributes can be changed (but not Node type, release, and EML/EMLIM)
• In case of Single NE (PHN or OCS) Node, user can add the companion NE, to create a
Compound Node
If the Node is Supervised:

• Location and TID can be modified and/or comments can be added
©
Nokia internal use
Note: In case of “Multi NE (Compound)” Node, you can only modify the location and TID and/or
add comments.
In case of “Single NE (PHN or OCS)” Node, you can add the companion NE or TDMXC/XC.

NE supervision and deletion
©
Nokia internal use

Communication state: NE reachability
NFM-T EML has lost
communication with
the equipment
UNREACHABLE
REACHABLE
NFM-T The equipment can

be reached by the
EML
©
Nokia internal use
Communication states:
• Unreachable: The communication between the OS and the NE is interrupted.
• Reachable: The OS can communicate with the NE.
• Undefined: The address hasn’t yet been assigned to the NE.

Ping a Node/NE
1. Select a Node
2. Right click and select

Ping Node(s) (or click
the Ping Node(s) icon)
©
Nokia internal use

Supervision state
It’s possible to supervise a Node/NE only if it:

• Has been created
• Is reachable: Has been given the address and all the required DCN parameters
Starting
DECLARED supervision
TRANSIENT TRANSIENT
(deactivating) (activating)
Stopping
supervision SUPERVISED
Stable states Transient states

©
Nokia internal use
Supervision state:
• Declared: The NE is simply created in the OS MIB but is not supervised.
• Supervised: The NE is under supervision.
• Activating: Supervision is being started (no management task can be performed on the NE).
• Deactivating: Supervision is being stopped (no management task can be performed on the
NE).

Starting supervision on a Node/NE
Start supervision:
• Starts the management of the selected Node/NE
2. Right click and select Supervision
• Activates alarm collection and configurations  Start (or click the icon)
1. Select a Node
or NE in the list
©
Nokia internal use
After supervision is started, the “Supervision” state attribute changes from a gray down arrow
to a green up arrow on the Node data table.

Stopping supervision
Stop supervision stops managing the selected Node/NE:

• Deactivates alarm collection and configurations
Right click and select Supervision

 Stop (or click the icon).
©
Nokia internal use
If the stop supervision command is successful, the “Supervision” state changes from green up
arrow to a gray down arrow on the Node data table.

Delete a Node/NE
To delete a 1830 PSS Node:

1. Stop the NE supervision
2. Right-click the Node  Delete Node
©
Nokia internal use

View 360°of the Node
A 360° view is all of the information that is related to a particular Node, presented as a set
of user-selectable tabs, directly below the data table of the selected Node.
1. Select a Node
2. Click one of the

displayed tabs
©
Nokia internal use

View 360°of the Node [cont.]
To check the reachability of the NEs, check the “Communication State” value:de
Selecting a Node displays

the NE status at the
bottom of the window
The “Alarm Synthesis” state indicates the most critical alarm present on the NE:
• Critical; Major; Minor; Warning; Cleared (no alarm)
• Indeterminate (the severity level cannot be defined by the resources that raise the alarm)
©
Nokia internal use

Displaying NE attributes
From the NE list, selecting the “i”
icon displays all the information
about the selected item.
©
Nokia internal use

Alignment state
Stable states = NFM-T
MIB
Transient states
ALIGNED
MIB
ALIGNING UP
NFM-T
MIB
NFM-T
MISALIGNED

MIB NFM-T
©
Nokia internal use
Alignment state:
• Misaligned: The NE MIB and its image in the OS are not identical. Typically, the NE is in this
state when:
− The Supervision state is “Declared”
• During the alignment phase (Aligning up, down, or auditing), the shown Alignment state is still
“Misaligned”. It turns into “Aligned” when the alignment phase is finished.
• Aligning Up: The system is performing a “MIB Align Upwards” operation. No operation can be
done on the NE.
• Aligned: The system becomes aligned when all the operations for synchronizing the EML with
the NE are fully completed. The synchronization procedure involves the alarms, the PM and
NE.

Node scalability
©
Nokia internal use

Compound Node
A Compound Node is a configuration that includes the user partnering of 1830 PSS OCS
NEs and 1830 PSS PHN/WDM NEs through the use of uplink cards.
1830 PSS has enhanced the “Compound” configuration to allow PSS NEs scalability and
more flexible configurations. The possible configurations are:
• Multiple SWDM NEs in Compound
• One SWDM NE with three OCS NEs
Compound Node
©
Nokia internal use
Note: Uplink Card Management (UCM), allows the 1830 PSS NE to directly control optical
characteristics (frequency, wave keys, dynamic power levels) of 1830 PSS OCS uplink ports as
needed in order to integrate uplink channels into WDM lines on three 1830 PSS OCS NEs.

Cluster Association
Cluster Association is a NFM-T concept that is used to affiliate one NE with another when
the NEs are configured in a Multi-NE Cluster.
With configurations such as those that include multi-slot 100G Optical Transponders (OTs),
a 24-shelf NE might not have enough room for OTs to fill 8 degrees. To promote scalability
and flexibility in such configurations, the NFM-T supports the Multi-NE Cluster feature for
1830 PSS NEs.
With Multi-NE Clusters, multiple 1830 NEs at a single site are associated in a cluster.
©
Nokia internal use

Cluster Association [cont.]
To add a cluster association on an NE, choose the Node  Modify Node
1. Check the Cluster Association,

Associated NE(s) tab appears
©
Nokia internal use

2. Choose Associate NE(s) 3. From drop down menu, select

the relevant NE to be associated
4. Click Modify
©
Nokia internal use

5. Cluster Associations can

be found under the tab
©
Nokia internal use

NE time and NTP
©
Nokia internal use

Network time protocol
NTP: Synchronizes the date and time of the NEs with a time source that typically is the
server hosting the NFM-T.
NTP configuration:
• In NFM-T:
− NTP must have been enabled during NFM-T installation.
• In NEs:
− NTP is automatically activated upon NE supervision.
− The NFM-T EML or OTNE server’s address is used as Main NTP Address.
Reminder: The date and time shown in the WebUI are same as the PC’s date and time.
©
Nokia internal use
Note: The NFM-T realigns the time of all the supervised NEs every 24 hours by default.

NTP configuration
Right-click the NE and select Configure  Configure NTP

Note: If NTP is already enabled the “Apply” option is gray
1. Check the IP address of the

NTP server on the NTP IP tab
3. Click Apply
2. Set to Enabled
©
Nokia internal use
When working with 1830 PSS, make sure no NTP servers have been configured by the local craft
terminal operator. If it is so, then remove the manually configured NTP servers.

Getting the NE time
1. From Nodes tab
2. Right click NE and select

Configure  Get Time
©
Nokia internal use
This operation is allowed only if the NE is under supervision and its NE reachability state is
Enabled.

Setting NE time
To manually align the NE time to the OS time
1. Same as Previous
but select Set Time 2. Click YES
©
Nokia internal use
This operation is allowed only if the NTP is configured as Disabled.

Add/Remove NTP Servers
To add a new NTP Server to the NE
1. Go to Administer  Configure NTP
2. Add or Delete the IP

Address of the NTP
server and click Save
©
Nokia internal use
To remove an NTP Server, highlight it and click Delete.

Lab exercise
The instructor assigns participants into four groups:
1. Log in to NFM-T with the login credentials provided by the instructor.

2. Create the assigned NE for your group.
3. Start supervision on the NE you created.
4. Explore the 360° view of your assigned NE.
©
Nokia internal use

Wrap-up
• Create manually the network elements by setting the required parameters
• Supervise the network elements
• Delete the network elements
©
Nokia internal use

Nokia internal use

EQM and Map creation
OP00090SG042FCF - V_Ed1
©

Learning objectives
• Check and manage 1830 PSS through Equipment Manager
• Create a network topology map using WebUI
©

ToC Slide
Table of contents
Equipment Manager 5
Purpose 6
Launch Equipment Manager 7
Main window: Overview 8
Inventory: Equipment details 9
Alarms: Inventory and AS navigation 10
Equipment view and EML NE WebUI navigation 11
Shelf provisioning 12
Card provisioning 13
Ports provisioning 14
Port details 15
Internal Cable 16
Auto Refresh 17
Checking part number 18
WebUI map creation 19
WebUI map features 20
Network Map basic 21
©

ToC Slide
Subnetwork and node management 22

Subnetwork creation 23
Add a node to the subnetwork 24
Node information in pop-up 25
Highlight an object 26
Remove a node from the subnetwork 27
Customize view 28
Top toolbar 29
Overlays 30
Right-click: Further actions 31
Lab exercise 32
Wrap-up 33
©

Equipment Manager
©

Purpose
•
The Equipment Manager (EQM) provides the following functionalities on multiple sets of defined Network
Elements (NEs):
• Inventories of:
− Hardware equipment (shelf, cards, ports, and pluggable module)
− Alarms affecting NEs
• Navigation toward:
− Alarm surveillance
− NE ZIC
• Provisioning of:
− Shelf, cards, ports, signal types, and pluggable modules
EQM is applicable to 1830 PSS NE types:

• 1830 PSS SWDM
• 1830 PSS OCS
• 1830 PSS-4
• 1830 PSS TDMX
©
SWDM NE includes 1830 PSS-32, 1830 PSS-24X, 1830 PSS-16II, 1830 PSS-16, and 1830 PSS-8
shelf types.
OCS NE includes 1830 PSS-64 and 1830 PSS-36.

Launch Equipment Manager
Use the EQM
Select Operate 
Equipment Manager
©
Note: The application is supported by Equipment Manager (EQM) server process of Network
Services Platform (NSP) NFM-T-EML that enables users to display the equipment details along
with port and alarm information. In addition, the Equipment Manager enables users to provision
Network Element (NE) shelves, slots, cards, ports, signal types, and pluggable modules.

Main window: Overview
Search filter and related 1830 PSS list in the tree structure. The operator can expand Details of the selected
the list having related shelf/cards/ports sublists. You can click the Refresh button to get Network Element
a new NE defined.
Refresh button
Alarms synthesis grouped
Alarm, Inventory, and by severity/navigation
Configuration tabs buttons
Shelf graphical
representation
©

Inventory: Equipment details
EQM Window You can click the Port Details tab to display ports available
in the selected node and other related details.
You can click the Equipment

Details tab to display shelf
available cards and the
related details.
Click the ( ) icon to get additional

attributes on cards or ports.
©
Note: NFM-T will support the Forced APR as well as return to normal for the RA2P and A2P2125
amplifiers. This is done by allowing the user to initiate a Force APR on the pack from the EQM
screen.

Alarms: Inventory and AS navigation
EQM window
You can click the ( ) button to open the
Alarm Surveillance (AS) window providing
filtered alarms list of the selected NE.
The Alarms tab displays the list of

active NE alarms and related details.
Note: The navigation toward

ShowEquipmentManager window is also
supported by the AS list.
Window  External Applications 
ShowEquipmentManager
©
The user is able to add descriptions to the card/port in EQM and this information is now sent to
the NE.
The PSS NE supports the addition of user labels against the cards and ports. During connection
discovery, this information is pulled from the NE and displayed against the card/port in the
connection tree.

Equipment view and EML NE WebUI navigation
The operator can expand the NE on the left side You can click the ( ) button to
list to see related shelf/cards/ports sublists. navigate toward the selected NE WebUI.
Icon ( )
shows the
OLCState
You can select shelf/cards on the left side list to open the graphical representation in the central part of the
EQM window.
©
Object Life Cycle State: Maintenance activities on an NE can evoke many alarms. The OLC
(Object Life Cycle) state of an object indicates whether the object is in service or maintenance.
The user can filter out alarms based on the OLC state of an object.

Shelf provisioning
Provisioning History: Displays the
history of configuration command
setup by the current EQM session
plus the related results.
After provisioning new subrack, the Provisioning

History will show the details of the subrack created.
©
Note: In case for removing a shelf, select the shelf on the left side list and click Delete under
Configure tab.

Card provisioning
2. Fill in card type and

other parameters, and
1. To provision a new PSS then click Create.
card, select the slot on the
left side and click the
Configure tab.
Once the operation is successfully terminated, the new port is available in NE
WebUI. Refresh the list to get updated the EQM view.
©
Note: To remove a card, change the Primary State setting to Out Of Service, and then remove
it. A confirmation will be requested by the system before the card is removed.

Ports provisioning
1. To provision a new PSS port, select the port

on the left side and click the Configure tab.
2. Fill in port parameters

Once the operation is successfully terminated, the new port is configured and is available in and click Modify.
the NE WebUI. Reload the list to get the updated EQM view.
©

Port details
1. Open the EQM and click the

desired shelf.
2. Choose the Port Details tab.
©

Internal Cable
Through the EQM you can check the Internal Cable Display of the relevant node. In case of
any cable, the tab will show the details as shown below:
©

Auto Refresh
To enable Auto Refresh: Preferences  Enable Auto Refresh
©
In NFM-T R.18, EQM has automatic refresh based on events from the network elements for user
provisioning activity/command, shelf/packs creation and deletion, port signal rate
creation/deletion. This will allow near real-time update of the specific screens of the EQM.

Checking part number
To check the part number of card Open the EQM and click the desired shelf  Equipment Details  Equipment Attributes
©

WebUI map creation
©

WebUI map features
- user to create or let the system auto-discover the physical connectivity
between nodes of the managed network
NFM-T provides the following features:
• -Network
Graphical object
topology management:
partition: Enables the userEnables
to organizethe
theuser to by
network move onsubnetworks
creating the mapsandthe
icons representing the network’s objects. The object position can then be
assigning nodes to them
fastened
• Link or unfastened
creation: Enables on the
the user to create maps
or let the system auto-discover the physical connectivity
between nodes of the managed network
• -Graphical
Alarmobject
status propagation:
management: EnablesIcon color
the user determined
to move on the maps bythe
the most
icons severethe
representing
alarm affecting its subtended objects
network’s objects. The object position can then be fastened or unfastened on the maps
• Alarm status propagation: Icon color determined by the most severe alarm affecting its subtended
-objects
Shortcut to queries or actions: Enables the user to retrieve lists or
perform
• Shortcut commands
to queries or actions:on the the
Enables network’s objects
user to retrieve lists from pop-up
or perform menus,
commands on the
available
network’s by from
objects right-clicking
pop-up menus,theavailable
related icons
by right-clicking the related icons
©
A map is a graphical view where the network’s objects, such as subnetworks, nodes, and links,
are represented by graphic symbols (icons).
Maps are shared among all the management applications, which are EML and OTN.

Network Map system
- The basic a utomatically instantiates a ROOT network that recursively
Create a map
contains all the subnetworks created by the users.
Staging Area: All
of the NEs that
are not assigned The tree lists all
to any user subnetworks that are in the Users can move the Network Map by
created particular optical network. putting the pointer on any location on
subnetwork are the map, clicking, and dragging the map.
displayed in the
Staging Area.
ROOT
network
Subnetworks can be
added to ROOT.
Subnetworks,
recursively
contained in
ROOT
©
To access the Network Map click Operate  Network Map.

Interconnecting links between NEs are not displayed in the Staging Area.
Interconnecting links are automatically displayed when both end NEs are placed (or moved) to
the right side of the Network Map.
When all links are made visible in the Map, they support the same management functions
normally available with a single link (alarms, navigation to 360 degree). This feature is required
only for PHN physical layer that is OTS.
The network map supports a double click on a Node to open an Equipment view of that Node.

Subnetwork and node
management
©

Subnetwork creation
Right-click on the map panel and
select Create Subnetwork.
Enter the required parameters

and click OK.
The new object is added to the map.
©

Add a node to the subnetwork
Different icon identifies the

Select a node from Shelf type:
the Staging Area.
SWDM and cluster
Compound
Drag and drop the node.
©

Node information in pop-up
Users can move the pointer
over a selected node or a
parent subnetwork to
display detailed information.
By right-clicking the item and

selecting Details, the same detailed
information is displayed.
©

Highlight an object
Users can click any object that is

at the subnetwork level on the
left side of the Network Map to
view its placement on the right
side of the Network Map.
©

Remove a node from the subnetwork
1. Right-click the node and select

Remove From Map.
2. Click Yes to confirm.
©

Customize view
©

Top toolbar
The top toolbar of the Network Map enables users to customize their view of the Network
Map in various ways. Users can move the pointer over each icon to determine its meaning
or access each drop-down list for options. Expand/collapse tree
Go UP one level Refresh
Information Go to the next <Name>

subnetwork Reset highlighting Increase
view size icon
Go to the previous Physical layer Decrease size icon

subnetwork view
©
Physical is a drop-down list that enables users to view the physical layers of the Network Map in
the named layers that are listed.
100 is a drop-down list that enables users to increase or decrease the size of the Network Map
in the percentages that are listed.
<NAME> enables users to locate an NE/node on the Network Map.

Overlays
Users can view which overlays are currently being displayed on the Network Map by clicking
the plus ( ) sign in the upper right corner of the Network Map.
By checking or unchecking
the boxes for each
overlay, users can
customize their view of
the Network Map.
©

Right-click: Further actions
Users can right-click any object on the tree or on the Network Map to access further actions
for that particular object.
Example: Right-click options for a node.
©

Lab exercise
• Log in to NFM-T with the login credentials provided by the Instructor.

• Explore the Equipment Manager options as indicated in this module for the NE your
group has created.
• Log out of NFM-T.
©

Wrap-up
• Check and manage 1830 PSS through Equipment Manager
• Create a network topology map using WebUI
©

Network construction
OP00090SG05A960 - V_Ed1
©

Learning objectives
• Explain how to create OS and OTS WDM node internal links
• Explain how to create OS and OTS physical connections
©

ToC Slide
Table of contents
Network construction overview 4

PSS managed plane network 5
NFM-T network construction 6
Network construction setup 7
Managed plane network setup: Work flow 8
Physical link types: Internal links (on PSS WDM) 9
Physical link types: Physical connections 10
PSS WDM internal links 12
Exercise sheet: Training network 13
PSS WDM internal connectivity: NMS automatic creation 14
PSS WDM internal connectivity: NMS user creation 15
PSS WDM internal connectivity: Checks 17
PSS WDM internal connectivity: Operation 18
PSS WDM Internal connectivity: Pluggable ports 20
PSS 24x internal connectivity: NMS user creation 23
PSS 24x internal connectivity: Checks 25
OTS physical connections 26
OTS physical connections: NMS discovery 27
Create OTS physical connections 28
OTS physical connections 29
OTS Routing Display 33
Photonic network map representation 34
OS physical connection 35
OS physical connections creation 36
Lab exercise 37
Wrap-up 38
©

Network construction overview
©

PSS managed plane network
L1 Layer
Legend
1830 PSS 36/64
L0 Layer
1830 PSS
8/8x/16II/16/32/24x
Managed plane network 1
(Example 1: Network with PSS WDM and OCS)
1830 PSS 4
1830 WDM/OCS
Compound Node
1830 PSS 4 L0 Layer
Managed plane network 2
(Example 2: Pure photonic network with PSS WDM)
NFM-T-OTN support managed plane networks:
• 1830 PSS 24x/32/16/16II/8x/8 and 1830 PSS 4 (Photonic/L0 layer)
• 1830 PSS 36/64 (Electrical/L1 layer)
• 1830 PSS WDM/OCS Compound Node
©

NFM-T network construction
NSP NFM-T
OTN
ASON ESM
1830
NML Layer
OTNE
PSS
EML Layer EML

OTNE embeds Further
EML and GUI applications,
functionalities optionally installed
Client GUI
The NFM-T-OTN is the application in-charge of path provisioning in the managed plane networks:
• The operator can access the provisioning functions (both for Trail and Services) through the Deploy  New
Service/Infrastructure Connection.
• The operator can view the provisioned trails through Operate  Infrastructure Connections and the provisioned
services through Operate  Services.
©
The management layers functions are accomplished by a set of different "applications”.

The Element Management Layer is implemented by the EML application. It provides functions
such as NE creation, SW download, NE data backup/restore.
EML is needed only in the following cases:
• Non 1830 PSS NEs: Legacy NEs, PTN NEs and all other kind of NEs.
• Largely only PSS networks not fitting with OTNE capacity or configurations with multiple
EMLs coming from previous releases.
The Network Management Layer is implemented by:

• ESM for the data technologies, such as Ethernet, T-MPLS, CES (Circuit Emulation Service) in
some equipment.
• OTN for the SDH & WDM technology and the OTN technology in 1830 PSS equipment and
further WDM nodes.
• OTNE (OTN plus EML) in case of only PSS network, which embeds also EML and GUI
functionalities.
GUI (Graphical User Interface) is needed only in the following cases:

• HA: For pure 1830 PSS networks, two GUIs applications are needed one on NOC and one on
DRC. For other cases, ore or more GUIs are needed on both NOC and DRC according to
dimensioning rules.
• Non 1830 PSS NEs: Legacy NEs, PTN NEs and all other kind of NEs are managed through
MSGUI component which GUI Server runs on GUI application. One or more GUIs are needed
on both NOC and DRC according to dimensioning rules.
ASON Manager is the component in charge to manager OTN Control Plane networks.

Network construction setup
©

Managed plane network setup: Work flow
DCN configuration to make the nodes reachable from EML

NFM-T EML preliminary
1
steps
All PSS NEs supervised by NFM-T-EML and nodes available in the

map
2
All cards configured on the NE (through local connection or

through equipment management). All available ports uploaded
3 (run synchronize node, in case necessary)
Synchronize  Full from

Physical connectivity to be node list of Web GUI
4 created
CPB will setup the
network according to
the Plan file Two types of connections:
(commissioning file Run Commissioning
Power Balancing (CPB) • OS (internal or external)
from EPT or NPT) • OTS (internal or external)
©
To check all the available port lists, select Node  Free Ports tab.

Physical link types: Internal links (on PSS WDM)
4 Create physical connectivity
Internal Optical Section (OS): Physical fiber connection within the Wavelength Division Multiplexing (WDM)
NE having only one lambda or B&W, for example:
• PSS-32 OT line port – SFD/CWR
• PSS-32 11DPM12 line – 112SCX10 Client (B&W connection)
Internal Optical Transmission Section (OTS): Physical connections within the WDM NE containing multiple
lambda, for example:
• CWR SIG port – LD SIG port
• ITLB OMD port – CWR OMD port
Both Internal OS and Internal OTS can be created through:
• CPB is a preferred solution during system provisioning, then internal links automatically uploaded into NFM-T-OTN.
• NE WebUI during the local NE configuration, then internal links automatically uploaded into NFM-T.
• NFM-T during manual user NMS network setup through EQM by choosing Operate  Equipment Manager
To get the list of Internal links from the OTN node tabbed view, select Impacted connection table or Internal Links
list from EQM.
©
OS is sometimes also called Optical Physical Section (OPS).

The Internal Links list of EQM does report some additional links, with respect to
the NFM-T OTN list, such as OTS between amplifiers SIG ports or OTS between CWR THRU
ports.

Physical link types: Physical connections
External Optical Transmission Section (OTS): Physical connection between two different PSS
WDM nodes containing multiple lambda:
• The external OTS can be created:
− Automatically by NE when it detects a valid signal from the neighbor NE or through NE WebUI during the local NE
configuration, then discovered in NFM-T by selecting the Node  Discover External Physical Links (preferred
solution).
− From NFM-T, choose Operate  Physical Connections view, click Create
icon ( ) during manual user NMS network setup or select Deploy  New OTN Physical Connection.
• At OTS implementation, the corresponding OMS trail is automatically created by the system.
©

Physical link types: Physical connections [cont.]
External Optical Section (OS): Physical connection between two different nodes carrying
B&W connections, for example:
• External NE: WDM OT client side port (User Network Interface (UNI) or Network to Network Interface
(NNI) type):
− The External OS physical connection is manually provisioned by the NFM-T user through the Create icon ( ) in
physical connection lists or by selecting Deploy  New OTN Physical Connection.
− The corresponding OTU trail is automatically created by the system for the NNI connections.
• To get the list: Operate  Physical Connections or OTN Physical connections tab in each node
tabbed view
©

PSS WDM internal links
©

Exercise sheet: Training network
OCS
Node 1 Node 4
1-15 1-2
OCS 154 #OCS PHN PHN
2-3
2-2
1-2
PHN PHN
1-14 1-15
PSS OCS
Node 2 Node 3
OCS
OCS
PHN PSS WDM

OCS 157 #OCS
©
There are four 1830 PSS WDM nodes connected in ring network. By using these WDM nodes we
would create the following:
1. 1830 PSS WDM internal connectivity
2. OTS physical connections
3. OS physical connections creation
There are two ways to perform these tasks, manually or automatically.

PSS WDM internal connectivity: NMS automatic creation
Create an example of
network construction
In case internal connectivity has been set up on the NE (through CPB or NE WebUI), it is automatically uploaded
on NFM-T-OTN.
To check the internal connectivity list: Operate  Nodes, select node. In the tabbed view,
choose Impacted Connections. Impacted connection list
Check Type equal

to Physical Link.
Internal links are also available in EQM, selecting WDM shelf on the left and Internal Links tab.
©
In case some internal connections are missed, run Synchronize Internal Links:
• Select Node, right-click  Synchronize  Internal Links.

PSS WDM internal connectivity: NMS user creation
In case internal connectivity is not yet configured, the user can create it from NFM-T EQM.
Lab: Create an internal link between an 11STAR1 OT port and SFD filter port.
In case internal connectivity is not yet configured, the user can
create it from NFM-T EQM, Operate  Equipment Manager
SFD
OT
1. On the left side of the window, select /CWR AMP
the WDM shelf hosting the OT to be
connected to the filter port. 2. Choose Topology view.
3. Select the OT Line port.
Selected port is also

reported here. Click Clear to clear port selection.
©
The create internal link between OT port and SFD filter port is applicable for all the Optical
Transponders having integrated ports (such as 11STAR1, 40/100 Gb OTs and so on).

PSS WDM internal connectivity: NMS user creation [cont.]
4. On the left side of

the window, select
the SFD shelf
hosting the filter
port to be 5. Select the filter port.
connected to the
OT line port.
6. Select the Bi-Directional button.
7. Select Create to send

create request to NE.
©

PSS WDM internal connectivity: Checks
Once internal link is created
Operation result ▪ The Operation result report appears.
▪ The Internal Links list in EQM is updated.

EQM Internal Links tab
Tabbed view Impacted Connections from Node list ▪ The Node Impacted Connections list is updated.
©

PSS WDM internal connectivity: Operation
Check the operations available on the internal OS from the Impacted connection list. Select Physical link
and right-click. The following operations are supported:
Routing Display: To navigate towards routing graphical representation

©

PSS WDM internal connectivity: Operation [cont.]
• Deployment control (DB Remove or DB Remove Connection and Clients): To force removal of the link in the NFM-T
system
• Remove connection with clients: To remove the link and related client resources
• Remove connection: To remove the link
• Modify PM/Report Profile Association/PM report: To modify/see Performance Monitoring setup and data
©

PSS WDM Internal connectivity: Pluggable ports
Lab: Create an internal link between an OT having pluggable ports and filter port
VA1 Line1 port
A or Z Node
Internal Link creation from EQM for pluggable
ports: Operate  Equipment Manager
SFD/
CWR
11DPM12
2. Choose Topology View.
3. Select the OT Line port.

1. On the left side of the
window, select the
WDM shelf hosting the
OT to be connected to
filter port.
©

PSS WDM Internal connectivity: Pluggable ports [cont.]
5. Select the filter port.
4. On the left side

of the window,
6. Select the
select the SFD
Bi-Directional button.
shelf hosting
the filter port to
be connected to
OT line port.
7. Select the following parameters:

• Signal Rate
• Include VA
• Choose VA port
8. Click Create.
©

PSS WDM Internal connectivity: Pluggable ports [cont.]
After link creation
Two unidirectional links are

available in the EQM Topology
view and Internal Links list.
One Physical Link is

displayed in the
Impacted Connections
tab of the Node.
©

PSS 24x internal connectivity: NMS user creation
Lab: Create an internal link between an 4UC400 port and CWR filter port.
In case internal connectivity is not yet configured, the user can create it from NFM-T EQM.
Operate  Equipment Manager…
SFD
UC
/CWR AMP
2. Choose 3. Select the Uplink Line port.

Topology view.
1. On the left side
of the window,
select the WDM
shelf hosting
the OT to be
connected to
the filter port. Selected port is also
reported here.
©
This lab is applicable for both the Uplink cards of the PSS-24x: 4UC400, 2UC400.

PSS 24x internal connectivity: NMS user creation [cont.]
5. Select the filter port.
4. On the left side of

the window, select
the SFD/CWR
shelf hosting the
filter port to be
connected to the
OT line port.
6. Select the Bi-Directional

button.
7. Select Create to send

create request to NE.
©

PSS 24x internal connectivity: Checks
Once internal link is created
Operation result • The Operation result report appears.
EQM Internal Links tab • The Internal Links list in EQM is updated.
Tabbed view Impacted Connections from Node list• The Node Impacted Connections list is updated.
©
Note: 130SCUPH is designed to interwork with 1830PSS-24x 4UC400. 130SCUPH is supported in

the following configurations:
1. Interworks with 1830 PSS-24x 4UC400 using U-SDFEC
2. Interworks with 130SCUPC and other 100G SWDM OTs using HDFEC or AFEC only
3. Used in Colorless ROADM configurations as a generic uplink thanks to improved TX OSNR
performance with respect to 130SCUPC
4. Supported in managed plane and L1 GMPLS

OTS physical connections
©

OTS physical connections: NMS discovery
Lab: Discover OTS physical connections.

In case the PSS WDM – PSS WDM connectivity has been already set up on NE, links can be discovered
by NFM-T. To discover the OTS physical connections in WDM network:
• Select Node, right click  Discover External Physical Links (OTN).
• Operate  Physical Connections
The label is automatically created using the connected amplifiers.
Implementation Status when the physical connection is implemented:

• The corresponding connection is set up in the NE (when applicable; for Commissioned Status:
example, for OTS, no connection is set in the NE since it is normally already • When the physical connection is
present). implemented:
• The correspondent Client Link Connection is created by the system and − Equal to Not Commissioned if Power
eventually, client objects are discovered (NFM-T trail for OTS connections). Adjustment not yet run
©
In-service state is an administrative state that allows to filter alarms only for in-service
transmission objects.

Create OTS physical connections
In case the connectivity is not yet configured, user can create it from NFM-T.
In case the connectivity is not yet configured, user can create it from NFM-T.
From Deploy  New OTN Physical Connections or
From Operate  Physical Connection, click Create icon
1. Manually enter
User Label 2. Connection type = Bidirectional
(check notes for further values)
3. Choose OTS
4. Select the A End Point

node (filter is applicable)
5. Select as A End Point port 7. Click Deploy 6. Repeat Step 4 and

the connected amplifier Step 5 for Z End Point
©
On the Basic Information panel in the User Label field, enter a name to identify the connection.
A maximum of 92 characters can be entered for the User Label field.
In the Connection Type field, select Bidirectional from the drop-down menu.
The other values are:
• Unidir for unidirectional connections
• Double Simple (uni) for setting OTS between undir amplifiers  It sets two undir
connections: From node 5, port OUT to node 6, port IN & From node 6, port OUT to node 5,
port IN .
• E-SNCP for scenarios having E-SNCP protection switch in an external network (represented in
NFM-T by an external node).
• Y-cable for scenarios having Optical-SNCP protection switch in an external network
(represented in NFM-T by an external node).
• OPS uplink to create inter-compound links between OCS Uplink card and WDM ports
SRG is applicable for Control plane scenarios.

The Allocation Cost field of Enhanced Information is populated by the system.
The Allocation Cost is the nominal cost of the physical connection which will be used by the
allocation algorithm (Dijkstra static). Allocation sets a cost threshold and is used to limit
resources exceeding the upper threshold. The range is 0-100.

OTS physical connections
Check the Physical Connection list  Tabbed View
• Alarms: List of the elementary • Structure: See next

alarms that affect the physical slides
links and the related
correlated alarms • PM Enabled Points: List
of the Monitored points
• Shared Risk Groups: Applicable for • Properties: List of all the applicable
GMRE scenario properties of physical connection
• Clients: List of the Clients resources
(Note: The client OMS infrastructure trail is
automatically created)
©

OTS physical connections [cont.]
Check the Structure tab.

Expand the list of client resources. Frequency/channel
Tooltip to see the client trail

Client OMS trail is that crosses this lambda
automatically created at
OTS physical connection
creation.
The OTS Structure presents the list of supported lambdas (LC at OCH layer) and for each of them, the related (if
provisioned) OTU trails. The user can expand the different resource layers to view all the supported client resources.
©

• Check the Operations of Physical Connection list:

• Select physical link and right-click. The following
operations are supported:
• Deployment control: To Implement/de-implement/set

in service the physical connection
• Modify labels: To modify the label of the physical
connection
• Correlate SRG: Applicable for ASON network
• Delete Connection: To directly remove the physical connection
©

• Non-Aligned objects: To get the list of the

objects
not aligned between OTN and node
• PM report: To get the report of PM
• Modify PM: To modify the Performance
Monitoring setup
• Optical power: To open the Optical Power
graphical
visualization
• Routing display: To open the graphical
representation of physical link
• Correlate ASAP: To correlate an Alarm severity
assignment profile to the link
©

OTS Routing Display
Right-click Physical Connection list to open Routing Display:
Ports involved in
Alarms synthesis physical link and
Last step status related nodes
Connection
direction
Protections type
Port information
options appear with
right-click on the port
Select Show  Equipment Manager
©

Photonic network map representation
Network Map
The color of the link represents the
highest alarm severity.
Tool tip reporting node

attributes
Number of physical
connections available
Click physical connection to open between two nodes
the physical connection list.
©

OS physical connection
©

OS physical connections creation
Physical connections creation from NFM-T
Physical connections creation from NFM-T
From Deploy  New OTN Physical Connections or
From Operate  Physical Connection, click Create icon
1. Choose Default or OPS

WDM connection type =
UNI –X for connections
toward external networks
2. Leave default
4. Choose the WDM and External

Node NNI ports or UNI ports
3. Choose WDM node

and external node as
A/Z END Nodes
5. Click Deploy.
©
When a single optical channel (without a supervisory channel) is transported along the optical
fiber, the OMS layer is skipped and the OTS layer is named the OPS (Optical Physical Section) or
the OS (Optical Section).

Lab exercise
1. Add the NE to the Network map.

2. Explore the Network map and the features presented in the module.
©

Wrap-up
• Explain how to create OS and OTS WDM node internal links
• Explain how to create OS and OTS physical connections
©

1830VWM CPRI
management
(Optional)
OP00090SG067627 - V_Ed1
©

Learning objectives
• Describe the CPRI/CRAN management options from NSP NFM-T
©

ToC Slide
Table of contents
Overview 4
Overview 5
Basic network schema 6
Node list and service list 7
Map management 8
Alarm management 9
PM management 10
Wrap-up 11
©

Overview
©

Overview
• The CRAN/CPRI solution is basically a WDM transport infrastructure used in Mobile

domain, but we are working to integrate the front-haul solution in transport NMS
(NFM-T).
• The CRAN/CPRI solution cannot be managed as a new Network Element because there
are some peculiar aspects that are not aligned at the current OTN behaviors.
• The impacted areas are:

− Node list and EQM
− OTU list
− Alarms and PM
− Map
©
CRAN: Cloud-Radio Access Network (RAN)

CPRI: Common Protocol Radio Interface

Basic network schema
• The picture is a summary of CRAN architecture applicable in NFM-T.

• The 1830 Versatile WDM Module (VWM) monitors and configures remotely up to 20
SAR-O/TLUs through OSC channel.
• The SAR-O/TLU supports maximum 9 connection to RRH; in NFM-T, the connection to
RRH have to be managed as a single port without additional appendix.
Max #9 CWDM
SAR- 1830VWM
Connection SAR-O/TLU
O/TLU 1830VWM
(OSU)
to RRH (OSU)
(antennas)
Max # 20 SAR-O
connected to OSU
©
SAR-O: Service Aggregation Router-Optical

TLU: Translation Line Unit
RRH: Remote Radio Head

Node list and service list
• The 1830VWM is managed as new NE type; it can be created by operator through NE

template creation or automatically discovered through IP scan.
• The node list contains the list of 1830VWM NEs in a separate tab providing an
hierarchical tree for remote shelf (SAR-O/TLU list).
• The NE has to be available in EQM as the 1830 NEs, providing the basic functions to
manage the SW upgrade, audit, CLI, logs, and so on.
Node List PSS 1830VWM
VWM
SAR-O
©

Map management
The 1830VWM is a node with a “virtual” connection with metro/access network; this means
that it cannot be physically connected to a metro node with a solid line but through BBU
object (new graphical object). At the same metro node, many 1830VWMs can be connected.
VWM
VWM
Metro/Access
Core VWM
Fronthaul
©
BBU: Base Band Unit

Alarm management
-
• The 1830VWM/Optical Service Unit (OSU) does not send spontaneous alarms, but it has
to be retrieved by NFM-T through periodical ping; the NE provides an alarm summary
and alarm history for all units.
• The alarms are managed through AS as well.
• No correlation of alarms have to be done at service layer; the alarms raised by RRH are
correlated at the port of SAR-O/TLU.
• In the case of failure of CWDM (LOS, LOP) connection, this has to be correlated to the
optical channel (Och) present in the infrastructure list.
©

PM management
• All objects support the PM@15min and 24h with the following granularity:
− OSU till 96 bins@15min and 1 bin@24h
− Remote Unit till 32 bins@15 min and 1 bin@24h
• The default configuration has to be configured automatically during the NE discovery.
• Only Optical Power Tx/Rx (average, low, high) and Ethernet PM data (octets, unicast,
mcast, bcast, err, discard, unknown) are supported.
©

Wrap-up
• Describe the CPRI/CRAN management options from NSP NFM-T
©

Commissioning and
Power Balancing for
1830 PSS WDM
(Optional)
OP00090SG07AAD8 - V_Ed1
©

Learning objectives
• Describe the generalities about the commissioning and power balancing feature for
1830 PSS networks
• Carry out the main provisioning and commissioning procedures for 1830 PSS
networks
©

ToC Slide
Table of contents
Generalities and CPB APP in NFM-T 5

EPT and CPB APP 6
System 8
Splitting network into systems: Example 9
Commissioning scenarios 10
Prerequisites to use CPB APP in NFM-T 11
Network commissioning: Macro steps 12
Onwards 13
CPB APP 14
Overview on CPB APP commands 15
CPB APP tool navigation 16
Optical NEs and System lists 17
Import the Commissioning File 18
Import the Commissioning File 19
Load the Commissioning File 20
System Validation 22
Perform System Validation 23
Provision system (using Plan) 25
Provision system (using Plan) 26
Select the Nodes 27
©

ToC Slide
Select Provisioning Options 28

Select Provisioning Power Parameters 29
Select Add/Drop Blocks 30
Provision the Nodes 31
Initial/Greenfield (using Plan) 33
Initial/Greenfield (using Plan) 34
Executing the Greenfield Power Adjustment 35
Channel Power Adjustment 37
Channel Power Adjustment 38
Execute Channel Power Adjustment 39
Generate System Loss Report 41
System Loss 42
System Loss: ASE Loss Report 44
System Loss: Power Balance Loss Report 45
System Loss: On-demand Loss Report 46
Export file for EPT 47
Download Network Data Files for EPT 48
Answer the questions 50
Wrap-up 51
©

Generalities and CPB APP in NFM-T
©

EPT and CPB APP
In deploying and operating an 1830 PSS network, three stages are foreseen:
• Network planning using the Engineering and Planning Tool (EPT).
• Greenfield commissioning of the network.
• Ongoing maintenance and network upgrade.
Commissioning and Power Balance APP(CPB) addresses the commissioning phase and also
helps the operator during the ongoing maintenance with the Loss Report and Power
Balancing options.
Report based on the To apply new target

current power values power values and
against the target ones power balance
©

EPT and CPB APP [cont.]
EPT:
• Is used to design and plan the network.
• It provides a .xml commissioning file per system that contains information such as:
− Card types, position, and mutual connectivity
− Min and max values for span losses
− Port-to-port losses between wavelength tracker detect points
− Amplifier gains
• It generates Bill-of-Material (BOM).
• It generates Installation Report.
• It generates Network Information Report.
• It generates Power Levels Report.
CPB APP has been introduced, which replaces the classic CPB application, for Photonic Commissioning and Power Balance
functions CPB APP:
• Imports the .xml commissioning files provided by EPT
• Configures the unequipped slots and compares the design data against installed equipment configuration and creates connections between
cards
• Provides optical power (setting of nominal values) and commissioning (setting of actual values based on real measures)
• Provides power balancing
©

System
A system may include several NEs:
Ring
Point-to-point
• 1830 PSS network must be decomposed by the EPT user into rings or
point-to-point systems.
• Each system has to be commissioned separately.
©

Splitting network into systems: Example
AHPHG
(1-6) CLS8 CLS8
CWR8 CWR8-88
(1-8) (1-4)
CLS1 CLS2 CLS3 CLS4 CLS5 CLS6 CLS1 CLS2 CLS3 CLS4 CLS5 CLS6 AHPLG E
ITLB (25)
O
ALPHG
(1-2) (2-2)
SFD44 (26)
Any Ch Any Ch Ch 30 Ch 53
From
11STAR1 L1 OMD CWR8-88
(1-15)
L1 L4 L3 L2 L1 CLS1 (2-4)
11STGE12 11QPA4 From Ch 35 CLS2 CLS8
(1-18) (1-13) 4DPA4 L1
C4 C3 C2 C1 (1-5)
C1 C2 …. C12
10GELAN Ch 30
GbE NE 1 10GELAN C1 L1
CLS1
CLS8
C2 11QPA4 L2 CLS2 CWR8
C3 (2-13) L3 Any Ch CLS3 (2-8)
C4 L4 CLS4
From Any Ch
11STGE12 L1
(1-8) ALPHG
AHPHG
(1-6)
NE 2 (2-6)
THRU CWR8
CWR8
(1-8) (1-4)
CLS1 CLS2 CLS3 ……….CLS7 CLS8 CLS1 CLS2 CLS3 CLS4 CLS5 CLS6
CLS connections between the
AHPLG CWR boards
Ch 35 (1-2)
L1 L2
L1 L2
4DPA4 11DPE12 The ring must be split in two point-to-
NE 3
(1-16)
(1-19)
C1 C2 C3 C4 C1 C2 …. C12 point systems (a topology is considered
as a ring only in case of connections
1GbE
STM-4 1GbE through THRU ports)
©
Note the different between System 1 and System2 of the picture:

• System 2 is composed by NE1 (1 degree), NE2 (1 degree), NE3 (two degrees, since inside there
is a THRU connection between the CWR8)
• System1 is composed by NE1 and NE2 one degree

Commissioning scenarios
In case of ring system (assuming that at least a pre-amplifier is present on each OTS):
• Commissioning is completely accomplished leveraging on the light source represented by the
Amplifier Spontaneous Emission (ASE).
In case of point-to-point system:

• Commissioning is carried out in two steps:
− Commissioning is only partially accomplished, leveraging on the light source represented by the ASE, because the
End nodes are not fed by any light source (for example ASE) and cannot be configured.
− The commissioning of the remaining nodes requires the operator to create a dedicated service, that can be
disrupted after the task completion or can be kept for real traffic (for power balancing step).
©

Prerequisites to use CPB APP in NFM-T
-
• The network is planned using Engineering Planning Tool (EPT).
• CPB APP component installed on the NFM-T server.
• 1830 PSS NEs must be created and given an address by NFM-T EML:
− Physical connections can either be created or not. They are necessary for creating the service in
point-to-point system commissioning.
©

Network commissioning: Macro steps
System Turn-up:
1. Preconditions:
• Verify circuit packs, cabling and so on
• One pair of OT cards is installed and fibered on the end terminals for a TOADM or ROADM system (Linear Systems
only)
• All Loopback or OAMP IP addresses of all the NEs in the network are configured
• Establish connection to the network and supervise the nodes from NFM-T
• The .xml commissioning file(s) produced by EPT is available
2. CPB APP: Provision the system (with EPT commissioning file)
3. CPB APP: Power Commissioning the system (with EPT configuration file)
4. CPB APP: Power Balancing
5. CPB APP: Generate and review loss report
©
This is a typical turn-up sequence based on your equipment configuration at your location.
A Loss Report is a CPB generated report that provides users with a view of the power losses in
each decoder port in an optical domain.

Onwards
• CPB APP in NFM-T is addressed

• No details about the commissioning guidelines for 1830 PSS networks are given:
− The trainee must already be familiar with them.
− For details, please refer to the Installation and System Turn-up Guide which is part of the Nokia
1830 PSS customer product documentation.
©

CPB APP
The Commissioning and Power Balancing tool integrated with NFM-T R.18 gets re-designed
to optimize performance and pair WebUI approach:
• Exploits NFM-T mediation & communication functions with the Node (no parallel comm)
• Exploits NFM-T network data (no parallel network auto-discovery)
• It embeds the photonic algorithms for commissioning and power balancing
• It execute CPB tasks based on EPT files
• A standalone/portable PC-based application with the same
©
• CPB APP has to be integrated in NFM-T, replacing CPB (PHM), which is no more available
starting from 1830 PSS R9.0.
• CPB APP shall be compatible with all the PSS releases supported by NFM-T release it is
integrated into (according to NE backward compatibility matrix).
• CPB APP does not keep any persistent network information (DB) as CPB.
• CPB APP gets photonic design data from EPT through xml files and performs the
commissioning/power-balance tasks through SNA - there is no more a parallel
communication channel with the NE.
• CPB App gets the node addresses, network topology and optical channel inventory
information from NFM-T DB. The CPB network auto-discovery function is no more present.

Overview on CPB APP commands
©

CPB APP tool navigation
To access the CPB APP,

click Operate 
Commissioning and
Power Balance.
©

Optical NEs and System lists
©

Import the Commissioning File
©

Import the Commissioning File
1. Click the icon to Load

a Commissioning file.
2. Click the Browse to

choose a pre-loaded
Commissioning File
from the PC.
©

Load the Commissioning File
3. The Selected Commissioning

File is shown in the field.
4. Click Load File.
©

Load the Commissioning File [cont.]
5. Wait for the upload

to complete.
©

System Validation
©

Perform System Validation
1. Click System Validation icon which

is present among the other operation
icons.
©
System validation must be performed to ensure that the commissioning file loaded has the
same plan as the nodes in the field.

Perform System Validation [cont.]
2. Validation completed
successfully.
©
It takes a few minutes to complete the process depending on the number of nodes.

Provision system (using Plan)
©

Provision system (using Plan)
-
• Query Inventory: involves collecting information from the uploaded commissioning file
• Provision Inventory: involves provisioning of the shelves and cards in all the nodes
• Provision External and Internal Topology-involves configuration of external and internal optical links
• Provision Power Attributes: involves configuration of the power attributes such as power gain and
nominal loss
1. Click Start Provisioning

icon which is present among
the other operation icons.
©
Before Provision system step, ensure that system validation is completed and errors
encountered during validation process are fixed.

Select the Nodes
2. Select the Nodes

to Provision.
5. The Selected Nodes

are shown in the list.
3. The tab shows All
Nodes reachable
by the system.
4. The arrow tabs can be used to
select or de-select Nodes.
©

Select Provisioning Options
6. Select the Provisioning Options.
7. Select All User Options.

©

Select Provisioning Power Parameters
8. Choose Power
Parameters.
9. Select All Power

Options.
©
WT Decoder Usage Type: This option is not selected by default; must be selected in order to
use the WT feature of the 1830 PSS.

Select Add/Drop Blocks
10. Choose Add/Drop 11. Click Provision tab to

Blocks. provision the system.
©

Provision the Nodes
12. The provisioning shows in

progress and status as Pending.
©

Provision the Nodes [cont.]
13. If some actions are completed correctly,

the Status will show Completed.
©

Initial/Greenfield (using Plan)
©

Initial/Greenfield (using Plan)
1. Click Greenfield ASE Power

Adjustment  icon
which is present among
the other operation icons.
©

Executing the Greenfield Power Adjustment
Clean Slate: Commissioning starts from scratch.
Continue Adjust: Resumes from 'partly-commissioned' network.
2. Click Start from Clean Slate 3. We have option to go

for Greenfield commissioning for Continue Adjust.
of the whole network.
©
Note: Prior to start Greenfield Power Adjustments, ensure that the External Physical links of the
nodes have been discovered

Executing the Greenfield Power Adjustment [cont.]
4. If some actions are not completed

correctly, the Status shows Failed. The
details can be checked in the message.
©

Channel Power Adjustment
©

Channel Power Adjustment
-
Channel Power Adjustment can be used to perform in-service power adjustments. While
performing this task, the channel power levels are adjusted to attempt to reach target
levels, using a wavelength service created through all nodes defined in the commissioning
file.
The channel power adjustment consists of the following steps:

• Verifying Inventory- includes verification of the provisioned system against the information in the commissioning file.
• Performing In Service Power Adjust- includes performing in-service power adjustments that includes ingress and egress
adjust/accept process, performing adjustment on a span, and so on.
• Setting NE Commissioned- includes setting the commissioning flag on the system and nodes to commissioned.
• Display In-Service Power Adjust Result Summary- includes displaying the results of the channel power adjustment in the
system and direction summaries.
©

Execute Channel Power Adjustment
1. Click Start Channel

Power Adjustment
 icon which is
present among the
other operation
icons.
2. Click Start icon to confirm

Power Adjustment.
©
The External Physical Links have already been discovered in previous chapter. Please make sure
that the ports are synchronized before executing Channel Power Adjustment.

Execute Channel Power Adjustment [cont.]
3. If some actions are not

completed correctly, the
Status shows ERROR. The
details can be checked in
the message.
©

Generate System Loss Report
©

System Loss
•
Generate Loss Report generates a power loss report based on the current power values
against the target power settings for the optical domain:
• Greenfield commissioning and power balancing operations always generate loss reports.
• System Loss Report generates a report that summarizes the failed auto power management, the
status of the last ingress/egress adjustment that was performed for each NE, and any components
that are suspected to be out of specification.
©
Ensure to complete the provisioning, commissioning, and power adjustment to get proper loss
reports in all spans of the network.

System Loss [cont.]
1. Click Generate a Loss Report for the

System  icon which is present
among the other operation icons.
©
The following types of loss reports are supported:

• ASE Loss Report
• Power Balance Loss Report
• On-demand Loss Report

System Loss: ASE Loss Report
2. Choose ASE Loss Report 
Generate icon for Report
generation.
3. After the loss report generation is
completed, the report is displayed
for each direction and each of the
add/drop blocks in the system.
©

System Loss: Power Balance Loss Report
4. Choose Power Balance Loss Report 
Generate icon for Report generation.
completed, the report is displayed for
each direction and each of the
©

System Loss: On-demand Loss Report
6. Choose On-demand Loss Report 
Generate icon for Report generation.
completed, the report is displayed for
each direction and each of the
©

Export file for EPT
©

Download Network Data Files for EPT
The Network Data File needs to be generated. This file is intar.gz format which can be
downloaded to your PC.
1. Click on Operate  Tools
 Network Data Files.
2. Click on Generate to
generate the files.
©
Transfer the files from EML instance to the pc using a SFTP connection.

Download Network Data Files for EPT [cont.]
3. Click the icon to save the

file on desktop/pc.
4. Unzip the file and we see

the different configuration
.json files. They can be
read using .json viewer.
©

Answer the questions
1. Which are the stages foreseen in planning, deploying and operating an 1830 PSS?
2. List the commissionning macro steps.
©

Wrap-up
• Describe the generalities about the commissioning and power balancing feature for
1830 PSS networks
• Carry out the main provisioning and commissioning procedures for 1830 PSS networks
©

© Nokia

OP00090-V-1-SG-Ed1 - PDF

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OP00090-V-1-SG-Ed1 - PDF

Uploaded by

Copyright:

Available Formats

Available

NFM-T R.18 Managed plane Network

Important notice on product safety

Upon completion of this course, you should be able to:

• Use the NMF-T Graphical interface

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

OP00090 provides the foundation The intended audience for this

© Nokia 2018 - Nokia Confidential

The prerequisites for attending this course are:

Optional prerequisite training for L2 services:

© Nokia 2018 - Nokia Confidential

Introductions and student information:

© Nokia 2018 - Nokia Confidential

Review student materials and classroom guidelines:

© Nokia 2018 - Nokia Confidential

How to get information?

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

Web-Based Training (WBT) Instructor-Led Training (ILT)

• TOP54048W OTH Overview • OP00091 NFM-T GMPLS Network

© Nokia 2018 - Nokia Confidential

https://nokialearn.csod.com (Global catalog, search by product)

© Nokia 2018 - Nokia Confidential

The related videos for the course OP00090 are:

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

1.Select the following folder:

2.Edit the hosts file

3. Insert the IP address and

4. Save the file and exit

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

The user password is subject to the following constraints:

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

Preferences window can be opened by selecting ADMINISTER  Preferences.

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

For WDM network

Note: 16x6 nodes are out of the scope of this training.

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

© Nokia 2018 - Nokia Confidential

A Data table is a WebUI structure in which data is systematically displayed, for a

Physical Connection list Users can view data tables

© Nokia 2018 - Nokia Confidential

When users mouse over certain column

© Nokia 2018 - Nokia Confidential

Users can click the plus sign that is

Users can select an item in a data