8000 INM SR6.0 System Description

7/23/2019 8000 INM SR6.0 System Description

http://slidepdf.com/reader/full/8000-inm-sr60-system-description 1/171

8000 Intelligent Network Manager SR6.0

System Description

76.8060-70200D09.12.2014



Document Information

Revision History

Document No. Date Description of Changes

76.8060-70200D 09.12.2014 Data on the 7100 Packet Optical Transport Series updated in

chapter 1.1.4.

Information on the OTN circuits updated in chapter 1.2.6.

Information on the TDM circuits updated in chapter 1.2.9.

The description of the 7100 Adapter updated in chapter 2.4.6.

The description of the Router application updated in chapter 3.3.1.

Information on the new PMS support added to chapter 3.6.

76.8060-70200C 07.10.2014 The description of 7090-40 CEM added to chapter 1.1.3.

The description of 8615 Smart Router added to chapter 1.1.6.

The description of the VLAN Quality Test Sub-package updated in

chapter 3.4.2.


76.8060-70200B 11.07.2014 The document has been rebranded.

The description of the 7090-15 CEM NE as well as information on

the Ethernet ring protection and configuration discovery added to

chapter 1.1.3.

Information on the optical circuit discovery added to chapter 1.1.4.

The descriptions of the 8115 NTU and 8155 Access Switch added

to chapter 1.1.5.

The description of the 8602-D variant added to chapter 1.1.6.

A new chapter 1.1.8 about mTera UTP added.

The data related to the OTN circuits updated in chapter 1.2.6.

New chapters 1.2.10 Ethernet First Mile Services and 1.2.13

Seamless MPLS added.

Information on the minimum configuration updated in chapter 2.1.2.

Information on the 8100 EFM Adapter added to chapter 2.4.6.The description of Multi Node SNMP Agent Wizard added to

chapter 3.2.1.

8602 Smart Router added to the list of supported nodes in chapters

3.2.1 and 3.2.12.

Information on the 7100 and mTera Node Manager updated in

chapter 3.2.2.

Information on the tunnel bandwidth reservations and MPLS-TP

tunnel discovery added to chapter 3.3.3.

The description of the VLAN Quality Test Sub-package updated in

chapter 3.4.2.


A new chapter 3.11.6 about VPN Provisioning and Tunnel

Engineering in partitioned network added.

© 2014 Coriant. All rights reserved.

This manual is protected by U.S. and international copyright laws, conventions and treaties. Your right to use this manual is

subject to limitations and restrictions imposed by applicable licenses and copyright laws. Unauthorized reproduction, modification,

distribution, display or other use of this manual may result in criminal and civil penalties.

The specifications and information regarding the products in this manual are subject to change without notice. All statements,

information, and recommendations in this manual are believed to be accurate but are presented without warranty of any kind,

express or implied. Users must take full responsibility for their application of any products.

Adobe® Reader ® are registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

8000 Intelligent Network Manager SR6.0 76.8060-70200DSystem Description © 2014 Coriant.

2




Terms and Abbreviations

Term Explanation

AAL ATM Adaptation Layer

ACL Access Control List

ADC Automated Deployment Controller

ADM Add/Drop Multiplexer

ADNS Automated Deployment Network Scanner

AIP Alarm Interface Panel

APS Automatic Protection Switching

ARP Address Resolution Protocol

ATM Asynchronous Transfer Mode

BFD Bidirectional Forwarding Detection

BGP-4 Border Gateway Protocol version 4

BMP Broadband Management Protocol. A communication protocol which is used between

the 8600 network elements and 8000 Intelligent Network Manager.

BSC Base Station Controller

CE Customer Edge

CEP Customer Edge Port

CES Circuit Emulation Service

CESoPSN Circuit Emulation Service over Packet Switched Network

CLI Command Line Interface

CMIP Common Management Information Protocol

CNPP Port-based Customer Network Port

CNPS S-tagged Customer Network Port

CORBA Common Object Request Broker Architecture

CSPF Constrained Shortest Path First

CWDM Coarse Wavelength Division MultiplexingDHCP Dynamic Host Configuration Protocol

DLCI Data Link Connection Identifier

DM Delay Measurement

DMA Deferred Maintenance Alarm

DSLAM Digital Subscriber Line Access Multiplexer

DSL Digital Subscriber Line

DWDM Dense Wavelength Division Multiplexing

E-LAN Ethernet LAN

76.8060-70200D 8000 Intelligent Network Manager SR6.0 © 2014 Coriant. System Description

3




E-tree Ethernet tree

EFM Ethernet in the First Mile

ELP Ethernet Link Protection

E-LSP EXP-inferred LSP (EXP bits in the label indicate the required per hop behavior)

EML Element Management Layer

EMS Element Management System

ERP Ethernet Ring Protection

FMS Fault Management System

FOADM Fixed Optical Add/Drop Multiplexer

FR Frame Relay

GCC General Communications Channel

GMPLS Generalized Multiprotocol Label Switching

GPRS General Packet Radio Service

GRE Generic Routing Encapsulation

GUI Graphical User Interface

HDLC High-Level Data Link Control

HTTPS Hypertext Transfer Protocol Secure

H-VPLS Hierarchical Virtual Private LAN Service

ICMP Internet Control Message Protocol

IFM Interface Module

IP Internet Protocol

IP VPN BGP/MPLS VPN

IRB Integrated Routing and Bridging

IS-IS Intermediate System to Intermediate System

L2 OSI Layer 2

LAG Link Aggregation Group

LAN Local Area Network

LDP Label Distribution Protocol

L-LSP Label-inferred LSP (PHB treatment is inferred from the label)

LM Loss Measurement

LMIP Local Management Information Protocol

LSP Label Switched Path

LTE Long Term Evolution

MA Maintenance Association

MAC Media Access Control

MD Maintenance Domain

MEI Maintenance Event Information


4




MEP Maintenance Endpoint

MIB Management Information Base

MIP Maintenance Intermediate Point

MPLS Multiprotocol Label Switching

MPLS-TP MPLS Transport Profile

MSAN Multi Service Access Node

MSP Multiple Section Protection

MSPP Multi-service Provisioning Platform

MTOSI Multi-Technology Operations System Interface

NBI Northbound Interface

NE Network Element

NID Network Interface Device

NML Network Management Layer

Node In 8000 Intelligent Network Manager refers to a network element.

NTP Network Time Protocol

NTU Network Terminating Unit

OAM Operations, Administration and Maintenance

ODU Optical Data Unit

OLA Optical Line Amplifier

OPU Optical Payload Unit

OS Operations System

OSL Object Server Layer

OSPF-TE Open Shortest Path First - Traf fic Engineering

OSR Object Server

OSS Operations Support System

OTN Optical Transport Network

OTS Optical Transport System

PDH Plesiochronous Digital Hierarchy

PE Provider Edge

PLM Physical Line Module

PMA Prompt Maintenance Alarm

PNNI Private Network to Network Interface

PPP Point-to-Point Protocol

PVC Permanent Virtual Circuit

PW Pseudowire

PWE3 Pseudowire Emulation Edge to Edge.

QoS Quality of Service


5




RADIUS Remote Authentication Dial-In User Service

RAN Radio Access Network

RNC Radio Network Controller

RNO Real Network Operator

ROADM Reconfigurable Optical Add/Drop Multiplexer

RPL Ring Protection Link

RSVP-TE Resource Reservation Protocol - Traf fic Engineering

RVT Resilient VLAN Tunnel

SAToP Structure-Agnostic Time Division Multiplexing over Packet

SBOADM Single Bay Optical Add/Drop Multiplexer

SDH Synchronous Digital Hierarchy

SHDSL Single-Pair High-Speed DSL

SGSN Service GPRS Support Node

SML Service Management Layer

SNC Subnetwork Connection

SNMP Simple Network Management Protocol

SPD Security Policy Database

SPF Shortest Path First

SSC Single Server Configuration

STP Spanning Tree Protocol

TCM Tandem Connection Monitoring

TCP Transmission Control Protocol

TDM Time Division Multiplexing

TTP Trail Termination Point

UDP User Datagram Protocol

UMTS Universal Mobile Telecommunications System

UNI User Network Interface

Unit In 8000 Intelligent Network Manager refers to a line or control card.

VCCV Virtual Circuit Connection Verification

VLAN Virtual LAN

VPLS Virtual Private LAN Service

VPN Virtual Private Network

VPWS Virtual Private Wire Service

VRF VPN Routing and Forwarding

VSI Virtual Switching Instance

WDM Wavelength Division Multiplexing

WiMAX Worldwide Interoperability for Microwave Access


6



Table of Contents

Table of Contents

About the Manual .............................................................................................................. 10

Objectives....................................................................................................................................................................... 10

Audience......................................................................................................................................................................... 10

Related Documentation ................................................................................................. ................................................. 10

Document Conventions...................................................................................................................................................11

Discontinued Products.....................................................................................................................................................11

Product Name Rebranding .............................................................................................................. ................................11Documentation Feedback................................................................................................................................................11

1 Introduction ................................................................................................................. 12

1.1 Supported Network Elements ..................................................................................................................... ......... 13

1.1.1 5500 Network Elements ...................................................................................................................... 13


1.1.3 7090 Packet Transport Platform Series ............................................................................................... 17

1.1.4 7100 Packet Optical Transport Series.................................................................................................. 18



1.1.7 8800 Smart Router Series.................................................................................................................... 33

1.1.8 mTera Universal Transport Platform................................................................................................... 34

1.2 Main Applications ................................................................................................................ ............................... 34

1.2.1 IP VPN ................................................................................................................................................ 36

1.2.2 Dense Wavelength Division Multiplexing........................................................................................... 37

1.2.3 VPLS VPN .......................................................................................................................................... 38

1.2.4 VLAN VPN ......................................................................................................................................... 39

1.2.5 Ethernet Pseudowire............................................................................................................................ 41

1.2.6 OTN Circuits ........................................................................................................ ............................... 42

1.2.7 ATM Pseudowire ................................................................................................................................. 44

1.2.8 TDM Pseudowire................................................................................................................................. 45

1.2.9 TDM Circuits....................................................................................................................................... 461.2.10 Ethernet First Mile Services ................................................................................................................ 46

1.2.11 Frame Relay DLCI Pseudowire.............................. ............................................................................. 47

1.2.12 HDLC Pseudowire.......... ..................................................................................................................... 48

1.2.13 Seamless MPLS........................................................................................................ ........................... 48

1.2.14 Internet Access ................................................................................................... ................................. 50

2 8000 Intelligent Network Manager Components and Architecture.........................51

2.1 Overall Architecture ............................................................................................. ............................................... 51

2.1.1 Typical Configuration ............................................................................................... ........................... 51


7



Table of Contents

2.1.2 Minimum Configuration ............................................................................................................. ......... 52

2.1.3 N-tier Architecture............................................................................................................................... 52

2.1.4 Object Server....................................................................................................................................... 53

2.1.5 Server Monitoring................................................................................................................................ 53

2.2 Workstations ............................................................................................................................. ........................... 53

2.3 Database Server .................................................................................................................... ............................... 55

2.3.1 The Role of the Database in 8000 Intelligent Network Manager........................................................ 55

2.3.2 Separate Performance Management Database and Performance Management Table Partitioning..... 55

2.4 Communication Server ............................................................................................. ........................................... 57

2.4.1 General...................................................................................... ........................................................... 57

2.4.2 Managing the Communication Servers ............................................................................................... 57

2.4.3 Fault Management in Communication Servers ................................................................................... 58

2.4.4 Backup Monitoring in Communication Servers.................................................................................. 58

2.4.5 Communication with Network Elements ............................................................................................ 58

2.4.6 Element Adapters ................................................................................................................................ 59

2.5 Management Server .............................................................................................................. ............................... 61

2.5.1 Service Processes................................................................................................................................. 622.5.2 Using Multiple Service Instances........................................................................................................ 64

2.5.3 Satellite Service ................................................................................................................................... 64

2.5.4 Fault Service........................................................................................................................................ 65

2.5.5 Northbound Interface........................................................................................................................... 65

2.6 Recovery Server ........................................................................................................... ....................................... 66

3 8000 Intelligent Network Manager Application Packages ....................................... 67

3.1 General.................................................................................... ............................................................................. 67

3.1.1 Other Software Packages..................................................................................................................... 68

3.2 Basic Package ..................................................................................................... ................................................. 68

3.2.1 Network Editor .................................................................................................................................... 68

3.2.2 Node Manager ..................................................................................................................................... 82

3.2.3 Customer Administration .................................................................................................................... 86

3.2.4 Fault Management System .................................................................................................................. 87

3.2.5 Trouble Ticket......................................................................................................... ............................. 95

3.2.6 Accounting Management..................................................................................................................... 96

3.2.7 Security Management.......................................................................................................................... 96

3.2.8 Scheduling Center................................................................................................................................ 97

3.2.9 OAM Management.............................................................................................................................. 98

3.2.10 IP Address Management....................... ............................................................................................. 100

3.2.11 IP Address Pool Management .................................................................................................. ......... 101

3.2.12 Automated Deployment.................................... ................................................................................. 1023.3 Provisioning Packages ............................................................................................ ........................................... 105

3.3.1 Router ..................................................................................................................... ........................... 105

3.3.2 VPN Provisioning.............................................................................................................................. 107

3.3.3 Tunnel Engineering ............................................................................................................................117

3.3.4 VLAN Manager..................................................................................................................................119

3.4 Testing Package ...................................................................................................... ............................................119

3.4.1 Overview .............................................................................................................. ..............................119

3.4.2 Packet Loop Test ............................................................................................................................... 120

3.4.3 Circuit Loop Test ............................................................................................................................... 134

3.5 Service Fault Monitoring Package ......................................................................................... ........................... 139

3.5.1 Service Fault Monitoring Windows................................................................................................... 140


8



Table of Contents

3.5.2 Service Management ......................................................................................................................... 140

3.6 Performance Management Package................................................................ ................................................... 141

3.6.1 Overview .............................................................................................................. ............................. 141

3.6.2 Performance Statistics ....................................................................................................................... 143

3.6.3 History Data Collection and Ageing ................................................................................................. 149

3.6.4 Performance Reporting...................................................................................................................... 149

3.6.5 Interface Utilization Threshold Monitoring ...................................................................................... 150

3.6.6 Trend Analysis................................................................................................................................... 151

3.6.7 Performance Overview Reporting Tool for 6300, 7090, 7100, 8600, 8800 and mTera UTP Network

Elements ............................................................................................................................................ 152

3.7 Recovery Package............................................................. ................................................................................. 153

3.7.1 Recovery Management System ......................................................................................................... 153

3.8 Service Viewing Package ......................................................................................................................... ......... 155

3.8.1 Service and Circuit Component View ............................................................................................... 155

3.9 Planning Package.............................. ................................................................................................................. 157

3.9.1 Fault Simulator .................................................................................................................................. 158

3.9.2 Network Capacity Calculator ............................................................................................................ 1583.10 8100 Service Computer ........................................................................................................ ............................. 160

3.11 Partitioned Package .............................................................................................. ............................................. 160

3.11.1 Hierarchy Levels for Partitioning ...................................................................................................... 160

3.11.2 Backbone Overview of Network....................................................................................................... 162

3.11.3 Backbone Network View.............................................................................................. ..................... 163

3.11.4 Regional Network View ..................................................................................................... ............... 164

3.11.5 Fault Management in Partitioned Network ...................................................................................... 165

3.11.6 VPN Provisioning and Tunnel Engineering in Partitioned Network................................................. 166

3.12 Unit Software Management Package ..................................................................................... ........................... 167

3.12.1 Element Software Management.............................................. ........................................................... 167

3.12.2 8100 Unit Software Management...................................................................................................... 169

3.13 Macro Package ....................................................................................................... ........................................... 1703.13.1 Macro Manager........................................................... ....................................................................... 170

3.13.2 Application Development Toolkit ..................................................................................................... 170

3.14 Web Reporter ........................................................................................................................ ............................. 171


9



About the Manual

About the Manual

Objectives

This manual provides an overview of 8000 Intelligent Network Manager. It contains descriptions

of 8000 Intelligent Network Manager features, components and architecture, as well as all major

software tools.

AudienceThis manual is designed for all those who wish to familiarize themselves with the functionality and

architecture of 8000 Intelligent Network Manager. It is assumed that you have a basic understanding

of network management systems and their functionality.

Related Documentation

The document numbering scheme consists of the document ID, indicated by numbers, and the

document revision, indicated by a letter. The references in the Related Documentation table below

are generic and include only the document ID. To make sure the references point to the latest

available document versions, please refer to the relevant product document program on the Tellabsand Coriant Portal by navigating to www.portal.tellabs.com > Product Documentation > Data

Networking > 8000 Intelligent Network Manager > Technical Documentation.


Third Party Hardware and Software Requirements

(76.8060-70222)

Describes all the needed third party software

components and versions (operating systems and

software versions) in the 8000 Intelligent Network

Manager system. Describes also the relevant

requirements and recommendations of the 8000

Intelligent Network Manager system.


Software Installation Manual (76.8060-70201)

Provides instructions on installing and configuring

8000 Intelligent Network Manager in different

computer platforms (workstation, servers).

8600 Smart Routers

8660 Smart Router FP5.0 Reference Manual

(76.8660-40124)

Describes network element features: subrack, fan

modules, timing module, CDCs, line cards and

IFMs.

8600 Smart Routers

8630 Smart Router FP5.0 Reference Manual

(76.8660-40123)

Describes network element features: subrack, fan

modules, CDCs, line cards and IFMs.

8600 Smart Routers

IP Forwarding and Traf fic Management

Configuration Guide (76.8600-50122)

Provides an overview of 8600 system IP forwarding

and traf fic management and instructions on how

to configure them CLI.


10

https://www.portal.tellabs.com/global/portal/home.jsp

https://www.portal.tellabs.com/global/portal/home.jsp



About the Manual

Document Conventions

This is a note symbol. It emphasizes or supplements information in the document.

This is a caution symbol. It indicates that damage to equipment is possible if the instructionsare not followed.

This is a warning symbol. It indicates that bodily injury is possible if the instructions are notfollowed.

Discontinued Products

Information on discontinued products can be found in Tellabs and Coriant Portal,

www.portal.tellabs.com.

Product Name Rebranding

Product names are being rebranded and as a result the product name format consists of a numerical

identifier and a descriptive part.

Additionally, the previous Tellabs 7300 product family is renamed and the individual product names

are also changed. The table below lists previous and new product names. You may see instancesof both the previous and the new product names in the customer documents during the transition

period to the new naming system.

Previous Product Name New Product Name

Tellabs® 7300 metro Ethernet switching series 7090 Packet Transport Platform Series

Tellabs® 7305 7090-05 CE

Tellabs® 7307 7090-07 CE

Tellabs® 7310 7310

Tellabs® 7325 7090-25 CE

Tellabs® 7345 7090-45 CE

Documentation Feedback

Please contact us to suggest improvements or to report errors in our documentation:

Email: [email protected]


11

https://www.portal.tellabs.com/

https://www.portal.tellabs.com/



1 Introduction

1 Introduction

8000 Intelligent Network Manager is an integrated network and service management system for

managing 5500 Digital Cross-Connect Series, 6300 Managed MSPP/Transport Series, 7090 Packet

Transport Platform Series, 7100 Packet Optical Transport Series, 8100 Managed Access System,

8600 Smart Router Series, 8800 Smart Router Series and mTera TM Universal Transport Platform

product families. It offers a Dashboard for performing all necessary functions to create, test and

monitor services provisioned on these product platforms. 8000 Intelligent Network Manager is a

multi-technology platform supporting IP VPN (RFC4364), DWDM optical, Layer 2 VPN, Ethernet,

G.709 OTN, ATM, TDM (PDH, SDH and SONET) and Internet access services provisioned on

top of the supported product families.

8000 Intelligent Network Manager is integrated in its entirety. The tools are integrated together,

they share and utilize the same data and they communicate with each other. The ef ficient data flow

between the tools is gained by the use of the same relational database for all the 8000 Intelligent

Network Manager tools. The database maintains an up-to-date status of the network, elements and

services and this status is shared in a real-time manner to all the tools and users. In a multi-user

environment, this ensures that all those who operate with the network are aware of events or actions

taken by other users in the network. In addition to maintaining the up-to-date status, 8000 Intelligent

Network Manager provides possibility for pre-planning of the network and services in advance.

The supported product families have been readily integrated within 8000 Intelligent Network

Manager and adapters for each product family are offered as an integrated part of the management

system. The network management system is thus ready to command and communicate with the

network elements without any additional modeling or adapter work. All communication to the

network and elements are designed to go through the network management system to ensure that the

consistency throughout the 8000 Intelligent Network Manager is maintained at all times.

With no single point of failure, 8000 Intelligent Network Manager is built to be a reliable and fault

tolerant system that performs well in a diverse environment and under variable circumstances. In

8000 Intelligent Network Manager, the needs of a growing network and operations have been

considered by ensuring the system scalability according to the size of the network and the number

of services and users.

8000 Intelligent Network Manager is designed to take full control over its own domain while keeping

in mind the requirements of operational support systems (OSS) and other domains. Northbound

interfaces can be used to adapt and integrate the system into other service provider’s systems. Via

the northbound interfaces, the OSS has access to the network infrastructure (e.g. elements andnetwork topology), the services (provisioning, monitoring and testing) and other OSS support data.

8000 Intelligent Network Manager brings a consistent yet adaptable way of managing not only the

elements but also the whole network and the services end-to-end within its domain.


12



1 Introduction

1.1 Supported Network Elements

1.1.1 5500 Network Elements

The 5500 Digital Cross-Connect Series of wideband and narrowband digital cross-connect

systems maximizes network capacity from the core to the edge, and offers the best combination of

functionality and density without compromise. The 5500 Series includes 5500 and 5500S Digital

Cross-Connects, scalable and carrier-class wideband systems that ef ficiently groom voice and data

traf fic over SONET and asynchronous facilities; and 5320L and 5320LS Digital Cross-Connects,

best-in-class density, narrowband systems that satisfy multiple cross-connect applications such as

3/1/0 grooming in wireless, mobile, ILEC and IXC markets.

Currently 8000 Intelligent Network Manager supports the 5500 and 5500S platforms, these are

collectively referred to as 5500/S.

5500 and 5500S

The 5500 and 5500S systems are available in several sizes. The 5500S system scales in-service

from 128 DS-3/STS-1 equivalent ports to a full 5500 system, up to 3072 DS-3/STS-1 equivalent

ports and beyond. 5500 and 5500S systems can grow in increments of one DS-3/STS-1 equivalents.

5500 and 5500S provide the following SONET functionality:

• Wideband DS-3/1

• Broadband DS-3/3

• DS-1, DS-3

• STS-1, STS-3c

• OC-3, OC-12


The 6300 Managed MSPP/Transport Series is a family of next-generation SDH network

elements, which offer multiple high-speed services and enable scalable utilization of the available

bandwidth. The nodes are supported similarly to the 8100 Managed Access System nodes,

providing tools for optimized use of the network elements in 8100 system networks. However, the

NM6300ct/NM2100ct Craft Terminal is used instead of Node Manager for configuring the nodes.

The following 6300 Series network elements, 6310 Edge, 6320 Edge, 6325 Edge, 6335 Switch,

6340 Switch, 6345 Switch and 6350 Switch are integrated into 8000 Intelligent Network Manager.

6310 Edge

6310 Edge Node is a complete add/drop or terminal multiplexer housed in a single, highly scalable

system. It is well-suited for access network applications and meets the requirements for customer

premises equipment. The node is available in two versions. The compact 1U-high version provides

you with a complete SDH node with 21 E1 lines. The 2U-high flexible version gives an extra

tributary service in addition to the 21 E1 lines.

Features:


13



1 Introduction

• Compact add-drop or terminal multiplexer (4/1)

• Convenient for outdoor cabinets

• Customer premises equipment; mobile network HUB sites

• 2/34/45/140 Mbps, STM-1, STM-4, Fast Ethernet and Gigabit Ethernet interfaces

• SNC/I and SNC/N protection

• VLAN, MAC and MPLS switching.

6320 Edge

6320 Edge Node has been designed to enhance the functionality of the access and regional part of

the SDH network. The node offers a complete, compact multi-service add/drop multiplexer and

terminal multiplexer with an STM-1 or STM-4 line interface. It supports a full range of PDH

interfaces, STM-1 optical or electrical interfaces as well as Fast Ethernet and Gigabit Ethernet.

Features:

• Super-compact single-board ADM/TM

• Upgradeable modular system

• 2/34/45/140 Mbps, STM-1, STM-4, Fast Ethernet and Gigabit Ethernet interfaces



6325 Edge

6325 Edge Node is a compact multi-service provisioning platform supporting SDH, PDH and data

services. High reliability and redundancy enable the node to be used not only in access networks,

but also in core networks. At only 1RU (44mm) in height, 6325 Edge Node is a complete, full-scale

SDH transport node. It offers speeds of up to 2.5 Gbps (STM-16) and enables a wide mix of services

from traditional SDH and PDH to colored WDM and IP interfaces. The compact design makes the

node an ideal choice for customer-located equipment.

Features:

• Compact multi-service provisioning platform

• 2 Mbps, 34 Mbps, 45 Mbps, STM-1, STM-4, STM-16, CWDM, DWDM, Fast Ethernet and

Gigabit Ethernet interfaces

• 80 ports 4/4 cross-connect

• 8 ports 4/3/1 switch matrix


• Redundant cross-connection matrices and power supplies


• CWDM and DWDM multiplexing and optical add/drop.


14



1 Introduction

Fig. 1 6325 Edge Node

6335 Switch

6335 Switch Node is a compact, full-featured multi-service provisioning platform (MSPP).

6335 Switch can handle SDH, PDH as well as data services in a compact and cost-effective

design. It offers reliability with full redundancy on the central switch matrix, the PDH interfaces,

synchronization functionality and power supplies. 6335 Switch Node can also be equipped as a

CWDM or DWDM multiplexer with the support of transponders, muxponders and repeaters.

6335 Switch Node is designed to fit anywhere in the SDH transport network. The cost-ef ficientand compact design makes it a logical choice for the access network, while the redundant

cross-connection matrices are well suited to core networks. Cross-connection redundancy makes

6335 Switch Node reliable as a HUB node handling high traf fic load. The combination of E1s,

STM-1s and Ethernet interfaces in one node makes 6335 Switch Node an important building block

in both GSM (2G) and UMTS (3G) mobile networks.

Features:

• Compact multi-service provisioning platform

• 2 Mbps, 34 Mbps, 45 Mbps, STM-1, STM-4, STM-16, STM-64, CWDM, DWDM, Fast Ethernet

and Gigabit Ethernet interfaces

• Redundant cross-connecting matrices, interface protection and redundant power supplies

• MAC, VLAN and MPLS Ethernet switching

• Support for differentiated service types enables customized service level agreements for individ-

ual customers

• WDM multiplex and transponder modules enable a traditional SDH node to be combined with a

WDM node in the same subrack

• Pluggable transceivers allow 6335 Switch Node to support a wide range of interfaces from tradi-

tional SDH over Ethernet to advanced WDM transceivers

• High reliability with fully redundant matrix protection and E1 equipment protection

• Network protection: SNC/I, SNC/N, MSP 1+1 and MS-SPRing

• Choice of 2RU and 7RU high subrack

Fig. 2 6335 Switch Node


15



1 Introduction

6340 Switch

6340 Switch Node is a third-generation multi-service provisioning platform designed for thetransport and delivery of converged services (voice, high-speed data and video-on-demand). It is

an SDH add/drop multiplexer or digital cross-connect with SDH 4/4 and 4/1 connectivity, and it

supports a wide range of physical interface options varying from 2 Mbps E1 to STM-16. Its main

strength is in regional and metropolitan networks where you can use the cross-connect functionality

for grooming and consolidation of traf fic from various sources.

Features:

• Add-drop multiplexer (16/4/1) and cross-connect in one element

• 132 or 48 ports 4/4 cross-connect (depending on version)

• 32 or 16 ports 4/3/1 cross-connect (depending on version)

• 2/34/45 Mbps, STM-1, STM-4, STM-16, Fast Ethernet and Gigabit Ethernet inter faces

• Colored STM-16 interfaces for 32 channel DWDM integration


• Full equipment redundancy


6345 Switch

6345 Switch Node is a multi-service provisioning platform, which has been specially designed to

enable a wide range of data, voice, and leased line applications. The unique combination of high

capacity and small footprint makes the unit ideal for compact ADM-64 or STM-16 ring-interworkingapplications, since multiple add/drop multiplexers can be configured within a single subrack, thus

avoiding external cabling and ensuring high uptime.

Features:

• Add-drop multiplexer and cross-connect in one element



• Colored STM-16 and STM-64 interfaces for 32 channel DWDM integration

• STM-1, STM-4, STM-16 and STM-64 interfaces• Fast Ethernet, Gigabit Ethernet and 10 Gigabit Ethernet interfaces

• Equipment protection of switch core, synchronization and power




16



1 Introduction

6350 Switch

6350 Switch Node is a third-generation high-capacity cross-connect suited for various data, voiceand leased line applications. This high-density system grooms and consolidates traf fic in the metro

and regional networks. 6350 Switch has a modular structure that enables you to configure add/drop

multiplexers and cross-connects from the same hardware platform.

Features:

• Add-drop multiplexer and cross-connect in one element



• Colored STM-16 interfaces for 32 channel DWDM integration

• STM-1, STM-4, STM-16 and STM-64 interfaces

• Fast Ethernet, Gigabit Ethernet and 10 Gigabit Ethernet interfaces

• Equipment protection of switch core, synchronization and power



1.1.3 7090 Packet Transport Platform Series

The 7090 Series is a product family offering a comprehensive end-to-end portfolio of Ethernet

switching products. The 7090 Series can combine with the 7100 Packet Optical Transport Series to build highly scalable connection-oriented Ethernet and carrier Ethernet networks and, when used

with the 8800 Smart Router Series, extends Ethernet services from IP/MPLS core networks.

8000 Intelligent Network Manager supports service provisioning based on provider bridging

(802.1ad) as well as LAG and G.8032 Ethernet ring based protection for the 7090 NEs.

Point-to-point VLAN services can be protected by resilient VLAN tunnels.

It is possible to manually discover the NE configuration of 7090-25 CE and 7090-45 CE using

8000 Intelligent Network Manager.

7090-05 CE Packet Transport Platform

7090-05 CE is a flexible Network Interface Device (NID) that can operate as a Transport NID or

Service NID to provide service demarcation. It includes the standard-based performance and OAM

features for transporting and delivering Carrier Ethernet services. It has 2 optical 10/100/1000

SFP-based Ethernet interfaces and 1 electrical 10/100/1000 UTP-based interface (3-port option).


7090-07 CE is a flexible Network Interface Device (NID) that can operate as a Transport NID or Service NID to provide service demarcation. It includes the standard-based performance and OAM

features for transporting and delivering Carrier Ethernet services. It has 5 ports supporting either

optical or electrical 10/100/1000 SFP-based Ethernet interfaces.


17



1 Introduction

7310 Ethernet Demarcation Device

7310 device is a 10 Gigabit demarcation device in one fixed rack unit. It has one integrated FANmodule, one integrated demarcation module with 2 optical 10 Gbps XFP-based Ethernet interfaces

and two removable power supply units.

7090-15 CEM Packet Transport Platform

7090-15 CEM is a flexible Network Interface Device (NID) that can operate as a Transport NID

or Service NID to provide service demarcation. It includes the standard-based performance and

OAM features for transporting and delivering Carrier Ethernet services. It has 3 ports supporting

optical 10 Gbps SFP+ or XFP-based Ethernet interfaces and 4 ports supporting optical 1 Gbps

SFP-based Ethernet interfaces.


7090-25 CE is a carrier-class layer 2 switch in one fixed rack unit. It has 24 optical 10/100/1000

SFP-based Ethernet interfaces.

7090-40 CEM Packet Transport Platform

7090-40 CEM is a carrier-class layer 2 switch supporting delivery of business Ethernet, broadband

data, Internet access services and metro Ethernet networking. The network element provides up

to 180 Gbps switching capacity. It has 26 optical 10/100/1000 SFP-based Ethernet interfaces,

4 optical 10 Gbps SFP+ or XFP-based Ethernet interfaces and 2 optical 40 Gbps QSFP+ based

Ethernet interfaces.


7090-45 CE is a carrier-class layer 2 switch supporting delivery of business Ethernet, broadband

data, Internet access services and metro Ethernet networking. The network element provides up to

40 Gbps throughput in two rack units. It has 24/48 optical 10/100/1000 SFP-based and at most 2/4

optical 10 Gbps XFP-based Ethernet interfaces.

1.1.4 7100 Packet Optical Transport Series

The 7100 Packet Optical Transport Series is a metro, dense wavelength division multiplexing

(DWDM) system based on a parallel architecture that provides scalable, non-service affectinggrowth to 88 protected wavelengths without network re-engineering. The system supports ITU-T

recommendation G.709 optical transport network (OTN) based transport, enabling transparent

high-capacity services. Services such as carrier Ethernet, video, storage area network, SONET and

SDH are carried on a shared infrastructure, scaling capacity as needed.

The 7100 OTS is built on unique, multi-patented system technologies that enable true next

generation multiservice delivery. It features an integrated dynamic optical core combined with an

intelligent services interface that delivers transponder, add/drop multiplexers (ADM), and switching

capability in client ranges of 100 Mbps to 100 Gbps. The 7100 OTS offers SONET/SDH ADM as

well as OTN ADM on a single blade. The dynamic optical core enables service providers to meet

today’s network needs while supporting the ability to effortlessly deploy additional nodes for future

expansion via a multi-degree reconfigurable optical ADM (ROADM).


18



1 Introduction

Hardware elements of the 7100 OTS provide support for higher bandwidth applications and

enhanced access. Hardware modules include 2.5G, 10G, 40G and 100G transponders, reconfigurable

multiplexers, multiplexers to support spur applications, packet multiplexers, colorless core

multiplexers for high-density metro applications, optical protection modules, SONET/SDH/Packet

module for digital cross-connects, intermediate- and long-reach amplifiers, system processors, anddata processors. Multirate transponders interface transmission equipment at client rates between

100 Mbps and 10.7 Gbps, including Fibre Channel, OC-3/STM-1, OC-12/STM-4, OC-48/STM-16,

OC-192/STM-64, OC-768/STM-256, OTU2, OTU3, OTU4, Gigabit Ethernet (GbE), 10 GbE,

40 Gbe and 100 GbE.

Both 7100 elements, the 7100 OTS and 7100 Nano, are supported by the 8000 Intelligent Network

Manager. The support includes the configuration of the hardware, the provisioning of services as

well as the monitoring of faults and performance data. The 8000 Intelligent Network Manager also

supports discovering elements that have already been deployed, either manually (using the GUI)

or automatically (no user action required). The manual discovery is also supported for the optical

circuits. The support is limited to the new circuit creation; the circuit modification or deletion

is not supported.

7100 Optical Transport System

7100 OTS is a dense wavelength division multiplexing (DWDM) system scaling up to eight

degrees. A fully-populated network element configuration is an 88-channel multi-shelf system

in a point-to-point, ring or mesh network. Each channel can be provisioned to carry from 100

Mbps to 100 Gbps signal capacity, or 100 Mbps to 2.488 Gbps broadband signals. Channels are

provisioned to either be added/dropped or optically passed-through a network element or for

unidirectional broadcast (including a drop-and-continue application). Optical channel levels may

also be regenerated at intermediate nodes through Optical-Electrical-Optical (OEO) conversion.

STS or VC facilities carrying GE signals can be grouped for concatenated transport between the

SMTM-U/SMTM-UX/SSM-D/SSM-X units.

7100 Nano Packet Optical Transport Platform

7100 Nano is a compact version of 7100 OTS that can add or drop up to 88 protected wavelengths

and pass through up to 88 simultaneous channels. This product provides an 8-degree DWDM

system (populated in 1-degree increments) comprised of up to eight 30-AMP shelves and a subset of 7100 OTS transponder modules. It can be deployed as a one-shelf optical line amplifier (OLA),

six-shelf direct connect application, 2-degree SBOADM with one main shelf and up to six port

shelves in 19- or 23-inch racks, or 8-degree SBOADM with up to four main shelves and up to six

port shelves in 19- or 23-inch racks.

7100 Packet Subsystem

One or more packet subsystems are supported in a 7100 NE based on the 7100 architecture. Each

packet subsystem consists of a group of packet modules (SMTM-P, TGIM-P and/or ESM20), one or

two switch fabric modules (SPFAB: SONET/SDH/Packet Fabric), and one or two corresponding

control modules (PSCM), so that the traf fic can be switched or forwarded within the switch domain

of the packet subsystem. The PSCM is SPM for 7100 OTS and SPM-N for 7100 Nano.

Packet-based transponder modules, SMTM-P, TGIM-P and ESM20, manage the ingress and egress

ports for the traf fic flow. The ingress and egress ports are connected to the SPFAB switch fabric.


19



1 Introduction

The 10G Subrate Multiplexer Transponder Module – Packet (SMTM-P) provides one 10 Gb

line-side facility interface and ten port-side facility interfaces that support signal rates of

10/100/1000 Mbps. Each of the ten port-side facility interfaces can be configured to support either

electrical or optical SFPs. The port-side optical interfaces support 100BaseFX and GbE.

The 10G Transponder - Packet Interface (TGIM-P) has one 10 Gb line-side facility interface and

one 10 GbE port-side interface (IEEE 802.3ae compliant). The TGIM-P is a one-slot wide card with

packet switching capability and one laser that is tunable across 88 wavelengths.

The Ethernet Switching Module - 20 Gigabits (ESM20) has a configurable amount of ports, with

up to two 10 Gb line-side facility interfaces and up to 16 GbE port-side interface (IEEE 802.3ae

compliant). The ESM20 can be deployed in three distinct configurations: 2 x 10G, 1x 10G + 10

x 1G and 16 x 1G. The ESM20 is also a one-slot wide card with packet switching capability and

one laser that is tunable across 88 wavelengths.

A proprietary logical entity called a virtual switch containing up to 4094 VLANs (a maximum of

4096 VLANs, but 2 VLANs are reserved for special use) is used. Each packet subsystem may

contain up to 32 virtual switches, which multiplies the VLAN address space by that factor per

packet-enabled shelf.

Supported features include MAC bridging, VLAN bridging (802.1Q), provider bridging (802.1ad),

an 802.3 compliant MAC client interface, packet security, packet fault management, packet

performance monitoring, multicasting, synchronized Ethernet, line-side resilient packet ring

protection, resilient VLAN tunnel tunnel-based protection and Ethernet Ring Protections (ERP).

8000 Intelligent Network Manager supports service provisioning based on provider bridging as

well as LAG and G.8032 Ethernet ring based protection for the packet subsystem of the 7100

OTS NEs. Point-to-point VLAN services can be protected by the resilient VLAN tunnels. The

working and protection paths of an RVT trunk can be built using VLAN trunks or G.8032 rings, or a

combination of both.


The 8100 product family is a network element family for managed access and transport solutions. It

consists of a number of nodes and NTUs designed to support business service and mobile access and

transport applications. The 8100 nodes can provide the functionality of a digital cross-connect and

multiplexer network element.

8110 network terminating units can be used to connect customer premises to an operator's POP

using an existing copper loop. The 8110 NTUs can be used in a stand-alone environment as well as

connected to 8100 nodes offering a fully managed customer premises equipment.

8100 node types are selected based on the access interface requirements. 8120 Mini Nodes and 8140Midi Nodes are typically used at customer premises, 8150 Basic Nodes, 8160 A111 Nodes, 8170

Cluster Nodes, 8184 Access Switches and 8188 Access Switches are typically used when there is a

requirement for bigger cross-connection devices or the 8100 nodes need to interoperate with an

SDH network.

8110 Network Terminating Unit CTE-R

8110 network terminating unit CTE-R has a maximum data rate of 4544 kbps over a 2-pair copper

line. 8110 CTE-R can act as an IP router, bridge or combined IP router and bridge (BRouter).


20



1 Introduction

8110 Network Terminating Unit CTE-S

8110 network terminating unit CTE-S is available with integrated X.21, V.35, V.36 or G.703interfaces. 8110 CTE-S has a maximum data rate of 4544 kbps over a 2-pair copper line.

8110 Network Terminating Unit CTE-R/208

8110 network terminating unit CTE-R/208 has a maximum data rate of 128 kbps. It has a

10/100-BaseT Ethernet access interface. The CTE-R/208 can act as an IP router, bridge or combined

IP router and bridge (BRouter).

8110 Network Terminating Unit CTE-S/208

8110 network terminating unit CTE-S/208 is available with integrated X.21, V.35, V.36 or G.703

interfaces and it is targeted to lower data rate applications. 8110 CTE-S/208 has a maximum datarate of 128 kbps.

8110 G.SHDSL Network Terminating Unit CTE2-R

8110 G.SHDSL network terminating unit CTE2-R has a maximum data rate of 12,224 kbps over a

4-pair copper line. It is designed for high-speed corporate LAN interconnect applications, where

service reliability and service differentiation is needed. It has a 10/100-BaseT Ethernet access

interface. The CTE2-R can act as an IP router, bridge or combined IP router and bridge (BRouter).

8110 G.SHDSL Network Terminating Unit CTE2-S

8110 G.SHDSL network terminating unit CTE2-S is primarily designed for leased line data

networks with fast and easy installation. With the G.703 interface it is also suitable for connecting,

for example, mobile base stations or PBXs to the transmission network. 8110 CTE2-S is available

with integrated X.21, V.35 or G.703 interfaces and the DSL transmission is based on ITU-T

G.SHDSL technology. 8110 CTE2-S has a maximum data rate of 8,128 kbps and it has AC and DC

power feed options.

8110 Network Terminating Unit CTU-R

8110 network terminating unit CTU-R is a high-speed NTU designed for managed data access with

rapid deployment. It is a network terminating unit using extended ETSI HDSL based technology.

8110 CTU-R has a maximum data rate of 4,544 kbps over 2 pairs with integrated IP routing. With

a direct 10/100-Base-T Ethernet interface it is able to offer data access services without the needfor a customer premises wide area network routing infrastructure. Typically such services are

dedicated to corporate Intranet and Internet access.

8110 Network Terminating Unit CTU-S

8110 network terminating unit CTU-S is primarily designed for managed serial data access with

fast and easy installation. With the G.704 interface it is also suitable for connecting, for example,

mobile base stations or PBXs to the transmission network. 8110 CTU-S is available with integrated

X.21, V.35 or G.703 interfaces and the DSL transmission is based on ETSI HDSL technology. 8110

CTU-S has a maximum data rate of 4,544 kbps and it has AC, DC and remote power feed options.


21



1 Introduction

8110 Network Terminating Unit CTU-512

8110 network terminating unit CTU-512 uses extended ETSI HDSL based technology and it istargeted to lower data rate applications. It has a maximum data rate of 512 kbps and it is available

with V.35 and X.21 interfaces.

8110 Network Terminating Unit G2M

8110 G.703 network terminating unit G2M is connected to the 8100 Managed Access System with

physical 2 Mbps G.703/704 interfaces in 8100 nodes. 8110 G2M has an integrated V.35 interface

and a maximum data rate of 1,984 kbps.

8110 Network Terminating Unit OTU-2M and 8110 Network Terminating Unit OTU-RP

8110 network terminating units OTU-2M and OTU-RP are primarily designed for connectingmobile network micro base stations to the rest of the mobile transmission network. They can also be

used in leased line networks to connect, for example, PBXs to the 8100 nodes.

8110 Network Terminating Unit STE-10M

8110 network terminating unit STE-10M has a maximum data rate of 12,160 kbps over a 4-pair

copper line. It is designed for high-speed corporate LAN interconnect applications, where service

reliability and service differentiation is needed. It has a 10/100-BaseT Ethernet access interface.

8110 STE-10M can act as an IP router, bridge or combined IP router and bridge (BRouter).

8115 Network Terminating Unit

8115 NTU is an Ethernet in the First Mile (EFM) terminating unit available with 2-wire or 4-wire

pairs based on the SHDSL technology supporting reliable, spectral compatible and symmetrical

services of 192 kbps to 15.3 Mbps per wire pair. 8115 NTU supports bonded high speed symmetrical

carrier Ethernet services on the MSAN/DSLAM platform. The comprehensive traf fic management

at the user network interface (UNI) and the integrated TDM CES interworking function enables the

implementation of high revenue services on every broadband platform.

8120 Mini Node

8120 Mini Node is a small cross-connect device operating as either part of the 8100 network or as a

stand-alone cross-connect device managed locally. It can integrate multiple services and transmit

them over a single access line.

8130 Micro Node

8130 Micro Node is a compact, cost-effective node especially targeted for mobile networks. It is

ideally suited to be located at base station sites where space is usually limited. It is often used in

a reliable ring structure to connect base stations to the backbone network. To guarantee the best

service availability at base station level, 1+1 protection can be implemented.


22



1 Introduction

8140 Midi Node

8140 Midi Node is a flexible access node for customer premises. The 8140 Midi subrack consistsof eight slots. The heart of the 8140 Midi Node is the one-slot wide multi-functional unit XCG,

which combines the functions of a cross-connect unit and control unit and offers, in addition,

four 2Mbps G.703 interfaces.

8150 Basic Node

8150 Basic Node can be used as a component in the local exchange or backbone layer of the

network, as well as in customer premises, depending on the needed services and applications. An

8150 Basic Node consists of a single or double 19–inch subrack with a total cross-connect capacity

of 64 Mbps. Some common units are found in every 8150 Basic Node. These are the power

supply, control and cross-connect units. Any of the free slots can be filled with a variety of base

units and interface modules.

8155 Access Switch

8155 Access Switch is an Ethernet in the First Mile (EFM) aggregation node. The 8155 Access

Switch offers Ethernet and TDM services over packet or TDM networks exploiting the existing

copper or fi ber access infrastructure.

8160 A111 Accelerator Node

8160 A111 Accelerator Node can be used for service grooming and consolidation at a POP site or at

several POP sites along a ring. It can also be used for high-capacity service delivery to customer

premises. The 8160 A111 Accelerator Node integrates SDH ADM and FlexMux functionalitiesin one double 19–inch subrack. It has a 4/1 matrix for adding/dropping traf fic from the aggregate

interfaces and a 1/0 matrix to cross-connect the added/dropped traf fic from the 4/1 matrix and the

traf fic coming from the tributary interfaces. The add/drop capacity is 256 Mbps and MSP 1+1

and sub-network connection protection options are available. Also interface unit protections and

trunk and circuit level protections are supported.

8170 Cluster Node

8170 Cluster Node is a 1/0 digital cross-connect that terminates up to 512 Mbps of non-blocking

cross-connect capacity. The node can provide a large-scale interconnection point in the network.

Depending on the needed services and applications, 8170 Cluster Node consists of a master subrack

and from one to eight slave subracks. It grooms and fi

lls traf fi

c to make the most ef fi

cient use of E1, and higher-order, transport facilities. The 8170 Cluster Node can be equipped with STM-1 and

synchronous 34M interfaces to implement cost-effective SDH transport network connectivity.

8184 Access Switch and 8188 Access Switch

8184 Access Switch and 8188 Access Switch nodes replace 8160 A111 Accelerator Node and havemuch bigger capacity. Both nodes have the same cross-connection capacity, but they use a different

size of subrack. The 8188 Access Switch has a double subrack (19-inch) and more slots for X-bus

interface units than the 8184 Access Switch that uses a single subrack (19-inch).


23



1 Introduction

The applications of these nodes are the same as with the 8160 A111 Accelerator and 8170 Cluster

Nodes. The 8188 Access Switchis used as an access node for grooming nx64 kbps - nx2 Mbps

services into STM-N/VC-4/VC-12/P12s, and the 8184 Access Switch is used as a 1/0 server node

beside 6300 nodes for grooming small nx64 kbps signals into VC-12.

Both nodes use the GMX2 SDH interface and cross-connect unit. The other units (SCU-H, PFU,

X-bus interface unit) are the same as in the 8160 A111 Accelerator Node. The GMX2 unit supports

STM-16, STM-4 and STM-1 interfaces, and SPF interface modules are utilized.

4/4 cross-connection capacity is 72 x AU-4.

• 1-2 x STM-16

• 4-8 x STM-4 or STM-1 interfaces

• 8 x VC-4 terminations into 4/1 cross-connection

4/1 cross-connection capacity is 16 x TUG ports.

• 8 x VC-4

• 504 x VC-12 towards 1/0 cross-connection

1/0 cross-connection capacity is max. 760 x 2 Mbps ports (1.5 Gbps)

• 504 x VC-12

• 4 x X-bus (8184 Access Switch) = 128 x 2M ports

• 8 x X-bus (8188 Access Switch) = 256 x 2M ports

The supported protections are:

• cross-connection core (GMX2) protection,

• STM-N MSP 1+1,

• 4/4 SNC/I,N,

• 4/1 SNC/I,N and

• 1/0 circuit and trunk recovery with 8000 Intelligent Network Manager.


24



1 Introduction

Fig. 3 8184 Access Switch

Fig. 4 8188 Access Switch


25



1 Introduction


The 8600 Smart Router Series product family is designed for providing managed 2G/3G mobiletransport, Ethernet, broadband service aggregation and IP VPN services. It has specifically been

designed to extend MPLS based services from the core network into access networks. Essential

technologies here include the following:

• MPLS for tunneling the customer traf fic through the operator network, both in core network and

in access networks.

• RSVP for managing traf fic engineered MPLS LSPs with bandwidth reservations, and optionally

operator-defined routes.

• DiffServ for managing different service classes with different QoS characteristics.

• Layer 3 (IP) VPNs based on BGP and MPLS for implementing many-to-many layer 3 connec-

tivity between customer sites through the operator network.

• Layer 2 VPNs based on pseudowires for implementing point-to-point layer 2 (TDM, ATM, Eth-

ernet, Frame Relay and HDLC) connectivity between sites through the operator network.

• BGP for distributing customer routes through the operator network between the service end-

points.

• OSPF and IS-IS for routing IP traf fic inside a single core/access network.

• Ethernet, ATM, Frame Relay and TDM as interfacing and access aggregation technology, as

an alternative to MPLS in the access network.

• Traf fic Engineering (TE) extensions for RSVP and OSPF protocols to reserve capacity for LSPs

aware of DiffServ based service classes and to select the used path based on available capacity

for the intended service class(es).

8602 Smart Router

The 8602 Smart Router is an optimized cell site router for macro and small cell backhauling. It

extends the Smart Router portfolio further down to the access network, enabling the operator to

utilize IP/MPLS as a unified technology down to the small cell sites. The 8602 Smart Router is a

perfect fit for IP or Ethernet-based traf fic aggregation with full QoS awareness and IP routing

capabilities. The 8602-A has AC and DC powering options and two 1000BASE-X Ethernet ports

and four 100/1000BASE-TX Ethernet RJ-45 ports. The 8602-D has AC and DC powering options

and six 1000BASE-X Ethernet ports.


26



1 Introduction

Fig. 5 8602 Smart Router

8605 Smart Router

The 8605 Smart Router is a compact and fully managed mobile cell site node with multiprocotol

support. It is designed for cost-ef ficient delivery of 2G and 3G voice and data services over a

diverse set of access and uplink interfaces. The switch has 16 x E1/T1 multiservice interfaces, 2

fixed 10/100 Mbps Ethernet ports as well as either 2 optical Ethernet uplink ports with SFPs or 2

x 10/100/1000 Mbps electrical Ethernet ports. It supports all relevant protocols for cost-ef ficienttransport of GSM, CDMA, CDMA-2000, EV-DO and WCDMA R99/R5 traf fic.

Fig. 6 8605 Smart Router AC


27



1 Introduction

Fig. 7 8605 Smart Router DC

8606 Ethernet Aggregator

The 8606 Ethernet Aggregator is a cost-ef ficient Ethernet switch for aggregating multiple customers

in dense locations to 8660 Smart Router, 8630 Smart Router or 8620 Smart Router. The switch has

24 10/100 Mbps Ethernet ports and four Gigabit ports.

8607 Smart Router

The 8607 Smart Router is a compact and highly modular access element with multiprotocol support.

Integration of Ethernet, DSL and pseudowire technology makes it attractive for 2G, 3G and WiMAX

cell sites and network evolution. Because of its small size and flexibility, 8607 Smart Router is

optimal for service providers’ access networks at small traf fic aggregation points or cell sites. The

high level of interface and power feed modularity enables meeting various site requirements and

optimizing the inventory with the same product. Due to the integrated DSL functionality, which is

one of the transport options, there is no need for an external NTU to provide the DSL part. Versatile

service capabilities, including support for TDM, ATM, HDLC and Ethernet based connections as

well as IP routing, enable the migration of 2G TDM and 3G ATM, Ethernet or IP based networks

into a single network infrastructure. 8607 Smart Router has packet based forwarding with QoS

support enabling network optimization for voice and data services.


28



1 Introduction


8609 Smart Router

The 8609 Smart Router is a compact, environmentally hardened network element with multiprocotol

support. It has 12 fixed Gigabit Ethernet ports and two slots for interface modules. Versatile service

capabilities, including support for TDM, ATM, HDLC and Ethernet based connections as well as IP

routing, enable the migration of 2G TDM and 3G ATM, Ethernet or IP based networks into a single

network infrastructure. 8609 Smart Router has packet based forwarding with QoS support enabling

network optimization for voice and data services.



29



1 Introduction

8611 Smart Router

The 8611 Smart Router is a 2RU high environmentally hardened network element with multiprocotolsupport and completely modular design. It can be equipped with redundant switching and control

modules (SCM) for carrier grade reliability and has seven slots for physical line modules. Versatile

service capabilities, including support for TDM, ATM, HDLC and Ethernet based connections as

well as IP routing, enable the migration of 2G TDM and 3G ATM, Ethernet or IP based networks

into a single network infrastructure. 8611 Smart Router has packet based forwarding with QoS

support enabling network optimization for voice and data services.


8615 Smart Router

The 8615 Smart Router is a compact 1U high IP, MPLS and Ethernet capable aggregator device

for 10 GE access rings. It provides 30 Gbps throughput with 10 GE and 1 GE interfaces and it is

targeted both for mobile backhaul and business services applications. 8615 Smart Router supports

IP routing, IP VPNs, MPLS switching and Ethernet switching. MPLS enabled services (IP VPN,

MPLS and pseudowires) are supported.



30



1 Introduction

8620 Smart Router

The 8620 Smart Router is a modular integrated access device. It can be used in the customer premises of high-end business customers or as a high-capacity aggregation element. 8620 Smart

Router offers carrier class operation, cost ef ficiency and QoS capabilities in a small tabletop or 19"

rack-mountable design. The same interface modules (IFMs) can be used both in 8620 Smart Router,

8630 Smart Router and the 8660 Smart Router except for 1xSTM-16 POS, which can only be used

in the 8630 Smart Router and 8660 Smart Router.

Fig. 12 8620 Smart Router AC

Fig. 13 8620 Smart Router DC

8630 Smart Router

The 8630 Smart Router is a modular, compact router positioned to hub sites in mobile networks.

8630 Smart Router has 6 slots with two slots reserved for redundant power/control cards. The

remaining 4 slots are available for line cards.


31



1 Introduction


8660 Smart Router

The 8660 Smart Router is a modular, scalable router positioned to RNC and large hub sites in

mobile networks. In fixed networks it can act either as a PE router on the edge of an MPLS core

network or as an access aggregator in an MPLS-based access network. In addition to this, it can also

be used as a P router in an MPLS core network or as a general-purpose IP router in places where

good scalability and redundancy is required.

The rack of 8660 Smart Router has 14 slots, of which slots number 1 and 14 are reserved for two

redundant power/control cards. The remaining 12 slots are available for line cards.

The 8660 Smart Router R2 subrack can be equipped with two redundant 8660 Smart Router R2

DC48 Power Input Modules (PIM) for supporting the maximum configuration of Ethernet line

cards (ELC1) in the subrack.


32



1 Introduction

Fig. 15 8660 Smart Router R2 Subrack

1.1.7 8800 Smart Router Series

The 8800 Smart Routers are high-performance next-generation multiservice edge routers. The

8800 Smart Routers support any-to-any layer 2 and layer 3 network and/or service interworking.

They provide service providers a graceful migration to a converged MPLS-enabled IP network.The 8800 Smart Routers combine Quality of Service and security with powerful MPLS traf fic

engineering capabilities.

The 8800 Smart Routers provide comprehensive standards-based signaling and routing support

including BGP, MP-BGP, OSPF, IS-IS and PIM-SM as well as LDP and RSVP-TE for MPLS

signaling and traf fic engineering.

8830 Smart Router

The 8830 Smart Router is a compact network element in the 8800 Smart Routers product family.

It can be equipped with up to 16 PLMs and provides the same fully-redundant platform for

carrier-class reliability as 8860 Smart Router and 8840 Smart Router. It can be equipped with the

same module options as the other 8800 Smart Routers.


33



1 Introduction

8840 Smart Router

The 8840 Smart Router provides 240 Gbps worth of full-duplex switching capacity. It has threeSCCs and 12 slots for ULCs with 4 modules in each line card. The same ELCs, ULCs and PLMs

may be used in 8840 Smart Router as in 8860 Smart Router.

8860 Smart Router

The 8860 Smart Router is a multiservice switch with 320 Gbps full-duplex switching positioned at

the edge of the core and in the core network for multiservice and mobile applications. The network

element has three switch and control cards (SCC), such that one of the switch cards may backup the

two other switch cards. Each network element has 16 slots for universal line cards (ULC). Each

ULC may be equipped with 4 physical line modules (PLM) with a variety of different module types.

In addition to ULCs, also Ethernet line cards (ELC) may be used in the network element.

1.1.8 mTera Universal Transport Platform

The mTera UTP is a metro multiplexing and switching system based on a parallel architecture

that provides scalable, non-service affecting growth without network re-engineering. The mTera

UTP supports ITU-T Recommendation G.709 Optical Transport Network (OTN)-based transport,

enabling transparent high-capacity services. Services such as Carrier Ethernet, video, Storage Area

Network, SONET, and SDH are carried on a shared infrastructure, scaling capacity as needed.

1.2 Main Applications

The main applications of the 8000 Intelligent Network Manager system are:

• Mobile transport in LTE, 3G and 2G RAN

• Optical networking

• Managed voice and data leased line business services

• Ethernet First Mile services

• Managed LAN interconnection services

• Managed IP VPNs

• Managed VPLS VPNs

• Broadband service aggregation

• Carrier Ethernet and business services

• Networks based on the Seamless MPLS architecture

These applications are supported by a suite of connectivity services, which offer scalability,

security, manageability and QoS comparable or exceeding the levels of current telecom network

infrastructures. The 8000 Intelligent Network Manager system offers the following connectivity

services:


34



1 Introduction

• IP VPNs providing many-to-many connectivity through the network. This connectivity service

is used mainly in the managed IP VPN application and in LTE networks.

• DWDM optical wavelength (channel) management. Optical channels can be used to carry purely

optical signals, SDH circuits and Ethernet services in a single optical channel. The DWDMsystem can be deployed either in a ring or mesh topology.

• Ethernet switching using VPLS VPNs. For many-to-many Ethernet connectivity, VPLS VPNs

can be used and configured on 8600 and 8800 network elements. The VPLS service specified

in RFC 4762 (Virtual Private LAN Service Using Label Distribution Protocol Signaling) is sup-

ported, which allows creating private Ethernet switching networks built of virtual switch in-

stances (VSI) interconnected with MPLS pseudowires.

• Ethernet switching using VLAN VPNs. For many-to-many Ethernet connectivity, VLAN VPNs

can be used and configured on 6300, 7090, 7100, 8100 and 8800 network elements. In the 8800

network element the VLAN VPN service is terminated to a VPLS/PW VPN service. Ethernet

switching is done in Ethernet switching capable units and the Ethernet traf fic transported over

shared TDM pipes in the 6300 and 8100 based network and optical channels in the 7090 and 7100

based networks. Due to the statistical nature of the Ethernet traf fic, the operator may choose tooversubscribe the network.

• Ethernet tunneling over MPLS using Ethernet PWs providing point-to-point connectivity through

the network. The PWE3 tunneling method is used. This point-to-point service is also sometimes

referred to as virtual private wire service (VPWS). Ethernet pseudowires are used both in the

managed Ethernet services application and broadband service aggregation application.

• G.709 OTN services. As the DWDM circuits, the OTN circuits can be used to carry different

types of signals across a network. Unlike the DWDM circuits, rerouting OTN circuits does not

require any re-configuration of the underlying hardware (e.g. cabling) leading to lower overall

costs in the network operation.

• ATM tunneling over MPLS using ATM pseudowires. ATM pseudowires provide point-to-point

connectivity through the network for tunneling ATM circuits over an MPLS or IP infrastructure.The PWE3 (pseudowire emulation edge-to-edge) tunneling method is used to tunnel the ATM

traf fic. This point-to-point service is sometimes also referred to as a virtual private wire service

(VPWS). This is the main connectivity service used in the mobile transport application for 3G

traf fic in R99 and R4 networks for transporting traf fic between the base stations (nodes B) and

the radio network controllers (RNCs). ATM tunneling can also be used in the broadband service

aggregation application for tunneling traf fic from ATM DSLAMs over an MPLS infrastructure.

• TDM tunneling over MPLS using TDM pseudowires (PWs). TDM pseudowires provide point-

to-point connectivity through the network for tunneling TDM bit streams over an MPLS infra-

structure. The PWE3 tunneling method is used. TDM pseudowires can be used to transport 2G

traf fic in mobile radio access networks between the base station and the base station controller

over an MPLS-based access network. TDM pseudowires can also be used to connect mobile

switching centers together over an MPLS backbone. Native nx64 kbps and 1.5/2 Mbps PDH as

well as nx64 kbps and 1.5/2 Mbps PDH bit streams over SDH/SONET are supported.

• PDH and SDH circuit management for the 1/0, 4/1 and 4/4 layers. TDM circuits can be used to

provide leased line services and mobile transport for 2G and 3G RAN networks. TDM circuits

can also be used for LAN interconnection services.

• Frame Relay and HDLC tunneling over MPLS using Frame Relay DLCI and HDLC pseudowires.

Frame Relay/HDLC pseudowires provide point-to-point connectivity through the network for

tunneling Frame Relay PVCs or other HDLC based services over an MPLS infrastructure. The

PWE3 tunneling method is used. Frame Relay/HDLC pseudowires can be used e.g. for trans-

porting GPRS or CDMA2000 1xRTT traf fic.


35



1 Introduction

• SONET circuit management for the STS-1 and STS-3c layers. SONET high-order circuits can

be used to provide similar services as SDH 4/4 circuits. SONET circuits can be configured and

used on the 5500 and 7100 network elements.

• Basic IP routing for broadband service aggregation applications.

Below, the different connectivity services are described more in detail.

1.2.1 IP VPN

The BGP/MPLS VPN method is the predominant and most scalable way to build MPLS-based

connectivity services. The service is based on RFC4364, which defines the MPLS/BGP-4-based

VPN implementation. Adding a new site to the VPN is easy and automated by the use of BGProuting advertisements. All the traf fic traversing through the VPN can be classified, and traf fic

quality can be handled properly through the network. The VPN allows any traf fic, including voice,

to be transported. IP traf fic from Ethernet frames or ATM/frame relay circuits may be terminated

and routed over the VPN. IP VPN services are used for example in LTE, LTE-Advanced (LTE-A)and 3G mobile backhaul networks.


36



1 Introduction

Fig. 16 Standard RFC4364 Based BGP/MPLS VPN

1.2.2 Dense Wavelength Division Multiplexing

Dense wavelength division multiplexing (DWDM) is an optical technology used for increasing the

capacity and flexibility of the optical infrastructure. In a DWDM system, multiple optical signals

are transmitted over multiple optical wavelengths (channels) on a single optical fi ber. The optical

layer interfaces the digital layer at the optical termination equipment, which can be considered a

part of both the electrical and the optical layer. The optical layer provides multiplexing schemes

and management that are not present on the digital layer of the network. This optical infrastructure

supports e.g. multiple data rates (for example, 622 Mbps, 2.5 Gbps, 10 Gbps) and SDH signal rates.

DWDM units are available for the 6300 and 7100 network elements.


37



1 Introduction

Fig. 17 Ethernet Services and SDH Circuits over a DWDM Network using 6300, 7100 and

8600 NEs

1.2.3 VPLS VPN

VPLS VPNs can be used to provide managed LAN interconnection services. A network of virtual

switch instances (VSI) interconnected with MPLS pseudowires is provisioned per VPLS VPN.

Customer devices are connected to the VSIs, and see the VPLS service as a large distributed

Ethernet switch. Because the VSIs ar e separate to each VPLS VPN, traf fic of different customers is

completely separated from each other.

VPLS VPNs are supported on 8600 and 8800 network elements. Both non-hierarchical and

hierarchical (H-VPLS) services are supported.


38



1 Introduction

Fig. 18 H-VPLS Service

1.2.4 VLAN VPN

VLAN VPNs can be used to provide managed LAN interconnection services. A VLAN tag is added

to the Ethernet frame to identify the customer at the ingress and the VLAN tag is then removed atthe egress point before forwarding the frame at the other endpoint of the VLAN VPN. The frames

are switched based on the VLAN tag and the Ethernet MAC address. A VLAN VPN may have

several endpoints in contrast to Ethernet pseudowires that only support point-to-point Ethernetconnections. TDM circuits are provisioned between the Ethernet switching points and overbooking

of these transport trunks can be exercised due to the statistical nature of the Ethernet traf fic.

Ethernet switching units are available in the 6300, 7090, 7100 and 8100 network elements. In

addition, a VLAN VPN service can be terminated to a VPLS/PW VPN service in an 8800 network

element. For a protected point-to-point service using the open RVT solution in the 7090 network,

the termination towards the VPLS service in the 8800 network provides dual homing i.e. there aretwo termination endpoints towards the VPLS service.


39



1 Introduction

Fig. 19 6300/8100 Ethernet Packet Network


40



1 Introduction

Fig. 20 7100 Ethernet Packet Network

1.2.5 Ethernet Pseudowire

Ethernet pseudowires are most suitable for those connections that need network layer transparency

also for other than IP protocols. The Ethernet pseudowires are based on the PWE3 architecture. The

Ethernet pseudowires are point-to-point connections much like with Frame Relay virtual circuits or

TDM leased lines. Connections are implemented in the network in such a way that the traf fic is

mapped to MPLS LSPs. If VLANs are used in the network, it is possible to map traf fic from each

VLAN into a separate connection. This provides full VLAN transparency. It is also possible to

terminate Ethernet traf fic from frame relay circuits and transport it over an Ethernet pseudowire.

Service VLANs can be used to aggregate traf fic from multiple Ethernet interfaces to a single

aggregated interface by adding a VLAN tag to the Ethernet frames.

A service class specifying the QoS treatment the traf fic gets in the MPLS network can be defined for

each connection separately.


41



1 Introduction

Fig. 21 Ethernet Pseudowire

1.2.6 OTN Circuits

The 7100 Packet Optical Transport Series and mTera Universal Transport Platform supports the

ITU-T Recommendation G.709 optical transport protocol (also known as Optical Transport Network

(OTN)). The OTN is intended to function as an evolutionary step form legacy TDM (SDH/SONET)transport by reducing the inherent complexity of these protocols, and thereby, lowering the overall

capital/operational expenditure associated with such networks.

The G.709 OTN services can be used to transparently transport e.g. SDH/SONET, Ethernet and

optical services across a DWDM network. At the ingress node, the client signal is mapped to

a corresponding Optical Payload Unit (OPU) which in turn is mapped into an Optical Data Unit(ODU). The ODU can then be switched or multiplexed into a higher layer ODU for transportation

across the network. An example is shown in the figure below. Rerouting the ODU is possible at

any point, without any need to re-configure the optical cabling.

The 7100 OTS and mTera UTP as well as 8000 Intelligent Network Manager support the following

ODUks: ODUflex, ODU0, ODU1, ODU2, ODU2e, ODU3 and ODU4.


42



1 Introduction

Fig. 22 OTN Circuits

ODUk Circuit Tandem Connection Monitoring

Customers typically monitor ODUk services end-to-end using the the ODUk PM overhead. The

TCM field is therefore reserved exclusively for customer use and should not be used by any operator

whose network the ODUk service is passing through. The Tandem Connection Monitoring (TCM)

functionality implemented in the network elements allows monitoring the quality of the ODUk

services (i.e. circuits in 8000 Intelligent Network Manager) over a subsection of the network. This

becomes more important if the service passes through many operator networks, as TCM makes it

possible to monitor which subsections of the service are working properly, or having too manyerrors. TCM can also be used for triggering protection switching when a subsection is out of order.


43



1 Introduction

Fig. 23 TCM Confi guration for ODUk Circuit Passing Multiple Networks Domains

1.2.7 ATM Pseudowire

ATM pseudowires are used in the mobile application for transporting the ATM traf fic over an MPLS

infrastructure. The ATM traf fic is encapsulated in the hub site node in an MPLS packet according

to the PWE3 architecture. The MPLS packet is then tunneled over an MPLS infrastructure which

may be, for instance, an SDH/SONET or Gigabit Ethernet ring. At the RNC site the ATM traf fic isdecapsulated from the MPLS packet and aggregated onto an unchannelized STM-1/OC-3c interface

towards the RNC. Either an ATM VPC or an ATM VCC may be tunneled in an ATM pseudowire.

Three mapping modes are supported for ATM pseudowires: N-to-one cell mode, one-to-one cell

mode and AAL5 SDU mode.

If no MPLS infrastructure is available, pseudowires can also be transported over an IP infrastructure

using IP tunnels. A typical application for MPLS over IP is the transport of Node B traf fic over

DSL lines to the RNC.


44



1 Introduction

Fig. 24 ATM Pseudowire

1.2.8 TDM Pseudowire

TDM pseudowires are used in the mobile application for transporting TDM traf fic over an MPLS

infrastructure. The TDM pseudowires are based on either the Structure-Agnostic Time Division

Multiplexing (SAToP) or the Structure-aware TDM Circuit Emulation Service over Packet Switched

Network (CESoPSN) specifications. The TDM payload is encapsulated in the ingress node in an

MPLS packet and tunneled over an MPLS infrastructure to the egress node. At the egress node the

TDM traf fic is decapsulated from the MPLS packet and the original TDM bit stream is reconstituted.

In SAToP pseudowires, the bit stream is encapsulated in MPLS without considering any possible

structure that may be imposed on the bit stream. In CESoPSN pseudowires, nx64 kbps channels are

extracted from the bit stream and encapsulated in an MPLS packet. CESoPSN pseudowires allow

traf fic grooming and save bandwidth when only a few of the nx64 kbps channels in an interface

carry user traf fic. SAToP pseudowires minimize delay and are the most bandwidth ef ficient when

the entire E1/T1 port needs to be transported over the MPLS network.

Fig. 25 TDM Pseudowire


45



1 Introduction

1.2.9 TDM Circuits

TDM circuits are used for providing leased line services and transport in 2G and 3G radio accessnetworks. Both PDH and SDH are widely used in these applications as the operator usually has

an existing PDH/SDH infrastructure that can be utilized for these applications. The 8100 network

elements have been optimized to provide nx64 kbps and E1 PDH circuits as well as connectivity to

SDH networks through mapping of PDH circuits to nxVC-12 and VC-4 SDH containers. The 6300

network elements have been designed for providing cost-ef ficient nxVC-12, nxVC-3 and nxVC-4

SDH connections. The 7100 network elements support n x VC-4 SDH connections.

The SONET technology can be used to deploy similar types of applications using the 5500 and

7100 network elements.

Fig. 26 TDM Circuits

1.2.10 Ethernet First Mile Services

The 8100 product family is complemented with an Ethernet over copper based solution consisting

of 8115 NTUs with the network terminating functionality and 8155 Access Switch nodes with the

aggregation functionality having Ethernet, E1, X.21, V.35 UNI interfaces and SHDSL copper

pairs between them. This platform supports L2 services such as Ethernet Private Line, E-LANand E-tree, as well as TDM SAToP and CES-based circuits where Ethernet packets are carried

over SHDSL/copper.

8000 INM supports adding the nodes to the network, launching the Local Craft Terminal and

managing faults. Services (Ethernet and TDM PW) are provisioned using Local Craft Terminal.


46



1 Introduction

Fig. 27 Ethernet First Mile Services

1.2.11 Frame Relay DLCI Pseudowire

Frame Relay DLCI pseudowires are used for transporting Frame Relay permanent virtual circuits

(PVC) over an MPLS network. The Frame Relay DLCI pseudowires are based on the PWE3architecture. The Frame Relay DLCI pseudowires are point-to-point connections, which map

Frame Relay PVCs to MPLS LSPs. Each PVC, identified by a DLCI value, is mapped to a separate

pseudowire (so-called one-to-one mode). In mobile networks, Frame Relay DLCI pseudowires can

be used for transporting GPRS traf fic between Base Station Controller (BSC) and Serving GPRS

Support Node (SGSN).

Fig. 28 Frame Relay DLCI Pseudowire


47



1 Introduction

1.2.12 HDLC Pseudowire

HDLC pseudowires are used for transporting HDLC based protocols, such as Point-to-PointProtocol (PPP), Frame Relay and Cisco HDLC over an MPLS network. The HDLC pseudowires are

based on the PWE3 architecture. The HDLC pseudowires are point-to-point connections, which

map HDLC frames to MPLS LSPs. HDLC pseudowires implement a so-called port mode service,

since all frames from one port are mapped to the same pseudowire (as opposed to e.g. Frame Relay

DLCI pseudowires, which map frames to pseudowires based on the DLCI values). In mobile

networks, HDLC pseudowires can be used for transporting CDMA2000 1xRTT traf fic.

Fig. 29 HDLC Pseudowire

1.2.13 Seamless MPLS

MPLS has been deployed in the core and aggregation networks for several years and provides a

mature and stable basis for large networks. In addition, MPLS is already used in the access networks,

e.g. in the mobile or DSL backhaul. Currently, MPLS as a technology is used on two different layers:

• transport layer and

• service layer (e.g. for MPLS VPNs).


48



1 Introduction

In both cases the protocols and encapsulation are identical, but the use of MPLS differs especially

with regard to the signaling, control plane, provisioning, scalability and frequency of updates. On

the service layer, only service-specific information is exchanged; every service can potentially

deploy its own architecture and individual protocols. The services are running on top of the

transport layer. However, these deployments are usually isolated, focused on a single use caseand not integrated in an end-to-end manner.

Seamless MPLS provides an architecture which supports a wide variety of different services in a

single MPLS platform fully integrating the access, aggregation and core network. The architecture

can be used for residential services, mobile backhaul as well as business services, and supports fast

reroute, redundancy and load balancing. Seamless MPLS provides the deployment of service

creation points which can virtually be everywhere in the network. This enables flexible service

and service creation for the network and service providers. Services can be created based on the

existing requirements without a need for dedicated service creation areas in fixed locations. With

the flexibility of Seamless MPLS, the services can be created anywhere in the network and easily

moved between different locations.

Many aggregation networks are already deploying MPLS but they are limited to the use of MPLS

per aggregation area. Those MPLS-based aggregation domains are connected to a core network

running MPLS as well. However, most of the services are not limited to an aggregation domain

but running between several aggregation domains crossing the core network. In the past, it was

necessary to provide connectivity between the different domains and the core per service level, and

not based on MPLS (e.g. by deploying native IP routing or Ethernet-based technologies between the

aggregation and core). In most cases service-specific configurations on the border nodes between

the core and aggregation were required.

With Seamless MPLS there are neither technology nor topology boundaries for the services.

Network (or region) boundaries are for scaling and manageability, and do not affect the service layer

since the transport pseudowire carrying packets from the access node to the service node does not

care whether it takes two hops or twenty, neither how many region boundaries it needs to cross. Thenetwork architecture is about network scaling, network resilience and network manageability and

the service architecture is about optimal delivery: service scaling, service resilience (via replicated

service nodes) and service manageability. The two are decoupled: each can be managed separately

and changed independently.

Due to Seamless MPLS, service-specific configurations between the different MPLS islands are

not needed. Seamless MPLS connects all MPLS domains on the MPLS transport layer providing

a single transport layer for all services, independently of the service itself. The Seamless MPLS

architecture therefore decouples the service and transport layer and integrates the access, aggregation

and core into a single platform. One of the main advantages is that problems on the transport layer

only need to be solved once (and the solutions are available to all services). With Seamless MPLS it

is not necessary to use service-specific configurations on intermediate nodes; all services can be

deployed in an end-to-end manner.

An example of the Seamless MPLS deployment for IP VPNs is presented in the figure below.


49



1 Introduction

Fig. 30 Seamless MPLS

1.2.14 Internet Access

The 8600 Smart Routers can be used for services in which the customer traf fic flows through the

nodes as basic IP route packets, without MPLS encapsulation or separate routing tables. ResidentialInternet access is a typical service like this. The operator usually provides dynamic IP addresses

for residential users through the DHCP protocol. The 8600 nodes support the DHCP relay

agent functionality, which can be used here. The traf fic from/to different residential customerstypically enters/leaves the 8600 nodes in separate customer-specific VLANs. Usually there is

a shaping/policing function configured in each VLAN to adjust the traf fic rate according to what

the customer has paid for.


50



2 8000 Intelligent Network Manager Components and Architecture

2 8000 Intelligent Network Manager Componentsand Architecture

2.1 Overall Architecture

2.1.1 Typical Configuration

8000 Intelligent Network Manager is usually installed in a separate Local Area Network in theoperator Network Operating Centre, here referred to as management LAN. An overall configuration

of a typical 8000 Intelligent Network Manager configuration is shown in the figure below.

Fig. 31 8000 Intelligent Network Manager Confi guration

A more detailed description about each of these components will be given later in the following

sections. The management LAN can be physically distributed between different locations. For

security reasons it should, however, be kept separate from the managed Wide Area Network. Only

the Communication Servers should have access to the WAN.


51




2.1.2 Minimum Configuration

Not all of the management system components need to be physically located in separate computers

when the size of the managed network and the number of management system users are small.

Single Server Configuration (SSC) can be used for networks having nodes up to 30 per cent

compared to a single Communication Server (for more information, refer to 8000 Intelligent

Network Manager Third Party Hardware and Software Requirements). SSC combines all of the

management system functions into one computer.

2.1.3 N-tier Architecture

In order to increase system flexibility and scalability, an N-tier architectural style has been applied in

the 8000 Intelligent Network Manager software. N-tier architecture, also often referred to as 3–tier

architecture, essentially means that at least the GUI client, application logic (business logic) anddata storage are separated from each other in a way that allows – but however does not force – them

to be run in separate computers. The advantages of this approach include better scalability (more

servers can be added to be able to handle large amounts of data) and relative easiness to make

changes to one part of the system without affecting the others.

The figure below shows the tiers of the system and their dependencies concerning some of the

network management system tools in a simplified way.

Fig. 32 N-tier Architecture in 8000 Intelligent Network Manager


52




2.1.4 Object Server

Object Server (OSR) isolates the 8000 Intelligent Network Manager business logic and GUI toolsfrom the database and network elements. They are offered a set of functions, by which they can

change the database contents, and select data from the database and network elements.

The Data Cacher process speeds up the data selection made by the Object Server. It keeps the

user-defined part of the database contents in the local RAM.

The advantages of the Object Server in multi-user environment include:

• Logical checks that prevent database inconsistency in multi-user environment can be collected in

OSR.

• Object Server collects the latest database changes in a specific database table (osrchan), where

also some additional information on the changes is stored.

• Object Server can inform the network management system tools of the changes in preselected

data, on the condition that all tools that change the corresponding data are also using Object

Server. This feature makes it possible to provide a practically real time view to the network data

to all 8000 Intelligent Network Manager users.

2.1.5 Server Monitoring

8000 Intelligent Network Manager servers can be configured to collect performance statistics of

the server computer and of the individual processes running in that computer. Refer to Server

Monitoring Con fi guration Wizard in the 8000 Intelligent Network Manager Online Help for the

options available. The collected statistics are stored in the database and can be viewed using thePerformance Management application.

2.2 Workstations

Workstations are the computers through which the operators use the 8000 Intelligent Network

Manager through a graphical user interface. Please see the document 8000 Intelligent Network

Manager Third Party Hardware and Software Requirements for detailed requirements concerning

workstation hardware and operating system.

The graphical user interface (GUI) is the interactive tool of network management. It is based

on hierarchical windows for all tools. The windows represent network elements and objectsgraphically. In addition, in some windows network elements and objects are displayed in treeand list view format, which is easy to navigate.

All 8000 Intelligent Network Manager tools are identified by the title bar text. The title bar also

identifies the target object in the network. For example, the Node Manager main window showsthe id and name of the target node in its title bar. The menu bar, where present, displays the sets of

actions available in each tool. The last of these sets is always the Help option.

Normal workstations can be configured to prefer a certain non-unique service instance by name, andto have backup servers if the preferred one cannot be found. In a large installation, the workstations

should be configured so that each group of workstations uses its own set of preferred non-unique

services, and uses the preferred sets of other workstation groups as backup only.


53




The first application the user sees after launching 8000 Intelligent Network Manager in a workstation

is the Dashboard. All available management tools can be launched from there. The Dashboard also

contains small applications, called widgets, which can be used for performing certain operations

(e.g. a search for nodes, trunks and services in the 8000 Intelligent Network Manager database),

monitoring certain aspects of the 8000 Intelligent Network Manager (e.g. faults), or showing the8600 units with the highest CPU load.

Fig. 33 Dashboard

The workstation does not contain any business logic. The business logic runs in a Management

Server (Satellite Service) and all database communication and change notifi

cation handling is donein the management server. Such a Management Server was previously known as a Gateway Server.In 8000 Intelligent Network Manager, the gateway server has been integrated into the management

server architecture as a Satellite service.

All workstations are "thin-client" workstations. Thus, a Management Server running Satellite

Service is required.


54




2.3 Database Server

Database Server contains a Sybase relational database where all 8000 Intelligent Network Manager tools store their data. Please see the document 8000 Intelligent Network Manager Third Party

Hardware and Software Requirements for detailed requirements concerning database server

hardware.

2.3.1 The Role of the Database in 8000 Intelligent Network Manager

All inventory and configuration data of the managed network elements are stored in the 8000

Intelligent Network Manager database. This kind of complete documentation about the network is

created automatically when different 8000 Intelligent Network Manager tools, all of which use thedatabase, are used for building, configuring and monitoring the network.

Examples of data stored in the database are:

• line and control cards

• interface modules

• interface configuration: layer 1, 2 and 3 parameters, VLANs etc.

• protocol (BGP, OSPF, DHCP, ARP...) configuration

• service (circuits, VPNs, pseudowires...) configuration

• equipment and service fault information (resulting from fault polling)

• performance data collected from the network elements.

8000 Intelligent Network Manager database can be used for pre-planning networks, configurations

and services before they are actually implemented. It is possible to plan the network topologywith network elements and trunks that do not exist in real world yet. It is also possible to create

the detailed configuration and parametrization of non-existing nodes in the database and use

these nodes in pre-planned services. After the pre-planned nodes and trunks are in place, it is

a straightforward task to bring the pre-planned parameters from database to the nodes and to

implement the pre-planned services utilizing them.

Note, however, that dynamic information, such as the routes in the default routing tables and VRFs

learned through the BGP/OSPF routing protocols, is not stored in the database.

2.3.2 Separate Performance Management Database and PerformanceManagement Table Partitioning

Network elements, such as 7100, mTera, 8600 and 8800 NEs, with thousands of physical and virtual

interfaces, as well as IP VPNs, TE tunnels and pseudowires generate a large volume of 15-minute performance monitoring (PM) data. The database space reserved by the PM data may be from 10

to 1000 times bigger than the space reserved by network configuration data. Due to this fact, PM

data has a limited retention period – old PM data has to be removed daily to free the database

space for the new data.

As the size of PM data tends to grow very rapidly, the separate PM database and PM table

partitioning features keep the 8000 Intelligent Network Manager configuration database compact

and fast when the PM data collected one day exceeds 10-20 million rows.


55




Fig. 34 Separate PM Database

Benefits of the separate PM database are the following.

• Smaller main database footprint means that main database backups and maintenance routines

work much faster.

• When PM database is located on its own server or in its own physical storage, PM operations donot affect main database input/output.

• 8000 Intelligent Network Manager opens dedicated database connections to the PM database,

which means that, e.g. long-running or complex PM reports do not interfere with other activities.

• Warm/hot standby works much faster as there is no need to replicate the PM data.

• It is possible to put different optimization goals on the main and PM database.

Benefits of the PM table partitioning are the following.

• Faster PM reports

• Very fast and ef ficient clean up of the old PM data

The separate PM database is currently supported to be created only on the same physicalserver as the primar y database. Within this server, it is recommended to locate the separatePM database in its own physical storage.


56




2.4 Communication Server

2.4.1 General

A Communication Server is required for managing the nodes integrated into the 8000 Intelligent

Network Manager. The Communication Server sends cross-connection, pseudowire and other

configuration commands to the nodes, fetches configuration snapshots, transfers ESW files, polls

the nodes for faults and performance data, etc. It also maintains real time clock settings for thosenode types that do not have NTP as an option. Note that e.g. all 8600 nodes support NTP, and thus

Communication Server will not update their real time clocks.

A domain concept is used to refer to a system or network which internally uses the same

management protocols and paradigms. A network consisting of 8600 nodes is an example of such a

domain. Nodes in this kind of a domain are accessed via an adapter or adapters in a Communication

Server. The adapters perform the conversion of information between 8000 Intelligent Network Manager and the domain, i.e. the 8600 domain in this case. The adapter is plugged into the

southbound interface of 8000 Intelligent Network Manager and it communicates with the nodes

either directly or by using a vendor specific mediator, proxy or element management system as a

gateway. In the case of 8600 nodes, the adapter communicates directly with the nodes using a

protocol called BMP and with SNMP.

There can be several Communication Servers per domain, each running its own set of adapter

processes. Communication Servers are associated with areas, so that each Communication Server

handles the nodes of those areas that have been assigned to it. This allows 8000 Intelligent Network

Manager to manage very large networks.

For each area, it is also possible to define a backup Communication Server, which assumes the

responsibilities of the primary server if the primary server fails. Communication Servers thus provide a fully redundant system in node communication.

Please see the document 8000 Intelligent Network Manager Third Party Hardware and Software

Requirements for detailed requirements concerning Communication Server hardware.

A separate licence is needed for each of the adapter types deployed in the CommunicationServer. In addition, separate licenses are needed also for each network element deployedin the network.

2.4.2 Managing the Communication Servers

The supervisor process controls the server functionality. It can be monitored and controlled through

a graphical user interface, the Server Monitor tool. The Server Monitor tool shows all the services

and processes that are installed in the server, and their current status. Through the Server Monitor

tool the user may start and stop individual services and restart/shut down the entire server.

The operator can configure Communication Servers by using the Communication Server

Parameters dialog in Network Editor. This dialog allows the setting of the name of the server and

the computer LAN name, its IP address and the backup level, as well as the adapters used by the

server. The Communication Server uses a communication adapter for each network element type or

protocol it supports. Some Communication Server parameters are defined in the configuration file.


57




The Communication Server can use the 8000 Manager Trace Utility to log its run time prompts,

warning messages and errors. The Trace Utility is a system through which different 8000 Intelligent

Network Manager tools generate log messages that are of help especially in the diagnosis of

problem situations.

2.4.3 Fault Management in Communication Servers

Fault management in 8000 Intelligent Network Manager Communication Servers is divided into

several dedicated processes. The polling controller creates poll jobs specified by polling policies.

The generic poller process uses adapters to poll faults from network elements. The faults are filtered

and reclassified, and then stored in the database. Polling policies can be edited in the Polling

Policies dialog in Network Editor.

2.4.4 Backup Monitoring in Communication Servers

The Communication Server can back up the functions of other Communication Servers in a

multi-server environment. The backup level can be configured in Network Editor. Possible values

for the backup level are Not Used, User Def and Auto.

The backup functionality is implemented by backup processes that run in each Communication

Server of the system. They poll each other to detect the loss of another server. If a server is lost, areas

are moved to running servers. This happens automatically if the backup level is defined as Auto for

the servers in the Communication Server Parameters dialog. It is also possible to set the backup

level to User Def and define the preferred Backup Communication Server in the Area Parameters

dialog in Network Editor. It is only possible to define one backup server for each area. On the other

hand, if both primary and backup server of an area fail the communication responsibility for the area

is moved to one of the running servers, as far as at least one running server exists.

2.4.5 Communication with Network Elements

There are two major ways of arranging the management communication:

• Outband management: There is a separate network for management communication, com-

pletely separate from the network that the 8000 Intelligent Network Manager installation in ques-

tion is managing. The external management communication network must provide IP connec-

tivity between the Communication Servers and all managed network elements. The advantage

of using outband management is that the management connectivity is not dependent on the state

of the managed network.

• Inband management: Communication between Communication Servers and managed nodesgoes through the managed network itself. The advantage here is that maintaining a separate

network for management communication is not needed. The disadvantage is that management

communication to the nodes is dependent on the state of the managed network.

When using inband management, care must be taken that configuration changes made in anetwork element do not cut the management connectivity to the node itself, or to any other nodes to which the management communication goes through the changed node.


58




2.4.6 Element Adapters

5500 Adapter

The 5500 Adapter is needed for communicating with the 5500 Series network elements. The

communication to the network elements is done using TL1. The EMS for 5500 network elements

utilizes a similar architecture than the 7090, 7100 and 8800 EMS.

6300 Adapter

The 6300 Adapter is needed for communicating with 6300 Series nodes. The communication to the

network elements is done using a protocol called LMIP (Local Management Information Protocol),

which is based on the CMIP protocol (Common Management Information Protocol). For some partsof the communication, SNMP (Simple Network Management Protocol) is used as well. LMIP is

transported using the OSI TP4 protocol or, in case of the newest NE feature packs, using the IPTCP protocol, while SNMP is transported using the IP UDP and TCP protocols. In addition, each

Communication Server also runs a so called Gateway Process, which act as communication gateway

between the 8000 Intelligent Network Manager workstations and the control network of the 6300

nodes. The Gateway Processes are used by the 6300 Craft Terminal tools when they are used for node management purposes on the workstations.

7090 Adapter

The 7090 Adapter is needed for communicating with 7090 Series network elements (e.g. 7090-25

CE and 7090-45 CE). The communication to the network elements is done using SNMP. The SNMP

protocol is mainly used for collection of faults from the network elements.

The launching of 7191 Craft Station for 7090 network elements utilizes the Gateway Process in

Communication Server. This enables the 8000 Intelligent Network Manager workstations and 7090

network elements to be located in separate LAN segments.

The EMS for 7090 network elements utilizes a multi-tier architecture (based on Java Remote

Method Invocation) for communication between the workstation, Management Server and

Communication Server. The 7090 EMS component on Communication Server uses SNMP to

communicate with the 7090 network elements. Note that the EMS does not support the 7090-05 CE,

7090-07 CE and 7090-15 CEM network elements.

7100 Adapter

The 7100 Adapter is needed for communicating with 7100 Packet Optical Transport Series network

elements (7100 OTS and 7100 Nano) and mTera Universal Transport Platform network elements.

The protocol used in the communication to 7100 and mTera elements is TL1 (Transaction Language

1) and SNMP protocol for the packet subsystem. TL1, developed by Telcordia Technologies on top

of TCP, is a cross-vendor, cross-technology man-machine language. It is widely used to manage

optical (SDH/SONET) and broadband access infrastructure especially in North America.

The launching of 7191 Craft Station for 7100 and mTera UTP network elements utilizes the Gateway

Process in Communication Server. This enables the 8000 Intelligent Network Manager workstations,

and the 7100 and mTera UTP network elements to be located in separate LAN segments.


59




The EMS for 7100 and mTera UTP network elements utilizes a multi-tier architecture (based on

Java Remote Method Invocation) for communication between the workstation, Management Server

and Communication Server. The 7100 and mTera EMS component on Communication Server uses

TL1 and SNMP to communicate with the 7100 and mTera UTP network elements.

8100 Adapter

The 8100 Adapter is needed to communicate with 8100 system nodes. Communication to the nodes

is based on a management protocol called the DXX protocol. The 8100 Adapter must be run in a

dedicated communication server, this server is also referred to as a DXX Server. No other adapters

may be run in a communication server running with the 8100 Adapter.

8100 EFM Adapter

The 8100 EFM Adapter is needed for communicating with the 8100 EFM network elements. The

communication to the network elements is done using SNMPv2. The SNMP protocol is mainly usedfor collection of faults from the network elements.

The EMS for the 8100 EFM NEs utilizes the Gateway Process in Communication Server.

8600 Adapter

Communication Servers communicate with 8600 network elements using BMP as the

communication protocol. This is an ef ficient, object-oriented management protocol, which is

specifically designed for managing data network elements. BMP uses UDP as a transport protocol,

although in the latest NE feature packs, TCP is also supported as a transport protocol. BMP has the

power of expression that makes it capable of making complex configurations in an effective way,

but is still relatively lightweight and simple compared to other powerful management protocols such

as CMIP. The 8600 Adapter is used for communicating with the 8600 network elements using the

BMP protocol. Third party management tools can read information from the 8600 network elements

using the SNMP protocol and the 8000 Intelligent Network Manager also uses the SNMP protocol

to collect performance statistics from the 8600 network elements.

8800 Adapter

The 8800 Adapter is needed for communicating with 8800 Smart Routers. The communication to

the network elements is done using SNMP. The SNMP protocol is used both for configuration of

the 8800 Smart Routers as well as for collection of the faults from the network elements. The

performance history data is collected using FTP.

The EMS for 8800 network elements utilizes a multi-tier architecture (based on Java RemoteMethod Invocation) for communication between the workstation, Management Server and

Communication Server. The 8800 EMS component on Communication Server uses SNMP to

communicate with the 8800 network elements

Generic SNMP Adapter

The Generic SNMP adapter is used for communicating with third party nodes supporting the SNMP

protocol and standard SNMP MIBs.


60




CLI Service

CLI Service is needed for communicating with 8600 network elements when no BMP interfaceis available in the network element.

ADNS Service

ADNS Service is used for detecting the appearance of newly deployed nodes in the network. ADNS

Service is a part of the automated deployment feature.

Deployment Service

Deployment Service is DHCP –like service for assigning initial IP address to newly deployed nodes

in the network. Deployment Service is a part of the automated deployment feature.

2.5 Management Server

Management Servers run most of the 8000 Intelligent Network Manager business logic. This is

divided into service processes. The placement of different services in the server computers is

flexible: most of the services can be run in the same server or alternatively different services can be

located in separate servers. It is also possible to have multiple servers running a single service in an

installation where the number of workstations is very large. The clients can be configured to use analternative Management Server if the preferred server is unavailable. The setup application offers a

number of pre-configured sets of services for ease if installation and configuration.

The currently installed services and their status can be seen in the Server Command Center - 8000INM dialog.


61




Fig. 35 Server Command Center

2.5.1 Service Processes

Some services must have only one copy running at a time, while there can be several copies of others

running simultaneously, if the service names and workstations have been configured appropriately.

The unique services with only one possible instance are described in the table below.

Service Description

Packet Loop Test Service Allows scheduled and immediate testing operations

Running more than one instance of the above services in the system will lead to error situations.

The rest of the services also depend on each other. As a general rule, there should be at least one copy

of each service installed and running in the management system for the system to be fully functional.

These services are described in the table below.


62




Service Description

EMS Service Takes care of 8600 network element level

configuration, including QoS and protocol

authentication settings.VPN Provisioning Service Serves the VPN Provisioning and Tunnel

Engineering tools.

Fault Service Distributes fault information to clients.

Service Management Service Provides information to the Service Management

GUI.

Node Management and Query Service Provides business logic and infrastructure for

multiple user components on multiple element

types, including Node Manager, macro services,

GMPLS management, and enhanced reporting.

Satellite Service Serves workstations. See below for more

information about the satellite service.

Performance Management Service Provides packet performance information to the

PMS GUI.

Macro Manager Service Serves macro applications used for configuring

8600 elements.

Element Software Management Service Provides information for the Element Software

Management GUI application and the

functionality to update software in network

elements.

Scheduling Service Scheduling Service is responsible for executing

scheduled tasks at specified intervals.

Web Reporter Service Web server that provides information about the

network and services in 8000 Intelligent Network Manager to web clients.

Northbound Interface Service Provides northbound interface for 3rd party

software integration purposes.

MTOSI Adapter Provides MTOSI 2.0 interface for MTOSI web

clients.

SNMP Adapter Provides an SNMP interface for the fault system.

ADC Service Automated Deployment Controller is responsible

for deploying the predefined configuration to the

network elements. ADC Service is a part of the

automated deployment feature.

You can relocate services between Management Servers after installation by rerunning theSetup Wizard and selecting the Reconfigure Old Installation option.

For more information on locating, balancing and backing up the services, refer to 8000 Intelligent

Network Manager Software Installation Manual .


63




2.5.2 Using Multiple Service Instances

If a Management Server fails, the same services can be activated in other Management Servers by updating their configuration files (or by reconfiguration) or clients can be preconfigured to

automatically revert to use another management server if the preferred server is unavailable.

2.5.3 Satellite Service

The Satellite Service serves an array of workstations, see the figure below. The Satellite Service

was previously known as the Gateway server.

Fig. 36 Management Server Running Satellite Service in 8000 Intelligent Network Manager

Workstations do not have a direct connection to the database as their access to the database is

multiplexed through the Satellite Service. Workstations are connected to the Management Server

running the Satellite Service with routed LAN. Individual remote clients and their connection to

the database can be better tolerated because the 8000 Intelligent Network Manager tools of the

workstations cannot lock directly onto the database tables. The Management Server serializes

transactions to the Database Server.


64




Workstations use the services of the Database Server, Management Servers, Communication Servers

and Recovery Server through the Satellite Service.

2.5.4 Fault Service

The Fault Service is run in the standard Management Server. It continuously polls the database

for changed faults, processes the fault data and performs service fault mapping. When the Fault

Service detects changed faults, it analyzes the fault data and informs Fault Management System

of the change in the fault condition. The Fault Service maps the raw fault data both to the basic

network elements, e.g. nodes and trunks, and to the higher-level objects, e.g. circuits, customers and

service categories. Fault Management System listens to the notifications from the Fault Service andinvokes fault queries for different objects under fault monitoring.

The Fault Service provides services for several workstations in the system, and there can be several

Fault Services running in the same system.

2.5.5 Northbound Interface

8000 Intelligent Network Manager can be integrated into the operator's OSS system by using the

Northbound Interface. The level of this integration as well as the exact OSS components to integrate

with will vary a lot from one operator to another. To address these needs 8000 Intelligent Network

Manager provides a framework which supports implementing a number of northbound interfaces for

different purposes, e.g. fault management, VPN provisioning etc.

MTOSI Adapter

TM Forum’s Multi-Technology Operations System Interface (MTOSI) effort has the goal of defining a unified open interface to be used between Operations Systems (OSs), where an OS isany management system that exhibits Element Management Layer (EML), Network Management

Layer (NML) and/or Service Management Layer (SML) functionality as defined in the ITU-T

TMN model. 8000 Intelligent Network Manager provides a northbound MTOSI interface using

traditional web-services technologies (WSDL/SXD and SOAP/HTTP) to implement a combination

of standard, pre-standard and proprietary operations. The interface is based on the MTOSI Release

2.0 specifications with some proprietary extensions for IP/MPLS based services as well as testand diagnostics functions.

Supported functionality includes the following.

• MPLS pseudowire provisioning (SAToP and Ethernet PWs)

• IP VPN provisioning

• RSVP-TE tunnel provisioning

• Port configuration

• Connection testing (VCCV LSP ping, ATM ping, IP Ping, Ethernet ping and traceroute)

• Port status checks

• Port and pseudowire loopbacks

• IP static route configuration

• LDP neighbor configuration


65




• NE inventory retrieval

• Network element provisioning

• Ethernet OAM (802.1ag and Y.1731) management

• IEEE 1588 synchronization management

• Generic extension interface (calling native 8000 Intelligent Network Manager macros through

MTOSI)

The supported elements include 8605 Smart Router, 8609 Smart Router, 8611 Smart Router, 8620

Smart Router, 8630 Smart Router and 8660 Smart Router.

The MTOSI Adapter can be configured as part of the NBI Server configuration.

SNMP NBI Adapter

8000 Intelligent Network Manager provides an SNMP interface for the fault system. Both SNMPversion 2 and SNMP version 3 are supported. The SNMP NBI Adapter can be configured as part of

the NBI Server configuration.

2.6 Recovery Server

Recovery Server provides facilities to restore user communication links if trunk or node faults occur

in the 8100 system network. The Recovery Server is used for circuit and trunk protection.

Recovery Server is optional and runs on a dedicated recovery computer. If there is only one DXXServer in the system, both Recovery and DXX Servers can run in the same computer.

It is possible to install two Recovery Servers in the 8100 network to increase reliability. In case of an

unrecoverable failure of the active Recovery Server (e.g. LAN failure, physical damage causing PC

hardware failure, electricity break) the backup Recovery Server will take over the recovery support

for the 8100 network. In case of a hardware or software update, the backup can also replace the

primary Recovery Server during the update operation.

Recovery Management System uses a single centralized Recovery Server that provides the recovery

functionality. However, it is possible to switch servers at any time. Server switching operations can

be initiated from Recovery Control Program if you have the required privileges.


66



3 8000 Intelligent Network Manager Application Packages

3 8000 Intelligent Network Manager ApplicationPackages

3.1 General

8000 Intelligent Network Manager is divided into the following separately licensed optional

application packages:

• Basic Package - Contains the functionality to build and configure the network, document thenetwork inventory, monitor network faults, administrate users and customers and get on-linehelp.

• Provisioning Packages - Includes tools for service provisioning and tunnel engineering as well

as online core network monitoring functionality. With the provisioning packages, the user may

configure IP VPNs, optical (DWDM and G.709 OTN) connections, Ethernet point-to-point and

multipoint services, ATM based services, TDM based services (circuits and pseudowires), Frame

Relay based services and HDLC based services.

• Testing Package - Enables testing the provisioned services with the Circuit and Packet Loop Test

tools. With these tools the user may detect and localize problems in circuits, pseudowires and IP

VPNs in the network. The Packet Loop Test tool can also be used to measure QoS levels in the

MPLS network.

• Service Fault Monitoring - Contains tools that enable management and real-time monitoring of

services in the network. The tools support both PDH and SDH circuits as well as TDM, ATM

and Ethernet pseudowires and IP VPNs.

• Performance Management - The Performance Management tool is targeted for network perfor-

mance monitoring and troubleshooting. The performance monitoring includes systematic col-

lection, storage and reporting of the traf fic flowing into and out of trunks and interfaces in the

network.

• Unit SW Management - The unit software management package reports the installed software

and hardware versions in the nodes and downloads new software to a selected set of nodes.

• Web Reporter - The Web Reporter tools provides network statistics through a web interface in

HTML reports. The reports include information on faults, configuration and capacity in easy-to-

read format.

• Macro Package - The Macro Package includes the Macro Manager tool and Application De-

velopment Toolkit that enables the user to develop customized tools and functions to speed up

network management tasks.

• Planning Package - The Planning Package contains tools similar to the ones used in real network

operations and tools dedicated to network design purposes. The tools can be used to optimize the

network when planning a roll-out of a network or when making changes to an existing network.

The network management tools in these packages can all be accessed from the Dashboard.

The licensing of each application package consists of a fixed starting fee, depending on the number

of users (up to 5, 10 or unlimited number of users) and an element fee per each managed element.


67




3.1.1 Other Software Packages

In addition to the packages above, there are a few software packages that do not contain specificManager tools, but extend the Manager with additional features. The following packages are

available:

• Recovery Management - Restores services when faults occur in the network. Both trunk and

circuit level recovery is included. The Recovery Management supports PDH 1/0 circuits and

trunks for 6300 and 8100 network elements.

• Service Viewing Package - With the Service Viewing Package users can filter the network view

to cover only specific circuits or regions, or circuits of a specific customer.

• Partitioning Package - The Partitioning Package allows large networks to be managed and or-

ganized regionally, while still providing an option to the user to also see an overview of the entire

network, if needed.

3.2 Basic Package

3.2.1 Network Editor

Network Editing Tools are used for building, viewing and editing the model of the 8000 system

network stored in the database. Network Editing Tools comprise Network Editor as a top-level

window from which you can launch the other tools, including Node Editor and ID Interval Editor.

The objects stored in the database represent the management view of the hardware and software

elements and the interconnections between them. Network Editor displays many of these objects and

connections graphically. It has many text-based dialogs for viewing and changing the parameters of the database objects. In a few cases Network Editor communicates with the hardware elements. A

special feature of Network Editor is the Toolbox, which floats on the Network Editor screen. It is a

collection of panels that allow new objects (nodes, trunks, locations and networks) to be created,

existing objects to be selected and moved, and independent tool sessions to be launched.


68




Fig. 37 Network Editor Window

Representation of Network

Network Editing Tools represent the network in the Navigator Tree, List and Network View

windows, and switches in one or more Node windows.

The Network View window represents a graphical view of the whole network, or the view can be

zoomed and scrolled to show a part of the network. In this window the nodes, trunks, locations andnetworks are represented by small graphic representations, symbols. Each object refers to a specific

item of hardware, a logical object created for the purpose of managing the hardware, or external

equipment connected to it. For example, each switch is represented by a graphic resembling the

front view of the switch subrack. A location is a symbol representing a group of nodes and trunks

that interconnect the network elements, usually all located in close proximity. A location can be

opened to view the subnetwork it represents. Locations can be nested, i.e., a location can contain

another location.

The Navigator Tree View window represents a navigational view of the whole network. Objectsare grouped according to their type and position in the topological hierarchy. The number of visible

objects in the window can be limited by using subdivision groups and filters. The List View window

gives a more detailed report view of object properties.


69




Two other types of Network window can be opened. The secondary network window displays an

overview of the network. A location window can be opened for any location object to display the

network of network elements in that location.

Trunk Symbols

Connections between network elements are represented by a connecting line, referred to as a bundle.

On this line, there are small symbols displaying the trunk type. More than one trunk can be placed

upon a connecting line and to represent multiple trunks between the same pair of end network

elements.

View Options

The types of objects displayed and how they are displayed can be controlled by a number of view

options.

The network view options include the following:

• Customer view

• Trunk view

• Network element view

• Selected area

• Unbound network elements

• Object labels

The network element level views include the following:

• Subrack or shelf view

• Module view

• Interface view

• Network element tree view

A Node window can be opened for any switch by launching a Node Editor session. The Node

window displays an overview of the subracks of a switch and a picture of a subrack with its cards

and interface modules.

State Logic

The main target of the 8000 Intelligent Network Manager State Logic is to allow the user to

pre-design the 8000 system networks in the database even if no hardware exists. State changes are

initiated by the user. The state of the object implies certain assumptions about its configuration

and behavior when managed.

The states have the following meaning for the objects in a network element:


70




8600 Network Element States

planned 1 Object is assumed not to exist physically. As a general rule, configuring the

object will only affect the database representation.

installed 2 Object exists also physically. Configuration operations will affect both databaseand network element.

in use 3 Object is used in production. From configuration point of view, this is the

same as installed, but end-to-end management and network level management

software considers this object to be suitable for production use.

8800 Network Element States

planned 1 Object is assumed not to exist physically. As a general rule, configuring the

object will only affect the database representation.

installed 2 Configuration operations will affect both database and network element. The

specific hardware object may or may not exist physically. Alarms are not

monitored for the object.

in use 3 Object is meant to be used in production. From configuration point of view,

this is the same as installed, but end-to-end management and netwo rk level

management software considers this object to be suitable for production use. For

objects representing physical resources, the system has ensured, at some point in

time that the physical resource is in place. Alarms are monitored for the object.

Usually, planned is seen as the lowest and in use as the highest state. When updating the state from

planned to installed or in use, the parameters are copied from the database to hardware. Parameters

that belong to the whole network element instead of a certain interface or other physical object

are associated to the state of the control card.

Node Editor

Node Editor is a tool for defining the provisioning of network elements and defining and viewing

interface uses and the bindings of interfaces to trunks and nodes.

There are two ways to add new cards and modules into the network element. This can be done

through a pop-up menu or with the help of toolboxes of available card and module types. A Settings

dialog allows the state of objects to be changed. Various Node Manager windows can also be

opened from Node Editor.

Node Editor provides two views for displaying network element furnishing: graphical view and

tree view. The graphical view shows subracks/shelves, cards and interfaces of the node as a picture.

The tree view shows the same information in a tree structure, but shows also binding information for the interfaces of the node. In addition to the two switch views, there is a network view showing

the trunks and other nodes attached to the node being viewed.

A pop-up menu is available both for the graphical view and the tree view.


71




Fig. 38 Node Editor Window

ID Interval Editor

ID Interval Editor is a tool for defining the range of valid IDs for each class of object that Network

Editor and other tools can add to the database, e.g. node IDs and trunk IDs.

Power Balance Application

The Power Balance application is used for estimating power consumption and power balance

(surplus or shortage) of 8660 Smart Router and 8630 Smart Router. The Power Balance Overview

dialog displays power estimates of several network elements whereas the Power Balance Details

dialog shows a detailed power report for a single network element. The power computation is

based on the network element inventory data stored in the 8000 Intelligent Network Manager

database. The Power Balance application gives just a rough estimate of the power figures, more

reliable estimates can be calculated manually as instructed in Tellabs® 8600 Smart Routers Tellabs®

8660 Smart Router Reference Manual and Tellabs ® 8600 Smart Routers Tellabs® 8630 Smart

Router Reference Manual .


72




QoS Settings Tool

The QoS Settings tool is used for setting up various Quality of Service related parameters in allinterfaces of the network. The parameters can either be set for one interface at a time or for a

point-to-point trunk, in which case identical parameters are set to both the end interfaces of the

trunk. This tool can be opened from Node Manager main window and Node Editor for an interface

and from Network Editor for a trunk.

The tool provides support for templates that make it possible to define a QoS setup suitable for

certain kinds of interfaces/trunks in a network, to name this template and to apply it for any number

of interfaces or trunks. Applying an existing template to each interface or trunk is done by opening

the QoS Settings tool for the interface or trunk, selecting the template from a drop-down list and

clicking a single button in the dialog. The templates are stored in the 8000 Intelligent Network

Manager database and there can be any number of them.

The QoS parameters supported by the tool include:

• Bandwidth Reservation: parameters related to RSVP capacity reservations for traf fic engineered

LSPs

• Policer: service class-specific policers for traf fic entering the node through the interface in ques-

tion

• Shaper: service class-specific shapers for traf fic leaving the node through the interface

• Queue: queuing parameters for the different service classes for traf fic leaving the node through

the interface

• Mappings between E-LSP exp bits/Ethernet priority bits and the service classes used by the op-

erator. These affect both ingress and egress traf fic.


73




Fig. 39 Queuing Parameters


74




Fig. 40 Policer Parameters

Synchronization Monitoring Tool

Synchronization Monitoring Tool is used to monitor the synchronization clock flow throughout the

8100 system network. It can also monitor 6300 nodes that are managed with 8000 Intelligent

Network Manager. This tool can be used, for example, to check that the synchronization network is

configured as planned and to locate faults (e.g. loops) in the synchronization network.

There are two possible methods of monitoring synchronization clock signal distribution in the

network. The first is Default Synchronization Path, and the second is Current Synchronization Path.

The default path shows where the synchronization clock signal is expected to come from, and

the current path shows where the synchronization clock signal is actually coming from. Tracing

can be done to one node at a time.

Enhanced Reporting Tool

The Enhanced Reporting tool provides a central and flexible location for querying the 8000

Intelligent Network Manager database for inventory and services.

• Custom queries can be built by setting various filters on any column in a given report.

• Customized queries may be saved for reuse and shared with other users.

• Once saved, queries can be scheduled for regular execution in Scheduling Center, with results

e-mailed to users.

• Report output may be exported to multiple formats, including CSV and PDF.


75




• A command-line interface to Enhanced Reporting allows external or scheduled access to 8000

Intelligent Network Manager data.

• For reports over managed objects, the user can right-click on any report row and directly access

management tools and operations.

Enhanced Reporting currently covers most key 8000 Intelligent Network Manager objects (circuits,

VPNs, etc.) as well as the entire element-level inventory and provisioning for multiple NE types.

The same interface is also integrated into the 5500, 7090, 7100 and 8800 Node Managers (as the

"Queries" mode) for direct and quick access to network element inventory and configuration objects.

Configuration Wizard Tools

Network Editor includes multiple configuration wizard tools which greatly simplify commissioning

and configuring the network infrastructure.

Node Configuration Wizard provides a simple and fast work flow for setting typical configuration

parameters for a 8602 Smart Router, 8605 Smart Router, 8607 Smart Router, 8609 Smart Router or 8611 Smart Router. Both basic node-level parameters and more advanced parameters, e.g. OSPFand IS-IS settings, are supported. The wizard also supports a template mechanism for predefining

frequently used settings.

Fig. 41 Node Confi guration Wizard

Multi-Node Creation Tool utilizes the Node Configuration Wizard tool and its templates and

provides an ef ficient method for quickly adding multiple 8602 Smart Router, 8605 Smart Router,

8607 Smart Router, 8609 Smart Router or 8611 Smart Router nodes to the network. The Multi-Node

Creation tool can load a CSV (comma separated values) file which has been produced with a

spreadsheet application. The CSV file contains the basic node parameters and a reference to the

templates used by the Node Configuration Wizard. Based on the file, the nodes are added to the

network and optionally discovered, and the configuration specified in the templates is commissioned

to the nodes.


76




Fig. 42 Multi-Node Creation Tool

Trunk Provisioning Tool simplifies the creation of STM POS, PPP, Ethernet and VLAN trunks

and IP/MPLS links between 8600 nodes. The Trunk Provisioning Tool is a wizard style application

which can guide the operators to set the trunk/link parameters step by step. The used configuration

parameters are defined in templates which can be edited and saved with the tool.

Fig. 43 Trunk Provisioning Tool


77




Multi-Trunk Provisioning Tool utilizes the Trunk Provisioning Tool and its templates and provides

an ef ficient method for quickly adding multiple STM POS, PPP, Ethernet and VLAN trunks and

their IP/MPLS links at the same time. The tool reads a CSV (comma separated values) file which

has been created e.g. with a spreadsheet application. It then adds trunks and configures the end

interfaces for them based on the information in the CSV file and in the already defined Trunk Provisioning Tool templates which are referred to in the CSV file.

Fig. 44 Multi-Trunk Provisioning Tool

Multi Node QoS Setting Wizard utilizes QoS templates in 8600 Node Manager and provides an

ef ficient method for quickly setting QoS parameters for the 8600 Smart Routers. Several nodes can

be selected in the wizard, and a QoS template can then be applied to the selected nodes one by one.


78




Fig. 45 Multi Node QoS Setting Wizard

Multi Node Real Time Clock Wizard provides an ef ficient method for quickly setting real time

clock parameters for the 8600 Smart Routers. Several nodes can be selected in the wizard, and the

configured real time clock parameters can then be applied to the selected nodes one by one.

Fig. 46 Multi Node Real Time Clock Wizard


79




Multi Interface MTU Setting Wizard provides an ef ficient method for quickly setting MTU

parameters for the Ethernet, IP and MPLS interfaces in the 8600 and 8800 Smart Routers. Several

interfaces can be selected in the wizard, and the configured MTU parameters can then be applied to

the selected interfaces one by one.

Fig. 47 Multi Interface MTU Setting Wizard

Multi-interface DHCP Relay Wizard provides an ef ficient method for quickly setting DHCP

parameters for a large number of interfaces. Several interfaces can be selected in the wizard, and the

configured DHCP relay agent related parameters can then be applied to the selected interfaces.


80




Fig. 48 Multi-interface DHCP Relay Wizard

Multi Node SNMP Agent Wizard provides an ef ficient method for quickly setting SNMP agent

parameters for the 8600 Smart Routers. Several nodes can be selected in the wizard, and theconfigured parameters can then be applied to the selected nodes one by one. The supported SNMP

agent settings include basic SNMP parameters, registered communities, trap addresses and filtering.

Fig. 49 Multi Node SNMP Agent Wizard


81




3.2.2 Node Manager

8100 Node Manager and 8600 Node Manager

Node Manager provides facilities to manage the network elements: switches, cards and interfaces.

The element management facilities include parameter setting, fault monitoring, consistency

checking and templates. Node Manager can be opened from Network Editor.

Node Manager is a collection of tools that are used for setting parameters for network elements

and monitoring the existing parameter values.

Node Manager shows the actual topology of the network element and which cards are active and

in use. With Node Manager it is also possible to add/remove cards and modules and change their

states (planned, installed, in use).

Fig. 50 8600 Node Manager Main Window


82




Preplanning

Preplanning makes it possible to create elements and set parameters for them in the planned stateindependently of the state of the physical hardware. Later, when the state of the elements is raised

from planned to installed or in use, the parameters are copied from the database to real hardware

elements. In normal use, when hardware communication exists and the element is in the in use state,

Node Manager shows the actual layout of network elements and allows the user to set parameters

for hardware values.

Templates

Templates are used to store a named set of interface parameters to the database. The use of templates

helps the user to set interface parameters faster and more accurately. The system administrator can,

for example, make an interface parameter template which the other operators can make use of later.

Node Manager Tools

There are several different tools in Node Manager. These include, among others, the following:

• Consistency Checker for finding and resolving inconsistencies between database and node. In the

Consistency Checker dialog it is possible to select for which topology elements the consistency

check is done.

• Node Autodiscovery for reading a node topology hierarchy to the database. Autodiscovery can be

initiated when a new network element has been installed or as an incremental discovery operation

when line cards and modules have been added to the network element. The network element must

be added to the database before initiating the autodiscovery operation.

• IP Routing Table for defining routing table

• MPLS for defining MPLS behavior

• IP Host for defining protocol parameters

• BGP-4 Router for defining BGP parameters and creating neighborhoods

• QoS Settings for defining Quality of Service parameters for the node

• ACL for defining Access Control Lists

• OSPF Router Process for defining OSPF router behavior

• OSPF Area for defining OSPF area parameters

• IS-IS Router Process for defi

ning IS-IS router behavior • Route Map for defining Route Maps

• Several dialogs for defining parameters for different types of interfaces including ETSI and ANSI

versions

• Configuration of protection including MSP 1+1, APS 1+1, ELP and BFD

• Active Faults for viewing currently active faults

• Ping/Traceroute for testing connections and for finding problems in the network

• CLI Show for sending show commands to the network element and for viewing the results

• ESW Management for managing the embedded software of the network element (for more infor-

mation, refer to 3.12 Unit Software Management Package)


83




• Synchronization for defining network synchronization behavior

• Ethernet Bridges for defining Ethernet bridging behavior

• Version Management for managing the network element driver version in the database

• Unit Upgrade for performing unit upgrades

Fig. 51 Access Control List Dialog

5500 Node Manager

5500 Node Manager is an integrated Node Manager tool within 8000 Intelligent Network Manager.

Through 5500 Node Manager, you can manage 5500 NEs, including 5500 and 5500S. Supported

functionality includes the following.

• SONET cross-connect provisioning

• Fault monitoring

• Resynchronization to reconnect the NE and resynchronize the EMS inventory and NE alarms

• TL1 Cut Through for managing the NEs with TL1 commands

7090 Node Manager

7090 Node Manager is an integrated Node Manager tool within 8000 Intelligent Network Manager,

which can be used to manage the 7310, 7090-25 CE and 7090-45 CE nodes.


84




7090 Node Manager supports provisioning ports, interfaces and other entities. Supported


• Resynchronization for inventory and alarms

• CLI Cut Through for managing the NEs with CLI commands

• Global Provisioning of 802.3 Ethernet services and G.1731 OAM.

• Database Operation for backup, restore and status check

• Security for assigning users and creating agent communities and groups

7100 and mTera Node Manager

7100and mTera Node Manager is an integrated Node Manager tool within 8000 Intelligent Network

Manager. Through 7100 and mTera Node Manager, you can manage 7100 NEs, including 7100

OTS and 7100 Nano, as well as mTera UTP.

The supported functionality for 7100 OTS and 7100 Nano includes the following.

• Dense wavelength division multiplexing used to increase the capacity andflexibility of the optical

infrastructure, with multiple optical signals transmitted over multiple optical wavelengths on asingle optical fi ber

• Performance monitoring for continuous, nonintrusive collection of system performance data to

determine the operational status and quality of service

• Control Plane for rapid circuit provisioning across mesh architectures in transport networks

• Ethernet Packet subsystem support with port shelf Packet modules installed and provisioned


• Main and port shelf and AIP creation


• TL1 user management for setting user access privilege code, password aging, session timeout,

password restrictions, enabling account lockout and viewing TL1 sessions and Radius properties

• Network diagnostics for pinging and trace routing

• IPSec management to download/install IPSec certificate, allow and inhibit IPSec, and manage

IPSec certificate, internet key exchange and SPD

• Provisioning line side and port side facilities, facility and path protection, timing synchronization,

terminations and channels, fi ber and cross-connections, optical power range, NE map, control

frame profi

le and NTP peer and LAG, TTP and VCG managementThe supported functionality for mTera UTP includes the following.

• Metro multiplexing and switching system based on a parallel architecture that provides scalable,

non-service affecting growth without network re-engineering

• Stand-alone optical transport shelf with 14 switched port slots where each slot has a 200G capac-

ity for a total shelf capacity of 2.8 Terabits

• Performance monitoring for continuous, non-intrusive collection of system performance data to

determine the operational status and Quality of Service



85




• GCC for remote mTera UTP NE management when connected to other mTera UTP NEs through

the GCC channel where the configured OTN services on mTera UTP port modules provide an

in-band GCC channel to connect the NE to the mTera UTP management network

• Automatically detects and reports internal hardware, software, communication, and loss of in-coming signal faults

• Network diagnostics for pinging and trace routing

• Provisioning facilities, OTN multiplexing/switching, Y-Cable facility and path protection, tim-

ing synchronization, terminations and channels, ODU cross-connections, optical power measure-

ments for port modules

8800 Node Manager

8800 Node Manager is an integrated Node Manager tool within 8000 Intelligent Network Manager.

Through 8800 Node Manager, you can manage the 8800 NEs, including 8830 Smart Router, 8840

Smart Router and 8860 Smart Router.

8800 Node Manager supports provisioning ports, channels, interfaces and other entities. Supported


• Resynchronization for inventory and alarms


• Global Provisioning for OSPF, MPLS, DHCP, BFD, BGP, IS-IS, NTP and client trap

• Interface Provisioning for APS groups, loopback interface, GRE tunnel interface, IRB interface

and PW interface

• Service Provisioning for PNNI nodes, bridging instances, LSP, routing instances, circuit bundles,

STP and forwarding groups

• QoS Provisioning for QoS traf fic parameters and groups, access control list, inband filter list,

prefix list and route map

• Database Operation for backup, restore and status check

• Security for assigning users and creating agent communities and groups

3.2.3 Customer Administration

Customer Administration provides tools to update the names and addresses of the operator's

customers and their different sites in the 8000 Intelligent Network Manager database. Once the

customer and site data has been inserted, it is possible to associate interfaces and entire network elements to different sites. This kind of association means that the interface in question is connected

to the customer site or that the node in question is located in the customer site. VPN provisioning

tool uses customers and sites for grouping interfaces available as VPN endpoints in its user interface.


86




Fig. 52 Customer Administration Dialog

3.2.4 Fault Management System

Fault Management (FMS) is used for monitoring and reporting the fault status in the 8000 system

network. The basic function of Fault Management System is fault monitoring, which includes thecontinuous supervision of network elements. The Communication Servers and DXX Servers collect

the fault data from network elements (Communication Server used in the text subsequently to refer

both to DXX Servers and Communication Servers). Each server is responsible for gathering fault

events from one or more network areas (a collection of network elements). The detected fault events

are filtered, if necessary, and transferred to the system database. The network fault status stored in

the database is, in turn, continuously monitored by Fault Servers in the system.

This arrangement offers a real-time fault view of the monitored network to the network operator.

Detected fault events are attached to proper object symbols (trunks, user access points, network

element kernel parts, etc.) in the Fault Management windows. The appearance of these symbols

directly indicates the severity of faults in the corresponding network elements.


87




Fig. 53 Main Window of Fault Management System

Fault Monitoring Principles

Fault monitoring is automatically started when the state of the network element is changed to in use.

Fault monitoring is based on network fault polling. 'To poll' means to perform a status query fromthe network element. Whenever a change in the network element fault status is detected, detailed

fault information is provided in the faulty network element itself. This information is read by the

Communication Server and transferred to the database. Communication Server obtains the fault

data through an adapter. Depending on the case, the adapter can interface with another managementsystem or contact the network element directly. Note that only a single poll has to be performed for

a network element because all the new faults and cleared faults are polled at the same time. By thisarrangement a single Communication Server can take care of the fault polling of a relatively large

area. The Communication Server polling parameters, like fault and network element ping polling

period, are configured in the Polling Policies dialog in the Network Editor.

Fault notifications, initiated by network elements, are used for speeding up the detection of new or

changed faults. When there is the first change in a fault situation of the node since the last time the

node was polled, a fault notification is sent to 8000 Intelligent Network Manager. After receivingthe notification the node that sent the notification is polled immediately – or almost immediately

if there are notifications coming from several nodes in a short period of time – even if it is not

yet that node's turn in the normal polling cycle.


88




In addition to the network fault status polling and notifications, also the consistency between the

system database (network element and card configurations) and the actual values stored in hardware

are checked periodically. Any inconsistencies detected during the checking are reported via the fault

management user interface.

The faults reported by a card are ignored in case the installation state of the faulty interface or the

card itself (card level faults) is below the configured threshold value. This value can be set to

installed or in use. By this method the faults generated during equipment installation can be omitted.

A card is under fault monitoring as long as it exists in 8000 Intelligent Network Manager. All

possible active faults and the card fault history are deleted when the operator deletes a card.

Fault filtering allows modification of the rules for including and excluding certain types of faults

into and from the database. Those faults already in the database can be viewed by the Fault

Management System windows.

Fault Management Windows

The fault management user interface contains five basic fault monitoring windows, the Network ,

Network Element, Bundle, User Access and Unit window. These windows follow the fault

condition in the supervised network in real time, which means that whenever the windows are open

at the workstation, new faults are indicated as soon as the Communication Server has detected them.

The faults are attached to proper fault management object symbols in these windows. The Fault

Management System objects in the windows are the following:

• Network

• Location

• Network element

• Subrack

• Bundle (trunk group between two network elements)

• User access group (user access interfaces of a single network element)

• Trunk

• Card

• Card block (card physical block objects )

• Card logical block (groups of physical block objects)

• Interface (interface of a card)

• Components

The appearance of the object symbol in the window (color coding, blinking status) directly reflects

the fault state of the object. The object is said to be in the normal state when it does not contain

any fault events at all. For example, a user access group object of a network element is in the

normal state when all the user access interfaces in the network element are operating normally.

The object is alerting if it contains at least one unacknowledged fault event. Note that normally

the object is alerting as long as the fault remains unacknowledged, regardless of the fault state in

the network (active or inactive). After the operator has acknowledged the fault, the object state is

changed to faulty. When the fault is fixed, the object state is changed to normal again. If an object

contains several faults, the layout of the object symbol in the window is determined according to

the most serious fault event.


89




In the Fault Management System there are two different card block types: physical block object and

logical block. A physical fault object contains a physical fault block and block class numbers, and

represents real hardware objects where faults originate from. The logical fault block is used to group

several physical fault block objects into a certain logical group.

In addition to basic fault monitoring windows, there are Service Fault Monitoring related windows:

Service Fault Monitoring (SFM) window and Service Fault window. Service Fault Monitoring

enables the real time supervision of all services, i.e. IP VPNs or pseudowires that are assigned to a

certain Service Category. A Service Category is a collection of pre-selected services. It is possible

to configure Service Fault Monitoring so that only the selected service categories are displayed.

In this mode, symbols are displayed in the order they were selected. In addition to the predefined

categories, an operator can select dynamically Customers to be taken under monitoring. Thefault status of categories and customers is displayed in the Service Fault Monitoring window.

The All Faulty Services symbol can be added to the lower right-hand corner of the window. This

symbol represents the total fault status of all services. By default, the selected service categories and

customers are saved on the configuration file and thus remembered. This means that next time the

previous view is automatically restored. One workstation or Fault Server can be selected to saveand update all faulty services in the database.

All faulty services and their fault status details of the corresponding category or customer are listed

in the Service Fault window. The appearance of Category and Customer symbols follow the same

characteristics as other objects in the FMS windows (color coding and blinking status directly

reflects the fault state of the object). From the Service Fault window an operator can open a Service

Fault Report window concerning a specific service and its faults.

The Critical Element Fault Monitoring window enables the real time supervision of faults related

to a particular trunk or node type. The window shows the selected trunk and node types with the

type label texts below the symbols. In the partitioned networks, the fault statuses of the trunk and

node types are shown for the selected regions. It is also possible to see the fault statuses which aresummed from all network faults without dependence on the regions. For more information on

partitioning, refer to 3.11 Partitioned Package.

The Fault Management System view can also be reduced to show only faulty network objects. This

option is very useful in large networks when only a small number of objects are faulty.

A warning beep facility can be activated at the workstation to give an audible warning when the

fault status in the network has triggered the preset severity level.

In addition to the fault monitoring facilities, the Fault Management System user interface also offers

other supporting tools. The fault view mode (maintenance status/service status/mask status) for

different types (network element/trunk/view/alarm/fault) can be defi

ned. Fault reports withseveral search conditions can be retrieved from the database and printed, if necessary. Old events

can be deleted from the fault history when no more needed. The Trouble Ticket facility can be

used to record information on network service problems. Any inconsistencies detected between

the system database and the actual network hardware can be studied in more detail. Tools for

defining the fault filtering characteristics also exist.

Fault Report Application

The Fault Report application can be used for monitoring individual faults and faulty services withsophisticated summarization, filtering and prioritization functions. The application has flexible

layout architecture, i.e. the windows can be dragged out from the main view, or moved and resized

within the application. Additionally, the windows can be tabbed together.


90




The Fault Report application can display numerous fault types, i.e. element faults, component

monitoring faults and faulty services, in the same window. The different fault types are shown in

their own fault perspectives providing different views to the fault data. By default, the Fault Report

application includes five different fault perspectives.

The Element Faults, Faulty Services and Component Monitoring perspectives can contain

the following subwindows.

• The main fault report window displaying the fault report rows. This window shows all report

rows according to the current perspective settings.

• Multiple summary windows showing graphical presentations of fault summaries. The summary

calculations are always based on the current perspective settings, and reflect the main fault report

window.

• The Fault Details window displaying a detailed view of the selected row in the report.

• Optional fault report subwindows showing related faults based on the selections made, e.g. the

element faults related to the selected faulty service or node faults. The selections made in thesummary windows are also applied to the fault report subwindows.

Fig. 54 Fault Report Application with Element Faults Perspective

The Fault Status and Fault Summary perspectives contain summary graphs of the overall

situation, e.g. the amount and severity of network element faults, faulty services and component

faults (server faults).


91




Fig. 55 Fault Report Application with Fault Status Perspective

Each fault perspective includes a predefined set of fault views affecting the fault data within the

perspective. Fault views can be used for filtering and sorting the fault data. The fault views are based on priority calculations whose results are shown in the Priority column as a star rating.

When using the fault views, every fault has a rating from one (lowest) to five (highest) stars

indicating its importance. By default, all data is shown as non-prioritized and sorted according to

the On-Time column.

Additionally, the fault perspectives contain a predefined set of summary windows presenting

summarized fault data in the pie and bar charts. The summary windows help to detect abnormalfault changes. Clicking a graph item displays detailed fault data in the fault report subwindow.

By using dynamic filters, the most significant faults currently existing in the network can be viewed

more thoroughly. Filtering affects all windows in the current perspective. These dynamic filters

are for temporary use only, and they are not permanently stored.


92




Fig. 56 Dynamic Filtering View

In the Fault Settings dialog, report types and time settings can be selected for the fault perspectives.

The layout settings of the Fault Report application can also be configured in this dialog. The fault

reports and summary graphs have their own settings. Many visual aspects, e.g. coloring and themaximum number of items to be shown can be configured. Additionally, it is possible to enable or

disable fault change messages for the reports and the summary graphs.

Fault Acknowledgment

Each fault event must be acknowledged. The fault acknowledging is either performed by the operator

or automatically by the system. When the fault is acknowledged, the alert indication (i.e. blinking)

stops. Alerting is thus active for an unacknowledged fault event if the fault itself has disappeared.

Only after the acknowledgement is performed and the fault is fixed in the network, the corresponding

object returns to the normal state and the fault event can be transferred to the fault history.

Fault Filtering

The purpose of fault filtering is to make it possible to fine-tune the fault management to meet

different needs. Faults that are filtered out (masked) are not stored in the database. If a fault is not

filtered, it is stored in the database. Those faults that are in the database can be later dynamically

view filtered in the Fault Management user interface.


93




Special Concepts Used in FMS

Fault Status Indication

A fault event reported by a network element contains the fields listed below.

The severity status has four categories:

• Critical

• Major

• Minor

• Warning

The maintenance status has three categories:

• Prompt Maintenance Alarm (PMA)

• Deferred Maintenance Alarm (DMA)

• Maintenance Event Information (MEI)

The maintenance status is converted from severity values in the following way:

• Critical mapped to Prompt Maintenance Alarm (PMA)

• Major mapped to Deferred Maintenance Alarm (DMA)

• Minor mapped to Maintenance Event Information (MEI)

• Warning mapped to Maintenance Event Information (MEI)

The service status of a fault event has two categories:

• Service alarm (S)

• Non-service alarm (non-S)

The fault status categories are used in the color coding of the FMS user interface to indicate the

severity of fault events.

The coding of different FMS object states in the Fault Management windows is by default as follows:

normal object Static color code:- CYAN for non-faulty objects

alerting object Blinking color code:

- RED for PMA/S/Critical faults

- YELLOW for DMA/Major faults

- GREEN for MEI/non-S/Minor/Warning faults

faulty object Static color code

- RED for PMA/S/Critical faults

- YELLOW for DMA/Major faults

- GREEN for MEI/non-S/Minor/Warning faults


94




It is possible to define a different color coding for a workstation with the Configure Fault Colors

dialog. Note, however, that the 8000 Intelligent Network Manager documentation in general refers

to standard coding (red, yellow, and green) when fault colors are concerned.

If an object contains several faults, the object symbol status and color are determined in accordance

with the most serious fault event. The order, from the most serious fault to the least serious one, is

as follows:

• Alerting PMA/S/Critical

• Alerting DMA/Major

• Alerting MEI/non-S/Minor/Warning

• Static PMA/S/Critical

• Static DMA/Major

• Static MEI/non-S/Minor/Warning

• Normal

Note that you can select the layout mode to be based either on the fault maintenance status (PMA,

DMA, MEI) or the service status (S, non-S). It is also possible to separate acknowledgement

information from priority calculation in the Set Fault Status View dialog. Thus the order, from the

most serious fault to the least serious one, is as follows:

• PMA/S/Critical

• DMA/Major

• MEI/non-S/Minor/Warning

• Normal

3.2.5 Trouble Ticket

The objective of the Trouble Ticket facility is to record, manage and control the service problems

associated with networks, customers and elements. A trouble ticket is a form filled in partly by

the system and partly by the operators. Tools for creating, viewing, editing and deleting these

tickets are supplied.

First category tickets are opened for general problems that do not involve a customer or a network

element. A customer ticket is attached to a specific customer in the network. Typically, it is created

as a response to a customer complaint. A network ticket is assigned to a specific network element,

either a trunk or a card.


95




Fig. 57 Trouble Ticket Dialog

3.2.6 Accounting Management

Accounting Management is supported for 8100 network elements. Circuit connection time reports

are based on the circuit accounting data that the 8000 Intelligent Network Manager components

(Router, Circuit Loop Tests, and Recovery) produce during the circuit’s lifetime. The accountingdata contains information on all activation, deactivation, testing and recovery actions on the circuit.

3.2.7 Security Management

Operator Access Control

Before any network management operation can be performed, an operator has to first perform a

login operation. In the login, the operator is requested to enter the correct username/password pair.

Several username/password combinations can be created by an operator for different purposes. If

wished, the system can force the operators to change their passwords regularly. The system can also

be set to limit the number of failed login attempts. Each login and logout operation is recorded in an

audit log where they can be viewed by an operator with security privileges.


96




Privileges

A set of privileges is attached to each operator when the username of an operator is created. A privilege is a permission to use a network management application or part of the application. In most

applications, privileges are divided into separate read and write privileges, allowing an operator

to use an application either in a read-only mode (no permission to alter any data) or in a modify

all mode (altering data in the database is allowed). In the case of some applications, operators can

be given even more detailed privileges, i.e. an operator can use an application to perform certain

operations while some other operations are prohibited.

In a partitioned network, it is possible to give operators permission to only manage part of the

network (one or several regions). Even inside a region, it is possible to restrict operator privileges

only to the backbone or access level of a network. If wished, other parts of a network can be hidden

altogether from a specified operator. For more information on partitioning, refer to 3.11 Partitioned

Package.

Profiles

Privileges to use different network management applications are grouped to form an operator

profile. A profile can then be attached to any network operator or group of operators. By giving

the same profile to a group of operators it is easy to add or remove privileges to/from several

operators at the same time.

LDAP and RADIUS Authentication

It is also possible to authenticate users from a central LDAP or RADIUS server. This is beneficial

when the user needs access to several tools. The passwords of the users are managed centrally at the

LDAP or RADIUS server. The passwords need to be changed only once in the LDAP or RADIUS

server, instead of being changed in each of the tools where the users have access. In addition, an

8000 Intelligent Network Manager user profile is assigned to the users in the LDAP or RADIUS

server. The user profile defines the user authorization for each of the 8000 Intelligent Network

Manager applications.

3.2.8 Scheduling Center

The Scheduling Center tool is used for scheduling tasks in 8000 Intelligent Network Manager.

The following types of tasks can be scheduled.

• Script/command line tasks. Any type of operating system scripts and commands can be sched-uled.

• Maintenance tasks. The database maintenance tasks can be scheduled. The database requires

regular maintenance in order to function optimally. These are mandatory tasks, and a default

schedule is automatically installed.

• Remote maintenance tasks. Maintenance tasks for the replicate database can be scheduled

(mandatory if NMRS is used).

• Database polling. Certain types of data can be polled from the main tables to the secondary tables

for reporting purposes.

• Backup tasks. Database resiliency requires database backups to be taken in adequate intervals.

These are mandatory tasks, and a default schedule is automatically installed.


97




• Housekeeper tasks. Housekeeper tasks clean up obsolete data, monitor the Sybase database server

parameters and delete aged data. These are mandatory tasks, and a default schedule is automati-

cally installed.

• Web Reporter tasks. Web Reporter tasks can produce reports and collect trend data.

• Enhanced Reporting tasks. Reports can be scheduled and post-processed e.g. e-mailed.

• Stored procedure. The stored procedures can be scheduled.

Fig. 58 Scheduling Center Dialog

3.2.9 OAM Management

The OAM Management tool is used for managing Ethernet operations, administration and

maintenance (OAM) functions, defined in IEEE 802.1ag and ITU-T Y.1731 standards. These

standards define a number of mechanisms and protocols for monitoring and testing Ethernet

connections.

• Continuity Check (CC) – Used for proactive OAM, i.e. for detecting loss of continuity or mis-

connections of an Ethernet connection.

• Loopback (LB) – Used for verifying connectivity of an Ethernet connection either between end-

points or between an endpoint and an intermediate point.

• Link Trace (LT) – Used as an on-demand OAM function for tracking the path of an Ethernet

connection, or for fault localization.


98




• Frame Loss Measurement (LM) – Used for measuring the frame loss experienced by an Ether-

net connection.

• Frame Delay Measurement (DM) – Used for measuring the frame delay and delay variation of

an Ethernet connection.

The OAM Management tool supports management of these mechanisms, as well as management of

the Ethernet OAM monitoring objects: Maintenance Domain (MD), Maintenance Association (MA),

Maintenance Association Endpoint (MEP) and Maintenance Domain Intermediate Point (MIP).

Fig. 59 OAM Management Tool

In addition to node-by-node management of Ethernet OAM, OAM Management supports also

service and trunk associated OAM management. This makes it possible to configure Ethernet OAM

directly for network level objects, such as Ethernet trunks, VPLS VPNs, Ethernet and VLAN pseudowires and VLAN VPNs, instead of configuring it separately for each endpoint.


99




Fig. 60 Service and Trunk Associated OAM Management

3.2.10 IP Address Management

The IP address management is a feature designed to prevent duplicate IP addresses in the network,

which could potentially interfere with the network configuration. When adding new IP addresses

or updating existing ones to the 8000 Intelligent Network Manager database, a check for findingduplicate IP addresses is done. If duplicates are found, a warning is displayed and then the operator

has two options: the warning can be overridden and the configuration can be continued, or the

configuration can be cancelled.


100




Faults are created for each network resource having the same IP address. In addition, the All IP

Addresses or IP Duplicates query can be executed in the Enhanced Reporting tool. The query

shows all the duplicates among the existing IP addresses.

Duplicate IP addresses are considered real if they can cause a conflict. There are no warnings or

faults for allowed duplicates. Examples of allowed duplicates include IP interfaces in different

MPLS VPNs, interface IP and node management IP in the same node, and Communication Server

IP and its domain adapter IPs.

The IP address management is supported for 8600 and 8800 IP interfaces, node IPs (management IP,

router ID IP, etc.) and Communication Server IPs. This feature is also supported in Node Managers,

VPN Provisioning, Autodiscovery Service and Macro Manager.

3.2.11 IP Address Pool Management

The IP Address Pool Management tool is designed to manage IP address pools and to allocate IP

addresses from the pools helping users to easily manage the IP configurations in the network. The IP

address pools can be added, modified and removed in the tool. IP addresses can be automatically

allocated from a certain IP address pool, or the next available IP address from an IP address pool can be assigned to an interface.

In addition, the All IPAddress Pools or IP Address Pool Usage query can be executed in the

Enhanced Reporting tool. The query shows information either on all IP address pools or on the

allocation of a certain IP address pool.

The IP address pool management is supported in Node Managers for 8600 IP and loopback

interfaces, and for 8800 L3, loopback and IRB interfaces.

Fig. 61 IP Address Pool Management Tool


101




3.2.12 Automated Deployment

The automated deployment is designed for deploying a large number of network elementsquickly with a minimum amount of manual effort. The automated deployment automates the

network element deployment by using the extensive preplanning support in 8000 Intelligent

Network Manager. Network element configurations are preplanned in the database with a set

of user-configurable templates. Newly deployed elements are detected automatically by 8000

Intelligent Network Manager and the configuration is pushed to the network element immediately

when the element is available in the network. It is possible to include IP VPN endpoint configuration

and even testing in the configuration process enabling the new network element to carry customer

traf fic within minutes after the physical installation and power on.

For the operator, the automated deployment functionality provides the following benefits, resulting

to lower operational expenses and fast time-to-market:

• Shortens the network and service rollout from days to minutes.

• Minimizes human errors and extra site visits.

• Enables ef ficient resource utilization, and reduces the training needs.

The deployment process takes place in four main phases:

• Planning (deployment planning and network planning)

• Physical installation

• Identification of the network element

• Deployment

The planning and physical installation requires manual work whereas the identification of thenetwork element and the deployment take place automatically. In the planning phase the operator

prepares 8000 Intelligent Network Manager for the deployment of the network elements (see the

figure below). The deployment planning is done for

• providing data for the Deployment Service (acting as a DHCP server) and 8000 Intelligent Net-

work Manager for identifying the network elements to be added to the network,

• preplanning the element and service configurations for the network elements to be added, and

• defining a deployment template containing the deployment steps, i.e. the operations to be run

once the network element is physically installed to the network.

8000 Intelligent Networ k Manager includes a set of wizards for assisting in the deployment

planning. The wizards are aligned for an easy creation of the basic configuration for adding thenetwork elements and endpoints to the IP VPN RAN for LTE. The configuration wizards and a

wizard for defining the deployment template are bundled into an application called Multi Node

Deployment Tool. The Multi Node Deployment Tool will pre-deploy the nodes, i.e. the preplanned

element and service configurations are created in the 8000 Intelligent Network Manager database.

Once the pre-deployment is done, it is possible to make further modifications to the preplanned

configuration in 8000 Intelligent Network Manager database with the 8000 Intelligent Network

Manager tools (e.g. Node Manager or VPN Provisioning).


102




Fig. 62 Multi-Node Deployment Tool

Some layer 2 network planning is needed if the smart router autoconfiguration feature and the

DHCP relay agent information option 82 [RFC3046] are used for providing the initial management

IP address. The network design principle for supporting the location-based identification of the

option 82 is illustrated in the figure below. The network elements are connected to an Ethernet

switching network. The first Ethernet switch identifies the location of the network elements site

based on its ports. It translates the network element VLANs (e.g. VLAN ID 100) in each port to a

unique VLAN. At the DHCP relay agent, the Ethernet port number and the VLAN ID are mapped to

a circuit ID (e.g. “ge1/0.100”) and the routed ID of the DHCP relay is mapped to a remote ID. The

Deployment Service identifies the network element based on its location, i.e. circuit ID and remote

ID, and assigns an IP address allocated for the network element.


103




Fig. 63 Network Planning for Supporting DHCP Relay Agent Information Option 82

In the physical installation phase, the field technician connects the physical cables and powers thenetwork element on. If the smart router autoconfiguration feature is used in the process, the field

technician needs to connect an autoconfiguration dongle to the CLI console port before the network

element is powered on. This enables the network element autoconfiguration functionality where

the network element scans Ethernet interfaces and VLANs while searching for the DHCP server.

For further details of the smart router autoconfiguration, the use of DHCP relay agent information

option 82 and interface scanning, see Tellabs®

8600 Smart Routers IP Forwarding and Traf fic Management Con fi guration Guide.

The identification of the network element is based on the IP address given to the management

interface of the network element. The IP address can be automatically given by the Deployment

Service or it can be configured by some other means. When the Automated Deployment Network

Scanner (ADNS) finds the added network element, it tells the Automated Deployment Controller

(ADC) to start the deployment.

The added network element is configured in the deployment phase. If the DHCP protocol was used

for giving a (temporary) IP address, 8000 Intelligent Network Manager first configures a permanent

IP address for the management interface and removes the DHCP client configuration. Once the

management communication to the network element is ensured, 8000 Intelligent Network Manager

configures the element and services as planned in the planning phase. For accomplishing this, theAutomated Deployment Controller runs the operations defined in the deployment template (made in

the planning phase). The deployment operations may include, for example,

• downloading a certain element software version to the network element,

• copying the configuration from the database to the NE by raising the state of the node to installed

or In Use,

• raising the states of trunks and connecting RSVP-TE tunnels,

• adding new endpoints to IP VPNs.

The automated deployment is currently available for the 8602 Smart Router, 8605 Smart Router,

8609 Smart Router and 8611 Smart Router NEs.


104




3.3 Provisioning Packages

The TDM, ATM, Ethernet, FR/HDLC, IP VPN and Optical Provisioning Packages allow the operator

to choose what kind of services to configure in the network. There are three tools for provisioning

the services available in the 8000 Intelligent Network Manager: Router, VPN Provisioning

and VLAN Manager. The Router tool is used to provision TDM and optical circuits, the VPN

Provisioning tool is used to configure IP VPNs and VLAN VPNs, Ethernet, ATM, TDM, Frame

Relay and HDLC pseudowires, and the VLAN Manager tool is used to configure VLAN VPNs in

the 6300 and 8100 networks. Each provisioning package contains the following functionality:

• IP VPN Provisioning - The IP VPN Provisioning Package allows the user to provision IP VPNs

with the VPN Provisioning tool.

• Optical Provisioning - The Optical Provisioning Package allows the user to establish optical

(DWDM) and G.709 OTN connections in a network where the 7100 system is deployed.

• Ethernet Provisioning - The Ethernet Provisioning Package allows the user to configure Ethernet

pseudowires, VPLS VPNs and 7090/7100 based VLAN VPNs with the VPN Provisioning tool.

It also allows the user to provision VLAN VPNs in the 6300 and 8100 networks with the VLAN

Manager tool.

• ATM Provisioning - The ATM Provisioning Package allows the user to configure ATM pseu-dowires with the VPN Provisioning tool.

• TDM Provisioning - The TDM Provisioning Package allows the user to configure PDH and SDH

circuits with the Router tool and TDM pseudowires with the VPN Provisioning tool.

• FR/HDLC Provisioning - The FR/HDLC Provisioning Package allows the user to configure

Frame Relay and HDLC pseudowires with the VPN Provisioning tool.

In addition, there is a Tunnel Engineering tool to provision manually traf fic engineered LSPs inMPLS networks. The Tunnel Engineering tool is automatically included in each of the Provisioning

Packages, except for the Optical Provisioning Package.

Below, a more detailed description about each of the provisioning tools - Router, VPN Provisioning,VLAN Manager and Tunnel Engineering - is given.

3.3.1 Router

General

Router is a flexible 8000 Intelligent Network Manager tool where you can set up and manage circuits

through the 8000 system network. Router shows an overview of the network with the Navigator

Tree, List and Network View windows, views for different network objects (nodes, trunks, NTUs

and locations) and displays connection routes. You can zoom into nodes and interfaces to view and

set the communication parameters of the interfaces.

Connections are referred to as circuits. Circuits can be routed through the 6300, 7100, 8100 andmTera UTP network elements both automatically and manually. It is also possible to terminate

SDH and PDH circuits in the 8600 and 8800 network elements. The circuits can be completely or

partially connected and disconnected. It is also possible to create planned circuits without a physical

network. In this way the connections can be built in advance using planned interfaces and trunks.

The circuit only has to be connected to be operational when the physical network is available.


105




Currently optical, ODUk, SDH, SONET, PDH, ATM and Frame Relay circuits are supported.

Circuits are also used to route virtual VC-4/2/12, VLAN, 2M, 1/1, ATM, Frame Relay and STM-64

trunks through the high-order network.

By enabling the Multi-Layer Routing feature, you can semi-automatically create VC-12 trunks over

the SDH 4/1 layer with Trunk Wizard when routing PDH 1/0 circuits.

With 2M Cascaded circuits, you can use the 4/1, 1/1 and 1/0 layers in the same circuit without

having to create virtual trunks when switching between layers.

If you have 6300 ETEX units in your network, you can use their VC groups in Diverse SDH circuits.

With the diverse circuit you can route each child VC interface of a VC group separately or together

with a selection of any other child VC interface of the VC group. You can also add or remove VC

child interfaces later to / from the VC group and route / unroute them later without disturbing the

traf fic. This can be used with LCAS for network protection and dynamic capacity change.

Circuit Components

A circuit is identified by a unique ID and name. The necessary circuit parameters, such as capacity,

customer and signaling, must be specified at the initial state when creating the circuit. The capacity

can be in the range of 8 kbps – 10 Gbps. The basic circuit consists of two endpoints (NTUs

or interfaces) and a route.

A route is created by allocating, manually or automatically, capacity from the trunks. Manual

routing is done by simply selecting (double-clicking on) the trunks with enough capacity (colored

green/dark green). The automatic routing uses a shortest path algorithm to find the optimal route by

calculating a set of weighted criteria (length, cost, delay and occupation).

Reserve backup routes for PDH 1/0 circuits can be pre-routed by Router or dynamically routed by

Recovery Management. They are used by Recovery Management to back up the primary route

when necessary.

In a partitioned network, the network is divided into regions into two levels, backbone and access.

Backbone level trunks are high-capacity trunks carrying only inter-regional data. Access level

trunks are mainly used for carrying data within the region. To keep this structural two-level network

well differentiated, you need to control the way you route. In short, regional routes use access

level trunks, and inter-regional routes mainly use backbone level trunks. For more information on

partitioning, refer to 3.11 Partitioned Package.

A complex circuit with several endpoints consists of several subcircuits to help manage the circuit.

In this way the circuit topology can be changed even while the original circuit is still active. The

subcircuits can, naturally, be separately connected and disconnected.

Circuit Topologies

The types of circuits supported are point-to-point (pp), point-to-multipoint (pmp) and broadcast (bc).

The point-to-point type of circuit, which is the most commonly used, is bi-directional and consists

of two end interfaces and a route, see Fig. 6. Interfaces for test purposes can also be added, butthey are used only in the Circuit Loop Test tool. When transporting a PCM signal, it is possible

to compress the signal to an ADPCM signal in order to save trunk capacity in the network. The

compression can be from 64 kbps to 32, 24, 16 or 8 kbps.


106




A special Circuit Swap feature can be used for the swap type of point-to-point circuits. The idea is

to allow the replacing of a circuit endpoint by another when, for some reason, the primary endpoint

is damaged. By convenience, several swap circuits can use the same swap point in order to allow

replacement of endpoints for several circuits in a single step.

The broadcast type of circuit is uni-directional and consists of one master and any number of slave

interfaces, branch nodes, subcircuits and routes.

The point-to-multipoint type is similar to the broadcast type of circuit, but the data flow is

bi-directional. Additionally, branch nodes have special Point-to-Multipoint (PMP) Servers that are

used to control data flow in the slave-master direction.

Network Optimization Tools

With the Reroute Circuits tool, you can select a set of PDH or SDH circuits and select alternative

endpoints and automatically route alternative paths with desired routing templates. Then the

connections can be swapped, and the unused routes deleted. This is useful when new nodes/trunkshave been installed or when the network topology is changing due to growth.

For the PDH, SDH and ATM circuits you can also route, unroute, connect and disconnect the

original paths.

The routing template basically controls what trunks to use or not to use. Weights can also be set

to optimize the route for cost, length, delay, occupation or a combination of these. The routing

templates are stored in the database, and special privileges are required to edit them. It is also

possible to keep a local routing template that is not stored in the database.

3.3.2 VPN Provisioning

The VPN Provisioning package provides tools for creating, modifying and deleting different kinds

of MPLS VPN services, in other words, pseudowires, VPLS VPNs and BGP/MPLS IP VPNs. In

addition, provider bridging based VLAN VPN services for the 7100 packet subsystems as well as

7090 and 8800 network elements are supported. Additionally, G.8032 rings are supported for the

7100 packet subsystems. These services are collectively referred to as VPN services in the text

below. The VPN Provisioning tool provides a high-level user interface for establishing any type

of these VPN services. Interfaces in which VPN endpoints are created can be chosen from a

tree view, where interfaces or entire nodes bound to customer sites are displayed below customer

and site information.

The main window of the VPN provisioning tool is shown in the figure below.


107




Fig. 64 Main Window of VPN Provisioning Tool

The VPN Provisioning tool supports ten different VPNs: Ethernet Pseudowire Mesh, ATM

Pseudowire Mesh, TDM Pseudowire Mesh, FR Pseudowire Mesh, HDLC Pseudowire Mesh, VPLS

VPN, VLAN VPN, G.8032 ring, BGP/MPLS VPN and Default Routing Access.

A Pseudowire Mesh VPN has a point-to-point topology with two endpoints connected with a

pseudowire. You may create several point-to-point pseudowires under the same VPN, therefore

creating a pseudowire mesh. For the Ethernet pseudowires, the two endpoints will either be in

Ethernet ports or VLAN/S-VLAN sub-interfaces. For ATM pseudowires, the endpoints will either be ATM VP or VC sub-interfaces. For TDM pseudowires, the endpoints will be either E1/T1

interfaces or nx64 kbps interfaces configured on top of the E1/T1 interfaces. The E1/T1 interfacemay be native E1/T1 interfaces or E1/T1 streams aggregated onto SDH/SONET channelized

interfaces. For Frame Relay pseudowires, the endpoints will be Frame Relay PVCs. For HLDC

pseudowires, the endpoints will be HDLC interfaces. Also TDM, ATM, Ethernet, Frame Relay and

HDLC cross-connections (locally connected pseudowires) are supported.

For pseudowires, two different topologies are supported: single-segment and multi-segment. These

differ in how the pseudowire is carried in the packet-based transport network. A single-segment

pseudowire is carried end-to-end by one packet network tunnel, whereas a multi-segment

pseudowire consists of many segments, each carried by a separate tunnel, which are switched inintermediate nodes. Multi-segment pseudowires provide a more flexible and scalable mechanism for

managing pseudowires, supporting e.g. aggregation of multiple pseudowires into the same tunnel in

hub points and interconnectivity between different packet network domains.


108




Fig. 65 Multi-segment Pseudowire

For protecting pseudowire-based services, pseudowire redundancy (as per [draft-ietf-pwe3-

redundancy-03] and [draft-ietf-pwe3-redundancy-bit-03]) is supported. The pseudowire redundancy

mechanism supports multiple protection schemes, e.g. protecting a multi-segment pseudowire

end-to-end by configuring multiple redundant paths for the PW, or providing multi-homing based

service protection when a part of the service is implemented with pseudowires. The pseudowire

redundancy for the end-to-end protection is presented below.

Fig. 66 Pseudowire Redundancy

VPLS VPNs may have multiple endpoints. Each endpoint is connected, either locally or via a

pseudowire, to an Ethernet Virtual Switching Instance (VSI). The VSIs in different nodes are then

interconnected with MPLS pseudowires either in a full mesh fashion or, when using hierarchicalVPLS (H-VPLS), in a hierarchy, to allow any-to-any connectivity between the endpoints. Together,

the switches form a Virtual Private LAN Service instance, emulating a single LAN to the end user.

An example of an H-VPLS VPN is presented below.


109




Fig. 67 H-VPLS VPN

A VLAN VPN is a static S-VLAN based service which may have multiple endpoints. VLAN trunks

and G.8032 rings are used for routing the service in such way that there are no loops in the route (a

G.8032 will not form a loop since one of the trunks is always open). The endpoints of the service

may e.g. terminate a single/multiple C-VLAN(s) in a Customer Edge Port (CEP), all C-VLANs of

a port-based Customer Network Port (CNPP) or an S-VLAN of an S-tagged Customer Network

Port (CNPS). This service can also be a protected point-to-point service, but in such case the route

consists of an RVT trunk. In addition, a VLAN VPN service can be terminated to a VPLS/PW

VPN service in an 8800 network element. For a protected point-to-point service using the openRVT solution in the 7090 network, the termination towards the VPLS service in the 8800 network

provides dual homing i.e. there are two termination endpoints towards the VPLS service.

There are two different types of Resilient VLAN Tunnels (RVT), i.e. XC-RVT and VB-RVT, and

they are used for protecting point-to-point VLAN services. An RVT has a working and a protection

path, which are routed using VLAN trunks and G.8032 rings, but the path must always start/end

using a VLAN trunk. The XC-RVT is used in the 7100 nodes for connecting/tunneling one or more

point-to-point VLAN services at the endpoint nodes of the RVT whereas the VB-RVT is used in the

7090 nodes for bridging a single point-to-point VLAN service to the RVT. The RVT has a protection

group at its endpoints for switching between the working and protection paths depending on when

a failure occurs in the active path.

A G.8032 ring consists of a set of VLAN trunks making up a ring. The VLAN VPN services can

be routed through the G.8032 rings, and they will be protected by the ring protection mechanism

even if a single trunk in the ring fails. The G.8032 ring provides an alternative and faster protection

mechanism to the spanning tree protocol for building multipoint VLAN services. The protection

mechanism can also be used as an alternative to an RVT trunk if the endpoints of the point-to-point

service are located at the nodes of the ring. This solution is more scalable since the protection

groups used in the nodes of the ring are shared by many services. One of the trunks in the G.8032

ring is defined as a Ring Protection Link (RPL) trunk. As the VLAN traf fic in the ring should

not make any closed loops, the RPL trunk is open if there are no errors in the ring, and it will be

closed when there is an error in another trunk of the ring. A G.8032 ring can also have one or more

sub-rings. The sub-ring is connected to its parent with two nodes (dual homing for avoiding a

single point of failure) called interconnection nodes. The sub-ring in a trunk has an own RPL trunk

functioning according to the same principle as in the main/parent ring.


110




BGP/MPLS VPNs may have multiple endpoints. Three different topology types are supported for

these kind of VPNs

1. Full mesh: Traf fi

c may be sent from any endpoint to any other endpoint through the VPN.2. Central services hub-and-spoke: Traf fic may be sent from a single hub endpoint to any of the

spoke endpoints or from any of the spoke endpoints to the hub endpoint. However, the spoke

endpoints may not communicate with each other through the VPN.

3. Full-featured hub-and-spoke: Also referred to as firewall hub-and-spoke based on one typi-

cal application. In this VPN topology the spoke endpoints can communicate with each other

through a customer router that lies behind the hub endpoint. Actually there are two endpoints

for hub here, one for incoming traf fic from the spokes towards the hub and another for outgoing

traf fic from the hub towards the spokes.

In the Default Routing Access type of service, the interfaces associated with the service do

not belong to any VPN. The IP traf fic originating from the interfaces will be routed using the

default routing table, thus interfaces belonging to different Default Routing Access instances may

actually communicate with each other. The Default Routing Access instances can be thought of as administrative instances for the service, used for documenting the interfaces where broadband

services have been configured.

In addition to these topologies available for customer VPNs carrying payload data, VPN

provisioning also supports a single management VPN (one per network) enabling central

management of the non VPN-aware CE routers on the customer premises. The topology of the

management VPN is like that of the central services hub-and-spoke VPN, with the exception that the

management VPN may have more than one hub site.

The work flow for establishing IP VPN services is basically the same as for pseudowires. However,

for the IP VPNs there are some additional steps related to classifying and policing the traf fic and

configuring routing options towards the customer networks.

Fig. 68 Endpoint Dialog


111




The Endpoint dialog is used for defining properties based on which different end customer sites

are connected to a BGP/MPLS VPN.

Fig. 69 Service Classi fi cation Templates Dialog

The Service Classification Templates dialog is used for defining how different kind of customer

traf fic is directed to different service classes when entering the VPN from a customer site.

Pseudowire Wizard

The Pseudowire Wizard is a very handy tool when creating a large number of pseudowires in the

network. The wizard allows you to select a group of source and destination interfaces from the

network and it will then create the needed pseudowires between the selected interfaces. If required,the wizard can connect the pseudowires during the same operation.


112




Fig. 70 Pseudowire Wizard Dialog

Cell Site Wizard

The Cell Site Wizard combines the steps needed when adding pseudowire connections from a

NodeB to an RNC. The wizard supports the user with automated tools to create and configurethe required ATM, TDM or Ethernet interface hierarchy and provision the required pseudowires.

The wizard supports configuration templates, which can be tailored for different types of NodeBs

as required by the network.


113




Fig. 71 Cell Site Wizard

Discovering Pseudowires and IP VPNs

It is possible to discover pseudowires and IP VPNs that have been configured in the 8600 network

elements directly through the command line interface. The discovery functionality has been

implemented for those who want to roll out the network quickly with pre-generated CLI scripts.

After the roll out phase, the pseudowires and IP VPNs can be uploaded to the 8000 Intelligent

Network Manager and managed centrally from the network management system with the discovery

functionality.

Reparenting Pseudowires

VPN Provisioning also contains Pseudowire Editor that is convenient to use for re-parenting

pseudowires. You can select a group of interfaces used for pseudowires and select Move

Endpoints from the pop-up menu. Then select the destination interfaces where you want to move

the pseudowires and click start. All pseudowires in Pseudowire Editor will be moved to the

new destination interfaces. Pseudowire Editor can also be used to edit basic parameters of the

pseudowires.


114




Fig. 72 Pseudowire Editor Dialog

7100 Service Endpoint Mapping Wizard and 7100 VCAT Diverse Circuit Wizard

Creating an end-to-end packet-over-SDH/SONET (PoS) circuit using the 7100 SSM-D/X cards

requires many steps, and critical steps in the procedure may be overlooked leading to suboptimal

performance. There are two wizards in 8000 Intelligent Network Manager aimed at helping to

make such procedures easier and more effective: 7100 Service Endpoint Mapping Wizard and

7100 VCAT Diverse Circuit Wizard.

The 7100 Service Endpoint Mapping Wizard is a tool used for setting the parameters and optionally

creating all the required entities, including the Ethernet ports, link aggregation groups and Ethernet

virtual connections associated with an SDH/SONET circuit that has already been created with

the Router tool.

The 7100 VCAT Diverse Circuit Wizard encompasses all the functionality found in the 7100 ServiceEndpoint Mapping Wizard, but additionally it can be used for creating an entirely new SDH/SONET

diverse circuit used for carrying the traf fic across the network.


115




Fig. 73 7100 Service Endpoint Mapping Wizard

Fig. 74 7100 VCAT Diverse Circuit Wizard


116




3.3.3 Tunnel Engineering

The Tunnel Engineering tool can be used for creating traf fic engineered LSPs either when provisioning an MPLS VPN or as an entirely separate action. It can also be used for setting explicit

routes for traf fic engineered LSPs and for viewing routes of existing LSPs in the network.

The Tunnel Engineering tool supports the following tunnel types:

• RSVP-TE tunnels. The RSVP tunnels are MPLS-switched tunnels signaled with the RSVP-TE

protocol.

• MPLS-TP tunnels. The MPLS-TP (MPLS Transport Profile) tunnels are MPLS-switched tunnels

configured statically, node by node, in the network by 8000 Intelligent Network Manager.

• IP tunnels. The IP tunnels are used for transporting pseudowires over an IP infrastructure when

MPLS is not available.

• Static LSPs. The static LSPs are statically configured single-hop MPLS tunnels.

The main window of the Tunnel Engineering tool is shown in the figure below.


117




Fig. 75 Main Window of Tunnel Engineering Tool

For the RSVP-TE and MPLS-TP tunnels, the Tunnel Engineering tool supports automatic,

semi-automatic and manual routing of tunnels. In the automatic routing, the tunnel is automatically

routed between the endpoint nodes. In case of the RSVP-TE tunnels, the route is calculated by the

source node using the CSPF (Constrained Shortest Path First) algorithm, whereas in case of the

MPLS-TP tunnels, the route is calculated by 8000 Intelligent Network Manager using its internalSPF (Shortest Path First) algorithm. In the semi-automatic and manual routing, the user defines

the hops (strict and/or loose) that are to be used as part of the route. In the manual routing all hops

are given along the path, whereas in the semi-automatic routing only some of the hops are given

and the node (in case of RSVP-TE) or 8000 Intelligent Network Manager (in case of MPLS-TP)

calculates the rest of the route. Additionally, it is possible to use bandwidth reservations for the

tunnels. A bandwidth value can be defined for the tunnel, which is to be reserved on the trunks alongthe path of the tunnel. For the RSVP-TE tunnels, bandwidth reservations are maintained by the

network elements, whereas for the MPLS-TP tunnels, the bandwidth reservation is maintained in the

8000 Intelligent Network Manager database.


118




For the MPLS-based tunnels (RSVP-TE and MPLS-TP), both E-LSP and L-LSP tunnels are

supported. The difference between these is essentially that while a single E-LSPs can carry traf fic

belonging to multiple service classes, a single L-LSP only carries traf fic belonging to a single

service class.

Tunnel protection is supported for the RSVP-TE and MPLS-TP tunnels. For the RSVP-TE tunnels,

RSVP-TE 1:1 Path Protection and RSVP-TE Fast Reroute Protection (RFC 4090) are supported.

For the MPLS-TP tunnels, MPLS-TP Linear Protection (RFC 6378) is supported.

Discovering Tunnels

It is possible to discover RSVP-TE and MPLS-TP tunnels that have been configured in the 8600 and

8800 network elements directly through the command line interface. The discovery functionality

has been implemented for those who want to roll out the network quickly with pre-generated CLI

scripts. After the rollout phase, the tunnels can be uploaded to the 8000 Intelligent Network

Manager and centrally managed from the network management system.

Discovering other tunnel types is currently not supported.

3.3.4 VLAN Manager

VLAN Manager is an optional tool for 8000 Intelligent Network Manager. It is used for graphical

and user friendly provisioning of VLAN connections, i.e. VLAN VPNs.

VLAN Manager is a part of Ethernet switched solution (ESS) concept. The concept makes it

possible to use an existing 6300/8100 network as a core network for layer 2 Ethernet services.

VLAN Manager is used only for VLAN VPN provisioning. Other management tasks suchas creating layer 1 connections are performed with other 8000 Intelligent Network Manager

applications, which enable seamless integration into TDM provisioning and eliminate the need of

redundant configuration work.

VLAN trunks, i.e. layer 1 connections between Ethernet/VLAN switching network elements, are

created in the same way as the other trunk types in 8000 Intelligent Network Manager by using

Network Editor. VLAN Manager considers VLAN trunks as TDM capacity reserved for VLAN

Manager use and uses the VLAN trunk information stored into the 8000 Intelligent Network

Manager database to calculate optimal routes for VLAN VPNs.

The VLAN Domain Configuration tool has also been integrated into Network Editor. The tool

automates the configuration of VLAN domain wide (e.g. QoS) parameters into the Ethernet/VLAN

switching network elements. VLAN domains are separate Ethernet/VLAN network instances, i.e.sets of Ethernet/VLAN switching elements and VLAN trunks that connect them.

3.4 Testing Package

3.4.1 Overview

The Testing Package contains the Packet Loop Test and Circuit Loop Test tools for troubleshootingcircuits, pseudowires, VLAN, VPLS, and IP VPNs services. The Circuit Loop Test tool can be used

for services in TDM-based networks whereas the Packet Loop Test tool has been designed for

services in MPLS and Ethernet based networks.


119




3.4.2 Packet Loop Test

Overview

Packet Loop Testing is a testing tool for detecting and localizing problems in packet networks and

verifying services, created by 8000 Intelligent Network Manager VPN Provisioning tool. It contains

a collection of test packages including different test items. The network can be tested after setting up

a new node or fixing a trunk fault or before creating a new service. With IP VPN and PW tests the

user can ensure that the IP VPN and PW are working correctly and fulfilling the QoS requirements

configured before taking the service into use.

The tests can be executed manually or they can be scheduled for automatic execution in the background. The tests running in the background could be used to give the operator a daily view of

the network and the services.

The results of the tests can be stored in the database for further analysis.

Test Packages

Packet Loop Testing contains the following test packages and test items:

Management Communication Test Package contains functionality for testing the communication

between 8000 Intelligent Network Manager and nodes. This package includes the following tests:

• Node Management Connectivity Test pings nodes to check the IP-level connectivity between

the Communication Server and the nodes.

• Node Management Traceroute Test detects the route along the Communication Server and thenodes. It can be useful when investigating management connectivity problems between the 8000

Intelligent Network Manager and a node.

• Trunk Management Connectivity Test test the IP-level connectivity between the Communica-

tion Server and one or both end nodes of a specific trunk in the network.

• IP VPN Management Connectivity Test pings all endpoint nodes of the IP VPN to check the

IP-level connectivity between the Communication Server and the nodes. Note that the loopback

interface of the node is tested instead of the real IP VPN endpoint interface.

• PW Management Connectivity Test pings all endpoint nodes of the pseudowire to check the

IP-level connectivity between the Communication Server and the nodes. Note that the loopback

interface of the node is tested instead of the real PW endpoint interface.

• TE Tunnel Management Connectivity Test pings the endpoint nodes of the tunnel to check theIP-level connectivity between the Communication Server and the nodes. Note that the loopback

interface of the node is tested instead of the real tunnel endpoint interface.


120




Fig. 76 Trunk Management Connectivity Test

Node Network Test Package contains functionality for testing basic router network communication

between nodes in the network. These tests can be run unidirectionally or bidirectionally.


121




• Node Connectivity Test pings nodes to check the IP or LSP level connectivity between two

nodes. The LSP level connectivity test requires MPLS support from the nodes – at the minimum.

• Node Traceroute Test traces the path between two nodes. It can be useful when investigating

node connectivity problems in the network.

• The Node Quality Test Sub-package can be used for testing the quality of the connectivity be-

tween two nodes.

• Node Throughput Test is an intrusive test for determining the maximum bandwidth avail-

able between two nodes without having the traf fic discarded. This test should be used with

care as it will affect live traf fic in the network and is usually only used in the initial deploy-

ment phases of the network. This test is supported in the 8600 node hardware and therefore

throughput between two nodes can be tested up to the line-speed of the interfaces in the

node. Packet distribution, send interval and QoS distribution can conveniently be selected

using predefined templates. It is also possible for the user to define his own distribution

values.

• Node Round-trip Delay Test is used for testing the round-trip delay of packets sent between

two nodes. This test is supported in the 8600 node hardware and therefore micro-second

accuracy can be obtained for the test results.

• Node One-way Delay Test can be used for testing the delay of packets sent between two

nodes. It needs accurate time synchronization between the nodes e.g. by using NTP.

• Node One-way Delay Variation Test can be used for testing the one-way delay variation

between two nodes. This test is supported in the 8600 node hardware and therefore micro-

second accuracy can be obtained for the test results.

• Node One-way Packet Loss Test can be used for testing the packet loss for packets sent

between two nodes. Packet distribution, send interval and QoS distribution can be defined

using predefined templates, or the user can define them manually.

Fig. 77 Node One-way Delay Variation Test


122




Trunk Test Package contains functionality for testing basic router network communication between

trunk end nodes in a basic router network. These tests can be run unidirectionally or bidirectionally.

• Trunk Connectivity Test pings trunk end nodes to check the IP-level connectivity between those

two end nodes.

IP VPN Test Package contains functionality for executing tests on individual VPNs. The IP VPN

tests are a combination of different tests that are organized so that the operator needs to execute

only a few tests manually.

• IP VPN Connectivity Test gives the operator the ability to test the connectivity automatically

between all endpoint interfaces of an IP VPN.

• IP VPN Traceroute Test allows the operator to discover the routes between all endpoint inter-

faces of an IP VPN.

• IP VPN Quality Test Sub-Package enables the operator to test the quality of transmission be-

tween each site in an IP VPN. These tests are supported in the 8600 node hardware, therefore,

both elements must be 8600 nodes.

• IP VPN Throughput Test is an intrusive test for determining the maximum bandwidth that

a certain IP VPN has between the endpoints in the IP VPN. This test will affect the IP VPN

traf fic and can also affect other traf fic in the network, so it should be used carefully. This

test is typically used when provisioning a new IP VPN to make sure that the IP VPN can

carry the traf fic provisioned for the user without discarding traf fic. This test is supported in

the node hardware, which means that traf fic can be generated up to the interface line-speeds.

Packet distribution, send interval and QoS distribution can conveniently be selected using

predefined templates. It is also possible for the user to define his own distribution values.

• IP VPN Round-trip Delay Test is used to measure the round-trip delay of packets being

sent between the endpoints in the IP VPN. This test is supported in the node hardware, and

therefore micro-second accuracy can be obtained.

• IP VPN One-way Delay Variation Test is used to test the one-way delay variation of test

packets sent between the endpoints in an IP VPN. This test is supported in the node hard-

ware, and therefore micro-second accuracy can be obtained.

• IP VPN One-way Packet Loss Test can be used for testing the packet loss for packets sent

between endpoints in an IP VPN. Packet distribution, send interval and QoS distribution can

be defined using predefined templates, or the user can define them manually.

The following figure shows an example of the GUI of an IP VPN Connectivity Test window:


123




Fig. 78 IP VPN Connectivity Test

The following figure shows an example of the IP VPN Round-trip Delay Test window:

Fig. 79 IP VPN Round-Trip Delay Test

PW Test Package contains functionality for testing basic router network communication between

pseudowire end nodes in a basic router network. These tests can be run unidirectionally.


124




• PW Connectivity Test can test the connectivity inband and end-to-end for a pseudowire having

the VCCV control channel enabled using the VCCV ping for all PW types. This is a powerful

test for verifying the consistency between the control plane and forwarding plane for the tested

PW. In addition, the ATM ping is supported for ATM based PWs, and Ethernet Ping for Ethernet

PWs. Maintenance endpoints (MEPs) need to be created at the ends of an Ethernet PW in order to test it. It is also possible to select an ICMP ping based test between the end nodes of the PW

e.g. when VCCV is not enabled for a PW or there are no MEPs at the ends of an Ethernet PW.

• PW Traceroute Test traces the path inband and end-to-end for a pseudowire having the VCCV

control channel enabled using the VCCV traceroute for all PW types. This is a powerful test

for verifying the consistency between the control plane and forwarding plane for multi-segment

PWs. It is also possible to select an ICMP traceroute based test between the end nodes of the PW

e.g. when VCCV is not enabled for a PW.

• The PW End Node Quality Test Sub-package can be used for testing the quality of the connec-

tivity between the end nodes of a pseudowire.

• PW End Node Throughput Test is an intrusive test for determining the maximum band-

width available between the end nodes of a pseudowire without having the traf fic discarded.This test should be used with care as it will affect live traf fic in the network and is usu-

ally only used in the initial deployment phases of the network. This test is supported in the

8600 node hardware and therefore throughput between two nodes can be tested up to the

line-speed of the interfaces in the node. Packet distribution, send interval and QoS distribu-

tion can conveniently be selected using predefined templates. It is also possible for the user

to define his own distribution values.

• PW End Node One-way Delay Variation Test can be used for testing the one-way delay

variation between the end nodes of a pseudowire. This test is supported in the 8600 node

hardware and therefore micro-second accuracy can be obtained for the test results.

• PW End Node One-way Packet Loss Test can be used fortesting the packet loss for packets

sent between the end nodes of a pseudowire. Packet distribution, send interval and QoS

distribution can be defined using predefined templates, or the user can define them manually.


125




Fig. 80 PW End Node One-way Delay Variation Test

TE Tunnel Test Package contains functionality for testing TE tunnel communication between the

tunnel ends in the network. These tests can be run only unidirectionally.


126




• TE Tunnel Connectivity Test can test the connectivity inband and end-to-end for an RSVP TE

tunnel using the LSP ping. This is a powerful test for verifying the consistency between the

control plane and forwarding plane for the tested tunnel. It is also possible to select an ICMP

ping based test between the end nodes of the tunnel e.g. when troubleshooting situations where

an LSP ping based test gives a connectivity error as a result.

• TE Tunnel Traceroute Test traces the path inband and end-to-end for an RSVP TE tunnel using

the LSP traceroute. This is a powerful test for verifying the consistency between the control

plane and forwarding plane for the tested tunnel. It is also possible to select an ICMP traceroute

based test between the end nodes of the tunnel e.g. when troubleshooting situations where an

LSP traceroute based test fails to trace the complete path.

• The TE Tunnel Quality Test Sub-package can be used for testing the quality between the end

nodes of a tunnel.

• TE Tunnel Throughput Test is an intrusive test for determining the maximum bandwidth

available between the end nodes of a tunnel without having the traf fic discarded. This test

should be used with care as it will affect live traf fic in the network and is usually only used

in the initial deployment phases of the network. This test is supported in the 8600 nodehardware and therefore throughput between two nodes can be tested up to the line-speed

of the interfaces in the node. Packet distribution, send interval and QoS distribution can

conveniently be selected using predefined templates. It is also possible for the user to define

his own distribution values.

• TE Tunnel One-way Delay Variation Test can be used for testing the one-way delay vari-

ation between the end nodes of a tunnel. This test is supported in the 8600 node hardware

and therefore micro-second accuracy can be obtained for the test results.

• TE Tunnel One-way Packet Loss Test can be used for testing the packet loss for packets

sent between the end nodes of a tunnel. Packet distribution, send interval and QoS distribu-

tion can be defined using predefined templates, or the user can define them manually.

Fig. 81 TE Tunnel Throughput Test

VLAN Test Package contains functionality for testing VLAN VPN services. These tests can

be run unidirectionally or bidirectionally. The maintenance domain, maintenance association,

maintenance endpoints and maintenance intermediate points associated with the service need to

be configured according to 802.1ag.


127




• VLAN Connectivity Test checks the connectivity between the service endpoints using an

802.1ag based loopback message between the source and destination MEPs associated with the

service.

• VLAN Traceroute Test traces the path checks between the service endpoints using an 802.1ag based link trace message between the source and destination MEPs associated with the service.

Intermediate MIPs found in the path are reported. This can be useful when investigating connec-

tivity problems in a network for the VLAN VPN service.

• The VLAN Quality Test Sub-package can be used for testing the quality between service end-

points located at 7090-05 CE, 7090-07 CE, 7090-15 CEM or 7090-25 CE (only the 82.7325A

switch module) nodes of a VLAN VPN service according to RFC2544. The endpoints to be

tested need to have MEPs. The test will be executed using multiple frame sizes, starting the test

from the smallest frame size towards the largest testable frame size in each iteration. Results will

be given separately for each frame size used in the test. The frame sizes to be used in the test can

be selected by the user, or the default frame sizes specified in RFC2544 can be used.

These tests are intrusive and can therefore be service-affecting when using high bit rates inthe tests. Thus, pay special attention when selecting the bit rate to be used in the test.

• The VLAN Throughput Test is used for determining for each testable frame size if the

frames using the given bit rate can be passed between the VLAN endpoints without losing

frames. When there are lost frames using the given bit rate, the test algorithm in the node

will iterate in order to find a bit rate at which frames are not lost in the test.

• The VLAN Round-trip Delay Test is for determining the latency for each testable frame

size using the given bit rate when frames can be passed between the VLAN endpoints with-

out losing frames. When there are lost frames using the given bit rate, the test algorithm in

the node will iterate in order to find a bit rate at which frames are not lost and measure the

latency of such frames.

• The VLAN Frame Loss Test is used for determining for each testable frame size the frame

loss rate using the given bit rate between the VLAN endpoints. If frames are lost using the

given bit rate, the frame loss rate will be measured using 90%, 80%, … of the given bit rate

until no frames are lost.

• The VLAN Burst Test is used for determining the maximum number of frames that can be

sent in a burst so that received frames are not lost using the given bit rate for frames sent

between the VLAN endpoints.

The following figures show examples of the windows in the VLAN Quality Test Sub-package.


128




Fig. 82 VLAN Throughput Test Using Result List

Fig. 83 VLAN Throughput Test Using Result Chart

Result Chart can also display the bar for the theoretical speed for each frame size, but that isderived from the egress port in the source node and has minor relevance if the bit rate used inthe test is much smaller than the port rate is.


129




Fig. 84 VLAN Round-trip Delay Test Using Result List

Fig. 85 VLAN Round-trip Delay Test Using Result Chart

The above Result Chart will show the minimum and maximum bars for the round-trip delay for each

frame size used in the test.


130




Fig. 86 VLAN Packet Loss Test Using Result List

Fig. 87 VLAN Frame Burst Test Using Result List


131




Fig. 88 VLAN Frame Burst Test Using Result Chart

VPLS Test Package contains functionality for testing VPLS VPN services. These tests can be run

unidirectionally or bidirectionally. The maintenance domain, maintenance association, maintenance

endpoints and maintenance intermediate points associated with the service need to be configured

according to 802.1ag.

• VPLS Connectivity Test checks the connectivity between the service endpoints using an 802.1ag

based loopback message between the source and destination MEPs associated with the service.

• VPLS Traceroute Test traces the path checks between the service endpoints using an 802.1ag

based link trace message between the source and destination MEPs associated with the service.

Intermediate MIPs found in the path are reported. This can be useful when investigating connec-tivity problems in a network for the VPLS service.

Ethernet OAM Test Package contains functionality for testing the connectivity and delay between

MEPs for a selected maintenance domain and maintenance association. These tests can be run

unidirectionally or bidirectionally. The MEPs to be tested can e.g. belong to a single service such as

an Ethernet PW, VLAN VPN or VPLS VPN, or to multiple services of the previously mentioned

types stitched together. The maintenance domain, maintenance association, maintenance endpoints

and maintenance intermediate points associated with the service need to be configured according to

802.1ag/Y.1731.

• Ethernet OAM Connectivity Test checks the connectivity between the MEPs selected for the

test using an 802.1ag based loopback message between the source and destination MEPs.

• Ethernet OAM Traceroute Test traces the path between the MEPs selected for the test using an

802.1ag based link trace message between the source and destination MEPs. Intermediate MIPs

found in the path are reported. This can be useful when investigating connectivity problems in a

network for a service(s) associated with the MEPs.

• Ethernet OAM Delay Measurement Test measures the delay between the MEPs selected for

the test using Y.1731 based messages between the source and destination MEPs. This can be

useful when investigating service quality problems in a network for a service(s) associated with

the MEPs.


132




Background Test Manager

The Background Test Manager contains functionality for defining and scheduling tests that areexecuted in the background. If the tests are run by the 8600 nodes, these are basically performance

tests, that is, they produce performance data to be used by, e.g., Integrated Performance Management

tools. Note that not all tests can be scheduled to run in the background. The test can be scheduled to

run once or on a minute, hourly, daily, weekly or yearly basis in a specified time interval.

The basic operations for managing background tests are the following:

• Adding a new test schedule

• Viewing the status of background tests

• Suspending a running background test

• Resuming a suspended background test• Deleting an existing background test schedule

• Modifying an existing background test configuration

• Viewing the result of the background tests

The following figure shows an example of the GUI of the Background Test Manager window.

Fig. 89 Background Test Manager Window

The following figure shows an example of the result window of a TE Tunnel ManagementConnectivity Test run by the Background Test Manager.


133




Fig. 90 Test Result Details Window

SLA Monitoring

The Background Test Manager can be used for SLA monitoring of services configured on the

8600 nodes. The node, IP VPN and PW throughput, one-way delay variation, round-trip delayand packet loss tests can be scheduled in the background and a threshold can be assigned to the

tests. If the threshold is exceeded, the background test manager will insert a fault in the database

notifying the user of an SLA violation.

3.4.3 Circuit Loop Test

The Circuit Loop Test is a testing tool for detecting and localizing problems in those circuits created

by 8000 Intelligent Network Manager. It can help to qualify the circuits or transmission media by

giving detailed performance results. Several features allow the user to test different sections of a

circuit. Different test patterns and loops can be used. The control signal operation can be tested

separately, and a break in a circuit can be easily detected.

The Circuit Loop Test facility supports three categories of circuits: PDH 1/0 and SDH paths and

ATM Virtual Paths. For the PDH 1/0 circuits the Circuit Loop Test window allows activating

test pattern generation and reception in order to retrieve detailed results including error rate, failure

and performance statistics. For the ATM virtual paths there are two tests: loop back test for data

transmission testing and continuity check test for permanent continuity monitoring. With the

Circuit Loop Test window it is also possible to define ATM virtual path segment endpoints required

for loop back and continuity check. The SDH paths have their own test window, which allows

access to several 8000 Intelligent Network Manager tools and can also activate a cross-connection

loop on the path.


134




General Test Properties for PDH 1/0 Circuits

For the PDH 1/0 circuits, the Circuit Loop Test tool supports testing of point-to-point, compressedpoint-to-point, swap point-to-point, broadcast and point-to-multipoint circuit types. All types,

except for compressed point-to-point circuits, can be tested at the endpoint level. Compressed

point-to-point circuits must be tested at the subcircuit level because they are not bit-transparent

from end to end.

All different types of point-to-point circuits can be tested either uni-directionally or bi-directionally.

A test is defined by selecting a subset of available resources between the endpoints. If a swap

point-to-point circuit is tested, one of the possible endpoint pairs must be chosen first.

When testing a broadcast circuit, the master endpoint and at least one of the slave endpoints must

be selected. It is normally possible to select any number - from one up to all - slave endpoints for

testing. However, the lack of common test resources can sometimes be a restriction.

Point-to-multipoint circuits are tested uni-directionally in the same way as the broadcast circuits.

The point-to-multipoint circuits can also be tested bi-directionally. In that case the master endpoint

and only one of the slave endpoints can be selected for testing.

A so-called intermediate node can be selected along the route of a circuit. The intermediate node

provides additional resources for testing.

It is also possible to test the predefined backup routes of point-to-point circuits. At the beginning,

the primary route is disconnected and the predefined backup route is connected. After that the

circuit can be tested in a normal way.

Test endpoints are additional interfaces that can be used for monitoring the data flow through the

actual circuit. This is a useful way to perform long-term monitoring tests without disturbing thecircuit. This feature is available for point-to-point circuits only.

Available Resources

There are three different resource types for testing purposes. Test resources are objects that can

transmit and receive data and control signals. Loops are used for looping the received signal

back to the original source. Redirections are used for directing the signal to test an endpoint for

monitoring purposes.


135




• Test resources are used to generate appropriate test data patterns or control signals. The circuit-

specific test resource is, for example, in an interface that is reserved by the circuit. The node

common test resource can also be used in access nodes or intermediate nodes. If the intermediate

node is a branch node in a point-to-multipoint circuit, there are two additional test resources in

the PMP Server units (VCM or GCH-A). The node common test resource is located in a controlunit (e.g. SCU and SCU-H). In addition, there is a test resource in every VCM and GCH-A

interface. There are test resources also in NTUs (for further information, refer to the appropriate

NTU manual or booklet).

• Loops are used for looping the incoming signal back to the original source. There are three

different places where a loop can be activated or created:

X-Connection The signal is looped back using a cross-connection

command to the given port of an endpoint interface

or trunk.

Loop in Interface A loop that is activated by a management command

in the given endpoint interface. This kind of aloop can be activated in the CAE, CCO, CCS,

GCH-A, GMH, IUM, ISD-LT, ISD-NT and VCM

interfaces.

Loop in NTU A loop that is activated by a management command

in the given Network Terminating Unit (NTU).

There are NTU loops in all NTU types.

• Redirections are located in a special kind of intermediate nodes called Test Branch Nodes. The

test branch node is the place where the incoming signal can be directed to test an endpoint. There

are two types of redirections. Listening of an endpoint means that you direct the signal to the

test endpoint by making a uni-directional connection from the endpoint to the test endpoint. The

normal operation of a circuit is not disturbed in any way. The other way is to replace one of theendpoints by a test endpoint. The original connection is removed and a bi-directional connection

is made from the other endpoint to the test endpoint. It is possible to create only one redirection

to one endpoint. Redirections to both endpoints can be activated at the same time.

Test Types

Testing of circuits can be separated into two categories. An internal test is performed by using one

or more test resources for transmit/receive purposes. In an external test neither a test pattern nor a

control signal is generated by Circuit Loop Test. External equipment is used for performing the test.

• Internal Test includes two different sets of tests. The first one is often referred to as a Control

test which is performed on the circuit control signals (105-109, 108-107, 105-106) by driving the

circuitry directly. The second one is simply called a Test. This means that the data path is tested

using different test patterns.

• External Test can be activated by making a loop-back or by using redirections. The external

equipment can, for example, transmit or receive data like a test resource. Monitoring the incom-

ing or passing signal is another example.

Both asynchronous and synchronous circuits can be tested.


136




Test Results

The Circuit Loop Test facilities allow the user to activate test pattern generation and reception of PDH 1/0 circuits in order to retrieve detailed results, including error rate, failure and performance

statistics. In the case of ATM virtual paths, the test results consist of the count of test cells looped

back or the presence of the loss of continuity fault in Fault Management, depending on the ATM test

type. Circuit Loop Test collects no results for SDH cross-connection loops. The current test status is

displayed while a test is active on a workstation. In addition, all types of active tests (PDH 1/0,

ATM, and SDH) can be saved on the test catalogue in the database. The workstation can even be

switched off while the testing remains active in the 8100 system network. In these cases the tests

are called background tests. The background tests can be accessed again or terminated at any time

by starting Circuit Loop Test for them again.

The test results are presented as bit error and G.821 counters, signal interruption counters, cell

counters or faults, depending on the test. When external test equipment is used, no test results are

available.

Characteristics of SDH Path Loop Test

The SDH Testing tool has two modes, intrusive and non-intrusive. In the non-intrusive mode one

can view faults, performance and trail trace from accessible VC objects. The intrusive mode adds a

capability to set cross-connection loops; add Supervisory Unequipped VC objects and access the

tool for SNC switch manipulation.

The window shows the whole SDH circuit at the same time. All nodes, trunks, internal connections

and VC objects are drawn. Endpoint information is shown for circuit endpoints. Accessible VCobjects related to the circuit are drawn as gray triangles. Typically, there are terminating VC objects

at circuit endpoints and possibly monitoring VC objects at SNC/N branch points.

Non-Intrusive Testing

Non-intrusive testing does not disturb circuit traf fic, unless one changes trail trace. The tools include:

• Trail Trace tool starts the Trail Trace Tool. It can be started for a single VC object or a concate-

nated group of VC objects.

• Performance tool start the Performance Tool. It can be started for a VC object. In the case of a

concatenated circuit, the VC object is selected from the Concatenated Components dialog.

• Faults tool starts the Fault View for the selected VC object. Use the Concatenated Components

dialog to select the component from a concatenated group.

• Active monitoring tool enables periodic polling of a VC object. The object is drawn in red if

there are faults or in dark blue if the performance has degraded. Black means that there has been

a communication error when the object was polled, and white means that polling has not been

performed for the object. A normal, well functioning object is shown in light blue. Only one

component of a group can be polled. The component can be selected from the concatenation

group.

• Node Manager tool starts the Node Manager tool for the selected node.

To use a tool, select it from the toolbox, then click on the VC object you wish to access.


137




The Concatenated Components dialog can be used to specify a component of a concatenated

group. Some of the tools require the selection of a single component. Cross-connection loops and

SNC switch always affect the whole group. Trail Trace can affect the whole group or a single

component. Other tools affect only a single component.

Intrusive Testing

Loops and SNC switch operations can disturb traf fic. If the circuit is a virtual trunk, a warning is

given. To appreciate the level of danger involved, consider a virtual trunk which carries hundreds of

circuits. If the virtual trunk is cut by a loop, all circuits will also be cut. If automatic recovery is

active, all of those PDH 1/0 circuits would be candidates for recovery, and that would severely tax

the servers and control channels of the network.

Intrusive testing differs from non-intrusive testing by allowing more tools and options. When the

selection tool is active and there is no active loop in the circuit, all locations where a loop can be

placed are shown by a green rectangle with an arrow inside. An active loop is shown in a yellow

rectangle, and all other possible loop locations are hidden while a loop is active. To activate theselected loop, click the Activate button. To reset an active loop, click the Reset button. To clear the

selection, click the Clear button. When a loop is activated, no faults are masked in the network.

If one exits from the tool while the loop is active, the loop will remain active in the network. The

test can be opened again for the same circuit, and the loop will be shown as active. It can be reset

normally then.

There are also two more tools in the toolbox than there was in the non-intrusive case, i.e. SNC

switch and Supervisory Unequipped:

• SNC Switch tool starts the SNC Switch Control Tool for the SNC branches. The tool is especially

useful in combination with the loop tool, as it allows the SNC/N protection to be bypassed so thatthe looped signal can be forced at the desired position. Normally a working SNC/N protection

would recover from the loop by using the non-looped portion of the circuit, if possible.

• Supervisory Unequipped. Node Manager can be used to create special VC objects called Su-

pervisory VC objects, which have a property of filling the payload with zeros. The signal sent

from Supervisory VC objects can be equipped with a trail trace, which distinguishes the signal

sent from the unequipped fault. The trail trace must be set separately.

This tool can be used to determine the points in the circuit where the Supervisory VC objects

will be connected. The actual connections are made when the test is activated, and removed

when the user resets the test, i.e. the connections are handled in the same manner as the

cross-connection loops.

There are no separate test results beyond those which can be seen from the different tools. The

test has no set duration (cross-connection loops have no time out possibility, and there is no fault

masking involved), but the database test catalog has a nominal 24-hour duration for the test. The

Test Reminder is not used by the SDH test tool.

The combination of trail trace, loop, supervisory unequipped testing and SNC switch can be used to

verify that the SNC protection works, signal reaches all parts of the circuit, and the correct faults are

generated at the endpoints under different conditions.

General Test Properties for ATM Virtual Paths

The Circuit Loop Test tool supports testing of point-to-point ATM virtual paths. As they can be

seen as circuits, the term ‘circuit’ is used of them, too.


138




The testing of ATM virtual paths is quite different from the testing of PDH circuits. All virtual path

tests are non-intrusive, since the normal transmission can continue in spite of the test activities.

The tests can have a slight effect on the overall performance though. The tests are based on the

ATM Operations and Maintenance (OAM) cells.

For the ATM Virtual Paths there are two tests: loop back test for data transmission testing and

continuity check test for permanent continuity monitoring. With the Circuit Loop Test window it

is also possible to define ATM virtual path segment endpoints.

The continuity check is a so-called permanent test, which means that it has no predefined test

duration. The test remains active until it is deactivated.

Testing Level

An ATM virtual path can be seen in different ways from the management point of view. You can

consider it as one entity from one virtual path connection endpoint to the other. In that case an

end-to-end level is in question. On the other hand, a virtual path connection can be divided intosmaller, independently managed portions, called segments. When a test is run in such a portion, it is

run at the segment level. Segment endpoints can be defined with the Circuit Loop Test facility.

The loop back test can be run either at the segment or end-to-end level. The end-to-end level

can be used if the other end of the test path is in external equipment. The continuity check testis always run at the segment level.

Available Resources

The testing resources for the ATM virtual path tests are so-called Link Termination Points (LTP).

There are two link termination points in one ATM access unit, one in the access interface side and

the other in the trunk interface side. The link termination points can also be defined as segmentendpoints.

For an ATM virtual path test, one link termination point is defined as a source and the other as a

sink. A source inserts test cells into the data stream. A sink receives those cells. Sometimes, as in a

loop back test, the source and the sink are the same link termination points.

A loop is a link termination point on the virtual path connection, where the test cells are looped

back to the original source. With a loop back test, this looping point can be a segment endpoint

or a virtual path connection endpoint. In the first case the testing is done at the segment level

and in the latter case the level is end-to-end.

Test Results

Test result for ATM virtual paths is the number of cells sent and received in the loop back test. For

continuity check, the results can be viewed in Fault Management as VPL (Virtual Path Link) down

alarm if LOC (loss of continuity) is detected.

3.5 Service Fault Monitoring Package

The Service Fault Monitoring Package allows the operator to monitor both TDM circuits and MPLS based services in the network. The operator may react to fault situations in the network based on the

priority of the services being affected. It also includes a service management tool that can be used to

bundle a number of TDM circuits, MPLS VPNs and VLAN VPNs into a logically managed service.


139




3.5.1 Service Fault Monitoring Windows

There are two Service Fault Monitoring related windows: Service Fault Monitoring (SFM)window and Service Fault window.

Service Fault Monitoring enables the real time supervision of all services, i.e. pseudowires, TDM

circuits, VLAN VPNs and IP VPNs that are assigned to a certain Service Category. A Service

Category is a collection of preselected services. It is possible to configure Service Fault Monitoring

so that only the selected service categories are displayed. In this mode, symbols are displayed in the

order they were selected. In addition to the predefined categories, an operator can select dynamically

Customers to be taken under monitoring. The fault status of categories and customers is displayed

in the Service Fault Monitoring window. The All Faulty Services symbol can be added to the

lower right-hand corner of the window. This symbol represents the total fault status of all services.

By default, the selected service categories and customers are saved on the configuration file and

thus remembered. This means that next time the previous view is automatically restored. One

workstation or Fault Server can be selected to save and update all faulty services in the database.

All faulty services and their fault status details of the corresponding category or customer are listed

in the Service Fault window. The appearance of Category and Customer symbols follow the same

characteristics as other objects in the FMS windows (color coding and blinking status directly

reflects the fault state of the object). From the Service Fault window an operator can open a Service

Fault Report window concerning a specific service and its faults.

3.5.2 Service Management

The Service Management tool allows the operator to manage a number of TDM circuits, VLAN

VPNs and MPLS VPNs as one logical service. The connections can be grouped together to form aservice object which can then be monitored as one entity in Service Fault Monitoring. It is also

possible to associate trunks and nodes with a service object.

In the Service Management window the operator can see all the components associated with the

service and launch associated tools with each of the components such as the Router, Circuit Loop

Test, VPN Provisioning, Packet Loop Test, etc. If fault monitoring has been enabled, the service is

monitored as one entity in Service Fault Monitoring and the user may also see the fault status of the

service in the Service Management window.

There is no restriction on how you group the connection in the network into services. It is also

possible to associate the same connection with several services. There are several options to group

the connections. The operator may group the circuits and VPNs such that all connections associated

with a certain base station are grouped together. Another option is to group all leased line trunkstogether and monitor them as one entity. If the operator uses some Ethernet switches managed by

the 8000 Intelligent Network Manager to form a management DCN, then the Ethernet switches

can be grouped to form one DCN service etc.


140




Fig. 91 Service Management Window

3.6 Performance Management Package

3.6.1 Overview

The Performance Management Package monitors and reports the performance data for the 8000

managed network.

Support for the 6300 network elements:

• Packet counter statistics

• TDM ETSI G.826 statistics



• QoS statistics

• Bandwidth utilization


141




• Y.1731 performance statistics

• MEP session available time statistics



• Optical/OTN statistics

• ODU TCM statistics

• TDM ETSI/ANSI statistics




• TDM ETSI G.826 statisticsSupport for the 8600 network elements:

• Packet and cell counter statistics

• QoS statistics

• TDM ETSI/ANSI statistics


• Element CPU and NPU load statistics

• MEP session available time statistics



• QoS statistics

• TDM ANSI statistics

• Element CPU load statistics

• Y.1731 DM real-time performance statistics

Support for the mTera UTP network elements:

• POS packet counter statistics

• Optical/OTN statistics• TDM ETSI/ANSI statistics

The background collection continuously collects data from the interfaces in the network and stores

the history data on the database. The history data can then be viewed and analyzed later. In

the real-time performance monitoring, the counters are read from the network elements with an

interval of 5 to 600 seconds and drawn in a graph. This is intended for status verification and

trouble-shooting purposes.

For more information on the supported counters and supported history periods related to 6300, 7090,

7100, 8600, 8800 and mTera UTP nodes, refer to 8000 Intelligent Network Manager Online Help.


142




3.6.2 Performance Statistics

The different types of supported performance statistics are listed below. For more information onthe available counters, refer to 8000 Intelligent Network Manager Online Help.

Data Granularity

The granularity of the collected data can be defined in more detail for the performance data types

supported by several interface types.

E.g. instead of collecting all PWE3 circuit statistics you can select to collect and store only Ethernet

PWE statistics, or instead of collecting all MIB2 type packet statistics only LAG can be selected.

This helps in all performance collection areas.

• There is less load on network elements (processing PM data queries).

• The DCN bandwidth usage (PM data transfer) is smaller.

• There is less load on Communication Servers (PM data processing).

• The size of the PM database is smaller.

• PM reports can be created faster.

The Polling Policy dialog can be used for configuring the granularity of the collected data. This is

currently supported for the 7100, 8600 and 8800 network elements.

6300 Network Elements

The following performance statistics are supported for 6300 network elements.

• G.821/G.826 TDM (ETSI) statistics for trunks, circuits and end interfaces.

• 24-hour history statistics

• 15-minute history statistics

• Packet statistics for Ethernet and VLAN interfaces as well as for ETEX and EMAP units.


• real-time statistics




143




• Packet statistics for MIB2 (In, Out).

• configurable interval history statistics for 7090-05 CE, 7090-07 CE, 7090-15 CEM, 7090-25

CE, 7090-40 CEM and 7090-45 CE

• real-time statistics for 7090-05 CE, 7090-07 CE, 7090-15 CEM, 7090-25 CE and 7090-45

CE

• Packet statistics for RMON (In) for 7090-25 CE, 7090-40 CEM and 7090-45 CE.


• Bandwidth Utilization statistics for 7090-25 CE and 7090-45 CE.


• QoS Drop Queue (scheduler) statistics for the Ethernet interfaces in 7090-25 CE, 7090-40 CEM

and 7090-45 CE.


• QoS Policer statistics for Ethernet for 7090-25 CE, 7090-40 CEM and 7090-45 CE.


• Y.1731 basic statistics for Frame Loss, Frame Delay and Frame Delay Variation is only supported

by 7090-05 CE, 7090-07 CE and 7090-15 CEM.



• Y.1731 bin histogram statistics for Frame Loss, Frame Delay and Frame Delay Variation is sup-

ported by 7090-05 CE, 7090-07 CE, 7090-15 CEM, 7090-25 CE, 7090-40 CEM and 7090-45

CE.



• An approximate available time for an end-to-end Ethernet OAM MEP connection calculated by

8000 Intelligent Network Manager based on the CCM session fault data.

• configurable interval statistics via Scheduling Center



• G.826 (ETSI) SDH TDM statistics for RS/MS/VC-4 path.



• GR-253/GR-820 (ANSI) Sonet TDM statistics for Section/Line/STSn path.



• ODU TCM statistics for ODUkT facilities.




144




• Optical/OTN statistics for optical trunks, circuits and end interfaces.



• Packet statistics for RMON and POS.

• 15-minute history statistics.

• Y.1731 bin histogram statistics for Frame Loss, Frame Delay and Frame Delay Variation are

supported by the ESM units with FP7.1 or higher.





• G.821/G.826 TDM (ETSI) statistics for trunks, circuits and end interfaces.



• Node 1/0 Cross-Connection statistics for 1/0 elements.

• 24-hour statistics

• Node 1/0 X-bus allocation statistics for 1/0 elements.

• The Circuit Recovery Down-Time Report contains the down time caused by circuit recovery

operations. A reduced set of error counters (TT, AT, UAT) is reported.

• The NTU line breaks count is reported for circuits and tells how many seconds the NTU sub-

scriber line has been unavailable.

• Trunk capacity 24-hour history data for primary trunks contains trunk used capacity and trunk

total capacity. Search criteria have been implemented to help find the most interesting or heavily

loaded trunks in the 8100 system network.

• Control channel path 24-hour history data for control channel paths and the alternative paths

are reported at the node level. For example, the statistics of a path ending at a 8170 Cluster Node

are composed of sums of subrack statistics. Errors and time-outs found during fixed one-day

periods are reported. The user may search for poorly functioning control channels on the basis

of errors and time-out criteria. The control paths of different areas may be reported separately.

• Trunk 24-hour G.82x history data for primary trunks contains G.82x performance statistics

for TDM trunks. The data is calculated once a day by SLA Server service in CommunicationServer and stored in the database. The data may then be exported to third party tools through the

northbound interface.

• Circuit 24-hour G.82x history data for circuits contains G.82x performance statistics for TDM

circuits. The data is calculated once a day by SLA Server service in Communication Server and

stored in the database. The data may then be exported to third party tools through the northbound

interface.




145




• Abis group statistics.



• ATM statistics for ATM port, IMA group, VP and VC.

• configurable interval history statistics


• Element statistics for unit CPU load, module NPU core load and memory usage.

• 1-minute history statistics for CPU

• 15-minute history statistics for CPU and NPU

• Frame Relay statistics.



• G.826 (ETSI) SDH TDM statistics for RS/MS/VC-4 path/VC-12 path/E1 line/P12s path.



• GR-253/GR-820 (ANSI) Sonet TDM statistics for Section/Line/STS path/VT1.5 path/DS1

line/DS1 path.



• MPLS TE tunnel statistics.



• Packet statistics for all MIB2 type packet interfaces.



• PWE Circuit statistics for pseudowires, including the pseudowire redundancy configuration.



• real-time statistics• PWE TDM statistics for SAToP and CESoPSN pseudowires, including the pseudowire redun-

dancy configuration.





146




• QoS Drop Queue DiffServ statistics for Ethernet, VLAN, HDLC, PPP and ML-PPP interfaces.

Dropped and passed octets/packets based on a threshold value are supported for 8602 Smart

Router, 8605 Smart Router, 8607 Smart Router, 8609 Smart Router, 8611 Smart Router and

8615 Smart Router. Dropped octets/packets based on threshold value and also on WRED algo-

rithm are supported for 8620 Smart Router, 8630 Smart Router and 8660 Smart Router.



• QoS Policer DiffServ statistics for L1 and L3.



• QoS Traf fic DiffServ statistics for VLAN interfaces.


• real-time statistics• SHDSL segment endpoint statistics for ETSI and ANSI.



• Y.1731 basic statistics for Frame Loss, Frame Delay and Frame Delay Variation with calculated

percentile values.




• An approximate available time for an end-to-end Ethernet OAM MEP connection calculated by8000 Intelligent Network Manager based on the CCM session fault data.

• configurable interval statistics via Scheduling Center



• Element statistics for unit CPU load and memory usage for Line, Route and Management CPUs.



• GR-253/GR-820 (ANSI) Sonet TDM statistics for Section/Line/STS path/DS1 line/DS1

path/DS3 line/DS3 path.


• MPLS TE tunnel statistics.



• Packet statistics for ports, IP interfaces, LAG members and LAG interfaces.




147




• PWE Circuit statistics for pseudowires, including the pseudowire redundancy configuration.



• QoS Policer statistics for packet interfaces and pseudowires.


• QoS Drop Queue statistics for packet interfaces.


• Y.1731 basic statistics for Frame Delay and Frame Delay Variation statistics.


mTera UTP Network Elements

The following performance statistics are supported for mTera UTP network elements.

• G.826 (ETSI) SDH TDM statistics for RS/MS/VC-4 path.



• GR-253/GR-820 (ANSI) Sonet TDM statistics for Section/Line/STSn path.



• Optical/OTN statistics for optical trunks, circuits and end interfaces.



• Packet statistics for POS.

• 15-minute history statistics.

Polling Statistics

You can enable the performance data collection system to store the history of its performance and

successful/failed elements. This data is collected per Communication Server and performance

collection type. The failed elements will also store the related cause for the collection failure.

Server Monitoring Statistics

You can view the server monitoring history statistics with the Performance Management graph

GUI. The data can be viewed per monitoring task and 8000 Intelligent Network Manager

Management/Communication Server.

The Server Monitoring Configuration Wizard can be used for defining which performanceindicators are monitored.


148




3.6.3 History Data Collection and Ageing

Communication Servers take care of the data collection from 6300, 7090, 7100, 8600, 8800 and

mTera UTP network elements. The DXX Servers take care of the data collection from the 8100

network elements. The data collection runs continuously without operator intervention after the

server programs have been started.

Statistics are polled from the network elements continuously in the background according to a

polling policy configured for the Communication Servers and stored on the 8000 Intelligent Network

Manager database. The polling policy controls how the data is polled from the network element.

The recommended polling cycles depend on the amount of network elements, their furnishing,

network configuration and the performance of the Database Server.

Since the amount of performance history data can become huge in large networks, the old

performance data must be continuously removed from the database. The user may defi

ne for howlong the performance data should be stored on the database by configuring the ageing settings.

The Communication and DXX Servers will then automatically remove the old performance data

according to the ageing settings. The Performance Configuration tool can be used for configuring

the ageing settings, and it also shows the current database size of performance history tables.

Trend Calculation

Trend calculation is performed daily by Communication Server. The user needs to enable thetrend calculation, and configure the time of calculation. The trend calculation uses daily interval

history data as the input for the calculation. The daily interval history data contains history records

collected according to a polling policy (performance poll period) that has been configured by the

user in Network Editor. The results of the trend data calculation for each period are stored on the

8000 Intelligent Network Manager database, and the Performance Management Overview tool

can be used for reporting.

Raw Performance Data

Raw performance data, i.e. data that is stored and presented exactly as it is available on the network

element, is supported for the 7090, 7100, 8800 and mTera UTP network elements.

The data collection is enabled in the polling policy for the adapter. This data can be viewed using

the Node Manager tool. Data ageing is configured in the Performance Configuration tool.

3.6.4 Performance Reporting

Performance reports are typically available both in tabular and graphical forms. The user can

configure the reports in different ways. It is, for example, possible to report the totals of G.821/G.826

performance counters during different time periods in calendar time (weeks, months). It is also

possible to select multiple circuits and trunks to have network level down-time reports. Printouts,

however, are only in tabular form.


149




Packet Counter Performance Reporting

A graphical tool is available in the 8000 Intelligent Network Manager for viewing packet and cell based performance statistics in the 6300, 7090, 7100, 8600 and 8800 network elements. The tool

can be used both for history performance reporting as well as real-time performance reporting

(when applicable for the interface).

Performance interval history can be viewed in the graphical Performance Management tool. The

user may define the reporting period and the performance indicators to be displayed in the window.

There is a number of performance indicators to select from including: utilization, sent/received

octets/packets, errored packets, discarded packets for the interface or trunk interface.

The interval history data can then be exported to third party tools for further analysis through the

northbound interface of 8000 Intelligent Network Manager.

Web Reporter can be used to report performance interval history data.

Real-time performance monitoring polls the data from the network elements in real-time

according to a configured time interval, which can vary from a few seconds to several minutes.

The polled data is not stored on the database, only showed in the graphical window, which is

updated after each data poll. The real-time performance monitoring tool is useful in troubleshooting

situations in which a real-time picture of the current interface or trunk utilization is required to be

checked, e.g., how many packets are transferred, how many packets have errors or how many

packets are dropped. If the data needs to be analyzed with an external tool, it can also be exported to

a text file. With the data logging feature, it is possible to log polled counter values into a file in the

8000 Intelligent Network Manager workstation.

Exporting of the performance data showed in the Performance Monitoring tool, both in history

and real-time modes, can be done to a PDF document, clipboard graphics, graphics file or text file.The data is stored in the file in comma-separated value (CSV) format. The data in CSV format can

also be imported from a text file and displayed in the Performance Monitoring tool.

Performance Configuration is used for configuring the automatic removal of obsolete history data

from the database as well as for enabling the utilization fault monitoring and trend calculation.

3.6.5 Interface Utilization Threshold Monitoring

The Performance Management Package contains a very useful feature to monitor the utilization of

the interfaces (or an associated trunk interface) supported by 8000 Performance Management. The

collected packet performance data is analyzed and the utilization of the interface is calculated. If theutilization exceeds a user-defined threshold, then a fault is created and the user is alerted through the

fault monitoring tools. This allows the user to monitor the utilization of the network and to add

more capacity to the network before the congestion situations in the network become critical.

This feature is supported for the data from the 6300 and 8600 network elements.


150




3.6.6 Trend Analysis

The performance trend analysis looks at the utilization history data of performance statistics andcalculates trends based on this data. This feature helps the user to plan when a particular interface or

link is becoming full. The trend data calculation uses the linear least squares method for fitting the

measurement data into a straight line. Performance Management extrapolates the straight line to the

future to find out when the utilization exceeds the user-configured threshold. The trend data can be

calculated over different periods, e.g. one day, one week, four weeks or a custom period.

The Performance Overview tool reports the trend data and shows the following trend and

performance data.

• Trend Delta in period [and 24h]; the utilization change during a trend calculation period [and

during a day] to find out the fastest growing interfaces.

• Congestion date In/Out; the estimated date of congestion calculated for the user-defined conges-tion threshold. The congestion threshold can be changed. Sorting by date gives a report showing

which interfaces will congest first.

• Average Utilization In and Utilization Out during a period.

• Total amount of traf fic In and Out during a period.

The utilization trend calculation is supported for interfaces having utilization In or Out supported in

the 6300, 7090, 7100, 8600, 8800 and mTera UTP network elements.


151




Fig. 92 Performance Management Overview Reporting Tool with Trend Data

3.6.7 Performance Overview Reporting Tool for 6300, 7090, 7100, 8600, 8800and mTera UTP Network Elements

The Performance Overview report is used for network level trend data analysis and reporting,

utilization reporting, and TDM and Abis group history reporting for the 6300, 8600 and 8800

network elements. Optical/OTN, TDM and port-level (Ethernet, POS) reporting is supported for the 7100 and mTera UTP network elements. Port-level (Ethernet) reporting is supported for the

7090 network elements.

The reporting application has a wizard making it easy to generate a report. Sorting and filtering is

supported, and the report can be saved to a file for further analyzing the history data. The graphical

Performance Reporting tool can be launched for more detailed reporting of performance history of an interface or specified layer.

The Performance Overview report helps to find congested interfaces or trunks by showing theutilization for all applicable interfaces. You can also look at e.g. Unavailable Seconds, Dropped

Packets and Delay counters in the corresponding report types for finding other problems in the

network.


152




TDM statistics reports are used for searching TDM interfaces having performance problems for

the 7100, 8600, 8800 and mTera UTP network elements. A TDM interface can be sorted so that

the worst interface (lowest Available Time) is on top of the list.

For more information on the trend data reporting, refer to 3.6.6 Trend Analysis.

3.7 Recovery Package

3.7.1 Recovery Management System

Recovery Management (RMS) is a centralized restoration system for the 8100 system network. It is

used for restoring user communication links if trunk or node faults occur in the network. Restoring

the user communication links can be done at the trunk level (trunk recovery) and circuit level

(circuit recovery). The RMS may keep a log of the incoming network faults and the RMS actions on

them. The operator may exclude some trunks or circuits from recovery actions or may disable trunk recovery or circuit recovery by setting RMS restrictions. The restrictions can by set for all trunks or all circuits or they can be set explicitly for some given trunk or circuit.

Trunk Recovery

Trunk recovery restores all connections in a specific trunk when there is a trunk failure. This is done

by reserving some of the trunks in the network for backup purposes.

If a trunk fault occurs in the network, RMS tries to remedy this fault by replacing the faulty trunk

with a backup trunk between the same two nodes. If such a trunk exists, the information flow

from the primary trunk will be switched to the backup trunk. This operation is called swapping.

If the primary trunk gets repaired, the unswap command switches back the information flow from

the backup trunk to the primary one.

If a backup trunk between the two nodes cannot be found, RMS tries to back up the faulty primary

trunk by a trunk route, which consists of two or more trunks between the end nodes of the primary

trunk. This means, that the information flow of the primary trunk will be redirected through other

nodes.

Since a trunk backup procedure is carried out much faster than the circuit recovery in a network,

RMS tries to restore network connections first by trunk recovery. If this fails, circuit recovery is

carried out. This behavior can be altered by the user by setting RMS restrictions.

Priority bumping at the trunk level provides low-cost recovery services. With priority bumping, the

backup trunks can be used by circuits that carry low traf fic class data. If a primary trunk fails, itis recovered by rejecting the low class traf fic of a backup trunk and no recovery action is started

for the bumped out low traf fic class circuits.

Recovery is not supported in the SDH network, but SDH trunk faults are administered by RMS

and RCPR.


153




Circuit Recovery

Circuit recovery is used to restore individual circuits in the network and allows a more granular control over the circuits that are restored in failure conditions. Thus the capacity reserved for

backup purposes in the network can be minimized. Also, if trunk recovery fails, circuit recovery

can be used to restore the circuits in the failing trunk. The circuit types supported by circuit

recovery are: PDH 1/0 point-to-point (pp), point-to-multipoint (pmp), broadcast (bc), compressed,

swap and virtual grooming circuits.

Circuit recovery is done either by explicitly defining a backup route for the circuit or by having

the RMS calculate a spontaneous backup route for the circuit.

In addition, the capacity of primary trunks is not always allocated totally to user circuits. Normally,

all primary trunks contain free timeslots that may be used for route allocation if a circuit breaks

down. The timeslot capacity of a primary trunk is divided into three capacity pools: a primary

pool, backup normal pool and backup low pool. Primary routes and predefined backup routes areallocated from the primary pool. The spontaneous route capacity allocation depends on the circuit

priority and on the allocation mechanism. Circuits have four possible priorities: undefined, high,

medium and low. The allocation mechanism can be specified by the user. A spontaneous route is not

created for the circuit whose priority is undefined.

If a trunk fault cannot be recovered either in trunk or circuit recovery, RMS waits for a while and

retries the circuit recovery for those broken circuits until a successful recovery. The delay and

behavior between the periodical retries can be configured in order to allow a scalable solution

for networks with a large amount of circuits.

Recovery Control Program

The Recovery Control Program (RCPR) serves as the user interface to RMS. Using RCPR the

system operator can control all the RMS actions performed in the 8100 system network. For

example, controlling the logging of RMS actions, controlling RMS settings, setting timeslot

allocation rules, refreshing the fault state of a trunk and so on.

Server Redundancy

Recovery Management System uses a single centralized Recovery Server that provides the recovery

functionality. However, if increased reliability is needed, it is possible to install two Recovery

Servers. In case of an unrecoverable failure of the active Recovery Server, the other (standby)

Recovery Server takes over the recovery support. This feature can also be used when updating

hardware or software components in a Recovery Server.

It is also possible to switch servers at any time. Server switching operations can be initiated from

Recovery Control Program if you have the required privileges. The Recovery Server state can also

be viewed from the Recovery Control Program.

It is also possible to have the active server poll the standby server periodically. If there is no standby

server or it is not responding, a notification message appears in the Recovery Control Program.


154




3.8 Service Viewing Package

The Service Viewing package can be used to restrict the network views of the 8000 Intelligent Network Manager tools. This makes the management of the network easier.

3.8.1 Service and Circuit Component View

It is possible to select views that are based on circuits and customers. In these three views, Circuit

Components View, Customer Components View and VLAN Components View, only those nodes,

trunks etc. that are part of a selected circuit, or belong to a given customer, or are in particular

VLAN domain are shown on screen.

Circuit Components View

Fig. 93 Circuit Components View

The Circuit Components View shows the components, i.e. nodes and trunks, which are used for aselected circuit in selected regions. Also, components of several circuits can be selected in the view.

Target circuits are defined in a dedicated dialog, depending on their attached regions and the nature

of the circuit traf fic (region-internal, region-terminating or transit traf fic).


155




Note that not all the trunks and nodes of circuits are necessarily shown in the view. The circuit

components in those regions which are not selected into the view are dropped from the display.

Using the Circuit Components View requires a license for component views. The view can be

activated/deactivated from the Backbone Overview mode or from the Regional Network View.

Customer Components View

Fig. 94 Customer Components View

The Customer Components View shows the components (nodes and trunks) which are used for

circuits of a selected customer or several customers in selected regions. In principle, this view is the

same as the Circuit Components View; instead of defining a set of circuits the operator selects a

customer whose circuits should be included. Also, the nodes which do not yet have circuits for thecustomer but which are dedicated to the customer, are included in the view.

Using the Customer Components View requires a license for component views. The view can be

activated/deactivated from the Backbone Overview mode or from the Regional Network View.


156




VLAN Components View

Fig. 95 VLAN Components View

The VLAN Components View shows the components (nodes, NTUs and trunks) which are used for

the selected VLAN domains.

Using the VLAN Components View requires a license for component views. The view can be

activated/deactivated from the All Network mode or from the Regional Network view.

3.9 Planning Package

The Planning Package is supported for the 6300 and 8100 network elements only. It contains two

tools: Fault Simulator and Network Capacity Calculator for planning purposes. In addition, the

user may also plan the network in a simulation database with the normal 8000 Intelligent Network

Manager tools without having the actual hardware in place.


157




3.9.1 Fault Simulator

If a fault occurs in the 8100 system network, Recovery Management (RMS) will try to remedy it by using the backup trunks or the free time slots in the primary trunks. The network operator

can also issue recovery commands through the Recovery Control Program (RCPR), which is an

operator interface to RMS.

No matter how the recovery works, the bottom line issue is whether there are suf ficient backup

trunks in the network or primary trunks which contain enough free timeslots.

Therefore the question of how to suf ficiently and economically arrange primary trunks and backup

trunks is an important issue to be considered when a network is planned and when the performance

of an existing network is examined. Is it possible to test network recovery without collecting real

time data

Fault Simulator (FSMR) is designed to serve this purpose. It simulates the faults which may occur

in the real network and allows you to observe how RMS reacts to faults. This tool is therefore very

useful in finding potential shortages in recovery designs of the planned or existing network, such as

a lack of redundancy or inef ficient parameter setups. It is possible to run Fault Simulator only in a

simulation database. This guarantees that Fault Simulator never disturbs normal network operation.

Fault Simulator generates two types of faults, i.e. trunk faults and node faults. It saves the faults in

the database and sends them immediately to RMS through a named pipe.

Fault Simulator is easy to use. Faults are introduced and removed by double-clicking on a node or a

trunk with the mouse or via trunk and node lists in the corresponding dialog boxes. In addition,command scripts for fault generation can be recorded by Macro Manager (see chapter 3.13.1 Macro

Manager ).

3.9.2 Network Capacity Calculator

In the 8100 system network, digital signals are carried by trunks and circuit cross-connections are

accomplished by nodes. The maximum amount of information flow through a trunk is called total

trunk capacity, and the maximum cross-connect capability is called total node capacity. When user

circuits are connected in the network, they take both trunk capacity and node capacity. What has been

taken into use is called used capacity, while what has not been taken into use is called free capacity.

Reporting

Network Capacity Calculator (NWCC) reports the network capacity, including total, free and used

capacity of trunks and nodes when circuit connections are made according to the customer's demand.

It is capable of calculating traf fic between different nodes or locations and traf fic internal to, ending

to or going through a location. It can be used when planning a network or evaluating an existing

one. This tool helps the network operator in discovering shortage or redundancy of capacity in the

planning or existing network. Fig. 96 shows a snapshot of NWCC in use.


158




Fig. 96 Snapshot of Network Capacity Calculator (NWCC)

Planning

It is possible to use NWCC in network planning. New nodes, trunks and circuit connections can becreated. First, it provides, as does Network Editor, a set of basic objects such as nodes and trunks to

create a network. In addition to the nodes and trunks referring to a specific item of the 8100 system

network hardware, NWCC introduces ideal nodes and ideal trunks into the network. An ideal node

has unlimited cross-connect capacity, and an ideal trunk has infinite transport capacity. It is also

possible to preset a real maximum capacity for a node type in the initialization file, and NWCC can

use the preset value in calculations instead of infinite values. Given the endpoints and the capacity

requirement, it builds up circuit connections, as does Router, automatically or manually. In theautomatic routing mode, each trunk is given a cost and the shortest path between the endpoints is

found by the program which minimizes the sum of the trunk costs. The user can select one from

various types of cost available before starting automatic routing.

NWCC first reads the network data from the database, while it is used for studying the existing

network. It displays the network, calculates the capacity, shows the statistics, and prints the results.The user can edit the network by adding or removing objects and make new circuit connections.

However, the changes made by using NWCC do not affect the data in the database. NWCC saves

the data in a file instead of the database.


159




3.10 8100 Service Computer

The Service Computer (SC) is supported for 8100 nodes. It is used to monitor and control the

operation of a single node. Node Manager is the only 8000 Intelligent Network Manager user

interface component which can be used in the Service Computer. Therefore it has some facilities of

Fault Management and Performance Management. The Service Computer has no database support.

3.11 Partitioned Package

The purpose of network partitioning is to allow large networks to be managed by 8000 Intelligent

Network Manager regionally and still provide a centralized view of the entire network. Large

networks consist of smaller regional subnetworks and a backbone network connecting the

subnetworks together. Network division into regions is performed on a geographical basis. The

main interest of regional operators is to manage their part of the network with less attention being paid to other parts. More or less, these operators want to view their regions as separate networks,

which can be managed ef ficiently no matter how large and complex the overall network structure is.

The regions are also protected against unauthorized usage by other operators. Special access rights

are needed in order to operate in several regions e.g. when building up the inter-region connections.

Partitioning improves the structural organization of the network and hence the management

procedures. This facilitates the network building and helps the operators to understand the overall

structure. Partitioning also guides the operators to build up the network in a more comprehensible

way; nationwide meshed networks can be avoided.

Users can focus on particular parts of the network; they can create different network views by

selecting the regions and hierarchy levels they wish to display on the screen. The views can be

selected in the Backbone Network Overview (see chapter 3.11.2 Backbone Overview of Network )of the Network Editor, Router, Fault Management and Performance Management tools. The

selected view also restricts the sphere of operation of these network level tools (refer to the chapters

describing these tools).

Views for VPN Provisioning and Tunnel Engineering are configured using the Region Selection

for VPN Provisioning dialog in the Dashboard. For further information, refer to 3.11.6 VPN

Provisioning and Tunnel Engineering in Partitioned Network .

In addition to views based on geographical region and hierarchy levels of the network elements, it is

possible to select views that are based on customers and circuits. In these three views, Customer

Components View, VLAN Components View and Circuit Components View, only those nodes,

trunks etc. that belong to a given customer, or are part of a selected circuit, or are in particular

VLAN domain are shown on screen.

The relationships between the different choices of viewing the partitioned network are described

in the following chapters.

3.11.1 Hierarchy Levels for Partitioning

A large flat network is divided into regions on a geographical basis. Each node is attached to

a single region. In addition to this, different hierarchy levels are assigned to network trunks and

nodes. There are two ways of configuring the regions: the hierarchy levels of nodes and trunks can

be used in dividing the network into the access and backbone parts (access L1, backbone/access L2

and backbone L3), or into generalized regions simply dividing the network into smaller parts.


160




If access/backbone division is used, a single geographical region can contain both access and

backbone level components, or only backbone level components. This model supports the

assumption that a regional operator is often responsible for installing, monitoring and maintaining

all the network elements in a region, including the backbone network components.

The hierarchy levels are originally based on three categories of traf fic:

• region internal traf fic

• traf fic terminating at a region

• transit traf fic

These traf fic categories are used in defining the hierarchy levels for network trunks. The level of a

trunk thus indicates the nature of traf fic that is either used or intended to be used. The nodes are

also assigned similar hierarchy levels. These, in turn, are determined according to the hierarchy

levels of the connected trunks.

Router and Recovery Management obey the hierarchy levels when routing circuits or recoveringcircuits or trunks if the Partitioning Traf fic Rules are enabled. In addition, these tools obey the

regional boundaries via the so-called Partitioning Network Rules. In Recovery Management the

operator can also disable the Partitioning Network Rules for a specific trunk or circuit.

Fig. 97 shows an example of a partitioned network. Note that the backbone network is formed by

trunks at the level L3 and nodes belonging to the categories L2 or L3. The access network consists

of trunks and nodes of the categories L1 and L2. The figure is purely logical and does not present

any geographical relationships between the regions.

Fig. 97 Network Partitioning Hierarchy Levels


161




3.11.2 Backbone Overview of Network

Selections of view preferences can be made in the Backbone Overview mode. The operator canselect (mark) one or more regions. For each region the operator can select to view either backbone

components, access level components or both if the access/backbone division is used. This selection

of the level of interest can be different for each region. If generalized regions are used, the operator

can select the desired region.

Fig. 98 Backbone Network Overview (Access-Backbone Division Used)

From this Backbone Network Overview mode the operator can open either a Regional Network View(chapter 3.11.4 Regional Network View), a Backbone Network View (chapter 3.11.3 Backbone

Network View ) or an All Network View. The selection of the regions and the selection of the

level of interest only affect the Regional Network View and are necessary before activating the

Regional Network View. The Backbone Network View displays the backbone level components

independently from the selection of the level of interest. The All Network View shows all the nodes

and trunks as if the network was not partitioned.


162




The operator can restrict the Regional Network View to consist of only such network components

which belong to a given customer, or are part of a selected circuit, by activating the Customer

Components View (chapter Customer Components View) or Circuit Components View (chapter

Circuit Components View ) or VLAN Components View (chapter VLAN Components View).

These component views can also be activated/deactivated in the Regional Network View. A separatelicense is needed to activate these component views.

An operator with permissions limited to a single region can bypass the Backbone Overview mode

and go directly to the Regional Network View when opening a network level tool. (See chapter

3.11.4 Regional Network View)

3.11.3 Backbone Network View

Fig. 99 Backbone Network View

The Backbone Network View shows the backbone level (L3) trunks and the corresponding end

nodes, i.e. the backbone network. In case the operator has no backbone level access to a region, the

corresponding trunks and nodes are dropped from the view. Real management operations can be

performed in this view, e.g. the operator can zoom into the node with Node Manager, or activate

fault monitoring for the components shown.


163




3.11.4 Regional Network View

Fig. 100 Regional Network View

The Regional Network View shows the access level and/or backbone level nodes and trunks of

selected regions. Different levels of interest can be used in different regions at a time; the selection

of regions to be viewed is performed in the backbone overview mode.

Each node must have a region and a hierarchy level in order to be shown in this view. The nodes andtrunks which are created in a VPN workstation are not shown in this view before a RNO has added

the required information to them. RNO can access such nodes and trunks in the non-partitioned All

Network View, which can be activated from the Backbone Network Overview mode.

A trunk which leaves a region to another region not shown in the view is represented by an arrow

symbol. Fig. 22 contains three such symbols for the backbone level (L3) trunk bundles.

Activating/deactivating the Customer Components View (chapter Customer Components View) or

Circuit Components View (chapter Circuit Components View) or VLAN Components View (chapter

VLAN Components View) is also possible in this Regional Network View.


164




3.11.5 Fault Management in Partitioned Network

In a partitioned network, different views are offered for operators in the network level tools to assistin focusing only on a relevant set of network elements at a time. In Fault Management System only

the faults originating from the components currently shown in the view are reported. Also, even if

the node is visible in the view, but the fault originates from an interface or a unit which is of no

interest for the current view (backbone/access aspects), the fault is filtered out. The rules for the

faults in different views are explained in the following chapters.

Backbone Overview

No faults are reported in this view.

Backbone Network View

The following faults are included:

• All faults from visible L3 trunks and L3 nodes.

• All faults from SCU, SXU etc. common units of visible nodes.

Regional Network View

The visible faults within each region depend on the level of interest defined (access/backbone/all)

for a region:

1. Level of interest is backbone for region BB1. The following faults are visible:

• Faults originated from L3 nodes in region BB1.

• Faults originated from common units (SCU, SXU etc.) of L2 nodes in region BB1.

• Faults originated from L3 trunk interfaces from L2 nodes in region BB1.

2. Level of interest is access for region ACC1. The following faults are visible:

• Faults originated from L1 nodes in region ACC1.

• Faults originated from L2 nodes, with the exception of L3 trunk faults.

3. Level of interest is all for region ALL1. The following faults are visible:

• All faults originated from all nodes in region ALL1.

Customer Components Network View

• Only those components and faults that are affected by the selected customers are displayed.

• Fault history reports cannot be retrieved in this view.

• Network change messages for the component view are not visible, but the main view will process

them.


165




Circuit Components Network View

• Only those components and faults that are affected by the selected circuits are displayed.

• Fault history reports cannot be retrieved in this view.

• Network change messages for component view are not visible, but the main view will process

them.

L3 Trunk Monitoring

A trunk which leaves a region to another region not shown in the view is represented by an exit

arrow symbol. In Fault Management System these bundles are also under fault monitoring. Two

different operational modes can be defined for the monitoring:

• full L3 trunk monitoring• partial L3 trunk monitoring

Full monitoring includes faults from both end interfaces of a trunk. Partial monitoring ignores the

L3 trunk faults in case the faulty interface is not within the selected regions.

3.11.6 VPN Provisioning and Tunnel Engineering in Partitioned Network

Partitioning for VPN Provisioning and Tunnel Engineering is enabled by default for the systems

that have already been configured for the generic partitioning support. The accessible regions and

the level of access allowed for the operator are configured in Regional Role Editor. Note that if

an operator profile has the Use global privileges to all regions or Super User option configured,

the operator automatically has access to all regions. When an operator logs in the Dashboard, theVPN Provisioning and Tunnel Engineering applications are automatically configured to show all

regions that the operator has access to.

The Region Selection for VPN Provisioning dialog is displayed in the Dashboard offering a

quick overview of the regions that the operator can access with VPN Provisioning and TunnelEngineering. In this dialog it is possible to select a set of regions to e.g.allow the operator to focus

on a specific group of network elements. Additionally, partitioning offers better performance as

without partitioning all existing VPN network element and tunnel data might get loaded into VPN

Provisioning and Tunnel Engineering. With partitioning only the data from regions with allowed

access is loaded.


166




Fig. 101 Region Selection

The rules regarding the allowed operations for an operator, .e.g. a connect or disconnect operation,

vary depending on which VPN or tunnel service is configured. In general, the operator needs to

have the Read/Write privileges to all regions where the involved network elements are located.

When a minimum number of regions is selected there may be elements in the VPN Provisioning

and Tunnel Engineering tools that are shown as Not in view. However, this does not impact the

operations that an operator is allowed to perform; e.g. the operator may still be able to connect a

VPN although some endpoints are shown as Not in view.

Note that if a set of regions changes while VPN Provisioning and Tunnel Engineering are running,

the applications must be restarted.

3.12 Unit Software Management Package

The Unit Software Management tools are used for updating the element software (ESW) in network

elements. Instead of updating the network elements one by one, these tools enable running the

update ef ficiently for tens or even hundreds of network elements. In addition, the tools provide ESW

reports for a set of selected nodes. The Element Software Management tool supports 7090, 7100

and 8600 product families. The 8100 Unit Software Management tool with reduced functionality

is used for 8100 network elements.

3.12.1 Element Software Management

The Element Software Management tool provides services to maintain element software files. The

software files are stored either in the database or FTP servers. The 8600 software files are stored in

the database whereas the 7090 and 7100 files are stored in the FTP servers.

The tool provides also ESW inventory reports for a set of selected nodes. Optionally, the report can

be enhanced with the detailed software information by reading the data directly from the network

elements. For 8600 nodes, the tool provides additionally unit-based reports. Reports can be saved to

a file in CSV format allowing to import the information to another reporting tool.


167




The software update in the network elements is based on download plans which can be created with

this tool. Each download plan supports a product family specific update procedure. The plan defines

a set of network elements to be updated. For each network element, the software file and version

can be selected. In addition, a set of run-time options for the plan can be defined. It is possible to

schedule the download task to be run later at the time defined in the plan. The software update can be done fully automatically, or the update procedure can be stopped in some update phase, e.g. after

transferring the file but before activating the software. This allows continuing the software update

manually. Before activating the plan, the user can select which network elements in the plan will be

processed enabling the user to take more control over the update procedure.

The tool provides a copy operation for creating new download plans based on the old plans. A plan

can consist of hundreds of network elements, and using this copy functionality a lot of manual work

can be avoided. The plan can be modified by adding new elements to the plan or by removing

old and obsolete network elements. The tool also enables easy modification of the used software

files and versions in the plan.

Normally the software of the network elements is updated as a whole including all units in the

network element. This can be done by using software packages including software and possibly

FPGA images for all types of units. However, the tool supports also a unit-based software update

with unit specific software files for some unit types.

When the download plan has been activated and the corresponding download task created, the

update procedure can be monitored by following the status columns in the plan. For each network

element in the plan, the tool reports the current update stage, state, operation and possible problems.

During the update procedure the download task can be temporarily paused or completely stopped. A

stopped task can be restarted again and the procedure will continue from the phase it was before the

stop operation. Also a completed task having some problems can be restarted.

The download task is performed stage by stage according to the product specific update procedure.

On each stage a set of network elements are processed in parallel speeding up the whole update procedure. The level of concurrency can be controlled by defining the corresponding options in the

download plan.

The completed download plans can be removed from the database but they can also be kept in the

system as documents about the software updates in the network elements.


168




Fig. 102 Element Software Management Application

3.12.2 8100 Unit Software Management

For the 8100 system nodes, the 8100 Unit Software Management tool provides features to get

reports on software and hardware versions of units of a selected type in a selected set of nodes.

The user can automatically download new software into several units selected anywhere in the

8100 system network. Downloading new software into different units can be done in one session,

and the events of download progress can be saved into a file for further review. The unit and file

information in the main window and in the download dialog can be saved in a file or printed on a

printer. The software version, serial number of units and the date of downloading are also updatedinto the database.

To prevent any errors in the unit software download, the tool also checks for inconsistent software:

the name of the software file is compared to the unit hardware type, as well as, checking the

software version numbers.

The time required for downloading can be reduced by opening several download sessions

simultaneously. You can start several download tools for different areas of the network in one or

more computers. In one computer, the recommended maximum number of tools is four, which thenalso requires four unique file names for download events to be saved. Unit Software Compatibility

Checker checks the compatibility between the GMU base unit software and other unit software

in a node.


169




3.13 Macro Package

3.13.1 Macro Manager

Macro Manager is an additional tool for managing the network by special macro commands. The aim

is to speed up the network management processes in the case of a large network and a huge number

of network objects (nodes, trunks, circuits, etc.). The interactive graphical interface is replaced by

macro commands. Additionally, you can create your own Graphical User Interface for your macros

using the Application Development Toolkit, see chapter 3.13.2 Application Development Toolkit.

You can reuse the sample macros delivered with the program or record your own macros. The macro

language supports high-level control structures, such as variables, conditional statements, loops and

submacro calls. It can also handle database change messages and supports file operation, threading,

scheduling, polling and printing. These features allow you to write complex programs in Macro

language to automate sequences of 8000 Intelligent Network Manager operations.

Node Manager macros are used for setting different kinds of hardware parameters. Most of them

also update the database. Network Editor macros are used to build and edit the network in the

database. Router macros are used for managing circuits. Fault Simulator macros are used for adding

and deleting node and trunk faults in the database. Note that simulator macros can only be run in

a simulation environment. Topology macros are used for node inventory and trunk provisioning.

Service provisioning macros are used for IP VPN and pseudowire provisioning. Discovery macros

are used for discovering nodes, IP VPNs and pseudowires.

Add-on macros are macros that can be launched directly from the 8000 Intelligent Network Manager

GUI. An add-on macro can be associated with specific NE objects (for example, interfaces of a

specific type) and then launched for those objects via pop-up menus in Node Manager.

Refer to the Macro Manager online help for details.

3.13.2 Application Development Toolkit

The Application Development Toolkit is a platform for the graphical user interface (GUI) and

network level programming. It is a high-level programming language with a class library that

gives you a network level object model of the 8000 system network. It includes the 8000 system

network, visual (GUI) and parameter objects. With Application Development Toolkit you can create

your own windows and dialogs to view and configure parameters of the 8000 system network.

With Dialog Editor you can design your own dialogs. Application Development Toolkit supportsstandard GUI application features, window and dialog controls like menus, buttons, edit fields

and list views with columns.

Application Development Toolkit requires a separate license. It uses the services provided by Macro

Manager and thus requires that the Macro Manager license is active in 8000 Intelligent Network

Manager.

The functionality provided by Application Development Toolkit and macros provided by Macro

Manager work seamlessly together. The window macro applications developed with Application

Development Toolkit can be run separately from Macro Manager.


170




3.14 Web Reporter

The Web Reporter tool is used to access information in the 8000 system network through the intranetor the Internet. In addition to the traditional browsers, there is a dedicated Web Reporter application

for mobile devices (for Android, iOS and Windows) providing an easy-to-use GUI. The resolution

and scale have been optimized for the mobile version. The same logic is being used in both browser

options for login, navigation tree and report filtering.

Web Reporter enables fast distribution of information without the need to consult the personnel

operating the network. For example, customer service staff and sales personnel can view circuit

capacity, availability, pseudowire and tunnel information, free node interfaces or faults when a

customer calls. Field service personnel can see where a fault is located and plan repairs accordingly;

they can also receive node information when installing new hardware and services. Management

can monitor the quality, performance and observe the size and contents of the network. Also the

network operators benefit from the clear and comprehensive reports. End customers may be

interested in monitoring the availability of their circuits and pseudowires. Regarding the secure

communication over the network, Web Reporter supports HTTPS providing the encryption of the

communication between a client and a server.

The system contains a number of predefined reports that the user can schedule. The output format

for these periodic reports is HTML, PDF or Excel.

8000 INM SR6.0 System Description

Documents

Transcript of 8000 INM SR6.0 System Description