6300 principle of operation

Technical Documentation

Copyright © 2002, 2004-2008 Tellabs. All rights reserved.

Product family Tellabs® 6300 Managed Transport System

Product name Tellabs® 6300 Network Manager

Title Working in Tellabs 6300 Manager Vol. 1: Principles of Operation

Document User’s ManualMA266 / Revision E2

Tellabs® 6300 Network ManagerWorking in Tellabs 6300 Manager Vol. 1: Principles of Operation

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 usethis manual is subject to limitations and restrictions imposed by applicable li-censes and copyright laws. Unauthorized reproduction, modification, distri-bution, display or other use of this manual may result in criminal and civilpenalties.

Trademark Notice The following trademarks and service marks are owned by Tellabs Opera-tions, Inc., or its affiliates in the United States and/or other countries: AUDIOPLUS®, CABLESPAN®, CEC-128™, DYNAMIC SIGNAL TRANSFER™,DXX®, DXX logo®, EC DUO®, ENHANCED AUDIO PLUS®, EX-PRESS/PATH®, FOCUS™, MARTIS®, MARTISDXX®, MARTIS logo®, MAR-TISDXX logo®, METROVANTAGE®, METROWATCH™, NETREACH®,NETWISE®, SCULPTURED SOUND™, TELLABS®, TELLABS and T sym-bol®, T symbol, TELLABS PROPARTNER™, TEL/MAP™, TEL/MOR®, THEWORLD COMMUNICATES THROUGH TELLABS™, TITAN®, VERITY™,YOUR NETWORKING PARTNER®.

Any other company or product names may be trademarks of their respectivecompanies.

2 MA266 • Rev. E2


Revision Information


Revision history This manual has changed as follows:

Rev. Date Description of Changes

A1 Oct. 31, 2002 First revision.

B1 Feb. 27, 2004 • Text and pictures have been updated to reflect feature pack 2.0 of Tellabs 6300 manager.

• Chapter ‘6 Quality of Service and AFC Profiles’ on page 47 has been added.

C1 Oct. 31, 2005 Compared to revision B1 the manual has changed as follows:

• Text and pictures have been updated to reflect feature pack 3.0 of Tellabs 6300 manager.

• A description of the Customer window has been added to ‘4 The Secondary Windows’ on page 25.

• Chapter ‘6 Quality of Service and AFC Profiles’ on page 47 has been revised to reflect the chang-es in Quality of Service window.

• All references to Traffic View have been deleted.

• A description of alarm colors and how to config-ure them has been added.

C2 March 1, 2006 Information about link alarm coloring has been added.

D1 Aug. 28, 2006 Compared to revision C2 the manual has changed as follows:

• Text and pictures have been updated to reflect feature pack 3.0 service pack 1 of Tellabs 6300 manager.

• Updated the procedure to create a new band-width profile. A note about additional CIR bandwidth classes, which are required when upgrading the embedded software of the mod-ules, has been added.

• Added information about 2 new menu items in the Tellabs 6300 Network Manager menu.

• Added a procedure that describes how users change their passwords.

• Added a new section that provides details about the characters that are permitted when provid-ing IDs and labels.

• Added a new procedure that describes how to edit customer IDs and Labels.

MA266 • Rev. E2 3



D2 Dec. 1, 2006 Compared to revision D1 the manual has changed as follows:

• Updated the information for the procedure when the AFC profiles are deployed. The De-ploy Process window appears.

• Some minor technical corrections.

E1 Sept. 1, 2007 Compared to revision D2 the manual has changed as follows:

• Added information about OTN layer.

• Updated the information for the Find Trail win-dow.


E2 Feb. 20, 2008 Compared to revision E1 the manual has changed as follows:

• Updated the procedure to locate specific NE en-tities.


Rev. Date Description of Changes

4 MA266 • Rev. E2


Contents

Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction to Tellabs 6300 Manager . . . . . . . . . . . . . . . . . . . . . . 11

2 Representation of Your Network . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.2 The Network Entities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 The Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1 The Main Menus in the Network Management Window . . . . . . . . . . . . 183.2 The Toolbar Buttons in the Network Management Window . . . . . . . . . 203.3 The Work Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

4 The Secondary Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254.1 Network Editor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.2 Alarm Handling Window from the TeMIP Client . . . . . . . . . . . . . . . . . . 274.3 Element Management Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284.4 Find Trail Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294.5 Entity Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.6 Link View and Matrix View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314.7 Customer Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.8 Backup Management Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334.9 Quality of Service Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

5 Basic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.1 Running the GUI Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.2 Creating an LND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385.3 Managing Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415.4 Navigating in a Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.5 Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

6 Quality of Service and AFC Profiles . . . . . . . . . . . . . . . . . . . . . . . . 476.1 The Quality of Service Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476.2 Configuring and Viewing Bandwidth Classes . . . . . . . . . . . . . . . . . . . . 486.3 Configuring and Viewing Queue Scheduling . . . . . . . . . . . . . . . . . . . . 526.4 Configuring and Viewing the IP Priority Map . . . . . . . . . . . . . . . . . . . . 556.5 Configuring and Viewing AFC Profiles . . . . . . . . . . . . . . . . . . . . . . . . . 576.6 Configuring and Viewing Bandwidth Profiles . . . . . . . . . . . . . . . . . . . . 626.7 Comparing and Deploying AFC Tables . . . . . . . . . . . . . . . . . . . . . . . . 64

6.7.1 Comparing the AFC Table with the Table in One or All ETEX 2.x and ETEX 3.x NEs 65

6.7.2 Deploying the AFC Profiles and IP DSCP Mapping into All ETEX NEs 65

6.8 Saving the QoS Parameter Settings . . . . . . . . . . . . . . . . . . . . . . . . . . 66

A Character Restrictions in Text Entries . . . . . . . . . . . . . . . . . . . . . . 67

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

MA266 • Rev. E2 5


Contents

6 MA266 • Rev. E2


Preface

Preface

The purpose of the manual

The manual "Working in Tellabs 6300 Manager" describes the core functional-ity of Tellabs 6300 manager and covers:

• The main graphical user interface of Tellabs 6300 manager and how to op-erate in it. The windows for the more specialised operations (creation and management of trails, for example) are mentioned briefly, with reference to the relevant manuals.

• The elements of the network model and how to create the network view.

• The entity browser, which provides a graphical user interface for working directly with the network model entities as represented by a TeMIP hier-archy.

• Handling of alarms as carried out in the TeMIP Client’s alarm handling windows.

• Changing passwords for users of Tellabs 6300 manager.

We assume that you are familiar with Microsoft® Windows and that youknow how to navigate in a tree structure, how to activate pop-up menus andso on.

Note: The manual has been split up into 5 separate volumes:

• Volume 1 describes the main graphical user interface and the general principles of operation in Tellabs 6300 manager.

• Volume 2 describes how to create the model of your network with the net-work editor. See reference item [1].

• Volume 3 describes how alarms are displayed and handled. See reference item [2].

• Volume 4 describes the windows and functionality of the entity browser. See reference item [3].

• Volume 5 describes those functions of Tellabs 6300 Manager that apply to the management of all network element types. See reference item [4].

The structure of this volume of the manual

This volume is structured as follows:

• ‘1 Introduction to Tellabs 6300 Manager’ on page 11 contains a brief sum-mary of the features of Tellabs 6300 manager.

• ‘2 Representation of Your Network’ on page 13 describes how a network is represented in Tellabs 6300 manager. It introduces the network model, which forms the basis of network management.

• ‘3 The Main Window’ on page 17 describes the main window of Tellabs 6300 manager.

• ‘4 The Secondary Windows’ on page 25 introduces the other (secondary) windows, which are described in more detail in the relevant manuals.

• ‘5 Basic Procedures’ on page 35 describes the basic work procedures in Tellabs 6300 manager. That is, it describes how to start the program, how to create the entity called an LND, which is a requirement before you can start to set up the actual network model, how to navigate in a network, and how to inspect the capacity and timing in the network.

MA266 • Rev. E2 7


Preface

• ‘6 Quality of Service and AFC Profiles’ on page 47 describes how to define the bandwidth classes and AFC profiles used in the management of Ether-net services with Tellabs 6300 manager.

• ‘A Character Restrictions in Text Entries’ on page 67 describes the charac-ters that are permitted when supplying IDs, Labels and text within Tel-labs 6300 manager.

Style conventions The following style conventions are used in the text:

• Italic text

Italics text is used in the following situations:

• File, computer and directory names.

• Commands in normal text.

• Text that is to be replaced with a correct term or expression. This text is normally enclosed in < >.

• Bold text

Bold text is used in the following situations:

• Names of windows displayed on screen

• Names of menu items accessed from the menu bar

• Names of push buttons displayed on screen

• Text typed as an answer to a question displayed on screen

• Monospaced text

Monospaced text is used in the following situations:

• Text to be typed as a command

• Computer dialog issued by software in a command line interface (no graphical interface used)

• [Text] in square brackets

Text in square brackets is used in the following situations:

• [Monospaced] text in square brackets indicates optional items in commands

• [Bold] text in square brackets indicates a function key on the keyboard

• {Text} in braces

Text in braces is used in the following situations:

• Choices in commands. These are normally separated by a vertical line (|).

Abbreviations AFC Assured Forwarding ClassCIR Committed Information Rate (bits/s)CTP Connection Termination PointGUI Graphical User InterfaceLC Link ConnectionLND Layer Network DomainMC Matrix ConnectionNE Network ElementPDH Plesiosynchronous Digital HierarchyPIR Peak Information Rate (bits/s)

8 MA266 • Rev. E2


Preface

QoS Quality of ServiceQSP Queue Scheduling ProfileSDH Synchronous Digital HierarchyTTP Trail Termination Point

References [1] MA267, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Working in Tellabs 6300 Manager, Vol.2: Using the Net-work Editor, User’s Manual

[2] MA268, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Working in Tellabs 6300 Manager, Vol.3: HandlingAlarms, User’s Manual

[3] MA269, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Working in Tellabs 6300 Manager, Vol.4: Using the EntityBrowser, User’s Manual

[4] MA335, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Working in Tellabs 6300 Manager Vol.5: Using the CoreFunctions of Element Management, User's Manual

[5] MA333, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, System Administration Guide and Reference for FP3.0.x

[6] MA345, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Managing ETEX, User’s Manual

[7] MA360, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Managing SDH and Ethernet Trails, User’s Manual

MA266 • Rev. E2 9


Preface

10 MA266 • Rev. E2


1 Introduction to Tellabs 6300 Manager


Overview Tellabs 6300 manager is a complete element manager and network manager,which allows you to survey both equipment and traffic, to set up and recon-figure end-to-end connections, to manage equipment, and to collect perfor-mance data for the traffic.

Alarm indication and presentation

Alarms received from the equipment are indicated in the GUI by color chang-es of the icons representing the equipment, where the color is determined bythe severity of the alarm. The change of color happens in every domain andwindow where the network element’s icon is shown.

If an alarm affects traffic in the network, alarms are generated for the end-to-end connections (trails). The trail alarm is indicated with the alarm severitycolor in the main window for trail management (the Find Trail window) aswell as with a sequence of colored triangels along the link in the Network Man-agement window. In case of more alarms in a group link, the color indicatingthe most severe alarm is displayed, while a mouse-over shows the alarm stateof all links.

TeMIP’s alarm handling windows are used to show the detailed informationabout each alarm. The information includes such data as the probable cause ofthe alarm, the name of the object that generated the alarm, when the alarmwas generated, and when it was received by Tellabs 6300 manager.

Element management Configuration and management of individual network elements is performedin a number of sub windows, each window dedicated to a specific task (for ex-ample, cross connections, module specification, and synchronization).

Traffic management End-to-end connections (trails) are set up in the GUI in one simple operation,where you select the two end points and then specify the trail’s parameters(parameters such as protection, signal structure, customer, and subroutes).Tellabs 6300 manager has very powerful trail management features for settingup and configuring traffic.

The network traffic management is based on a powerful network model con-cept. The model is not concerned with the specific attributes of the network el-ements, but mainly represents the network’s end-to-end connections (trails)and capacity at the different bandwidth layers. Each network element is rep-resented by a matrix that contains information about termination points andinternal connections. The model also registers the time slots (link connections)between the network elements that are used by the trails.

Network editing The network view is created and edited in a network editor GUI, in which youcan create new network objects and drag-and-drop them to their position inthe domain.

Timing view Tellabs 6300 manager provides a graphical view of the clock distribution andsynchronization between network elements in the network.

The information provided by timing view can be used to discover timingloops and to improve the topology of the network.

Performance monitoring The collection of performance data can be used to monitor and document thequality of supplied services.

MA266 • Rev. E2 11



All kinds of performance data can be collected, including the standard SDHperformance counters supported in the managed SDH network elements (fol-lowing the ITU G.826 standard). The performance data is represented in re-port form by a performance report generator.

The performance data can be correlated from the network elements to thetrails. The periodic performance management reports are generated per net-work element or per trail.

12 MA266 • Rev. E2


2 Representation of Your Network


Overview This topic describes how the equipment in your network is represented in theTellabs 6300 manager windows.

• ‘2.1 Introduction’ on page 13

• ‘2.2 The Network Entities’ on page 15

2.1 Introduction

Network representation The figure shows an example of a network representation in the main windowof the Tellabs 6300 manager’s graphical user interface. This is the window inwhich the managed equipment is represented and operated on, and fromwhich the main functions of the system are initiated.

Different levels of detail The network representation as such is shown at different levels of detail. Themain window of Tellabs 6300 manager shows the topology of the network(that is, which elements the network consists of, how the elements are con-nected, and how they have been grouped in domains). Other windows showthe details of the individual elements (for example, the contents of a specificnetwork element (NE)). This allows operations - for instance inspection andconfiguration - to be performed on the whole network or on parts of it.

MA266 • Rev. E2 13



How the managed equipment is represented

The different types of equipment in a network are represented in the follow-ing way:

• Network elements

In Tellabs 6300 manager the network elements (NEs) are represented byNE objects and NE matrix objects. (The NE matrix objects are relevant inconnection with trail management, and with one matrix representation pernetwork traffic layer). However, to make a clear distinction between thephysical NEs and their representation in the network model, the term "NE"always refers to the physical network element and the term "NE matrix" isused in general for any NE representation, even when the representation"only" consists of element management. Via an NE matrix you can there-fore access and manage both the physical NE itself and the correspondingnetwork database representation.

• Cables

Cables are represented by links.

• Cable interconnections

Interconnections between fibres from different cables (that is, manholes ordistribution frames) are represented by fibre matrices at the physical layer.

• "Foreign" equipment

Equipment which is not managed directly in the current network model,but which is connected to elements inside the managed network (andthereby is part of the trails in the managed network), is represented by ex-ternal matrices.

Entities and child entities The elements of a network representation are often referred to by the generalterms ‘entities’ and ’child entities’.

The parts constituting an entity, such as the traffic aspects of the channels ofan NE, are referred to as ‘child entities’. Child entities cannot exist alone butare always bound together with the entity of which they are parts. For in-stance, it would be meaningless to represent the traffic aspect of an aggregateVC-4 channel detached from an NE.

Note: When an entity is not a child entity, it is sometimes called a ‘global en-tity’ to explicitly distinguish it from child entities.

Logical grouping in a domain hierarchy

Tellabs 6300 manager has been designed to manage transmission networks ofmajor geographical areas. Thousands of NEs - that is multiplexers, cross con-nects, and regenerators - may be controlled and monitored by the system.

The elements of the network representation can therefore be grouped in a log-ical, hierarchical structure in so-called ‘domains’. A domain can, for example,represent a geographical area and contain all equipment placed in that area.We recommend that you create a hierarchy of domains and subdomains.

You can easily inspect the contents of a specific domain by opening the do-main. You open the top domain either by selecting it in the Domain: field orvia the domain browser. You open a subdomain by double-clicking on theicon representing it.

14 MA266 • Rev. E2



2.2 The Network Entities

Domains representing traffic layers

To be able to represent the different aspects of the network in management ofthe traffic, the network model is organised according to the individual net-work traffic layers (physical, OTS, OMS, OCH, OTH, RS, MS, VC-4, VC-3, VC-12 and data). Each of these traffic layer domains contains representations ofthe relevant parts of the network (that is, those parts of the network that carrytraffic at that layer).

The basis for each layer is a so-called layer network domain (LND), whichcontains the definition of all network entities at that particular layer.

NEs and NE matrices The NE matrix contains connection termination points (CTPs), trail termina-tion points (TTPs) and matrix connections (MCs) based on the correspondingtermination points and the connections between these in the NE. The relevantinformation is uploaded from the physical network element to the NE matrixat the current layer.

To make it easier to manage an NE matrix with a large number of TTPs, it ispossible to group TTPs together in TPPools. The TPPool can be used separate-ly when setting up trails.

If an NE does not have a corresponding NE matrix, the NE itself is shown inthe graphical user interface. In that case, there is no access to NE matrix man-agement.

Fibre matrices The fibre matrix contains matrix connections that model the inflexible inter-connections between pairs of link connections ("fibres") in the links ("cables")terminating in the fibre matrix. The fibre matrix is therefore always inflexible.

The fibre matrix does not contain all of the subparts of an NE matrix describedin ‘NEs and NE matrices’ on page 15. There are no trail termination points orTPPools in a fibre matrix, as there is no termination of traffic in a fibre inter-connection. The subparts in a fibre matrix must be defined manually since thefibre matrix is not a manageable object.

Note: Because fibre matrices represent manholes, they only appear at thephysical layer.

MA266 • Rev. E2 15



External matrices We distinguish between two types of external matrix: a flexible external matrixand an inflexible external matrix. The flexible external matrix represents equip-ment which you do not manage directly as part of the current network, butwhich you do, nevertheless, have some control over (for example, one of yourown networks). The inflexible external matrix represents equipment whichyou do not have any control over and of which you can therefore only showthe parts that are known to you (for example, specific lines leased from anoth-er supplier). An inflexible external matrix generally represents a whole sub-network owned by another supplier.

The model of an external matrix is very similar to an NE matrix and containsall of the subparts described in ‘NEs and NE matrices’ on page 15 except TP-Pools. The subparts in an external matrix are either defined manually on thephysical layer or are created automatically by the system in connection withthe creation of trails.

Links A link is a bundle of link connections (LCs) which are a set of timeslots trans-mitted between matrices. LCs representing, for instance, timeslots carried bysea cables and satellites, could be contained in separate links. In the networkmodel, all layers except the physical layer require that all LCs in a specific linkare carried by the same server trail.

The links used to supply Ethernet services, are known as "packet links".

External links An external link and its LCs represent an unknown network that connects twoof our networks. Unlike ordinary LCs, external LCs do not have any servertrails and must be created manually.

Trails A trail is a connection between two trail termination points (TTPs). A trail isthe object that carries payload traffic and also can act like a server for link con-nections (LCs) at another layer.

Attributes of network entities

The features and properties of an entity - such as configuration parametersand idenfication of an NE matrix - are called attributes. Attributes describe thesettings of an entity and its modes and levels of working.

An attribute can be attached either to a global entity or to a child entity - neverto both of them. Attributes attached to a global entity - such as an LND - nor-mally describe information relating to the entity as a whole (the signal type ofan LND is an example of such an attribute). Attributes attached to a child en-tity describe details relating to that specific child entity, for instance the direc-tionality of a matrix connection.

Entity names When you register an entity, it must be given a unique, official name that fol-lows the naming standards. However, as the official name may not be veryuseful for easy identification of the icon in the graphic representation, you candefine a nick name for the entity, which is used only in connection with theicon.

16 MA266 • Rev. E2


3 The Main Window

3 The Main Window

The work environment for network management

The figure shows the main window of Tellabs 6300 manager’s graphical userinterface: the Network Management window. In the Network Management win-dow the managed equipment is represented and operated on, and the mainfunctions of the system are initiated. It is from this window that you open allof the other windows available for configuration of network elements, set-upof trails, and so on (the network editor can, however, also be activated on itsown).

The Network Management window itself consists of the following areas:

• A menu bar, which contains menus for general functionalities: such as navigation in the domain hierarchy and printing of the currently dis-played domain.

• A toolbar, which provides shortcuts for commonly used menu functions.

• Display specification fields, with which you can specify the domain and the network layer that you want displayed.

• The work area which contains the actual graphical display of your net-work. The pop-up menus available for the various icons allow you to acti-vate the network management functions.

• A status line, which registers the name of the currently selected entity, in-dicates alarms, and so on.

MA266 • Rev. E2 17


3 The Main Window

3.1 The Main Menus in the Network Management Window

File menu The Network Management window’s File menu contains the following menuitems:

Operations menu The Network Management window’s Operation menu contains the followingmenu items:

Navigation menu The Network Management window’s Navigation menu contains the followingmenu items:

Menu item Description

Refresh Refreshes the view of the domain.

Print... Opens the Print window. See ‘5.5 Printing’ on page 45.

Page Setup... Opens the Page Setup window. See ‘5.5 Printing’ on page 45.

Exit Closes the Network Management window.


Find Entity... Opens the Find Entity window. See the descrip-tion in ‘To locate a specific entity’ on page 44.

Find Trail... Opens the Find Trail window. See ‘4.4 Find Trail Window’ on page 29.

Trail History... Opens the Trail History window. See [7].

Network Editor... Opens the Network Editor window. See ‘4.1 Network Editor Window’ on page 26.

Entity Browser... Opens the Entity View window. See ‘4.5 Entity Browser’ on page 30.

Customer... Opens the Customer window. See ‘4.7 Customer Window’ on page 33.

Performance Graph... Opens the Performance Graph window. See [6].

Backup Management... Opens the Backup Management... window. See ‘4.8 Backup Management Window’ on page 33.

Quality of Service... Opens the Quality of Service window. See ‘6.1 The Quality of Service Window’ on page 47.


Domain Browser Opens the Domain Browser window. See the de-scription in ‘5.4 Navigating in a Network’ on page 43.

18 MA266 • Rev. E2


3 The Main Window

Options menu The Network Management window’s Options menu contains the followingmenu items:

Help menu The Network Management window’s Help menu contains the following menuitems:

Reset Domain Hierarchy Updates the domain structure. If any changes have been made to the domain structure in the network editor, this menu item can be used to read in the new structure.

Back Opens the domain that is listed immediately be-low the current domain in the domain history list.

Forward Opens the domain that is listed immediately above the current domain in the domain history list.

Top Opens the domain that is currently specified as the top domain.

List of domains Contains a list of the domains that have previous-ly been open within the same "session".



Show Link Names Displays the link names in the currently open do-main.

Show Link Capacity Displays the capacity of the currently shown links.

Show Alarm Status Enables the display of alarm colors.

Show External Links Displays any existing external links. External links represent foreign networks that connect our networks.

Show Packet Links Displays the packet links available for Ethernet services.

Set Default Top Domain Sets the currently displayed domain as your de-fault top domain.

Show Timing Displays the timing view of the currently open domain.

Timing Options Opens the Timing Options window, which allows you to disable and enable the display of one or more of the different types of timing links.

Menu Item Description

About Network Manage-ment

Displays server/client information about Tellabs 6300 manager.

MA266 • Rev. E2 19


3 The Main Window

3.2 The Toolbar Buttons in the Network Management Window

Toolbar buttons in the Network Management window

The Network Management window contains the following sets of buttons,which, for the most part, correspond to menu items in the main menus:

The table describes the individual buttons.

No Name Description

1 Previous domain Opens the domain that is listed immediately be-low the current domain in the domain history list.Corresponds to the menu item Navigation → Back.

2 Next domain Opens the domain that is listed immediately above the current domain in the domain history list.Corresponds to the menu item Navigation → For-ward.

3 Stop process Interrupts the current process (timing view dis-play, link capacity display, or highlighting of trail).

4 Top domain Opens the domain that is currently specified as the top domain.Corresponds to the menu item Navigation → Top.

5 Refresh screen Refreshes the view of the domain.Corresponds to the menu item File → Refresh.

6 Zoom in Enlarges the view of the domain.

7 Zoom out Diminishes the view of the domain.

8 Find Entity Opens the Find Entity window. See the descrip-tion in ‘To locate a specific entity’ on page 44.Corresponds to the menu item Operations → Find Entity.

9 Domain Tree Browser

Opens the Domain Browser window. See the de-scription in ‘5.4 Navigating in a Network’ on page 43.Corresponds to the menu item Navigation → Do-main Browser.

10 Find Trail Opens the Find Trail window. See ‘4.4 Find Trail Window’ on page 29.Corresponds to the menu item Operations → Find Trail.

20 MA266 • Rev. E2


3 The Main Window

3.3 The Work Area

Introduction The work area of the Network Management window is where you view yournetwork and where you manage the network entities (network element man-agement, trail management and so on).

Each entity has a pop-up menu that allows you to manage the entity.

Entity icons The default icons used in Tellabs 6300 manager to represent the various net-work entity types are shown in the table.

Note: If required, you can use other icons for the individual entities. This isdone by specifying the icon in the network editor, as described in [1].

11 Network Editor Opens the Network Editor window. See ‘4.1 Network Editor Window’ on page 26.Corresponds to the menu item Operations → Net-work Editor.

12 Print domain Opens the Print Domain window. See ‘5.5 Printing’ on page 45.Corresponds to the menu item File → Print ....

No Name Description

Icon Description

Represents a subdomain.

Represents an NE and the corresponding NE matrix. Each NE type has a specific icon.

Represents a 6315, ETEX module or an ETEX NE. Background color shows severity of generated alarm.

Represents an NE matrix. This icon is mainly used in the net-work editor and is rarely shown in the Network Management window.

Represents a fibre matrix.

MA266 • Rev. E2 21


3 The Main Window

Pop-up menus The table provides an overview of the contents of the pop-up menus availablein the Network Management window’s work area.

Represents an external matrix.

Represents a link. A link group (that is, two or more links con-necting the same two entities) is represented by a thicker line.

Represents a link group with alarm(s).

Represents a TPPool.

Icon Description

Entity Menu Item Description

NE matrix Trail related items Activates the various functions relat-ed to trail management, as described in [7].

NE management re-lated items

Activates the various functions relat-ed to NE management, as described in the relevant element management manual.

Matrix Directive View Opens the Entity View window with the NE matrix as the specified entity. See ‘4.5 Entity Browser’ on page 30.

NE Directives Opens the Directive View window with the NE matrix’s corresponding NE as the specified entity. See ‘4.5 Entity Browser’ on page 30.

Matrix Directives Opens the Directive View window with the NE matrix as the specified entity. See ‘4.5 Entity Browser’ on page 30.

22 MA266 • Rev. E2


3 The Main Window

External ma-trix

Trail related items Activates the various functions relat-ed to trail management, as described in [7].

Matrix View Opens the Matrix View window, which allows you to inspect the ca-pacity (TPs and MCs) of the external matrix at the current network layer. See ‘4.6 Link View and Matrix View’ on page 31.

Matrix Directives Opens the Directive View window with the external matrix as the speci-fied entity. See ‘4.5 Entity Browser’ on page 30.

Fibre matrix Trail related items Activates the various functions relat-ed to trail management, as described in [7].

Matrix View Opens the Matrix View window, which allows you to inspect the ca-pacity (TPs and MCs) of the fibre matrix at the current network layer. See ‘4.6 Link View and Matrix View’ on page 31.

Matrix Directives Opens the Directive View window with the fibre matrix as the specified entity. See ‘4.5 Entity Browser’ on page 30.

TPPool Trail related items Activates the various functions relat-ed to trail management, as described in [7].

TPPool Directives Opens the Directive View window with the TPPool as the specified en-tity. See ‘4.5 Entity Browser’ on page 30.


MA266 • Rev. E2 23


3 The Main Window

Alarm colors NE and trail alarms can be shown through a coloring of the background be-hind the NE matrix icons and colored triangles on links in the Network Man-agement window. The NE matrix shows the most severe active NE alarm, thelink shows the most severe active alarm of the associated physical or servertrail (depending on the network layer). The coloring of a link group is deter-mined by the most severe alarm among the contained links.

Note: The alarm colors are not shown when colors are used for other purpos-es (for example in timing view).

Link Trail related items Activates the various functions relat-ed to trail management, as described in [7].

Link View Opens the Link View window, which allows you to inspect the capacity (LCs) of the link at the current net-work layer. See ‘4.6 Link View and Matrix View’ on page 31.

Link Directives Opens the Directive View window with the link as the specified entity. See ‘4.5 Entity Browser’ on page 30.

Show Other End If one of the ends of the link is not currently displayed (either because the network in the present domain is larger than the work area or because the end exists in another domain than the currently displayed one), this menu item will transfer you to the other part of the network or to the other domain directly.


24 MA266 • Rev. E2


4 The Secondary Windows


Overview The Network Management window is the "start point" from which you have ac-cess to all of the network management functions of Tellabs 6300 manager (thatis, management of network elements, management of trails, and so on). Thevarious functions are related to special windows that are opened from the Net-work Management window.

Note: The Network Editor window can, however, also be activated on its own.This management function and the related windows are described in a sepa-rate manual (see [1]). However, a brief overview is provided below.

• ‘4.1 Network Editor Window’ on page 26, in which you create and edit the network.

• ‘4.2 Alarm Handling Window from the TeMIP Client’ on page 27

• ‘4.3 Element Management Windows’ on page 28

• ‘4.4 Find Trail Window’ on page 29, which is the main window for trail management.

• ‘4.5 Entity Browser’ on page 30, in which you can work directly on the en-tities in the information model.

• ‘4.6 Link View and Matrix View’ on page 31, in which you can inspect the capacity of the network.

• ‘4.7 Customer Window’ on page 33, in which you create an delete custom-er definitions.

• ‘4.8 Backup Management Window’ on page 33, in which you can config-ure the automatic backup of the NEs.

• ‘4.9 Quality of Service Window’ on page 34, in which you create and edit the the AFC profiles and bandwidth profiles used in trail management.

MA266 • Rev. E2 25



4.1 Network Editor Window

Creating and editing the network

The network view shown in the Network Management window is created andedited in the Network Editor window. This is where you create domains, createNEs and place them in the domains, and create links between the NEs and ma-trices.

See [1] for a detailed description of the Network Editor window.

26 MA266 • Rev. E2



4.2 Alarm Handling Window from the TeMIP Client

Viewing and handling alarms

Alarms are displayed in the windows for alarm handling provided by theTeMIP client. Each alarm is described by a line in the Alarm Handling win-dow, providing such information as the severity of the alarm, the alarm typeand the managed object causing the alarm.

The windows and functionality of alarm handling are described in [2].

MA266 • Rev. E2 27



4.3 Element Management Windows

NE management Configuration of network elements is carried out in a set of windows, whereeach is dedicated to a particular function (for example, specifying which mod-ules the NE contains or setting up cross connections in the NE). The pop-upmenu for NE matrices in the Network Management window contains menuitems for the various NE management functions.

The windows and work procedures related to NE management are describedin separate manuals.

28 MA266 • Rev. E2



4.4 Find Trail Window

Trail management windows

Set-up of trails is performed directly in the Network Management window, us-ing the mouse to specify the trail endpoints. Similarly, many other functionsof trail management are activated via the pop-up menus for the matrices andlinks.

The main window for reconfiguration and inspection of existing trails is, how-ever, the Find Trail window. In this window, you can see a list of existing trails,search for a specific trail, see the trail attributes, and operate on the trails.

Various windows for inspecting and handling a specific trail are opened viathe pop-up menu for the trails in the displayed trail list. Windows and workprocedures related to trail management are described in [7].

MA266 • Rev. E2 29



4.5 Entity Browser

Working in the information model

Direct access to the entity hierarchy is provided by the entity browser (that is,the Entity View and Directive View windows), which allows you to operate di-rectly on the information model. While the Entity View window allows you tonavigate in the hierarchy to locate a specific entity, the Directive View windowallows you to execute an operation for a specific entity.

The windows and functionality of the entity browser are described in [3].

30 MA266 • Rev. E2



4.6 Link View and Matrix View

Inspecting the contents of a link

You can inspect the contents of a specific link in the Link View window, whichis a table listing the link connections in the link (representing time slots in acable) and such information as the server trails related to the link connectionsand various management settings.

The link view contains the following information:

• A menu bar, which contains menu items to activate the column filter and so on.

• A field for selecting a specific link.

• A toolbar, containing buttons that provide shortcuts to various menu items.

• An indication of the link’s end points.

• A table, which contains a list of the link connections in the link and infor-mation concerning each link connection.

• A status line at the bottom, which displays various types of information.

How to use the link view is described in [7].

MA266 • Rev. E2 31



Inspecting the contents of a matrix

You can inspect the contents of a specific external matrix or fibre matrix in theMatrix View window, which contains a graphical illustration of the internalconnections in matrices (representing, for example, cross connections in a net-work element or fibre interconnections in a manhole).

The matrix view contains the following information:

• The CTPs of the matrix, shown as circles in an expansion tree to the left, and the TTPs of the matrix, shown as circles to the right. The lay-out of the tree structure depends on which layer of the matrix is shown in the matrix view, as the structure mirrors the CTP naming.

• The currently existing MCs in the matrix, shown as arrows between the TPs. The color of the arrow indicates the state of the MC: black means that the MC is free, the use of the same color as the end point TPs means that the MC is part of a trail.

• Pop-up menus for the MCs and TPs, containing menu items for showing attribute values, for finding the layer trail, for showing the details of a specific MC and so on.

When you place the mouse cursor on a TP or an MC, the full name of the entityis displayed in a text ‘bubble’ next to the cursor. How to use the matrix viewis described in [7].

32 MA266 • Rev. E2



4.7 Customer Window

Creating and editing customers

You can create, edit and delete customers in the Customer window. It is re-quired that the customer is created in this window before the customer can beapplied to the customer parameter of a trail.

The window contains a table listing the Customer ID and User Label of thecurrently defined customers.

The procedures for creating, editing and deleting customers are described in‘5.3 Managing Customers’ on page 41.

4.8 Backup Management Window

Backup management Backup of individual NEs and backup groups is set up and edited in the Back-up Management window. New NEs that are registered in the management sys-tem, are automatically added to the backup group "Default".

The window and functionality of backup management is described in [4].

MA266 • Rev. E2 33



4.9 Quality of Service Window

Setting up the quality of service parameters

The quality of service parameters used in management of Ethernet traffic aredefined and edited in the Quality of Service window.

The procedures for creating and editing the various quality of service param-eters are described in ‘6 Quality of Service and AFC Profiles’ on page 47.

34 MA266 • Rev. E2


5 Basic Procedures

5 Basic Procedures

Overview The following basic procedures are described:

• ‘5.1 Running the GUI Client’ on page 35

• ‘5.2 Creating an LND’ on page 38

• ‘5.3 Managing Customers’ on page 41

• ‘5.4 Navigating in a Network’ on page 43

• ‘5.5 Printing’ on page 45

5.1 Running the GUI Client

How to run the GUI client After the installation of Tellabs 6300 manager, the menu shown in the figurehas been added to your start menu.

The menu allows you to start either individual programs or all of the pro-grams at once (using the Start All menu item). The available individual pro-grams are:

• Network editor, which is where you create your network model.

• Network manager, which is the main management window of Tellabs 6300 manager.

• Shell, which is where you can open a Telnet session.

• Tellabs 6300 Change Password, which is where you can change the pass-word for your own Tellabs 6300 manager login.

• Tellabs 6300 User Manager, which is where System Managers can create log in profiles for new users, modify access rights for existing users and delete user logins that are no longer required. These functions are not de-scribed in this documentation, see [5].

• The TeMIP client, which is where you are able to monitor alarms generat-ed in the network management system.

The first time you start one of the programs in a specific session, you will bepresented with a login window to log on to the host, as described in ‘To openTellabs 6300 manager’ on page 35.

To open Tellabs 6300 manager

This procedure describes how to open Tellabs 6300 manager. The procedureapplies to the programs listed below:

• Network Editor

• Network Manager

• Start All

MA266 • Rev. E2 35


5 Basic Procedures

• TeMIP Client

Step Action

1 Open your start menu and select the relevant Tellabs 6300 Network Manager → <program> menu item.

A yellow session manager icon appears in the right side of your task-bar.

The Tellabs 6300 Network Manager Logon window appears, showing the user name and host name of the last Tellabs 6300 manager ses-sion.

2 If required, type your own user name in the User Name: field.

Note: The user name from the last session is shown in the field as de-fault.

3 If you want to log on to a different host than the one shown in the Host: field, click on the down arrow alongside the field and select the required host name from the drop-down list.

Note: The drop-down list in the Host: field contains only the hostnames that the current Tellabs 6300 manager installation has beenconfigured with.

4 Type your password in the Password: field and click OK.

The Tellabs 6300 Network Manager window is closed. If the connec-tion to the host is possible, the session manager icon changes to green.

After a few moments, the requested Tellabs 6300 manager window appears.

36 MA266 • Rev. E2


5 Basic Procedures

To close the Tellabs 6300 manager

This procedure describes how to close all currently open Tellabs 6300 manag-er windows and log out of the session manager.

Note: Closing all open Tellabs 6300 manager windows manually does not logyou out of the session manager.

To change a your user password

This procedure describes how you can change your own log in password forthe Tellabs 6300 manager.

Note: If you have system administrator access rights, then you can alsochange the password for other users. For details to do this, see [5].

Step Action

1 Click on the green session manager icon with the secondary mouse button.

The pop-up menu item Log Off Tellabs 6300 Network Manager ap-pears.

2 Select the Log Off Tellabs 6300 Network Manager menu item.

The session manager icon changes to red.

After a few moments, all currently open Tellabs 6300 manager win-dows close and the session manager icon disappears.

Step Action

1 Select Start → Tellabs 6300 Network Manager → Tellabs 6300 Change Password.

The T6300 Change Password window appears.

2 Type in your own Tellabs 6300 manager user name in the User Name: field.

3 Type in your current password in the Old Password: field.

MA266 • Rev. E2 37


5 Basic Procedures

5.2 Creating an LND

Creating entities Most of the entities of the network representation are created in the networkeditor (as described in [1]). The LND, which is the basis for the whole networkentity hierarchy at a specific layer, must however be created in the entitybrowser.

Note: The relevant LNDs must be created before you set up your networkmodel in the network editor. LNDs are generally created as part of theinstallation of Tellabs 6300 manager.

When you create your network in the network editor, the entities are automat-ically generated in the LNDs specified in the system configuration file.

To create an LND This procedure describes how to create an LND, using the entity browser.

4 Type in your new password in the New Password: field.

Note: The password must have 6 characters or more.

5 Type in the password you used in Step 4 in the Confirm New Pass-word: field.

6 If the Tellabs 6300 manager installed on the PC client has access to more than one server, then select the correct server name from the Host drop-down list.

7 Click OK to make the changes and close the T6300 Change Password window.

Note: You must use the new password the next time you log on toTellabs 6300 manager.

Step Action

Step Action

1 Start the Tellabs 6300 network management system and log on to the correct server.

38 MA266 • Rev. E2


5 Basic Procedures

2 In the network manager window, select Operations → Entity Brows-er.

The Entity View window appears.

3 In the Global Classes list, open the pop-up menu for LND and select Directive View.

The Directive View - LND window appears.

Step Action

MA266 • Rev. E2 39


5 Basic Procedures

4 To create the LND:

a) In the Entity field, delete the * and type in the name for the new LND.

Note: Each LND must have a unique name. We recommend thatyou let the name indicate which layer the LND represents. For ex-ample, PH to represent the physical layer.

b) In the Directive field, select Create in the drop-down list.

c) Select the SignalType in the drop-down list.

d) In the Net field type in a name for the net.

e) Select Operations → Start.

5 To register the operation context you just created:

a) In the Directive field, select Register in the drop-down list.

b) Make sure that the Operation field is set to Register.

c) Select Operations → Start.

6 Keep the Directive View window open as you need to copy the text in the Entity field later on in this procedure.

7 In the Network Management window, select Operations → Network Editor.

The Network Editor window appears.

8 To insert the LND that you created:

a) In the domains view of the Network Editor, open the pop-up menu for the domain name you defined in Step 4 and select Open domain. A map view for the domain opens.

b) In the map view for the domain, open the pop-up menu and se-lect Insert TeMIP object. The Insert TeMIP Object window appears.

c) In the Insert TeMIP Object window, select the Name field and paste the text from the Entity field in the Directive View window.

d) Click OK.

e) Select File → Commit to implement the changes. The Commit win-dow appears.

f) Click Start in the Commit window.

Step Action

40 MA266 • Rev. E2


5 Basic Procedures

5.3 Managing Customers

To create a customer This procedure describes how to create a customer for trail management.

Step Action

1 Select the menu item Operations → Customer.

The Customer window appears, containing a table with all the cur-rently existing customers.

2 Click New....

The New Customer window appears.

3 Specify the name of the customer in the Customer ID: field.

4 If required, specify an extra description of the customer in the User Label: field.

5 Click OK.

The New Customer window closes, and the customer is listed in the table in the Customer window.

6 If you want to create more customers, click Apply.

7 To save the new customer and close the window, click OK.

MA266 • Rev. E2 41


5 Basic Procedures

To edit a customer ID or Label

This procedure describes how to edit the ID and/or Label of an existing cus-tomer.

To delete a customer This procedure describes how to delete an existing customer.

Note: It is not possible to delete a customer when active trails exist for thiscustomer. Therefore, it is necessary to delete all trails for this customeror move them to another customer name.

Step Action



2 Select the line representing the customer that you want to edit.

3 In the fields at the bottom of the widow, change the value(s) for Cus-tomer ID and/or Customer Label.

4 Click OK.

The changes to the table are applied and the Customer window clos-es.

Note: The Customer ID and Customer Label values on all trails thatbelong to this customer change to match these edits.

Step Action



42 MA266 • Rev. E2


5 Basic Procedures

5.4 Navigating in a Network

Navigating with the mouse

When a subdomain is represented by an icon in the parent domain, you canopen the subdomain by double-clicking on the icon.

Navigating with the Navigation menu items

The domains that you have had open during the current session create a listof domains shown in the Navigation menu. You can navigate in the list eitherdirectly by selecting the domain name or stepwise by using the menu itemsBack and Forward.

To navigate with the Domain Browser

The Network Management window contains a domain browser, which allowsyou to navigate in the domain hierarchy via a tree structure.

2 Select the line representing the customer that you want to delete and click Delete.

The customer disappears from the table.

3 Click OK.

The changes to the table are applied and the Customer window clos-es.

Step Action

Step Action

1 Select the menu item Navigation → Domain Browser.

The Domain Browser window appears, showing the tree structure of the domain hierarchy.

MA266 • Rev. E2 43


5 Basic Procedures

To locate a specific entity The Network Management window contains a Find Entity option, which al-lows you to search for a specific entity in the full domain hierarchy.

2 To open another domain, use one of the following methods:

• Expand the relevant branch of the tree (if required) and double-click on the domain node.

• Expand the relevant branch of the tree (if required), click on the domain node to select it and then select the menu item File → Open Domain.

Step Action

Step Action

1 Select the menu item Operations → Find Entity.

The Find Entity window appears.

The window contains toggle buttons, which allow you to specify the relevant entity type, and an entry field where you can type the name of the required entity.

2 Select the relevant entity type and specify the name of the entity.

Note: The relevant LND name and the entity type are automaticallyentered in the entry field when you select the NEMatrix, ExternalMatrixor FibreMatrix toggle button. The Other toggle button leaves the entryfield empty so that you can specify other types of entities (for examplea domain).

3 Click Find.

If the specified entity exists, the first domain where the entity is used appears in the Network Management window. The entity is located in the center of the window and is highlighted with a shaded back-ground behind the matrix icon. The message "Entity found in <do-main>" appears in the Find Entity window.

If the entity exists in more than one domain, click Find again. The next domain where the entity is used appears and the entity appears with a shaded background in the center of the window.

44 MA266 • Rev. E2


5 Basic Procedures

5.5 Printing

To print the contents of the Network Management window

If you have a printer installed on your PC, you can print the current contentsof the Network Management window to your printer or to a file.

Step Action

1 To change the page setup:

a) Select the menu item File → Page Setup.... The Page Setup win-dow appears.

b) To change the paper size, open the Size: drop-down list and select the required value.

c) To change the paper source, open the Source: drop-down list and select the required value.

d) To change the page orientation to landscape, select the Landscape radio button.

e) To change the margins, type the relevant values in the fields.

f) Click OK. The settings are saved and the Page Setup window clos-es.

2 Select the menu item File → Print....

If a printer is installed on the PC, the Print window appears.

MA266 • Rev. E2 45


5 Basic Procedures

3 Set up the printing options as required:

a) To select another printer, select the printer in the Select Printer list or click Find Printer....

b) To configure the printer, click Preferences.

c) To print to a file, select the Print to file check box.

d) To print a specific selection of pages, use the radio buttons and field in the Page Range group box.

e) To print more than one copy, type or select a value in the Number of copies field.

4 Click Print.

Step Action

46 MA266 • Rev. E2


6 Quality of Service and AFC Profiles


Overview Tellabs 6300 manager uses bandwidth profiles and AFC profiles in the man-agement of Ethernet traffic and quality of service (QoS). The bandwidth pro-files define a set of bandwidth classes for the individual AFC profile. The fol-lowing topics describe how to configure bandwidth profiles, AFC profiles andthe other elements used for QoS:

• ‘6.1 The Quality of Service Window’ on page 47

• ‘6.2 Configuring and Viewing Bandwidth Classes’ on page 48

• ‘6.3 Configuring and Viewing Queue Scheduling’ on page 52

• ‘6.4 Configuring and Viewing the IP Priority Map’ on page 55

• ‘6.5 Configuring and Viewing AFC Profiles’ on page 57

• ‘6.6 Configuring and Viewing Bandwidth Profiles’ on page 62

• ‘6.7 Comparing and Deploying AFC Tables’ on page 64

• ‘6.8 Saving the QoS Parameter Settings’ on page 66

Note: If you add a new QoS element, you must restart Tellabs 6300 managerto activate the element.

6.1 The Quality of Service Window

Quality of Service window

The Quality of Service window and its sub-windows are used for defining andviewing the parameters specifying the quality of service delivered to the cus-tomer.

The window contains five tabs. The Bandwidth Classes tab page is preselectedwhen you open the window.

MA266 • Rev. E2 47



6.2 Configuring and Viewing Bandwidth Classes

Bandwidth classes A maximum number of 512 bandwidth classes can be defined. A bandwidthclass consists of an ID, a label, a bandwidth and a burst size. A bandwidth ofthe specified size will be guaranteed, but the customer is allowed to send bursttraffic up to the specified burst size. However, traffic sent at a rate which ishigher than the guaranteed bandwidth but still below the burst size, is notguaranteed.

The bandwidth classes are grouped according to the following types:

Note: Different bandwidth classes are already available by default.

Note: CIR classes are used when Fixed is selected in Queue Scheduling. PIRclasses are used when Free is selected. CIR + PIR classes are used whenboth Fixed and Free are selected. See ‘6.3 Configuring and ViewingQueue Scheduling’ on page 52.

Bandwidth Type Description

CIR This type of bandwidth is always available to the traffic.

PIR This type of bandwidth is only available when unused bandwidth (not used by CIR) is available.

CIR + PIR This type of bandwidth guarantees a specified amount of bandwidth. If additional bandwidth is required, then the available additional band-width is shared between the traffic using PIR.

48 MA266 • Rev. E2



To create a new bandwidth class

This procedure describes how to create a new bandwidth class.

Note: You have to be a System Administrator to be able to access the Qualityof Service window.

Note: If you try to create a new bandwidth class with a combination of param-eters that is identical with the parameters of an existing bandwidthclass, the new class will be rejected and a message will inform youabout the ID and label of the existing bandwidth class,

Step Action

1 Select Operations → Quality of Service... in the main menu of Tellabs 6300 manager.

The Quality of Service window appears, showing the Bandwidth Classes tab page.

A table with six columns is shown, in which you can view the speci-fications of the defined bandwidth classes. The table displays an au-tomatically assigned ID for each bandwidth class, the unique label assigned to each class, the bandwidth and/or peak rate in kbit/s, and the burst size and/or peak burst size in kbytes.

2 Click Add Bandwidth Class....

The Add Bandwidth Class window appears.

MA266 • Rev. E2 49



3 If required, select another bandwidth type in the Bandwidth Class Type: drop-down list.

Note: The bandwidth value fields change according to the selectionof type.

4 Specify a unique label in the Bandwidth Class Label: field.

5 Select a bandwidth in the Mean Rate: drop-down list, or type a value in the field.

6 Select a burst size in the Max Burst Size: drop-down list, or type a val-ue in the field.

7 Select a peak rate in the Peak Rate: drop-down list, or type a value in the field.

8 Select a peak burst size in the Peak Burst Size: drop-down list, or type a value in the field.

9 Click OK.

The window closes and the input focus is returned to the Quality of Service window. The new bandwidth class is added to the table on the Bandwidth Class tab page. The lowest free ID is automatically as-signed to the new bandwidth class.

10 Click OK or Apply.

Step Action

50 MA266 • Rev. E2



To edit the label of a bandwidth class

This procedure describes how to edit the label of an existing bandwidth class.


Step Action



The table shows the bandwidth classes related to the CIR bandwidth type.

2 If required, select another bandwidth type in the Bandwidth Class Type: drop-down list.

3 Select the row describing the relevant bandwidth class.

4 Click Edit Label....

The Edit Label window appears. The window shows the label of the selected bandwidth class.

5 Specify the new label in the Label: field.

Note: The label must be unique.

6 Click OK.

The window closes and the input focus is returned to the Quality of Service window. The label of the selected bandwidth class is changed to the new value.


MA266 • Rev. E2 51



6.3 Configuring and Viewing Queue Scheduling

Queue scheduling Queue scheduling defines which class of service each queue in the systemsupports. Each type of queue is given one or more type of bandwidth. Fixedand/or Free. Fixed uses CIR settings and Free uses PIR settings (see ‘Band-width classes’ on page 48). The queue is also given a priority value: High, Nor-mal or Low. These settings determine how the traffic is handled by the band-width available.

There are by default four different classes.

Warning: We recommend that you do not change the settings for QueueScheduling

Class of Service Description

Real Time Committed (fixed), high priorityA real-time traffic class for VoIP and other traffic that needs a constant flow with very lit-tle jitter.

Business Data with Burst Committed (fixed) with burst (free), normal priorityA class for customers who want not only a guaranteed bandwidth but also to be able to send bursts of traffic.

Business Data Committed (fixed), normal priorityA class for packet-emulated Ethernet connec-tion service.

Best Effort Limited (free), normal priorityA low-cost traffic option for customers who do not need a guaranteed bandwidth.

52 MA266 • Rev. E2



To change a queue This procedure describes how to change the settings of a specific queue.

Note: We recommend that you use the default settings.

Step Action



2 Select the Queue Scheduling tab.

The Queue Scheduling tab page is displayed.

On this tab page you can view the specifications of the defined queues or classes of service.

MA266 • Rev. E2 53



3 Select the row describing the relevant queue.

The fields below the queue table become active.

4 Change the settings of the check boxes and the drop-down list as re-quired.

5 To change the label of the queue, click Edit Label....

The Edit Label window appears. The window shows the label of the selected queue.

6 Specify the new label in the New Label: field and then click OK.

The window closes and the input focus is returned to the Quality of Service window. The label of the selected queue is changed to the new value.

7 Select OK or Apply.

Step Action

54 MA266 • Rev. E2



6.4 Configuring and Viewing the IP Priority Map

To configure the IP priority mapping

This procedure describes how to configure the mapping of IP DSCP priorityto EXP priority.

Step Action



2 Select the IP Priority Map tab.

The IP Priority Map tab page is displayed.

On this page you can view the mapping of IP DSCP priority values to EXP priority values.

MA266 • Rev. E2 55



3 Select the row for the relevant IP DSCP priority value.

The drop-down list for selection of the EXP priority value becomes active.

4 Select an EXP priority value in the drop-down list.


Step Action

56 MA266 • Rev. E2



6.5 Configuring and Viewing AFC Profiles

AFC profiles A maximum number of 16 AFC profiles can be defined. An AFC profile con-sists of an ID, a label and a priority mapping table. The priority mapping tablecontains 8 different priorities each associated with a queue number and a dropprecedence level. When you create an LSP that spans several network ele-ments, the same AFC profile must be selected in all network elements. Thismeans that the definition of AFC profiles is a network-wide operation and nota network element specific issue.

The set of default AFC profiles consists of 5 AFC profiles, where 4 of the pro-files map to only one queue each and therefore have the same names as therelevant queue (see ‘Queue scheduling’ on page 52). The last default AFC pro-file (Multi Service) uses all queue types.

To create a new AFC profile

This procedure describes how to create a new AFC profile.


Step Action



MA266 • Rev. E2 57



2 Select the AFC Profiles tab.

The AFC Profiles tab page is displayed.

On this tab page you can view the specifications of the defined AFC profiles. The page contains two tables. The table to the left displays all defined AFC profiles, specified by an ID and a unique label. The table to the right displays the priority mapping of the AFC profile currently selected in the table to the left. Eight different priorities can be specified, where each priority is associated with a specific queue.

3 Click Add AFC Profile....

The Add AFC Profile window appears.

4 Specify a unique label for the new AFC profile in the Label: field.

5 Select an ID in the ID: drop-down list.

Note: The list only contains the free IDs and the lowest free ID is au-tomatically displayed.

Step Action

58 MA266 • Rev. E2



To edit the label of an AFC profile

This procedure describes how to edit the label of an existing AFC profile.

6 Specify the queue priority mapping in the following way:

a) Select the row for the relevant priority in the EXP Priority: table. The line below the table becomes active.

b) Select the relevant queue in the drop-down list.

c) Repeat the procedure for each priority, if required.

7 Click OK.

The Add AFC Profile window closes and the input focus is returned to the Quality of Service window. The new AFC profile is added to the list of AFC profiles in the Quality of Service window.


Step Action

Step Action



MA266 • Rev. E2 59





3 Select the row for the relevant AFC profile.

The Edit Label... button becomes active.

4 Click Edit Label....

The Edit Label window appears. The window shows the label of the selected AFC profile.

Step Action

60 MA266 • Rev. E2



To delete an AFC profile This procedure describes how to delete an AFC profile.

5 Specify the new label in the New Label: field and then click OK.

The window closes and the input focus is returned to the Quality of Service window. The label of the selected AFC profile is changed to the new value.


Step Action

Step Action





MA266 • Rev. E2 61



6.6 Configuring and Viewing Bandwidth Profiles

Bandwidth profiles Bandwidth profiles define the sets of bandwidth classes that are used by theindividual AFC profile.

To create a new bandwidth profile

This procedure describes how to create a new bandwidth profile.

3 Select the row for the relevant AFC profile in the Select AFC Profile for Configuration: table.

The Delete Profile button becomes active.

4 Click Delete Profile.

The AFC profile is removed from the list.


Step Action

Step Action



62 MA266 • Rev. E2



2 Select the Bandwidth Profiles tab.

The Bandwidth Profiles tab page is displayed.

On this page you can view the specifications of the defined band-width profiles and see how they relate to the AFC profiles. The de-fault setting shows the bandwidth profiles for all AFC profiles.

3 In the Select AFC Profile: drop-down list, select the AFC profile that you want to add a new bandwidth profile to.

The Add Bandwidth Profile... button becomes active.

Step Action

MA266 • Rev. E2 63



6.7 Comparing and Deploying AFC Tables

Overview The behavior of a cross-connection (MC) in an ETEX 2.x or ETEX 3.x moduledepends on two tables stored in the NE: the Assured Forwarding Class (AFC)profiles table and the Queue Scheduling Profile (QSP) table. The QSP table ispredefined in the NE, whereas the AFC table must be defined and then trans-ferred (deployed) into all new NEs. The following topics describe how to com-pare and deploy AFC tables:

• ‘6.7.1 Comparing the AFC Table with the Table in One or All ETEX 2.x and ETEX 3.x NEs’ on page 65

• ‘6.7.2 Deploying the AFC Profiles and IP DSCP Mapping into All ETEX NEs’ on page 65

Warning: When you are using a specific AFC profiles table in your network,do not change the profiles but only add new ones. If the priority ofa specific profile is changed, trails using that profile may suddenlyno longer be allowed to carry traffic.

4 Click Add Bandwidth Profile....

The Add Bandwidth Profile window appears.

The window contains a field for specifying the label of the new band-width profile and a number of drop-down lists for selecting the bandwidth classes.

Note: Only the drop-down lists relevant for the currently selectedAFC profile are active. For example, when Multi Service is selected allthe drop-down lists are active.

Note: When the Business Data with Burst attribute is active, the list ofpossible values includes all the Business Data with Burst bandwidthclasses and the complete list of CIR bandwidth classes. In this situa-tion, PIR values = 0, which gives an unlimited peak information rate.The values in this list are required when you upgrade the embeddedsoftware your ETEX modules from 2.x to 3.x.

5 Specify a unique label for the bandwidth profile in the Label: field.

6 Select a bandwidth class in the relevant drop-down list or lists and then click OK.

The window closes and the input focus is returned to the Quality of Service window. The new bandwidth profile is listed in the table.


Step Action

64 MA266 • Rev. E2



6.7.1 Comparing the AFC Table with the Table in One or All ETEX 2.x and ETEX 3.x NEs

Compare a single ETEX 2.x or 3.x NE

The following FCL command allows you to compare the AFC profile table ina specific ETEX 2.x or 3.x module with the general AFC profile table. In thisexample, the comparison is for an ETEX 2.0 NE:

>compare NeSysConfig nesysconfig ne=etex_20 ne_name, con-figType=AFC

where ne_name is the ID of the specific ETEX NE.

Compare all ETEX 2.0, 2.2 or 3.0 NEs

The following FCL command allows you to compare the AFC profile tables inall ETEX 2.0, 2.2 or 3.0 modules in the network with the general AFC profiletable. In this example, the comparison is for all the ETEX NEs with the globalclass ETEX_20. (The correct way to write the class is shown in the Global Class-es list in the Entity Browser window):

>compare NeSysConfig nesysconfig ne=etex_20 *, config-Type=AFC

6.7.2 Deploying the AFC Profiles and IP DSCP Mapping into All ETEX NEs

To deploy AFC profiles and IP DSCP mapping

This procedure describes how to send the definitions of AFC profiles and IPDSCP mapping to all ETEX modules in the network.

Step Action

1 In the Quality of Service window, click Deploy.

A Warning window appears, asking whether you want to continue the operation.

2 Click Yes.

The Deploy Progress window appears.

This window gives a list of ETEX NEs where the quality of service settings are being deployed and it provides a status of the deploy-ment in each NE: successfully deployed or not deployed.

MA266 • Rev. E2 65



6.8 Saving the QoS Parameter Settings

To save the QoS parameters

The current setting of QoS parameters can be saved to a set of text files (anAfcProfile file, a BandwidthClass file and so on). This procedure describes howto create the set of files.

3 Press Close to exit this window and return to the Quality of Service window.

Step Action

Step Action

1 In the Quality of Service window, click Save....

The Save Quality of Service Parameters window appears.

2 Locate the folder where you want to save the parameter files and click Save.

The following set of text files is created:

• AfcProfile

• BandwidthClass

• BandwidthProfile

• Defaults

• DpPrioProfile

• IpDsProfile

• QSchedulingProfile

66 MA266 • Rev. E2


A Character Restrictions in Text Entries


General restrictions The following character restrictions apply to all text entries:

• The ’ (hyphen) character is invalid as it is reserved in Oracle.

• The * (asterisk) is invalid as it is used as a wildcard.

Restrictions in ID texts The table describes the character restrictions in ID attribute texts.

Note: sp (space) is valid in trail IDs when the trail ID is enclosed in quotationmarks.

MA266 • Rev. E2 67



Restrictions in Customer, User Label and Note texts

The table describes the character restrictions in Customer, User Label andNote attribute texts.

68 MA266 • Rev. E2


Index

Index

Numerics6300 network manager

changing user password 37closing 37opening 35

AAbbreviations 8About Network Management menu item

in Network Management window 19AFC profiles 57

configuring and viewing 57creating new 57deleting 61editing label 59

BBack menu item

in Network Management window 19Bandwidth classes 48

configuring and viewing 48creating new 49editing label 51

Bandwidth profiles 62configuring and viewing 62creating new 62

Buttonsin Network Management window 20

CChanging a queue 53Child entities 14Configuring and viewing AFC profiles 57Configuring and viewing bandwidth classes 48Configuring and viewing bandwidth profiles 62Configuring and viewing IP priority mapping 55Configuring and viewing queue scheduling 52Creating and deleting customers 41Creating new AFC profile 57Creating new bandwidth class 49Creating new bandwidth profile 62Customers

creating 41deleting 41, 42editing 41, 42

DDeleting AFC profile 61

Domainuse of 14

Domain Browser menu itemin Network Management window 18using 43

Domain Browser window 43Domain Tree Browser button

in Network Management window 20Domains 15

EEditing label of AFC profile 59Editing label of bandwidth class 51Entities 14

child entities 14global entities 14

Entity Browser menu itemin Network Management window 18

Equipmentgrouping in domains 14

Exit menu itemin Network Management window 18

External links 16External matrices 16

FFibre matrices 15Find Entity button

in Network Management window 20Find Entity menu item

in Network Management window 18using 44

Find Entity window 44Find Trail button

in Network Management window 20Find Trail menu item

in Network Management window 18Forward menu item

in Network Management window 19

GGlobal entities 14GUI client

running 35

IIcons

for network entities 21

MA266 • Rev. E2 69


Index

IP priority mappingconfiguring and viewing 55

LLayer network domains 15Links 16LNDs

creating 38

MMenus


NNavigating in network 43NE matrices 15NEs 15Network Editor button

in Network Management window 21Network Editor menu item

in Network Management window 18Network entities

attributes 16definitions 15icons 21locating 44

Network Management window 17alarm colors 24buttons 20main menus 18pop-up menus 22

Next domain buttonin Network Management window 20

PPacket links 16Page setup 45Page Setup menu item 45Previous domain button

in Network Management window 20Print ... menu item

in Network Management window 18Print Domain button

in Network Management window 21Print menu item

using 45Printing domain display 45

QQoS 47

saving parameters 66

Quality of service 47saving parameters 66

Quality of Service window 47Quality of Service... menu item

in Network Management window 18Queue scheduling 52

changing a queue 53configuring and viewing 52

Queueschanging 53

RRefresh menu item

in Network Management window 18Refresh screen button

in Network Management window 20Reset Domain Hierarchy menu item

in Network Management window 19Running GUI client 35

SSet Default Top Domain menu item

in Network Management window 19Setting up page 45Show Alarm Status menu item

in Network Management window 19Show External Links menu item

in Network Management window 19Show Link Capacity menu item

in Network Management window 19Show Link Names menu item

in Network Management window 19Show Packet Links menu item

in Network Management window 19Show Timing menu item

in Network Management window 19Starting program 35Stop process button

in Network Management window 20Style conventions 8

TTellabs 6300 Network Manager Logon

window 36Timing Options menu item

in Network Management window 19Toolbar buttons

in Network Management window 20Top domain button

in Network Management window 20Top menu item


70 MA266 • Rev. E2


Index

Trail History menu itemin Network Management window 18

Trails 16

ZZoom in button

in Network Management window 20Zoom out button


MA266 • Rev. E2 71


Index

72 MA266 • Rev. E2

6300 principle of operation

Documents