TNMS management framework presentation

Under: HTC-ITC-DWDM project

Version: 2.0

For internal use

1 © Nokia Siemens Networks Presentation / Author / Date
Outline

 TNMS system architecture

 System Administration Guidelines

 Clients Guidelines

 Step by step procedure

For internal use

2 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Core services architecture
Core is a scalable multi-user system with a distributed, client/server architecture comprising
several industry-standard PCs
Core is comprised of the Client, System Administration, Server and NetServer applications.
The Client and System Administration are installed on a client PC.

For internal use

3 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Hardware components
The table below provides an overview of recommended hardware requirements for Core
installations. However, other configurations are possible, depending on the network size.

For internal use

4 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Software components

Client/Sys Admin
components

Core Server
components

Core Net Server

components

For internal use

5 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Core Server components

Core Server components:

Core Server is the central
component of Core and
controls the following FCAPS
for the network management
layer and element
management layer:
– fault management
– configuration management
– performance management
– security management.

For internal use

6 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Gateway NE and DCN Channel
DCN channel quick view:

DCN channels connect the

NEs directly or via an
external EM to their Core
NetServer.

The operator uses DCN

channels to group NEs of the
same DCN channel type.
Core supports the following
DCN channels and
interfaces:

• Gateway NEs separate carrier DCN from internal hiT 7300 DCN
• No additional HW for Gateway NEs (just different configuration)
• All internal IP addresses are automatically assigned (via DHCP)
• More than two Gateway NEs can be configured
(e. g. if redundant TNMS access for each NE required)
• SNMP or TL-1, OSMINE certification

For internal use

7 © Nokia Siemens Networks Presentation / Author / Date
System architecture
DCN configuration
The internal DCN refers to the data communication network used by the NEs to communicate
with each other. While the customer DCN is separated from the internal DCN operation,
following information about the internal DCN is necessary for commissioning:
• Internal DCN IP addresses and the mapping to the NE name/location
• Internal IP addresses within NE and the mapping to the subrack/card/slot
• Internal DCN configurations, e.g. locations of DHCP-, NTP-, ftp-server, etc.
• Internal DCN performance statistics
• Customer DCN networking information (e.g. northbound IP address, default gateway,
mask …), customer FTP server IP address

Means of communication between NEs are:

• Optical supervisory channel (OSC) on fiber links between NEs
• Ethernet interfaces (100BT) between distinct NEs at one location
• Embedded communication channels (GCC0) on transponders

Default mode of communication between NEs is to operate OSC and Ethernet interfaces in a
switching domain with dynamic assignment of IP addresses via “DHCP”

For internal use

8 © Nokia Siemens Networks Presentation / Author / Date
System architecture
Aspects of DCN configuration
IP Address assignment and distribution
DHCP servers are used to automatically assign IP addresses to individual network
elements. DHCP servers take IP addresses from a configurable pool of IP
addresses.

Gateway Function (GF)

The gateway function can be activated on any NE. No separate hardware is
needed. Usually there will be dedicated gateway NEs, which also handle DHCP
server and NE detection function and host the FTP and NTP servers.
The provisioning of the gateway function parameter is assumed to be a manual
procedure. The planner has to identify the GF-NE that is considered to be the
DHCP server (for both primary and secondary).

For internal use

9 © Nokia Siemens Networks Presentation / Author / Date
System architecture
HTC-DWDM project TNMS Core design

IP range: 10.20.1.x/24
Server/NetServer IP: 10.20.1.2
Client IP: 10.20.1.5
Hanoi Primary Gateway: 10.20.1.3
HCM Secondary Gateway: 10.20.1.4
For internal use
10 © Nokia Siemens Networks Presentation / Author / Date
System architecture
HTC-DWDM project DCN design/ OSC Slot layout

IP range: 10.20.1.x/24
Server/NetServer IP: 10.20.1.2
Client IP: 10.20.1.5
Hanoi Primary Gateway: 10.20.1.3
HCM Secondary Gateway: 10.20.1.4
For internal use
11 © Nokia Siemens Networks Presentation / Author / Date
System architecture
HTC-DWDM project DCN design/ DHCP IP design

IP range: 10.20.1.x/24
Server/NetServer IP: 10.20.1.2
Client IP: 10.20.1.5 Microsoft Office
Excel Worksheet
Hanoi Primary Gateway: 10.20.1.3
HCM Secondary Gateway: 10.20.1.4 Please use attachment for
details
For internal use
12 © Nokia Siemens Networks Presentation / Author / Date
Outline

 TNMS system architecture

 System Administration Guidelines

 Clients Guidelines

 Step by step procedure

For internal use

13 © Nokia Siemens Networks Presentation / Author / Date
System Administration functions
The Core System Administration application is used to configure and
administer the Server and NetServer components, since they have no
user interface. An overview of Core Server data is available from the
System Administration menu tree
(Properties > Component Info > Core Server).

Concepts

For internal use

14 © Nokia Siemens Networks Presentation / Author / Date
System Administration logon
1. Start System Administration
Start the Core System Administration interface via Start > Programs > TNMS > System
Administration.
2. login
Log onto Core System Administration via the displayed login dialog.

– in the field Server, enter the name of the PC where

the Core Server is installed. If you are logging in
Concepts directly to the PC where the Core Server is installed,
enter "."
– in the field User name enter the default value
Administrator. This account is created automatically
during the installation of Core
– when you log on for the first time, the field
Password does not have to be completed
– after confirming the entry via the login button,
change the password for the default administrator
account as requested.

For internal use

15 © Nokia Siemens Networks Presentation / Author / Date
System Administration user interface
The System Administration user interface consists of the following parts:
• Menu bar
• Toolbar
• Status bar
• Tree pane
• Working area
• Operational functions

Concepts

For internal use

16 © Nokia Siemens Networks Presentation / Author / Date
System Administration user interface

Title Reference From/To page

Menu bar TNMS operator guidelines Pg.99 - Pg.100

Toolbar TNMS operator guidelines Pg.101

Status bar TNMS operator guidelines Pg.102

Tree pane TNMS operator guidelines Pg.102 - Pg.126 .

Operational functions TNMS operator guidelines

Concepts
Menu bar

Toolbar

Status bar

Reference download: http://www.mediafire.com/?wk6ltmd46ds8tqq

For internal use

17 © Nokia Siemens Networks Presentation / Author / Date
Outline

 TNMS system architecture

 System Administration Guidelines

 Clients Guidelines

 Step by step procedure

For internal use

18 © Nokia Siemens Networks Presentation / Author / Date
Clients functions
The Core Client is responsible for the following functional layers:
Network Management User Interface
The Core Client user interface provides the operator with several network views which
contain graphical and textual information about current alarms, states and resources.
Element Manager/Network Manager Application Interfaces
A corresponding element manager can be started for each NE with a simple double-click. Element
manager applications provide full access to all NE data and also enable the
configuration and control of NE behavior.
Network Management Data Export
Data export is provided in the Core Client to export data for external evaluation. This
enables the operator to export the content of each list and log to a file.

For internal use

19 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Configuration management is an umbrella term for the tasks involved in the organization
and modification of the network plan, the creation and modification of services, and the
administration of subscribers to these services. In Configuration management we have:
1.Network topology management
- Network element
- Protection group & MS protection
- NE container
- Port connection
- Server path
- Remote inventory
- Network augmentation
- Auto link detection
2.Path management
- Supported path types
- Path bundle routing
- Trail-oriented server model
- Loopback function
- Status management for path
- Showing service for path
- Path analyze.
3.Subscribers management
For details please download reference: http://www.mediafire.com/?wk6ltmd46ds8tqq
For internal use
20 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Network topology management
- Network element The properties of a NE can be displayed via one of
- Protection group & MS protection the following menu entries:
– Network Elements Tree: <NE> <Properties...> (A)
- NE container – DCN Components Tree: <NE> <Properties...> (B)
- Port connection – Network Plan: <NE> <Properties...> (C)
- Server path

(A)
- Remote inventory
- Network augmentation
- Auto link detection

(B) (C)

For internal use

21 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Network topology management
- Network element The properties of a NE can be displayed via one of
- Protection group & MS protection the following menu entries:
– Network Elements Tree: <NE> <Properties...>
- NE container – Network Plan: <NE> <Properties...>
- Port connection This feature is only available in Network Editor Mode.
- Server path
- Remote inventory
- Network augmentation
- Auto link detection (Protection group)

(MS Protection)

For internal use

22 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Network topology management
- Network element This feature is only available in Network Editor Mode
- Protection group & MS protection (otherwise, no modifications are possible).
An NE container can be created via one of the
- NE container following menu entries:
- Port connection – Menu Bar: <Configuration> <Create NE
Container...>
- Server path – Network Elements Tree: <Title Bar> <Create NE
- Remote inventory Container...>
– Network Elements Tree: <NE Container> <Create
- Network augmentation NE Container...>
- Auto link detection – Network Plan: <Working Area> <Create NE
Container...>
The properties of an existing NE container can be
(NE container window) displayed and modified via one of the following menu
entries:
– Network Elements Tree: <NE Container>
<Properties...>
– Network Plan: <Working Area> <Properties...>
– Network Plan: <NE Container> <Properties...>

For internal use

23 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Network topology management
A Port Connection can be created via one of the following menu entries:
- Network element – Menu Bar: <Configuration> <Create Port Connection...>
- Protection group & MS protection – Network Elements Tree: <NE> <Create Port Connection...>
- NE container – Network Plan: <NE> <Create Port Connection...>
The figure below shows an example of the Create Port Connection window.
- Port connection In this window, the operator has to
- Server path – select the NEs from the Network Plan (or Network Element tree or DCN
Components tree)
- Remote inventory – select an appropriate transmission layer,
- Network augmentation – select suitable ports and
– set the cost factors, attributes and administrative state.
- Auto link detection

For internal use

24 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Network topology management
- Network element Automatic link detection (ALD) can be handled via the menu entry:
- Protection group & MS protection – Menu Bar: <Configuration> <Engage Link Detection>
The result of the ALD will be displayed within the Link Detection View window
- NE container
- Port connection
- Server path
- Remote inventory
- Network augmentation
- Auto link detection

For internal use

25 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Path management A service or a path can be edited via one of the following menu
- Supported path types entries:
– Subscribers and Services Tree: <Service> <Properties...>
- Path bundle routing – Subscribers and Services Tree: <Path> <Properties...>
- Trail-oriented server model
- Loopback function
- Status management for path
- Showing service for path
- Path analyze.

For internal use

26 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Path management The Options window can be invoked via the menu bar
- Supported path types <Configuration> <Preferences & Routing Options> or by
pressing the Options button in the toolbar of the path
- Path bundle routing wizard.
- Trail-oriented server model There are two tabs in the Options window:
– Automatic Routing Options (influences the behavior of the
- Loopback function automatic router)
- Status management for path – Preferences (display options for the path wizard)

- Showing service for path

- Path analyze.

For internal use

27 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Path management
A service is created via the Path Wizard. Within the Path Wizard Properties window, the
- Supported path types service properties have to be defined. The Path Wizard can be invoked via the following
menu items:
- Path bundle routing
– Menu Bar: <Configuration> <Create Service...> (only available in Services Mode)
- Trail-oriented server model – Subscribers and Services Tree: <Subscriber> <Create Service...>
- Loopback function – Subscribers and Services Tree: <Path Container> <Create Service...>
– Network Elements Tree: <NE> <Create Service...> (only available in Services Mode)
- Status management for path – Network Plan: <NE> <Create Service...> (only available in Services Mode
- Showing service for path
- Path analyze.

For internal use

28 © Nokia Siemens Networks Presentation / Author / Date
Clients – Configuration management functions
Subscribers management
For internal use
29 © Nokia Siemens Networks
A subscriber can be handled via one of the following menu entries:
– Menu Bar: <Configuration> <Subscribers...> (only available in Services Mode)
– Toolbar: <Subscriber> (only available in Services Mode)
– Subscribers and Services Tree: <Title Bar> <Create Subscriber...>
– Subscribers and Services Tree: <Subscriber> <Subscriber Management>
– Subscribers and Services Tree: <Path Container> <Subscriber Management>
– Subscribers and Services Tree: <Path> <Subscriber Management>
Presentation / Author / Date
Clients – Performance management functions

Transmission quality can be monitored by PMP (performance measurement point) for any path.

Furthermore any PMP of any NE may be monitored. Network topology management

A measurement and an update interval is configured for each performance measurement log. The

measurement interval which determines how often data is collected can be set to either every 15

minutes or every 24 hours. The update interval which determines when data is actually written to the

performance data log is freely configurable. However, in order to minimize the DCN load, the update

interval is always determined by the PMPs attributes.

For internal use

30 © Nokia Siemens Networks Presentation / Author / Date
Clients – Performance management functions

Performance management A performance log can be handled via one of the following menu entries:
– Menu Bar: <Performance> <Performance Logs>
– Menu Bar: <View> <Tables...> <Performance Logs>
– Toolbar: <Logs>
– Subscribers and Services Tree: <Path> <Create Performance Log...>
– Subscribers and Services Tree: <Path> <View Performance Log...>

For internal use

31 © Nokia Siemens Networks Presentation / Author / Date
Clients – Fault management functions
Fault management in Core comprises the following alarm handling functions:
– alarm list
– alarm log
– display of alarm summary
– display of alarm state
– display of alarm severity
– audible alarm
– external alarm output
– alarm messenger for alarm summary forwarding via email/SMS
For each alarm notification received by the Core Server:
– the notification is forwarded to all connected Core Clients
– the list of current alarms is updated
– automatic correlation to services is performed
– the notification is stored in the alarm log.
For each alarm notification received by the Core Client:
– the alarm is updated
– the alarm log is updated
– the alarm supervision of NE icons and NE container icons is updated
– the current alarm statistics for NEs and NE containers are updated
– the operational state for services/paths is updated.

For internal use

32 © Nokia Siemens Networks Presentation / Author / Date
Clients – Fault management functions

Alarm and path statistics An overview of all alarms in the network can be displayed via the following
menu entry:
– Menu Bar: <Fault> <Alarm and Path Statistics...>

For internal use

33 © Nokia Siemens Networks Presentation / Author / Date
Clients – Fault management functions
A list of current alarms related to a selected object can be opened via one
Current alarms of the following menu entries:
– Menu Bar: <Fault> <Current Alarms...>
– Network Elements Tree: <NE Container> <Alarms> <Current
Alarms...>
– Network Elements Tree: <NE> <Alarms> <Current Alarms...>
– DCN Components Tree: <NE> <Alarms> <Current Alarms...>
– Network Plan: <Working Area> <Alarms> <Current Alarms...>
– Network Plan: <NE Container> <Alarms> <Current Alarms...>
– Network Plan: <NE> <Alarms> <Current Alarms...>
– Alarm Statistics Window: <Counter> <Current Alarms...>

For internal use

34 © Nokia Siemens Networks Presentation / Author / Date
Clients – Fault management functions
An alarm log related to a selected object can be opened via one of the
Alarm logs following menu entries:
– Menu Bar: <Fault> <Alarm Log...>
– Network Elements Tree: <NE Container> <Alarms> <Alarm Log...>
– Network Elements Tree: <NE> <Alarms> <Alarm Log...>
– DCN Components Tree: <NE> <Alarms> <Alarm Log...>
– Network Plan: <NE> <Alarms> <Alarm Log...>

For internal use

35 © Nokia Siemens Networks Presentation / Author / Date
Clients – Fault management functions
The Alarm Statistics window for an individual object can be opened via one of
the following menus:
Alarm statistics – Network Elements Tree: <Title Bar> <Alarms> <Alarm Statistics...>
– Network Elements Tree: <NE Container> <Alarms> <Alarm Statistics...>
– Network Elements Tree: <NE> <Alarms> <Alarm Statistics...>
– DCN Components Tree: <Title Bar> <Alarms> <Alarm Statistics...>
– DCN Components Tree: <NetServer> <Alarms> <Alarm Statistics...>
– DCN Components Tree: <DCN Channel> <Alarms> <Alarm Statistics...>
– DCN Components Tree: <NE> <Alarms> <Alarm Statistics...>
– Network Plan: <Working Area> <Alarms> <Alarm Statistics...>
– Network Plan: <NE Container> <Alarms> <Alarm Statistics...>
– Network Plan: <NE> <Alarms> <Alarm Statistics...>

For internal use

36 © Nokia Siemens Networks Presentation / Author / Date
Clients – Security management functions

Security management functions can be used to restrict access either to the Core user interface or

to individual NEs.

Access to the Core user interface is controlled by a user ID and a password which are initially

configured in the security settings provided by System Administration. The access rights defined

for users based on their class can be further restricted to particular NE containers (domains) for

which the user is responsible. This way, useless visibility of objects is also avoided, i.e. only those

objects belonging to those NE or sub-NE containers for which the user has access permissions are

displayed.

For internal use

37 © Nokia Siemens Networks Presentation / Author / Date
Outline

 TNMS system architecture

 System Administration Guidelines

 Clients Guidelines

 Step by step procedure

For internal use

38 © Nokia Siemens Networks Presentation / Author / Date
Step by step procedure

To be updated by NSN engineers

For example:
1. How to create NE in DCN management of Core Server
2. How to add/delete paths/services of NE
3. How to filter alarm, display history alarm for troubleshooting
4. …

NSN is the leader in the 40G market and the best customer care

For internal use

39 © Nokia Siemens Networks Presentation / Author / Date
Summary
• Overview of TNMS Core System architecture and HTC-DWDM
TNMS Core design for HTC-ITC optical transmission backbone
• Guidelines of System Administration for Server operation and
maintenance
• Guidelines of Client for daily tasks of customer’s system
• Step by step procedure for reference, training.
• For more details, please download reference as:
- TNMS Technical description: http://www.mediafire.com/?
pwrqe1wo7ekp8nr
- TNMS Operational guidelines: http://www.mediafire.com/?
wk6ltmd46ds8tqq

NSN is the leader in the 40G market and the best customer care

For internal use

40 © Nokia Siemens Networks Presentation / Author / Date
Thanks for your attention!

For internal use

41 © Nokia Siemens Networks Presentation / Author / Date
Backup: NG 40G

For internal use

42 © Nokia Siemens Networks Presentation / Author / Date
Map of 40G-Technologies
Modulation Channel Cost
Reach Est. GA Remarks
Format spacing add-on
NRZ short reach to LH 100GHz  x 1,0 now Available today as MSA300.

reach < 300 km

PMD < 3 ps
Carrier ULH 100GHz x 1,05 now Deployed hiT 7500 interleaver filters and 50 GHz
suppressed RZ OADM infrastructure are too narrow for reasonably
(CS-RZ) reach < 1500 km good operation.
PMD < 5 ps
Duobinary (DB) LH 50GHz x 1,1  now Current OEM-solution, largest inherent chromatic
dispersion tolerance 150ps/nm, twice as much as NRZ
reach < 800 km or CS-RZ.
PMD < 3 ps
(with PMDC < 8ps)
Differential phase ULH 50GHz x 1,2  Q2-Q3 Simulations started to estimate the penalty for 50 GHz
shift keying with penalty 2006 grid (Interleaver filters and 50 GHz OADM
(DPSK) reach < 1500 km infrastructure are the critical elements)
PMD < 5 ps
Differential LH 50GHz x 1,4  2007+ Neighbouring ASK channels may distort the DQPSK
quadrature phase channels severely, nonlinear phase noise has to be
shift keying reach < 1000 km considered; due to lower symbol rate combination with
(DQPSK) PMD < 8 ps electronic distortion compensation possible –
Reach may be DQPSK + MLSE is investigated within the
enhanced with BMBF project EIBONE
MLSE (< 2000km)
Optical single side LH 50GHz x 1,2  2007+ Combination with electronic predistortion compensation
band
Source: Bohn/Krummrich to adjust 10G dispersion compensation infrastructure to
(AMI-RZ-OSS) reach < 1200 km 40G requirements for upgrading from 10 to 40G
with pre-EDC Duobinary offers ~700km reach @ 80ch
PMD < 5 ps (tbc.) without any change in existing 10G network
infrastructure. Lab setup available.
DPSK offers ~1200km reach @ 80ch/~1500km reach @ 40ch
For internal use
43 © Nokia Siemens Networks Presentation / Author / Date