Tellabs OSN2

Technical Documentation

Copyright © 2002-2007, 2009 Tellabs. All rights reserved.

Product family Tellabs® 6300 Managed Transport System

Product name Tellabs® 6300 Network Manager

Title Monitoring Performance

Document User’s ManualMA276 / Revision D1

Tellabs® 6300 Network ManagerMonitoring Performance

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 MA276 • Rev. D1


Revision Information


Revision history This manual has changed as follows:

Rev. Date Description of Changes

A1 15/10-2002 First revision

B1 Feb. 27, 2004 • Syntax and description of the "dbextract" com-mand have been changed in ‘4 Exporting Perfor-mance Data’ on page 49.

• Monitoring of Ethernet-related entities has been added.

• Command appendix has been removed.

C1 Oct 31, 2005 • Descriptions of Monitoring Set attributes have been added in ‘A Attributes Connected to Moni-toring’ on page 57.

• All references to Traffic View have been re-moved.

• dbextract parameters have been updated.

• Procedures concerning starting and stopping trail monitoring from Trail View have been re-moved.

• Text and pictures have been updated to reflect feature pack 3.0 of Tellabs 6335 switch node.

• Description of VCG monitoring attributes has been added.

• Procedure concerning starting monitoring for a VCG has been added.

• Procedure concerning starting and stopping MTP monitoring from EM GUI has been added.

• Procedure concerning making a performance re-port for an MTP from EM GUI has been added.

C2 Aug. 10, 2006 Compared to revision C1:

• Added 2 new procedures. These describe how to start and stop performance monitoring for NEs that use older software.

• Added 2 new procedures. These describe how to make performance monitoring reports for NEs that use older software.

• Added new illustration that explains time-stamps.

• Added a new procedure that describes how to print a performance report to a text file.

MA276 • Rev. D1 3



C3 Sept. 1, 2007 Compared to revision C2:

• Updated the data fields available with the dbex-tract command.

• Updated the list of NEs where data collection can occur.

• Minor technical corrections.

D1 Mar. 3, 2009 Added information for Tellabs 6335 switch node.

Rev. Date Description of Changes

4 MA276 • Rev. D1


Contents

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

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

1 Description of Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . 91.1 A General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2 The Collection of the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101.3 The Performance Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

2 Collecting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.2 The Available Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162.3 Collecting Data from Individual Monitored Termination Points . . . . . . . 182.4 Collecting Data from Individual Trails . . . . . . . . . . . . . . . . . . . . . . . . . . 222.5 Collecting Data from Concatenated Trails . . . . . . . . . . . . . . . . . . . . . . 312.6 Using the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

3 Displaying the Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . 353.1 The Window in which the Data is Displayed . . . . . . . . . . . . . . . . . . . . 353.2 How to Create the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

3.2.1 Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363.2.2 Using the Search Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.3 How to Print the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

4 Exporting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494.1 Creating Files with Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . 494.2 The Generated Performance Data File . . . . . . . . . . . . . . . . . . . . . . . . 50

A Attributes Connected to Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 57A.1 Trail Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57A.2 TTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58A.3 CTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58A.4 VCG Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59A.5 How the TPs’ Monitoring State Attribute Changes . . . . . . . . . . . . . . . . 60

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

MA276 • Rev. D1 5


Contents

6 MA276 • Rev. D1


Preface

Preface

Overview Using performance monitoring, you can collect performance data for as wellindividual network elements as for a specific trail or for all the trails in a spe-cific layer network domain (LND).

In addition to that, you can control the collection of performance data for spe-cific termination points or specific network elements directly from the net-work traffic management interface.

Finally, you can suspend the collection of data from a network element tem-porarily and then resume it when required.

Product version Check the Software Release Notes to make sure that this manual correspondsto your current product version.

The structure of this manual

The manual is structured as follows:

• ‘1 Description of Performance Monitoring’ on page 9 describes the basic principles behind performance monitoring and introduces some concepts that are used in the rest of the manual.

• ‘2 Collecting Performance Data’ on page 15 describes how to control the collection of performance data from termination points, network elements and trails.

• ‘3 Displaying the Performance Data’ on page 35 describes how to create performance reports for termination points and trails from the collected data.

• ‘4 Exporting Performance Data’ on page 49 describes how to export per-formance data into comma-separated files.

• ‘A Attributes Connected to Monitoring’ on page 57 describes the at-tributes relevant for performance monitoring.

MA276 • Rev. D1 7


Preface

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

• Names from the screen

Bold typeface are used for names of, for instance, windows, operations,fields, and push buttons when the names appear on the screen (example:the Performance Report window). When it is clear that we are referring to,for instance, a push button, the name is used alone (example: Click on OK).Note that bold typeface are also used in other contexts (for example, in sec-tion headings).

• Text to be replaced

Italics are used for words to be replaced by a specific member of the groupthat the word represents (example: NE type). If the words are substitutedby the system, angle brackets are used around the italics.

• Text from the screen

“Quotation marks” are used for text strings from the screen (example:“Performance Collection successfully started on 2 entities”).

• Menus

Arrows are used for indicating the menu structure in instructions on howto select a certain menu item (example: Select Performance Monitoring →Report).

Abbreviations BBE Background Block ErrorsCTP Connection Termination PointES Errored SecondsLND Layer Network DomainMTP Monitored Termination PointNE Network ElementOAM Operation, Administration and MaintenanceSES Severely Errored SecondsTTP Trail Termination PointUAS UnAvailable SecondsUTC Universal Time Co-ordinatesVCG Virtual Concatenation Group

References [1] MA333, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, System Administration Guide and Reference

[2] MA360, Tellabs® 6300 Managed Transport System, Tellabs® 6300 Net-work Manager, Managing SDH and Ethernet Trails, 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

8 MA276 • Rev. D1


1 Description of Performance Monitoring


Overview The basic principles behind performance monitoring are described and someconcepts that are used in the rest of the manual are introduced.

We assume that you are familiar with the concepts described in the ElementManagement manuals and in the manual describing network traffic manage-ment (see [2]).

1.1 A General Overview

What is performance monitoring?

The performance monitoring facility collects performance data from Tellabs6300 manager and stores the data in an SQL database. The collected data canthen be displayed in performance reports.

The monitored entities Performance data are collected from the termination points in the network el-ements (the ‘monitored termination points’ or MTPs).

Depending on the type of network element, an MTP may represent the corre-sponding termination point either at only one network layer or at several net-work layers at the same time. This means that, for some NE types, the perfor-mance data for an MTP may consist of several instances of the same counter,only at different layers.

You can activate the data collection either for specific MTPs, for all MTPs be-longing to specific NEs, or for MTPs that are part of specific trails (both indi-vidual trails and concatenated trails).

In NEs that support non-intrusive monitoring, a connection termination point(CTP) is represented by two MTPs, one for each data flow direction (incomingor outgoing).

Performance data The performance data collected in performance monitoring are the values of:

• SDH OAM data:

• 15-minute and 24-hour counters (Counters attributes)A counter value is the sum of measurement values. The values of indi-vidual measurements are added to the counter value during the 15 minutes or 24 hours, then it starts from 0 again.

• Gauges (for example, laser temperature).A gauge value is the measurement value for that specific moment.

• Ethernet statistics data:

• The statistics provide information about how many packets have been sent and received and how they have been distributed.

Note: When you create the performance reports for SDH OAM data, youmust choose which type of information you want displayed. That is,

MA276 • Rev. D1 9



you can either get a report of the counter values or a report of the gaugevalues.

Requirements Performance monitoring uses both the element access facilities and the net-work traffic management facilities of Tellabs 6300 manager.

• The performance data are retrieved from the network element via the rel-evant element management functions.

• The performance reports for trails are created via the network traffic man-agement functions. Performance reports for individual MTPs are created via the dbextract command.

1.2 The Collection of the Data

15-minute counters The performance counters are collected with 15-minute intervals, the first onestarting at 00:00 and ending at 00:15. A time stamp is assigned to the counter,corresponding to the start of the covered interval.

Example: The 00:00 counter covers the time interval from 00:00 to 00:15.

24-hour counters The 24-hour performance counters are collected with 24-hour intervals, start-ing at 00:00 and ending at 00:00 the next night. A time stamp is assigned to thecounters, indicating the covered interval.

Note: ETEX NEs and SDH ETEX NEs follow different times. ETEX NEs canonly follow UTC time while SDH ETEX NEs typically are configured tofollow server time.

Gauges The gauge values are collected each time performance monitoring polls fordata. Laser temperature is an example of a gauge.

Statistics The statistics data are read each time performance monitoring polls for data.The number of packets that have been transmitted is an example of statisticsdata.

Polling The NEs store performance counters for a limited period. Typically, an NE canstore 15-minute counters for 24 hours. With regular intervals, 6300NM perfor-mance monitoring polls the NEs for these data. The time interval between twopolls is called a polling period.

The polling period is specific for each type of NE and varies between 15 min-utes and 24 hours (example: 8 hours for Tellabs® 6320 edge node or Tellabs®6330 core node). All polling periods start at 00:00 or an integer number of poll-ing periods later. For example, 8-hour polling periods start at 00:00, 08:00 and16:00.

When performance monitoring polls for data, all the 15-minute counters fromthe previous polling period are retrieved. After a poll, the data are stored inthe performance database. This means, however, that performance data with-in the current polling period are not available for performance reports. See‘Example of 15-minute counter collection’ on page 11.

The 24-hour counters are checked at each poll, but are not stored until at theend of the 24-hour interval. At each poll, if no error has occurred in the previ-ous polling period, a 15-minute counter “indicator” is stored (indicating thatno errors occurred). If, however, the 24-hour counter’s value at a poll indicates

10 MA276 • Rev. D1



an error, the 15-minute counter from the time of the error is stored (to showthe time of the error) along with “indicators” for the remaining parts of the pe-riod. See ‘Example of 24-hour counter collection’ on page 12.

Data time Performance monitoring uses UTC time when it saves and presents data. If theequipment uses local time, the server time is converted to UTC time.

Note: The time stamp shown in a dbextract report is UTC time. The timestamp used in the GUI is server time.

Example for 24-hour counters: ETEX NEs, which can only run UTC, will on aDanish server during summertime (UTC+2) have the dbextract time stamp00:00:00 and the GUI time stamp 02:00:00. SDH ETEX NEs are typically con-figured to follow server time and will therefore on the same Danish serverhave the dbextract time stamp 22:00:00 and the GUI time stamp 00:00:00.

Illustration of data time stamps in dbextract and GUI

This figure illustrates how the time stamps differ depending on whether theperformance data is viewed using dbextract or using the 6300NM GUI.

Recovery of data after collection failure

If data communication problems occur or if the system shuts down, no dataare collected for a period of time. When data collection is again possible, theperformance monitoring function will attempt to recover the missing data bysending a request for the data to the network elements. However, it is onlypossible to recover data from maximum 3 previous polling periods.

Example of 15-minute counter collection

The figure shows an example of 1-hour polling for 15-minute counters. At01:00, the polling for data from the counters of the previous hour begins (that

MA276 • Rev. D1 11



is, the 00:00, 00:15, 00:30 and 00:45 counters). Shortly after, when the pollinghas completed, these counters are available.

Note: The figure also shows the time flow of the collection of counters. At00:15, the counter started at 00:00 is stored. At 00:30, the counter startedat 00:15 is stored. And so on.

Example of 24-hour counter collection

The figure shows an example of 24-hour counter collection with a polling pe-riod of 8 hours. Two errors occur in the second polling period (between 08:00and 16:00).

At 08:00 the 24-hour counter value does not indicate any error (the value hasnot changed abnormally), so only a 15-minute counter “indicator” is stored forthe previous polling period. The indicator shows that the interval has beenpolled, and that no errors occurred.

At 16:00 the 24-hour counter value has changed abnormally (due to two er-rors). The two 15-minute counters indicating the times of the two errors arestored, and three “indicators” are stored for the remaining parts of the period.

At 00:00 when the 24-hour counter itself is stored, the counter has not changedabnormally since its value at 16:00, so only a 15-minute counter “indicator” isstored for the previous period.

Note: Only when an error occurs within an 8 hour period does the system col-lect 15-minute counters. This is done to determine in which 15 minuteperiod the error occurred.

12 MA276 • Rev. D1



1.3 The Performance Data Reports

Report types The data collected by performance monitoring can be inspected in perfor-mance reports. You can create reports either for one specific MTP or for all theMTPs in a specific trail. The report contains either the counter data or thegauge data for the selected entity.

The layout of a report The figure shows the general layout of a performance report, using a 15-minute counters report for an MTP as an example.

The first lines of the report contain the name of the MTP, an indication of theperiod for which data have been retrieved, and a time stamp, indicating thetime that the report was generated. The rest of the report contains the data, ar-ranged in columns for each counter/gauge.

Each data line represents a period where the counter values did not change:periods less than or equal to the polling period. The time stamp at the start ofthe line indicates the start of that time interval for which the data was collect-ed. For example, the row “1999-04-14 08:00:00” covers the time interval from08:00 to 16:00.

The second column indicates the interval length of the data line (in seconds).If the number of seconds is less than the actual time length between the timestamps of the current data line and the next, it is an indication that data aremissing for some reason (data collection may have been stopped or suspend-ed for a while, the NE may have been unreachable, or some other reason).

If a whole polling period contains nothing but zero-counters (that is, counterswith the value 0), the corresponding data line in the report is empty apart fromtime stamp and interval length.

MA276 • Rev. D1 13



In a report for a trail, the data for each MTP in the trail are presented separate-ly, with a header indicating the name of the relevant MTP. The figure showsthe general layout of a trail report.

Note: Counter values that were not available during the collection, are indi-cated as “na”. For instance, if both the MS and the VC-4 trail layers arehandled by the same MTP, the VC-4 trail counters are not available ifthe trail is not terminated.

14 MA276 • Rev. D1


2 Collecting Performance Data


Overview This chapter describes how you control the collection of performance data.That is, how you start, stop, suspend and resume data collection for individu-al entities.

• ‘2.1 Introduction’ on page 15

• ‘2.2 The Available Operations’ on page 16 describes the available data col-lection operations.

• ‘2.3 Collecting Data from Individual Monitored Termination Points’ on page 18 to ‘2.5 Collecting Data from Concatenated Trails’ on page 31 de-scribe how to use the graphical user interface to activate the operations for MTPs and trails.

• ‘2.6 Using the Command Line Interface’ on page 33 describes how to use the command line interface to activate the operations.

Note: The procedure for creating performance reports from the collected datais described in detail in ‘3 Displaying the Performance Data’ on page 35.

2.1 Introduction

Collecting data for an MTP as part of NE and/or trail

The performance monitoring facility distinguishes between whether the datacollection operations are being activated with ’NE scope’ or with ’trail scope’(that is, whether they are being activated for the MTP as part of an NE or forthe MTP as part of a trail).

This means that if, for example, you start data collection for one particularMTP with both scopes (first with ’NE scope’ and then with ’trail scope’, or viceversa), you will also have to stop the collection with both scopes — eventhough data is, actually, only collected once at each polling period for a par-ticular MTP.

Note: The scope used for the data collection is important for later reports.Trail reports can be generated only if the data was collected with ’trailscope’, while MTP reports can be generated with data from eitherscope.

‘2.3 Collecting Data from Individual Monitored Termination Points’ on page18‘2.4 Collecting Data from Individual Trails’ on page 22 and ‘2.5 CollectingData from Concatenated Trails’ on page 31 describe ’trail scope’.

Non-intrusive monitoring Non-intrusive monitoring of a trail or a trail segment is a way of monitoringwhich does not influence the monitored signal in any way. This means that itis possible to monitor the status of the trail (segment) without terminating thetrail.

In addition to monitoring the end point TTPs of the trail, non-intrusive moni-toring allows you to monitor individual CTPs along the trail’s route(s). Youcan monitor a CTP in one or both of the two data flow directions (that is, in-coming and outgoing data flow). In end point TTPs only the incoming dataflow is monitored.

MA276 • Rev. D1 15



2.2 The Available Operations

Starting data collection The collection of performance data is started with either NE scope or the trailscope, and the actual collection then begins at the start of the next polling in-terval for the NE containing the entities. The first counter to be polled is thecounter for the time interval in which performance collection was started.

In the example shown in the figure, data collection is activated between 0:30and 0:45. When the new polling period starts – in this case at 1:00 – the 00:30and 00.45 counters are collected, and data are then continuously collected.

Stopping data collection No performance data are retrieved for all of the polling period in which youstop the data collection; however, the data collection is not actually stoppeduntil the start of the next polling interval for the NE containing the entities,and until that time the entity will appear as “stopping” if you check its status.

Note: It is possible to reactivate the entity while it is in the “pending” state be-tween the Stop Performance Collection operation and the next polling.

In the example shown in the figure, data collection is stopped between 0:30and 0:45. The entity is in the “pending” state until 1:00 when the next pollingstarts, and its status is “stopping”. Data from the period between 0:00 and 0:45are collected.

16 MA276 • Rev. D1



Seeing the status of the data collection

You can check the current data collection status of an entity with the Get Per-formance Collection Status operation. When you check an NE or a trail, a listis displayed of those MTPs that are currently “active” or “stopping” and theirstate is indicated. When you check a concatenated trail, a list is displayed ofthe currently "active" or "stopping" VCGs.

Seeing the status of the MTPs in a trail

You can check the current monitoring status of the MTPs in a specific trail, us-ing the Performance Monitoring → Get Status (NE) menu item in the Find Trailwindow. When you activate the menu item, the trail view is displayed, withthe color of the label indicating the current value of the MTP’s Monitoring Stateattribute. The figure shows an example of a trail view.

Temporary suspension of data collection

Data collection for an NE can be suspended temporarily and then later re-sumed (using the Suspend Performance Collection and Resume PerformanceCollection operations). MTPs contained in a suspended NE are marked with"SUSP" when you display their status.

It is not possible to suspend data collection for a trail.

Creating a report with the collected data

You can create a report containing some of the collected data from a specificMTP or trail. This operation is described in detail in ‘3 Displaying the Perfor-mance Data’ on page 35.

The ways to activate the operations

The procedures described in ‘2.3 Collecting Data from Individual MonitoredTermination Points’ on page 18 to ‘2.5 Collecting Data from ConcatenatedTrails’ on page 31 illustrate how to activate the data collection operations viathe graphical user interface.

Activating the operations for MTPs from the Performance Data window isused in the procedure in ‘2.3 Collecting Data from Individual Monitored Ter-mination Points’ on page 18.

MA276 • Rev. D1 17



How to use the Find Trail window and the Trail View window for activating theoperations for trails is described in the trail procedures in ‘2.4 Collecting Datafrom Individual Trails’ on page 22 and ‘2.5 Collecting Data from Concatenat-ed Trails’ on page 31.

As the command line interface provides you with possibilities not availablefrom the graphical user interface (mainly, the possibility for carrying out anoperation on several entities at the same time), it is also described in some de-tail (in ‘2.6 Using the Command Line Interface’ on page 33).

Note: You can also use the Directive View window in the entity browser to ac-tivate the data collection operations. The operations for NEs are activat-ed that way.

2.3 Collecting Data from Individual Monitored Termination Points

Which operations can be used?

The following operations can be used in connection with data collection fromindividual MTPs:

• Starting performance collection

• Stopping performance collection

• Getting performance collection status

See ‘2.2 The Available Operations’ on page 16 for a description of the individ-ual operations.

To control data collection for an MTP on a 6315, 6325, 6335, 6340 (FP4.0 or later), 6345 or 6350

This procedure describes how you activate the operations that allow you tocontrol the collection of performance data from a single MTP.

Note: The procedure is valid for the following NE types:

• Tellabs® 6315 metro ethernet node release 1.0 and later

• Tellabs® 6325 edge node release 1.0 and later

• Tellabs® 6335 switch node release 1.3 and later




• All ETEX NEs

Step Action

1 Select Performance → Performance Data... in the pop-up menu of the relevant NE icon.

The Performance Data window appears.

18 MA276 • Rev. D1



Note: You can also control the data collection via the available operations forthe entities in the entity browser. Or you can use the operations directlyin the command line interface.

2 Select the Data Collection tab.

The Data Collection tab page is displayed.

3 Expand the tree structure and select the relevant monitor point to display the available operations.

Note: You cannot select more than one monitor point at a time.

The available buttons (corresponding to individual operations) are:

• Start

• Stop

• Get Status

• Report.

4 Click the relevant button.

The Directive View window appears for the selected operation.

For more information, see [3].

5 In the Directive View window, select Operations → Start to activate the operation.

When the operation has been performed, status information is dis-played in the output area of the Directive View window.

Step Action

MA276 • Rev. D1 19



To control data collection for an MTP on a 6310 or 6320



• Tellabs® 6310 edge node release 4.8 – 6.0.1


Step Action

1 Select Performance → Performance Monitoring... in the pop-up menu of the relevant NE icon.

The Performance Monitoring window appears.

2 Select the Source Selection → Monitor Points tabs.



4 Open the pop-up menu for the selected monitor point.

20 MA276 • Rev. D1




To control data collection for an MTP on a 6340 (FP1.0 to 3.x)


Note: The procedure is valid for Tellabs® 6340 switch node, releases 1.0 – 3.x.

5 Select one of the following options:

• Start

• Stop

• Get Status

• Report.



6 In the Directive View window, select Operations → Start button to ac-tivate the operation.

When the operation is complete, status information appears in the output area of the Directive View window.

Step Action

Step Action

1 Select Performance → Bit Error Counters... in the pop-up menu of the relevant NE icon.

The Bit Error Counters window appears.




MA276 • Rev. D1 21




2.4 Collecting Data from Individual Trails

Monitoring of trails The default monitoring of a trail is to monitor the trail’s end point TTPs. If,however, the trail ends in an ExternalMatrix, that TTP is replaced by the firstCTP in an NE matrix connected via an LC to the CTP in the ExternalMatrix.

In addition to the end point TTPs (or their replacements), it is also possible toset up monitoring of individual CTPs along the trail’s route, provided the NEcontaining the CTP supports non-intrusive monitoring. The data flow in theCTP can be monitored either in just one direction or in both (incoming andoutgoing); only the incoming data flow is monitored in an end point TTP.

The monitoring of the end point TTPs can only be stopped by stopping themonitoring of the whole trail, whereas the monitoring of the CTPs can bestopped individually. When you reconfigure a trail, monitoring is stopped forthose TPs that are no longer part of the trail’s route(s).


5 Select one of the following options:

• Start

• Stop

• Get Status

• Report.





Step Action

22 MA276 • Rev. D1



Note: The actual collection of performance data from trail and CTP is only ac-tivated when the trail is assigned (that is, in service).

When you set up monitoring of a trail, the monitoring relies on a MonitoredTPs list which indicates the specific TPs that are to be monitored. The defaultcontent is the two end point TTPs (or their replacement-CTPs if the end pointsare in ExternalMatrices). Each CTP that you specify monitoring for is addedto the list (with an indication of the data flow directions to be monitored). If aCTP at the edge of the network replaces one of the end point TTPs, the partic-ular CTP is automatically set to being monitored in both flow directions.

Note: When you monitor an Ethernet trail, 3 additional MTPs representingthe Ethernet (one for each Ethernet layer) will be added to each of themonitored end point TTPs. This means that the Ethernet - no clients,MPLS - in and MPLS-out trails are monitored.


The following operations can be used in connection with data collection fromtrails:

• Start performance collection

• Stop performance collection

• Get performance collection status

See ‘2.2 The Available Operations’ on page 16 for a description of the individ-ual operations. The recommended procedure for activating the operations isdescribed in ‘To control data collection for a whole trail’ on page 23.

To control data collection for a whole trail

This procedure describes how you activate the operations that allow you tocontrol the collection of performance data from a specific trail.

Note: For a new trail, you can start data collection directly in the Set Up Trailwindow while you are creating the trail.

Step Action

1 Search for the trail in the Find Trail window.

See [2] for a description of the Find Trail window and how to use it.

2 Move the mouse cursor to the name of the relevant trail and open the pop-up menu.

The pop-up menu is displayed.

MA276 • Rev. D1 23



3 Select the menu item Performance Monitoring to display the available operations.

The available menu items (corresponding to individual operations) are:

• Start if not started, and Stop if started.

• Get Status (NE)

• Get Status (Collection)

• Report

Step Action

24 MA276 • Rev. D1



4 To start or stop monitoring of a trail or to see the monitoring status, select the menu item for the required operation:

• To start monitoring of a trail which is not currently being moni-tored, select Start.

• To stop monitoring of a trail, select Stop.

• To see the current monitoring status of a trail, select Get Status (NE).

The trail view of the selected trail appears showing the trail in a state which corresponds to the selected operation.


See ‘Trail view states’ on page 26 for a description of the possible states of the trail view in connection with data collection.

The example in the figure above shows a trail for which the menu item Performance Monitoring → Get Status (NE) was selected.

In the trail view, you can perform one or more of the following pro-cedures:

• ‘To start monitoring of a CTP in one direction’ on page 27

• ‘To start monitoring of the second direction in a CTP’ on page 28

• ‘To stop monitoring of a CTP in one direction’ on page 29

5 To see the current collection status of the MTPs in the trail, select Get Status (Collection).

The Directive View window appears showing a list of the MTPs that are currently “active” or “stopping”.


Step Action

MA276 • Rev. D1 25



Note: You can also control the data collection via the available operations inthe entity browser. Or you can use the operations directly in the com-mand line interface.

Trail view states When you open trail view via one of the Performance Monitoring menu itemsin the Find Trail window, the trail will be displayed in one of the 3 possiblestates illustrated in the figure.

Note: Two examples are shown for state c): one without and one with non-in-trusive monitoring of a CTP.

Monitoring is indicated by In: and Out: text fields next to the monitored TTPsand CTPs. These fields are displayed when the menu item View → Perf MonTPs is active in the Trail View window.

Note: The Perf Mon TPs menu item is automatically activated when trail mon-itoring is started or when you look at the performance monitoring sta-tus.

Note: All In: and Out: text labels for TPs in a specific trail will be printed in thetrail’s performance report.

6 To create a report with the collected data, select Report.

The Performance Report window appears, as described in ‘3 Displaying the Performance Data’ on page 35.

Step Action

26 MA276 • Rev. D1



Note: The color of the frame around a text field indicates the monitor state(planned, partly active or active) of the related MTP.

To start monitoring of a CTP in one direction

This procedure describes how to start non-intrusive monitoring of one dataflow direction in a specific CTP in a trail.

Note: Starting monitoring from a CTP will automatically start monitoring forthe trail itself, if it is not already active.

The example used in the procedure is monitoring of the incoming data flow.

Step Action

1 In the Trail View window, open the pop-up menu for the CTP that you want to monitor.

2 Select the Monitor incoming menu item.

An empty In: text field appears next to the CTP.

3 To write text in the In: text field, double-click on the field to open it for editing.

MA276 • Rev. D1 27



To start monitoring of the second direction in a CTP

This procedure describes how to start non-intrusive monitoring of the seconddata flow direction in a CTP when the first direction is already being moni-tored.

The example used in the procedure continues the example in ‘To start moni-toring of a CTP in one direction’ on page 27, showing how to add monitoringof the outgoing data flow.

4 Type the required text in the text field and then press Enter.

The text field contains the specified text.

Step Action

Step Action

1 In the Trail View window, open the pop-up menu for the CTP.

2 Select the Monitor outgoing menu item.

An empty Out: text field appears next to the CTP’s existing In: field.

28 MA276 • Rev. D1



To stop monitoring of a CTP in one direction

This procedure describes how to stop non-intrusive monitoring of one of thedata flow directions in a CTP which has previously been monitored in both di-rections.

In the example, monitoring of the incoming data flow is stopped.

3 To write text in the Out: text field, double-click on the field to open it for editing.

4 Type the required text in the text field and then press Enter.

The text field contains the specified text.

Step Action

Step Action

1 In the Trail View window, open the pop-up menu for the relevant CTP.

MA276 • Rev. D1 29



Trail Log entries When trail monitoring is started or stopped, the following information is en-tered in the Trail Log:

• From start monitoring:

• Trail ID

• Date and time of operation

• Operator ID

• Resulting management state of trail

• Any additional and error information.

• From stop monitoring:

• Trail ID

• Date and time of operation

• Operator ID

• Resulting management state of trail

• Any additional and error information.

2 Select the Monitor incoming menu item.

The In: text field disappears from the CTP, indicating that the incom-ing data flow is no longer monitored.

Step Action

30 MA276 • Rev. D1



2.5 Collecting Data from Concatenated Trails

Monitoring of concatenated trails

The monitoring of a concatenated trail (that is, a collection of trails) is actuallya monitoring of the virtual concatenation groups (VCGs) that terminate theconcatenated trail.


The following operations can be used in connection with data collection fromconcatenated trails:

• Start performance collection

• Stop performance collection

• Get performance collection status

See ‘2.2 The Available Operations’ on page 16 for a description of the individ-ual operations. The recommended procedure for activating the operations isdescribed in ‘To control data collection for concatenated trails’ on page 31.

To control data collection for concatenated trails

This procedure describes how you activate the operations that allow you tocontrol the collection of performance data from a specific set of concatenatedtrails.

Note: For a new set of concatenated trails, you can start data collection direct-ly in the Set Up Trail window while you are creating the trails.

Step Action

1 Search for the concatenated trails in the Find Trail window.

See [2] for a description of the Find Trail window and how to use it.

2 Move the mouse cursor to the name of the relevant trail set and open the pop-up menu.

The pop-up menu is displayed.

3 Select the menu item Performance Monitoring to display the available operations.

The available menu items (corresponding to individual operations) are:

• Start/Stop (depending on the present state of the collection)

• Get Status (Collection)

• Report

MA276 • Rev. D1 31



Note: You can also control the data collection via the available operations inthe entity browser. Or you can use the operations directly in the com-mand line interface.

To control data collection for VCGs

This procedure describes how you start data collection for a new VCG.

4 To start or stop monitoring of a concatenated trail, select the menu item for the required operation:

• To start monitoring of a concatenated trail which is not currently being monitored, select Start.

• To stop monitoring of a concatenated trail, select Stop.

The corresponding operation is started and a message reporting the start of the operation is displayed.

5 To see the current monitoring status of a concatenated trail, select Get Status (Collection).

The Directive View window appears showing a list of the VCGs that are currently “active” or “stopping”.


6 To create a report with the collected data, select Report.

The Performance Report window appears.

For more information, see ‘3 Displaying the Performance Data’ on page 35.

Step Action

Step Action

1 In the Setup Packet Link window, select the Perf. Mon check box in the VCG Parameters group box.

Monitoring of the new VCG starts directly when it is created.

32 MA276 • Rev. D1



2.6 Using the Command Line Interface

What to use it for Using the command line interface makes it possible to activate one of the datacollection operations for several entities at the same time.

Telling the operation which entities to control

The table describes what the required parameter for a data collection opera-tion is, depending on how many and which type of entities you want to con-trol with the same operation.

Note: You can also combine the use of wildcards.Example: ‘AC1_30 * vc4TTPBidirectional *’ specifies all VC4MTPs in all AC1_30 NEs.

An operation for ...

requires the specification of ...

a single MTP the MTP’s name.Example:AC1_30 .east vc4TTPBidirectional 1-1-20-2

all MTPs of a specific type in a single NE

the MTP type and a wildcard.Example: AC1_30 .east vc4TTPBidirectional *

all MTPs in a specific NE

the NE’s name.Example:AC1_30 .east

all NEs of a spe-cific type

the NE type and a wildcard.Example:AC1_30 *

all CTP-related MTPs in a specif-ic trail

the trail’s name and all MTP names (identified as in-coming or outgoing direction).Example:startmonitoring <trail> incoming monitor -TPs=<Full list of relevant CTPs>, outgoing monitor -TPs=<Full list of relevant CTPs>

all MTPs in a specific trail

the trail’s name.Example:LND vc4 TRAIL east-west

MA276 • Rev. D1 33



Examples of operations The figure shows some examples of operations activated via the commandline interface.

34 MA276 • Rev. D1


3 Displaying the Performance Data


Overview This describes how to create reports from the collected performance data. Thereport is displayed in a separate window, the Performance Report window,which is described in ‘3.1 The Window in which the Data is Displayed’ onpage 35.

3.1 The Window in which the Data is Displayed

What does the window contain?

The Performance Report window shown in the figure is used to display theperformance report for either a single MTP or for all the MTPs in a specifictrail.

The window contains 3 areas:

• The search filter area, in which you define the search criteria that are used to determine which performance data are shown in the data area. See ‘3.2.2 Using the Search Filter’ on page 41 for a description of this area and how to use the filter.

• The data area, in which the performance report is displayed. See ‘1.3 The Performance Data Reports’ on page 13 for a description of what is dis-played in this area.

• The button panel, which contains the buttons for starting the search for the data and for printing the report shown in the data area. See ‘3.3 How to Print the Reports’ on page 44 for a description of how to print perfor-mance reports.

MA276 • Rev. D1 35



3.2 How to Create the Reports

Overview This section contains the following information:

• ‘3.2.1 Creating Reports’ on page 36

• ‘3.2.2 Using the Search Filter’ on page 41

3.2.1 Creating Reports

To create a report for an MTP on a 6315, 6325, 6335, 6340 (FP4.0 or later), 6345 or 6350

This procedure describes how you create a report with the data collected froma specific MTP.


• Tellabs® 6315 metro ethernet node release 1.0 and later

• Tellabs® 6325 edge node release 1.0 and later





• All ETEX NEs

Step Action

1 Select Performance → Performance Data... in the pop-up menu of the relevant NE icon.

The Performance Data window appears.

2 Select the Data Collection tab and then select the relevant MTP in the tree structure.

The operation buttons are available.

3 Click the Report button.

The Performance Report window appears.

For more informaiton, see the figure in ‘What does the window con-tain?’ on page 35.

36 MA276 • Rev. D1



Note: You can print the displayed report either to a file or directly on a print-er, as described in ‘3.3 How to Print the Reports’ on page 44.

To create a report for an MTP on a 6310 or 6320





4 Set up the search filter criteria for the report data, as described in ‘3.2.2 Using the Search Filter’ on page 41.

5 Click on the Search button.

The requested data are displayed as a report in the data area. See ‘1.3 The Performance Data Reports’ on page 13 for a description of the report layout.

Step Action

Step Action

1 Select Performance → Performance Monitoring... in the pop-up menu of the relevant NE icon.

The Performance Monitoring window appears.




MA276 • Rev. D1 37



Note: You can also create a report via the available operations for the entitiesin the entity browser. Or you can use the operations directly in the com-mand line interface.

To create a report for an MTP on a 6340 (FP1.0 to 3.x)


Note: The procedure is valid for Tellabs® 6340 switch node, releases 1.0 – 3.x.


5 Select Report in the pop-up menu.

The Directive View window appears for the selected operation (see [3] for a description).



Step Action

Step Action

1 Select Performance → Bit Error Counters... in the pop-up menu of the relevant NE icon.

The Bit Error Counters window appears.

38 MA276 • Rev. D1



Note: You can also create a report via the available operations for the entitiesin the entity browser. Or you can use the operations directly in the com-mand line interface.





5 Select Report in the pop-up menu.

The Directive View window appears for the selected operation (see [3] for a description).



Step Action

MA276 • Rev. D1 39



To create a report for a trail

This procedure describes how you create a report with the data collected fromall MTPs in a specific trail.


Step Action

1 Search for the trail in the Find Trail window (see [2]).

2 Select the name of the trail and open the pop-up menu.

3 Select the menu item Performance Monitoring → Report.

The Performance Report window appears (see the figure in ‘What does the window contain?’ on page 35).




40 MA276 • Rev. D1



To create a report for a concatenated trail

This procedure describes how you create a report with the data collected fromall MTPs in a specific concatenated trail.


3.2.2 Using the Search Filter

The search criteria The search filter area shown in the figure is used to set up filtering criteria forthe information that will be displayed in the performance report.

The area gives you 3 filtering options:

• Specifying which monitored entity you want to see the performance data for in the report. See ‘To specify the entity whose data you want to see’ on page 42. The default contents of the Entity field is the name of the entity chosen when the Performance Report window was opened.

Step Action

1 Search for the concatenated trail in the Find Trail window (see [2]).

2 Select the name of the specific concatenated trail and open the pop-up menu.

3 Select the menu item Performance Monitoring → Report.

The Performance Report window appears (see the figure in ‘What does the window contain?’ on page 35).




MA276 • Rev. D1 41



• Specifying the collection period for the performance data that are to be shown in the report. See ‘To specify the collection period for the data’ on page 42.

• Specifying the type of the performance data in the report (15-minute counters, 24-hour counters or gauges). See ‘To specify the type of perfor-mance data’ on page 43.

To specify the entity whose data you want to see

This procedure describes how you specify which monitored entity’s data youare interested in.

Note: The default setting is the entity from which you opened the Perfor-mance Report window. So if you want to see that entity’s data, you donot need to use this procedure.

To specify the collection period for the data

This procedure describes how you specify the collection period of the perfor-mance data that will be shown in the report.

Note: When you open the Performance Report window, the start time and theend time of the period are both set to the current date and time.

Note: The following rules apply for the start time and end time entries:

• You must specify the year within the range of maximum 5 years going back from the current year.

Step Action

1 Enter the full name of the required trail in the Entity field.

When you press the Search button, the entity name in the headlines of the Performance Report window and the Print Performance Data Report window changes, and the performance data report for the specified entity is displayed.

Step Action

1 Set the required start time and end time using the following meth-ods:

• Specify year, day, hour and minute either by clicking on the up and down arrow buttons alongside the fields or by entering the values manually.

• Specify the month by clicking on the down arrow button along-side the field and selecting the month from the drop-down list.

42 MA276 • Rev. D1



• The valid day specifications depend on the month and year, taking into account the number of days in a particular month and leap years.

• You must specify the time with hour indication between 0 and 23. That is, twelve hour intervals with ‘AM’ and ‘PM’ notification are not used.

• You must specify the minute within the range of 0 to 59.

To specify the type of performance data

This procedure describes how you specify which type of performance data areshown in the report (counter data or gauge data).

Step Action

1 Click on the down arrow button alongside the Performance Data Type field and select the required data type from the list.

The possible data types are:

• 15 minute counters (the default value)

• 24 hour counters

• gauges

MA276 • Rev. D1 43



3.3 How to Print the Reports

To print the performance report on your printer

This procedure describes how you can print the currently displayed perfor-mance report on your default printer.

Step Action

1 Click on the Print button at the bottom of the Performance Report window.

The Print window appears.

The default print setting is to send all pages of the report to your de-fault printer.

2 If you want to use another printer, select the relevant printer in the Select Printer field.

3 If you want to use a printer which is not listed, click Find Printer... and locate the printer in the Find Printers window.

44 MA276 • Rev. D1



See ‘Example of a printed performance report’ on page 48 to get an idea ofwhat a printed performance report looks like.

To print the performance report to a file

This procedure describes how you can print the currently displayed perfor-mance report to a report file.

4 If you want to change the settings of the selected printer, click Prefer-ences and set up the printer in the Printing Preferences window.

5 To print the report, click Print in the Print window.

The performance report is sent to the printer.

Step Action

Step Action



The default print setting is to send the report to your default printer.

MA276 • Rev. D1 45



To print the performance report to a text file

This procedure describes how you can print the currently displayed perfor-mance report to a ASCII text file.

2 Select the Print to File check box and click Print.

The Print to File window appears.

3 Specify the name and location of the report file in the Output File Name field and click OK.

The performance report is saved as the specified file.

Step Action

46 MA276 • Rev. D1



Note: A text file contains gauge values, such as the temperatures of the opticaltransceivers. And you are able to use the copy and paste functionswhen you want to reuse the information present in the report.

Step Action



The default print setting is to send the report to your default printer.

2 Select the Generic/ Text only printer in the Select Printer list.

Note: If this printer is not present, then use the standard Windowsprocedure to add a local printer.

3 Select the Print to file check box.

4 Click Print.

The Print to File window appears.

5 Specify the name and location of the report file in the Output File Name field and click OK.

The performance report is saved as the specified text file.

MA276 • Rev. D1 47



Example of a printed performance report

The figure shows an example of a printed performance report for a trail.

48 MA276 • Rev. D1


4 Exporting Performance Data


Overview This describes how to export data from the performance monitoring databaseinto comma-separated files. The syntax of the command used for the export isdescribed, as well as the format of the output data.

4.1 Creating Files with Performance Data

Report data in comma-separated files

The data collected by performance monitoring can be output into comma-sep-arated data files, which can then be transferred to a database or analysis tool.

The UNIX command to extract performance data

The UNIX command that you can use to generate performance data files hasthe following syntax:

dbextract Starttime Endtime Countertype [ Trailname [ MTPname [ -sdh -exact -show-sql ]]] > outputfile

Where:

Starttime indicates the start time of the required period. Use the following for-mat: ‘yyyy-mm-dd hh:mm:ss’. All parts must be filled in. The selected periodsend after this time. Time is in UTC.

Endtime indicates the end time of the required period. Use the following for-mat: ‘yyyy-mm-dd hh:mm:ss’. All parts must be filled in. The selected periodsbegin before this time. Time is in UTC.

Countertype indicates the required counter type. Use one of the following val-ues:

• 0 to request 15-minute counters

• 1 to request 24-hour counters

• 2 to request gauge counters (these are available for optical ports only)

• 3 to request all counters

Trailname is an optional argument, and indicates the required trail name. InTrailname the wildcard symbol ‘%’ can be used to indicate the remaining partof the name.

MTPname is an optional argument, and indicates the required MTP name. InMTPname the wildcard symbol '%' can be used to indicate the remaining partof the name. Note that if you specify MTPname, the Trailname must also bespecified.

-sdh is an optional argument that limits the contents of the output. See ‘TheSDH data file’ on page 51.

-exact is an optional argument, and indicates that the white spaces in Trail-name and MTPname must be matched exactly as given.

-show-sql is an optional argument, and indicates that SQL statements willbe logged.

outputfile indicates the name of the file in which data is stored. “dbextract”sends data to standard output if not redirected to a file using > outputfile.

The contents and format of the data file generated by performance monitoringin response to this command is described in ‘4.2 The Generated PerformanceData File’ on page 50.

MA276 • Rev. D1 49



Location of the command The command is located in the directory: “/usr/opt/temip/nm2000/sub-sys/pmon/lib/pmdbif”.

Scheduling of the command

You can schedule the execution of the “dbextract” command by putting it inthe “crontab” file.

Examples Two examples of the “dbextract” command, with the current directory as de-scribed in ‘Location of the command’ on page 50:

The first example extracts 24-hour counters from all MTPs:

./dbextract '2001-05-04 00:00:00' '2001-05-04 00:00:01' 1> /tmp/mylog

The output will be the 24-hour periods which include the time 2001-05-0400:00:00. The output will be stored in the file “/tmp/mylog”.

The second example extracts 15-minute counters from specific MTPs:

./dbextract '2002-06-12 08:00:05' '2002-06-12 10:25:00' 0‘%’ ‘AC4_50 london%’ > /tmp/mylog

The output will be the counters for all MTPs in the NE AC4_50 london. Theoutput will be stored in the file “/tmp/mylog”.

4.2 The Generated Performance Data File

The default data file The default performance data file generated by the “dbextract” command (de-scribed in ‘The UNIX command to extract performance data’ on page 49) con-tains lines for all monitored termination points (MTPs) for which there aredata of the specified type for the specified time in the performance database.

Each entry in the data file has the following format and contents:

<MTPid>,<NwtpName>,<Trailname>,<Label>,<Timestamp>,<Period>,<Layer>,<FarEnd>,<BBE>,<ES>,<SES>,<UAS>,<SuspectFlag>,<ElapsedTime>,<framesRx>,<octetsRx>,<dropFramesRx>,<DiscFramesRx>,<framesTx>,<octetsTx>,<dropFramesTx>,<DiscFramesTx>,<BAR>,<FCSErrors>,<GfptHECErrors>,<GfpcHECErrors>,<LapfLMILinkRel>,<LapfLMIProtErrs>,<LapfLMIInac-tErrs>,<lostFrames>,<lostOctets>

The individual fields are separated by a comma. Data in strings is enclosed insingle quotes. NULL is represented by a space. One data source is uniquelyidentified by (<MTPid>, <Layer>).

Note: When countertype 0 or 1 is selected, then a fixed number of data fields(see above) are displayed for all the NE classes. When countertype 2 or 3is selected, then the number of data fields displayed is dynamic. EachNE class has its own set of counters. The number of data fields dis-played changes to reflect the individual NE classes.

See a description of the fields in ‘The fields in the data file’ on page 52.

Not all counters are relevant for all MTPs.

Note: Some of the Ethernet-related counters are relevant only for MTPs atspecific data sublayers.

50 MA276 • Rev. D1



The SDH data file The SDH performance data file (generated by a “dbextract” command withthe -sdh argument) contains information about the following counters: BBE,ES, SES and UAS.

Each entry in the data file has the following format and contents.

<MTPid>,<NwtpName>,<Trailname>,<Label>,<Timestamp>,<Period>,<Layer>,<FarEnd>,<BBE>,<ES>,<SES>,<UAS>,<SuspectFlag>,<ElapsedTime>

See a description of the fields in ‘The fields in the data file’ on page 52.

The contents of an all counters data file

The all counters data file contains information for all the counters presentwithin the time period defined. The output contains the same counter infor-mation as if counter type options 0, 1 and 2 were used successively.

Note: The fields present in the all counters data file are dynamic. Only thosefields relevant to those counters are present. Therefore, for more infor-mation, see the information about the contents of the data files forcounter type options 0, 1 and 2.

MA276 • Rev. D1 51



The fields in the data file The table describes the individual fields in the report file.

Note: Some of the Ethernet-related counters are relevant only for MTPs atspecific data sub-layers.

Field Type Description

<MTPid> String The name of the monitored TP. This is the pri-mary sort key.Example: 'LX_20 ROME_LX_20 vc4TTPBidirectionalR2 1-2-6-1'

<NwtpName> String Name of the monitored TP in Trail View.

<Trailname> String The name of the monitored trail. This data item is included only if the collection of per-formance data was started from a trail, other-wise NULL.

<Label> String The label (as given in Trail View) for the MTP at the specific time.

Note: Labels are only relevant for MTPs dur-ing trail monitoring.

<Timestamp> String The start time of the period. The following format is used: ‘yyyy-mm-dd hh:mm:ss’. Time is in UTC. This is the secondary sort key.

<Period> Integer The length of the period, estimated by perfor-mance monitoring, in number of seconds.

<Layer> Integer An indication of the network layer. The possi-ble values are: 0 = Ph, 1 = RS, 2 = MS, 3 = VC-4, 4 = VC-3, 5 = VC-12, 7 = VC-11, 9 = OMS, 10 = OCH, 11 = DS3, 12 = DS1, 13 = Data.

<FarEnd> Integer Indicates if it is a far end counter (1 = far end; 0 = near end).

<BBE> Integer The value of the Background Block Errors counter.

<ES> Integer The value of the Errored Seconds counter.

<SES> Integer The value of the Severely Errored Seconds counter.

<UAS> Integer The value of the UnAvailable Seconds counter.

<SuspectFlag> Integer An indication of the validity of the entry. The possible values are: 0 = OK, 1 = suspect, 2 = Zero suppressed data.

<ElapsedTime> Integer The elapsed time estimated by the NE, in number of seconds. NULL if not supported by equipment.

<framesRx> Integer The number of payload frames that are re-ceived OK.

52 MA276 • Rev. D1



<octetsRx> Integer The number of payload octets that are re-ceived.

<dropFrames-Rx>

Integer The number of bad payload frames that are received.

Note: This counter is only relevant for MTPsat the mapping, MPLS terminated and MPLSnon-intrusive layers.

<DiscFrames-Rx>

Integer The number of bad payload frames that are received.

Note: This counter is only relevant for MTPsat the Ethernet MAC layer.

<framesTx> Integer The number of payload frames that are trans-mitted.

<octetsTx> Integer The number of payload octets that are trans-mitted.

<drop-FramesTx>

Integer The number of payload frames that are not transmitted.

Note: This counter is only relevant for MTPsat the MPLS terminated and MPLS non-intru-sive layers.

<Disc-FramesTx>

Integer The number of payload frames that are not transmitted.

Note: This counter is only relevant for MTPsat the Ethernet MAC layer.

<BAR> Integer The value of the Bandwidth Availability Ra-tio counter (percentage).

Note: This counter is only relevant for MTPsat the mapping layer.

<FCSErrors> Integer The value of the Frame Check Sequence Er-rors counter.


<GfptHECEr-rors>

Integer The value of the GFP Type Header Error Check Errors counter.


<GfpcHECEr-rors>

Integer The value of the GFP Core Header Error Check Errors counter.



MA276 • Rev. D1 53



The contents of a 24-hour counter file

Each line in the file contains data for a 24-hour period. <Timestamp> definesthe start time and <Period> defines the length of the period in seconds.Lines may have NULL values in fields after the <Layer> field. That means thatthere is no data for the counter or counters.

The contents of a 15-minute counter file

Each line in the file contains data for a period. <Timestamp> defines the starttime and <Period> the length of the period in seconds. If the period from oneline does not end at the start time of the next line for the same data source, theperformance database does not contain information for the missing interval.If all the counters are zero for a complete polling period and the <SuspectFlag>is OK, the fields after <Layer> will be NULL. <Timestamp> and <Period> definethe period.

Note: This special case where all counter values are zero, is marked by giving<SuspectFlag> the value 2.

If all the counters are the same in more than one 15-minute period, the com-plete period up to one polling period is represented by 1 line, where <Period>defines the complete period and the counter values show the value for one 15-minute period. The polling period depends on the type of network element.

Counter values that were not available during the collection, are indicated as“ “ (blank). For instance, if both the MS and the VC-4 trail layers are handledby the same MTP, the VC-4 trail counters are not available if the trail is not ter-minated.

<LapfLMI-LinkRel

Integer The value of the LAPF LMI Link Reliability Errors counter.


<LapfLMIProt-Errs>

Integer The value of the LAPF LMI Protocol Errors counter.


<LapfLMIInac-tErrs>

Integer The value of the LAPF LMI Inactive Errors counter.


<lostFrames> Integer The number of frames lost between 2 ETHS monitoring points.

<lostOctets> Integer The number of octets lost between 2 ETHS monitoring points


54 MA276 • Rev. D1



Example The figure shows an example of a 15-minute counter data file

MA276 • Rev. D1 55



56 MA276 • Rev. D1


A Attributes Connected to Monitoring


Overview This chapter describes the attributes related to monitoring of trails.

• ‘A.1 Trail Attributes’ on page 57

• ‘A.2 TTP Attributes’ on page 58

• ‘A.3 CTP Attributes’ on page 58

• ‘A.4 VCG Attributes’ on page 59

• ‘A.5 How the TPs’ Monitoring State Attribute Changes’ on page 60

A.1 Trail Attributes

Monitored TPsContains a list of all TTPs and CTPs in the trail that are currently being moni-tored or are planned to be monitored (that is, all TTPs and CTPs whose Moni-toring State attributes have the value planned, active or partly active).

Monitored VCGsContains a list of all VCGs in the concatenated trail that are currently beingmonitored or are planned to be monitored (that is, all VCGs whose MonitoringState attributes have the value planned, active or partly active).

Monitoring StateIndicates whether the trail is being monitored or not (that is, whether the TPslisted in the trail’s Monitored TPs attribute are being monitored or not (see‘Monitored TPs’ on page 57)).

Monitoring SetIndicates the type of monitoring of the trail.

Value Description

none No TPs in the trail are either being moni-tored or planned to be monitored. The trail’s Monitored TPs attribute is empty.

planned All TPs listed in the trail’s Monitored TPs attribute have the Monitoring State value planned.

active All TPs listed in the trail’s Monitored TPs attribute have the Monitoring State value active.

partly active Some of the TPs listed in the trail’s Moni-tored TPs attribute have the Monitoring State value partly active.

Value Description

oam OAM monitoring enabled.

MA276 • Rev. D1 57



Note: SDH trails allow only OAM monitoring while data trails (except MPLStrails) allow only statistics monitoring. MPLS trails allow both types ofmonitoring.

A.2 TTP Attributes

Monitoring StateIndicates whether the TTP is being monitored or not.


A.3 CTP Attributes

Monitoring StateIndicates for each of the two data flow directions (incoming and outgoing)whether the CTP is being monitored or not.

statistics Statistics monitoring enabled.

Value Description

Value Description

none The TTP is neither monitored nor planned to be monitored.

planned The TTP will be monitored when the trail is assigned.

active The TTP is being monitored.

partly active It is not known whether monitoring is en-abled or disabled.

Value Description



Direction Value Description

incoming: none The CTP is neither monitored nor planned to be monitored in the incoming direction.

planned The CTP will be monitored in the incoming direction when the trail is assigned.

active The CTP is being monitored in the incom-ing direction.

partly active It is not known whether monitoring is en-abled or disabled in the incoming direction.

58 MA276 • Rev. D1



Monitoring SetIndicates for each of the two data flow directions (incoming and outgoing) thetype of monitoring of the trail.

A.4 VCG Attributes

Monitoring StateIndicates whether the VCG is being monitored or not.


outgoing: none The CTP is neither monitored nor planned to be monitored in the outgoing direction.

planned The CTP will be monitored in the outgoing direction when the trail is assigned.

active The CTP is being monitored in the outgo-ing direction.

partly active It is not known whether monitoring is en-abled or disabled in the outgoing direction.

Direction Value Description

Value Description



Value Description

none The VCG is neither monitored nor planned to be monitored.

planned The VCG will be monitored when the trail is assigned.

active The VCG is being monitored.

partly active It is not known whether monitoring is en-abled or disabled.

Value Description



MA276 • Rev. D1 59



A.5 How the TPs’ Monitoring State Attribute Changes

TP Monitoring State for assigned/deassigned/reconfigured trail

When a monitored trail is assigned, deassigned or reconfigured, the Monitor-ing State attribute for the affected TPs changes as described in the table.

TP Monitoring State when trail monitoring is started

When monitoring is started for a specific trail, the monitoring-related at-tributes change as described in the table.

TP Monitoring State when trail monitoring is stopped

When monitoring of a specific trail is stopped, the monitoring-related at-tributes change as described in the table.

When the trail is ... then TP Monitoring State ...

assigned planned and partly active change to

• active when monitoring is enabled in NEs.

• partly active when monitoring could not be enabled in NEs.

deassigned active and partly active change to

• planned when monitoring is disabled in NEs.

• partly active when monitoring could not be disabled in NEs.

reconfigured (rerout-ed/groomed/unprotected)

changes to none for those TPs that are no longer part of the trail.

If the trail is ... when trail monitoring is started then ...

not in service The Monitoring State of all new TPs added to the Moni-tored TPs list is set to planned for each monitored data flow direction.

in service Monitoring is enabled in NEs for all TPs in the Moni-tored TPs list with Monitoring State value planned or partly active. If enabling is a success, the Monitoring State is set to active; if enabling is not possible, the Monitoring State is set to partly active.

If the trail is ... when trail monitoring is stopped then ...

not in service • Monitoring is disabled in the NEs for all TPs in the Monitored TPs list with Monitoring State value partly active.

• All TPs with Monitoring State value planned are set to none. All partly active TPs in NEs where monitoring is successfully disabled are set to none.

60 MA276 • Rev. D1



in service Monitoring is disabled in the NEs for all TPs in the Mon-itored TPs list with Monitoring State value active or part-ly active. If disabling in the NE is a success, the Monitor-ing State is set to none and the TP is removed from the list; if disabling in the NE is not possible, the Monitoring State is set to partly active.

If the trail is ... when trail monitoring is stopped then ...

MA276 • Rev. D1 61



62 MA276 • Rev. D1


Index

Index

AAbbreviations 8Arial font

use of 8Arrows

use of 8

BBit Error Counters window

using 21, 38Bold

use of 8

CCollection of data 10, 15

check status 17start 16stop 16

Collection Period partin Performance Report window 42

Command line interfaceusing 33

Comma-separated filecreating 49fields 52format 50SDH format 51

Concatenated trailscreating report for 41

Counters15-minute 1024-hour 10

DData

check status of collection 17check status of MTP 17collecting 10, 15definition 9displaying in report 35operations for collecting 16output in comma-separated file 49recovery of 11reports 13resume collection of 17start collection of 16stop collection of 16suspend collection of 17

Data collectionfor a 6310 20, 37for a 6315 18for a 6320 20, 37for a 6325 18for a 6335 18for a 6340 18, 21, 38for a 6345 18for a 6350 18operations possible 18

Data file fields 52Data file format 50Data file SDH format 51Data time 11dbextract command

location 50syntax 49

EEntities being monitored 9Entity field

in Performance Report window 42

FFields in data file 5215-minute counter file 5415-minute counters 10File

fields 52format 50printing reports to 45SDH format 51

Filterusing 41

Find Trail windowusing 23, 31, 40, 41

Format of data file 50Format of SDH data file 51

GGauges 10Get Performance Collection Status operation 17Get Status (Collection) menu item 24, 31Get Status (NE) menu item 17, 24Get Status button

in Performance Data window 19

MA276 • Rev. D1 63


Index

IItalics

use of 8

LLayout of reports 13

MManual

structure of 7style conventions 8

Monitor incoming menu item 27, 30Monitor outgoing menu item 28Monitored entities 9MTPs

collecting data from individual MTPs 18controlling many 33creating report for 36

NNetwork elements

controlling many 33

OOperations 16

parameters for 33Overview of performance monitoring 9

PPerformance data

fields in data file 52file format 50SDH file format 51see Data

Performance Data Type fieldin Performance Report window 43

Performance Data windowusing 18, 20, 36, 37

Performance Monitoring menu itemin Find Trail window 24, 31, 40, 41

Performance Report window 35search filter 41using 36, 40, 41

Performance reportssee Reports

Polling 10Print button

in Performance Report window 44Print window

using for performance report 44using for report file 45, 47

Printerprinting reports to 44

Printing performance reports 44to a text file 46to file 45to printer 44

QQuotation marks

use of 8

RRecovery of data 11References 8Report button

in Performance Data window 19, 36Report menu item

in Find Trail 31in Find Trail window 24, 40, 41

Reportscreating 35description 13in comma-separated files 49layout 13printing 44types 13

Requirements 10Resume Performance Collection operation 17

SSearch filter

using 41Start button

in Performance Data window 19Start menu item

in Find Trail 31in Find Trail window 24

Statistics 10Status of entity 17Status of MTP 17Stop button

in Performance Data window 19Stop menu item

in Find Trail 31in Find Trail window 24

Suspend Performance Collection operation 17Syntax for UNIX command 49

TText file

printing reports to 46Time indication 11

64 MA276 • Rev. D1


Index

Trailscollecting data from concatenated trails 31collecting data from individual trails 22controlling many 33creating report for 40creating report for concatenated 41

24-hour counter file 5424-hour counters 10

UUNIX command

location 50syntax 49

VVCGs

collecting data from VCGs 31

MA276 • Rev. D1 65


Index

66 MA276 • Rev. D1

Tellabs OSN2

Documents

Transcript of Tellabs OSN2