Ma334 A1

Technical Documentation
Product family
Tellabs 6300 Managed Transport System

Tellabs 6300 Network Manager Description of Management Application and Platform
Product name
Title
Document
Product Description
MA334 / Revision A1
Copyright 2002 Tellabs. All rights reserved.
Tellabs 6300 network manager Description of Management Application and Platform
Legal Notices
Legal Notices
Copyright Statement
This Tellabs manual is owned by Tellabs or its licensors and 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 following trademarks and service marks are owned by Tellabs Operations, Inc., or its affiliates in the United States and/or other countries: AUDIO PLUS, CABLESPAN, CEC-128, DYNAMIC SIGNAL TRANSFER, DXX, DXX logo, EC DUO, ENHANCED AUDIO PLUS, EXPRESS/PATH, FOCUS, MARTIS, MARTISDXX, MARTIS logo, MARTISDXX logo, METROVANTAGE, METROWATCH, NETREACH, NETWISE, SCULPTURED SOUND, TELLABS, TELLABS and T symbol, T symbol, TELLABS PROPARTNER, TEL/MAP, TEL/MOR, THE WORLD COMMUNICATES THROUGH TELLABS, TITAN, VERITY, YOUR NETWORKING PARTNER. Any other company or product names may be trademarks of their respective companies.
Trademark Notice
MA334 Rev. A1
Revision Information
Revision history
This document has changed as follows:

Rev. Date Description of Changes
A1
Nov. 30, 2002
First revision.
MA334 Rev. A1
MA334 Rev. A1
Contents
Introduction
...........................................
Part 1
The Management Application

2 Description of Tellabs 6300 Manager . . . . . . . . . . . . . . . . . . . . . .
2.1 2.2 2.3 2.4 2.5 2.6 2.7 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Representation of the Network in Tellabs 6300 Manager . . . . . . . . . Indication and Presentation of Alarms . . . . . . . . . . . . . . . . . . . . . . . . Viewing Timing in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Management of Network Elements . . . . . . . . . . . . . . . . . . . . . . . . . . Collection of Performance Data and Events . . . . . . . . . . . . . . . . . . . Management of Network Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.1 Network Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.2 Creating Trails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.7.3 Inspecting and Handling Trails . . . . . . . . . . . . . . . . . . . . . . . 2.7.4 Inspecting the Network Database . . . . . . . . . . . . . . . . . . . . . 2.7.5 Representing Foreign Equipment in the Network Model. . .
11
11 12 15 18 19 22 23 24 25 29 35 36
3 4
Tellabs 6300 Manager as a Structure of Licenses Connecting to Other Systems
...........
39 41
...........................
Part 2
The Management Platform

5 The Platform of Tellabs 6300 Manager
5.1 5.2
....................
45
45 46 46 47 48 50 51 52 52 53
5.3 5.4
The Main Structure of a Tellabs 6300 Manager System . . . . . . . . . . The System Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 Stand-Alone (Single-Server) Systems . . . . . . . . . . . . . . . . . . 5.2.2 Distributed (Multi-Server) Systems . . . . . . . . . . . . . . . . . . . . 5.2.3 Using Clusters to Improve Availability . . . . . . . . . . . . . . . . . . 5.2.4 Using Remote Standby Systems to Improve Availability . . . . Configuration and Installation of the System . . . . . . . . . . . . . . . . . . . System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Management of System Security. . . . . . . . . . . . . . . . . . . . . . 5.4.2 Default User Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
55
MA334 Rev. A1
Contents
MA334 Rev. A1
1 Introduction
Introduction
A telecommunications management network (TMN) is a management network which is used to monitor and manage a telecommunications network; that is, monitoring and managing the equipment in the network as well as the traffic in it. The TMN provides the various functions for managing the network as well as the actual communication with the equipment in the network and with other TMNs. A TMN can vary in complexity from a very simple connection between a management system and a single piece of telecommunications equipment to a complex network interconnecting many different types of management systems and equipment. The TMN may provide management functions and offer communications both between the management systems themselves, and between management systems and the various parts of the telecommunications network.
Definition of a TMN
Tellabs 6300 manager
The system architecture of Tellabs 6300 manager complies with the requirements for a TMN architecture. It offers an open architecture with network element management and network traffic management functionality, and it is a field-proven system for integrated management of SDH transmission networks composed of network elements from multiple suppliers. On top of that, Tellabs 6300 manager offers open interfaces for interconnection to other TMN architectures to provide automated information processing. Management of end-to-end network traffic Management of individual network elements Management of the interconnecting data communications network Management of the management system itself. The integration of these management functions with high availability options and security functions makes Tellabs 6300 manager a well suited solution for overall management of transmission networks.
The platform
Tellabs 6300 manager runs on a platform with the following configuration: Industry standard AlphaServer machines from HP used as servers. The Tru64 UNIX-based HP OpenView TeMIPTM software platform from HP. TeMIP is an abbreviation of Telecommunications Management Information Platform. An Oracle SQL database. The platform is delivered, installed and configured by Tellabs Denmarks Systems Integration department. The communication between the management system and the telecommunications equipment is handled by a data communications network (DCN).
MA334 Rev. A1
1 Introduction
Advantages from the platform of Tellabs 6300 manager
The following items are just a selection of the advantages from the platform of Tellabs 6300 manager: Capacity for management of multi-vendor equipment A distributed, scalable computer network with efficient backup to ensure constant availability Modular design for seamless migration Constant surveillance of not only the telecommunications network, but also of the platform itself Interface to other management systems An easy-to-use graphical user interface. These features, and others, are described in more detail in this document.
User workstations
Tellabs 6300 manager is accessed from workstations with the following configuration: PCs used as clients Windows 2000TM software platform from Microsoft. The workstations provide access to the graphical user interface described in this document.
This document
The focus of this document is to give you a general overview of the capabilities and potential of Tellabs 6300 manager as a complete SDH Management application. Therefore, to provide such an overview, the description is feature-byfeature rather than function-license by function-license (a brief introduction to the function licenses is, though, given in 3 Tellabs 6300 Manager as a Structure of Licenses on page 39). The first part of the document describes how to use Tellabs 6300 manager for network management, while the second part is a description of the platform used by Tellabs 6300 manager.
Further information
The detailed information about the features of Tellabs 6300 manager is, of course, to be found in the manuals accompanying the system. We offer one set of manuals that are meant as a general introduction to the system (describing the general use of the systems graphical user interface and the procedures for alarm handling), and then, on top of that, the manuals describing the main functionalities of the system individually (that is, one manual for management of a specific network element, one manual for traffic management, and so on).
MA334 Rev. A1
Part 1 The Management Application
Part 1
The Management Application

2 Description of Tellabs 6300 Manager on page 11 3 Tellabs 6300 Manager as a Structure of Licenses on page 39 4 Connecting to Other Systems on page 41
MA334 Rev. A1
Part 1 The Management Application
10
MA334 Rev. A1
2 Description of Tellabs 6300 Manager
Description of Tellabs 6300 Manager

This chapter is meant to give you an idea of how Tellabs 6300 manager is used for managing telecommunications networks. We will, of course, focus mainly on the special features of the system. Part of the concept behind Tellabs 6300 manager is to provide you with a quick and easy overview of your network, with easy access to the relevant management functions.
Overview
2.1
Introduction
The general features provided by the graphical user interface of Tellabs 6300 manager are: A graphical representation of the network, with icons representing network elements and other objects. Use of a hierarchical map structure to split up the network representation in logical groupings (for example, grouping in geographical locations). In Tellabs 6300 manager, the maps are called domains and subdomains. Use of the mouse (point, click and drag) to navigate in the network, to manipulate the displayed objects, to perform operations on the different objects, etc.
The general features of the graphical user interface
Multiple users possible Single-server or multiple servers possible
Several users can have access to Tellabs 6300 manager at the same time. A Tellabs 6300 manager system can be set up either as a single-server system or as a distributed system with several servers (hosts) running the Tellabs 6300 manager software. In a distributed system each host is responsible for managing a specific group of network elements. Such distribution makes the Tellabs 6300 manager system very scalable, as new hosts can simply be added.
Command line interface also available
In addition to the graphical user interface described in this chapter, Tellabs 6300 manager also offers you a text-based command line interface. This can be used to combine a series of manual operations into one compound operation.
MA334 Rev. A1
11
2.2
Representation of the Network in Tellabs 6300 Manager

In Tellabs 6300 manager, the network is visualised with icons representing network elements, manholes etc. and with lines representing the cables between them. The network can be organised in a hierarchy of domains, with each domain showing a specific part or level of the network.
Showing the network structure
A network element can be shown in several domains at the same time. This allows you to create some domains showing the network structure and other domains showing, for example, groups of network element types.
Navigating in the domain hierarchy
One of the special features of Tellabs 6300 manager is a domain browser, which shows the domain hierarchy as a tree structure. This makes it easy to navigate between the domains.
12
MA334 Rev. A1
Setting up the network model
Tellabs 6300 manager contains a network editor which is designed to make it easy for you to set up the traffic model of your network. The network editor only requires the creation of one level and then automatically generates the representations of all relevant network levels from that one.
The work environment for using the network editor is provided by the Network Editor window. This window contains all the necessary tools for creating a network model.
Working in the network editor on page 14 gives a brief overview of how to use the network editor.
MA334 Rev. A1
13
Working in the network editor
The tree structures in the Network Editor window provide you with those network objects that can be placed in the domain map.
Actions
1.
Create the network object in the appropriate tree.
2.
Transfer the network object to the domain map.
3.
Open the network object for further configuration (for example, to set up the matrix connections representing fibre interconnections in a manhole).
14
MA334 Rev. A1
2.3
Indication and Presentation of Alarms

When an alarm is received from a network element, a new alarm information line appears in the alarm list in the Alarm Handling window and the icon representing the network element in TeMIPs Iconic Map changes color to indicate the appearance of an alarm. The alarm indication color is determined by the severity level of the alarm. The change of color happens in every map where the network element is shown. Similarly, if an alarm affects traffic in the network, Tellabs 6300 manager can generate alarms for affected network level entities such as end-to-end connections (trails), and the alarm is indicated by a change of color of the trail name in a list of trails. This particular function is called trail surveillance (see Trail surveillance on page 32). The alarm function presents the alarm information in fields according to the standard ITU-T OSI alarm_Record (X.721), and it implements the ITU-T X.733 and ITU-T X.735 standards.
Indicating alarms
Information about a new alarm
The detailed information for each new alarm includes the probable cause of the alarm, the name of the object that generated the alarm, the identity of the operator who has acknowledged the alarm (when the alarm has been acknowledged), when the alarm was issued, and when it was received by Tellabs 6300 manager.
You can open an extra window with the details of one specific alarm by either double-clicking on the alarm or by selecting the alarm and pressing the Full Information button.
MA334 Rev. A1
15
Trails affected by alarms from network elements
When a network element alarm appears, you can get direct information about which network traffic trails, if any, are affected by the specific alarm. This is done via the pop-up menu for the relevant alarm line. The figure shows how information about the trails affected by a specific alarm is displayed in the Find Trail window.
Filtering of alarms
The TeMIP alarm handling used by Tellabs 6300 manager splits up alarm monitoring into various operational areas (that is, monitoring of alarms from different areas of the network, from different element types etc.). This is done by using special objects called operation contexts, where each operation context is assigned to a specific domain, and will therefore collect all alarms from that domain and all of its subdomains. When you set up the alarm handling function, you specify which operation contexts to receive alarms from. On top of that, you can create special filters for the presentation of alarms in the alarm window and/or have Tellabs Denmarks Systems Integration set up special low-level event filters.
Filtering criteria
The following alarm filtering criteria are available in the alarm window: Alarm type Problem status Perceived severity Probable cause State Target entities Managed object Operation context Domain
16
MA334 Rev. A1
Security alarm cause Specific problem Before time After time Clearance report flag Correlated notification information Operator note Additional text
Saving alarm information
All alarms are automatically stored in an alarm log. Each operation context has its own alarm log, in which you can search for specific alarms.
From the alarm log, the alarms can be archived in an SQL database from which they can later be retrieved for further analysis.
MA334 Rev. A1
17
2.4
Viewing Timing in a Network

The timing view of Tellabs 6300 manager provides a graphical view of the clock distribution and synchronization between network elements in the network. The timing view shows the following features: The active and alternative clock sources (SDH, PDH or external) The port number, quality and priority level of each timing source. It can be used to discover timing loops and to improve the topology of the network.
The information shown
Timing view
Since the timing information is obtained from the MS overhead, the timing view is shown in the network representation of the MS layer in the Network Management window. As illustrated in the figure below, the icons and lines ordinarily used in network view are replaced by special icons and arrows, indicating the clock sources.
18
MA334 Rev. A1
2.5
Management of Network Elements

The configuration of a network element (that is, the actual equipment installed in the physical network element), can be managed in an equipment view.
Inspecting and managing network element configuration
The equipment view is a graphic representation of the network element: showing the type and position of the modules in the network element, with alarm coloring. From this view, you can commission network elements, add new modules, configure modules, look at alarms etc..
MA334 Rev. A1
19
Setting up a new cross connection
The traffic view of the network element allows you to easily operate on the existing cross connections and set up new cross connections. To set up a new cross connection, you use the mouse and simply select one of the connection points, activate the pop-up menu, and then draw a line representing the cross connection to the other connection point.
Description Illustration
1.
Select the connection point and open the pop-up menu to select the type of connection.
2.
A red line is attached to the mouse, starting in the selected connection point.
3.
Drag the line to the other conenction point. The line changes color to green if connection is possible.
4.
Click with the mouse to verify the connection. The connection is created.
20
MA334 Rev. A1
Configuring synchronization
The graphical representation of a network elements synchronization architecture allows you to easily access all configuration aspects and operations of synchronization.
Note: The synchronization of the whole network can be inspected in the spe-
cial timing view, as described in 2.4 Viewing Timing in a Network on page 18.
From the Synchronization window you can synchronize the internal clock generator of the network element with an external stable and reliable synchronization source, and you can configure an external clock output from the network element, which can be used as a reference source for external equipment.
Element management functions
Other available element management functions are: Setup of data communication network (DCN) Performance monitoring of network element termination points Management of embedded software Management of network element backup Management of optical ports Management of termination points.
MA334 Rev. A1
21
2.6
Collection of Performance Data and Events

All kinds of performance data can be collected (standard SDH performance counters supported in the managed SDH network elements as well as GFP mapping data for Gigabit Ethernet cards). The performance data is stored in a standard SQL database and is presented in report form by a performance report generator.
Collecting performance data
22
MA334 Rev. A1
Operations in performance data monitoring
The following operations are involved in monitoring of performance data: Starting and stopping the collection of performance data for network elements or other monitored objects. Automatic collection and storage of performance counters in the performance database. Generating performance data reports based on the performance data. 15 minute and 24 hour reports are available. Generating performance collection status reports that show all the active monitored objects. The performance data can be correlated from the network elements to the trails. The performance management reports are generated per network element or per trail. It is, however, also possible to export the data in comma-separated files and generate other types of reports.
Monitoring trail segments non-intrusively
In addition to the ordinary end-to-end trail monitoring, it is possible to monitor a trail segment without terminating the trail. This kind of "listen-only" monitoring is called non-intrusive monitoring and allows you to monitor the incoming and outgoing data flows in the segment separately. Non-intrusive monitoring is, for example, useful when it is necessary to monitor a specific customers segment of the network.
Collecting event data
Event logging can be used to record the events for a domain representing the entire network or a selected portion of the network. The events are placed in event logs where you can analyse and manage the individual records (whether you want to use only a single event log or multiple is up to you). It is possible to search for specific event records, using such search criteria as managed object, notification identifier, log record class etc. The event logging can also be suspended for a specific time interval and then later resumed. Event logging implements the ITU-T X.734 Event Management Function and the ITU-T X.735 Log Control Function. The managed object classes (log and eventLogRecord) are ITU-T X.721 compliant.
2.7
Management of Network Traffic

The key to the wide variety of network-layer management functions offered by Tellabs 6300 manager for network traffic management is a powerful network model concept. The model is not concerned with the specific attributes of the network elements, but is intended to mainly represent the networks end-to-end connections (trails) and capacity (in the form of available time slots between network elements) at the different bandwidth layers. Each network element is represented by a matrix that contains information about termination points and internal connections. The model goes further in the sense that it registers those time slots (called link connections) between the network elements that are used by the trails. Various media optical, electrical, microwave etc. are represented in a uniform way. The network topology at the different bandwidth layers is stored together with element resources (capabilities), and the logical states of the trails across the network are managed. This information, which is stored in a net-
Using a network model
MA334 Rev. A1
23
work database (see Network database on page 24), gives a picture of the state of the physical transmission network. The network model also allows you to include representations of equipment which is not actually managed as part of the specific network but which is used by the trails in it. Such foreign equipment could, for example, be a leased line in another suppliers network or it could be one of your own networks which is managed separately. See 2.7.5 Representing Foreign Equipment in the Network Model on page 36.
2.7.1
Network Information
The network information is split up into information concerning the different bandwidth layers, each represented by a network level.
Representing the network at different bandwidth layers
The physical layer as well as the RS- and MS layers are modelled in order to support, for example, routing of working and protecting routes in physically separated resources. The OCH and OMS layers are used to model dense wavelength division multiplexing (DWDM) equipment.
Network database
The main functions of the network database used by Tellabs 6300 manager are to provide: an information repository for all functions at the network level functions for registration of trails, links, matrices etc. the structural relations between entities at different traffic layers in the SDH multiplexing architecture the means for storing the operational state of network resources. The network database is an implementation base on the ETSI ES 200 653 recommendation for telecommunication management networks. That is, it stores information about SDH trail termination points (TTPs), connection termination points (CTPs), links, link connections and matrices, which are the basic entities for using the network layer functions. The contents of the database are presented either graphically or in tabular form, and the network information itself is implemented in an industry standard SQL-database.
24
MA334 Rev. A1
2.7.2
Creating Trails
If you had to use the ordinary element management work procedures for setting up trails, you would have to operate on each individual network element in the trail to create cross connections between one element and the next. This could very easily result in misconnections of time slots between elements. Using the special trail setup function, however, you can set up trails (end-to-end connections) across all of the network elements as one single operation, with no risk of misconnections, simply by selecting the two end points for the trail in the graphical user interface.
Description Illustration
Setting up trails in one operation
1.
Select one of the end points and open the pop-up menu to start trail setup.
2.
A red line is attached to the mouse, starting in the selected end point icon.
MA334 Rev. A1
25
Description
Illustration
3.
Drag the line to the other end point. The line changes color to green if a trail is possible.
4.
Click with the mouse to verify the trail. The line changes color to yellow and the Setup Trail window appears.
The default trail created this way is a trail with only one, automatically selected route (that is, an unprotected trail) which is not reserved for any customer. However, the Setup Trail window contains a number of fields and toggle buttons that can be used to specify of the trails parameters.
26
MA334 Rev. A1
The main functions of trail setup
Trail setup in Tellabs 6300 manager is used for end-to-end trail configuration. It allows you to set up protected and unprotected bi-directional trails at the VC12, VC3 and VC4 layers across the SDH transmission network. The route (or routes if the trail is protected) can either be specified manually or be calculated automatically. The main functions of trail setup are: Calculation of the optimal route and, optionally, an associated protection route Automatic and manual setup of trails in meshed networks according to criteria specified by the user Connection in the network elements of a reserved trail
Note: The other traffic in the network is not disturbed when Tellabs 6300
manager establishes a new trail in the network elements.

Setting up trail using automatic route calculation
When you create trails using automatic route calculation, you only need to select the desired end points for the trail and specify the routing preference criteria (cost parameter values and exclusion of specific resources). When that is done, Tellabs 6300 manager executes the high-level process stages described in the table.
Stage Description
The route is calculated according to the routing preference criteria (that is, specific cost parameter values for the route to be selected and exclusion of specific resources to ensure physically diverse routing).
Note: This calculation is highly sophisticated, with options to assign priority according to fibre kilometres, number of link connections, spare capacity in link, traffic load factor, or a user-defined parameter (corresponding to the cost parameters: length, jump, spare, load and user). Also it is possible to set up an Exclude List of those resources that are not to be used in the route.
2 3
The calculated route is reserved in the network database. The trail is implemented in the physical network elements. During connection, alarms are suppressed.
MA334 Rev. A1
27
Setting up the trail using manual route specification
When you want to set up the route (or routes) for the trail manually, you can select the route in the graphical user interface of the Network Management window simply by clicking on the links, one after the other, that are to form the route. The selected links are highlighted in a special color, so that you can see the selected route in the graphical user interface.
Note: The links forming the primary (working) route and the links forming
the alternative protection route are highlighted in different colors.

Partial protection of trails
When you are setting up a new trail, you can only protect it with one end-toend protecting route. Afterwards, however, you can set up partial protection of the trail by adding protecting subroutes.
The figure shows an example of the use of partial protection. A trail passing two rings is protected in the two rings separately, thereby avoiding any dependency between the protection of the rings.
Trail trace identifiers
To check that the routes of a specific trail are connected as planned, a trail trace identifier (TTI) can be transmitted from one end of the trail and received at the other end. The received TTI is compared to the expected TTI value in monitored termination points along the trails route.
28
MA334 Rev. A1
The TTI values can be either user-defined or generated by the system. They can be created when the trail is created and are then copied into the termination points when the trail is connected. It is, however, also possible to reconfigure the TTIs for an existing trail, whether the trail is connected in the network elements or not. Information about TTI values and validation can be displayed graphically for a specific trail. See Inspecting trail trace identifiers on page 33.
2.7.3
Inspecting and Handling Trails

You can use the Find Trail window to get information about all or some of the registered trails.
Finding and inspecting specific trails
The Find Trail window contains a filter part that enables you to search for trails terminating in specified end points, used by a specific customer and/or in a specific management state. The window also contains an attribute filter so that you can display and compare a selection of attribute values for the trails.
MA334 Rev. A1
29
A pop-up menu is attached to the trail name. With the menu items in this popup menu, you can activate trail operations and open other windows with information about the selected trail.
Handling trails
The main functions available in the trail pop-up menu in the Find Trail window are: Disconnection of a reserved/connected trail Removal of trails Managing trail trace identifiers (TTIs) Managing protection Changing the configuration of a trail Viewing the detailed routing of a trail.
30
MA334 Rev. A1
Inspecting the route(s) of a trail
The route(s) of a specific trail can be highlighted in the display of the network. But you can also open a more detailed view of the routes.
The detailed view of a trails routes shows the specific time slots and cross connections used in the trail. Further details about the cross connections, time slots and other entities (matrices and links) shown in the view can be obtained by activating the operations in the pop-up menu attached to each type of entity. It is, for example, possible to open the traffic view of the network element corresponding to a matrix. Any parts of a trail that do not form well-defined subroutes are also indicated in the trail view, so that they can be identified and corrected.
Reconfiguring trails
In connection with network repairs or periodic administration, it may be desirable to alter the configuration of a particular trail. This is done in a set of windows that each are dedicated to a specific reconfiguration operation: Changing the routes and subroutes of the trail. Protecting a trail (that is, adding alternative routes or subroutes). Unprotecting a protected trail (that is, removing routes or subroutes). Changing the signal structure of a VC4 trail (that is, the packing of VC3/ VC12). The trail reconfiguration functions are activated via the trail pop-up menu in the Find Trail window.
Reallocating capacity in VC4 layer trails
The furnishing of VC12 capacities in a VC4 server trail can be reallocated, to free up available VC3 capacity. In the VC4 signal, the individual VC12 time slots are moved to a sequence of nicely arranged VC12 time slots, so that as much space as possible in the VC4 trail is left to VC3 time slots.
Note: This grooming function will generally affect traffic since VC12 traffic is
moved from one time slot to another.
MA334 Rev. A1
31
Trail surveillance
As mentioned in Indicating alarms on page 15, the network can be monitored for alarms that affect trails. This is done by the trail surveillance, which emits alarms for the trails and also changes the information in the network database about the operational state of the trail (the operational state information reflects the trails ability to provide service): A set of alarms for each termination point in the network elements are monitored. Based on these alarms the operational state of the corresponding termination points in the network database is determined. Changes in operational state are propagated to all objects within the network database which are serviced directly or indirectly by those termination points. Alarms are emitted for trails and connections that fail.
Non-intrusive monitoring of VC4 layer trails
The non-intrusive monitoring of a trail segment, mentioned above in Monitoring trail segments non-intrusively on page 23, is set up graphically in the trail view. The monitored data flows are indicated by the use of labels attached to the termination point icons. These labels are also shown in the performance report.
32
MA334 Rev. A1
Inspecting trail trace identifiers
The values of the trail trace identifiers for a specific trail and the validation results in the trails monitored termination points can be inspected in the trail view
and in the more detailed view of individual matrix connections.
MA334 Rev. A1
33
Switching traffic
The switch status of the traffic flow in a protected trail can be inspected and changed in the trail view.
You can use either manual or forced switching to change the active route of the trail.
34
MA334 Rev. A1
2.7.4
Inspecting the Network Database

At each network level, you can inspect the configuration of the network model in matrix views and link views. The matrix view shows the internal connections in the matrix (representing, for example, cross connections in a network element or fibre interconnections in a manhole). The link view shows the link connections in the link (representing time slots in a cable).
Looking at the contents of matrices and links
MA334 Rev. A1
35
Looking at a specific connection
In the matrix view, it can be difficult to see the details of a specific connection (especially a protected connection consisting of several legs). Via the pop-up menu in matrix view, you can therefore open a separate window with a closeup of the selected connection. The figure shows how a protected connection is shown in the matrix view and in the detailed connection view.
2.7.5
Representing Foreign Equipment in the Network Model

If your network is connected to equipment which is not managed directly in the current network model, but which is part of the trails in the managed network, you can let such foreign equipment be represented in the network model by an external matrix. We distinguish between two types of external matrix: a flexible external matrix and an inflexible external matrix. The flexible external matrix is used to represent equipment which you do not manage directly as part of the current network, but which you do, nevertheless, have some control over (for example, one of your own networks). The inflexible external matrix is used to represent equipment which you do not have any control over and of which you can therefore only show the parts that are known to you (for example, the connection points to a specific line leased from another supplier).
Foreign equipment represented by an external matrix
Managing external matrices
An external matrix can be considered as a black box, where only the different interfaces of the external matrix to which the managed network can be connected, as well as the internal connections between some of the interfaces, are stored in the network database. During trail setup, connection points and internal connections are created automatically in the external matrix to support any requested trail routes. To make the necessary changes in the foreign equipment to support these requirements, you can use the matrix view to inspect the configuration of the external matrix. However, when the external matrix represents leased lines, it is important that the external matrix is allowed to contain only the capacity that you have access
36
MA334 Rev. A1
to in the other suppliers network. In that case, you use the matrix view to make the external matrix inflexible and to delete all non-supported connections.
MA334 Rev. A1
37
38
MA334 Rev. A1
3 Tellabs 6300 Manager as a Structure of Licenses
Tellabs 6300 Manager as a Structure of Licenses

Tellabs 6300 manager is sold as a series of licenses: a core license for the server, a number of user licenses, and licenses for the required management functionalities. This chapter contains a brief description of the different types of licenses. A core license is required for each server. The core license does not include any user licenses; these will have to be purchased separately. There are two types of user licenses: Configured user licenses, which determine the number of users (that is, operator terminals) that can be attached to the system. Concurrent user licenses, which determine how many of the configured users that can be active on the server at any given time. The number of concurrent user licenses will be less than or equal to the number of configured user licenses.
Overview
Server (core) license
User licenses
Management functionality licenses
There are three levels of management functionality that can be licensed, depending on your requirements: Element management functionality, which provides element management of the individual network elements in the network. Typical functionalities are configuration, alarm handling and collection of performance data. Basic network management functionality, which provides network management on top of the element management. The focus is on trails (end-toend connctions) rather than on individual network elements and network layers (path layers) are introduced. Enhanced management functionality, which provides such extra functionalities as grooming of trails and the use of the Connector.
Note: Licenses for basic management include element management function-
ality, and licenses for enhanced management include both basic management and element management functionality.
MA334 Rev. A1
39
3 Tellabs 6300 Manager as a Structure of Licenses
40
MA334 Rev. A1
4 Connecting to Other Systems
Connecting to Other Systems

Instead of developing a fully customized, proprietary element access application for a 3rd party network element, Tellabs 6300 manager is connected to the other suppliers own element management system. This leaves equipment near management of duplicated modules, synchronisation etc. to the other vendors element manager, while Tellabs 6300 manager focuses on alarms, traffic flow configuration, and performance data Letting the other vendors element manager act as mediating device, reduces the dependency of specific versions of embedded software in the managed network element, and often allows implementation of a near-standard interconnection between the management systems.
Managing 3rd party network elements
SNMP interface
An SNMP Element Access is available for management of the data communications network of routers, bridges, modems etc., which is used to connect the management system with remote users, network elements, and inferior/ peer/superior management systems. The SNMP management module supports SNMP Traps, which are mapped into standardised OSI format alarms. These can be handled, logged etc. like alarms from any other management function in the system.
General ASCII interface
Many older systems and PDH systems provide at best an ASCII-coded bit stream on an administrative port. Such equipment can easily be integrated under Tellabs 6300 manager by installation of the Graphical ASCII Toolkit. A dedicated toolkit allows the management module to be set up to support both alarms, configuration, and supervision of such legacy equipment. The Graphical ASCII Toolkit parses the protocol, decodes the message set, and generally provides the mediation function between the managed network elements and Tellabs 6300 manager. A special implementation of the Graphical ASCII Toolkit is support for the TL-1 message set, often seen on equipment produced in USA. In many cases, the network elements/EMSs are not able to support a robust suite of TMN management functions. In many cases, Tellabs 6300 managers element management capabilities depend on the capabilities of the managed network elements to support specific management functions.
Integrating with other management systems
A northbound XML interface is available for integration of Tellabs 6300 manager with umbrella management systems (UMS). The interface allows: Real time forwarding and synchronization Provisioning of circuits Upload of network topology Monitoring of events for topology and circuit changes Monitoring of alarms. Using the XML interface requires an understanding of both XML coding language and the Tellabs 6300 network database information model, as well as general knowledge about TeMIP data representation.
MA334 Rev. A1
41
4 Connecting to Other Systems
42
MA334 Rev. A1
Part 2 The Management Platform
Part 2
The Management Platform
5 The Platform of Tellabs 6300 Manager on page 45
MA334 Rev. A1
43
Part 2 The Management Platform
44
MA334 Rev. A1
The Platform of Tellabs 6300 Manager

This chapter is an introduction to the most important features of the platform of Tellabs 6300 manager.
Overview
5.1
The Main Structure of a Tellabs 6300 Manager System

The figure outlines the main components of a Tellabs 6300 manager system and their interconnections.
Overview of main components
Computer system
The computer system contains computer hardware and software. Among the hardware units are the computers themselves, the disk storage, the tape storage, and various communication devices. The software consists of Tellabs 6300 manager and standard software products controlling the computer, the databases, and communication with external units. The Tellabs 6300 manager software is run on a central Alpha server, while the users access to the system is provided by a number of Windows 2000 PCs running Tellabs 6300 manager client software and X Windows. The Tru64 UNIXbased HP OpenView TeMIP has been chosen as platform to ensure that Tellabs 6300 manager is a scalable multi-user system with standardized alarm handling and with the ability for managing multi-vendor telecommunications equipment.
Data communications network
The data communications network (also known as DCN) transports the management information from the computer system to the network elements in the telecommunications network and vice versa. The DCN consists of different types of connections: embedded connections (the management information is transported within the telecommunications signal) and connections between the computer system and a network element (NE). The latter type of connections may be based on direct (point-to-point) connections, local area networks, leased lines, or some other media.
MA334 Rev. A1
45
The data communications networks are continuously monitored, and alarms are generated if errors or disturbances are detected.
Connections to multivendor equipment
Management of telecommunications equipment from other suppliers is done by letting Tellabs 6300 manager connect to the other suppliers element manager. This way, management of the network element itself is left to the other suppliers software while Tellabs 6300 manager focuses on management of alarms, traffic flow and performance data. Similarly, Tellabs 6300 manager can connect upwards to an over-all management system from another supplier.
Tellabs 6300 manager self-management
The hardware, software and data communication are represented in the Tellabs 6300 manager user interface in the same way as the telecommunications equipment; that is, as icons, lines etc. You can therefore manage the Tellabs 6300 manager system itself in exactly the same way as managing the network elements. Key aspects of the computer system such as free disk storage capacity and communication with external units are monitored. Alarms will be generated if disturbances or errors are detected.
5.2
The System Architecture

The Tellabs 6300 manager system can be built (that is, configured) in many different ways. This flexibility is one of its main features. In deciding how to configure your management system, various factors need to be taken into consideration. For example: The number of network elements to be managed by the system The number of alarms that can be expected to be received from the network elements. The number of network operators employed to manage the traffic, and the geographical location of the operators. The expected future development of the system. Depending on these factors, the Tellabs 6300 manager system can be set up either as a stand-alone system with only one server (for management of smaller networks) or as a distributed system with several servers (for management of larger, expanding networks).
Factors to consider
5.2.1
Stand-Alone (Single-Server) Systems

A stand-alone Tellabs 6300 manager management system consists of a single Alpha computer on which the software is installed. This computer supplies all processing power for the server side of the management system. A number of Windows 2000 PCs for the network operators are connected to this server, either locally or remotely (that is, via a wide area network). The PCs have the Tellabs 6300 manager client software installed. A stand-alone system would probably be relevant to manage telecommunications networks where network operators are on the same site (geographical location) as the central network management centre.
A stand-alone system
Choosing a stand-alone system
46
MA334 Rev. A1
5.2.2
Distributed (Multi-Server) Systems

In a stand-alone system with remote operators the data traffic can be enormous and greatly reduce the responsiveness of the system. Most data is presented graphically in Tellabs 6300 manager, and graphical displays demand large data files. A distributed Tellabs 6300 manager system places servers at each location. Besides reducing response time, this type of system architecture does, however, also enable distributed storage of data, making each server responsible for the data from part of the managed network.
A distributed system
System architecture of a distributed system
A distributed Tellabs 6300 manager management system consists of a number of Alpha computer systems linked together via a data communications network. One server (the central server) is placed in the central management centre and can, if necessary, manage the entire telecommunications network. The other servers are either used for communication with various parts of the managed network (AM servers) or used to provide the remote PCs with their user interface (PM servers)
Directors
The servers in a Tellabs 6300 manager system (that is, the computers running TeMIP) are known as directors. Each director is given its own unique name, and is made responsible for a number of network elements in the telecommunications network (usually equipment in a specific region). Such a director is known as the managing director for these network elements. Information
MA334 Rev. A1
47
about the network elements is stored in the managing directors database and can then be shared via the TeMIP Name Service.
TeMIP Name Service
The TeMIP Name Service (TNS) makes a distributed system transparent; that is, it makes it easier and faster to find information about any of the registered entities in the network from anywhere in the system. The information about a specific network element is stored its managing director, but each director contains a so-called replica database with the addresses of each registered entity in the whole managed network. This means that when a director requires information about a specific entity that is not managed by the director itself, it does not have to contact a central server to get the address but can locate the address of the entity in its own replica database and then contact the relevant managing director directly.
DCN
The data communications network (DCN) between management system and network elements consists of various types of equipment: computers, PCs, routers, and modems, which are connected together either via electrical/optical cables or via Ethernet cables. Each component in the DCN is in some way responsible for transferring management data in the network. The use of dedicated servers means that a distributed Tellabs 6300 manager system can easily be scaled to cope with any new requirements from a growing managed network: New PM servers can be added to cope with increased demands from network operators New AM servers can be added to cope in managing new network elements New servers can be added to the Central Server to cope with increased demands on the Central Network Management Centre.
A scalable system
5.2.3
Availability
Using Clusters to Improve Availability

In the telecommunications world, downtime often results in service interruption, which besides being expensive, can reduce an operators competitiveness. In the open, liberalized market of today, this can be catastrophic. It is important to investigate the factors affecting a systems availability, that is the proportion of time that a system can be used for productive work. The availability of a system is not dependent upon whether it is configured as a stand-alone or as a distributed system. The availability is dependent, among other factors, on the way in which the computer system hardware is configured. One way of improving the availability of all Tellabs 6300 manager systems is by using clusters.
48
MA334 Rev. A1
Using clusters
A cluster is a group of two or more interconnected computers, which are on the same site, the same LAN and the same SCSI bus. The computers in a cluster share data, thereby safeguarding it against any kind of computer failure. It is normally only central servers and AM servers that are made as clusters.
The computers in a cluster can share the data either through mirroring of the disks or through the use of a redundant array of independent disks (a socalled RAID system).
Mirrored disks
A cluster can share two disks that are exact copies of one another (mirror images). Data stored in disk storage equipment A and is automatically copied over to B. This means that if A fails, B can immediately take over As functions.
MA334 Rev. A1
49
Redundant array of independent disks
Data storage in a redundant array of, for example, four independent disks means that independent data is stored on disks A, B and C, whereas disk D contains all the data from A, B and C. This way, if a disk fails, for example A, disk A can be replaced by a new one, and the information on the original disk A can be recovered by comparing data on disk D with the data on both B and C.
5.2.4
Using Remote Standby Systems to Improve Availability

The use of a separate management center means having a complete remote standby system for your production system. Via a 2 Mbit/s line, a backup is transferred from the production system to the standby system at a programmable time interval (normally once every 24 hours). The systems may be placed physically very far apart.
Separate management center
At any time (except while the backup is taking place) the roles of the two systems can be switched manually by the system administrator of the standby system. The use of advanced Site Synchronization software ensures stability and fast recovery in this switch-over process. The special advantage of a remote standby system is that it allows one of the systems to be taken down for service, upgrades, expansion etc. while the other system is managing the network.
50
MA334 Rev. A1
5.3
Configuration and Installation of the System

To ensure that you are able to implement the use of Tellabs 6300 manager as your network management system as fast as possible, Tellabs Denmarks Systems Integration department offers to control and manage the entire project. That is, Systems Integration helps you with configuration, delivery, installation, commissioning, training and subsequent support.
Help from Systems Integration
This will give you a fully functional, customized, ready-to-use management system.
Systems Integration services
Tellabs Denmarks Systems Integration department provides the following services: Planning support, including: Setup of Tellabs 6300 manager test systems Technical proposals, including system configurations, sizing and estimates for customizations. Overall technical management of the project Paste together of Tellabs Denmarks products with 3. party hardware and software Migration of data between platforms Support, including: Upgrading of software Maintenance of database.
MA334 Rev. A1
51
5.4
System Administration
The design of Tellabs 6300 manager allows the system to run practically unattended, so the tasks of the system administrator are limited to those of daily management: Managing system security and user accounts Archiving alarms and performance data Managing back-ups (restoring lost user files, checking the daily back-up, and managing tape media) Starting and shutting down the system Keeping an eye on the system load Upgrading software Recognizing system trouble, if any, and calling for service.
The system administrators tasks
5.4.1
Introduction
Management of System Security

The management of system security is part of Tellabs 6300 managers TeMIP core system. The security facilities are flexible and can be adjusted to meet the needs of your organization. The security policy of Tellabs 6300 manager is: A number of people must be authorized to perform a variety of tasks within the system. Users must be allowed to perform only the tasks that are relevant for their jobs. Unauthorized persons must not be able to log in to the system.
Security policy
Security mechanisms
The following basic security mechanisms are used to implement the security policy of the Tellabs 6300 manager system: The password check ensures that only authorized personnel can log in to the system. The user profile facility allows users of the system to be divided into groups with different access rights. In this way network monitoring tasks can be separated from the tasks of network planning and administration and from the tasks related to maintaining the hardware and software of the Tellabs 6300 manager system. The contents and number of these profiles may be adapted to the needs of each customer. See a description of the default user profiles in Section 5.4.2. It is possible to log operations performed in the system.
Note: The access to various functions is adjusted to the user profile of the in-
dividual user.
Session manager
The session manager establishes and manages user sessions on the UNIX server host. The session manager is responsible for starting and stopping Tellabs 6300 manager GUIs and the PC application interfacing to the UNIX server.
52
MA334 Rev. A1
A user session is protected by a login mechanism, which validates the users right to access the system. After the user is validated, he/she may run applications against the server. The session manager controls processes while the session is established, and removes processes when the session is terminated.
5.4.2
Introduction
Default User Profiles

Tellabs 6300 manager contains the pre-defined user profiles described in this section. Each of these default profiles can be modified and more can be added in the overall integration project, to fit your companys network, system architecture and organization. A guest has read-only access to the Tellabs 6300 manager system and cannot perform any operations. A network operator is responsible for administrating and supervising the managed network. That is: Add new network elements to the system. This includes configuring the network elements and setting up the data communications network (DCN). Define the network operators field of responsibility, that is divide the composite supervision task into tasks of appropriate size. Set up the performance data collection, if available. Restructure the entire representation of the managed network, if expansion on top of expansion has made the current representation obsolete. Monitoring the alarm activity Keeping up to date with the performance of the managed equipment Taking action to restore traffic in case of errors, disturbances, or degradation of transmission quality.
The guest
The network operator
The system manager
A system manager or system administrator is responsible for the hardware and software of the Tellabs 6300 manager system, including archiving of alarm and performance data, back-up, user administration, software upgrading, and several other tasks (see The system administrators tasks on page 52).
MA334 Rev. A1
53
54
MA334 Rev. A1
Index
Index A
Advantages 8 Alarms 15 affecting trails 16 filtering 16 filtering criteria 16 indicating 15 information about 15 saving information 17 trail surveillance 32 Architecture of system 46 ASCII interface 41 Availability 48
F
Filtering of alarms 16 filtering criteria 16 Find Trail function 29
G
General features 11 Grooming VC4 layer trails 31 Guest 53
I
Installing the system 51 ITU-T standards X.721 15, 23 X.733 15 X.734 23 X.735 15, 23
C
Clusters use of 49 Command line interface 11 Configuration 7 Configuring the system 51 Connecting to other systems 41 Connection view of network model 36 Cost parameters in route calculation 27 Cross connections in network elements 20
L
Licenses 39 Link view of network model 35
M
Management of system 46 Manuals 8 Matrix view of network model 35 Mirrored disks 49 Monitoring non-intrusive 32 Multiple servers 11 Multiple users 11 Multi-vendor equipment 46
D
Data about events logging 23 Data about performance collecting 22 monitoring 23 Data communications network 45, 48 Database for network traffic management 24 DCN 45, 48 Directors 47 Disks independent in array 50 mirrored 49 Distributed system 47 Domain hierarchy navigating in 12
N
Navigating in domain hierarchy 12 Network bandwidth layers 24 foreign equipment 36 model 23 representation 12 structure 12 synchronization 18 timing view 18 Network database 24 inspecting 35 Network editor 13 working in 14
55
E
Event data logging 23 ExternalMatrices 36
MA334 Rev. A1
Index
Network elements cross connections in 20 equipment view 19 management of 19 synchronization 21 traffic view 20 Network operator 53 Network traffic management 23 creating trails 25 database 24 layers 24 Non-intrusive monitoring 32
P
Performance data collecting 22 monitoring 23 Platform 45
R
Redundant array of independent disks 50 Routes calculating 27 creating manually 28 inspecting 31
S
Scalability 48 Security 52 Separate management center 50 Server directors 47 Session manager 52 Single-server 11 SNMP interface 41 Stand-alone system 46 Standards X.721 15, 23 X.733 15 X.734 23 X.735 15, 23 Standby system 50 Structure 45 Synchronization in a network element 21 in the network 18 System administrator 52, 53 System manager 53 Systems Integration 51
TeMIP Name Service 48 Text-based user interface 11 Third party network elements managing 41 Timing view 18 TMN 7 Traffic switching 34 Traffic management 23 Traffic view of network elements 20 Trail trace identifiers 28, 33 Trails affected by alarms 16 creating 25 creating routes manually 28 finding 29 grooming 31 handling 29 inspecting 29 non-intrusive monitoring 32 partial protection 28 reallocating capacity 31 reconfiguring 31 route inspection 31 surveillance for alarms 32 switching traffic 34 trail trace identifiers 28, 33 using automatic route calculation 27
U
UNIX 45 User interface graphical 11 text-based 11 User profiles 53 User workstations 8
W
Workstations 8
X
X.721 standard X.733 standard X.734 standard X.735 standard 15, 23 15 23 15, 23
T
Telecommunications management network 7 TeMIP 45
56 MA334 Rev. A1

Ma334 A1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ma334 A1

Uploaded by

Copyright:

Available Formats

Technical Documentation

Tellabs 6300 Managed Transport System

Copyright 2002 Tellabs. All rights reserved.

Tellabs 6300 network manager Description of Management Application and Platform

Tellabs 6300 network manager Description of Management Application and Platform

This document has changed as follows:

Nov. 30, 2002

Tellabs 6300 network manager Description of Management Application and Platform

Tellabs 6300 network manager Description of Management Application and Platform

The Management Application

Tellabs 6300 Manager as a Structure of Licenses Connecting to Other Systems

The Management Platform

Tellabs 6300 network manager Description of Management Application and Platform

Tellabs 6300 network manager Description of Management Application and Platform

Tellabs 6300 manager

Tellabs 6300 network manager Description of Management Application and Platform

Advantages from the platform of Tellabs 6300 manager

Tellabs 6300 network manager Description of Management Application and Platform

Part 1 The Management Application

The Management Application

Tellabs 6300 network manager Description of Management Application and Platform

Part 1 The Management Application

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Description of Tellabs 6300 Manager

The general features of the graphical user interface

Multiple users possible Single-server or multiple servers possible

Command line interface also available

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Representation of the Network in Tellabs 6300 Manager

Showing the network structure

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Setting up the network model

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Working in the network editor

Create the network object in the appropriate tree.

Transfer the network object to the domain map.

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Indication and Presentation of Alarms

Information about a new alarm

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Trails affected by alarms from network elements

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Viewing Timing in a Network

The information shown

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Management of Network Elements

Inspecting and managing network element configuration

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Setting up a new cross connection

Tellabs 6300 network manager Description of Management Application and Platform

2 Description of Tellabs 6300 Manager

Tellabs 6300 network manager Description of Management Application and Platform