Tellabs OSN2 PDF

Technical Documentation
Product family Tellabs® 6300 Managed

Transport System
Product name Tellabs® 6300 Network Manager
Title Monitoring Performance
Document User’s Manual

MA276 / Revision D1
Copyright © 2002-2007, 2009 Tellabs. All rights reserved.

Tellabs® 6300 Network Manager Legal Notices
Monitoring Performance
Legal Notices
Copyright Statement This Tellabs manual is owned by Tellabs or its licensors and protected by U.S.
and international copyright laws, conventions, and treaties. Your right to use
this manual is subject to limitations and restrictions imposed by applicable li-
censes and copyright laws. Unauthorized reproduction, modification, distri-
bution, display or other use of this manual may result in criminal and civil
penalties.
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: AUDIO
PLUS®, 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®, THE
WORLD COMMUNICATES THROUGH TELLABS™, TITAN®, VERITY™,
YOUR NETWORKING PARTNER®.
Any other company or product names may be trademarks of their respective
companies.
2 MA276 • Rev. D1
Tellabs® 6300 Network Manager Revision Information
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
Tellabs® 6300 Network Manager Revision Information
Rev. Date Description of Changes
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.
4 MA276 • Rev. D1
Tellabs® 6300 Network Manager Contents
Legal Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Revision Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Description of Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . 9

1.1 A General Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2 The Collection of the Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 The Performance Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 Collecting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.2 The Available Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3 Collecting Data from Individual Monitored Termination Points . . . . . . . 18
2.4 Collecting Data from Individual Trails . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.5 Collecting Data from Concatenated Trails . . . . . . . . . . . . . . . . . . . . . . 31
2.6 Using the Command Line Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3 Displaying the Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . 35

3.1 The Window in which the Data is Displayed . . . . . . . . . . . . . . . . . . . . 35
3.2 How to Create the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2.1 Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.2.2 Using the Search Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3.3 How to Print the Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4 Exporting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4.1 Creating Files with Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . 49
4.2 The Generated Performance Data File . . . . . . . . . . . . . . . . . . . . . . . . 50
A Attributes Connected to Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 57

A.1 Trail Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
A.2 TTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
A.3 CTP Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
A.4 VCG Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
A.5 How the TPs’ Monitoring State Attribute Changes . . . . . . . . . . . . . . . . 60
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
MA276 • Rev. D1 5
Tellabs® 6300 Network Manager Contents
6 MA276 • Rev. D1
Tellabs® 6300 Network Manager Preface
Preface
Overview Using performance monitoring, you can collect performance data for as well
individual 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 corresponds
to your current product version.
The structure of this The manual is structured as follows:

manual
• ‘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
Tellabs® 6300 Network Manager 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 group
that the word represents (example: NE type). If the words are substituted
by 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 how
to select a certain menu item (example: Select Performance Monitoring →
Report).
Abbreviations BBE Background Block Errors

CTP Connection Termination Point
ES Errored Seconds
LND Layer Network Domain
MTP Monitored Termination Point
NE Network Element
OAM Operation, Administration and Maintenance
SES Severely Errored Seconds
TTP Trail Termination Point
UAS UnAvailable Seconds
UTC Universal Time Co-ordinates
VCG 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 Entity
Browser, User’s Manual
8 MA276 • Rev. D1
Tellabs® 6300 Network Manager 1 Description of Performance Monitoring
1 Description of Performance Monitoring
Overview The basic principles behind performance monitoring are described and some
concepts that are used in the rest of the manual are introduced.
We assume that you are familiar with the concepts described in the Element
Management manuals and in the manual describing network traffic manage-
ment (see [2]).
1.1 A General Overview
What is performance The performance monitoring facility collects performance data from Tellabs
monitoring? 6300 manager and stores the data in an SQL database. The collected data can
then 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 (incoming
or 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, you
must 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 gauge
values.
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 one
starting 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 the
counters, indicating the covered interval.
Note: ETEX NEs and SDH ETEX NEs follow different times. ETEX NEs can
only follow UTC time while SDH ETEX NEs typically are configured to
follow server time.
Gauges The gauge values are collected each time performance monitoring polls for
data. 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 statistics
data.
Polling The NEs store performance counters for a limited period. Typically, an NE can
store 15-minute counters for 24 hours. With regular intervals, 6300NM perfor-
mance monitoring polls the NEs for these data. The time interval between two
polls 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 and
16:00.
When performance monitoring polls for data, all the 15-minute counters from
the previous polling period are retrieved. After a poll, the data are stored in
the 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 the
end 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 that
no 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 show
the 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 the
equipment uses local time, the server time is converted to UTC time.
Note: The time stamp shown in a dbextract report is UTC time. The time
stamp used in the GUI is server time.
Example for 24-hour counters: ETEX NEs, which can only run UTC, will on a
Danish server during summertime (UTC+2) have the dbextract time stamp
00: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 server
have the dbextract time stamp 22:00:00 and the GUI time stamp 00:00:00.
Illustration of data time This figure illustrates how the time stamps differ depending on whether the
stamps in dbextract and performance data is viewed using dbextract or using the 6300NM GUI.
GUI
Recovery of data after If data communication problems occur or if the system shuts down, no data
collection failure are collected for a period of time. When data collection is again possible, the
performance monitoring function will attempt to recover the missing data by
sending a request for the data to the network elements. However, it is only
possible to recover data from maximum 3 previous polling periods.
Example of 15-minute The figure shows an example of 1-hour polling for 15-minute counters. At
counter collection 01: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 polling
has completed, these counters are available.
Note: The figure also shows the time flow of the collection of counters. At
00:15, the counter started at 00:00 is stored. At 00:30, the counter started
at 00:15 is stored. And so on.
Example of 24-hour The figure shows an example of 24-hour counter collection with a polling pe-
counter collection riod of 8 hours. Two errors occur in the second polling period (between 08:00
and 16:00).
At 08:00 the 24-hour counter value does not indicate any error (the value has
not changed abnormally), so only a 15-minute counter “indicator” is stored for
the previous polling period. The indicator shows that the interval has been
polled, 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 are
stored, 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 changed
abnormally since its value at 16:00, so only a 15-minute counter “indicator” is
stored 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 minute
period 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 the
MTPs in a specific trail. The report contains either the counter data or the
gauge 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 the
period for which data have been retrieved, and a time stamp, indicating the
time 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 of
the 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 from
08: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 time
stamps of the current data line and the next, it is an indication that data are
missing 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, counters
with the value 0), the corresponding data line in the report is empty apart from
time 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 shows
the 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 are
handled by the same MTP, the VC-4 trail counters are not available if
the trail is not terminated.
14 MA276 • Rev. D1
Tellabs® 6300 Network Manager 2 Collecting Performance Data
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 data
is described in detail in ‘3 Displaying the Performance Data’ on page 35.
2.1 Introduction
Collecting data for an The performance monitoring facility distinguishes between whether the data
MTP as part of NE and/or collection operations are being activated with ’NE scope’ or with ’trail scope’
trail (that is, whether they are being activated for the MTP as part of an NE or for
the MTP as part of a trail).
This means that if, for example, you start data collection for one particular
MTP with both scopes (first with ’NE scope’ and then with ’trail scope’, or vice
versa), you will also have to stop the collection with both scopes — even
though 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 ’trail
scope’, while MTP reports can be generated with data from either
scope.
‘2.3 Collecting Data from Individual Monitored Termination Points’ on page
18‘2.4 Collecting Data from Individual Trails’ on page 22 and ‘2.5 Collecting
Data 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 monitoring

which does not influence the monitored signal in any way. This means that it
is possible to monitor the status of the trail (segment) without terminating the
trail.
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). You
can 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 data
flow 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 trail
scope, 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 the
counter for the time interval in which performance collection was started.
In the example shown in the figure, data collection is activated between 0:30
and 0:45. When the new polling period starts – in this case at 1:00 – the 00:30
and 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 you
stop the data collection; however, the data collection is not actually stopped
until 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:30
and 0:45. The entity is in the “pending” state until 1:00 when the next polling
starts, and its status is “stopping”. Data from the period between 0:00 and 0:45
are collected.
16 MA276 • Rev. D1
Seeing the status of the You can check the current data collection status of an entity with the Get Per-
data collection formance Collection Status operation. When you check an NE or a trail, a list
is displayed of those MTPs that are currently “active” or “stopping” and their
state is indicated. When you check a concatenated trail, a list is displayed of
the currently "active" or "stopping" VCGs.
Seeing the status of the You can check the current monitoring status of the MTPs in a specific trail, us-
MTPs in a trail ing the Performance Monitoring → Get Status (NE) menu item in the Find Trail
window. When you activate the menu item, the trail view is displayed, with
the color of the label indicating the current value of the MTP’s Monitoring State
attribute. The figure shows an example of a trail view.
Temporary suspension Data collection for an NE can be suspended temporarily and then later re-
of data collection sumed (using the Suspend Performance Collection and Resume Performance
Collection 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 You can create a report containing some of the collected data from a specific
collected data MTP or trail. This operation is described in detail in ‘3 Displaying the Perfor-
mance Data’ on page 35.
The ways to activate the The procedures described in ‘2.3 Collecting Data from Individual Monitored
operations Termination Points’ on page 18 to ‘2.5 Collecting Data from Concatenated
Trails’ on page 31 illustrate how to activate the data collection operations via
the graphical user interface.
Activating the operations for MTPs from the Performance Data window is
used 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 the
operations for trails is described in the trail procedures in ‘2.4 Collecting Data
from 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 available
from the graphical user interface (mainly, the possibility for carrying out an
operation 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 The following operations can be used in connection with data collection from
used? individual 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 This procedure describes how you activate the operations that allow you to
for an MTP on a 6315, control the collection of performance data from a single MTP.
6325, 6335, 6340 (FP4.0
Note: The procedure is valid for the following NE types:
or later), 6345 or 6350
• 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
Step Action
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.
Note: You can also control the data collection via the available operations for
the entities in the entity browser. Or you can use the operations directly
in the command line interface.
MA276 • Rev. D1 19
for an MTP on a 6310 or control the collection of performance data from a single MTP.
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
Step Action
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.
for an MTP on a 6340 control the collection of performance data from a single MTP.
(FP1.0 to 3.x)
Note: The procedure is valid for Tellabs® 6340 switch node, releases 1.0 – 3.x.
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
Step Action
5 Select one of the following options:

• Start
• Stop
• Get Status
• Report.

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 first
CTP 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 to
set up monitoring of individual CTPs along the trail’s route, provided the NE
containing the CTP supports non-intrusive monitoring. The data flow in the
CTP can be monitored either in just one direction or in both (incoming and
outgoing); 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 the
monitoring of the whole trail, whereas the monitoring of the CTPs can be
stopped individually. When you reconfigure a trail, monitoring is stopped for
those TPs that are no longer part of the trail’s route(s).
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 Monitored
TPs list which indicates the specific TPs that are to be monitored. The default
content is the two end point TTPs (or their replacement-CTPs if the end points
are in ExternalMatrices). Each CTP that you specify monitoring for is added
to the list (with an indication of the data flow directions to be monitored). If a
CTP 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 representing
the Ethernet (one for each Ethernet layer) will be added to each of the
monitored end point TTPs. This means that the Ethernet - no clients,
MPLS - in and MPLS-out trails are monitored.
used? trails:
• Start performance collection
• Stop performance collection
• Get performance collection status
ual operations. The recommended procedure for activating the operations is
described in ‘To control data collection for a whole trail’ on page 23.
for a whole trail control the collection of performance data from a specific trail.
Note: For a new trail, you can start data collection directly in the Set Up Trail
window 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
Step Action
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
24 MA276 • Rev. D1
Step Action
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”.
MA276 • Rev. D1 25
Step Action
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.
Note: You can also control the data collection via the available operations in
the 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 items
in the Find Trail window, the trail will be displayed in one of the 3 possible
states 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 TTPs
and CTPs. These fields are displayed when the menu item View → Perf Mon
TPs 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 the
trail’s performance report.
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 This procedure describes how to start non-intrusive monitoring of one data
CTP in one direction flow direction in a specific CTP in a trail.
Note: Starting monitoring from a CTP will automatically start monitoring for
the 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
Step Action
4 Type the required text in the text field and then press Enter.
The text field contains the specified text.
To start monitoring of the This procedure describes how to start non-intrusive monitoring of the second
second direction in a data flow direction in a CTP when the first direction is already being moni-
CTP 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 monitoring
of the outgoing data flow.
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
Step Action
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.
To stop monitoring of a This procedure describes how to stop non-intrusive monitoring of one of the
CTP in one direction data 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.
Step Action
1 In the Trail View window, open the pop-up menu for the relevant
CTP.
MA276 • Rev. D1 29
Step Action
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.
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.
30 MA276 • Rev. D1
2.5 Collecting Data from Concatenated Trails
Monitoring of The monitoring of a concatenated trail (that is, a collection of trails) is actually
concatenated trails a monitoring of the virtual concatenation groups (VCGs) that terminate the
concatenated trail.
used? concatenated trails:
• Start performance collection
• Stop performance collection
• Get performance collection status
ual operations. The recommended procedure for activating the operations is
described in ‘To control data collection for concatenated trails’ on page 31.
for concatenated trails control the collection of performance data from a specific set of concatenated
trails.
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
Step Action
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.
Note: You can also control the data collection via the available operations in
the entity browser. Or you can use the operations directly in the com-
To control data collection This procedure describes how you start data collection for a new VCG.
for VCGs
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 data
collection operations for several entities at the same time.
Telling the operation The table describes what the required parameter for a data collection opera-
which entities to control tion is, depending on how many and which type of entities you want to con-
trol with the same operation.
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 the MTP type and a wildcard.

specific type in a Example:
single NE AC1_30 .east vc4TTPBidirectional *
all MTPs in a the NE’s name.

specific NE Example:
AC1_30 .east
all NEs of a spe- the NE type and a wildcard.

cific type Example:
AC1_30 *
all CTP-related the trail’s name and all MTP names (identified as in-
MTPs in a specif- coming or outgoing direction).
ic trail Example:
startmonitoring <trail> incoming monitor -
TPs=<Full list of relevant CTPs>, outgoing monitor
-TPs=<Full list of relevant CTPs>
all MTPs in a the trail’s name.

specific trail Example:
LND vc4 TRAIL east-west
Note: You can also combine the use of wildcards.

Example: ‘AC1_30 * vc4TTPBidirectional *’ specifies all VC4
MTPs in all AC1_30 NEs.
MA276 • Rev. D1 33
Examples of operations The figure shows some examples of operations activated via the command
line interface.
34 MA276 • Rev. D1
Tellabs® 6300 Network Manager 3 Displaying the Performance Data
3 Displaying the Performance Data
Overview This describes how to create reports from the collected performance data. The
report is displayed in a separate window, the Performance Report window,
which is described in ‘3.1 The Window in which the Data is Displayed’ on
page 35.
3.1 The Window in which the Data is Displayed
What does the window The Performance Report window shown in the figure is used to display the
contain? performance report for either a single MTP or for all the MTPs in a specific
trail.
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 This procedure describes how you create a report with the data collected from
MTP on a 6315, 6325, a specific MTP.
6335, 6340 (FP4.0 or
later), 6345 or 6350
• 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
Step Action
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.
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 This procedure describes how you activate the operations that allow you to
MTP on a 6310 or 6320 control the collection of performance data from a single MTP.

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
Step Action
5 Select Report in the pop-up menu.

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

Note: You can also create a report via the available operations for the entities
in the entity browser. Or you can use the operations directly in the com-
To create a report for an This procedure describes how you activate the operations that allow you to
MTP on a 6340 (FP1.0 to control the collection of performance data from a single MTP.
3.x)
Note: The procedure is valid for Tellabs® 6340 switch node, releases 1.0 – 3.x.
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
Step Action
5 Select Report in the pop-up menu.

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

Note: You can also create a report via the available operations for the entities
in the entity browser. Or you can use the operations directly in the com-
MA276 • Rev. D1 39
To create a report for a This procedure describes how you create a report with the data collected from
trail all 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).

the report layout.
40 MA276 • Rev. D1
To create a report for a This procedure describes how you create a report with the data collected from
concatenated trail all MTPs in a specific concatenated trail.
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).

the report layout.
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 for
the 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.
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 This procedure describes how you specify which monitored entity’s data you
whose data you want to are interested in.
see
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 do
not need to use this procedure.
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.
To specify the collection This procedure describes how you specify the collection period of the perfor-
period for the data mance data that will be shown in the report.
Note: When you open the Performance Report window, the start time and the
end time of the period are both set to the current date and time.
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.
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.
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 This procedure describes how you specify which type of performance data are
performance data shown 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 This procedure describes how you can print the currently displayed perfor-
report on your printer 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
Step Action
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.
See ‘Example of a printed performance report’ on page 48 to get an idea of

what a printed performance report looks like.
report to a file mance report to a report file.
Step Action

window.
The default print setting is to send the report to your default printer.
MA276 • Rev. D1 45
Step Action
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.
report to a text file mance report to a ASCII text file.
46 MA276 • Rev. D1
Note: A text file contains gauge values, such as the temperatures of the optical
transceivers. And you are able to use the copy and paste functions
when you want to reuse the information present in the report.
Step Action

window.
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 Windows
procedure 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 The figure shows an example of a printed performance report for a trail.
performance report
48 MA276 • Rev. D1
Tellabs® 6300 Network Manager 4 Exporting Performance Data
4 Exporting Performance Data
Overview This describes how to export data from the performance monitoring database
into comma-separated files. The syntax of the command used for the export is
described, as well as the format of the output data.
4.1 Creating Files with Performance Data
Report data in comma- The data collected by performance monitoring can be output into comma-sep-
separated files arated data files, which can then be transferred to a database or analysis tool.
The UNIX command to The UNIX command that you can use to generate performance data files has
extract performance data the 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 periods
end 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 periods
begin 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. In
Trailname the wildcard symbol ‘%’ can be used to indicate the remaining part
of the name.
MTPname is an optional argument, and indicates the required MTP name. In
MTPname the wildcard symbol '%' can be used to indicate the remaining part
of the name. Note that if you specify MTPname, the Trailname must also be
specified.
-sdh is an optional argument that limits the contents of the output. See ‘The
SDH 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 will
be 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 monitoring
in response to this command is described in ‘4.2 The Generated Performance
Data 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 You can schedule the execution of the “dbextract” command by putting it in
command the “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-04
00: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. The
output 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 are
data 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 in
single quotes. NULL is represented by a space. One data source is uniquely
identified 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 3
is selected, then the number of data fields displayed is dynamic. Each
NE 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 at
specific data sublayers.
50 MA276 • Rev. D1
The SDH data file The SDH performance data file (generated by a “dbextract” command with
the -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 The all counters data file contains information for all the counters present
counters data file within 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 those
fields relevant to those counters are present. Therefore, for more infor-
mation, see the information about the contents of the data files for
counter 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 at
specific 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- Integer The number of bad payload frames that are

Rx> received.
Note: This counter is only relevant for MTPs
at the mapping, MPLS terminated and MPLS
non-intrusive layers.
<DiscFrames- Integer The number of bad payload frames that are

Rx> received.
at 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- Integer The number of payload frames that are not

FramesTx> transmitted.
at the MPLS terminated and MPLS non-intru-
sive layers.
<Disc- Integer The number of payload frames that are not

FramesTx> transmitted.
at the Ethernet MAC layer.
<BAR> Integer The value of the Bandwidth Availability Ra-

tio counter (percentage).
at the mapping layer.
<FCSErrors> Integer The value of the Frame Check Sequence Er-

rors counter.
<GfptHECEr- Integer The value of the GFP Type Header Error

rors> Check Errors counter.
<GfpcHECEr- Integer The value of the GFP Core Header Error

rors> Check Errors counter.
MA276 • Rev. D1 53
<LapfLMI- Integer The value of the LAPF LMI Link Reliability

LinkRel Errors counter.
<LapfLMIProt- Integer The value of the LAPF LMI Protocol Errors

Errs> counter.
<LapfLMIInac- Integer The value of the LAPF LMI Inactive Errors

tErrs> 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
The contents of a Each line in the file contains data for a 24-hour period. <Timestamp> defines
24-hour counter file the 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 that
there is no data for the counter or counters.
The contents of a Each line in the file contains data for a period. <Timestamp> defines the start
15-minute counter file time and <Period> the length of the period in seconds. If the period from one
line does not end at the start time of the next line for the same data source, the
performance 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> define
the 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 handled
by the same MTP, the VC-4 trail counters are not available if the trail is not ter-
minated.
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
Tellabs® 6300 Network Manager A Attributes Connected to Monitoring
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 TPs
Contains 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 VCGs
Contains a list of all VCGs in the concatenated trail that are currently being
monitored or are planned to be monitored (that is, all VCGs whose Monitoring
State attributes have the value planned, active or partly active).
Monitoring State
Indicates whether the trail is being monitored or not (that is, whether the TPs
listed in the trail’s Monitored TPs attribute are being monitored or not (see
‘Monitored TPs’ on page 57)).
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.
Monitoring Set
Indicates the type of monitoring of the trail.
Value Description
oam OAM monitoring enabled.
MA276 • Rev. D1 57
Value Description
statistics Statistics monitoring enabled.
Note: SDH trails allow only OAM monitoring while data trails (except MPLS
trails) allow only statistics monitoring. MPLS trails allow both types of
monitoring.
A.2 TTP Attributes
Monitoring State
Indicates whether the TTP is being monitored or not.
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.
Monitoring Set
Value Description

A.3 CTP Attributes
Monitoring State
Indicates for each of the two data flow directions (incoming and outgoing)
whether the CTP is being monitored or not.
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.

abled or disabled in the incoming direction.
58 MA276 • Rev. D1
Direction Value Description
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.

abled or disabled in the outgoing direction.
Monitoring Set
Indicates for each of the two data flow directions (incoming and outgoing) the
type of monitoring of the trail.
Value Description

A.4 VCG Attributes
Monitoring State
Indicates whether the VCG is being monitored or not.
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.
abled or disabled.
Monitoring Set
Value Description

MA276 • Rev. D1 59
A.5 How the TPs’ Monitoring State Attribute Changes
TP Monitoring State for When a monitored trail is assigned, deassigned or reconfigured, the Monitor-
assigned/deassigned/re ing State attribute for the affected TPs changes as described in the table.
configured trail
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- changes to none for those TPs that are no

ed/groomed/unprotected) longer part of the trail.
TP Monitoring State When monitoring is started for a specific trail, the monitoring-related at-
when trail monitoring is tributes change as described in the table.
started
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.
TP Monitoring State When monitoring of a specific trail is stopped, the monitoring-related at-
when trail monitoring is tributes change as described in the table.
stopped
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
If the trail is ... when trail monitoring is stopped then ...
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.
MA276 • Rev. D1 61
62 MA276 • Rev. D1
Tellabs® 6300 Network Manager Index
Index
A Data collection
for a 6310 20, 37
Abbreviations 8
for a 6315 18
Arial font
for a 6320 20, 37
use of 8
for a 6325 18
Arrows
for a 6335 18
use of 8
for a 6340 18, 21, 38
for a 6345 18
B for a 6350 18
Bit Error Counters window operations possible 18
using 21, 38 Data file fields 52
Bold Data file format 50
use of 8 Data file SDH format 51
Data time 11
dbextract command
C location 50
Collection of data 10, 15
syntax 49
check status 17
start 16
stop 16 E
Collection Period part Entities being monitored 9
in Performance Report window 42 Entity field
Command line interface in Performance Report window 42
using 33
Comma-separated file
creating 49
F
Fields in data file 52
fields 52
15-minute counter file 54
format 50
15-minute counters 10
SDH format 51
File
Concatenated trails
fields 52
creating report for 41
format 50
Counters
printing reports to 45
15-minute 10
SDH format 51
24-hour 10
Filter
using 41
D Find Trail window
Data using 23, 31, 40, 41
check status of collection 17 Format of data file 50
check status of MTP 17 Format of SDH data file 51
collecting 10, 15
definition 9
displaying in report 35
G
operations for collecting 16 Gauges 10
output in comma-separated file 49 Get Performance Collection Status operation 17
recovery of 11 Get Status (Collection) menu item 24, 31
reports 13 Get Status (NE) menu item 17, 24
resume collection of 17 Get Status button
start collection of 16 in Performance Data window 19
stop collection of 16
suspend collection of 17
MA276 • Rev. D1 63
I Printer
printing reports to 44
Italics
Printing performance reports 44
use of 8
to a text file 46
to file 45
L to printer 44
Layout of reports 13
Q
M Quotation marks
Manual use of 8
structure of 7
style conventions 8
Monitor incoming menu item 27, 30
R
Monitor outgoing menu item 28 Recovery of data 11
Monitored entities 9 References 8
MTPs Report button
collecting data from individual MTPs 18 in Performance Data window 19, 36
controlling many 33 Report menu item
creating report for 36 in Find Trail 31
in Find Trail window 24, 40, 41
Reports
N creating 35
Network elements description 13
controlling many 33 in comma-separated files 49
layout 13
printing 44
O types 13
Operations 16
Requirements 10
parameters for 33 Resume Performance Collection operation 17
Overview of performance monitoring 9
P S
Search filter
Performance data
using 41
fields in data file 52
Start button
file format 50
in Performance Data window 19
SDH file format 51
Start menu item
see Data
in Find Trail 31
Performance Data Type field
in Find Trail window 24
in Performance Report window 43
Statistics 10
Performance Data window
Status of entity 17
using 18, 20, 36, 37
Status of MTP 17
Performance Monitoring menu item
Stop button
in Find Trail window 24, 31, 40, 41
in Performance Data window 19
Performance Report window 35
Stop menu item
search filter 41
in Find Trail 31
using 36, 40, 41
in Find Trail window 24
Performance reports
Suspend Performance Collection operation 17
see Reports
Syntax for UNIX command 49
Polling 10
Print button
in Performance Report window 44 T
Print window Text file
using for performance report 44 printing reports to 46
using for report file 45, 47 Time indication 11
64 MA276 • Rev. D1
Trails
collecting data from concatenated trails 31
collecting data from individual trails 22
controlling many 33
creating report for 40
creating report for concatenated 41
24-hour counter file 54
24-hour counters 10
U
UNIX command
location 50
syntax 49
V
VCGs
collecting data from VCGs 31
MA276 • Rev. D1 65
66 MA276 • Rev. D1

Tellabs OSN2 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Tellabs OSN2 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

Technical Documentation

Product family Tellabs® 6300 Managed

Title Monitoring Performance

Document User’s Manual

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

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-

C1 Oct 31, 2005 • Descriptions of Monitoring Set attributes have

C2 Aug. 10, 2006 Compared to revision C1:

Rev. Date Description of Changes

C3 Sept. 1, 2007 Compared to revision C2:

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

1 Description of Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . 9

2 Collecting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Displaying the Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . 35

4 Exporting Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

A Attributes Connected to Monitoring . . . . . . . . . . . . . . . . . . . . . . . . 57

The structure of this The manual is structured as follows:

Abbreviations BBE Background Block Errors

1 Description of Performance Monitoring

1.1 A General Overview

1.2 The Collection of the Data

1.3 The Performance Data Reports

2 Collecting Performance Data

Non-intrusive monitoring Non-intrusive monitoring of a trail or a trail segment is a way of monitoring

2.2 The Available Operations

2.3 Collecting Data from Individual Monitored Termination Points

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

2 Select the Data Collection tab.

The available buttons (corresponding to individual operations) are:

4 Click the relevant button.

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

• Tellabs® 6310 edge node release 4.8 – 6.0.1

1 Select Performance → Performance Monitoring... in the pop-up menu

2 Select the Source Selection → Monitor Points tabs.

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

5 Select one of the following options:

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

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

2 Select the Source Selection → Monitor Points tabs.

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

5 Select one of the following options:

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

2.4 Collecting Data from Individual Trails

1 Search for the trail in the Find Trail window.

3 Select the menu item Performance Monitoring to display the available

The available menu items (corresponding to individual operations)

4 To start or stop monitoring of a trail or to see the monitoring status,

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

2 Select the Monitor incoming menu item.

2 Select the Monitor outgoing menu item.

2 Select the Monitor incoming menu item.

2.5 Collecting Data from Concatenated Trails

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

3 Select the menu item Performance Monitoring to display the available

The available menu items (corresponding to individual operations)

4 To start or stop monitoring of a concatenated trail, select the menu

5 To see the current monitoring status of a concatenated trail, select

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

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

2.6 Using the Command Line Interface