TNMS end to end management system –

Future outlook
November 2013

Dario Milinović
IT@RATIO d.d.
Value Proposition

OPEX minimization

Value added features

Multi-technology support
CAPEX Optimization
Automated processes

Improved network utilization

Scalable platform
Quality & User Experience
Open for integration

Reliable server platform

Field-proven TNMS solution

Copyright © Coriant 2013. All rights reserved.

3M

Multi-platform
TNMS is a true multi-platform solution. Its state of the art architecture allows deployments in different Operating Systems

Multi-technology
TNMS provides a seamless capability to support multiple network technologies:
 SDH/PDH
 DWDM (OCH), OTN (ODU)
 ASON (SDH, OCH, ODU)
 MPLS-TP, Ethernet, IP-MPLS

Multi-vendor
TNMS provides effective technical solutions to efficiently integrate 3rd party network elements. This capability allows operators
to perform network consolidation reducing the need for different network management systems, therefore reducing the OPEX
and CAPEX need.

Paulo Ferreira / ON Product Management

© Coriant
TNMS Example
Alarm shown on map & tree views

Alarm
correlation Embedded
to service EM (LCT)

Network Map

Alarm List/ Path

Disabled Properties/
Paths Routing

© Coriant
FCAPS functionality as defined by the ITU-T M.3010
Security Management Performance Management Network Automation

Access control Performance monitoring Network inventory

Domain concept Performance analysis NE configuration backup
Access rights Performance reporting NE SW & user management
User classes Performance logging
Disaster recovery

P
Supervision S System E2E Configuration Management
F Mng A
Alarm reporting & logging E2E multi layer service provisioning
Alarm localization / diagnostic C Network configuration
Service alarm correlation Service Management Layer
Path/circuit provisioning
Test facilities Network Management Layer Protection switching / routing
Element Management Layer

Microwave MSPP DWDM OTN Ethernet PTN IP

© Coriant
Towards a new architecture
Umbrella Systems Layered approach for logical and physical organization
of components. Implementation is based on the J2EE
Client Layer
standards, therefore multiplatform

Managers Common Functions Uses a SOA based architecture with highly

independent components/services, consisting of
Common Functions / Technology Managers covering
specific feature areas.
TMF CORBA SNMP MTOSI
Server Layer
SDH & Optical Common Functions
Provides supervision of all processes. Automatic
Mgmt DCN Mgmt User Mgmt License Mgmt
restart / resynchronization if required. Hardware and
Software monitoring integrated into fault
ASON Mgmt Topo Mgmt Fault Mgmt System Sup.
management
Element Mgmt Perf. Mgmt NE Conf. Backup
Ethernet &
Log Mgmt Inventory Mgmt NW SW Mgmt Advantages of the new TNMS architecture:
MPLS- TP Mgmt
scalable and flexible
TMF SNMP Legacy easy to maintain and extend
Mediation Mediation Mediation
Oracle
reusable and portable
Server interoperable and resilient
transactional and secure

© Coriant
TNMS NCT and LCT

TNMS LCT TNMS NCT:

A single network overview for alarm monitoring and
Element management of individual NE
LCT functionality for configuration
TNMS LCT TNMS NCT

Paulo Ferreira / ON Product Management

© Coriant
TNMS Core Deployment configurations

TNMS Core system (up to 14.x) TNMS Hybrid system (up to 14.x):
TNMS Core server for SDH element, network and
TNMS Core Server for hiT70xx management, with
service management
additional optional features (from TNMS R14)

TNMS
TNMS Clients
Clients

TNMS Core TNMS AM

TNMS Core Server Server
Server

SDH element, network and service management

Paulo Ferreira / ON Product Management

© Coriant
TNMS Deployment configurations (new architecture)

Single server system Distributed mediation:

TNMS server and mediation SW run in the same
TNMS server and mediation SW run in different
single server. (recommended configuration due to
servers.
CAPEX and OPEX savings) TNMS
Clients

TNMS
Clients

TNMS
Server

TNMS
Server

TNMS
Netserver

Paulo Ferreira / ON Product Management

© Coriant
TNMS High availability deployments (new architecture)

The Standby concept using the Oracle Streams The Active-Active concept only available for
feature allows geo-redundancy specific network configurations

TNMS
Clients

TNMS DB
TNMS 1st TNMS 2nd TNMS
Server sync Stand-by Server Server
Server

Paulo Ferreira / ON Product Management

© Coriant
TNMS rebranding starts with R14.1
TNMS V14.1

Following NSN agreement to

sell Optical Networks Business
Unit to Marlin Equity Partners
LLC (‘Marlin’), the new
the name of the new, independent company that was established following
company “CORIANT” has the closing of the sale of NSN’s optical business on May 6th
born.

All the Coriant portfolio is now

being rebranded.

Rebrand extends to all areas

of the product, from the
Graphical user interface to the
registry keys (including LCTs)

© Coriant
Automation Functionalities
Network Inventory Management

• Provides a network wide view of

Shelf, Cards and Ports

• Provides details on the Planned

equipment and installed
equipment

• Includes among others Serial

Numbers and Part numbers

• Available for limited cards of

hiT7300 5.30 50

© Coriant
NE Configuration Backup

TNMS allows the Manual or scheduled

backup of the entire network at once.
Different schedule options are available.
Several jobs can be created for different
Network Elements, with different
schedules.
Parallel backups are configurable based
on DCN bandwidth.
Retention period for backups is
configurable
All activity is logged and Alarms are raised
for failed operations

© Coriant
NE SW Download

Central repository of APS files on the

server used as the base directory for the
software download.
Scheduled download of the APS to inactive
bank
TNMS validates the APS and upgrade
path, avoiding user mistakes.
Wide view of active APS and inactive APS
on the network
Parallel Downloads are configurable based
on DCN bandwidth.
Manual and Sheduled Switch APS and NE
reboot

© Coriant
NE user & security management

NE User Configuration feature allows you

to manage network wide user accounts
TNMS provides the possibility to create
delete, modify the NE user account in NEs.
Several other rules can be configured, as
number of invalid logins, account
expiration, between many others.
Enable/Disable of NE user with TNMS
Display of logged in users with IP and User
Class

Paulo Ferreira / ON Product Management

© Coriant
Optical Manager
Customer value

Seamless configuration use Operational debug efficiency

case independent from network With:
element and/or layer • Alarm Correlation
• Path Hierarchy
• Path History

Flexible creation of DWDM and OTN

paths:
• Optical Transport Section (OTS)
• Optical Multiplex Section (OMS)
• Optical Channel (OCh) IOC/SDN integration
• Optical Transport Unit (OTU)
• Optical Data Unit (ODUK, FLEX)

Copyright © Coriant 2013. All rights reserved.

Supported equipment

Optical Manager

Aggregation * Core * Aggregation

hiT 7100
Scalable POTS for
aggregation and core

hiT 7500/7300
Scalable WDM for
aggregation and core

FSP 3000 R7
Scalable WDM for
aggregation and core

© Coriant
Path Creation

• Creation of OCH/ODU Paths

• Assisted Routing with automatic
definition of the return route for
OCH Paths
• Display of alarms and traffic
status.
• Path operational status including
propagation of server status

© Coriant
ODU Templates

ODU switching configuration, with TP Template

concept

This type of TP is used to display the possible

allocations left in a given TP.

Optical Manager automatically structure the ODU

in the network.

Optical Manager allows the creation of high order

ODU paths to be used later by a low order ODU
path as a server path.

© Coriant
Path Hierarchy

• View complete hierarchy of used

server paths for a given client
Path
• Details on each of the Paths
regarding current operational
state, alarm severity, resilience
and other relevant
• Ability to toggle the hierarchy in
order to see all client paths of a
given server.
• Path options can be invoked
directly via a right click on the
Path in the list

© Coriant
Alarm mapping

• Correlation of Alarms to
Paths directly visible from the
Path list.

• Possibility to filter alarm list

for a specific Path.

• Possibility to Filter alarm

history per path (Alarm log)

© Coriant
Path History

• Provide a list of the past

routes of a given Path

• Possibility to restore a route

from history

• Support of temporary routes

when integrated with IOC
solution

© Coriant 24
ASON Manager
GMPLS for a dynamic control plane

Management ASON architecture defined by

plane
ITU-T based on IETF‘s GMPLS

GMPLS control plane

GMPLS
GMPLS Control • Multi-layer control plane across
Plane
WDM, OTN, SDH, and MPLS-TP
E-NNI
GMPLS GMPLS
GMPLS
• Protection & restoration against
multiple fiber breaks
Infrastructure • GMPLS UNI / E-NNI
Plane • Combines with IP/MPLS control
WDM OTN SDH plane in an efficient manner

GMPLS Multi-layer GMPLS

 Easiest and most efficient service management
 Improved service protection & resilience
in multi-layer networks

© Coriant 26
Customer Value

Multi layer GMPLS support for Wizard-aided ASON service

OCH, ODU and SDH configuration

ASON
Manager

Network Discovery, Monitoring Comprehensive logging of

and virtualization system and calls events

© Coriant
Supported equipment
ASON Manager

Access Aggregation * Core * Aggregation Access

hiT 70xx hiT 7100
1.5 TB
640G

Scalable POTS for aggregation and core

hiT 7300

Passive
Flat Pack Shelf
Scalable NGSDH for
access and aggregation Scalable WDM for aggregation and core

Copyright © Coriant 2013. All rights reserved.

Protections
1+1 Path Protection
› Working and protection paths are provisioned as two permanent connections with dedicated routes in the network (50ms
SNCP protection)
Permanent 1+1 + DSR
› Multi-failure 1+1 Path Protection
› Whenever such paths fail they are dynamically restored, thus providing fast 50ms resilience against multiple failures
› In case further disjoint paths cannot be found the next failure recovery is attempted dynamically (DSR)
Dynamic Source Re-routing upon Failure (DSR)
› Multi-failure recovery by dynamic source re-routing of failed LSPs by the control plane, using any available bandwidth
› Supporting make-before-break with resource re-use of fault-free link segments
Pre-Planned Shared Restoration
› Restores a path affected by a failure end-to-end to a pre-planned restoration path.
› Highly resources efficiency: the transport resources that are not occupied can be shared among restoration paths that don’t
need the resources at the same time.
Permanent Pre-Planned Shared Restoration + DSR
› Multi-failure Pre-Planned Shared Restoration

Copyright © Coriant 2013. All rights reserved.

ASON Manager for network virtualization

DWDM GMPLS
domain

OTN GMPLS domain

IP domain

© Coriant
Ethernet Manager

Coriant hiT 7300

Value proposition
With data traffic exploding and now dwarfing the Time Division Multiplexing (TDM)-based
demands, a move to pure packet-based transport over Dense Wavelength Division
Multiplexing (DWDM) has significant economic .

In fact, a Metro Ethernet Forum (MEF) study suggests that an Ethernet–over-optical network
costs about half as much to operate as a legacy SONET/SDH one.

Traffic Cost (legacy

By combining packet-processing volume technologies)
intelligence and optical- Revenue
wavelength assignment into a Cost
single unified system, service (packet over DWDM)
providers can achieve significant Time
operational savings. Voice Data dominated
dominated

© Coriant
Ethernet Manager – Added Value

Fast network provisioning Operational

› Wizard-aided service configuration efficiency
› User-friendly, easy-to-understand GUI
 Less training time!

Service monitoring Decrease OPEX

› Service alarm correlation and CAPEX
› Configuration supervision

Time savings by error free processes Speed

Multi-vendor integration

© Coriant
Supported equipment

TNMS

hiT 7300 Simplified Multi- hiT 7080

Optical Transport Layer and Multi- Next Generation SDH
Vendor Network
• I22CE10G Card Operations • 6xGE + 4xFEGE/A (L2)
• 1x10GE/T
(Transparent)

Copyright © Coriant 2013. All rights reserved.

TNMS Support of MEF 6.1 Ethernet Services

Port-Based VLAN-Based
Service Type
(All-to-One Bundling) (Service Multiplexed)

E-Line Ethernet Private Line Ethernet Virtual Private Line

(Point-to-Point EVC) (EPL) (EVPL)

E-LAN Ethernet Private LAN Ethernet Virtual Private LAN

(multipoint-to-multipoint EVC) (EP-LAN) (EVP-LAN)

E-Tree Ethernet Private Tree Ethernet Virtual Private Tree

(rooted multipoint EVC) (EP-Tree) (EVP-Tree)

Full support Limited support

Copyright © Coriant 2013. All rights reserved.

Service Management

Services:

 E-Line, E-LAN Service

Configuration
 E-Line, E-LAN, E-Tree
Service Discovery

Definition of service name,

Transport VLAN (S-VLAN) and
End/Route ports

Provisioning and Network

Event Log

© Coriant
VLAN Management per service

VLAN Mapping
Configuration per service:

 Definition of individual,
lists or C-VLAN ranges
 Map untagged traffic to a
specific C-VLAN
 Map the S-VLAN for
transparent transport

© Coriant
Policing per service

Priority:

 COS [0…7] defined for prioritization for each end port

of the service

Policing:

 Single rate, two color marking per service Port

 two rates, three color marking per Service Port

© Coriant
Service supervision

Alarm status per service

and service alarm
correlation

Administration and
Operational state
Supervision

Supervision of Configured
services configuration

G.8262/Y.1362 –
Synchronous Ethernet
Supervision

© Coriant
Evolution scenarios

Coriant hiT 7300

TNMS setups (2013-2015)
• 3 possible setups exist

TNMS Core TNMS Hybrid TNMS Standalone

(<=14.x) (TNMS Core+AM) (>=14.x)
(<=14.x)

© Coriant
Core
TNMS Core Configuration & Dimensioning (1)

Optional

Remote Inventory

TMF CORBA Mgmt

Performance Log

Import/Export I/F.
SNMP Agent I/F
Capacity Mgmt
Warm Standby
Feature Licenses

Domain Mgmt

SNMP SBI I/F

Netviewer Int.
Network Category
Dependent

export
A, B, C, D

I/F
Connection License ~ NE, Card, Interface
Base SW + License
Basic License + SW ~ Network category independent

Platform Software ~ Number of computers

OEM SW + License
Server Hardware ~ Number of servers

© Coriant
Core
TNMS Core Configuration & Dimensioning (2)
TNMS Hardware
Client HW
Client
Client
Client
Tests only! Key Dimensioning Table
0..40
Client HW
Client
Client
Client
NetServer
Dimensioning Parameters Medium Large
TNMS Core Server Load Equivalents (LEs) 400 8400
0..25
TNMS Core Server HW Managed Paths (MP)*** 5.000 60.000
Client 0..10 Number of NEs per NetServer* 350 500
TNMS Core Server
TNMS Core Server
NetServer
Number of NetServer HW 0 10
NetServer
NetServer
NetServer Number of Client HW 25 40
NetServer HW
TNMS Core Server HW
TNMS Core Server HW (normal Client** + System Admin) 15 + 10 30 + 10
* Depending on the NE types
** Incl. SNMP and CORBA and CITRIX clients, too.
SMALL MEDIUM LARGE *** ca. 660.000 Route elements (REs)

© Coriant
Core
TNMS Core Configuration & Dimensioning (3)
Server – Medium
Minimum Recommended
XEON DP dual core 3.0 GHz, 1 x Intel Xeon E5-2420 6C/12T 1.90 GHz 15 MB,
4 GB RAM, 73 GB HD, 12 GB RAM, 2 x HD SATA 6G 500GB 7.2K,
Win2003 SE 32bit, R2, SP2 Win2008 R2, SE 64bits, R2, SP2

Server – Large
Minimum Recommended
Minimum and
XEON DP dual core 3.0 GHz, 2 x Intel Xeon E5-2609, 4C/4T 2.40 GHz, 10 MB, 24 recommended
6 GB RAM, 73 GB HD,
Win2003 SE 64bit, R2, SP2
GB RAM, 2x HD SAS 6G 146GB 15K, Win2008 R2,
SE 64bits, R2, SP2
Hardware
Standard HW: Fujitsu
NetServer – Rack
Minimum Recommended
Techn.
Core 2 Duo E8400, 1 x Intel Xeon E3-1220v2 4C/4T 3.10 GHz 8
2 GB RAM, 73 GB HD, MB, 8 GB RAM, HD SATA 6G 500GB 7.2K
Win XP SP3 Win2008 R2, SE 64bits, R2, SP2

NetServer – Floor and Client

Minimum Recommended
Core 2 Duo E8400, 1 x Core i5-3470 3.20 GHz, 6 MB, quad core/4
2 GB RAM, 73 GB HD, threads, 8 GB RAM, HDD SATA III 500GB 7.2k
Win XP SP3 Windows 7 Professional 32 bits

© Coriant
Core
Upgrade to V13.2 10
Upgrade & Migration for TNMS Core:
From any versions of V12 only one upgrade
(and two updates) are needed:
• V12 (any)  V13.1 EP1 upgrade
• V13.1 EP1  V13.2 update
• V13.2  V13.2 10 update

© Coriant
TNMS Core Upgrade to V14.1
TNMS Core V14.1

V14.1 is a base install

TNMS Core
Just need to backup the Server TNMS Core
(V13.2 12
database in previous Server
or
version (V13.2 12 or V14.0 V14.0 20) V14.1
20) and restore it in V14.1
DB
No migration is necessary

Backup / Restore

© Coriant
TNMS Upgrade to V14.1
TNMS V14.1

Just need to install the new

TNMS on top of existing TNMS (AM)
one and DB will be Server
automatically migrated TNMS
(V13.2 12
or Server
V14.0 20) V14.1
Migration is a simple process
in TNMS, by usage of SQL DB
statements.

DB migration

© Coriant
Summary
Key differentiators

Multi-technology Configuration Management

Optical Channels, ODU switching, SDH / PDH,
Ethernet, MPLS-TP, GMPLS

Renewed Architecture
Scalability. Single system with high operational efficiency increasing CAPEX and OPEX efficiency.
Layered and tiered approach

Open for Integration

Multi Vendor Integration via southbound interfaces
Umbrella-OSS integration via standardized interfaces

© Coriant
Success stories and references

China Unicom

Cyta

© Coriant
Thank you…..

> [Link]@[Link]