NetcoolProviso Nortel - CS2K 43X PDF

IBM
Netcool/Proviso 4.3-X
Tivoli
Document Revision R2E1
Nortel CS2000 2.4.1.0 Technology Pack Users Guide
Notices
This information was developed for products and
services offered in the U.S.A. IBM
may not offer the

products, services, or features discussed in this
document in other countries. Consult your local IBM
representative for information about the products and
services currently available in your area. Any reference to
an IBM product, program, or service is not intended to
state or imply that only that IBM product, program, or
service may be used. Any functionally equivalent
product, program, or service that does not infringe any
IBM intellectual property right may be used instead.
However, it is the users responsibility to evaluate and
verify the operation of any non-IBM product, program,
or service.
IBM may have patents or pending patent applications
covering subject matter described in this document. The
furnishing of this document does not give you any
license to these patents. You can send license inquiries,
in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS)
information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing,
to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the
United Kingdom or any other country where such
provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A
PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this
statement might not apply to you.
This information could include technical inaccuracies or
typographical errors. Changes are periodically made to
the information herein; these changes will be
incorporated in new editions of the publication. IBM
may make improvements and/or changes in the
product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web
sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The
materials at those Web sites are not part of the materials
for this IBM product and use of those Web sites is at
your own risk.
IBM may use or distribute any of the information you
supply in any way it believes appropriate without
incurring any obligation to you.
Licensees of this program who wish to have information
about it for the purpose of enabling: (i) the exchange of
information between independently created programs
and other programs (including this one) and (ii) the
mutual use of the information which has been
exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758
U.S.A.
Such information may be available, subject to
appropriate terms and conditions, including in some
cases payment of a fee.
The licensed program described in this document and all
licensed material available for it are provided by IBM
under terms of the IBM Customer Agreement, IBM
International Program License Agreement or any
equivalent agreement between us.
Any performance data contained herein was determined
in a controlled environment. Therefore, the results
obtained in other operating environments may vary
significantly. Some measurements may have been made
on development-level systems and there is no guarantee
that these measurements will be the same on generally
available systems. Furthermore, some measurement may
have been estimated through extrapolation. Actual
results may vary. Users of this document should verify
the applicable data for their specific environment.
Information concerning non-IBM products was
obtained from the suppliers of those products, their
published announcements or other publicly available
sources. IBM has not tested those products and cannot
confirm the accuracy of performance, compatibility or
any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products
should be addressed to the suppliers of those products.
All statements regarding IBMs future direction or intent
are subject to change or withdrawal without notice, and
represent goals and objectives only.
This information is for planning purposes only. The
information herein is subject to change before the
products described become available.
This information contains examples of data and reports
used in daily business operations. To illustrate them as
completely as possible, the examples include the names
of individuals, companies, brands, and products. All of
these names are fictitious and any similarity to the names
and addresses used by an actual business enterprise is
entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs
in source language, which illustrate programming
techniques on various operating systems. You may copy,
modify, and distribute these sample programs in any
form without payment to IBM, for the purposes of
developing, using, marketing or distributing application
programs conforming to the application programming
interface for the operating system for which the sample
programs are written. These examples have not been
thoroughly tested under all conditions. IBM, therefore,
cannot guarantee or imply reliability, serviceability, or
function of these programs. You may copy, modify, and
distribute these sample programs in any form without
payment to IBM for the purposes of developing, using,
marketing, or distributing application programs
conforming to IBM's application programming
interfaces.
If you are viewing this information in softcopy form, the
photographs and color illustrations might not appear.
Trademarks
AIX
, DB2
, developerWorks
, eServer, i5/OS
,
IBM
, the IBM logo
, IBMLink, iSeries
, Lotus
,
Netcool
, Netcool/Proviso
, OMEGAMON
,
Passport Advantage
, pSeries
, Rational
, Redbooks
,
OS/390
, OS/400
, Tivoli
, the Tivoli logo
, Tivoli
Enterprise Console
, WebSphere
, and zSeries
are
trademarks or registered trademarks of International
Business Machines Corporation in the United States,
other countries, or both.
Intel
is a registered trademark of Intel Corporation or

its subsidiaries in the United States, other countries, or
both.
Linux is a trademark of Linus Torvalds in the United
States, other countries, or both.
Microsoft
, Windows
, Windows NT
, and the
Windows logo are trademarks of Microsoft Corporation
in the United States, other countries, or both.
UNIX
is a registered trademark of The Open Group in

the United States and other countries.
Other company, product, and service names may be
trademarks or service marks of others.
Copyright IBM Corp. 2009.
US Government Users Restricted Rights Use,
duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Java
and all Java-based

trademarks and logos are
trademarks or registered
trademarks of Sun Microsystems,
Inc. in the United States, other
countries, or both.
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X v
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxxi
Chapter 1: Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
How is the Data Collected? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Inventory. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
How is the Data Processed and Loaded into the Database? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
CME Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Loading Phase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Building Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Processing Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Output Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How is the Data Reported? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Chapter 2: Supported Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Report Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Reporter Set Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Call Distribution Analysis - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Call Distribution Analysis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Call Server NPI - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Call Server NPI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Client Manager Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Client Manager Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Compact (3PC) System Health - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Compact (3PC) System Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Compact XA-Core System Health - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Compact XA-Core System Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
CS2K Device Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Contents
vi Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
CS2K Device Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
CS2K Trunk Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CS2K Trunk Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Customer Profile Analysis - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Customer Profile Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Customer Profile QoS - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Customer Profile QoS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Extension QoS - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Extension QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Extension Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Extension Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Extension Utilization - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Extension Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
GWC Health Report - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
GWC Health Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Line Quality Report - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Line Quality Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
MGW Call Utilization - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
MGW Call Utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
MGW QoS - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
MGW QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
MS2010 Announcements and Conferences - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
MS2010 Announcements and Conferences. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
MS2010 Device Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
MS2010 Device Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
MS2010 RTP-MP Analysis - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
MS2010 RTP-MP Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Nortel CS2K System Performance - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Nortel CS2K System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Path Call Utilization - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Path Call Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Path QoS - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Path QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PVG Card Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
PVG Card Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
PVG Card Temperature - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X vii
PVG Card Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
PVG Device Call Signaling - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
PVG Device Call Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
PVG Device Usage - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
PVG Device Usage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
PVG Interface Usage - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
PVG Interface Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
PVG VSP Call Signaling - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
PVG VSP Call Signaling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
PVG VSP Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
PVG VSP Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
RAS Port Statistics - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
RAS Port Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
SAM21 Device Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
SAM21 Device Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
SCAI Messaging - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
SCAI Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Server CPU and Memory - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Server CPU and Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Server Swap - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Session Policy Controller Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Session Policy Controller Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
SIP Inbound Response Report - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
SIP Inbound Response Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
SIP Outbound Response Report - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
SIP Outbound Response Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
SIP Transaction Report - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
SIP Transaction Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
SLA Voice Quality Report - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
SLA Voice Quality Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Softswitch Call Utilization - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Softswitch Call Utilization - MLH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Softswitch Call Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Softswitch QoS - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Softswitch QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
SS-T Call Analysis- DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Contents
viii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
SS-T Call Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
SS-T System - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
SS-T System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
SSL - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
SSL Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Stream Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Stream Quality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
System Performance - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Termination Cause Analysis - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Termination Cause Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Termination Cause QoS - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Termination Cause QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
TypeOfCall Call Setup and Termination Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
TypeOfCall Call Setup and Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
TypeOfCall QoS - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
TypeOfCall QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
USP Device Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
USP Device Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
USP Link Quality - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
USP Link Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
USP Linkset Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
USP Linkset Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
USP Routeset Metrics - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
USP Routeset Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Voice Quality - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Voice Quality Report - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Voice Quality Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Voice Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
VOIP Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
XA-Core System Health - DC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
XA-Core System Health . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Zone QoS - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Zone QoS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Zone Utilization - DC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Zone Utilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X ix
Chapter 3: Devices and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Nortel CS2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Nortel CS2000 CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Nortel GWC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Nortel IEMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Nortel AMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Nortel CICM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Nortel MS 2010 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Nortel SAM21 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Nortel SPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Nortel PVG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Nortel SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Nortel SST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Nortel USP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Services and Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Nortel MDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Nortel MDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Nortel PMSP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Nortel QCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Nortel STP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Nortel UAS and Nortel SDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Chapter 4: Data Collection Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Nortel CS2000 Devices That Generate Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Nortel CS2000 Performance Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Nortel CS2000 CDRs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Nortel IEMS Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Nortel PVG Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Nortel SSL Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Nortel SST Performance Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Nortel USP Performance Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Bulk Adaptor Design Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Configuration and Technology Pack-Specific Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Chapter 5: Element and Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Contents
x Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Nortel CS2000 Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Nortel CS2000 Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
CS2K Softswitch Trunk Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Nortel CS2000 CDRs Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Nortel CS2000 Device CDR Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Customer Profile Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Termination Cause Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
TypeOfCall Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Media Gateway Trunk Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Subscriber Zone Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Path Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Extension Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Nortel CS2000 Extended QoS Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Nortel IEMS Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Nortel AMS Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Nortel CICM Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Nortel GWC Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Nortel MS 20xx Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Nortel RAS Port Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Nortel SAM21 Shelf Controller Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . 162
Nortel SPC Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Nortel SSL Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Nortel PVG Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
PVG Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Media Gateway FC Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Media Gateway SC Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
MGI Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Media Gateway VSP PC Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Media Gateway VSP CC Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Nortel SST Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Nortel USP Device Sub-Element Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
USP Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
USP Linkset Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
USP Routeset Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
USP Carrier Link Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Chapter 6: Defined Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Element Names Defined for Nortel CS2000 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Nortel CS2000 Device Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xi
Nortel CS2000 CDRs Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Nortel IEMS Device Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Nortel PVG Device Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Nortel SST Device Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Nortel USP Device Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Sub-Element Names Defined for Nortel CS2000 Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Nortel CS2000 Device Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Nortel CS2000 Device Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
CS2K Softswitch Trunk Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Nortel CS2000 CDRs Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Nortel CS2000 Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Customer Profile Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Termination Cause Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
TypeOfCall Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Media Gateway Trunk Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Subscriber Zone Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Path Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Extension Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Nortel CS2000 Extended QoS Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Nortel IEMS Device Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Nortel AMS Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Nortel CICM Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Nortel GWC Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Nortel MS 20xx Device Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Nortel RAS Port Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Nortel SAM21 Shelf Controller Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Nortel SPC Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Nortel SSL Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Nortel PVG Device Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
PVG Device Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Media Gateway FC Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Media Gateway SC Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
MGI Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Media Gateway VSP PC Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Media Gateway VSP CC Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Nortel SST Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Nortel USP Device Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
USP Device Sub-Element Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
USP Linkset Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
USP Routeset Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
USP Carrier Link Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Nortel CS2000 Devices Sub-Element Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Contents
xii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Nortel CS2000 Devices Sub-Element Family Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Chapter 7: Bulk Collection Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Data Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Formulas and Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Netcool/Proviso Formula Tree for the Nortel CS2000 Technology Pack . . . . . . . . . . . . . . . . . . . . 192
Formula Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
3PortConfFailureRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
3PortOcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
6PortConfFailureRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
6PortOcc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
AboveMOSpercentage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
acPerfBctFailedDueToLackOfResources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
acPerfBctRequests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
acPerfConfAddFailedDueToLackOfResources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
acPerfConfFailedDueToLackOfResources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
acPerfConfRequests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
acPerfIvrContDigitCollectFailedDueToLackOfResources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
acPerfIvrPlayCollectFailedDueToLackOfResources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
acPerfIvrPlayCollectFailedDueToProvMismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
acPerfIvrPlayCollectRequests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
acPerfIvrPlayFailedDueToLackOfResources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
acPerfIvrPlayFailedDueToProvMismatch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
acPerfIvrPlayRequests. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
acPerfRtpFailedDueToLackOfResources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
acPerfRtpRcvrLostPackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
acPerfSystemPacketEndpointsInUse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xiii
acPerfTtRequests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
ActiveConnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
ActiveIvrMPConnections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
ActiveSessions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Alignment Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
AllocatedAudioBuffers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
ANNFailureRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
ANNocc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
AUXCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
AverageHoldingTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
AverageInboundUtilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
AverageLossRate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
AverageOutboundUtilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
AvgCPUutilizationCardProcessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
AvgCPUutilizationVSPCard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
AvgCPUutilizationVSPCard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
BHHCA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Buffer Overrun Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
BusyCallHourAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Bytes Received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Bytes Transmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
BytesProcessedPerSecond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
bytesRxedPerSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
bytesSentPerSec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
BytesStreamedPerSecond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
CallAgentCPUUtilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
CallAgentMemoryUtilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
CallCompletionRatio_EndOffice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Contents
xiv Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
CallCompletionRatio_Tandem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264
CallDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
CallsReleasedBySST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
CallVolumeForTheSSTnode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
CardUtilAvg. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268
CCR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
CDR Extension Call Duration (CME). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
CDR Extension Successful Calls Percentage (CME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271
CDR Softswitch Device Minute Of Use (CME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272
CDR Softswitch Device Successful Calls percentage (CME) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273
cellDropCount. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
CongestedSeconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
CongestedSeconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Connection Failures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Connections Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Context Switches/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
CPUutilizationForCallProcessing% . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
CRC Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
CS2K Grade of Service CME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
DropCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xv
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
EchoReturnLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307
EndSystemDelay. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308
ENGCAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309
Exception Dispatches/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
ExternalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
ExternalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312
ExternalProviderConnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Failovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314
Failovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
FERserverCCRforTheSSTnode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
FERserverMHTforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
FERserverMTTforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
FERserverNERforTheSSTnetwork. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
FERserverNERforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
File Control Bytes/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
File Control Operations/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
File Data Operations/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
H248Retransmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
H248Retransmission. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
HalfCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
HIOP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
hrStorageAllocationFailures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
hrStorageUsed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Contents
xvi Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 332
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
hrSystemUptime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
In_2xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
In_3xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
In_4xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
In_5xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339
In_6xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
In_Unknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
InboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
InboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343
InboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
InboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
InboundInvitePostDialDelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
InboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347
InboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
InboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
InboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
InboundPacketRate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
InBYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
IncomingAnswerSeizureRatio%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
IncomingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
IncomingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
IncomingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
IncomingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
IncomingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
IncomingCallTrunkRoutingFailure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
IncomingSuccessfulCalls%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
IncomingSuccessfulCalls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
IncomingTrunkToLineCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
InternalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
InternalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
InternalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xvii
InternalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
InternalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367
InternationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
IntraSwitchLineToLineCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374
Invite200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375
JitterAverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Jitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377
LineCodeViolations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378
LineErroredSeconds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379
LineLossOfSignalSeconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380
LineSeverelyErroredSeconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381
LinkFailureAllReasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382
LinkMSUreceived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383
LinkMSUtransmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
LinksetInactivityDuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
LinkUnavailableDuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
LinkUtilization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
ListeningQualityMOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388
LMBUtil . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
LocalGWCCCRforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
LocalGWCMHTforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 399
LocalGWCMTTforTheSSTnode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400
LocalGWCNERforTheSSTnetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Contents
xviii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
LocalGWCNERforTheSSTnode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
LoggedInUsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
LossOfEstablishedCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
LostPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
LostPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
LostPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
LostPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408
maxCpuOccupancyValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
maxRamUtilizationValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
maxSwapUtilizationValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
MaxTemp. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412
medianCpuOccupancyValue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
medianRamUtilizationValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414
medianSwapUtilizationValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Mid-call Failure Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
minCpuOccupancyValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
minRamUtilizationValue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418
minSwapUtilizationValue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
MobileCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
NationalCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
NetworkCallFailure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
NetworkCallFailure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
NetworkEffectivenessRatio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Nodal NER (CME). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
NormalCall Termination. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xix
NormalCallTermination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
OffNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
OffNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
OffNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
OffNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
OffNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
OnNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
OnNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
OnNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
OnNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
OnNetCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
OriginatingAbandonsBeforeConnection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
OriginatingAttemptFailures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
OriginatingFailures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
OriginatingLineCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Out_2xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Out_3xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Out_4xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Out_5xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
Out_6xx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Out_Unknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
OutboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
OutboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
OutboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
OutboundByte . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
OutboundInvitePostDialDelay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
OutboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
OutboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
OutboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
OutboundPacket . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
OutboundPacketRate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
OutBYE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
OutgoingAnswerSeizureRatio% . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Contents
xx Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
OutgoingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
OutgoingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
OutgoingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
OutgoingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
OutgoingCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
OutgoingCallTrunkRoutingFailure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
OutgoingLineToTrunkCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
OutgoingSuccessfulCalls%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
OutgoingSuccessfulCalls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
OverloadCmdRejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
OverloadCmdRejected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
oversizedPDUCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
PacketDelayVariation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
PacketLatency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
PacketLatency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
PacketLatency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
PacketLatency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
PacketLoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
PendingIvrMPConnections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Percent Compression Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
PercentageCpuUsed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
PercentageMemoryUsed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
ProcessorElement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
RoundTripAverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxi
RSTReceived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
RSTTransmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
rxedTimeoutCount . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
SCAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
ServiceFailureRate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
ShortCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
SimultaneousCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
SparingBandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
SSLOverload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
SuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
System Calls/sec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
TDMCallFailures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
TerminatingFailures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Threads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Timeout Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Total Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
TotalActiveCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
TotalActive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
totalBytesRxed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
totalBytesSent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Contents
xxii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
TotalCallBidAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
TotalCall. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
TotalCallTrunkRoutingFailure%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
TotalConnectionOrientedIPDistributionViolations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
TotalConnectionOrientedMessagesHandled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
TotalConnectionOrientedMessagesRoutingFailure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558
TotalFilesTranscoded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559
TotalGTTAlternateRoutingOnCongestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
TotalGTTHopCounterViolation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
TotalGTTNoTranslationForAddress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
TotalGTTPerformed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
TotalGTTTranslationTypeNotFound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
TotalICMPPackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
TotalIn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566
TotalMessagesErrors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
TotalMessagesHandled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
TotalMessagesIncompatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
TotalMessagesTooLargeForSegmentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
TotalMinutesOfUse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
TotalMinutesOfUse. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572
TotalMSUDiscardedSCCPMessages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
TotalNumberOfDiscardedPackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
TotalNumberOfPacketExceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575
TotalNumberOfTCPPackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
TotalNumberOfUDPPackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
TotalOut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578
TotalOutOfSequenceSCCPMessages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
TotalPackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
totalRam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxiii
TotalReassemblyBufferUnavailable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
TotalReassemblyFailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
TotalReassemblyTimerExpired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
TotalRoutesetCongested. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
TotalRoutesetManualBusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
TotalRoutesetUnavailabilityDuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
TotalRoutesetUnavailability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
TotalSCCPRoutingFailure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
TotalSegmentationFailed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
TotalSoftswitchCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
TotalSoftswitchSuccessfulCalls%. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
TotalSoftswitchSuccessfulCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
TotalSoftswitchUnsuccessfulCalls% . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
TotalSoftswitchUnsuccessfulCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595
TotalSuccessfulCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
TotalSuccessfulCalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
totalSwap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
TotalTCPPackets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599
TotalTDMCallFails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
TotalUDPPackets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
TrafficBusyUse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Transactions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
TransferAllowedRoutingAvailableReceived. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
TransferAllowedRoutingAvailableTransmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
TransferControlledTransmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 606
TransferProhibitedRoutingNotAvailableReceived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
TransferProhibitedRoutingNotAvailableTransmitted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608
TransferRestrictedReceived . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
TransferRestrictedTransmitted. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
TransitTrunkToTrunkCallAttempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
TransmissionStreams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Contents
xxiv Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
TrunkGOS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
TrunkOrCarrierBusy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
TrunkOverflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
UnderMOSLimit(3.7)all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
UnderMOSLimit(3.7)offnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
UnderMOSLimit(3.7)onnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 632
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
UnderMOSLimit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 634
UnderMOSLimitOffnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
UnderMOSLimitOnnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
UnsuccessfulCallBusy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxv
UnsuccessfulCallInvalidAddress . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
UnsuccessfulCall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
UnsuccessfulCallNetwork . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
UnsuccessfulCallNoAnswer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Appendix A: Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Contents
xxvi Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Configure the Technology Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Other Tasks and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Verifying Resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Appendix B: UBA Parameters Reference (Netcool/Proviso 443 and Higher) . . . . . . . 701
UBA Parameters Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Appendix C: Template File Reference (Pre-443 Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Pack-Specific UBA Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Additional Information on UBA Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Appendix D: Configuring cs2kcdr.pl Script Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Configuration of the cs2kcdr.pl Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Editing the cs2kcdr-config.pl Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Appendix E: Reports Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Report Navigation Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Infrastructure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
IP Centrex . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Media Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Signaling Gateways . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Softswitch Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
User Experience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
User Experience->Call Signaling Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822
User Experience->Service Usage Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
User Experience->Voice Quality Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
VOIP Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Infrastructure Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
IP Centrex Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Client Manager Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Media Gateways Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
PVG Card Quality Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832
PVG Card Temperature Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
PVG Device Usage Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
PVG Device Call Signaling Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
PVG Interface Usage Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxvii
PVG VSP Call Signaling Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
PVG VSP Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Media Servers Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
System Performance Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Stream Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
RAS Port Statistics Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
MS2010 Device Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
MS2010 RTP - MP Analysis Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Signaling Gateways Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
USP Device Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
USP Link Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
USP Linkset Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
USP Routeset Metrics Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Softswitch Platform Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
CS2K Device Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
CS2K Trunk Quality Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
SAM21 Device Quality Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 848
Session Policy Controller Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
User Experience Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Call Signaling CDR/IPDR Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
TypeOfCall Call Setup and Termination Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Termination Cause Analysis Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Service Usage CDR/IPDR Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Customer Profile Analysis Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Extension Utilization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
MGW Call Utilization Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Path Call Utilization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Softswitch Call Utilization - MLH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Softswitch Call Utilization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Zone Utilization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Call Distribution Analysis Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 864
Voice Quality CDR/IPDR Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Extension Quality Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Voice Quality Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Appendix F: Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Nortel CS2000 Device Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Nortel CS2000 Device Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . 870
CS2K Softswitch Trunk Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . 873
Nortel GWC Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874
Nortel MS 2010 (SDM) Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Contents
xxviii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Nortel CS2000 CDRs Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Nortel CS2000 CDR Device Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . 877
Termination Cause Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . 878
TypeOfCall Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Media Gateway Trunk Sub-Element Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . 880
Customer Profile Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . 882
Subscriber Zone Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . 883
Extension Sub-Element Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Path Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
CDR Location Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . 887
Nortel IEMS Device Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888
hrSystem Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Nortel AMS Bulk Collection Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Nortel RAS Port Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Nortel AMS Stream Source Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . 890
Nortel AMS Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
Nortel AMS TCP Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891
Nortel CICM Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Nortel MS 2010 (IEMS) Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
acPerfBct Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
acPerfConf Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
acPerfIvr Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
acPerfRtp Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
acPerfSystem Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
acPerfTt Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Nortel SAM21 Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Nortel SPC Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Nortel SSL Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
Nortel PVG Device Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
PVG Device Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . 899
Media Gateway FC Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . 900
Media Gateway SC Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . 900
MGI Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Media Gateway VSP PC Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . 901
Media Gateway VSP CC Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . 902
Nortel SST Device Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . 903
Nortel USP Device Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903
USP Device Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . 904
USP Linkset Sub-Element Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . 905
USP Routeset Sub-Element Bulk Collection Formula Mappings . . . . . . . . . . . . . . . . . . . . . . . . 906
USP Carrier Link Sub-Element Bulk Collection Formula Mappings. . . . . . . . . . . . . . . . . . . . . . 906
Contents
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxix
Additional Copyright Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
Contents
xxx Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxxi
Preface
This manual describes the Netcool/Proviso Nortel CS2000 Technology Pack, focusing on the Nortel CS2000
environment. Specifically, the manual describes the reports for displaying information about the devices and
technologies that operate in the Nortel CS2000 environment. The manual also describes the data collection
model, properties, resources, collection formulas, and metrics that the Nortel CS2000 Technology Pack provides
to create the associated reporter sets.
Audience
The audiences for this manual are the network administration engineers at IBM customer sites who will install,
configure, and use the Nortel CS2000 Technology Pack as part of their Netcool/Proviso installation. IBM
Professional Services engineers may also find this manual useful.
To install and use the Nortel CS2000 Technology Pack, you should have a working knowledge of the following
subjects:
Netcool/Proviso DataMart
TCP/IP networks
Telecom network management
Administration of the operating system
The audiences should also be familiar with the specific technology that the Nortel CS2000 Technology Pack deals
with, in this case Nortel CS2000.
Organization
This guide is organized as follows:
Chapter 1, Introduction
Provides a general introduction to technology packs.
Chapter 2, Supported Reports
Provides information about the reports that the Nortel CS2000 Technology Pack provides for each device
operating in the Nortel CS2000 environment.
Chapter 3, Devices and Services
Describes the devices and services that the Nortel CS2000 Technology Pack supports.
Chapter 4, Data Collection Model
Preface
xxxii Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Describes the data collection model that the Nortel CS2000 Technology Pack uses to collect data from the
different devices and services that operate in the Nortel CS2000 environment.
Chapter 5, Element and Sub-Element Properties
Describes the properties that the Nortel CS2000 Technology Pack discovers during the inventory process.
Chapter 6, Defined Resources
Provides information about the elements and sub-elements that the technology pack defines in the Proviso
database.
Chapter 7, Bulk Collection Formulas
Provides information about the Bulk collection formulas that the Nortel CS2000 Technology Pack provides
for devices operating in the Nortel CS2000 environment that generate and store data in Bulk input files.
Specifically, the chapter discusses the metrics on which the Bulk collection formulas operate.
Appendix A, Configuration
Describes how to configure the Nortel CS2000 Technology Pack.
Appendix B, UBA Parameters Reference (Netcool/Proviso 443 and Higher)
Provides UNIX reference pages for each of the pack-specific UBA parameters supplied with the XSD file
for the Nortel CS2000 Technology Pack.
Appendix C, Template File Reference (Pre-443 Only)
Explains the edits that need to be made (with a text editor) to pack-specific UBA parameters delivered in the
pack template file.
Appendix D, Configuring cs2kcdr.pl Script Execution
Describes how to configure and run the cs2kcdr.pl script that is delivered as part of the Nortel CS2000
Technology Pack.
Appendix E, Reports Examples
Provides examples of reports that the Nortel CS2000 Technology Pack provides.
Appendix F, Bulk Collection Formula Mappings
Provides mappings of bulk collection formulas to corresponding fields in the Bulk input files.
The Netcool/Proviso Product Suite
Netcool/Proviso is made up of the following components:
Netcool/Proviso DataMart is a set of management, configuration and troubleshooting GUIs that the
Netcool/Proviso System Administrator uses to define policies and configuration, as well as verify and
troubleshoot operations.
Netcool/Proviso DataLoad provides flexible, distributed data collection and data import of SNMP and
non-SNMP data to a centralized database.
Preface
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X xxxiii
Netcool/Proviso DataChannel aggregates the data collected through Netcool/Proviso DataLoad for use
by the Netcool/Proviso DataView reporting functions. It also processes on-line calculations and detects real-
time threshold violations.
Netcool/Proviso DataView is a reliable application server for on-demand, web-based network reports.
Netcool/Proviso Technology Packs extend the Netcool/Proviso system with service-ready reports for
network operations, business development, and customer viewing.
The following figure shows the different Netcool/Proviso modules.
Figure 1: Netcool/Proviso Modules
Netcool/Proviso Documentation
Netcool/Proviso documentation consists of the following:
release notes
configuration recommendations
user guides
technical notes
online help
The documentation is available for viewing and downloading on the infocenter at:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp?topic=/com.ibm.netcool_proviso.doc/welcome.htm
Preface
xxxiv Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
NOTES
Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X 1
Chapter 1: Introduction
This chapter discusses the following topics:
Overview
Netcool/Proviso Technology Packs are individually installed modules that contain discovery, grouping,
collection, and reporting instructions created by Technology Pack developers or Professional Services personnel
for a specific network technology or network equipment provider, such as Nortel CS2000.
Once installed, a Technology Pack programs Netcool/Proviso to inventory and group specific network
resources, perform mathematical calculations on raw or aggregated data streams collected from these resources,
and produce key performance monitoring metrics that are stored on the Netcool/Proviso database. Reporter sets
designed for each Technology Pack query the database for this information and display the results on a web portal
in the form of specialized report tables, graphs, and charts.
This chapter provides an overview of how Technology Packs work with Netcool/Proviso to collect, process, load,
and report data from a network environment.
How is the Data Collected?
Inventory
After a Netcool/Proviso Technology Pack has been installed, an inventory process must be run so that the
Technology Packs target network resources can be identified and modeled within Netcool/Proviso as sub-
elements. Sub-elements must be created before data from any network resource can be collected, processed, and
stored in the database.
How sub-elements are discovered depends on whether the target resources are SNMP resources or non-SNMP
resources:
For SNMP network resources, a Technology Pack provides a discovery formula. Discovery formulas are used
to evaluate network resources, determine which resources become sub-elements, and set values for items
defined as properties in the formula. Once all the sub-elements have been discovered and created in the
database, the inventory process organizes the sub-elements according to the grouping rules provided by a
Topic Page
Overview 1
How is the Data Collected? 1
How is the Data Processed and Loaded into the Database? 2
How is the Data Reported? 3
2 Netcool/Proviso Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X
Technology Pack. The grouping rules use the properties and values defined within inventory formulas or
adaptor design files to filter the sub-elements into their appropriate collection or reporting groups.
For non-SNMP network resources, a Technology Pack provides a Bulk Adaptor Design File. Bulk Adaptor
Design Files define how data fields that reside in files generated by network resources are used to create sub-
elements and set values for items defined as properties.
During the database synchronization phase of the inventory process, the list of discovered sub-elements is
compared to what exists in the database. Newly discovered sub-elements are assigned a resource identifier (RID)
and timestamp, and the database uses both items to create a new entry for the sub-element to reflect the known
state of the network inventory.
Collection
Following the completion of the inventory process, Netcool/Proviso is ready to collect performance data for a
Technology Packs target network resources. A Technology Pack provides Netcool/Proviso with collection
formulas that instruct a DataLoad collector residing in a DataChannel to collect specific types of performance
data against a particular sub-element.
The types of collection formulas applied to the data depend on whether the sub-element is an SNMP resource
or non-SNMP resource:
For SNMP network resources, a Technology Pack provides SNMP collection formulas. SNMP collection
formulas instruct the SNMP Collector to take the data gathered during a specified collection interval,
perform some mathematical operation on the data, and output the result as a performance metric.
For non-SNMP network resources, a Technology Pack provides Bulk collection formulas. A Bulk collection
formula, unlike an SNMP collection formula, has no executable instructions. A Bulk collection formula
consists of a metric name that is mapped by the Bulk Adaptor Design File to a statistic that resides in the
input file generated by a network resource.
Either type of collection formula outputs a metric and corresponding unique metric identifier (MID) that are
passed along the DataChannel to the Complex Metric Engine for processing.
How is the Data Processed and Loaded into the Database?
The Complex Metric Engine (CME) is a component in the DataChannel that performs calculations on data
gathered by the SNMP or Bulk collectors deployed in a network. These calculations include the following:
Pre-defined formulas that are provided by a Technology Pack
User-defined formulas created using the CME Formula API
Time aggregations for sub-elements
In addition to performing calculations on the data stream in the DataChannel, the CME also buffers and sorts
metric records according to their RIDs and MIDs to optimize how the data and metrics are stored in the database.
CME Operation
The CME is designed to work with data that is gathered over the space of one hour. Within that hour, there are
several distinct phases that characterize the operation of the CME:
Loading Phase
Building Phase
Processing Phase
Output Phase
Loading Phase
During the beginning of each hour, the CME creates a new network configuration model based on the inventory
structure that exists in the database at that time. This model is used as a snapshot of the network environment
and serves as the basis for all metric processing for the entire duration of the hour. At the end of the hour, the
CME polls the database for any changes that have been made to the inventory and creates a new network
configuration model for the next hour.
As the CME reloads its configuration hourly, any metrics produced by sub-elements following the last polling
period are rejected by the CME until the beginning of the next hour.
Building Phase
Once the current configuration model has been built, the CME creates a table of sub-elements and metrics that
are expected for the current hour. The CME uses the RIDs and MIDs to build the table and determine which
metrics should be arriving from the collectors. The table also specifies how resources are related, and determines
if there are any CME formulas that must be applied to a sub-elements metrics once the data is gathered.
Processing Phase
Whenever new data arrives at the CME, it is evaluated and stored in the appropriate table location, along with any
Resource Aggregation information. Once the input and processing dependencies for a metric in the table have
been met, the CME processes the metrics and stores the data until the end of the hour.
Output Phase
At the end of the current hour, the CME outputs everything in memory to the Hourly and Daily Loaders. The
data sent to the database loaders includes the sorted data for the current hour, and resource and group
aggregations for each of the processing periods up to the current time. The Hourly Loader computes group and
resource aggregations, while the Daily Loader creates metric statistics and inserts the data into the database.
How is the Data Reported?
The data collected, processed, and stored in the database by Netcool/Proviso is organized and output for
customers using reporter sets that are designed by developers and Professional Services personnel for a specific
Technology Pack.
A Technology Pack reporter set is a related group of reports that provide performance information on a specific
set of devices or resources that exist in a network. Each report consists of a series of queries that retrieve related
sub-elements and their corresponding metrics from the database using the RIDs and MIDs assigned during the
inventory and collection processes. The retrieved results are then organized within the report and are displayed
on a web portal in the form of tables, graphs, and charts.
A Technology Pack provides a variety of reports and charts, including:
Resource Summary Reports (RSTs) (sometimes referred to as Resource Summary Tables) aggregate data
across time for an individual sub-element and define the statistics that are relevant for a measure of its
network performance.
Group Summary Reports (GSTs) (sometimes referred to as Group Summary Tables) aggregate data across
both time and sub-elements, and define the statistics that are relevant for a measure of network performance
for a group of resources.
Detail Charts (DCs) display raw data for a metric that has been aggregated for an individual sub-element over
a particular period of time.
Dashboards display a series of abbreviated tables and charts that provide an overall summary of the metrics
collected for the target network resource supported by the Technology Pack.
Timeseries charts present time series information, where the x axis is time and the y axis is the data value.
TopN reports list the N highest values during a specified time range for a specific metric.
Resource Distribution charts (often referred to as pie charts) show the distribution of resources across
specific ranges. Typically, a legend for the Resource Distribution chart appears in the report.
Resource Over Threshold Tables (RTTs) display a list of resources that have violated their threshold for a
specific metric. Typically, users navigate to an RTT from a Group Summary Table (GST), using the threshold
overflow cell navigation link.
Ratio charts show the relationship of a single metric among different resources or a single resource among
different metrics.
Chapter 2: Supported Reports
Overview
The Nortel CS2000 Technology Pack supplies a set of reports suitable for displaying information about the
devices and activity associated with the Nortel CS2000 environment.
Reports contain metrics that are generated by the formulas that this technology pack provides. Metric names are
the same as the names of the formulas that generate them. For information about a metric that is listed for a
particular report, see the description of the associated formula in the collection formula chapter of this guide.
This chapter includes information to help you navigate to a particular report on the DataView portal. This
navigation path is the same as the path where the report has been deployed through the DataMart Resource
Editor. Note, however, that some reports are not explicitly deployed on the portal navigation path. You can
display such a report by "drilling down" to it from other reports.
For information about understanding report types, creating reports, configuring reports, viewing and working
with reports, and deploying reports, see the Netcool/Proviso DataView Users Guide. This Technology Pack Users
Guide assumes an understanding of the report-related topics discussed in the Netcool/Proviso DataView Users
Guide.
Report Reference
The following pages provide a reference of the reports that this technology pack provides. The reference pages
have the following sections:
Description. Describes the purpose and content of the report.
Reporter Set. The reporter set that the report belongs to.
Tables and Charts. The types of tables and charts in this report. For each listed table or chart type, this
section shows how many of the given type that the technology pack implements out of the total that the
stylesheet provides. For example:
Tables: Resource Summary Table (1 of 2 implemented)
Charts: Resource Distribution Chart (2 of 2 implemented)
Topic Page
Overview 5
Report Reference 5
Reports 8
In cases where the stylesheet information is not available for a given report, only the number of tables or
charts actually implemented is shown.
Metrics Used in Reports. The collection formulas that provide metrics for the report.
Navigation Path. The navigation path to use to select the report on the DataView portal.
Some reports are not accessed directly from a DataView portal navigation path. You can access such reports
by drilling down from another report. If you want to make the report available on the navigation path, you
can use the DataMart Resource Editor to deploy it.
Drills Down To. One or more reports that can be accessed by drilling down from a table or chart in the
report.
Drilled Down From. One or more reports from which you can drill down to reach the report.

Reporter Set Tree
This technology pack provides the reporter sets listed below. The list presents the reporter sets as they appear in
the DataView Navigator tree structure:
VOIP
...Softswitch
......Styles
......Dashboard
.........Nortel CS2K
......Infrastructure
.........Signaling Gateways
............Nortel USP
...............Device
...............Linkset
...............Routeset
...............Link
.........Media Gateways
............Device
...............Nortel PVG
............Nortel PVG Interface
............Nortel PVG Card
............Nortel PVG VSP
.........Class 5 Softswitch
............Nortel CS2K
...............CS2K
............Nortel SST
............Nortel SSL
............Nortel GWC
......Call Detail Records
.........Class 5 Softswitch
............Call Setup Quality
............Termination Cause
............Call Usage
............Call Distribution
............Media Gateway
............Path
............Zone
............Customer Profile
............Voice Quality
............Extension
...Carrier VOIP
......IEMS
.........AMS
.........CICM
.........SAM21
.........SPC
.........MS2000
......Voice Quality
.........CDR / IPDR
............Location
Reports
This technology pack provides the following reports:
Call Distribution Analysis
Call Distribution Analysis - DC
Call Server NPI
Call Server NPI - DC
Client Manager Quality
Client Manager Quality - DC
Compact (3PC) System Health
Compact (3PC) System Health - DC
Compact XA-Core System Health
Compact XA-Core System Health - DC
CS2K Device Quality
CS2K Device Quality - DC
CS2K Trunk Quality
CS2K Trunk Quality - DC
Customer Profile Analysis
Customer Profile Analysis - DC
Customer Profile QoS
Customer Profile QoS - DC
Extension QoS
Extension QoS - DC
Extension Quality
Extension Quality - DC
Extension Utilization
Extension Utilization - DC
GWC Health Report
GWC Health Report - DC
Line Quality Report
Line Quality Report - DC
MGW Call Utilization
MGW Call Utilization - DC
MGW QoS
MGW QoS - DC
MS2010 Announcements and Conferences
MS2010 Announcements and Conferences - DC
MS2010 Device Quality
MS2010 Device Quality - DC
MS2010 RTP-MP Analysis
MS2010 RTP-MP Analysis - DC
Nortel CS2K System Performance
Nortel CS2K System Performance - DC
Path Call Utilization
Path Call Utilization - DC
Path QoS
Path QoS - DC
Platform Software Metrics
Platform Software Metrics - DC
PVG Card Quality
PVG Card Quality - DC
PVG Card Temperature
PVG Card Temperature - DC
PVG Device Call Signaling
PVG Device Call Signaling - DC
PVG Device Usage
PVG Device Usage - DC
PVG Interface Usage
PVG Interface Usage - DC
PVG VSP Call Signaling
PVG VSP Call Signaling - DC
PVG VSP Quality
PVG VSP Quality - DC
RAS Port Statistics
RAS Port Statistics - DC
SAM21 Device Quality
SAM21 Device Quality - DC
SCAI Messaging
SCAI Messaging - DC
Server CPU and Memory
Server CPU and Memory - DC
Server Swap - DC
Session Policy Controller Quality
Session Policy Controller Quality - DC
SIP Inbound Response Report
SIP Inbound Response Report - DC
SIP Outbound Response Report
SIP Outbound Response Report - DC
SIP Transaction Report
SIP Transaction Report - DC
SLA Voice Quality Report
SLA Voice Quality Report - DC
Softswitch Call Utilization
Softswitch Call Utilization - DC
Softswitch Call Utilization - MLH
Softswitch QoS
Softswitch QoS - DC
SS-T Call Analysis
SS-T Call Analysis- DC
SS-T System
SS-T System - DC
SSL - DC
SSL Dashboard
Stream Quality
Stream Quality - DC
System Performance
System Performance - DC
Termination Cause Analysis
Termination Cause Analysis - DC
Termination Cause QoS
Termination Cause QoS - DC
TypeOfCall Call Setup and Termination
TypeOfCall Call Setup and Termination Quality - DC
TypeOfCall QoS
TypeOfCall QoS - DC
USP Device Quality
USP Device Quality - DC
USP Link Quality
USP Link Quality - DC
USP Linkset Quality
USP Linkset Quality - DC
USP Routeset Metrics
USP Routeset Metrics - DC
Voice Quality
Voice Quality - DC
Voice Quality Report
Voice Quality Report - DC
VOIP Dashboard
XA-Core System Health
XA-Core System Health - DC
Zone QoS
Zone QoS - DC
Zone Utilization
Zone Utilization - DC
The reports in this technology pack are described on the following pages.
Description
The Call Distribution Analysis - DC report aggregates call utilization information (number of calls, minutes of
use, and so on) for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. You can drill
down to this report from the Call Distribution Analysis report.
Reporter Set
Call Distribution
Tables and Charts
Charts: Time Series Chart
Ratio Chart
Metrics Used in Report
OffNetCall
OnNetCall
SuccessfulCall
TotalCall
UnsuccessfulCallBusy
UnsuccessfulCallInvalidAddress
UnsuccessfulCall
UnsuccessfulCallNetwork
UnsuccessfulCallNoAnswer
Navigation Path
Navigation path on the DataView portal:
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > Call Distribution
Drills Down To
None.
Drilled Down From
Description
The Call Distribution Analysis report aggregates call utilization information (number of calls, minutes of use, and
so on) for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. This report drills down
to the Call Distribution Analysis - DC report.
Reporter Set
Call Distribution
Tables and Charts
Tables: Resource Summary Table
Charts: Ratio Chart
TotalCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > Call Distribution
Drills Down To
Drilled Down From
None.
Description
The Call Server NPI - DC report provides network performance indicator information (NPI). This includes the
average holding time, call completion ratios and information on network jitter and delay. You can drill down to
this report from the Call Server NPI report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
AverageHoldingTime
CallCompletionRatio_EndOffice
CallCompletionRatio_Tandem
Delay
Jitter
NetworkEffectivenessRatio
PacketLoss
ServiceFailureRate
Navigation Path
This report is not deployed on the portal navigation path during the initial configuration of the technology pack.
To display this report, drill down to it from another report or deploy it with the DataMart Resource Editor.
Drills Down To
None.
Drilled Down From
Call Server NPI
Call Server NPI
Description
The Call Server NPI report provides network performance indicator information (NPI). This includes the
average holding time, call completion ratios and information on network jitter and delay. This report drills down
to the Call Server NPI - DC report.
Reporter Set
CS2K
Tables and Charts
AverageHoldingTime
Delay
Jitter
PacketLoss
ServiceFailureRate
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel CS2K > Device
Drills Down To
Drilled Down From
None.
Description
The Client Manager Quality - DC report aggregates device quality metrics for the Nortel Centrex IP Client
Manager (CICM). The report displays device quality metrics for all Nortel CICM devices operating in the Nortel
Carrier VoIP environment. You can drill down to this report from the Client Manager Quality report.
Reporter Set
CICM
Tables and Charts
Ratio Chart
ActiveConnections
ActiveSessions
HalfCallAttempts
LoggedInUsers
PercentageCpuUsed
PercentageMemoryUsed
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > IP Centrex > Nortel CICM
Drills Down To
None.
Drilled Down From
Description
The Client Manager Quality report aggregates device quality metrics for the Nortel Centrex IP Client Manager
(CICM). The report displays device quality metrics for all Nortel CICM devices operating in the Nortel Carrier
VoIP environment. This report drills down to the Client Manager Quality - DC report.
Reporter Set
CICM
Tables and Charts
ActiveConnections
ActiveSessions
HalfCallAttempts
hrSystemUptime
LoggedInUsers
PercentageCpuUsed
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > IP Centrex > Nortel CICM
Drills Down To
Drilled Down From
None.
Description
The Compact (3PC) System Health - DC report provides system health information for Compact (3PC) devices.
This includes information on CPU utilization, memory utilization and sparing bandwidth. You can drill down to
this report from the Compact (3PC) System Health report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
CallAgentCPUUtilization
CallAgentMemoryUtilization
SparingBandwidth
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Nortel Compact (3PC) System Health report aggregates health information for Nortel Communication
Server 2000-Compact systems. This information includes CPU utilization, memory utilization and sparing
bandwidth. This report drills down to the Nortel Compact (3PC) System Health - DC report.
Reporter Set
CS2K
Tables and Charts
SparingBandwidth
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Compact XA-Core System Health report provides health information for Nortel Compact Extended Core
(XA-Core) systems. This report drills down to the Compact XA-Core System Health - DC report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
AUXCP
BusyCallHourAttempts
ENGCAP
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Nortel Compact XA-Core System Health report provides health information for Nortel Compact Extended
Core (XA-Core) systems. This report drills down to the Nortel XA-Core System Health - DC report.
Reporter Set
CS2K
Tables and Charts
AUXCP
ENGCAP
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The CS2K Device Quality - DC report aggregates quality information (CPU utilization, total successful calls, and
so forth) for all Nortel Communication Server 2000 (CS2K) devices operating in the Nortel Carrier VoIP
environment. You can drill down to this report from the CS2K Device Quality report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
IncomingTrunkToLineCallAttempts
IntraSwitchLineToLineCallAttempts
OutgoingLineToTrunkCallAttempts
TransitTrunkToTrunkCallAttempts
Navigation Path
Drills Down To
None.
Drilled Down From
CS2K Device Quality
CS2K Device Quality
Description
The CS2K Device Quality report aggregates quality information (CPU utilization, total successful calls, and so
forth) for all Nortel Communication Server 2000 (CS2K) devices operating in the Nortel Carrier VoIP
environment. This report drills down to the CS2K Device Quality - DC report.
Reporter Set
CS2K
Tables and Charts
CPUutilizationForCallProcessing%
TotalSoftswitchCallAttempts
TotalSoftswitchSuccessfulCalls%
TotalSoftswitchSuccessfulCalls
TotalSoftswitchUnsuccessfulCalls%
TotalSoftswitchUnsuccessfulCalls
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Nortel CS2K Trunk Quality - DC report aggregates trunk quality information (successful
incoming/outgoing calls, total trunk routing failures, and so forth) for all Trunks controlled by all Nortel
Communication Server 2000 (CS2K) devices operating in the Nortel Carrier VoIP environment. You can drill
down to this report from the CS2K Trunk Quality report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
IncomingCallTrunkRoutingFailure
IncomingSuccessfulCalls
OutgoingCallTrunkRoutingFailure
OutgoingSuccessfulCalls%
OutgoingSuccessfulCalls
TotalCallBidAttempts
TrunkGOS
TrunkOverflow
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel CS2K > Trunk
Drills Down To
None.
Drilled Down From
CS2K Trunk Quality
CS2K Trunk Quality
Description
The Nortel CS2K Trunk Quality report aggregates trunk quality information (successful incoming/outgoing
calls, total trunk routing failures, and so forth) for all Trunks controlled by all Nortel Communication Server 2000
(CS2K) devices operating in the Nortel Carrier VoIP environment. This report drills down to CS2K Trunk
Quality - DC report.
Reporter Set
CS2K
Tables and Charts
IncomingAnswerSeizureRatio%
IncomingSuccessfulCalls%
OutgoingAnswerSeizureRatio%
TotalCallTrunkRoutingFailure%
TrunkGOS
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel CS2K > Trunk
Drills Down To
Drilled Down From
None.
Description
The Customer Profile Analysis - DC report aggregates call information (total calls, incoming calls, and so on) for
all customer profiles. You can drill down to this report from the Customer Profile Analysis report.
Reporter Set
Customer Profile
Tables and Charts
Ratio Chart
IncomingCall
InternalCall
InternationalCall
MobileCall
NationalCall
OutgoingCall
TotalCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Customer Profile
Drills Down To
None.
Drilled Down From
Description
The Customer Profile Analysis report aggregates call information (total calls, incoming calls, and so on) for all
customer profiles. This report drills down to the Customer Profile Analysis - DC report.
Reporter Set
Customer Profile
Tables and Charts
Charts: Ratio Chart
IncomingCall
InternalCall
OutgoingCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Customer Profile
Drills Down To
Drilled Down From
None.
Description
The Customer Profile QoS - DC report aggregates QoS information (average loss rate, round trip average, and
so on) for all customer profiles. You can drill down to this report from the Customer Profile QoS report.
Reporter Set
Customer Profile
Tables and Charts
Charts: Resource Time Series Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By
Customer Profile
Drills Down To
None.
Drilled Down From
Description
The Customer Profile QoS report aggregates QoS information (average loss rate, round trip average, and so on)
for all customer profiles. This report drills down to the Customer Profile QoS - DC report.
Reporter Set
Customer Profile
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
Customer Profile
Drills Down To
Drilled Down From
None.
Extension QoS - DC
Description
The Extension QoS - DC report aggregates voice quality information (average loss rate, round trip average, and
so on) for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. You can drill down to
this report from the Extension QoS report.
Reporter Set
Extension
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > Extension
Drills Down To
None.
Drilled Down From
Extension QoS
Extension QoS
Description
The Extension QoS report aggregates voice quality information (average loss rate, round trip average, and so on)
for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. This report drills down to the
Extension QoS - DC report.
Reporter Set
Extension
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
Drills Down To
Extension QoS - DC
Drilled Down From
None.
Description
The Extension Quality - DC report aggregates call information (number of calls, minutes of use, and so on) for
all call extensions. You can drill down to this report from the Extension Quality report.
Reporter Set
Extension
Tables and Charts
Ratio Chart
InboundPacket
LostPacket
OutboundPacket
PacketDelayVariation
PacketLatency
Navigation Path
Drills Down To
None.
Drilled Down From
Extension Quality
Extension Quality
Description
The Extension Quality report aggregates call information (number of calls, minutes of use, and so on) for all call
extensions. This report drills down to the Extension Quality - DC report.
Reporter Set
Extension
Tables and Charts
Charts: Ratio Chart
InboundPacket
LostPacket
OutboundPacket
PacketLatency
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Extension Utilization - DC report aggregates call information (number of calls, minutes of use, and so on)
for all call extensions. You can drill down to this report from the Extension Utilization report.
Reporter Set
Extension
Tables and Charts
Ratio Chart
CallDuration
CDR Extension Successful Calls Percentage (CME)
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Extension
Drills Down To
None.
Drilled Down From
Description
The Extension Utilization report aggregates call information (number of calls, minutes of use, and so on) for all
call extensions. This report drills down to the Extension Utilization - DC report.
Reporter Set
Extension
Tables and Charts
Charts: Ratio Chart
CDR Extension Call Duration (CME)
InternationalCall
MobileCall
NationalCall
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Extension
Drills Down To
Drilled Down From
None.
Description
The GWC Health Report - DC provides system health information for a Nortel Media Gateway device. This
includes information on call completion, call attempts and mid-call failure rates. You can drill down to this report
from the GWC Health Report.
Reporter Set
Nortel GWC
Tables and Charts
Ratio Chart
BHHCA
CCR
Mid-call Failure Rate
Processor
Navigation Path
Drills Down To
None.
Drilled Down From
GWC Health Report
GWC Health Report
Description
The GWC Health Report provides system health information for Nortel Media Gateway devices. This includes
information on call completion, call attempts and mid-call failure rates. This report drills down to the GWC
Health Report - DC.
Reporter Set
Nortel GWC
Tables and Charts
BHHCA
CCR
Processor
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel GWC
Drills Down To
Drilled Down From
None.
Description
The Line Quality Report - DC provides information on line quality. This includes information on throughput
traffic, attempted calls and call failures. You can drill down to this report from the Line Quality Report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
OriginatingAbandonsBeforeConnection
OriginatingAttemptFailures
OriginatingFailures
OriginatingLineCallAttempts
TerminatingFailures
TrafficBusyUse
Navigation Path
Drills Down To
None.
Drilled Down From
Line Quality Report
Line Quality Report
Description
The Line Quality Report provides information on line quality. This includes information on throughput traffic,
attempted calls and call failures. This report drills down to the Line Quality Report - DC.
Reporter Set
CS2K
Tables and Charts
OriginatingFailures
TerminatingFailures
TrafficBusyUse
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The MGW Call Utilization - DC report aggregates call utilization information (total calls, successful calls, and so
on) for all Media Gateways controlled by all Nortel CS2000 devices operating in the Nortel Carrier VoIP
environment. You can drill down to this report from the MGW Call Utilization report, from the SSL Dashboard
report, and from the VOIP Dashboard report.
Reporter Set
Media Gateway
Tables and Charts
Ratio Chart
CallDuration
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Media Gateway
Drills Down To
None.
Drilled Down From
VOIP Dashboard
Description
The MGW Call Utilization report aggregates call utilization information (total calls, successful calls, and so on)
for all Media Gateways controlled by all Nortel CS2000 devices operating in the Nortel Carrier VoIP
environment. This report drills down to the MGW Call Utilization - DC report.
Reporter Set
Media Gateway
Tables and Charts
Charts: Ratio Chart
CallDuration
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Media Gateway
Drills Down To
Drilled Down From
None.
MGW QoS - DC
Description
The MGW QoS - DC report aggregates QoS information (average loss rate, round trip average, and so on) for
all Media Gateways controlled by all Nortel CS2000 devices operating in the Nortel CS2000 environment. You
can drill down to this report from the MGW QoS report.
Reporter Set
Media Gateway
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Media
Gateway
Drills Down To
None.
Drilled Down From
MGW QoS
MGW QoS
Description
The MGW QoS report aggregates QoS information (average loss rate, round trip average, and so on) for all Media
Gateways controlled by all Nortel CS2000 devices operating in the Nortel CS2000 environment. This report drills
down to the MGW QoS - DC report.
Reporter Set
Media Gateway
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Media
Gateway
Drills Down To
MGW QoS - DC
Drilled Down From
None.
Description
The MS2010 Announcements and Conferences - DC report provides information related to announcement and
conference port usage and occupancy. You can drill down to this report from the MS2010 Announcements and
Conferences report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
3PortConfFailureRatio
3PortOcc
6PortOcc
ANNFailureRatio
ANNocc
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Servers > Nortel MS20xx Device
Drills Down To
None.
Drilled Down From
Description
The MS2010 Announcements and Conferences report provides information related to announcement and
conference port usage and occupancy. This report drills down to the MS2010 Announcements and Conferences
- DC report.
Reporter Set
CS2K
Tables and Charts
3PortOcc
6PortOcc
ANNFailureRatio
ANNocc
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The MS2010 Device Quality - DC report aggregates device quality information (BCT requests, conference
requests, TT requests, and so on) for each Nortel Media Server 2010 (MS 2010) device operating in the Nortel
Carrier VoIP environment. You can drill down to this report from the MS2010 Device Quality report.
Reporter Set
MS2000
Tables and Charts
Ratio Chart
acPerfBctFailedDueToLackOfResources
acPerfBctRequests
acPerfConfAddFailedDueToLackOfResources
acPerfConfFailedDueToLackOfResources
acPerfConfRequests
acPerfIvrContDigitCollectFailedDueToLackOfResources
acPerfIvrPlayCollectFailedDueToLackOfResources
acPerfIvrPlayCollectFailedDueToProvMismatch
acPerfIvrPlayFailedDueToLackOfResources
acPerfIvrPlayFailedDueToProvMismatch
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The MS2010 Device Quality report aggregates device quality information (BCT requests, conference requests,
TT requests, and so on) for each Nortel Media Server 2010 (MS 2010) device operating in the Nortel Carrier VoIP
environment. This report drills down to the MS2010 Device Quality - DC report.
Reporter Set
MS2000
Tables and Charts
acPerfBctRequests
acPerfConfRequests
acPerfIvrPlayCollectRequests
acPerfIvrPlayRequests
acPerfSystemPacketEndpointsInUse
acPerfTtRequests
hrSystemUptime
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The MS2010 RTP-MP - DC report aggregates device quality information (RTP failures and RTP receiver lost
packets) for each Nortel Media Server 2010 (MS 2010) device operating in the Nortel Carrier VoIP environment.
You can drill down to this report from MS2010 RTP-MP report.
Reporter Set
MS2000
Tables and Charts
Ratio Chart
acPerfRtpFailedDueToLackOfResources
acPerfRtpRcvrLostPackets
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The MS2010 RTP-MP report aggregates device quality information (RTP failures and RTP receiver lost packets)
for each Nortel Media Server 2010 (MS 2010) device operating in the Nortel Carrier VoIP environment. This
report drills down to the MS2010 RTP-MP - DC report.
Reporter Set
MS2000
Tables and Charts
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Nortel CS2K System Performance - DC report contains perfomance information for a Nortel CS2000
Communication Server system. This information includes the number of dropped calls and the number of calls
terminating with a carrier busy or trunk busy message. You can drill down to this report from the Nortel CS2K
System Performance report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
LossOfEstablishedCalls
TrunkOrCarrierBusy
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Nortel CS2K System Performance report contains perfomance information for Nortel CS2000
Communication Server systems. This information includes the number of dropped calls and the number of calls
terminating with a carrier busy or trunk busy message. This report drills down to the Nortel CS2K System
Performance - DC report.
Reporter Set
CS2K
Tables and Charts
TrunkOrCarrierBusy
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Path Call Utilization - DC report aggregates call utilization information (total calls, successful calls, and so
on) for all Paths controlled by all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. You
can drill down to this report from the Path Call Utilization report.
Reporter Set
Path
Tables and Charts
Ratio Chart
CallDuration
DropCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Path
Drills Down To
None.
Drilled Down From
Description
The Path Call Utilization report aggregates call utilization information (total calls, successful calls, and so on) for
all Paths controlled by all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. This report
drills down to the Path Call Utilization - DC report.
Reporter Set
Path
Tables and Charts
Charts: Ratio Chart
CallDuration
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Path
Drills Down To
Drilled Down From
None.
Path QoS - DC
Description
The Path QoS - DC report aggregates QoS information (average loss rate, round trip average, and so on) for all
Paths controlled by all Nortel CS2000 devices operating in the Nortel CS2000 environment. You can drill down
to this report from the Path QoS report.
Reporter Set
Path
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Path
Drills Down To
None.
Drilled Down From
Path QoS
Path QoS
Description
The Path QoS report aggregates QoS information (average loss rate, round trip average, and so on) for all Paths
controlled by all Nortel CS2000 devices operating in the Nortel CS2000 environment. This report drills down to
the Path QoS - DC report.
Reporter Set
Path
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Path
Drills Down To
Path QoS - DC
Drilled Down From
None.
Description
The PVG Card Quality - DC report aggregates shelf card quality information (CPU Utilization and message block
in use) for the Control Processor card component of the PVG device. The report displays shelf card quality
information for all Control Processor cards associated with all PVG devices operating in the Nortel Carrier VoIP
environment. You can drill down to this report from the PVG Card Quality report.
Reporter Set
Nortel PVG Card
Tables and Charts
Ratio Chart
CardUtilAvg
LMBUtil
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Gateways > Nortel PVG > Card
Drills Down To
None.
Drilled Down From
PVG Card Quality
PVG Card Quality
Description
The PVG Card Quality report aggregates shelf card quality information (CPU Utilization and message block in
use) for the Control Processor card component of the PVG device. The report displays shelf card quality
information for all Control Processor cards associated with all PVG devices operating in the Nortel Carrier VoIP
environment. This report drills down to PVG Card Quality - DC report.
Reporter Set
Nortel PVG Card
Tables and Charts
Charts: Ratio Chart
CardUtilAvg
LMBUtil
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The PVG Card Temperature - DC report aggregates fabric card quality information (temperature) for the Fabric
card component of the PVG device. The report displays fabric card quality information for all Fabric cards
associated with all PVG devices operating in the Nortel Carrier VoIP environment. You can drill down to this
report from the PVG Card Temperature report.
Reporter Set
Nortel PVG Card
Tables and Charts
Ratio Chart
MaxTemp
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The PVG Card Temperature report aggregates fabric card quality information (temperature) for the Fabric card
component of the PVG device. The report displays fabric card quality information for all Fabric cards associated
with all PVG devices operating in the Nortel Carrier VoIP environment. This report drills down to PVG Card
Temperature - DC report.
Reporter Set
Nortel PVG Card
Tables and Charts
Charts: Ratio Chart
MaxTemp
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The PVG Device Call Signaling - DC report aggregates device call signaling information (congested seconds,
H248 retransmission, and so on) for the PVG device. The report displays device call signaling information for all
PVG devices operating in the Nortel Carrier VoIP environment. You can drill down to this report from the PVG
Device Call Signaling report.
Reporter Set
Nortel PVG
Tables and Charts
Ratio Chart
CongestedSeconds
Failovers
H248Retransmission
NetworkCallFailure
OverloadCmdRejected
TDMCallFailures
TotalMinutesOfUse
TotalSuccessfulCalls
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Gateways > Nortel PVG > Device
Drills Down To
None.
Drilled Down From
Description
The PVG Device Call Signaling report aggregates device call signaling information (congested seconds, H248
retransmission, and so on) for the PVG device. The report displays device call signaling information for all PVG
devices operating in the Nortel Carrier VoIP environment. This report drills down to PVG Device Call Signaling
- DC report.
Reporter Set
Nortel PVG
Tables and Charts
Charts: Ratio Chart
CongestedSeconds
Failovers
H248Retransmission
OverloadCmdRejected
TotalMinutesOfUse
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Nortel PVG Device Usage - DC report aggregates device call usage information (total active calls, total
minutes of use, and so on) for the PVG device. The report displays device call usage information for all PVG
devices operating in the Nortel Carrier VoIP environment. You can drill down to this report from the PVG
Device Usage report.
Reporter Set
Nortel PVG
Tables and Charts
Ratio Chart
AvgCPUutilizationCardProcessing
AvgCPUutilizationVSPCard
Failovers
NetworkCallFailure
TDMCallFailures
TotalActiveCalls
TotalICMPPackets
TotalMinutesOfUse
TotalPackets
TotalTCPPackets
TotalUDPPackets
Navigation Path
Drills Down To
None.
Drilled Down From
PVG Device Usage
PVG Device Usage
Description
The Nortel PVG Device Usage report aggregates device call usage information (total active calls, total minutes
of use, and so on) for the PVG device. The report displays device call usage information for all PVG devices
operating in the Nortel Carrier VoIP environment. The report also displays two bar graphs:
TDM vs IP Network Failure Ratio
TCP-UDP-ICMP Packets Ratio
This report drills down to the PVG Device Usage - DC report.
Reporter Set
Nortel PVG
Tables and Charts
Charts: Ratio Chart
Failovers
NetworkCallFailure
TDMCallFailures
TotalActiveCalls
TotalICMPPackets
TotalMinutesOfUse
TotalPackets
TotalTCPPackets
TotalUDPPackets
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The PVG Interface Usage - DC report aggregates interface usage information (average inbound/outbound
utilization, total packets discarded, and so on) for each Media Gateway Interface (MGI) operating in the Nortel
Carrier VoIP environment. You can drill down to this report from the PVG Interface Usage report.
Reporter Set
Nortel PVG Interface
Tables and Charts
Ratio Chart
AverageInboundUtilization
AverageOutboundUtilization
InboundPacketRate
OutboundPacketRate
TotalNumberOfDiscardedPackets
TotalNumberOfPacketExceptions
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Gateways > Nortel PVG > Interface
Drills Down To
None.
Drilled Down From
PVG Interface Usage
PVG Interface Usage
Description
The PVG Interface Usage report aggregates interface usage information (average inbound/outbound utilization,
total packets discarded, and so on) for each Media Gateway Interface (MGI) operating in the Nortel Carrier VoIP
environment. This report drills down to the PVG Interface Usage - DC report.
Reporter Set
Tables and Charts
TotalNumberOfTCPPackets
TotalNumberOfUDPPackets
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Gateways > Nortel PVG > Interface
Drills Down To
Drilled Down From
None.
Description
The PVG VSP Call Signaling - DC report aggregates call signaling information (congested seconds, failovers, and
so on) for each Media Gateway VSP Call Card (CC) operating in the Nortel Carrier VoIP environment. You can
drill down to this report from the PVG VSP Call Signaling report, from the SSL Dashboard report, and from the
VOIP Dashboard report.
Reporter Set
Nortel PVG VSP
Tables and Charts
Ratio Chart
CongestedSeconds
Failovers
Failovers
H248Retransmission
NetworkCallFailure
OverloadCmdRejected
TotalMinutesOfUse
TotalTDMCallFails
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Gateways > Nortel PVG > VSP
Drills Down To
None.
Drilled Down From
VOIP Dashboard
Description
The PVG VSP Call Signaling report aggregates call signaling information (congested seconds, failovers, and so
on) for each Media Gateway VSP Call Card (CC) operating in the Nortel Carrier VoIP environment. The display
also shows a bar graph called TDM vs IP Network Failure Ratio. This report drills down to the PVG VSP Call
Signaling - DC report.
Reporter Set
Nortel PVG VSP
Tables and Charts
Charts: Ratio Chart
CongestedSeconds
Failovers
H248Retransmission
NetworkCallFailure
OverloadCmdRejected
TotalMinutesOfUse
TotalTDMCallFails
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The PVG VSP Quality - DC report aggregates CPU utilization information for each Media Gateway VSP
Processor Card (PC) operating in the Nortel Carrier VoIP environment. You can drill down to this report from
the PVG VSP Quality report.
Reporter Set
Nortel PVG VSP
Tables and Charts
Ratio Chart
Navigation Path
Drills Down To
None.
Drilled Down From
PVG VSP Quality
PVG VSP Quality
Description
The PVG VSP Quality report aggregates CPU utilization information for each Media Gateway VSP Processor
Card (PC) operating in the Nortel Carrier VoIP environment. This report drills down to the PVG VSP Quality -
DC report.
Reporter Set
Nortel PVG VSP
Tables and Charts
Charts: Ratio Chart
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The RAS Port Statistics - DC report aggregates RAS port performance information (bytes received, bytes
transmitted, and so on) for each Nortel Remote Access Server (RAS) Port device operating in the Nortel Carrier
VoIP environment. You can drill down to this report from the RAS Port Statistics report.
Reporter Set
AMS
Tables and Charts
Ratio Chart
Alignment Errors
Buffer Overrun Errors
CRC Errors
Percent Compression Out
Timeout Errors
Total Errors
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Servers > Nortel AMS > RAS Port
Drills Down To
None.
Drilled Down From
RAS Port Statistics
RAS Port Statistics
Description
The RAS Port Statistics report aggregates RAS port performance information (bytes received, bytes transmitted,
and so on) for each Nortel Remote Access Server (RAS) Port device operating in the Nortel Carrier VoIP
environment. This report drill downs to the RAS Port Statistics - DC report.
Reporter Set
AMS
Tables and Charts
Alignment Errors
Bytes Received
Bytes Transmitted
CRC Errors
Timeout Errors
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Servers > Nortel AMS > RAS Port
Drills Down To
Drilled Down From
None.
Description
The SAM21 Device Quality - DC report aggregates device quality information (cell drop count, oversized PDU
count, and so forth) for all Nortel SAM21 Shelf Controller devices operating in the Nortel Carrier VoIP
environment. You can drill down to this report from the SAM21 Device Quality report.
Reporter Set
SAM21
Tables and Charts
Ratio Chart
bytesRxedPerSec
bytesSentPerSec
cellDropCount
oversizedPDUCount
rxedTimeoutCount
totalBytesRxed
totalBytesSent
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SAM21
Drills Down To
None.
Drilled Down From
Description
The SAM21 Device Quality report aggregates device quality information (cell drop count, oversized PDU count,
and so forth) for all Nortel SAM21 Shelf Controller devices operating in the Nortel Carrier VoIP environment.
This report drills down to the SAM21 Device Quality - DC report.
Reporter Set
SAM21
Tables and Charts
bytesRxedPerSec
bytesSentPerSec
cellDropCount
oversizedPDUCount
rxedTimeoutCount
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SAM21
Drills Down To
Drilled Down From
None.
SCAI Messaging - DC
Description
The SCAI Messaging - DC report provides health information about switch-to-computer application interface
messaging activity. You can drill down to this report from the SCAI Messaging report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
SCAI
Navigation Path
Drills Down To
None.
Drilled Down From
SCAI Messaging
SCAI Messaging
Description
The SCAI Messaging report provides health information about switch-to-computer application interface
messaging activity. This report drills down to the SCAI Messaging - DC report.
Reporter Set
CS2K
Tables and Charts
SCAI
Navigation Path
Drills Down To
SCAI Messaging - DC
Drilled Down From
None.
Description
The Server CPU and Memory - DC report provides information on CPU and memory utilization for a device.
This information includes the total amount of available memory, and the minimum, median, and maximum CPU
occupancy for the reporting period. You can drill down to this report from the Server CPU and Memory report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
maxCpuOccupancyValue
maxRamUtilizationValue
medianCpuOccupancyValue
medianRamUtilizationValue
minCpuOccupancyValue
minRamUtilizationValue
Navigation Path
Drills Down To
None.
Drilled Down From
SSL Dashboard
Description
The Server and CPU Memory report provides information about CPU and memory usage for a device. This
information includes the minimum, median and maximum utilization and occupancy for the reporting period.
This report also includes information on the memory and swap space utilization for the device. This report drills
down to the Server CPU and Memory - DC report and to the Server Swap - DC report.
Reporter Set
Nortel SSL
Tables and Charts
Tables: Summary Table
Charts: Chart
maxSwapUtilizationValue
medianSwapUtilizationValue
minSwapUtilizationValue
totalRam
totalSwap
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SSL
Drills Down To
Server Swap - DC
Drilled Down From
None.
Server Swap - DC
Description
The Server Swap - DC report provides information on swap space usage for a device. You can drill down to this
report from the Server CPU and Memory report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
totalRam
totalSwap
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Session Policy Controller Quality - DC report aggregates device quality information (storage allocation
failures and storage used) for all Nortel Session Policy Controller (SPC) devices operating in the Nortel Carrier
VoIP environment. You can drill down to this report from the Session Policy Controller Quality report.
Reporter Set
SPC
Tables and Charts
Ratio Chart
hrStorageAllocationFailures
hrStorageUsed
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SPC
Drills Down To
None.
Drilled Down From
Description
The Session Policy Controller Quality report aggregates device quality information (storage allocation failures and
storage used) for all Nortel Session Policy Controller (SPC) devices operating in the Nortel Carrier VoIP
environment. This report drills down to the Session Policy Controller Quality - DC report.
Reporter Set
SPC
Tables and Charts
hrStorageUsed
hrSystemUptime
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SPC
Drills Down To
Drilled Down From
None.
Description
The SIP Inbound Reponse Report - DC contains information on inbound SIP activity. You can drill down to this
report from the SIP Inbound Reponse Report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
In_2xx
In_3xx
In_4xx
In_5xx
In_6xx
In_Unknown
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The SIP Inbound Reponse Report contains information about inbound SIP activity. This report drills down to
the SIP Inbound Reponse Report - DC.
Reporter Set
Nortel SSL
Tables and Charts
Charts: Ratio Chart
In_2xx
In_3xx
In_4xx
In_5xx
In_6xx
In_Unknown
Navigation Path
Drills Down To
Drilled Down From
Description
The SIP Outbound Reponse Report - DC contains information on outbound SIP activity. You can drill down to
this report from the SIP Outbound Reponse Report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
Out_2xx
Out_3xx
Out_4xx
Out_5xx
Out_6xx
Out_Unknown
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The SIP Outbound Reponse Report contains information about outbound SIP activity. This report drills down
to the SIP Outbound Reponse Report - DC.
Reporter Set
Nortel SSL
Tables and Charts
Charts: Ratio Chart
Out_2xx
Out_3xx
Out_4xx
Out_5xx
Out_6xx
Out_Unknown
Navigation Path
Drills Down To
Drilled Down From
Description
The SIP Transaction Report - DC provides information about SIP transactions. You can drill down to this report
from the SIP Transaction Report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
TotalActive
TotalIn
TotalOut
Navigation Path
Drills Down To
None.
Drilled Down From
SSL Dashboard
Description
The SIP Transaction Report provides information about SIP transactions. This report drills down to the SIP
Transaction Report - DC.
Reporter Set
Nortel SSL
Tables and Charts
Charts: Ratio Chart
TotalActive
TotalIn
TotalOut
Navigation Path
Drills Down To
Drilled Down From
Description
The SLA Voice Quality Report - DC displays SLA voice quality data for Nortel CS2000 devices operating in the
Nortel Carrier VoIP environment. You can drill down to this report from the SLA Voice Quality Report.
Reporter Set
Location
Tables and Charts
Ratio Chart
AboveMOSpercentage
ListeningQualityMOS
TransmissionStreams
UnderMOSLimit(3.7)all
UnderMOSLimit(3.7)offnet
UnderMOSLimit(3.7)onnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > Location
Drills Down To
None.
Drilled Down From
Description
The SLA Voice Quality Report displays SLA voice quality data for Nortel CS2000 devices operating in the Nortel
Carrier VoIP environment. This report drills down to the SLA Voice Quality Report - DC.
Reporter Set
Location
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
ListeningQualityMOS
TransmissionStreams
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Softswitch Call Utilization - DC report aggregates call utilization information (number of calls, minutes of
use, and so on) for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. You can drill
down to this report from the Softswitch Call Utilization report and from the Softswitch Call Utilization - MLH
report.
Reporter Set
Call Usage
Tables and Charts
Ratio Chart
CallDuration
CDR Softswitch Device Successful Calls percentage (CME)
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Softswitch
Drills Down To
None.
Drilled Down From
Description
Softswitch Call Utilization - MLH is a Most Loaded Hour (MLH) Resource Summary Table (RST) that aggregates
call utilization information (number of calls, minutes of use, and so on) for all Nortel CS2000 devices operating
in the Nortel Carrier VoIP environment.
Reporter Set
Call Usage
Tables and Charts
No table and chart information is available for this report (stylesheet PVLsResDistrib_Ratio_MLH_RST.html).
CDR Softswitch Device Minute Of Use (CME)
TotalCall
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Softswitch Call Utilization report aggregates call utilization information (number of calls, minutes of use, and
so on) for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. This report drills down
to the Softswitch Call Utilization - DC report.
Reporter Set
Call Usage
Tables and Charts
Charts: Ratio Chart
CS2K Grade of Service CME
InternationalCall
MobileCall
NationalCall
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
Drills Down To
Drilled Down From
None.
Softswitch QoS - DC
Description
The Softswitch QoS - DC report aggregates QoS information (average loss rate, round trip average, and so on)
for all Nortel CS2000 devices operating in the Nortel CS2000 environment. You can drill down to this report
from the Softswitch QoS report.
Reporter Set
Voice Quality
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K >
Softswitch Quality
Drills Down To
None.
Drilled Down From
Softswitch QoS
Softswitch QoS
Description
The Softswitch QoS report aggregates QoS information (average loss rate, round trip average, and so on) for all
Nortel CS2000 devices operating in the Nortel CS2000 environment. This report drills down to the Softswitch
QoS - DC report.
Reporter Set
Voice Quality
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
Softswitch Quality
Drills Down To
Softswitch QoS - DC
Drilled Down From
None.
Description
The SS-T Call Analysis - DC report aggregates call information (Far End Remote information, Local Gateway
Controller information, and so on) for all Nortel Session Server - Trunk devices operating in the Nortel Carrier
VoIP environment. You can drill down to this report from the SS-T Call Analysis report.
Reporter Set
Nortel SST
Tables and Charts
Ratio Chart
FERserverCCRforTheSSTnode
FERserverMHTforTheSSTnode
FERserverMTTforTheSSTnode
FERserverNERforTheSSTnetwork
FERserverNERforTheSSTnode
InboundInvitePostDialDelay
LocalGWCCCRforTheSSTnode
LocalGWCMHTforTheSSTnode
LocalGWCMTTforTheSSTnode
LocalGWCNERforTheSSTnetwork
LocalGWCNERforTheSSTnode
OutboundInvitePostDialDelay
Navigation Path
Drills Down To
None.
Drilled Down From
SS-T Call Analysis
SS-T Call Analysis
Description
The SS-T Call Analysis report aggregates call information (Far End Remote information, Local Gateway
Controller information, and so on) for all Nortel Session Server - Trunk devices operating in the Nortel Carrier
VoIP environment. This report drills down to the SS-T Call Analysis - DC report.
Reporter Set
Nortel SST
Tables and Charts
Charts: Ratio Chart
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SST
Drills Down To
Drilled Down From
None.
SS-T System - DC
Description
The SS-T System - DC report aggregates device information (call volume, calls released, and so on) for all Nortel
Session Server - Trunk devices operating in the Nortel Carrier VoIP environment. You can drill down to this
report from the SS-T System report.
Reporter Set
Nortel SST
Tables and Charts
Ratio Chart
CallsReleasedBySST
CallVolumeForTheSSTnode
Processor
SimultaneousCalls
Navigation Path
Drills Down To
None.
Drilled Down From
SS-T System
SS-T System
Description
The SS-T System report aggregates device information (call volume, calls released, and so on) for all Nortel
Session Server - Trunk devices operating in the Nortel Carrier VoIP environment. This report drills down to the
SS-T System - DC report.
Reporter Set
Nortel SST
Tables and Charts
Tables: Summary Table
Charts: Chart
CallsReleasedBySST
Processor
SimultaneousCalls
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Softswitch Platform > Nortel SST
Drills Down To
SS-T System - DC
Drilled Down From
None.
SSL - DC
Description
The SSL - DC report contains activity information for a Session Server Line (SSL) system. You can drill down to
this report from the SSL Dashboard report.
Reporter Set
Nortel SSL
Tables and Charts
Ratio Chart
Processor
SSLOverload
TotalActive
TotalIn
TotalOut
Transactions
Navigation Path
Drills Down To
None.
Drilled Down From
SSL Dashboard
SSL Dashboard
Description
The SSL - Dashboard report provides general information about Session Server Line (SSL) activity. This
information includes the median CPU occupancy, the nodal network effectiveness ration, and the SSL overload
measured as number of 503 messages observed. This report drills down to the MGW Call Utilization - DC report,
the PVG VSP Call Signaling - DC report, and the SSL - DC report.
Reporter Set
Nortel SSL
Tables and Charts
Tables: TopN Table
Charts: Ratio Chart
Group Time Series Chart
Resource Distribution Chart
Nodal NER (CME)
SSLOverload
TotalActive
Navigation Path
Drills Down To
SSL - DC
Drilled Down From
None.
Stream Quality - DC
Description
The Stream Quality - DC report contains system performance information (total files transcoded, allocated audio
buffers, and so on) for each Nortel Announcement Media Server (AMS) device operating in the Nortel Carrier
VoIP environment. You can drill down to this report from the Stream Quality report.
Reporter Set
AMS
Tables and Charts
Ratio Chart
ActiveIvrMPConnections
AllocatedAudioBuffers
BytesProcessedPerSecond
BytesStreamedPerSecond
ExternalProviderConnection
PendingIvrMPConnections
TotalFilesTranscoded
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Media Servers > Nortel AMS > Device
Drills Down To
None.
Drilled Down From
Stream Quality
Stream Quality
Description
The Stream Quality report contains system performance information (total files transcoded, allocated audio
buffers, and so on) for each Nortel Announcement Media Server (AMS) device operating in the Nortel Carrier
VoIP environment. This report drills down to the Stream Quality - DC report.
Reporter Set
AMS
Tables and Charts
Navigation Path
Drills Down To
Stream Quality - DC
Drilled Down From
None.
Description
The System Performance - DC report aggregates system performance information (context switches per second,
exception dispatches per second, and so on) for each Nortel Announcement Media Server (AMS) device
operating in the Nortel Carrier VoIP environment. You can drill down to this report from the System
Performance report.
Reporter Set
AMS
Tables and Charts
Ratio Chart
Connection Failures
Connections Active
Context Switches/sec
Exception Dispatches/sec
File Control Bytes/sec
File Control Operations/sec
Processes
Threads
Navigation Path
Drills Down To
None.
Drilled Down From
System Performance
System Performance
Description
The System Performance report aggregates system performance information (context switches per second,
exception dispatches per second, and so on) for each Nortel Announcement Media Server (AMS) device
operating in the Nortel Carrier VoIP environment. This report drills down to the System Performance - DC
report.
Reporter Set
AMS
Tables and Charts
File Data Operations/sec
hrSystemUptime
System Calls/sec
Navigation Path
Drills Down To
Drilled Down From
None.
Description
The Termination Cause Analysis - DC report aggregates call information (total calls, incoming calls, and so on)
for all termination causes. You can drill down to this report from the Termination Cause Analysis report.
Reporter Set
Termination Cause
Tables and Charts
Ratio Chart
IncomingCall
InternalCall
OffNetCall
OnNetCall
OutgoingCall
TotalCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Call Signaling > CDR/IPDR > Nortel CS2K >
Termination Cause
Drills Down To
None.
Drilled Down From
Description
The Termination Cause Analysis report aggregates call information (total calls, incoming calls, and so on) for all
termination causes. This report drills down to the Termination Cause Analysis - DC report.
Reporter Set
Termination Cause
Tables and Charts
Charts: Ratio Chart
IncomingCall
InternalCall
OutgoingCall
TotalCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Call Signaling > CDR/IPDR > Nortel CS2K >
Termination Cause
Drills Down To
Drilled Down From
None.
Description
The Termination Cause QoS - DC report aggregates QoS information (average loss rate, round trip average, and
so on) for termination causes. You can drill down to this report from the Termination Cause QoS report.
Reporter Set
Termination Cause
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
Termination Cause
Drills Down To
None.
Drilled Down From
Description
The Termination Cause QoS report aggregates QoS information (average loss rate, round trip average, and so
on) for termination causes. This report drills down to the Termination Cause QoS - DC report.
Reporter Set
Termination Cause
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
Termination Cause
Drills Down To
Drilled Down From
None.
Description
The TypeOfCall Call Setup and Termination - DC report aggregates call setup quality information (total calls,
successful calls, and so on) for all types of calls (incoming, outgoing, and so on) that occur in the Nortel Carrier
VoIP environment. You can drill down to this report from the TypeOfCall Call Setup and Termination report.
Reporter Set
Call Setup Quality
Tables and Charts
Ratio Chart
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Call Signaling > CDR/IPDR > Nortel CS2K > Call Setup
Quality
Drills Down To
None.
Drilled Down From
Description
The TypeOfCall Call Setup and Termination report aggregates call setup quality information (total calls,
successful calls, and so on) for all types of calls (incoming, outgoing, and so on) that occur in the Nortel Carrier
VoIP environment. This report drills down to the TypeOfCall Call Setup and Termination - DC report.
Reporter Set
Call Setup Quality
Tables and Charts
Charts: Ratio Chart
CallDuration
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Call Signaling > CDR/IPDR > Nortel CS2K > Call Setup
Quality
Drills Down To
Drilled Down From
None.
TypeOfCall QoS - DC
Description
The TypeOfCall QoS - DC report aggregates QoS information (average loss rate, round trip average, and so on)
for call types. You can drill down to this report from the TypeOfCall QoS report.
Reporter Set
Call Setup Quality
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Type
Of Call
Drills Down To
None.
Drilled Down From
TypeOfCall QoS
TypeOfCall QoS
Description
The TypeOfCall QoS report aggregates QoS information (average loss rate, round trip average, and so on) for
call types. This report drills down to the TypeOfCall QoS - DC report.
Reporter Set
Call Setup Quality
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Type
Of Call
Drills Down To
TypeOfCall QoS - DC
Drilled Down From
None.
Description
The USP Device Quality - DC report aggregates device quality information for each USP device component
operating in the Nortel Carrier VoIP environment. You can drill down to this report from the USP Device Quality
report.
Reporter Set
Device
Tables and Charts
Ratio Chart
TotalConnectionOrientedIPDistributionViolations
TotalConnectionOrientedMessagesRoutingFailure
TotalGTTAlternateRoutingOnCongestion
TotalGTTHopCounterViolation
TotalGTTNoTranslationForAddress
TotalGTTTranslationTypeNotFound
TotalMessagesErrors
TotalMessagesIncompatibility
TotalMessagesTooLargeForSegmentation
TotalMSUDiscardedSCCPMessages
TotalOutOfSequenceSCCPMessages
TotalReassemblyBufferUnavailable
TotalReassemblyFailed
TotalReassemblyTimerExpired
TotalSCCPRoutingFailure
TotalSegmentationFailed
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Device
Drills Down To
None.
Drilled Down From
USP Device Quality
USP Device Quality
Description
The USP Device Quality report aggregates device quality information for each USP device component operating
in the Nortel Carrier VoIP environment. This report drills down to the USP Device Quality - DC report.
Reporter Set
Device
Tables and Charts
TotalConnectionOrientedMessagesHandled
TotalGTTPerformed
TotalMessagesErrors
TotalMessagesHandled
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Device
Drills Down To
Drilled Down From
None.
Description
The USP Link Quality - DC report aggregates carrier link quality information (link utilization, link failures, line
code violations, and so on) for each carrier link component controlled by the USP devices operating in the Nortel
Carrier VoIP environment. You can drill down to this report from the USP Link Quality report.
Reporter Set
Link
Tables and Charts
Ratio Chart
LineCodeViolations
LineErroredSeconds
LineLossOfSignalSeconds
LineSeverelyErroredSeconds
LinkMSUreceived
LinkMSUtransmitted
LinkUnavailableDuration
LinkUtilization
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Link
Drills Down To
None.
Drilled Down From
USP Link Quality
USP Link Quality
Description
The USP Link Quality report aggregates carrier link quality information (link utilization, link failures, line code
violations, and so on) for each carrier link component controlled by the USP devices operating in the Nortel
Carrier VoIP environment. This report drills down to the USP Link Quality - DC report.
Reporter Set
Link
Tables and Charts
LineCodeViolations
LineErroredSeconds
LinkFailureAllReasons
LinkUtilization
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Link
Drills Down To
Drilled Down From
None.
Description
The USP Linkset Quality - DC report aggregates linkset quality information (linkset inactivity duration, RST
received/transmitted, transfer control transmitted, and so on) for each linkset component controlled by the USP
devices operating in the Nortel Carrier VoIP environment. You can drill down to this report from the USP
Linkset Quality report.
Reporter Set
Linkset
Tables and Charts
Ratio Chart
RSTReceived
RSTTransmitted
TransferAllowedRoutingAvailableReceived
TransferAllowedRoutingAvailableTransmitted
TransferProhibitedRoutingNotAvailableReceived
TransferProhibitedRoutingNotAvailableTransmitted
TransferRestrictedReceived
TransferRestrictedTransmitted
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Linkset
Drills Down To
None.
Drilled Down From
USP Linkset Quality
USP Linkset Quality
Description
The USP Linkset Quality report aggregates carrier link quality information (link utilization, link failures, line code
violations, and so on) for each carrier link component controlled by the USP devices operating in the Nortel
Carrier VoIP environment. This report drills down to USP Linkset Quality - DC report.
Reporter Set
Linkset
Tables and Charts
LinksetInactivityDuration
RSTReceived
RSTTransmitted
TransferControlledTransmitted
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Linkset
Drills Down To
Drilled Down From
None.
Description
The USP Routeset Metrics - DC report aggregates routeset quality information (total routeset manual busy, total
routeset congested, and so on) for each routeset component controlled by the USP devices operating in the
Nortel Carrier VoIP environment. You can drill down to this report from the USP Routeset Metrics report.
Reporter Set
Routeset
Tables and Charts
Ratio Chart
TotalRoutesetCongested
TotalRoutesetManualBusy
TotalRoutesetUnavailabilityDuration
TotalRoutesetUnavailability
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Routeset
Drills Down To
None.
Drilled Down From
Description
The USP Routeset Metrics report aggregates routeset quality information (total routeset manual busy, total
routeset congested, and so on) for each routeset component controlled by the USP devices operating in the
Nortel Carrier VoIP environment. This report drills down to the USP Routeset Metrics - DC report.
Reporter Set
Routeset
Tables and Charts
Navigation Path
NOC Reporting > Carrier VOIP > Infrastructure > Signaling Gateways > Nortel USP > Routeset
Drills Down To
Drilled Down From
None.
Voice Quality - DC
Description
The Voice Quality - DC report displays voice quality data for Nortel CS2000 devices operating in the Nortel
Carrier VoIP environment. You can drill down to this report from the Voice Quality report.
Reporter Set
Voice Quality
Tables and Charts
Ratio Chart
InboundPacket
LostPacket
OutboundPacket
PacketLatency
Navigation Path
Softswitch Quality
Drills Down To
None.
Drilled Down From
Voice Quality
Description
The Voice Quality Report - DC displays data about Nortel CS2000 Carrier VOIP voice quality, including average
loss, echo return, end system delays, jitter averages, listening quality and round trip averages. You can drill down
to this report from the Voice Quality Report.
Reporter Set
Location
Tables and Charts
Ratio Chart
AverageLossRate
EchoReturnLoss
EndSystemDelay
JitterAverage
ListeningQualityMOS
RoundTripAverage
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Voice Quality Report displays data about Nortel CS2000 Carrier VOIP voice quality, including average loss,
echo return, end system delays, jitter averages, listening quality and round trip averages. This report drills down
to the Voice Quality Report - DC.
Reporter Set
Location
Tables and Charts
Charts: Ratio Chart
AverageLossRate
EchoReturnLoss
EndSystemDelay
JitterAverage
ListeningQualityMOS
RoundTripAverage
Navigation Path
Drills Down To
Drilled Down From
None.
Voice Quality
Description
The Voice Quality report displays voice quality data for Nortel CS2000 devices operating in the Nortel Carrier
VoIP environment. This report drills down to the Voice Quality - DC report.
Reporter Set
Voice Quality
Tables and Charts
Charts: Ratio Chart
InboundByte
InboundPacket
LostPacket
OutboundByte
OutboundPacket
PacketLatency
Navigation Path
Softswitch Quality
Drills Down To
Voice Quality - DC
Drilled Down From
None.
VOIP Dashboard
Description
The VoIP Dashboard report displays data on the dashboard, including ratio, group time series, and resource
distribution for CPU Utilization, offnet calls, minutes of use, and card/call processing. This report drills down to
the MGW Call Utilization - DC report and to the PVG VSP Call Signaling - DC report.
Reporter Set
Nortel CS2K
Tables and Charts
Tables: TopN Table
Charts: Ratio Chart
Group Time Series Chart
Resource Distribution Chart
OffNetCall
OnNetCall
SuccessfulCall
TotalCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP
Drills Down To
Drilled Down From
None.
Description
The XA-Core System Health - DC report provides system health information for XA-Core devices. This includes
information on CPU, memory and I/O utilization. You can drill down to this report from the XA-Core System
Health report.
Reporter Set
CS2K
Tables and Charts
Ratio Chart
HIOP
ProcessorElement
Navigation Path
Drills Down To
None.
Drilled Down From
Description
The Nortel XA-Core System Health report provides health information for a Nortel Extended Core (XA-Core)
system. This information includes memory utilization, I/O utilization and CPU utilization. This report drills
down to the Nortel XA-Core System Health - DC report.
Reporter Set
CS2K
Tables and Charts
HIOP
ProcessorElement
Navigation Path
Drills Down To
Drilled Down From
None.
Zone QoS - DC
Description
The Zone QoS - DC report aggregates QoS information (average loss rate, round trip average, and so on) by zone
for all Nortel CS2000 devices operating in the Nortel CS2000 environment. You can drill down to this report
from the Zone QoS report.
Reporter Set
Zone
Tables and Charts
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Zone
Drills Down To
None.
Drilled Down From
Zone QoS
Zone QoS
Description
The Zone QoS report aggregates QoS information (average loss rate, round trip average, and so on) by zone for
all Nortel CS2000 devices operating in the Nortel CS2000 environment. This report drills down to the Zone QoS
- DC report.
Reporter Set
Zone
Tables and Charts
Charts: Ratio Chart
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K > By Zone
Drills Down To
Zone QoS - DC
Drilled Down From
None.
Description
The Zone Utilization - DC report aggregates call utilization information (number of calls, minutes of use, and so
on) by zone for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. You can drill down
to this report from the Zone Utilization report.
Reporter Set
Zone
Tables and Charts
Ratio Chart
CallDuration
DropCall
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Zone
Drills Down To
None.
Drilled Down From
Zone Utilization
Zone Utilization
Description
The Zone Utilization report aggregates call utilization information (number of calls, minutes of use, and so on)
by zone for all Nortel CS2000 devices operating in the Nortel Carrier VoIP environment. This report drills down
to the Zone Utilization - DC report.
Reporter Set
Zone
Tables and Charts
Charts: Ratio Chart
CallDuration
InternationalCall
MobileCall
NationalCall
ShortCall
SuccessfulCall
TotalCall
UnsuccessfulCall
Navigation Path
NOC Reporting > Carrier VOIP > User Experience > Service Usage > CDR/IPDR > By Zone
Drills Down To
Drilled Down From
None.
Nortel CS2000 2.4.1.0 Technology Pack Users Guide, Version 4.3-X 141
Chapter 3: Devices and Services
Overview
Nortel Communication Server 2000 (CS2K) is a full-featured softswitch designed for new packet network
deployments. It enables carriers and service providers to deliver a full suite of traditional voice services to global
business, residential, and transit markets for their strategic Voice over IP applications.
This chapter provides brief introductions to the devices and services that the Nortel CS2000 manages. This
chapter focuses on the support that the Nortel CS2000 Technology Pack provides to enable users to display the
reports discussed in Chapter 2, Supported Reports on page 5.
Note: It is impractical and beyond the scope of this Technology Pack Users Guide to provide exhaustive
descriptions and explanations of the Nortel CS2000 technology. See the documentation that ships with the
previously listed devices and associated services for detailed information on the devices and services capabilities
and features.
Figure 2 shows some of the major components operating in a typical Nortel CS2000 environment.
Topic Page
Overview 141
Devices 142
Services and Applications 147
Figure 2: Typical Nortel CS2000 Environment
Devices
The Nortel CS2000 Technology Pack supports the following Nortel devices:
Nortel CS2000 on page 142
Nortel CS2000 CDRs on page 143
Nortel GWC on page 143
Nortel IEMS on page 144
* Nortel AMS on page 144, including the subcomponent Nortel RAS Port
* Nortel CICM on page 145
* Nortel MS 2010 on page 145
* Nortel SAM21 on page 145
* Nortel SPC on page 145 (formerly known as Nortel NGSS)
Nortel PVG on page 145
Nortel SSL on page 146
Nortel SST on page 146
Nortel USP on page 146
Nortel CS2000
The Nortel CS2000 is a Voice-over-Packet softswitch that enables service providers to economically serve global
business, residential, and transit markets with new network solutions that deliver a comprehensive set of revenue-
generating services. Nortel CS2000 performs call agent (call-processing engine) and gateway controller functions.
Nortel CS2000 holds the call processing rules, but uses the media gateways and the signaling gateway to perform
the actual call operations. The Nortel CS2000 is a distributed system consisting of a number of different
functional elements. Communication between the elements of the Nortel CS2000 takes place over a LAN or over
a message switch.
The following list briefly describes the main subcomponents of a standard Nortel CS2000:
Extended Architecture Core (XA-Core) This subcomponent is the standard shared-memory, parallel-
processing computing platform for Nortel CS2000 call processing and service logic.
Message Switch (MS) This subcomponent delivers messages between the XA-Core and the Fiberized
Link Peripheral Processor, input/output module equipment, and Integrated Element Management System.
Integrated Services Module (ISM) This subcomponent provides conference circuits, enhanced digital
announcements, and line test, trunk test, and office alarm unit interfaces.
Input/Output Module (IOM) This subcomponent provides communication interfaces, storage media,
and data interfaces such as simplified message desk interface links to voice messaging systems.
Enhanced Network (ENET) This subcomponent provides a TDM switching fabric for access to TDM
line, trunk, and service circuit peripherals.
Service Application Module 21 (SAM21) This component is also referred to as the Nortel SAM21 Shelf
Controller. See Nortel SAM21 on page 145 for more information.
Gateway Controller (GWC) This subcomponent acts as a call processing protocol converter between the
Nortel CS2000 series messages and the open-standard H.248 (Megaco) or MGCP used by the Nortel
Universal Audio Server (UAS) and Media Gateways. The GWC also can be configured to support H.323
messaging for communication to IP-PBXs/key systems and Data Packet Trunk functionality for interoffice
packet trunks.
The Nortel CS2000 Technology Pack supports the Nortel CS2000 by:
Defining data generation, data storage, and data collection methods See Chapter 4, Data Collection Model
for more information.
Defining Netcool/Proviso Properties See Chapter 5, Element and Sub-Element Properties for more
information.
Defining Netcool/Proviso Resources See Chapter 6, Defined Resources for more information.
Nortel CS2000 CDRs
The Nortel SuperNode Data Manager (SDM) provides accounting data through Call Detail Records (CDRs)
using the Automatic Message Accounting (AMA) record format and the XML IPDR (IP Data Record) format,
to produce User Experience reports and Quality of Service (QoS) reports.
The Nortel CS2000 Technology Pack supports Nortel CS2000 CDRs by:
information.
Nortel GWC
The Nortel GWC data is delivered to the Nortel CS2000 Technology Pack in the core operational metrics data.
Nortel IEMS
The Nortel Integrated Element Management System (IEMS) is a software solution that delivers OSS (operational
support system) interface aggregation, hardware platform consolidation, a centralized browser and launch-point,
and enhanced security. The Nortel IEMS:
Reduces the time and cost required for system integration by providing a common set of standardized
interfaces to northbound network management/OSSs.
Reduces operations cost and complexity by standardizing on one platform type and one operating system
that share common spares and software management processes, as well as enabling element manager system
(EMS) co-existence.
Provides a common look and feel across multiple EMSs while centralizing key management functions that
simplify and streamline operations.
Simplifies Authentication, Authorization, Administration and Logging. Password encryption hardens
security to meet demanding requirements.
The Nortel CS2000 Technology Pack supports the Nortel IEMS as an element and the following components as
sub-elements:
* Nortel AMS on page 144, including the subcomponent Nortel RAS Port
* Nortel CICM on page 145
* Nortel MS 2010 on page 145
* Nortel SAM21 on page 145
* Nortel SPC on page 145
The Nortel CS2000 Technology Pack supports the Nortel IEMS and its associated components by providing a
by providing a Bulk Adaptor Design File that instructs the Universal Bulk Adaptor (UBA) application on how to
parse the Bulk input files that contain the Nortel IEMS performance data.
The Nortel CS2000 Technology Pack supports the Nortel IEMS and its associated components by:
information.
Nortel AMS
The Nortel Announcement Media Server (AMS) provides announcement services. The following list identifies
the main subcomponents of a Nortel AMS:
Nortel AMS Processor
Nortel RAS Port
Nortel RAS Total
Nortel AMS
Nortel AMS Redirector
Nortel AMS Stream Source
Nortel AMS TCP
The Nortel CS2000 Technology Pack supports the Nortel AMS and its associated component Nortel RAS Port
-as sub-elements of the Nortel IEMS. See Nortel IEMS on page 144 for more information.
Nortel CICM
The Nortel Centrex IP Client Manager (CICM) is a high-availability, NEBS-compliant platform that is hosted
from one of the following:
DMS-100/500
Nortel CS2000
Communication Server 2000-Compact softswitch.
The Nortel CICM is responsible for hosting IP telephones or PC Clients and serves as a VoIP gateway when used
with the DMS-100/500 switch, enabling delivery of Centrex IPs rich feature set.
The Nortel CS2000 Technology Pack supports the Nortel CICM as a sub-element of the Nortel IEMS. See Nortel
IEMS on page 144 for more information.
Nortel MS 2010
The Nortel Media Server 2010 (MS 2010) provides announcement, conferencing, intercept, and trunk-testing
capabilities in a Nortel CS2000. The Nortel MS 2010 is a 240-port, 1-rack-unit device for IP (Internet Protocol)
networks. The Nortel MS 2010 is controlled by the Nortel CS2000 through the standard H.248 protocol.
The Nortel CS2000 Technology Pack supports the Nortel MS 2010 as a sub-element of the Nortel IEMS. See
Nortel IEMS on page 144 for more information.
Nortel SAM21
The Nortel SAM21 Shelf Controller (also referred to as the Service Application Module 21 (SAM21)) provides
the hardware that hosts and supports Gateway Controller (GWC) circuit cards and associated software. This
hardware includes multiple pairs of redundant processor elements that handle call processing for 6,400 lines per
processor pair, scalable to a capacity of 150,000 lines and 48,000 trunks per frame.
The Nortel CS2000 Technology Pack supports the Nortel SAM21 as a sub-element of the Nortel IEMS. See
Nortel IEMS on page 144 for more information.
Nortel SPC
The Nortel CS2000 Technology Pack supports the Nortel Session Policy Controller (SPC) as a sub-element of
the Nortel IEMS. Nortel SPC was formerly called Nortel Next Generation Session Server (NGSS). See Nortel
IEMS on page 144 for more information.
Nortel PVG
The Nortel Passport Packet Voice Gateway (PVG) consists of a gateway software load running on a Passport
hardware platform to support packet trunking on IP (Internet Protocol). The hardware platform to provide PVG
capabilities is the Passport 15000 Multiservice Switch. The PVGs act as Media Gateways (also called Public
Switched Telephone Network (PSTN) Gateways or Trunk Gateways) between the IP packet network and the
TDM switches and PBXs (PRI) in service provider networks. The PVGs terminate TDM-based DS0s on E1/T1,
DS3, OC-3, and convey the media on these DS0s in real time protocol (RTP) packets over an IP interface. The
PVGs also carry out a similar conversion in the other direction. The interfaces to the packet network can be OC-
3 to OC-48 or Gigabit Ethernet. The Passport is a high-density gateway with 40,000+ ports DS0 channels.
Passport Packet Voice Gateway utilizes ATM and IP protocols to enable wireline and wireless service providers
to migrate TDM voice trunking to a packet-based infrastructure.
The Nortel CS2000 Technology Pack supports the PVG by:
information.
Nortel SSL
The Nortel CS2000 Technology Pack supports the Nortel Session Server Lines (SSL) as a sub-element of the
Nortel IEMS. See Nortel IEMS on page 144 for more information.
Nortel SST
The Nortel Session Server Trunk (SST) is part of the new Nortel Session Server that replaces Nortel SPC
(formerly known as Nortel NGSS). Nortel SST is the PSTN-facing side of Nortel Session Server.
The Nortel CS2000 Technology Pack supports the Nortel SST by:
information.
Nortel USP
The Universal Signaling Point (USP) is the Signaling Gateway component in the complete Nortel Softswitch
architecture. A Signaling Gateway is a component that connects to the Signaling System 7 (SS7) network. SS7 is
an Out-of-Band signaling network using a messaging protocol based on a set of international standards for high-
speed digital communications. The SS7 protocol serves as the foundation for telephony infrastructures
worldwide. With SS7, the signaling control element is no longer part of the voice circuit. Instead, SS7 uses an out-
of-band signaling channel, separating the voice circuit from the routing channel. SS7 permits message routing and
maintenance of the network to be performed independently of the actual transmission of voice or data. As such,
SS7 facilitates rapid service creation and deployment of services (such as 1-800, Calling Name Delivery, Calling
Card) across the network. The USP has either IP or ATM SS7 interfaces available, and serves as the gateway for
SS7 signaling from the TDM-to-packet networks. The USP provides CCS7 signaling terminations that enable a
Nortel CS2000 to exchange ISUP and TCAP signaling with a conventional TDM-side CCS7 signaling network.
The Nortel CS2000 Technology Pack supports the USP by:
information.
Services and Applications
The Nortel CS2000 Technology Pack supports the following Nortel services and applications, although these are
not visible within the technology pack:
Nortel MDM on page 147
Nortel MDP on page 147
Nortel PMSP on page 148
Nortel QCA on page 148
Nortel STP on page 148
Nortel UAS and Nortel SDM on page 148
Nortel MDM
The Nortel Multiservice Data Manager (MDM) manages Passport 6000, 7000, 15000, and 20000 Multiservice
Platforms. MDM integrates, monitors, and controls Passport network elements, allowing operators to proactively
manage their network. MDM applications can be part of an overall management environment or operate as a
standalone system. The MDM forwards NTM (network traffic management) statistics to the Passport Packet
Voice Gateway (PVG) device. The Nortel CS2000 Technology Pack supports the MDM by providing a Bulk
Adaptor Design File that instructs the Universal Bulk Adaptor (UBA) application on how to parse the Bulk input
files that contain the PVG performance data.
The Nortel CS2000 Technology Pack supports the MDM by:
information.
Nortel MDP
The Nortel Management Data Provider (MDP) is a Bulk data collection and processing system for Nortel
network accounting and statistical information. MDP collects metric data from the switches using bulk FTP
transfers to minimize the performance degradation that typically results from constant metric polling. The data
is then correlated to provide historical accounting and statistical records. The records can be customized in
content and format to ensure usability by external systems for billing, and customer network management (CNM)
planning and analysis.
Nortel PMSP
On the MDM servers, the Nortel Performance Measurement Stream Processor (PMSP) server application
handles network traffic management (NTM) statistics originating from node processors. It is the PMSP server
application that converts these NTM statistics into CSV (Comma-Separated Values) files.
Nortel QCA
The Nortel QoS Collector Application (QCA) is an add-on application in charge of Voice Quality metrics data
collection.
Nortel STP
The Nortel Signal Transfer Point (STP) is the heart of the SS7 network, providing for the efficient transport of
SS7 messages that control signaling and access database services in an SS7 network. The STP does not originate
or terminate SS7 message packets (except those related to network management), but acts as a router for messages
to other signal points within the network. Additionally, an STP provides management functions designed to
prevent, detect, supervise, and recover from failures in the network. To ensure network integrity, STPs are
deployed in mated pairs, usually located at separate sites. If a problem develops with one STP, its mate provides
an uninterrupted transfer of messages to all concerned nodes in the network.
Nortel UAS and Nortel SDM
The Nortel Universal Audio Server (UAS) delivers leading edge announcement and conferencing capabilities into
converged networks. Deployed with the Nortel CS2000, the UAS delivers a rich set of advanced audio services.
The UAS's Digital Signal Processing technology supports speech recognition, speaker verification, and text-to-
speech synthesis, as well as conference bridges for up to 61 ports and FAX transmit and receive. Built on a
commercially available NEBS 3 compact PCI platform running a Microsoft Windows NT 4.0 server operating
system, the UAS provides advanced audio capabilities directly on the IP or ATM packet network.
The Nortel SuperNode Data Manager (SDM) serves as an element manager for the Nortel CS2000, and as a
foundation element for Nortel Multiservice Data Manager, retaining its suite of OAM&P applications and
existing OSS connectivity.
The UAS sends performance data to the SDM using CSV (Comma-Separated Values) file format.
The Nortel CS2000 Technology Pack supports the UAS and SDM by:
information.
Chapter 4: Data Collection Model
Overview
The Nortel CS2000 Technology Pack collects performance and accounting data using Bulk data importation.
This chapter provides an understanding of this data collection model.
Nortel CS2000 Devices That Generate Data
The Nortel CS2000 Technology Pack collects performance and accounting data from devices that operate in the
Nortel CS2000 environment. Specifically, the Nortel CS2000 Technology Pack collects:
Nortel CS2000 Performance Data
Nortel CS2000 CDRs
Nortel IEMS Performance Data
Nortel PVG Performance Data
Nortel SSL Performance Data
Nortel SST Performance Data
Nortel USP Performance Data
The following sections discuss each of these data-related topics.
Nortel CS2000 Performance Data
The Nortel SuperNode Data Manager (SDM) provides performance data from the Nortel Universal Audio Server
(UAS) and Media Gateway Controller (MGC) using CSV (Comma-Separated Values) file format. Each deployed
Nortel CS2000 softswitch usually has one SDM.
Topic Page
Overview 149
Nortel CS2000 Devices That Generate Data 149
Bulk Adaptor Design Files 151
Configuration and Technology Pack-Specific Files 153
SDM is the data source for all Nortel Communication Server 2000 (CS2K) performance data and Nortel GWC
performance data. Nortel Media Server 20xx (MS 20xx) performance data can also be found in the core
operational metrics data from the SDM.
Note: Two different sets of inventory are created for Nortel Media Server 20xx (MS 20xx): one set from the
SDM, and one set from the IEMS.
The Nortel CS2000 Technology Pack provides a Bulk Adaptor Design File that instructs the Universal Bulk
Adaptor (UBA) application on how to parse the Bulk input files that contain the performance data for Nortel
CS2000, Nortel GWC, and Nortel Media Server 20xx (MS 20xx).
Nortel CS2000 CDRs
The Nortel SuperNode Data Manager (SDM) provides accounting data through Call Detail Records (CDRs)
using the Automatic Message Accounting (AMA) record format and the XML IPDR (IP Data Record) format.
The IPDR format is based on Extensible Markup Language (XML) schema definition. SDM is the data source
for all CDRs and IPDR data collection.
Note: In the CVM13 release of the Nortel CS2000 code, the extended QoS data is in the IPDR. This data
is supported through the regular CDR/IPDR processing by the cs2kcdr.pl pre-processor. If any of the
extended QoS fields are omitted from the IPDR XML, the corresponding metric fields in the QoS reports have
dashes instead of zeroes.
The Nortel CS2000 Technology Pack provides Bulk Adaptor Design Files that instruct the Universal Bulk
Adaptor (UBA) application on how to parse the Bulk input files that contain the Nortel CS2000 CDRs
performance data.
Nortel IEMS Performance Data
The Nortel IEMS generates performance data and stores it in Extensible Markup Language (XML) file format.
SDM, and one set from the IEMS.
Adaptor (UBA) application on how to parse the Bulk input files that contain the Nortel IEMS performance data.
Nortel PVG Performance Data
The Passport Packet Voice Gateway (PVG) device collects performance data as follows:
Data Collection System (DCS) The DCS on the node collects NTM (network traffic management)
statistics. Each PVG device forwards these statistics records to the Nortel Multiservice Data Manager
(MDM) servers.
MDM servers On the MDM servers, the Nortel Performance Measurement Stream Processor (PMSP)
server application manages performance. NTM statistics originating from node processors flow to the PMSP
server application. The PMSP server application converts the statistics into CSV (Comma-Separated Values)
files every five minutes. The PMSP server also performs the conversion every 30 minutes by aggregating six
5-minute data records.
The MDM passes the NTM data to the SDM running on the Core Manager (CMT/IEMS) according to the
network configuration.
The Nortel CS2000 Technology Pack provides two Bulk Adaptor Design Files that instruct the Universal Bulk
Adaptor (UBA) application on how to parse the Bulk input files that contain the PVG performance data: one
Bulk Adaptor Design File for PVG performance data that comes directly from the MDM, and a different Bulk
Adaptor Design File for PVG performance data that comes from the IEMS.
Nortel SSL Performance Data
The Nortel Session Server Lines (SSL) generates performance data and stores this data in Extensible Markup
Language (XML) file format. Nortel SSL performance data is delivered by the Nortel IEMS system, but is
processed by a special SSL adaptor, not by the IEMS adaptor.
Adaptor (UBA) application on how to parse the Bulk input files that contain the Nortel SSL performance data.
Nortel SST Performance Data
The Nortel Session Server Trunk (SST) generates performance data and stores this data in Common Performance
Reporting (CPR) format. Nortel SST performance data is delivered by the Nortel IEMS system, but is processed
by a special SST adaptor, not by the IEMS adaptor.
Adaptor (UBA) application on how to parse the Bulk input files that contain the Nortel SST performance data.
Nortel USP Performance Data
A USP Manager obtains performance data from the Universal Signaling Point (USP) device and stores it in CSV
(Comma-Separated Values) file format. The USP Manager is the data source for USP performance data. There is
one USP Manager for each USP device.
Adaptor (UBA) application on how to parse the Bulk input files that contain the USP performance data.
Bulk Adaptor Design Files
There are many formats associated with Bulk input files, for example CSV, XML, and binary. Typically, a
technology pack provides a Bulk Adaptor Design File (a JavaScript file) that defines the format or formats of the
Bulk input files for which it is responsible for processing. This Bulk Adaptor Design File processes both inventory
and statistics from the same Bulk input file. More specifically, this Bulk Adaptor Design File provides a function
that creates the Bulk collection formula names. Some technology packs might provide several Bulk Adaptor
Design Files each of which handles a specific Bulk input file format.
Table 1 lists the Bulk Adaptor Design Files (implemented as JavaScripts) that the Nortel CS2000 Technology Pack
provides. These Bulk Adaptor Design Files are maintained by IBM Professional Services:
Typically, Bulk Adaptor Design Files instruct the Universal Bulk Adaptor (UBA) application in the:
Creation of element names for the associated device
Creation of sub-element names for the associated device components
Creation of sub-element labels and sub-element family names
Implementation of Bulk collection formulas that use fields from the different Bulk input files
Table 1 lists each Bulk Adaptor Design File (by JavaScript name) and the associated Bulk input files name or
names.
Table 1: Nortel CS2000 Technology Pack Bulk Adaptor Design Files
Bulk Adaptor Design File Bulk Input File Description
CPRAdaptor.js *.csv Specifies a Bulk Adaptor Design File for the
Nortel Session Server Trunk (SST). Also
specifies a Bulk Adaptor Design File for the
Passport Packet Voice Gateway (PVG) data that
comes from the IEMS.
You must create one instance of this adaptor for
each input file stream.
CS2KCDRAdaptor.js *.xml Specifies a Bulk Adaptor Design File for the
Nortel CS2000 CDR.
This Bulk Adaptor Design File supports only
old installations of the Nortel CS2000
Technology Pack (in which Location
subelements exist), and processes only the old
format of the Nortel CS2000 Extended QoS
XML data.
CS2KCDRAdaptor.js has been replaced by
SimpleCS2KCDRAdaptor.js, which
reads data from the pre-processor.
CS2KPERFAdaptor.js *.csv Specifies the Bulk Adaptor Design File for the
Nortel CS2000. This Bulk Adaptor Design File
also handles Nortel GWC devices and Nortel
MS 20xx devices.
See Appendix A, Configuration for information
about how to specify the configuration settings.
IEMSPERFAdaptor.js *.xml Specifies the Bulk Adaptor Design File for the
Nortel Integrated Element Management System
(IEMS).
PVGAdaptor.js *.csv Specifies the Bulk Adaptor Design File for the
Passport Packet Voice Gateway (PVG) data that
comes directly from the MDM.
SimpleCS2KCDRAdaptor.js *.0.csv
*.STRAY.csv
Specifies the Bulk Adaptor Design File for the
Nortel CS2000 CDR. This Bulk Adaptor Design
File replaces CS2KCDRAdaptor.js.
SSLAdaptor.js *.csv Specifies a Bulk Adaptor Design File for the
Nortel Session Server Lines (SSL).
Configuration and Technology Pack-Specific Files
Table 2 lists the configuration and technology pack-specific files provided by the Nortel CS2000 Technology
Pack.
Table 2: Nortel CS2000 Technology Pack Configuration Files
USPPERFAdaptor.js *.txt Specifies the main Bulk Adaptor Design File for
the Universal Signaling Point (USP).
Bulk Adaptor Design File Bulk Input File Description
File Name Description
CS2KCDRTerminationCause.js Specifies the definitions files that maps termination cause code
numbers to their associated strings. These termination causes are
associated with the Nortel CS2000 CDR.
CS2KPERFConfig.js Specifies the configuration file for the Nortel CS2000.
IEMSPERFConfig.js Specifies the configuration file for the Nortel IEMS.
IEMSPERFMethods.js Specifies commonly used log-related message functions.
nortel_cs2000_sample_dc.cfg The template configuration file located in the
$DC_HOME/scripts (typically,
/opt/datachannel/scripts) directory. See
Appendix C, Template File Reference (Pre-443 Only) for more
information.
PVGConfig.js Specifies the configuration file for the PVG.
USPConfig.js Specifies the configuration file for the USP.
NOTES
Chapter 5: Element and Sub-Element
Properties
Overview
A Netcool/Proviso property is an attribute or characteristic of an element or sub-element. Typically, a
Netcool/Proviso Technology Pack uses an inventory process to collect information generated by the devices,
interfaces, and services operating in the technology environment it supports.
A technology pack uses Netcool/Proviso properties for some or all of the following purposes:
To organize information in reports
To display values in reports
To construct names such as sub-element names, sub-element instance names, and sub-element labels
The Nortel CS2000 Technology Pack attaches Netcool/Proviso properties to the sub-elements associated with
the devices and components that operate in the Nortel CS2000 environment. See Chapter 6, Defined Resources for
a discussion of the sub-element names defined for each of these devices and components.
The Netcool/Proviso properties associated with sub-elements appear in the Properties list (Sub-Element view)
of the Netcool/Proviso DataMart Resource Editor. See the Netcool/Proviso DataMart Configuration Guide for more
information on the Resource Editor.
Topic Page
Overview 155
Nortel CS2000 Device Sub-Element Properties 156
Nortel CS2000 CDRs Sub-Element Properties 157
Nortel CS2000 Extended QoS Sub-Element Properties 160
Nortel IEMS Device Sub-Element Properties 161
Nortel PVG Device Sub-Element Properties 163
Nortel SST Sub-Element Properties 165
Nortel USP Device Sub-Element Properties 166
Chapter 5: Element and Sub-Element Properties
Nortel CS2000 Device Sub-Element Properties
The Nortel CS2000 Technology Pack defines properties for the Nortel Communication Server 2000 (CS2K)
device sub-element and its associated component sub-elements. Specifically, the Nortel CS2000 Technology Pack
defines:
Nortel CS2000 Sub-Element Properties
CS2K Softswitch Trunk Sub-Element Properties
The following sections discuss the defined properties for these sub-elements.
Nortel CS2000 Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel CS2000
sub-element:
VOIPSoftswitchComponentType The VOIPSoftswitchComponentType property specifies the
component or device to which the sub-element maps. The Nortel CS2000 sub-element maps to a Nortel
CS2000 device. The value of VOIPSoftswitchComponentType is Class 5 Softswitch for a Nortel
CS2000 sub-element.
VOIPSoftswitchVendor The VOIPSoftswitchVendor property specifies the name of the vendor
responsible for manufacturing the component or device to which the sub-element maps. The value of
VOIPSoftswitchVendor is Nortel for a Nortel CS2000 sub-element.
VOIPSoftswitchLocation The VOIPSoftswitchLocation property specifies the location of the
component or device to which the sub-element maps. The Nortel CS2000 Technology Pack fills in the
property automatically during the Bulk collection process by reading the switchname field in the associated
CSV file.
CS2K Softswitch Trunk Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the CS2K Softswitch
Trunk sub-element:
component or device to which the sub-element maps. The CS2K Softswitch Trunk sub-element maps to
a Nortel Communication Server 2000 (CS2K) Softswitch Trunk, a component of the Nortel CS2000 device.
The value of VOIPSoftswitchComponentType is Class 5 Trunk for a CS2K Softswitch Trunk sub-
element.
VOIPSoftswitchVendor is Nortel for a CS2K Softswitch Trunk sub-element.
property automatically during the Bulk collection process by reading the switchname field in the associated
CSV file.
Nortel CS2000 CDRs Sub-Element Properties
The Nortel CS2000 Technology Pack defines properties for the Nortel CS2000 CDRs sub-element and its
associated component sub-elements. Specifically, the Nortel CS2000 Technology Pack defines:
Nortel CS2000 Device CDR Sub-Element Properties
Customer Profile Sub-Element Properties
Termination Cause Sub-Element Properties
TypeOfCall Sub-Element Properties
Media Gateway Trunk Sub-Element Properties
Subscriber Zone Sub-Element Properties
Path Sub-Element Properties
Extension Sub-Element Properties
Nortel CS2000 Device CDR Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel CS2000
device CDR sub-element:
component or device to which the sub-element maps. The Nortel CS2000 device CDR sub-element maps
to a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is
CDR_Softswitch_Device for a Nortel CS2000 device CDR sub-element.
VOIPSoftswitchVendor is Nortel for a Nortel CS2000 device CDR sub-element.
property automatically during the Bulk collection process by reading the sensor_id field in the associated
binary AMA file.
VOIPSoftswitchZone The VOIPSoftswitchZone property specifies the zone of the component or
device to which the sub-element maps. The Nortel CS2000 Technology Pack fills in the property
automatically during the Bulk collection process by reading the sensor_id field in the associated binary
AMA file or the subscriberId field in the IPDR file.
Customer Profile Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Customer Profile
sub-element:
component or device to which the sub-element maps. The Customer Profile sub-element maps to a
customer profile associated with a Nortel CS2000 device. The value of VOIPSoftswitchComponentType
is CDR_Softswitch_CustomerProfile for a Customer Profile sub-element.
VOIPSoftswitchVendor is Nortel for a Customer Profile sub-element.
binary AMA file.
Termination Cause Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Termination
Cause sub-element:
component or device to which the sub-element maps. The Termination Cause sub-element maps to a
termination cause associated with a Nortel CS2000 device. The value of
VOIPSoftswitchComponentType is CDR_TC for a Termination Cause sub-element.
The Nortel CS2000 Technology Pack manages each Q.931 Termination Cause as a specific sub-element. This
technology pack cannot manage each cause as a metric because there are more than 100 Termination Causes
defined in Q.931. The Nortel CS2000 Technology Pack attaches metrics to each Termination Cause sub-
element.
The Nortel CS2000 Technology Pack defines a Termination Code Hash table in cs2kcdr.pl.
VOIPSoftswitchVendor is Nortel for a Termination Cause sub-element.
binary AMA file.
TypeOfCall Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the TypeOfCall sub-
element:
component or device to which the sub-element maps. The TypeOfCall sub-element maps to a call type
associated with a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is
CDR_TypeOfCall for a Termination Cause sub-element.
VOIPSoftswitchVendor is Nortel for a TypeOfCall sub-element.
binary AMA file.
Media Gateway Trunk Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Media Gateway
Trunk sub-element:
component or device to which the sub-element maps. The Media Gateway Trunk sub-element maps to a
trunk associated with a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is
CDR_MGW for a Media Gateway Trunk sub-element.
VOIPSoftswitchVendor is Nortel for a Media Gateway Trunk sub-element.
binary AMA file.
Subscriber Zone Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Subscriber Zone
sub-element:
component or device to which the sub-element maps. The Subscriber Zone sub-element maps to a zone
associated with a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is CDR_Zone
for a Subscriber Zone sub-element.
VOIPSoftswitchVendor is Nortel for a Subscriber Zone sub-element.
binary AMA file.
Path Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Path sub-element:
component or device to which the sub-element maps. The Path sub-element maps to a path associated with
a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is CDR_Path for a Path sub-
element.
VOIPSoftswitchVendor is Nortel for a Path sub-element.
binary AMA file.
Extension Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Extension sub-
element:
component or device to which the sub-element maps. The Extension sub-element maps to an extension
associated with a Nortel CS2000 device. The value of VOIPSoftswitchComponentType is
CDR_Extension for an Extension sub-element.
VOIPSoftswitchVendor is Nortel for an Extension sub-element.
binary AMA file.
Nortel CS2000 Extended QoS Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the CDR location
sub-element associated with the Nortel CS2000 Extended QoS:
component or device to which the sub-element maps. The CDR location sub-element maps to a location
generated by the Nortel Centrex IP Client Manager (CICM). The value of
VOIPSoftswitchComponentType is CDR_Location for a CDR location sub-element.
VOIPSoftswitchVendor is Nortel for a CDR location sub-element.
property with a location string if the IP address from the Bulk input file matches one of the specified
addresses or ranges in the cs2kcdr.pl file.
Nortel IEMS Device Sub-Element Properties
The Nortel CS2000 Technology Pack defines properties for the Nortel IEMS device sub-element and its
associated component sub-elements. Specifically, the Nortel CS2000 Technology Pack defines:
Nortel AMS Sub-Element Properties
Nortel CICM Sub-Element Properties
Nortel GWC Sub-Element Properties
Nortel MS 20xx Device Sub-Element Properties
Nortel RAS Port Sub-Element Properties
Nortel SAM21 Shelf Controller Device Sub-Element Properties
Nortel SPC Sub-Element Properties
Nortel SSL Sub-Element Properties
Nortel AMS Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel AMS sub-
element:
component or device to which the sub-element maps. The Nortel AMS sub-element maps to a Nortel
Announcement Media Server (AMS). The value of VOIPSoftswitchComponentType is IEMS_AMS for
a Nortel AMS sub-element.
Nortel CICM Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel CICM
sub-element:
component or device to which the sub-element maps. The Nortel CICM sub-element maps to a Nortel
Centrex IP Client Manager (CICM). The value of VOIPSoftswitchComponentType is
IEMS_CICM_Mgr for a Nortel CICM sub-element.
Nortel GWC Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel Gateway
Controller (GWC) sub-element:
component or device to which the sub-element maps. The Nortel GWC sub-element maps to a Nortel
GWC device. The value of VOIPSoftswitchComponentType is Class 5 GWC for a Nortel GWC sub-
element.
Nortel MS 20xx Device Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel MS 20xx
device sub-element:
component or device to which the sub-element maps. The Nortel MS 20xx device sub-element maps to a
Nortel Media Server 20xx (MS 20xx) device. The value of VOIPSoftswitchComponentType is
IEMS_MS2000 for a Nortel MS 20xx device sub-element.
Nortel RAS Port Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel RAS Port
sub-element:
component or device to which the sub-element maps. The Nortel RAS Port sub-element maps to a Nortel
Remote Access Server (RAS) Port. The value of VOIPSoftswitchComponentType is
IEMS_AMS_RAS_Port for a Nortel RAS Port sub-element.
Nortel SAM21 Shelf Controller Device Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel SAM21
Shelf Controller device sub-element:
component or device to which the sub-element maps. The Nortel SAM21 Shelf Controller device sub-
element maps to a Nortel SAM21 Shelf Controller device. The value of
VOIPSoftswitchComponentType is IEMS_SAM21 for a Nortel SAM21 Shelf Controller device sub-
element.
Nortel SPC Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the Nortel Session
Policy Controller (SPC) sub-element:
component or device to which the sub-element maps. The Nortel SPC sub-element maps to a Nortel
Session Policy Controller. The value of VOIPSoftswitchComponentType is IEMS_Session% for a
Nortel SPC sub-element.
Nortel SSL Sub-Element Properties
Server Lines (SSL) sub-element:
component or device to which the sub-element maps. The Nortel SSL sub-element maps to a Nortel SSL
device. The value of VOIPSoftswitchComponentType is IEMS_SSL for a Nortel SSL sub-element.
Nortel PVG Device Sub-Element Properties
The Nortel CS2000 Technology Pack defines properties for the PVG device sub-element and its associated
component sub-elements. Specifically, the Nortel CS2000 Technology Pack defines:
PVG Device Sub-Element Properties
Media Gateway FC Sub-Element Properties
Media Gateway SC Sub-Element Properties
MGI Sub-Element Properties
Media Gateway VSP PC Sub-Element Properties
Media Gateway VSP CC Sub-Element Properties
PVG Device Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the PVG device sub-
element:
component or device to which the sub-element maps. The PVG sub-element maps to a Passport Packet
Voice Gateway (PVG) device. The value of VOIPSoftswitchComponentType is
Media_Gateway_Device for a PVG sub-element.
VOIPSoftswitchVendor is Nortel for a PVG sub-element.
property automatically during the Bulk collection process by reading the OFFICEID field in the associated
CSV file.
Media Gateway FC Sub-Element Properties
FC sub-element:
component or device to which the sub-element maps. The Media Gateway FC sub-element maps to a Media
Gateway Fabric Card (FC), a component of the PVG device. The value of
VOIPSoftswitchComponentType is Media_Gateway_FabricCard for a Media Gateway FC sub-
element.
VOIPSoftswitchVendor is Nortel for a Media Gateway FC sub-element.
CSV file.
Media Gateway SC Sub-Element Properties
SC sub-element:
component or device to which the sub-element maps. The Media Gateway SC sub-element maps to a Media
Gateway Shelf Card (SC), a component of the PVG device. The value of
VOIPSoftswitchComponentType is Media_Gateway_ShelfCard for a Media Gateway SC sub-
element.
VOIPSoftswitchVendor is Nortel for a Media Gateway SC sub-element.
CSV file.
MGI Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the MGI sub-
element:
component or device to which the sub-element maps. The MGI sub-element maps to a Media Gateway
Interface (MGI), a component of the PVG device. The value of VOIPSoftswitchComponentType is
Media_Gateway_Interface for a Media Gateway SC sub-element.
VOIPSoftswitchVendor is Nortel for a MGI sub-element.
CSV file.
VOIPSoftswitchLinkcap The VOIPSoftswitchLinkcap property specifies the
capability of the Media Gateway Interface. The Nortel CS2000 Technology Pack automatically sets
this property for each MGI sub-element, according to the value of the IPLINKCAP field (field number
103) in the input file. The IPLINKCAP field reports the maximum byte rate per second possible over the
Media Gateway Interface. This rate applies to both incoming and outgoing bandwidth limits.
Media Gateway VSP PC Sub-Element Properties
VSP PC sub-element:
component or device to which the sub-element maps. The Media Gateway VSP PC sub-element maps to a
Media Gateway VSP Processor Card (PC), a component of the PVG device. The value of
VOIPSoftswitchComponentType is Media_Gateway_VSP_ProcessorCard for a Media Gateway
VSP PC sub-element.
VOIPSoftswitchVendor is Nortel for a Media Gateway VSP PC sub-element.
CSV file.
Media Gateway VSP CC Sub-Element Properties
VSP CC sub-element:
component or device to which the sub-element maps. The Media Gateway VSP CC sub-element maps to
a Media Gateway VSP Call Card (CC), a component of the PVG device. The value of
VOIPSoftswitchComponentType is Media_Gateway_VSP_CallSignaling for a Media Gateway
VSP CC sub-element.
VOIPSoftswitchVendor is Nortel for a Media Gateway VSP CC sub-element.
CSV file.
Nortel SST Sub-Element Properties
Server Trunk (SST) sub-element:
component or device to which the sub-element maps. The Nortel SST sub-element maps to a Nortel
Session Server Trunk. The value of VOIPSoftswitchComponentType is SS-T for a Nortel SST sub-
element.
Nortel USP Device Sub-Element Properties
The Nortel CS2000 Technology Pack defines properties for the USP device sub-element and its associated
component sub-elements. Specifically, the Nortel CS2000 Technology Pack defines:
USP Device Sub-Element Properties
USP Linkset Sub-Element Properties
USP Routeset Sub-Element Properties
USP Carrier Link Sub-Element Properties
USP Device Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the USP device sub-
element:
component or device to which the sub-element maps. The USP device sub-element maps to a Universal
Signaling Point (USP) device. The value of VOIPSoftswitchComponentType is SGW for a USP device
sub-element.
VOIPSoftswitchVendor is Nortel for a USP device sub-element.
component or device to which the sub-element maps. The Nortel CS2000 Technology Pack cannot fill in
this property automatically during the Bulk collection process. Instead, this property must be set manually
using the following function in the UBANORTEL.xml configuration file:
setLocation(USP Hostname, my_location)
The value for USP Hostname should match with the corresponding Hostname value defined in the URI for
each managed USP. The value for My_location can be any string for the associated USP Hostname.
USP Linkset Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the USP Linkset sub-
element:
component or device to which the sub-element maps. The USP Linkset sub-element maps to a USP Linkset
component associated with a Universal Signaling Point (USP) device. The value of
VOIPSoftswitchComponentType is SGW Linkset for a USP Linkset sub-element.
VOIPSoftswitchVendor is Nortel for a USP Linkset sub-element.
USP Routeset Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the USP Routeset
sub-element:
component or device to which the sub-element maps. The USP Routeset sub-element maps to a USP
Routeset component associated with a Universal Signaling Point (USP) device. The value of
VOIPSoftswitchComponentType is SGW Routeset for a USP Routeset sub-element.
VOIPSoftswitchVendor is Nortel for a USP Linkset sub-element.
USP Carrier Link Sub-Element Properties
The Nortel CS2000 Technology Pack attaches the following Netcool/Proviso properties to the USP Carrier Link
sub-element:
component or device to which the sub-element maps. The USP Carrier Link sub-element maps to a USP
Carrier Link component associated with a Universal Signaling Point (USP) device. The value of
VOIPSoftswitchComponentType is SGW Trunk for a USP Carrier Link sub-element.
VOIPSoftswitchVendor is Nortel for a USP Carrier Link sub-element.
NOTES
Chapter 6: Defined Resources
Overview
A Netcool/Proviso resource is a network element or sub-element, such as a router or a hub. Typically, an IBM
Technology Pack defines a set of Netcool/Proviso elements, sub-elements, and properties that map to specific
devices and services operating in a network. These resources allow IBM support engineers to:
Configure (using the Netcool/Proviso DataMart Request Editor) data collection requests for the sub-
elements associated with each Technology Pack
View (using the Netcool/Proviso DataMart Resource Editor) sub-elements and sub-element groups
associated with each Technology Pack
Note: The following sections refer to element names, sub-element names, and sub-element family names without
using the word Netcool/Proviso. The following sections assume that these are Netcool/Proviso defined names.
Element Names Defined for Nortel CS2000 Devices
The element name identifies the element that resides in the database. The element name or names discussed in
this chapter display in the name column (Element view) of the Netcool/Proviso DataMart Resource Editor. The
Nortel CS2000 Technology Pack defines a group of Netcool/Proviso elements, sub-elements, and properties that
map to the devices and services that operate in the Nortel CS2000 environment. For information on how to use
the Netcool/Proviso DataMart Request Editor to configure data collection requests and the Netcool/Proviso
DataMart Resource Editor to view element names, see the Netcool/Proviso DataMart Configuration Guide.
The Nortel CS2000 Technology Pack defines element names for the devices operating in the Nortel CS2000
environment. Specifically, the Nortel CS2000 Technology Pack defines:
Nortel CS2000 Device Element Name
Nortel CS2000 CDRs Element Name
Topic Page
Overview 169
Element Names Defined for Nortel CS2000 Devices 169
Sub-Element Names Defined for Nortel CS2000 Devices 172
Nortel CS2000 Devices Sub-Element Labels 189
Nortel CS2000 Devices Sub-Element Family Names 189
Nortel IEMS Device Element Name
Nortel PVG Device Element Name
Nortel SST Device Element Name
Nortel USP Device Element Name
The following sections discuss the element names defined for each of these devices.
Nortel CS2000 Device Element Name
The Nortel CS2000 Technology Pack defines an element name for each Nortel Communication Server 2000
(CS2K) device operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack manages the
creation of element names for the Nortel CS2000 devices through a Bulk Adaptor Design File that is maintained
by IBM Professional Services. It is necessary to specify Nortel CS2000 Performance Bulk Adaptor Design File
configuration settings in the dc.cfg configuration file. See Appendix C, Template File Reference (Pre-443 Only) for
information on the Nortel CS2000 Performance Bulk Adaptor Design File settings you must specify in the
dc.cfg configuration file.
The Nortel CS2000 Technology Pack defines the element name for a Nortel CS2000 device by using the following
syntax:
switchname
where:
switchname Specifies a switch name field that resides in the CSV (Comma-Separated Values) files
associated with a Nortel CS2000 device operating in the Nortel CS2000 environment.
The following examples use the switchname field to define the element name for a PVG device:
LowellCS2K
BOSTON
Nortel CS2000 CDRs Element Name
The Nortel CS2000 Technology Pack defines an element name for each Nortel Communication Server 2000
(CS2K) Call Detail Records (CDRs) operating in the Nortel CS2000 environment. The Nortel CS2000
Technology Pack manages the creation of element names for the Nortel CS2000 CDR devices through a Bulk
Adaptor Design File that is maintained by IBM Professional Services. It is necessary to specify Nortel CS2000
CDR Bulk Adaptor Design File configuration settings in the dc.cfg configuration file. See Appendix C,
Template File Reference (Pre-443 Only) for information on the Nortel CS2000 CDR Bulk Adaptor Design File settings
you must specify in the dc.cfg configuration file.
The Nortel CS2000 Technology Pack defines this element name by using the sensor_id field in the input file
associated with the Nortel CS2000 CDRs. Because this field is an encoded hexadecimal value, the Nortel CS2000
Technology Pack provides a user configuration section in the cs2kcdr.pl file that IBM Professional Services
uses to associate each sensor ID value to the Nortel CS2000 devices name and location.
Based on the values specified in the cs2kcdr.pl file previous example, the element names display as follows:
LOWELL_1_SENSOR
LOWELL_2_SENSOR
MTV_18_SENSOR
MTV_19_SENSOR
MTV_20_SENSOR
MTV_17_SENSOR
Nortel IEMS Device Element Name
The Nortel CS2000 Technology Pack defines an element name for each Nortel Integrated Element Management
System (IEMS) device operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack
manages the creation of element names for the Nortel IEMS devices through a Bulk Adaptor Design File that is
maintained by IBM Professional Services. It is necessary to specify Nortel IEMS Bulk Adaptor Design File
configuration settings in the dc.cfg configuration file. See Appendix C, Template File Reference (Pre-443 Only) for
information on the Nortel IEMS Bulk Adaptor Design File settings you must specify in the dc.cfg
configuration file.
The Nortel CS2000 Technology Pack defines this element name based on the EntityId property configured in
the input file associated with a specific Nortel IEMS. Typically, this EntityId field stores an IP address
associated with the Nortel IEMS device.
The following examples use the EntityId field to define element names for Nortel IEMS devices:
47.104.11.120
172.17.40.230
172.17.40.232
49.204.91.120
Nortel PVG Device Element Name
The Nortel CS2000 Technology Pack defines an element name for each Passport Packet Voice Gateway (PVG)
device operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack manages the creation
of element names for the PVG devices through a Bulk Adaptor Design File that is maintained by IBM
Professional Services. This technology pack also provides a configuration file called PVGConfig.js that allows
IBM Professional Services to specify customer-specific configuration parameters. See Appendix A, Configuration
for information on how to specify customer-specific options in the PVGConfig.js configuration file. It is also
necessary to specify PVG Bulk Adaptor Design File configuration settings in the dc.cfg configuration file. See
Appendix C, Template File Reference (Pre-443 Only) for information on the PVG Bulk Adaptor Design File settings
you must specify in the dc.cfg configuration file.
The Nortel CS2000 Technology Pack defines the element name for a PVG device by using the following syntax:
OFFICEID | LINKID | OFFICEID&LINKID
where:
OFFICEID Specifies that the element name for a PVG device can consist of an office ID field that resides
in the PVG Performance file associated with a PVG device operating in the Nortel CS2000 environment.
LINKID Specifies that the element name for a PVG device can consist of a link ID field that resides in
the PVG Performance file associated with a PVG device operating in the Nortel CS2000 environment. The
following syntax describes the information that the LINKID field provides:
EM/shelf_id/component_id
where:
shelf_id Specifies the ID of the shelf associated with the component managed by the PVG device.
component_id Specifies the ID of the component managed by the PVG device.
The following list shows examples of the LINKID field in a PVG Performance file for a PVG device:
EM/DESIGN_6 SHELF CARD/14
EM/DESIGN_6 SHELF CARD/15
EM/DESIGN_6 SHELFFABRICCARD/X
EM/DESIGN_6 LP/10 SONET/0
EM/DESIGN_6 LP/12 VSPPMODULE/1 PBLOCK/1
EM/DESIGN_6 ATMIF/1000
EM/DESIGN_6 NSTA/12
EM/DESIGN_3 LP/15 ETH/3
EM/DESIGN_3 NSTA/12VGS
OFFICEID&LINKID Specifies that the element name for a PVG device can consist of a combination of
the office ID and link ID fields residing in the PVG Performance files.
The following example uses the OFFICEID field to define the element name for a PVG device:
LowellPVG
Nortel SST Device Element Name
The Nortel CS2000 Technology Pack defines an element name for each Nortel Session Server Trunk (SST) device
operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack manages the creation of
element names for the Nortel SST devices through a Bulk Adaptor Design File that is maintained by IBM
Professional Services. It is necessary to specify Nortel SST Bulk Adaptor Design File configuration settings in the
dc.cfg configuration file. See Appendix C, Template File Reference (Pre-443 Only) for information on the Nortel
SST Bulk Adaptor Design File settings you must specify in the dc.cfg configuration file.
Nortel USP Device Element Name
The Nortel CS2000 Technology Pack defines an element name for each Universal Signaling Point (USP) device
operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack manages the creation of
element names for the USP devices through a Bulk Adaptor Design File that is maintained by IBM Professional
Services. It is necessary to specify USP Bulk Adaptor Design File configuration settings in the dc.cfg
configuration file. See Appendix C, Template File Reference (Pre-443 Only) for information on the USP Bulk Adaptor
Design File settings you must specify in the dc.cfg configuration file.
The Nortel CS2000 Technology Pack defines this element name based on the hostname on which the USP device
resides. The Nortel CS2000 Technology Pack obtains this hostname from the Universal Resource Identifier (URI)
configured in UBANORTEL.xml: ftp://user:passwd@HOSTNAME/xxxxxxx. The reason for this approach is
that the USP device hostname cannot be guaranteed to be stored in the associated input files and because the
element field does not always provide this hostname from one record to another.
Sub-Element Names Defined for Nortel CS2000 Devices
The sub-element name identifies the sub-element that resides in the database. The sub-element names discussed
in the following sections display in the name column (Sub-Element view) of the Netcool/Proviso DataMart
Resource Editor. Sub-element names are often used in reports to identify specific entities.
The Nortel CS2000 Technology Pack defines a group of Netcool/Proviso elements, sub-elements, and properties
that map to the devices and services that operate in the network. For information on how to use the
Netcool/Proviso DataMart Request Editor to configure data collection requests and the Netcool/Proviso
DataMart Resource Editor to view sub-element names, see the Netcool/Proviso DataMart Configuration Guide.
The Nortel CS2000 Technology Pack defines sub-element names for the devices, device components, and
services operating in the Nortel CS2000 environment. Specifically, the Nortel CS2000 Technology Pack defines:
Nortel CS2000 Device Sub-Element Names
Nortel CS2000 CDRs Sub-Element Names
Nortel CS2000 Extended QoS Sub-Element Names
Nortel IEMS Device Sub-Element Names
Nortel PVG Device Sub-Element Names
Nortel SST Sub-Element Name
Nortel USP Device Sub-Element Names
The following sections discuss the defined sub-element names for each of these devices and associated
components and services.
Nortel CS2000 Device Sub-Element Names
The Nortel CS2000 Technology Pack defines sub-element names for the components associated with a Nortel
CS2000 device operating in the Nortel CS2000 environment. Specifically, the Nortel CS2000 Technology Pack
defines:
Nortel CS2000 Device Sub-Element Name
CS2K Softswitch Trunk Sub-Element Name
The following sections discuss the defined sub-element names for these Nortel CS2000 device components.
Nortel CS2000 Device Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel CS2000 device itself. This sub-
element reports originating, terminating, incoming, and outgoing network traffic that occurs on the Nortel
CS2000 device. The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name
for a Nortel CS2000 device:
switchname_Device
where:
switchname Specifies a switch name field that resides in the input files associated with a Nortel CS2000
device operating in the Nortel CS2000 environment.
Device Specifies the string that follows the switch name.
The following is an example of a sub-element name for a Nortel CS2000 device taken from the name column
(Sub-Element view) of the Netcool/Proviso DataMart Resource Editor:
CS2KPERF_BOSTON_Device
CS2K Softswitch Trunk Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Communication Server 2000
(CS2K) Softswitch Trunk component. This component connects to external network devices. This sub-element
reports outgoing and transit network traffic statistics that occur on the CS2K Softswitch Trunk. The Nortel
CS2000 Technology Pack uses the following syntax to define the sub-element name for a CS2K Softswitch Trunk:
switchname_Trunkinstance
where:
switchname Specifies a switch name field that resides in the input files associated with a CS2K
Softswitch Trunk operating in the Nortel CS2000 environment.
Trunk Specifies the string that follows the switch name and identifies this as a CS2K Softswitch Trunk
component.
instance Specifies an instance of the CS2K Softswitch Trunk component. The Nortel CS2000
Technology Pack automatically discovers the instance using the Tuple/Number/Key/Info field value.
The following is an example of a sub-element name for a CS2K Softswitch Trunk device taken from the name
column (Sub-Element view) of the Netcool/Proviso DataMart Resource Editor:
CS2KPERF_BOSTON_Trunk3
Nortel CS2000 CDRs Sub-Element Names
The Nortel CS2000 Technology Pack defines sub-element names for the Nortel Communication Server 2000
(CS2K) Call Detail Records (CDRs). Specifically, the Nortel CS2000 Technology Pack defines:
Nortel CS2000 Sub-Element Name
Customer Profile Sub-Element Name
Termination Cause Sub-Element Name
TypeOfCall Sub-Element Name
Media Gateway Trunk Sub-Element Name
Subscriber Zone Sub-Element Name
Path Sub-Element Name
Extension Sub-Element Name
The following sections discuss the defined sub-element names for these Nortel CS2000 CDRs.
Nortel CS2000 Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel CS2000 device itself. This sub-
element reports call accounting and voice quality metrics that occur on the Nortel CS2000 device through the
collection of Call Detail Records (CDRs). These CDRs reside in Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Nortel
CS2000 device:
CDR_CS2Ksensorid_Device
where:
CDR Specifies the string that begins each sub-element name for a CS2K CDR device-related component.
CS2Ksensorid Specifies the sensor ID for this CS2000 device.
Device Specifies the string that follows the sensor ID for this Nortel CS2000 device.
The following are examples of sub-element names for Nortel CS2000 devices taken from the name column (Sub-
Element view) of the Netcool/Proviso DataMart Resource Editor:
CDR_LOWELL_1_SENSOR_Device
CDR_LOWELL_2_SENSOR_Device
Customer Profile Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Customer Profile. This sub-element
reports call accounting and packet metrics that occur on the Nortel CS2000 device through the collection of Call
Detail Records (CDRs). These CDRs reside in Bulk input files. The metrics are collected for specific customer
profiles. Each Nortel CS2000 device can be configured to manage the following types of customer profile:
Residential
Corporate
Inter trunk (no subscriber billing)
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Customer
Profile:
CDR_CS2Ksensorid_Customer_customerprofile
where:
CDR Specifies the string that begins each sub-element name for a CS2K CDR device-related component.
Customer_ Specifies the string that follows the sensor ID for this Nortel CS2000 device and that
identifies this CDR as a Customer Profile.
customerprofile Specifies one of the following customer profile values:
Residential The customer is a residential customer.
Corporate The customer is a corporate customer.
InterTrunk There is no subscriber billing.
The following are examples of sub-element names for Customer Profiles taken from the name column (Sub-
CDR_MTV_19_SENSOR_Customer_Residential
CDR_MTV_19_SENSOR_Customer_Corporate
CDR_MTV_19_SENSOR_Customer_InterTrunk
Termination Cause Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for each Termination Cause defined in the
Q.931 protocol. Each Termination Cause sub-element reports on the total number of calls per termination cause.
The Nortel CS2000 Technology Pack collects this metric for each sub-element through the collection of Call
Detail Records (CDRs) that reside in Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Termination
Cause:
CDR_CS2Ksensorid_TC_terminationcause
where:
CDR_ Specifies the string that begins each sub-element name for a CS2K CDR device-related component.
TC Specifies the string that follows the sensor ID for this Nortel CS2000 device and that identifies this
CDR as a Termination Cause.
terminationcause Specifies one of the termination causes identified by the Q.931 protocol.
The following are examples of sub-element names for a Termination Cause taken from the name column (Sub-
CDR_MTV_19_SENSOR_TC_NoCircuit
CDR_MTV_19_SENSOR_TC_NormalCallClearing
CDR_MTV_19_SENSOR_TC_PermanentSignal
TypeOfCall Sub-Element Name
The Nortel CS2000 Technology Pack does not manage each phone number or each subscriber as a specific sub-
element. Instead, the Nortel CS2000 Technology Pack defines a sub-element name for the TypeOfCall, which
categorizes the call according to its direction. This sub-element reports call usage metrics that occur on the Nortel
CS2000 device through the collection of Call Detail Records (CDRs) that reside in Bulk input files. The metrics
are collected for the following types of calls:
Internal
External
Incoming
Outgoing
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a TypeOfCall:
CDR_CS2Ksensorid_TypeOfCall_typeofcall
where:
TypeOfCall Specifies the string that follows the sensor ID for this Nortel CS2000 device and that
identifies this CDR as a TypeOfCall.
typeofcall Specifies one of the following call types:
Internal Specifies a call where both caller and callee are part of the carrier VoIP on-net network.
External Specifies a call where both caller and callee are part of the carrier VoIP off-net network.
Incoming Specifies a call that is an off-net network call coming from the Public Switched Telephone
Network (PSTN) and going to an internal VoIP number. An incoming call is a call where the AMA record
has the TRUNK_FACILITY_MODULE defined and where TRUNK_FACILITY_ID starts with the 1 digit
(1=incoming call, 2=outgoing call).
Outgoing Specifies a call that is an off-net network call routed to the PSTN and originating from an
internal VoIP number. An outgoing call is a call where the AMA record has the
TRUNK_FACILITY_MODULE defined and where TRUNK_FACILITY_ID starts with the 2 digit
(1=incoming call, 2=outgoing call).
undefined The type of call could not be determined.
The following are examples of sub-element names for a TypeOfCall taken from the name column (Sub-Element
view) of the Netcool/Proviso DataMart Resource Editor:
CDR_MTV_18_SENSOR_TypeOfCall_Incoming
CDR_MTV_20_SENSOR_TypeOfCall_Outgoing
CDR_LOWELL_1_SENSOR_TypeOfCall_Internal
Media Gateway Trunk Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway Trunk. This sub-
element reports call accounting and packet metrics that occur on the Nortel CS2000 device through the collection
of Call Detail Records (CDRs) that reside in Bulk input files. The metrics are collected for specific media gateway
devices.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Media
Gateway Trunk:
CDR_CS2Ksensorid_Trunk_trunkname
where:
Trunk Specifies the string that follows the sensor ID for this Nortel CS2000 device and that identifies
this CDR as a Media Gateway Trunk.
trunkname Specifies the name of the trunk for this Media Gateway Trunk.
The following are examples of sub-element names for a Media Gateway Trunk taken from the name column (Sub-
CDR_MTV_18_SENSOR_Trunk_MTV_TRUNK_3
CDR_MTV_18_SENSOR_Trunk_MTV_TRUNK_2
Subscriber Zone Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Subscriber Zone. A Subscriber Zone
is defined by a group of subscribers connected to the same group of Digital Subscriber Line Access Multiplexers
(DSLAMs) (or any other group of access network devices). The Nortel CS2000 Technology Pack manages each
Subscriber Zone as a sub-element, using the subscriberid field in the Bulk input files. The Subscriber Zone
information is only available for successful calls where records in the files are defined. This sub-element reports
call accounting and packet metrics that occur on the Nortel CS2000 device through the collection of Call Detail
Records (CDRs) that reside in Bulk input files. The metrics are collected for specific subscriber zones.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Subscriber
Zone:
CDR_CS2Ksensorid_Zone_zonename
where:
Zone Specifies the string that follows the sensor ID for this Nortel CS2000 device and that identifies this
CDR as a Subscriber Zone.
zonename Specifies the name of the zone.
The following are examples of sub-element names for a Subscriber Zone taken from the name column (Sub-
CDR_MTV_17_SENSOR_Zone_LOWELL
CDR_MTV_20_SENSOR_Zone_LOWELL
CDR_LOWELL_2_SENSOR_Zone_LOWELL
Path Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Path. A Path is an end-to-end
Subscriber Zone (or Pop) between the location of the Nortel CS2000 device and the location of the Media
Gateway Trunk. The Nortel CS2000 Technology Pack manages each Path as a sub-element, using Media Gateway
Trunk and Subscriber Zone information in the Bulk input files. The Path information is only available for
successful calls where records in the files are defined. This sub-element reports call accounting and packet metrics
that occur on the Nortel CS2000 device through the collection of Call Detail Records (CDRs) that reside in Bulk
input files. The metrics are collected for specific paths.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Path:
CDR_CS2Ksensorid_Path_pathname_zonename_trunkfacility
where:
Path Specifies the string that follows the sensor ID for this Nortel CS2000 device and that identifies this
CDR as a Path.
pathname Specifies the name of the path.
zonename Specifies the name of the zone.
trunkfacility Specifies the CS2K Softswitch Trunk component of a Nortel CS2000 device.
The following are examples of sub-element names for a Path taken from the name column (Sub-Element view)
of the Netcool/Proviso DataMart Resource Editor:
CDR_MTV_17_SENSOR_Path_LOWELL_3481
Extension Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Extension.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for an Extension:
CDR_Extension_Untracked
where:
Extension Specifies the string that identifies this CDR as an Extension.
Untracked Specifies the string that identifies this CDR as an Extension whose location is unknown.
The following is an example of a sub-element names for an Extension taken from the name column (Sub-Element
CDR_Extension_Untracked
Nortel CS2000 Extended QoS Sub-Element Names
The Nortel CS2000 device supports Extended QoS (Quality of Service) voice and quality measures available
through the Nortel Centrex IP Client Manager (CICM). This support guarantees that end-to-end latency will not
exceed a specific level. The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel CS2000
Extended QoS. Specifically, the Nortel CS2000 Technology Pack maps the Nortel CS2000 Extended QoS to a
CDR location sub-element.
The Nortel CS2000 Technology Pack maps Nortel CS2000 Extended QoS to a CDR location sub-element
through the locationMap hash table in the cs2kcdr.pl file. The mapping algorithm takes the IP addresses
associated with CDR locations and maps them to location strings. The Nortel CS2000 Technology Pack uses the
following syntax to define the sub-element name for a CDR location:
CDR_Location_location
where:
CDR_Location Specifies the string that further identifies this Nortel CICM component as a CDR
location.
location Specifies a string that identifies the location. The Bulk Adaptor Design File makes use of the
locationMap hash table in the cs2kcdr.pl file to map the IP address to the location string. Note that
the string is preceded with an _ (underscore) character.
The following is an example of a CDR location sub-element name taken from the name column (Sub-Element
CDR_Location_Lowell6
Nortel IEMS Device Sub-Element Names
A Nortel Integrated Element Management System (IEMS) serves as the Media Server component in the Nortel
CS2000 environment. The Nortel CS2000 Technology Pack defines sub-element names for the components
associated with a Nortel IEMS device. Specifically, the Nortel CS2000 Technology Pack defines:
Nortel AMS Sub-Element Name
Nortel CICM Sub-Element Name
Nortel GWC Sub-Element Name
Nortel MS 20xx Device Sub-Element Name
Nortel RAS Port Sub-Element Name
Nortel SAM21 Shelf Controller Sub-Element Name
Nortel SSL Sub-Element Name
The following sections discuss the defined sub-element names for these Nortel IEMS device components.
Nortel AMS Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Announcement Media Server
(AMS) component. The Nortel AMS component provides announcement services. The Nortel CS2000
Technology Pack manages each Nortel AMS as a sub-element, attaching specific records from the Bulk input files.
SAM21 Shelf Controller:
elementname_entityType_Device
where:
elementname Specifies the element name for the Nortel IEMS device. See Nortel IEMS Device Element
Name on page 171 for more information. The syntax shows that the elementname is followed by an _
(underscore) character.
entityType Specifies the string that identifies this IEMS component. This string is obtained by the Bulk
Adaptor Design File using the Entity Type property that resides in the input file associated with this
component. In this case, the Entity Type property has a value of AMS.
_Device Specifies a string that the input Bulk Adaptor Design File appends to the entityType. Note that
The following is an example of a sub-element name for a Nortel AMS component taken from the name column
49.204.91.120_AMS_Device
Nortel CICM Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Centrex IP Client Manager
(CICM) component of a Nortel CS2000. The Nortel CS2000 Technology Pack manages each Nortel CICM as a
sub-element, attaching specific records from the Bulk input files.
CICM device:
where:
Adaptor Design File using the Entity Type property that resides in the file associated with this
component. In this case, the Entity Type property has a value of CICM_Mgr.
_Device Specifies a string that the Bulk Adaptor Design File appends to the entityType. Note that the string
is preceded with an _ (underscore) character.
The following is an example of a sub-element name for a Nortel CICM component taken from the name column
47.104.11.120_CICM_Mgr_Device
Nortel GWC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Gateway Controller (GWC)
component of a Nortel CS2000. The Nortel CS2000 Technology Pack manages each Nortel GWC device as a
sub-element, attaching specific records from the Bulk input files.
GWC device:
where:
component. In this case, the Entity Type property has a value of GWC.
The following is an example of a sub-element name for a Nortel SSL component taken from the name column
47.104.11.120_GWC_Device
Nortel MS 20xx Device Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Media Server 20xx (MS 20xx)
media server component of a Nortel CS2000. The media server component provides announcement,
conferencing, intercept, and trunk testing capabilities. An example of this media server component is the Nortel
Media Server 2010 (MS 2010). The Nortel CS2000 Technology Pack manages each Nortel MS 20xx media server
as a sub-element, attaching specific records from the Bulk input files.
Media Server 20xx (MS 20xx) device:
where:
component. In this case, the Entity Type property has a value of MS2000.
_Device Specifies a string that the input Bulk Adaptor Design File appends to the entityType. Note that
The following are examples of sub-element names for Nortel MS 2000 components taken from the name column
172.17.40.230_MS2000_Device
172.17.40.232_MS2000_Device
Nortel RAS Port Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Remote Access Server (RAS)
Port component. The Nortel CS2000 Technology Pack manages each Nortel RAS Port as a sub-element,
attaching specific records from the Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Nortel RAS
Port:
elementname_entityType_RAS_Port_vpnPort
where:
component. In this case, the Entity Type property has a value of AMS.
_RAS_Port_ Specifies the string that further identifies this IEMS component as a Nortel RAS Port. The
Bulk Adaptor Design File appends this string to the entityType. Note that the string is preceded with and
followed by _ (underscore) characters.
vpnPort Specifies the RAS port number. The Bulk Adaptor Design File obtains this value by parsing the
MeasureSuppId1 property value. In the example, the MeasureSuppId1 property value is VPN3-0.
The following is an example of a sub-element name for a Nortel RAS Port component taken from the name
49.204.91.120_AMS_RAS_Port_VPN3-0
Nortel SAM21 Shelf Controller Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel SAM21 Shelf Controller
component. The Nortel SAM21 component provides the hardware that hosts and supports Gateway Controller
(GWC) circuit cards and associated software. The Nortel CS2000 Technology Pack manages each Nortel SAM21
as a sub-element, attaching specific records from the Bulk input files.
SAM21 Shelf Controller:
where:
component. In this case, the Entity Type property has a value of SAM21.
The following is an example of a sub-element name for a Nortel SAM21 component taken from the name column
172.17.40.230_SAM21_Device
Nortel SPC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Session Policy Controller (SPC)
(also referred to as a Nortel Session Server) component of a Nortel CS2000. The Nortel CS2000 Technology Pack
manages each Nortel Session Policy Controller as a sub-element, attaching specific records from the Bulk input
files.
Session Policy Controller device:
where:
component. In this case, the Entity Type property has a value of Session_Server.
The following is an example of a sub-element name for a Nortel Session Policy Controller component taken from
the name column (Sub-Element view) of the Netcool/Proviso DataMart Resource Editor:
47.104.11.120_Session_Server_Device
Nortel SSL Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Session Server Lines (SSL)
component of a Nortel CS2000. The Nortel CS2000 Technology Pack manages each Nortel SSL device as a sub-
element, attaching specific records from the Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Nortel SSL
device:
where:
component. In this case, the Entity Type property has a value of SSL.
The following is an example of a sub-element name for a Nortel SSL component taken from the name column
47.104.11.120_SSL_Device
Nortel PVG Device Sub-Element Names
The Nortel CS2000 Technology Pack defines sub-element names for the components associated with a Passport
Packet Voice Gateway (PVG) device operating in the Nortel CS2000 environment. Specifically, the Nortel
CS2000 Technology Pack defines:
PVG Device Sub-Element Name
Media Gateway FC Sub-Element Name
Media Gateway SC Sub-Element Name
MGI Sub-Element Name
Media Gateway VSP PC Sub-Element Name
Media Gateway VSP CC Sub-Element Name
The following sections discuss the defined sub-element names for these PVG device components.
PVG Device Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Passport Packet Voice Gateway (PVG)
device itself. Although the PVG Performance files associated with PVG devices provide no statistical data at the
device level, the Nortel CS2000 Technology Pack defines a sub-element name for the device. The reason for this
is to create additional metrics coming from the PVG devices associated components (for example, the Media
Gateway FC, MGI, Media Gateway VSP PC, and so forth).
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a PVG device:
elementname_Device
where:
elementname Specifies the element name for the PVG device. See Nortel PVG Device Element Name on
page 171 for more information.
Device Specifies the string that follows the element name. The string identifies this component as the
PVG device itself.
The following is an example of a sub-element name for a PVG device taken from the name column (Sub-Element
LowellPVG_Device
Media Gateway FC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway Fabric Card (FC)
component of a PVG device. This sub-element reports card temperature statistics that the Media Gateway FC
generates. The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a
Media Gateway FC component:
elementname_SHELFFABRICCARD/card_id
where:
SHELFFABRICCARD Specifies the string that follows the element name. The string identifies this
component as a Media Gateway FC. This string is part of a substring value of the LINKID field in the input
file associated with the PVG device.
card_id Specifies an ID that uniquely identifies the Media Gateway FC component. This value is part of a
substring value of the LINKID field.
The following is an example of a sub-element name for a Media Gateway FC component taken from the name
LowellPVG_SHELFFABRICCARD/Y
Media Gateway SC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway Shelf Card (SC)
component of a PVG device. This sub-element reports card CPU load and local messages statistics that the Media
Gateway SC generates. The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element
name for a Media Gateway SC component:
elementname_SHELF_CARD/card_id
where:
SHELF_CARD Specifies the string that follows the element name. The string identifies this component as
a Media Gateway SC. This string is part of a substring value of the LINKID field in the input file associated
with the PVG device.
card_id Specifies an ID that uniquely identifies the Media Gateway SC component. This value is part of a
The following are examples of sub-element names for Media Gateway SC components taken from the name
LowellPVG_SHELF_CARD/12
LowellPVG_SHELF_CARD/15
MGI Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway Interface (MGI)
component of a PVG device. This sub-element reports network interface performance statistics that the MGI
generates. The Nortel CS2000 Technology Pack collects network performance statistics on DS1 (T-1) or DS3 (T-
3) interfaces that connect to the Public Switched Telephone Network (PSTN). The Nortel CS2000 Technology
Pack does not collect network performance statistics for network interfaces that make use of Asynchronous
Transfer Mode (ATM) technology and the Frame Relay protocol.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for an MGI
component:
elementname_networkinterface/number networkinterfacetype/netinterfaceid
where:
networkinterface Specifies the string that follows the element name. The string identifies this component as
an MGI. This string is part of a substring value of the LINKID field in the input file associated with the PVG
device. Possible values include LP and ATMIF.
number Specifies a number that uniquely identifies the MGI component. This value is part of a substring
value of the LINKID field.
networkinterfacetype Specifies a string that identifies the type of MGI component. This value is part of a
substring value of the LINKID field. The following list identifies some of the supported strings:
ETH The MGI uses an Ethernet network interface.
SONET The MGI uses a network interface that adheres to the Synchronous Optical Network
(SONET) standard.
SDH The MGI uses a network interface that adheres to the SDH (Synchronous Digital Hierarchy)
standard.
DS1 The MGI uses a T-1 carrier network interface.
DS3 The MGI uses a T-3 carrier network interface.
netinterfaceid Specifies a number that uniquely identifies the MGI component. This value is part of a
The following examples show sub-element names for MGI components taken from the name column (Sub-
LowellPVG_ATMIF/1000
LowellPVG_LP/10_SONET/0
LowellPVG_LP/10_SONET/1
Media Gateway VSP PC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway VSP Processor Card
(PC) component of a PVG device. This sub-element reports CPU load statistics that the Media Gateway VSP PC
Media Gateway VSP Processor Card (PC) component:
elementname_VSPMODULE/vspnumber_PBLOCK/pblock_number
where:
VSPMODULE Specifies the string that identifies this component as a Media Gateway VSP PC. This string
is part of a substring value of the LINKID field.
vspnumber Specifies a number that uniquely identifies the Media Gateway VSP PC component. This value
is part of a substring value of the LINKID field.
PBLOCK This string is part of a substring value of the LINKID field.
pblock_number This value is part of a substring value of the LINKID field.
The following is an example of a sub-element name for a Media Gateway VSP PC component that uses the
element name for a PVG device and the substring value of the LINKID field:
LowellPVG_VSPMODULE/15_PBLOCK/5
LowellPVG_VSPMODULE/16_PBLOCK/5
Media Gateway VSP CC Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Media Gateway VSP Call Card (CC)
component of a PVG device. This sub-element reports call signaling statistics that the Media Gateway VSP CC
Media Gateway VSP CC component:
elementname_NSTA/number
where:
NSTA Specifies the string that follows the element name. The string identifies this component as a Media
Gateway VSP CC. This string is part of a substring value of the LINKID field in the input file associated with
the PVG device.
number Specifies a number that uniquely identifies the Media Gateway VSP CC component. This value is
part of a substring value of the LINKID field.
The following is an example of sub-element name for a Media Gateway VSP CC component taken from the name
LowellPVG_NSTA/12
Nortel SST Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Nortel Session Server Trunk (SST)
component of a Nortel CS2000. The Nortel CS2000 Technology Pack manages each Nortel SST device as a sub-
element, attaching specific records from the Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a Nortel SST
device:
where:
elementname Specifies the element name for the Nortel SST device. See Nortel SST Device Element Name on
page 172 for more information. The syntax shows that the elementname is followed by an _ (underscore)
character.
entityType Specifies the string that identifies this SST component. This string is obtained by the Bulk
component. In this case, the Entity Type property has a value of SST.
The following is an example of a sub-element name for a Nortel SST component taken from the name column
47.104.11.120_SST_Device
Nortel USP Device Sub-Element Names
The Nortel CS2000 Technology Pack defines sub-element names for the components associated with a Universal
Signaling Point (USP) device operating in the Nortel CS2000 environment. A Universal Signaling Point (USP)
serves as the Signaling Gateway component in the Nortel CS2000 environment. Specifically, the Nortel CS2000
Technology Pack defines:
USP Device Sub-Element Name
USP Linkset Sub-Element Name
USP Routeset Sub-Element Name
USP Carrier Link Sub-Element Name
The following sections discuss the defined sub-element names for these USP device components.
USP Device Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Universal Signaling Point (USP) device
itself. The Nortel CS2000 Technology Pack manages each USP device as a sub-element, using SS7 Signaling
Connection Control Part (SCCP) messages, routing information, and error-related information from the USP
Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a USP device:
elementname_Device
where:
elementname Specifies the element name associated with a USP device. See Nortel USP Device Element
Name on page 172 for a description of the syntax associated with a USP device element name.
Device Specifies the string that identifies this sub-element as the USP device itself.
The following is an example of a sub-element name for a USP device taken from the name column (Sub-Element
maple_Device
USP Linkset Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Universal Signaling Point (USP) linkset
component. The linkset component provides links between Signal Transfer Points (STPs). The Nortel CS2000
Technology Pack manages each USP linkset as a sub-element, attaching specific records from the USP Bulk input
files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a USP linkset
component:
elementname_subelementname
where:
elementname Specifies the element name associated with the linkset component of a USP device. See
Nortel USP Device Element Name on page 172 for a description of the syntax associated with a USP device
element name.
subelementname Specifies the sub-element name associated with the linkset component of a USP
device.
The following are examples of sub-element names for linkset components of a USP device taken from the name
maple_LS_CS2K_LS
maple_LS_CTI2_LS
USP Routeset Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Universal Signaling Point (USP)
routeset component. The routeset component provides routes between Originating Point Code (OPC) nodes and
Destination Point Code (DPC) nodes. The Nortel CS2000 Technology Pack manages each USP routeset as a sub-
element, attaching specific records from the USP Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a USP
routeset component:
where:
elementname Specifies the element name associated with the routeset component of a USP device. See
Nortel USP Device Element Name on page 172 for a description of the syntax associated with a USP device
element name.
subelementname Specifies the sub-element name associated with the routeset component of a USP
device.
The following are examples of sub-element names for routeset components of USP device taken from the name
maple_RS:STP1_RS
maple_RS:CTI2_RS
USP Carrier Link Sub-Element Name
The Nortel CS2000 Technology Pack defines a sub-element name for the Universal Signaling Point (USP) carrier
link component. The carrier link component provides links between carrier DS1 links and paths. The Nortel
CS2000 Technology Pack manages each USP carrier link as a sub-element, attaching specific records from the
USP Bulk input files.
The Nortel CS2000 Technology Pack uses the following syntax to define the sub-element name for a USP
routeset component:
where:
elementname Specifies the element name associated with the carrier link component of a USP device.
See Nortel USP Device Element Name on page 172 for a description of the syntax associated with a USP device
element name.
subelementname Specifies the sub-element name associated with the carrier link component of a USP
device.
The following are examples of sub-element names for carrier link components of a USP device taken from the
name column (Sub-Element view) of the Netcool/Proviso DataMart Resource Editor:
maple_E1_MTP_NODE_2_1
maple_E1_MTP_NODE_2_2
Nortel CS2000 Devices Sub-Element Labels
The sub-element label identifies a specific instance of the sub-element that resides in the database. The sub-
element labels associated with the Nortel CS2000 Technology Pack display in the label column (Sub-Element
view) of the Netcool/Proviso DataMart Resource Editor. It is useful to know sub-element labels because they
typically display in reports. For information on how to use the Netcool/Proviso DataMart Request Editor to
configure data collection requests and the Netcool/Proviso DataMart Resource Editor to view sub-element
labels, see the Netcool/Proviso DataMart Configuration Guide.
The Nortel CS2000 Technology Pack defines sub-element labels for each defined sub-element. The Nortel
CS2000 Technology Pack maps all sub-element labels to the sub-element names. In other words, the sub-element
label is exactly the same as the sub-element name. The following example shows the sub-element labels for the
Customer Profile (which are exactly the same as the sub-element name):
CDR_MTV_19_SENSOR_Customer_Residential
CDR_MTV_19_SENSOR_Customer_Corporate
CDR_MTV_19_SENSOR_Customer_InterTrunk
Nortel CS2000 Devices Sub-Element Family Names
The sub-element family identifies the family to which the sub-element belongs. The sub-element family name
displays in the fam column (Sub-Element view) of the Netcool/Proviso DataMart Resource Editor. It is useful to
know sub-element families because you can sort entries by family name.
For information on how to use the Netcool/Proviso DataMart Request Editor to configure data collection
requests and the Netcool/Proviso DataMart Resource Editor to view sub-element families, see the Netcool/Proviso
DataMart Configuration Guide.
Table 3 lists the family names for the sub-elements that the Nortel CS2000 Technology Pack defines. The table
lists the device or service associated with the sub-element. See the appropriate section in this chapter for a
description of the syntax used to define the sub-element name for each device or service.
Table 3: Sub-Element Family Names
Family Name Sub-Element (Associated Device/Service)
Nortel CS2K Nortel CS2000 CDR
Nortel SSL
Nortel_IEMS Nortel AMS
Nortel CICM
Nortel GWC
Nortel MS 20xx Device
Nortel RAS Port
Nortel SAM21 Shelf Controller
Nortel SPC
VOIP_Softswitch CS2K Softswitch Trunk
Customer Profile
Extension
Media Gateway FC
Media Gateway Interface
Media Gateway SC
Media Gateway Trunk
Media Gateway VSP CC
Media Gateway VSP PC
Nortel CS2000 Device
Nortel CS2000 Extended QoS
Nortel SST
Path
PVG Device
Termination Cause
TypeOfCall
USP Carrier Link
USP Device
USP Linkset
USP Routeset
Zone
Chapter 7: Bulk Collection Formulas
Overview
A Bulk collection formula, unlike an SNMP collection formula, has no executable instructions. However, the Bulk
Collector requires database IDs for the value it returns after reading Bulk input files. Bulk collection formulas
provide these unique database IDs. The Formula Table (FRML_DESC) must contain an ID for each metric the
Bulk Collector might return. If the entry in the Formula Table does not exist, the Bulk Collector cannot report
the value.
Typically, a Bulk collection formula consists of a name that maps to a statistic that resides in a Bulk input file.
Typically, the device or devices that the technology pack supports generate the statistics that reside in these Bulk
input files. In many cases, the statistics reside in these Bulk input files as data records or data fields.
Each Bulk collection formula name has an associated ID. It is the Bulk collection formula ID (along with the sub-
element ID and timestamp) that identify a specific location in the database where the statistic resides. In other
words, the Bulk collection formulas do not perform any calculations, but merely serve as pointers to the actual
statistics residing in the database.
There are many formats associated with Bulk input files, for example CSV, XML, and binary. Typically, a
technology pack provides a Bulk Adaptor Design File (implemented as a JavaScript file) that defines the format
or formats of the Bulk input files for which it is responsible for processing. This Bulk Adaptor Design File
processes both inventory and statistics from the same Bulk input file. More specifically, this Bulk Adaptor Design
File provides a function that creates the Bulk collection formula names. Some technology packs might provide
several Bulk Adaptor Design Files each of which handles a specific Bulk input file format.
Data Collection
This technology pack uses bulk collection to gather data about Nortel CS2000 devices and services.
Topic Page
Overview 191
Data Collection 191
Formulas and Metrics 192
Netcool/Proviso Formula Tree for the Nortel CS2000 Technology Pack 192
Formula Reference 193
With bulk collection, the Netcool/Proviso Bulk Collector gathers input files that contain non-SNMP data
generated by Nortel CS2000 devices. This data is processed by the technology packs Bulk Adaptor Design Files,
which are described in Chapter 4.
Formulas and Metrics
After the network data is collected, Netcool/Proviso processes the data and generates the metrics that are stored
in the DataMart database and used in DataView reports. This processing is performed by the formulas described
in this chapter.
A metric has the same name as the formula that generates it.
Metrics are categorized according to the type of process used to calculate the metric, as follows:
Import Data collected from bulk input files generated by a Nortel CS2000 device and processed by the
Bulk Adaptor Design File. In some cases, the design file maps a bulk metric to a single statistic in an input
file. In other cases, the design file generates a bulk metric value through a calculation involving multiple input
file statistics.
Generic A metric whose database location is mapped to multiple formulas. This allows the formulas
to store the metrics they generate against a single database ID, allowing the metrics to appear in a single
DataView report.
CME Metrics that are produced by calculations that the Netcool/Proviso Complex Metric Engine (CME)
performs, using other metrics and sub-element properties as inputs.
Note: Generic and CME formulas may not be included in this technology pack.
Metrics may appear in DataView reports as raw data, or they may be further processed by the Complex Metric
Engine for example, to produce data aggregations over time. To learn where the metrics generated by the
formulas in this chapter are used, see the chapter on supported reports in this guide.
This chapter is a reference of the formulas that the Nortel Communication Server 2000 Technology Pack
provides. The chapter lists formulas alphabetically.
Netcool/Proviso Formula Tree for the Nortel CS2000 Technology
Pack
Figure 3 shows the formula tree where the Bulk collection formulas are defined in the Netcool/Proviso database.
You can access this directory using the Netcool/Proviso DataMart Formula Selector. See the Netcool/Proviso
DataMart Configuration Guide for more information.
Figure 3 also shows that the Bulk collection formulas reside in directories that map to the devices and associated
components operating in the Nortel CS2000 environment.
Figure 3: Nortel CS2000 Technology Pack Formula Tree
Formula Reference
The following pages provide a reference of the bulk collection formulas that this technology pack provides. The
reference pages have the following sections:
Type. The source of data for the formula being described for example, IMPORT (collect).
Description. The description of the formula.
Syntax. Bulk formulas have no executable instructions. Typically, this section indicates that a bulk metric is
mapped to this formula in the Netcool/Proviso database.
Bulk metrics can be used in Netcool/Proviso DataView reports and in calculations of other metrics.
Generic Database Alias. A database location where the bulk metric can be stored.
Typically, generic metrics serve as repositories in the database for mixed data collected from a particular kind
of sub-element for example, low- and high-capacity interfaces. Storing mixed data against a generic metric
ID allows you to display the different kinds of data in a single report.
Path. The path where the referenced bulk formula appears in the Netcool/Proviso database.
You view the formula tree through the Formula Selector dialog of the Netcool/Proviso Formula Editor. To
display this dialog, click File > Load in the Formula Editor.

Type
Import
Description
This formula provides the failure percentage for a three port conference server during the period observed.
Syntax
#Bulk Metric
Generic Database Alias
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Softswitch Platform > Class 5 Softswitch > MS2010
3PortOcc
Type
Import
Description
This formula provides the percentage occupancy for a three port conference server.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the failure percentage for a six port conference server during the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
6PortOcc
Type
Import
Description
This formula provides the percentage occupancy for a six port conference server.
Syntax
#Bulk Metric
None.
Formula Editor Path
AboveMOSpercentage
Type
Import
Description
This formula calculates the total number of streams that measured above the Mean Opinion Score (MOS) Service
Level Agreement (SLA) requirement as defined in the SimpleCS2KCDRAdaptor.js Bulk Adaptor Design File.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > User Experience > Voice Quality > CDR/IPDR > Nortel CS2K >
Location
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Zone
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Softswitch Device
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Media Gateway
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Extension
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Type of Call
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Path
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Termination Cause
AboveMOSpercentage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Class 5 CDR > CDR Customer Profile
Type
Import
Description
This formula indicates that the BCT failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfBct
acPerfBctRequests
Type
Import
Description
This formula calculates the total number of BCT requests.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfBct
Type
Import
Description
This formula indicates that the conference failed to add due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfConf
Type
Import
Description
This formula calculates the conference(s) failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
acPerfConfRequests
Type
Import
Description
This formula calculates the total number of conference requests.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR Cont Digit Collect failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfIvr
Type
Import
Description
This formula calculates the total number of IVR Play Collect failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR Play Collect failed due to prov mismatch.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR Play Collect Requests.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR Play failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR play failed due to prov mismatch.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of IVR Play Requests.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of RTP failed due to lack of resources.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfRtp
Type
Import
Description
This formula calculates the total number of RTP receiver lost packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfRtp
Type
Import
Description
This formula calculates the total number of system packet endpoints currently in use.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfSystem
acPerfTtRequests
Type
Import
Description
This formula calculates the total number of TT requests.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > acPerfTt
ActiveConnections
Type
Import
Description
This formula calculates the total number of currently active connections.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > CICM Mgr
Type
Import
Description
This formula calculates the total number of active Ivr MP Connections.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > StreamSource
ActiveSessions
Type
Import
Description
This formula calculates the total number of currently active sessions.
Syntax
#Bulk Metric
None.
Formula Editor Path
Alignment Errors
Type
Import
Description
This formula calculates the total number of memory alignment errors.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > RAS Port
Type
Import
Description
This formula calculates the total number of allocated audio buffers.
Syntax
#Bulk Metric
None.
Formula Editor Path
ANNFailureRatio
Type
Import
Description
This formula provides the failure percentage for an annoncement server during the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
ANNocc
Type
Import
Description
This function provides percentage occupancy for the announcement port for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
AUXCP
Type
Import
Description
This formula provides an XA system auxiliary call processing class.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Softswitch Platform > Class 5 Softswitch > Device
AverageHoldingTime
Type
Import
Description
This formula provides the average time that calls are put on hold during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of average inbound bandwidth utilization.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > Interface
AverageLossRate
Type
Import
Description
This formula calculates the average audio loss rate.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AverageLossRate
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the average outbound bandwidth utilization.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the average percentage of CPU utilization for all Shelf Cards processing.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > Device
Type
Import
Description
This formula calculates the average percentage of CPU utilization of the on-board processor for this VSP Card.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > VSP Processor Card
Type
Import
Description
This formula calculates the average percentage of CPU utilization of the on-board processor for VSP Cards.
Syntax
#Bulk Metric
None.
Formula Editor Path
BHHCA
Type
Import
Description
This formula provides the total call attempts based on the half-call model that occurred during the observed
period.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Softswitch Platform > Class 5 Softswitch > GWC
Type
Import
Description
This formula calculates the total number of Buffer overruns (nb).
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the total number of call attempts made during the peak call hour.
Syntax
#Bulk Metric
None.
Formula Editor Path
Bytes Received
Type
Import
Description
This formula calculates the total number of bytes received.
Syntax
#Bulk Metric
None.
Formula Editor Path
Bytes Transmitted
Type
Import
Description
This formula calculates the total number of bytes transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of streamed bytes processed per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
bytesRxedPerSec
Type
Import
Description
This formula calculates the total number of bytes received per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > SAM21 > voip
bytesSentPerSec
Type
Import
Description
This formula calculates the total number of bytes sent per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of bytes streamed per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the percentage of CPU utilization for the call agent.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the percentage of memory utilization for the call agent.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the successful call completion ratio for end office as a percentage.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the successful call completion ratio for a class 4 tandem switch as a percentage.
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
This formula calculates the total length of a call in seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallDuration
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
CallsReleasedBySST
Type
Import
Description
This formula calculates the number of calls released by the SST, also known as mid-call failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > SessionServer
Type
Import
Description
This formula calculates the total number of calls for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
CardUtilAvg
Type
Import
Description
This formula defines the business of the processing component of the Control Processor card. This is reported
as average percentage of CPU utilization of the processing.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > Card
CCR
Type
Import
Description
This formula provides the percentage of total calls completed for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
CDR Extension Call Duration (CME)
Type
CME
Description
This formula calculates the call duration measured in seconds.
Syntax
^(duration/60)
Formula Input
Input: duration
Source: CallDuration (Formula)
None.
Formula Editor Path
AP > Specific > CME > VOIP > Softswitch
Type
CME
Description
This formula calculates the percentage of successful calls for a CDR extension.
Syntax
(successful + unsuccessful ) = 0 ifTrue: [^nil].
^(100 * ( successful / ( successful + unsuccessful ) ) )
Formula Input
Input: successful
Source: SuccessfulCall (Formula)
Input: unsuccessful
Source: UnsuccessfulCall (Formula)
None.
Formula Editor Path
Type
CME
Description
This formula calculates the total minutes of use for a particular device.
Syntax
^(duration/60)
Formula Input
Input: duration
Source: CallDuration (Formula)
None.
Formula Editor Path
Type
CME
Description
This formula calculates the total number of successful calls for a particular softswitch.
Syntax
(successful+unsuccessful) = 0 ifTrue: [^nil].
^(100*(successful/(successful+unsuccessful)))
Formula Input
Input: successful
Source: SuccessfulCall (Formula)
Input: unsuccessful
Source: UnsuccessfulCall (Formula)
None.
Formula Editor Path
cellDropCount
Type
Import
Description
This formula calculates the total number of cells dropped.
Syntax
#Bulk Metric
None.
Formula Editor Path
CongestedSeconds
Type
Import
Description
This formula calculates the total number of congestion Seconds. This is defined as the total number of seconds
during which media connection requests were rejected because the card is busy.
Syntax
#Bulk Metric
None.
Formula Editor Path
CongestedSeconds
Type
Import
Description
This formula calculates the total number of congestion Seconds. This is defined as the number of seconds during
which media connection requests were rejected because the card is busy.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > VSP Call Signaling
Connection Failures
Type
Import
Description
This formula calculates the total number of connection failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > TCP
Connections Active
Type
Import
Description
This formula calculates the current number of active connections.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > TCP
Type
Import
Description
This formula calculates the total number of context switches per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > System
Type
Import
Description
This formula calculates the percentage of CPU in use for call processing.
Syntax
#Bulk Metric
None.
Formula Editor Path
CRC Errors
Type
Import
Description
This formula calculates the total number of CRC Errors.
Syntax
#Bulk Metric
None.
Formula Editor Path
CS2K Grade of Service CME
Type
CME
Description
This formula calculates the grade of Service score, for example, the number of calls out of 1000 which may fail
due to network conditions.
Syntax
( total_calls ) = 0 ifTrue: [^100].
^( ( network_blocked * 1000 ) / total_calls )
Formula Input
Input: network_blocked
Source: UnsuccessfulCallNetwork (Formula)
Input: total_calls
Source: TotalCall (Formula)
None.
Formula Editor Path
Delay
Type
Import
Description
This formula provides the average packet delay during calls for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula provides metrics for call completion that is classified as dropped as opposed to having cleared
normally.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates if the call completion is classified as dropped rather than cleared normally.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates that the call completion is classified as dropped rather than cleared normally.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates that the call completion is classified as dropped rather than cleared with a normal call
clearing code.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates that the call attempt was dropped abnormally.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates that the call made was dropped abnormally.
Syntax
#Bulk Metric
None.
Formula Editor Path
DropCall
Type
Import
Description
This formula indicates if the call was dropped abnormally.
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
This formula calculates the Volume loss observed in audio echo packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
EchoReturnLoss
Type
Import
Description
This formula calculates the volume loss observed in audio echo packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EchoReturnLoss
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
This formula calculates the delay observed for a particular end device.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
EndSystemDelay
Type
Import
Description
This formula calculates the observed delay that was created by the end device.
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
EndSystemDelay
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ENGCAP
Type
Import
Description
This formula provides the total number of call attempts made during the peak call hour divided by BRISC (bi-
processor reduced instructionset computer) capacity.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of exception Dispatches per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
ExternalCall
Type
Import
Description
This formula calculates the total number of calls made outside of switch fabric or call manager.
Syntax
#Bulk Metric
None.
Formula Editor Path
ExternalCall
Type
Import
Description
This formula calculates the total number of calls that originated from an external source.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formulas gives the total number of external provider connections.
Syntax
#Bulk Metric
None.
Formula Editor Path
Failovers
Type
Import
Description
This formula calculates the total number of Failover procedures. This is defined as the number of times a Media
Gateway card performs failover procedures and attempts contact with another controller.
Syntax
#Bulk Metric
None.
Formula Editor Path
Failovers
Type
Import
Description
This formula calculates the total number of Failover procedures. This is defined as the number of times that a
Media Gateway card performs a failover procedure and attempts contact with another controller.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Far End Remote (FER) Cumulative Concealment Ratio (CCR) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Far End Remote (FER) Mean Hold Time (MHT) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Far End Remote (FER) Mean Talk Time (MTT) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Far End Remote (FER) server Network Effective Ratio (NER) for the SST network.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Far End Remote (FER) server Network Effective Ratio (NER) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of file control bytes per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of File control operations per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of file data operations per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
H248Retransmission
Type
Import
Description
This formula calculates the total number of H248 Retransmissions.
Syntax
#Bulk Metric
None.
Formula Editor Path
H248Retransmission
Type
Import
Description
This formula calculates the total number of H248 Retransmissions.
Syntax
#Bulk Metric
None.
Formula Editor Path
HalfCallAttempts
Type
Import
Description
This formula calculates the total number of half call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
HIOP
Type
Import
Description
This formula provides the percentage of I/O utilization for the Nortel Extended Core (XA-Core) system.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total number of storage allocation failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > Session Server
hrStorageUsed
Type
Import
Description
This formula calculates the amount of storage used.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > Session Server
hrSystemUptime
Type
Import
Description
This function provides the percentage of system uptime for the time period observed, based upon the
hrSystemUptime metric.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > Session Server > hrSystem
hrSystemUptime
Type
Import
Description
This formula calculates the percentage of system uptime for the time period specified, based on the
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > AMS > hrSystem
hrSystemUptime
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > CICM Mgr > hrSystem
hrSystemUptime
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > MS2000 > hrSystem
hrSystemUptime
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > SAM21 > hrSystem
hrSystemUptime
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > SSL > hrSystem
In_2xx
Type
Import
Description
This formula provides the total inbound 200-range call codes for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > IEMS > SSL
In_3xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
In_4xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
In_5xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
In_6xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
In_Unknown
Type
Import
Description
This formula provides the total inbound call codes in the unknown range for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundByte
Type
Import
Description
This formula calculates the inbound octet count.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundByte
Type
Import
Description
This formula calculates the total number of inbound octets.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundByte
Type
Import
Description
This formula calculates the total number of inbound octets.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundByte
Type
Import
Description
This formula calculates the total number of bytes sent inbound during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Inbound Post-Dial Delay for SIP invite messages. This formula measures the amount
of time that elapses from the moment that the invite is issued until the moment that a 18x or 2xx message is
received from the far end.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundPacket
Type
Import
Description
This formula calculates the total number of packets received.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundPacket
Type
Import
Description
This formula calculates the total number of inbound IP packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundPacket
Type
Import
Description
This formula calculates the total number of inbound packets sent during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundPacket
Type
Import
Description
This formula calculates the total number of inbound packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
InboundPacketRate
Type
Import
Description
This formula calculates the rate of incoming packets per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
InBYE
Type
Import
Description
This formula provides the number of inbound BYE messages for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingAnswerSeizureRatio%
Type
Import
Description
This formula calculates the ratio of inbound calls that were answered successfully to inbound calls that seized.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Softswitch Platform > Class 5 Softswitch > Trunk
IncomingCall
Type
Import
Description
This formula calculates the total number of inbound call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingCall
Type
Import
Description
This formula calculates the total number of inbound calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingCall
Type
Import
Description
This formula calculates the total number of inbound calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingCall
Type
Import
Description
This formula calculates the total number of incoming calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingCallTrunkRoutingFailure
Type
Import
Description
This formula calculates the total number of calls that failed due to trunk routing problems.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingSuccessfulCalls%
Type
Import
Description
This formula calculates the percentage of inbound calls that completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingSuccessfulCalls
Type
Import
Description
This formula calculates the total number of inbound calls that completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
IncomingTrunkToLineCallAttempts
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
InternalCall
Type
Import
Description
This formula calculates the total number of calls made that originated and terminated by the softswitch or device.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternalCall
Type
Import
Description
This formula calculates the total number of calls made within switch fabric or call manager.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternalCall
Type
Import
Description
This formula calculates the total number of internal calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternalCall
Type
Import
Description
This formula calculates the total number of internal calls made via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternalCall
Type
Import
Description
This formula calculates the total number of calls originated and terminated within the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of calls made across national boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of calls made across international boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of calls placed across national boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of international calls made via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of calls made outside of national boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
InternationalCall
Type
Import
Description
This formula calculates the total number of calls placed across international boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
IntraSwitchLineToLineCallAttempts
Type
Import
Description
This formula calculates the total number of line-to-line call attempts within an individual switch.
Syntax
#Bulk Metric
None.
Formula Editor Path
Invite200
Type
Import
Description
This formula provides the total number of 200-range invite messages for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
JitterAverage
Type
Import
Description
This formula calculates the average jitter measured in milliseconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
Jitter
Type
Import
Description
This formula provides the average jitter during calls for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
LineCodeViolations
Type
Import
Description
This formula calculates the total number of line code violations.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Signaling Gateway > Link
LineErroredSeconds
Type
Import
Description
This formula calculates the total number of line errored seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
LineLossOfSignalSeconds
Type
Import
Description
This formula calculates the total duration in seconds that the link was observed to have loss of signal (LOS).
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the total Line Severely Errored seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
LinkFailureAllReasons
Type
Import
Description
This formula calculates the total number of link failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
LinkMSUreceived
Type
Import
Description
This formula calculates the total MSUs received by this device or group of devices.
Syntax
#Bulk Metric
None.
Formula Editor Path
LinkMSUtransmitted
Type
Import
Description
This formula calculates the total MSU messages transmitted on this link.
Syntax
#Bulk Metric
None.
Formula Editor Path
LinksetInactivityDuration
Type
Import
Description
This formula calculates the total duration of linkset inactivity.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Signaling Gateway > Linkset
Type
Import
Description
This formula calculates the duration of Layer 1 link unavailability.
Syntax
#Bulk Metric
None.
Formula Editor Path
LinkUtilization
Type
Import
Description
This formula calculates the link utilization measurement (in percent).
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
This formula calculates the Listening quality Mean Opinion Score measured on a 1.0 to 5.0 scale.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
ListeningQualityMOS
Type
Import
Description
This formula calculates the listening quality Mean Opinion Score measured on the 1.0 to 5.0 scale.
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ListeningQualityMOS
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
LMBUtil
Type
Import
Description
This formula calculates the average percentage of local message blocks in use.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > Card
Type
Import
Description
This formula calculates the Local Gateway Controller (GWC) Cumulative Concealment Ratio (CCR) for the SST
node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Local Gateway Controller (GWC) Mean Hold Time (MHT) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Local Gateway Controller (GWC) Mean Talk Time (MTT) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Local Gateway Controller (GWC) Network Effective Ratio (NER) for the SST
network.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Local Gateway Controller (GWC) Network Effective Ratio (NER) for the SST node.
Syntax
#Bulk Metric
None.
Formula Editor Path
LoggedInUsers
Type
Import
Description
This formula calculates the total number of users logged into the system.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the number of dropped calls that occurred during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
LostPacket
Type
Import
Description
This formula indicates that the packet was never received.
Syntax
#Bulk Metric
None.
Formula Editor Path
LostPacket
Type
Import
Description
This formula indicates the packet was not received.
Syntax
#Bulk Metric
None.
Formula Editor Path
LostPacket
Type
Import
Description
This formula calculates the total number of packets lost during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
LostPacket
Type
Import
Description
This formula indicates that packet was not received.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the maximum CPU occupancy as a percentage value for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the maximum amount of ram utilization for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the maximum amount of swap space utilized for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
MaxTemp
Type
Import
Description
This formula indicates the maximum temperature in degrees Celsius of the Fabric card.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Media Gateway > Fabric Card
Type
Import
Description
This formula provides the median CPU occupancy as a percentage value for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the median ram utilization for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the median amount of swap space utilized for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the percentage of total calls that fail mid-call for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the minimum CPU occupancy as a percentage value for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the minimum ram utilization for the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the minimum amount of swap space utilized for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula calculates the total number of calls made from a mobile device.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula calculates the total number of calls made from a mobile phone.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula indicates if call was made by a mobile device.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula indicates the termination cause for a call made from a mobile device.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula calculates the total number of mobile calls made via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula provides metrics for CDR type of call.
Syntax
#Bulk Metric
None.
Formula Editor Path
MobileCall
Type
Import
Description
This formula calculates the total number of calls made from a mobile device.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula indicates that call was made within country boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula calculates the total number of calls made within national call boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula indicates if a call made was within the boundaries of one country.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula calculates the total number of national calls made via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula calculates the total number of calls made within national boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
NationalCall
Type
Import
Description
This formula provides metrics for calls when the placed call was within national boundaries.
Syntax
#Bulk Metric
None.
Formula Editor Path
NetworkCallFailure
Type
Import
Description
This formula calculates the total number of IP Network Call Failures. Call failures are defined as the number of
connections lost due the network failures in the IP Core.
Syntax
#Bulk Metric
None.
Formula Editor Path
NetworkCallFailure
Type
Import
Description
This formula calculates the total number of IP Network Call Failures. IP Network Call Failures are defined as the
number of connections lost due to network failures in the IP Core.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the network effectiveness ratio (NER) for the observed period. The NER is calculated as
the percentage of successful allocation for a voice circuit. This value is an indicator of congestion on a network,
where 100% indicates the optimal condition.
Syntax
#Bulk Metric
None.
Formula Editor Path
Nodal NER (CME)
Type
CME
Description
This formula provides the nodal NER (network effectiveness ration) for the period observed. The nodal NER is
the total number of 200-range invite codes divided by the sum of inbound and outbound BYE messages, or
invites / (inbound BYE + outbound BYE).
Syntax
^( invite_two_hundred / ( in_bye + out_bye ) )
Formula Input
Input: in_bye
Source: InBYE (Formula)
Input: invite_two_hundred
Source: Invite200 (Formula)
Input: out_bye
Source: OutBYE (Formula)
None.
Formula Editor Path
NormalCall Termination
Type
Import
Description
This formula calculates the total number of call termination code that matched a normal call completion code.
Syntax
#Bulk Metric
None.
Formula Editor Path
NormalCallTermination
Type
Import
Description
This formula indicates if the call termination code is considered normal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula indicates that the call termination cause code is considered normal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula indicates that the call termination cause code is deemed normal call clearing.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula defines the normal call clearing termination cause.
Syntax
#Bulk Metric
None.
Formula Editor Path
OffNetCall
Type
Import
Description
This formula indicates that the call extended beyond the range of the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
OffNetCall
Type
Import
Description
This formula indicates that the call was placed outside of carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
OffNetCall
Type
Import
Description
This formula calculates the CDR Customer Profile for an incoming call.
Syntax
#Bulk Metric
None.
Formula Editor Path
OffNetCall
Type
Import
Description
This formula indicates an incoming call via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
OffNetCall
Type
Import
Description
This formula identifies a call placed outside of the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
OnNetCall
Type
Import
Description
This formula indicates that the call origin and destination were within the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
OnNetCall
Type
Import
Description
This formula indicates that a call was place within the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
OnNetCall
Type
Import
Description
This formula provides information for OnNet calls in the CDR Customer Profile.
Syntax
#Bulk Metric
None.
Formula Editor Path
OnNetCall
Type
Import
Description
This formula provides information on incoming OnNet calls via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
OnNetCall
Type
Import
Description
This formula provides information on calls placed within the carrier network.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the number of calls that failed before the connection completed during the observed
period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the number of calls that failed due to a network-side error during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
OriginatingFailures
Type
Import
Description
This formula provides the number of calls that failed due to an originating-side error during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides the number of call attempts originating with session server lines (SSL) during the observed
period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_2xx
Type
Import
Description
This formula provides the total outbound 200-range call codes for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_3xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_4xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_5xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_6xx
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Out_Unknown
Type
Import
Description
This formula provides the total outbound call codes in the unknown range for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundByte
Type
Import
Description
This formula provides information on the outbound octet count.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundByte
Type
Import
Description
This formula provides information on outbound octets.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundByte
Type
Import
Description
This formula provides information on total outbound octets.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundByte
Type
Import
Description
This formula provides information on the total number of bytes sent outbound during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula calculates the Outbound Post-Dial Delay for SIP invite messages. This formula measures the
amount of time that elapses from the moment that the invite is issued until the moment that a 18x or 2xx message
is received from the far end.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundPacket
Type
Import
Description
This formula provides information on the total number of packets transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundPacket
Type
Import
Description
This formula provides information on the total number of outbound IP packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundPacket
Type
Import
Description
This formula provides information on the total number of outbound packets sent during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundPacket
Type
Import
Description
This formula provides information on the total number of outbound packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutboundPacketRate
Type
Import
Description
This formula provides information on the rate of outbound packets per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutBYE
Type
Import
Description
This formula provides the number of outbound BYE messages for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingAnswerSeizureRatio%
Type
Import
Description
This formula provides information on the ratio of outbound calls that were answered successfully rather than
seized.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCall
Type
Import
Description
This formula provides information on outgoing call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCall
Type
Import
Description
This formula provides information on outbound calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCall
Type
Import
Description
This formula provides information on outbound calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCall
Type
Import
Description
This formula provides information on outgoing calls via the CDR Media Gateway.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCall
Type
Import
Description
This formula provides information on outbound call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingCallTrunkRoutingFailure
Type
Import
Description
This formula provides information on outbound call that failed due to trunk routing problem.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingLineToTrunkCallAttempts
Type
Import
Description
This formula provides information on outbound call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the percentage of outbound call attempts that were successfully
completed.
Syntax
#Bulk Metric
None.
Formula Editor Path
OutgoingSuccessfulCalls
Type
Import
Description
This formula provides information on the number of successful outbound calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
OverloadCmdRejected
Type
Import
Description
This formula provides information on the total Number of MGC Commands Rejected due to Overload of the
Input Message Buffer.
Syntax
#Bulk Metric
None.
Formula Editor Path
OverloadCmdRejected
Type
Import
Description
This formula provides information on the total Number of MGC Commands Rejected due to Overload of the
Input Message Buffer.
Syntax
#Bulk Metric
None.
Formula Editor Path
oversizedPDUCount
Type
Import
Description
This formula provides information on the number of oversized PDU.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the average latency observed on inbound media streams.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the average delta in latency between media stream packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on average delta in media packet latency observed during VoIP conversations.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the average variation in latency between media stream packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
PacketLatency
Type
Import
Description
This formula provides information on the length of time between received RTP media packets. This is defined
as calls where packet latency is greater than 150 milliseconds and may have a noticeable impact on the caller and
callee.
Syntax
#Bulk Metric
None.
Formula Editor Path
PacketLatency
Type
Import
Description
This formula provides information on the average delay between media stream packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
PacketLatency
Type
Import
Description
This formula provides information on the average latency measured in milliseconds for VoIP calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
PacketLatency
Type
Import
Description
This formula provides information on the average length of time between media stream packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
PacketLoss
Type
Import
Description
This formula provides the percentage of packets lost during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on pending Ivr MP Connections.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on Percent Compression Out.
Syntax
#Bulk Metric
None.
Formula Editor Path
PercentageCpuUsed
Type
Import
Description
This formula provides information on the percentage of CPU utilized.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the percentage of memory used.
Syntax
#Bulk Metric
None.
Formula Editor Path
Processes
Type
Import
Description
This formula provides information on the number of processes.
Syntax
#Bulk Metric
None.
Formula Editor Path
ProcessorElement
Type
Import
Description
This formula provides the percentage of CPU utilization for the Nortel Extended Core (XA-Core) system.
Syntax
#Bulk Metric
None.
Formula Editor Path
Processor
Type
Import
Description
This formula provides the percentage of CPU utilization measured by medianCpuOccupancyValue.
Syntax
#Bulk Metric
None.
Formula Editor Path
Processor
Type
Import
Description
This formula provides the percentage of processor utilization for the gateway controller device during the period
observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
Processor
Type
Import
Description
This formula calculates the current CPU occupancy.
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
This formula provides information on the average time in milliseconds for packet round trips.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
RoundTripAverage
Type
Import
Description
This formula calculates the average time in milliseconds for packet round trips.
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RoundTripAverage
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
RSTReceived
Type
Import
Description
This formula provides information on the RST messages received.
Syntax
#Bulk Metric
None.
Formula Editor Path
RSTTransmitted
Type
Import
Description
This formula provides information on the number of RST messages transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
rxedTimeoutCount
Type
Import
Description
This formula provides information on the number of timeouts received.
Syntax
#Bulk Metric
None.
Formula Editor Path
SCAI
Type
Import
Description
This function provides information on switch-to-computer application interface messaging (SCAI).
Syntax
#Bulk Metric
None.
Formula Editor Path
ServiceFailureRate
Type
Import
Description
This formula provides the service failure ratio for the period observed. The service failure ratio is measured as
the percentage of call failures due to a busy trunk.
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
This formula provides information on the length of call under 2 seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
This formula provides information on the length of a call under 2 seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
This formula provides information on the length of a call under 2 seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
This formula provides information on the length of calls under 2 seconds.
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
ShortCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
SimultaneousCalls
Type
Import
Description
This formula calculates the total number of simultaneous calls initiated.
Syntax
#Bulk Metric
None.
Formula Editor Path
SparingBandwidth
Type
Import
Description
Sparing bandwidth measured in dirty pages
Syntax
#Bulk Metric
None.
Formula Editor Path
SSLOverload
Type
Import
Description
This formula provides the total number of server session lines (SSL) 503 messages that occurred during the
observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on calls completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on calls set up and completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on calls was set up and completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on if call completion was successful.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on call attempts which completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on calls completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
SuccessfulCall
Type
Import
Description
This formula provides information on successful call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
System Calls/sec
Type
Import
Description
This formula provides information on the number of system calls per second.
Syntax
#Bulk Metric
None.
Formula Editor Path
TDMCallFailures
Type
Import
Description
This formula provides information on the total Number of TDM Network Call Failures. This is defined as the
number of connections lost due to failure of a TDM Port.
Syntax
#Bulk Metric
None.
Formula Editor Path
TerminatingFailures
Type
Import
Description
This formula provides the number of calls terminating with failure codes during the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
Threads
Type
Import
Description
This formula provides information on the number of currently running threads.
Syntax
#Bulk Metric
None.
Formula Editor Path
Timeout Errors
Type
Import
Description
This formula provides information on RAS port timeout errors.
Syntax
#Bulk Metric
None.
Formula Editor Path
Total Errors
Type
Import
Description
This formula provides information on total RAS port errors.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalActiveCalls
Type
Import
Description
This formula provides information on the Total Number of Active Calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalActive
Type
Import
Description
This formula provides the total active call codes for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
totalBytesRxed
Type
Import
Description
This formula provides information on the total bytes received.
Syntax
#Bulk Metric
None.
Formula Editor Path
totalBytesSent
Type
Import
Description
This formula provides information on the total bytes sent.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the total number of call bid attempts for device or group.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
This formula provides information on the total number of calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
This formula provides information on the total number of call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCall
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalCallTrunkRoutingFailure%
Type
Import
Description
This formula provides information on the percentage of total calls that failed due to trunk routing problems.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalConnectionOrientedIPDistributionViolations
Type
Import
Description
This formula provides information on the total call setup failures due to IP distribution violations.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Signaling Gateway > Device
TotalConnectionOrientedMessagesHandled
Type
Import
Description
This formula provides information on the total setup messages handled.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalConnectionOrientedMessagesRoutingFailure
Type
Import
Description
This formula provides information on the total call setup routing failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides information on the total number of files transcoded.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalGTTAlternateRoutingOnCongestion
Type
Import
Description
This formula provides information on the total GTT performed which used alternate route paths due to primary
path congestion.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalGTTHopCounterViolation
Type
Import
Description
This formula provides information on the total GTT Hop Counter Violations. This is defined as packets that may
have traversed too many gateways before reaching their destination.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalGTTNoTranslationForAddress
Type
Import
Description
This formula provides information on on the total GTT failed due to lack of translation for specified address.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalGTTPerformed
Type
Import
Description
This formula provides information on the total Global Title Translations performed.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalGTTTranslationTypeNotFound
Type
Import
Description
This formula provides information on the total GTT translation type not found.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalICMPPackets
Type
Import
Description
This formula provides information on the total Number of ICMP Packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalIn
Type
Import
Description
This formula provides total number of inbound call codes for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMessagesErrors
Type
Import
Description
This formula provides metrics for the total number of error messages observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMessagesHandled
Type
Import
Description
This formula provides metrics for the total number of call messages handled.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMessagesIncompatibility
Type
Import
Description
This formula provides metrics for the total number of messages received that are considered incompatible.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMessagesTooLargeForSegmentation
Type
Import
Description
This formula provides metrics for the total number of messages too large for segmentation.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMinutesOfUse
Type
Import
Description
This formula provides metrics for the total number of minutes of Use or Total Call Duration.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMinutesOfUse
Type
Import
Description
This formula provides metrics for the total number of minutes of Use, that is. the Total call duration in minutes.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalMSUDiscardedSCCPMessages
Type
Import
Description
This formula provides metrics for the total number of SCCP call signaling messages discarded.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of discarded IP packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of packet exception errors.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalNumberOfTCPPackets
Type
Import
Description
This formula provides metrics for the total number of TCP packets received and transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalNumberOfUDPPackets
Type
Import
Description
This formula provides metrics for the total number of UDP packets received and transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalOut
Type
Import
Description
This formula provides the total outbound call codes for the period observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalOutOfSequenceSCCPMessages
Type
Import
Description
This formula provides metrics for the total number of of SCCP call signaling messages that arrived out of
sequence.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalPackets
Type
Import
Description
This formula provides metrics for the total number of Inbound and Outbound Packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
totalRam
Type
Import
Description
This formula provides the total system memory.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalReassemblyBufferUnavailable
Type
Import
Description
This formula provides metrics for the total message reassembly attempts that failed due to unavability of buffer
space.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of message reassembly attempts that failed.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalReassemblyTimerExpired
Type
Import
Description
This formula provides metrics for the total number of failed reassembly attempts due to timer expiration.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of routeset congestion messages observed.
Syntax
#Bulk Metric
None.
Formula Editor Path
AP > Specific > Bulk > Carrier VOIP > Infrastructure > Signaling Gateway > Routeset
Type
Import
Description
This formula provides information on the total number of times routeset was manually busied.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of seconds routeset was unavailable.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of times routeset was unavailable.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSCCPRoutingFailure
Type
Import
Description
This formula provides metrics for the total number of SCCP call setup attempts that failed due to the inability to
route them.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of segmentation failures.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSoftswitchCallAttempts
Type
Import
Description
This formula provides metrics for the total number of attempted calls made through this softswitch or group of
softswitch devices.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSoftswitchSuccessfulCalls%
Type
Import
Description
This formula provides metrics for the percentage of total calls made that completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSoftswitchSuccessfulCalls
Type
Import
Description
This formula provides metrics for the total number of calls made through this softswitch or group of softswitches
that completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSoftswitchUnsuccessfulCalls%
Type
Import
Description
This formula provides metrics for the percentage of total calls made that terminated unsuccessfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalSoftswitchUnsuccessfulCalls
Type
Import
Description
This formula provides metrics for the total number of attempted calls through this softswitch or group of
softswitch devices that terminated unsuccessfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of successful Calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of successful Calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
totalSwap
Type
Import
Description
This formula provides the total amount of swap space configured for the device.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalTCPPackets
Type
Import
Description
This formula provides metrics for the total number of TCP Packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalTDMCallFails
Type
Import
Description
This formula provides metrics for calls failed on the TDM network.
Syntax
#Bulk Metric
None.
Formula Editor Path
TotalUDPPackets
Type
Import
Description
This formula provides metrics for the total number of UDP Packets.
Syntax
#Bulk Metric
None.
Formula Editor Path
TrafficBusyUse
Type
Import
Description
This formula provides the percentage of traffic throughput utilized during the observed period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Transactions
Type
Import
Description
This formula provides the total number of inbound and outbound SIP invites that occurred during the observed
period.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
The total number of messages received indicating that transfer requests are allowed and routing for destination is
available.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the total number of messages transmitted indicating that transfer requests are
allowed and routing for destination is available.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransferControlledTransmitted
Type
Import
Description
This formula provides metrics for transmitted Transfer Controlled messages.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransferProhibitedRoutingNotAvailableReceived
Type
Import
Description
This formula provides metrics for the total number of messages received indicating that transfer request is
prohibited due to unavailability of destination routing.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransferProhibitedRoutingNotAvailableTransmitted
Type
Import
Description
This formula provides metrics for the total number of messages transmitted that indicate that the transfer request
is prohibited due to unavailability of destination routing.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransferRestrictedReceived
Type
Import
Description
This formula provides metrics for the number of transfer restricted messages received.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransferRestrictedTransmitted
Type
Import
Description
This formula provides metrics for the total number of transfer restricted messages transmitted.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransitTrunkToTrunkCallAttempts
Type
Import
Description
This formula provides metrics for the total number of transit trunk to trunk call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
This formula provides metrics for the total number of media streams.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
TransmissionStreams
Type
Import
Description
This formula calculates the total number of media streams.
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TransmissionStreams
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
TrunkGOS
Type
Import
Description
This function provides the probability of a call being blocked or delayed on a particular network trunk.
Syntax
#Bulk Metric
None.
Formula Editor Path
TrunkOrCarrierBusy
Type
Import
Description
This formula provides the number of calls during the observed period that terminated with a carrier busy or trunk
busy condition.
Syntax
#Bulk Metric
None.
Formula Editor Path
TrunkOverflow
Type
Import
Description
This formula provides the metrics for when Trunk capacity is exceeded.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for the Amount of all MOS scores that fall under 3.7 in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
Type
Import
Description
This formula provides metrics for the amount of offnet calls that fell below MOS. 3.7
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
Type
Import
Description
This formula provides metrics for the amount of OnNet calls that fell below 3.7 in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
Location
UnderMOSLimit
Type
Import
Description
This formula calculates the number of all Mean Opinion Score (MOS) values that fall below the specified Service
Level Agreement (SLA) in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimit
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
This formula calculates the number of OffNet calls that fall below the specified Service Level Agreement (SLA)
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOffnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
This formula calculates the number of OnNet calls that fall below the specified Service Level Agreement (SLA)
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnderMOSLimitOnnet
Type
Import
Description
in quality.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Called numbers that returned a busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Dialed numbers that returned a busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Dialed numbers that returned a busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for called number that returned a busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for placed calls that returned busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for call attempts that returned a busy signal.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Called numbers that returned a busy status.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for all Dialed numbers that are invalid.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This is the formula that indicates that the dialed number is not valid.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Dialed numbers that are not valid.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics if the dialed number is an invalid one.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics if calls failed due to invalid dialed number or recipient address.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for call attempts that failed due to invalid callee number or address.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for calls that failed due to invalid dialed number.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics if call completion was unsuccessful.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics if the call was not set up and completed successfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics for unsuccessful calls.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics for calls whose completion was unsuccessful.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics for call attempts which completed unsuccessfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics for call that completed unsuccessfully.
Syntax
#Bulk Metric
None.
Formula Editor Path
UnsuccessfulCall
Type
Import
Description
This formula provides metrics for unsuccessful call attempts.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for call completion that was unsuccessful on the network leg of the call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Call completion that was unsuccessful on the network leg of the call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for calls terminated unsuccessfully on the network leg of the call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for calls that failed on the network leg of the call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for calls that failed due to network-related problem.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Called numbers that did not answer.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for called numbers that did not answer this call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for called numbers that did not answer this call.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for Dialed numbers that were not answered.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for call that were not answered.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for called numbers or addresses that were not answered.
Syntax
#Bulk Metric
None.
Formula Editor Path
Type
Import
Description
This formula provides metrics for calls that failed due to no answer received from dialed party.
Syntax
#Bulk Metric
None.
Formula Editor Path
NOTES
Appendix A: Configuration
This appendix explains how to configure the Nortel CS2000 Technology Pack and consists of the following
topics:
Overview
The Nortel CS2000 Technology Pack is a bulk (or UBA) technology pack. Bulk technology packs collect data
against non-SNMP devices, and rely on the Universal Bulk Adaptor (UBA) of the Netcool/Proviso DataChannel
to process the data. Prior to Netcool/Proviso 443, bulk packs could be very difficult to configure, and in many
cases required extensive Netcool/Proviso domain knowledge.
Netcool/Proviso 443 introduced a graphical user interface (GUI) to configure Netcool/Proviso UBA technology
packs on supported Netcool/Proviso platforms.
Before You Begin
Before configuring the Nortel CS2000 Technology Pack, ensure that you:
Have the following software and documentation for your version of Netcool/Proviso:
Release notes for the current technology pack release.
Netcool/Proviso Installation Guide.
Netcool/Proviso Upgrade Guide (if performing an upgrade).
Netcool/Proviso DataMart Configuration Guide.
Important: You will need to refer to this guide in order to create an inventory profile and initiate a discovery.
Access to the Netcool/Proviso DataMart server.
An X Window server on the DataMart server.
Topic Page
Overview 687
Before You Begin 687
Configure the Technology Pack 689
Other Tasks and Considerations 699
Note: (Pre-443 Netcool/Proviso) If there is no graphics card on the DataMart server, you can install the Xvfb
virtual frame buffer package to provide X Window services, as described in the Netcool/Proviso Installation
Guide.
Access to the SilverStream server.
Access to the DataChannel server.
Have completed the following tasks:
Reviewed the release notes for the current technology pack.
Important: Release notes contain important information you need to consider before installing a technology pack.
They also contain information on specific patches that need to be installed before you configure a technology pack.
Installed the current version of the Netcool/Proviso components, as described in the Netcool/Proviso
Installation Guide.
Installed the Nortel CS2000 Technology Pack.
Note: Installation instructions for a technology pack can be found in the Appendices of the Netcool/Proviso
Installation Guide (covers core and technology packs).
Upgrade instructions for a technology pack can be found in Chapter 3 of the Netcool/Proviso Upgrade Guide
(covers core and technology packs).
Configured at least one DataChannel.
Configured multiple UBA Bulk Collectors, based on the following Netcool/Proviso platforms:
443 and higher You already configured multiple UBA Bulk Collectors using the Topology Editor as
part of the technology pack installation. See the Netcool/Proviso Installation Guide for more information.
Pre-443 You should configure one UBA Bulk Collector for each of the following input sources as part
of the DataChannel installation. See the Netcool/Proviso Installation Guide for information on how to
configure a UBA Bulk Collector.
* Nortel CS2000 Performance The UBA application executing on this subchannel retrieves Bulk
input files generated by the Nortel CS2000 Performance device. The Bulk Adaptor Design File for the
Nortel CS2000 Performance device is called CS2KPERFAdaptor.js.
Note: The CS2KPERFAdaptor.js Bulk Adaptor Design File also handles Nortel GWC devices and Nortel
MS 20xx devices.
* Nortel CS2000 CDR device The UBA application executing on this subchannel retrieves Bulk input
files generated by the Nortel CS2000 CDR device. The Bulk Adaptor Design File for the Nortel CS2000
CDR device is called SimpleCS2KCDRAdaptor.js.
* Nortel CS2000 CDR Stray Handler The UBA application executing on this subchannel retrieves
stray Bulk input files generated by the Nortel CS2000 CDR device. The Bulk Adaptor Design File for
the Nortel CS2000 CDR device is called SimpleCS2KCDRAdaptor.js.
Note: The CS2K CDR Stray Handler must share the same collector alias as you defined for the Nortel
CS2000 CDR Device.
* Nortel Integrated Element Management System (IEMS) The UBA application executing on this
subchannel retrieves Bulk input files generated by the Nortel IEMS device. The Bulk Adaptor Design
File for the Nortel IEMS device is called IEMSPERFAdaptor.js.
* Nortel Passport Packet Voice Gateway (PVG) The UBA application executing on this subchannel
retrieves Bulk input files generated by the Nortel PVG device. The Bulk Adaptor Design Files for the
Nortel PVG device are called PVGAdaptor.js (for data that comes directly from the MDM) and
CPRAdaptor.js (for data that comes from the IEMS).
* Nortel Session Server Lines (SSL) The UBA application executing on this subchannel retrieves Bulk
input files generated by the Nortel SSL device. The Bulk Adaptor Design File for the Nortel SSL device
is called SSLAdaptor.js.
* Nortel Session Server Trunk (SST) The UBA application executing on this subchannel retrieves
Bulk input files generated by the Nortel SST device. The Bulk Adaptor Design File for the Nortel SST
device is called CPRAdaptor.js.
* Nortel Universal Signaling Point (USP) The UBA application executing on this subchannel retrieves
Bulk input files generated by the Nortel USP device. The Bulk Adaptor Design File for the Nortel USP
device is called USPPERFAdaptor.js.
Note: Both Nortel Passport Packet Voice Gateway (PVG) and Nortel Session Server Trunk (SST) provide
data in the Common Performance Reporting (CPR) format. CPRAdaptor.js specifies a Bulk Adaptor Design
File for the SST and also specifies a Bulk Adaptor Design File for the PVG data that comes from the IEMS.
You must create one instance of this adaptor for each input file stream.
Configure the Technology Pack
To configure the Nortel CS2000 Technology Pack, follow these steps:
Important: Localization is now done automatically during installation of the technology pack and requires no
manual steps to configure.
1. Load the DataMart environment.
To load the shell with the DataMart environment, follow these steps:
1-a. Log in to the DataMart server as pvuser.
1-b. Change your working directory to the DataMart home directory (/opt/datamart, by default), using
the following command:
$ cd /opt/datamart
1-c. Load the shell with the DataMart environment, by sourcing the dataMart.env file, as follows:
$ . /opt/datamart/dataMart.env
Note: After you load the DataMart environment into the shell, the PVMHOME variable is set to the
DataMart home directory, /opt/datamart by default. These instructions assume that this variable has been set.
2. Copy technology-specific files from the DataMart server to the DataChannel server.
Technology-specific files are used to associate a UBA technology pack with a specific instance of the UBA.
Note: While it is possible to install DataMart and DataChannel on the same server, in a typical installation
these modules are installed on separate servers. If this is the case, use ftp to copy the technology-specific files.
Otherwise, if DataMart and DataChannel are on the same server, use the cp command to copy the files to the
appropriate DataChannel directory.
To copy technology-specific files to the DataChannel server, follow these steps:
2-a. Log in to the Netcool/Proviso DataChannel server by entering the username and password that you
specified when installing and configuring a DataChannel. The default username and password are
pvuser and PV, respectively.
2-b. Change your working directory to the DATA_CHANNEL_HOME/scripts directory by entering the
following command, replacing DATA_CHANNEL_HOME with the DataChannel home directory
(/opt/datachannel, by default):
$ cd DATA_CHANNEL_HOME/scripts
2-c. Using the ftp utility in text mode, log into the DataMart server using the appropriate username and
password (pvuser and PV, by default).
2-d. Using the cd sub-command, change your working directory to the
$PVMHOME/APFiles/nortel_cs2000/datachannel/scripts directory.
2-e. Using the get sub-command, copy the Bulk Adaptor Design Files (*.js), scripts (if any), and other
files (if any) from the DataMart server to the DataChannel server.
2-f. (Pre-443 Netcool/Proviso only) Copy the nortel_cs2000_sample_dc.cfg template file as
follows:
* Using the cd sub-command, change your working directory to the
$PVMHOME/APFiles/nortel_cs2000/datachannel/conf directory.
* Using the get sub-command, copy the nortel_cs2000_sample_dc.cfg template file from
the DataMart server to the DataChannel server.
2-g. Exit the ftp utility by entering the bye sub-command.
2-h. Verify that the technology-specific files now reside in the target directory as follows:
* (Netcool/Proviso 443 and higher) Verify that the Bulk Adaptor Design Files (*.js), scripts (if any),
other files (if any) now reside in the DATA_CHANNEL_HOME/scripts directory.
* (Pre-443 Netcool/Proviso) Verify that the Bulk Adaptor Design Files (*.js), scripts (if any), other
files (if any), and nortel_cs2000_sample_dc.cfg template file now reside in the
DATA_CHANNEL_HOME/scripts directory.
3. Activate data collection requests.
During installation of the technology pack, all predefined data collection requests are promoted to the
database and set to inactive (that is, idle displays in the Active column of the Netcool/Proviso DataMart
Request Editor). You need to activate these predefined data collection requests using the Request Editor.
To set data collection requests to active, follow these steps:
3-a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the
DataMart server.
3-b. Invoke the DataMart GUI by entering the following command and pressing Enter:
pvm
3-c. Click the Configuration tab, then click Request Editor to open the Request Editor.
3-d. Click the Collection tab.
3-e. Click Refresh.
The predefined data collection requests are loaded into the Request Editor from the database.
3-f. Click the Inactive button in the Filter group box to display only idle requests.
3-g. In the Sub-Element Groups pane, select all idle data collection requests in the following group or
groups:
Root->Sub-Element Collect->Carrier VOIPInfrastructure
Root->Sub-Element Collect->Carrier VOIPUser Experience
3-h. Click the Active box under Details. The Request Editor toggles the idle setting for these data collection
requests from idle to active in the Active column.
3-i. Click Save.
Optionally, before making the selection, click the Inactive button in the Filter group box to display only
idle requests.
3-j. Click the Active box under Details. The Request Editor toggles the idle setting for these data collection
3-k. Click Save.
4. Set the Element Name Source for the Nortel PVG device in the PVGConfig.js file.
Before the Nortel CS2000 Technology Pack can create the Element name for the Nortel PVG device, the
source for the element name must be identified in the PVGConfig.js file.
To configure the PVGConfig.js design file, follow these steps:
4-a. On the DataChannel server, change your working directory to the
DATA_CHANNEL_HOME/scripts directory by entering the following command, replacing
DATA_CHANNEL_HOME with the DataChannel home directory (/opt/datachannel, by default):
cd DATA_CHANNEL_HOME/scripts
4-b. Make a backup copy of the PVGConfig.js design file, by entering the following command:
cp PVGConfig.js PVGConfig.js.ORIG
4-c. In a text editor, open the PVGConfig.js design file for editing.
4-d. Specify the source of the element name for the Passport Packet Voice Gateway (PVG) by
uncommenting one of the following options:
FILE Specifies that the source for the element name is a PVG Bulk input file. The default option is
to specify the filename by using the FILE option. See Nortel PVG Performance Data on page 150 for an
explanation of the syntax that the PVG Bulk input files use.
LINKID Specifies that the source for the element name is the LINKID record that resides in a PVG
Bulk input file.
OFFICEID Specifies that the source for the element name is the OFFICEID record that resides in a
PVG Bulk input file.
The following example shows the selection of the FILE option:
5. Set the Location for the Nortel CS2000 Performance device in the CS2KPERFConfig.js file.
Before the Nortel CS2000 Technology Pack can create the Location name for the Nortel CS2000
Performance device, the location names must be identified in the CS2KPERFConfig.js file.
To configure the CS2KPERFConfig.js design file, follow these steps:
5-b. Make a backup copy of the CS2KPERFConfig.js design file, by entering the following command:
cp CS2KPERFConfig.js CS2KPERFConfig.js.ORIG
/ /
/ / $I d: PVGConf i g. j s 1346 2007- 07- 11 23: 23: 26Z wmar t i n $
/ /
set PVGEl ement Name( " FI LE" ) ;
/ / set PVGEl ement Name( " LI NKI D" )
/ / set PVGEl ement Name( " OFFI CEI D" )
5-c. In a text editor, open the CS2KPERFConfig.js design file for editing.
5-d. Specify the location name for the Nortel CS2000 Performance device as follows:
switchN Specifies the name of the switch.
locationN Specifies the location of the switch.
6. Set the Location for the Nortel USP device in the USPConfig.js file.
Before the Nortel CS2000 Technology Pack can create the Location name for the Nortel USP device, the
location names must be identified in the USPConfig.js file.
To configure the USPConfig.js design file, follow these steps:
6-b. Make a backup copy of the USPConfig.js design file, by entering the following command:
cp USPConfig.js USPConfig.js.ORIG
6-c. In a text editor, open the USPConfig.js design file for editing.
6-d. Specify the location name for the Nortel USP device as follows:
switchN Specifies the name of the switch.
locationN Specifies the location of the switch.
6-e. You can edit existing error messages or add new error messages for the Nortel USP device as follows:
messageErrors[N] Specifies the error condition.
text Specifies the error message for the corresponding error condition.
7. Activate percentile requests.
During installation of the technology pack, all predefined percentile requests are promoted to the database
and set to inactive (that is, idle displays in the Active column of the Netcool/Proviso DataMart Request
Editor). You need to activate these predefined percentile requests using the Request Editor.
To set percentile requests to active, follow these steps:
7-a. Click the Aggregation tab on the Request Editor.
7-b. In the Sub-Element Groups pane, select all percentile requests in the following group:
Root->NOC Reporting->Carrier VOIP
7-c. Click the Active box under Details. The Request Editor toggles the idle setting for these percentile
7-d. Click Save.
8. Edit pack-specific UBA parameters, based on the following Netcool/Proviso platforms:
443 and higher
Pre-443
443 and Higher
In this release of Netcool/Proviso, you were instructed to modify the technology pack-specific UBA
parameters when you installed the Nortel CS2000 Technology Pack, using the Topology Editor. If you did
not modify the UBA parameters with site-specific values or you want to make additional edits, you can do so
now. Otherwise, you can go to the next step.
See the Installing Technology Packs chapter of the Netcool/Proviso Installation Guide for more information.
Pre-443
The Nortel CS2000 Technology Pack requires specific UBA parameters that are not in the dc.cfg file. The
DataChannel installer creates a dc.cfg file in the DATA_CHANNEL_HOME/conf directory
(/opt/datachannel/conf, by default). These pack-specific parameters were delivered in a template file
called nortel_cs2000_sample_dc.cfg.
The best practice on adding these pack-specific parameters to the dc.cfg file is to:
Edit the pack-specific UBA parameters in the template file with site-specific values.
Manually add them to the dc.cfg file.
To edit the pack-specific UBA parameters in the template file with site-specific values, follow these steps:
8-b. Make a backup copy of the nortel_cs2000_sample_dc.cfg template file, by entering the
following command:
cp nortel_cs2000_sample_dc.cfg nortel_cs2000_sample_dc.cfg.ORIG
8-c. In a text editor, open the nortel_cs2000_sample_dc.cfg template file for editing.
8-d. Edit the pack-specific UBA parameters according to the instructions provided in Appendix C, Template File
Reference (Pre-443 Only).
8-e. When you are satisfied with your edits, write (but do not quit) the
nortel_cs2000_sample_dc.cfg template file.
Important: Editing the dc.cfg file is a non-trivial task and prone to error. Take your time and check your work
carefully.
To manually add the pack-specific UBA parameters to the dc.cfg file, follow these steps:
8-f. Open a second terminal emulator.
8-g. On the DataChannel server, change your working directory to the DATA_CHANNEL_HOME/conf
directory (/opt/datachannel/conf, by default), by entering the following command:
cd DATA_CHANNEL_HOME/conf
8-h. Make a backup copy of the dc.cfg file, by entering the following command:
cp dc.cfg dc.cfg.ORIG
8-i. In a text editor, open the dc.cfg file for editing.
8-j. Search for the UBA parameters, which begin with the string UBA. These parameters were written to the
dc.cfg file when you configured the UBA Bulk Collector and installed the DataChannel
configuration, as described in the Netcool/Proviso Installation Guide.
8-k. Copy the pack-specific UBA parameters from the nortel_cs2000_sample_dc.cfg template
file to the dc.cfg file.
8-l. When you are satisfied with your edits, do the following:
Quit the nortel_cs2000_sample_dc.cfg template file.
Write and quit the dc.cfg file.
9. Edit and run the cs2kcdr-config.pl script.
Before the Universal Bulk Adaptor (UBA) application can begin processing files, you must edit and then run the
cs2kcdr-config.pl script as described in Appendix D, Configuring cs2kcdr.pl Script Execution.
10. Load the DataChannel environment.
In subsequent steps, you will execute DataChannel commands. To ensure that you can run these commands,
load the shell with the DataChannel environment by following these steps:
10-a. Log in to the DataChannel server as pvuser.
10-b. Change your working directory to the DataChannel home directory (/opt/datachannel, by
default), using the following command:
$ cd /opt/datachannel
10-c. Load the shell with the DataChannel environment, by sourcing the dataChannel.env file, as
follows:
$ . /opt/datachannel/dataChannel.env
11. Stop the DataChannel components and visual processes.
11-a. Open a terminal emulator on the DataChannel server.
11-b. Use the dccmd command to stop all DataChannel applications:
dccmd -action stop all
11-c. Use the dccmd command to release all daemons running in the DataChannel:
dccmd -action forget all
11-d. Use the following command to find the process identifiers (pids) associated with the DataChannel
visual processes:
DATA_CHANNEL_HOME/bin/findvisual
where:
DATA_CHANNEL_HOME is /opt/datachannel, by default.
11-e. Use the following commands to stop each DataChannel visual process:
kill -9 <cnsw_pid>
kill -9 <logw_pid>
kill -9 <amgrw_pid>
kill -9 <cmgrw_pid>
11-f. Use the following commands to restart each DataChannel visual process:
cnsw
logw
amgrw
cmgrw
12. Restart the DataChannel components to activate one of the UBAs you have configured and read in changes
to the deployed topology (443 only) or dc.cfg (pre-443 only).
12-a. Use the dccmd command to start one of the UBAs you have configured. For example, if you
configured a UBA on datachannel 1 and collector 1:
dccmd -action start uba.1.1
12-b. Use the dccmd command to verify that the DataChannel components are running:
dccmd -action status all
12-c. Watch the output of the status switch to verify that all the necessary processes are running. If these
processes are running, run the tail utility on the log file for the UBA by issuing a command similar
to the following:
tail -f DATA_CHANNEL_HOME/log/proviso.log | grep UBA.<channel>.<collector>- | more
where:
The following table identifies some events to watch for during the syntax check:
13. Ensure that the Bulk input files can be read.
To verify that the UBA application can read the Bulk input files, follow these steps:
13-a. Place a Bulk input file at the source input location.
(443 only) The source input location for Bulk input files is specified using the URI parameter from the
packs XSD file, which you can view using the Topology Editor.
(Pre-443 only) The source input location for Bulk input files is specified using the URI parameter from
the template file, which you added to the dc.cfg file in a previous step.
Within the configured file retrieval interval (typically, five minutes), the UBA application retrieves the
Bulk input file and copies it to the following directory:
DATA_CHANNEL_HOME/UBA.<channel>.<collector>/<instance>/do/
Variable Meaning
DATA_CHANNEL_HOME Is /opt/datachannel, by default.
<channel> Specifies the channel number (for example, 1) you
specified when configuring this DataChannel.
<collector> Specifies the collector number (for example, 100) you
specified when configuring this UBA Bulk Collector.
The trailing dash () after <collector> Removes extraneous log messages from your view. That is,
the trailing dash guarantees that the command displays
only those messages generated by your application. The
first set of messages relate to syntax checks.
Event Meaning
The UBA application starts successfully, but then stops
executing.
Typically, this event occurs because of a licensing issue.
The Bulk Adaptor Design File might be corrupt. This event causes a syntax error before the UBA
application connects to the database.
The UBA application connects to the database. This event causes a message similar to the following to
display:
DB_CONNECT Connecting to <sid> as
<user>
If you see this database connection message without prior
errors, the UBA application has passed the syntax check.
where:
The UBA application then processes the Bulk input file according to the instructions in the Bulk Adaptor
Design File.
Note: The first time that the UBA processes a Bulk input file, it passes a metric to the CME. The CME rejects
this metric as a BAD_METRIC because the metric does not have an associated grouped sub-element prior to
the time this metric is recorded. This is expected behavior. The CME accepts metrics from the Bulk input files
after the inventory is run.
13-b. Ensure that the UBA application can successfully read the Bulk input file you copied into the source
input location by issuing a tail utility command similar to the following:
tail -f DATA_CHANNEL_HOME/log/proviso.log | grep UBA.<channel>.<collector>- | more
The following table identifies the success messages you should look for. Line breaks appear in the
messages to make them more readable.
Variable Meaning
DATA_CHANNEL_HOME Is /opt/datachannel, by default.
<channel> Specifies the channel number (for example, 1) you
specified when configuring this DataChannel.
<collector> Specifies the collector number (for example, 100) you
specified when configuring this UBA Bulk Collector.
<instance> (443 only) Specifies the string for the INSTANCES parameter in the
packs XSD file. Typically, this string represents the name
of the pack and is read-only. You can view the string
specified for INSTANCES using the Topology Editor.
<instance> (pre-443 only) Specifies the string for the INSTANCES parameter in the
packs template file. You were instructed to copy this
parameter to the dc.cfg file in a previous step.
Success Message Meaning
PERF_INPUT_PROCESSING Processed <integer> records in <float>
seconds (<float> records/minute): <int> records
Specifies a Bulk Adaptor Design File
completion message. A Bulk Adaptor
Design File successfully completes
when an informational message similar
to this one displays in the log file.
Success occurs when <int> records
equals 0.
14. Run the initial inventory.
The initial inventory of elements and sub-elements runs automatically when you start the CWMIF
component. This activity can be time-consuming, depending on the size of the network that the Nortel
CS2000 manages. In a large network, the initial inventory can take 6 to 12 hours.
To run a subsequent inventory for the Nortel CS2000 Technology Pack, follow these steps:
14-a. Login as pvuser on the computer (server) that hosts the BLB process for the Nortel CS2000 Technology
Pack.
14-b. Verify that all Nortel CS2000 Technology Pack components are running. Use a command like the
following:
$ /opt/datachannel/bin/dccmd -action status -channel channel#
where: channel# is the number of the DataChannel, specified when you configured it for the Nortel
CS2000 Technology Pack.
14-c. Start the inventory utility with the following syntax:
$ /opt/datachannel/bin/cs2kifDump channel#.collector#
where: collector# is the UBA Collector number, specified when you configured it for the Nortel CS2000
Technology Pack.
For example:
$ /opt/datachannel/bin/cs2kifDump 1.100
15. Use the DataMart Resource Editor to verify that resources are being created by the UBA. See the
Netcool/Proviso DataMart Configuration Guide for more information.
METRIC_STREAM_INFO Completed writing metric output:
DATA_CHANNEL_HOME/UBA.<channel>.<collector>/streaming/
state/temp/output/<time>.<instance>.NRAW.BOF; wrote <int>
metrics; <int> bad resource IDs; <int> bad formula names (#())
Specifies a metric creation success
message. The UBA application
successfully creates metrics when a
debug 2 message similar to this one
displays in the log file.
For some technology packs, the metric
creation may be done across different
instances of UBA applications. Success
occurs when <int> metrics is greater
than one, <int> bad resource IDs
equals 0, and <int> bad formula names
equals 0.
PERF_INVFLUSH Inserted/updated <int> inventory objects in
<float> seconds
Specifies an inventory success message.
The inventory successfully completes
when an informational message similar
to this one displays in the log file.
If <int> is greater than one, the UBA
application created or updated at least
one sub-element, and the inventory
process is successful. The log file might
record further details (if necessary) in
the messages associated with the
PERF_INVFLUSHPV sub-element
message category.
Success Message Meaning
Please allow the UBA sufficient processing time to create these resources before performing this check.
16. Once resources have been created, repeat Step 12 - Step 16 for any other related UBA instances that you
have configured. For example, if UBA.1.1, UBA.1.4, and UBA.2.2 are all related, once UBA.1.1 has been
started and verified, repeat the process for UBA.1.4, then finally for UBA.2.2.
17. After a set of related UBAs have all been started and verified, repeat Step 12 - Step 17 for each remaining set
of UBAs that you have configured.
18. Run the Bulk inventory profile.
The UBA application handles the inventory and metrics according to the instructions provided in the
technology pack design file or files. Specifically, the UBA application inserts the created elements, sub-
elements, and metrics into the database. However, the UBA application does not handle the grouping of
these elements and sub-elements.
To handle the grouping of the elements and sub-elements that were inserted into the database, UBA
technology packs supply a bulk inventory profile. The bulk inventory profile is automatically created when
the pack is installed. Bulk inventory profiles use the following name syntax:
bulk_N
where:
You must use the Inventory Tool to run a bulk inventory profile.
To run the bulk inventory profiles for this technology pack, perform the following steps:
18-a. In the command window where you loaded the DataMart environment, change your working directory
to $PVMHOME/bin (/opt/datamart/bin, by default) on the DataMart server.
18-b. Invoke the DataMart GUI:
$ pvm
18-c. Click Inventory Tool in the Resource tab. The Inventory Tool window appears.
This window displays a list of the existing inventory profiles on the Configuration tab. The names of the
inventory profiles to run are bulk_N1 and bulk_N2, where N1 and N2 are the collector numbers
configured for this pack.
18-d. On the Configuration tab, click on the bulk inventory profiles for this technology pack and then select
Run Profile from the Action menu.
The Live Information tab displays messages about the status of the profile. See the Netcool/Proviso
DataMart Configuration Guide for more information about running an inventory profile.
18-e. (Optional) Every time the UBA technology pack design file creates new elements, sub-elements, and
metrics, you need to perform the previous steps to group the elements and sub-elements. One way to
accomplish this task on a regular basis is to create a cron entry that make use of the inventory
command. The following example shows the cron entries that periodically perform the grouping
operation for the bulk inventory profiles called bulk_100 and bulk_101:
0 * * * * . /opt/datamart/dataMart.env && inventory -name bulk_100 -action pregrouping -reload -noX
0 * * * * . /opt/datamart/dataMart.env && inventory -name bulk_100 -action grouping -reload -noX
0 * * * * . /opt/datamart/dataMart.env && inventory -name bulk_101 -action pregrouping -reload -noX
Syntax Item Meaning
bulk_ Identifies this as a bulk inventory profile for a UBA
technology pack.
N Specifies the collector number (for example, 100) that the
user specified when configuring this UBA Bulk Collector.
0 * * * * . /opt/datamart/dataMart.env && inventory -name bulk_101 -action grouping -reload -noX
See the Netcool/Proviso Command Line Interface Guide for more information about the inventory command.
19. Use the dccmd command to start all DataChannel applications:
dccmd -action start all
20. Deploy reports.
After the technology pack installation completes, the rules for the new device are automatically loaded into
the database. The inventory process uses those rules to group elements and sub-elements. You must
manually deploy (auto-group) the reports by associating them with groups in the DataMart Resource Editors
NOC Reporting tree.
To deploy the Nortel CS2000 Technology Pack reports, follow these steps:
20-a. Open the Netcool/Proviso DataMart Resource Editor.
20-b. Click the ReportSEGroup tab.
20-c. Move the cursor to the left pane and scroll up to select any group under the SUB-ELEMENTS->NOC
Reporting tree.
20-d. Right-click and select the AutoGrouping option from the menu. The AutoGrouping option places the
reports in dynamically generated groups created during inventory.
20-e. Click Yes to continue.
20-f. Click Close to exit the message box, or click Details to view a description of any errors.
20-g. (Optional) You can also deploy reports on a regular basis by creating a cron entry that makes use of the
inventory CLI command and the -reportGrouping option. This option instructs the inventory
command to run the report grouping rules and update the deployed reports stored in the database.
Report grouping rules must first have been created before this option can be used. For information on
creating report grouping rules, see the Netcool/Proviso DataMart Configuration Guide.
The following example shows a cron entry that periodically performs the deploy report operation:
0 * * * * . /opt/datamart/dataMart.env && inventory -noX -reportGrouping
See the Netcool/Proviso Command Line Interface Guide for more information about the inventory
command.
Other Tasks and Considerations
This section contains information on the following topics:
Verifying Resources
Verifying Resources
Use the Netcool/Proviso DataMart Resource Editor to determine if the technology packs resources (elements,
sub-elements, properties, and so forth) were successfully discovered and created in the database during inventory.
See the Netcool/Proviso DataMart Configuration Guide for information on using the Netcool/Proviso DataMart
Resource Editor.
Appendix B: UBA Parameters Reference
(Netcool/Proviso 443 and Higher)
This appendix provides UNIX reference pages for each of the pack-specific UBA parameters supplied with the
XSD file for the Nortel CS2000 Technology Pack. The descriptions are the same as those that display in the
Topology Editor Help. These reference pages are provided as a convenience.
UBA Parameters Reference
The following pages provide a reference of the UBA parameters that this technology pack provides. The reference
pages have the following sections:
Parameter name. Each reference page begins with the parameter name. Parameter names use the following
syntax:
[<device>.][<instance>.][<schema>.]<parameter_name>
where:
<device> Specifies the name of the device.
<instance> Specifies the group alias, which is typically a string that represents the name of the
technology pack.
<schema> Specifies the string passed to the input schema object referenced in the packs Bulk Adaptor Design
(JavaScript) file.
<parameter_name> Specifies the name of the parameter.
In the Detail sections of the reference pages, parameter names in the descriptions are typically referenced as
<schema>.<parameter_name> or simply <parameter_name>. The descriptions do not reference the <device> or
<instance> part of the parameter name.
Description. A short description that identifies the purpose of the parameter.
Component. The DataChannel application (component) to which the parameter applies. The value
specified for this parameter controls the behavior of this DataChannel application. This section can contain
the following values:
BLB Specifies the DataChannel BLB (Bulk Load Balancer) application.
IF Specifies the DataChannel Inventory File (IF) application. Examples of IF applications include:
* SAMIF Specifies the IF application for the Alcatel 5620 SAM Technology Pack.
* QCIF Specifies the IF application for the Alcatel 5620 NM Technology Pack.
* CWMIF Specifies the IF application for the Cisco CWM Technology Pack.
UBA Specifies the DataChannel UBA (Universal Bulk Adaptor) application.
Most UBA technology packs operate with only the UBA application.
Value. Specifies the following information:
Default Identifies the default value, if one is specified, for the parameter.
Appendix B: UBA Parameters Reference (Netcool/Proviso 443 and Higher)
Attribute Specifies whether the parameter is writable.
Location Specifies the location of the parameter in the Topology Editor.
Detail. Provides details about the parameter, including possible values.

Appendix B: UBA Parameters Reference (Netcool/Proviso 443 and
CDR: COLLECTOR_ALIAS
Description
Allows a DataChannel application to process elements owned by other collectors
Component
UBA
Value
Default: No default value
Attribute: Writable
Location: Properties tab
Detail
The COLLECTOR_ALIAS parameter allows DataChannel applications that handle inventory and metrics
operations to process inventory and/or metrics for Netcool/Proviso elements owned by other collectors.
Typically, this parameter is used in dual collection with an SNMP Collector. Specify the SNMP Collector number
or other UBA Bulk Collector number that was configured for this technology pack.
CDR: COLLECTOR_LIST
Description
Comma separated list of collector numbers from which to take input
Component
UBA
Value
Attribute: Writable
Detail
The COLLECTOR_LIST parameter defines the collectors to which the DataChannel applications that handle
inventory and metrics operations can assign resources during the inventory process. The value specified is a
comma separated list of collectors that map to configured collectors and should always include the current
collector number. If you specify more than one collector, the DataChannel inventory and metrics applications
assign resources to the collector that has the lightest load.
CDR: INSTANCES
Description
Group alias
Component
UBA
Value
Default: NORTEL_CS2000
Attribute: Read-only
Location: Advanced Properties tab
Detail
The DataChannel supports multiple instances of technology packs running in a single channel component.
Therefore, there must be a way to guarantee that the DataChannel applications that handle inventory and metrics
parse the correct design files and read the appropriate Bulk input files. The INSTANCES parameter helps ensure
that the DataChannel applications that handle inventory and metrics perform the correct operation for a specific
technology pack.
This is a read-only parameter whose value you cannot change. Typically, the value for INSTANCES is a string that
represents the name of the technology pack.
CDR: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Number of sub-elements added to inventory
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
The INVENTORY_SUBELEMENT_FLUSH_THRESHOLD parameter specifies the number of sub-elements that are
added to the inventory before the DataChannel application that handles inventory flushes them to the database.
CDR: NORTEL_CS2000.CS2K.DELETEONACQUIRE
Description
Deletes Nortel CS2K CDR Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The CS2K.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel CS2K CDR
device generates should be preserved after the UBA acquires them. A related parameter - CS2K.URI - specifies
the location of these Bulk input files.
Set this parameter to the value true to instruct this UBA application to delete the Bulk input files after it acquires
them. Otherwise, set this parameter to false to instruct this UBA application to preserve the Bulk input files
after it acquires them.
CDR: NORTEL_CS2000.CS2K.URI
Description
Full path to Nortel CS2K CDR Bulk input files
Component
UBA
Value
Detail
The DataChannel applications that handle inventory and metrics (typically, the UBA) must be directed to the
location of the Bulk input files generated by the devices associated with the technology on which the application
operates. The CS2K.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel CS2K CDR generates. A related parameter -
CS2K.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk input files after it
acquires them.
The CS2K.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
username, password or input directory fields of the URI specification, edit these parameters:
INPUT_USE_SECURE_FTP
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
Note: Any subdirectories and the actual wildcard used to specify the Bulk input files to be acquired are
automatically specified in the CS2K.URI parameter.
CDR: NORTEL_CS2000.DESIGNFILE
Description
JavaScript file that controls UBA
Component
UBA
Value
Default: SimpleCS2KCDRAdaptor.js
Detail
Netcool/Proviso technology packs control the behavior of the DataChannel UBA application through
instructions contained in Bulk Adaptor design (JavaScript) files. The DESIGNFILE parameter identifies the name
of a technology packs design file.
This is a read-only parameter. You cannot change the name of the technology packs Bulk Adaptor design file.
CDR: NORTEL_CS2000.INPUT_ID
Description
The ID of a CDR UBA in a load balancing scenario
Component
UBA
Value
Attribute: Writable
Detail
The INPUT_ID parameter specifies the ID of a particular CDR UBA in a load-balancing scenario.
CDR: NORTEL_CS2000.TIMEZONE
Description
Timezone in which UBA obtains input data
Component
UBA
Value
Default: GMT
Detail
The TIMEZONE parameter specifies the timezone in which the UBA obtains the input data from the Bulk input
files. Typically, technology packs deliver this parameter only when the input data is something other than UTC.
The default timezone is GMT (Greenwich Mean Time).
CDR_Stray_Handler: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
CDR_Stray_Handler: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
CDR_Stray_Handler: NORTEL_CS2000.CS2K.DELETEONACQUIRE
Description
Deletes Nortel CS2K CDR Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The CS2K.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel CS2K CDR
device generates should be preserved after the UBA acquires them. A related parameter - CS2K.URI - specifies
the location of these Bulk input files.
CDR_Stray_Handler: NORTEL_CS2000.CS2K.URI
Description
Full path to Nortel CS2K CDR Bulk input files
Component
UBA
Value
Detail
operates. The CS2K.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel CS2K CDR generates. A related parameter -
CS2K.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk input files after it
acquires them.
The CS2K.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the CS2K.URI parameter.
CDR_Stray_Handler: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: SimpleCS2KCDRAdaptor.js
Detail
CDR_Stray_Handler: NORTEL_CS2000.INPUT_DIRECTORY
Description
Path to Bulk input files directory
Component
UBA
Value
Attribute: Writable
Detail
The INPUT_DIRECTORY parameter specifies the path to the directory where the generated Bulk input files should
be stored.
Do not enter any subdirectories and the actual wildcards used to specify the Bulk input files to be acquired. Any
subdirectories and wildcards are automatically specified in the URI-related parameters. An example of an input
directory specification is /opt/uba.
CDR_Stray_Handler: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
FTP or SFTP password for Bulk input files
Component
UBA
Value
Attribute: Writable
Detail
The INPUT_FTP_PASSWORD parameter specifies the password that the server administrator assigned (using the
ftp or sftp utility) to the FTP or SFTP user. The FTP or SFTP user specifies this password to gain access to the
server on which the Bulk input files reside.
Likewise, the UBA uses this same password to gain access to the server on which the Bulk input files reside.
CDR_Stray_Handler: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
FTP or SFTP username for Bulk input files
Component
UBA
Value
Attribute: Writable
Detail
The INPUT_FTP_USERNAME parameter specifies the username that the server administrator assigned (using the
ftp or sftp utility) to the FTP or SFTP user. The FTP or SFTP user specifies this username to gain access to the
Likewise, the UBA uses this same username to gain access to the server on which the Bulk input files reside.
CDR_Stray_Handler: NORTEL_CS2000.INPUT_HOST
Description
Hostname for Bulk input files
Component
UBA
Value
Attribute: Writable
Detail
The INPUT_HOST parameter specifies the hostname of the server on which the Bulk input files reside. These are
the files that the UBA parses.
CDR_Stray_Handler: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Acquire Bulk input files using secure FTP
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The INPUT_USE_SECURE_FTP parameter specifies whether FTP (File Transfer Protocol) or SFTP (secure FTP)
is used. To use FTP, specify the value false. Otherwise, to use SFTP, specify the value true. The default value
is false.
To use the sftp command, you must have an SSH client installed on the servers where the Bulk input files reside
and where the DataChannel is running. Typically, an SSH client is installed by default on most UNIX systems.
For more information, see your operating system documentation or the sftp manpage.
Note: You cannot do the following:
Use an FTP client to connect to an SFTP server
Connect to an FTP server with a client that supports only SFTP
CDR_Stray_Handler: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
CPR: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
CPR: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
CPR: NORTEL_CS2000.CPR.DELETEONACQUIRE
Description
Deletes CPR Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The CPR.DELETEONACQUIRE parameter specifies whether the Bulk input files that the CPR device generates
should be preserved after the UBA acquires them. A related parameter - CPR.URI - specifies the location of these
Bulk input files.
CPR: NORTEL_CS2000.CPR.URI
Description
Full path to CPR Bulk input files
Component
UBA
Value
Detail
location of the Bulk input files that are generated by the devices associated with the technology on which the
application operates. The CPR.URI parameter specifies the location, in Universal Resource Identifier (URI)
format, for the specified UBA to retrieve the Bulk input files that are CPR-based data files. In its current
incarnation, the CPRAdaptor can handle CPR files that are generated from the Nortel Packet Voice Gateway
(PVG) and the Nortel Session Server Trunk (SST). A related parameter - CPR.DELETEONACQUIRE - specifies
whether the UBA application should delete these Bulk input files after it acquires them.
The CPR.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the CPR.URI parameter.
CPR: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: CPRAdaptor.js
Detail
CPR: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
CPR: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
CPR: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
CPR: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
CPR: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
CPR: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
IEMS: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
IEMS: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
IEMS: NORTEL_CS2000.AMS.DELETEONACQUIRE
Description
Deletes Nortel AMS Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The AMS.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel AMS generates
should be preserved after the UBA acquires them. A related parameter - AMS.URI - specifies the location of these
Bulk input files.
IEMS: NORTEL_CS2000.AMS.URI
Description
Full path to Nortel AMS device Bulk input files
Component
UBA
Value
Detail
operates. The AMS.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel Announcement Media Server (AMS) generates. A
related parameter - AMS.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk
input files after it acquires them.
The AMS.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the AMS.URI parameter.
IEMS: NORTEL_CS2000.CICM.DELETEONACQUIRE
Description
Deletes Nortel CICM Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The CICM.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel CICM generates
should be preserved after the UBA acquires them. A related parameter - CICM.URI - specifies the location of
these Bulk input files.
IEMS: NORTEL_CS2000.CICM.URI
Description
Full path to Nortel CICM device Bulk input files
Component
UBA
Value
Detail
operates. The CICM.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel Centrex IP Client Manager (CICM) generates. A
related parameter - CICM.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk
The CICM.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the CICM.URI parameter.
IEMS: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: IEMSPERFAdaptor.js
Detail
IEMS: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
IEMS: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
IEMS: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
IEMS: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
IEMS: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
IEMS: NORTEL_CS2000.MS2000.DELETEONACQUIRE
Description
Deletes Nortel MS 2000 Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The MS2000.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel MS 2000
generates should be preserved after the UBA acquires them. A related parameter - MS2000.URI - specifies the
location of these Bulk input files.
IEMS: NORTEL_CS2000.MS2000.URI
Description
Full path to Nortel MS2000 Bulk input files
Component
UBA
Value
Detail
operates. The MS2000.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for
the specified UBA to retrieve the Bulk input files that the Nortel Media Server 2000 (MS 2000) generates. A
related parameter - MS2000.DELETEONACQUIRE - specifies whether the UBA application should delete these
Bulk input files after it acquires them.
The MS2000.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the MS2000.URI parameter.
IEMS: NORTEL_CS2000.SAM21.DELETEONACQUIRE
Description
Deletes Nortel SAM21 Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The SAM21.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel SAM21
generates should be preserved after the UBA acquires them. A related parameter - SAM21.URI - specifies the
location of these Bulk input files.
IEMS: NORTEL_CS2000.SAM21.URI
Description
Full path to Nortel SAM21 Bulk input files
Component
UBA
Value
Detail
operates. The SAM21.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel SAM21 Shelf Controller (SAM21) generates. A
related parameter - SAM21.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk
The SAM21.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the SAM21.URI parameter.
IEMS: NORTEL_CS2000.SPC.DELETEONACQUIRE
Description
Deletes Nortel SPC Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The SPC.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel SPC generates
should be preserved after the UBA acquires them. A related parameter - SPC.URI - specifies the location of these
Bulk input files.
IEMS: NORTEL_CS2000.SPC.URI
Description
Full path to Nortel SPC Bulk input files
Component
UBA
Value
Detail
operates. The SPC.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Nortel Session Policy Controller (SPC) generates. A related
parameter - SPC.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk input files
The SPC.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the SPC.URI parameter.
IEMS: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
Performance: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
Performance: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
Performance: NORTEL_CS2000.CS2KPERF.DELETEONACQUIRE
Description
Deletes Nortel CS2K Performance Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The CS2KPERF.DELETEONACQUIRE parameter specifies whether the Bulk input files that the Nortel CS2K
Performance device generates should be preserved after the UBA acquires them. A related parameter -
CS2KPERF.URI - specifies the location of these Bulk input files.
Performance: NORTEL_CS2000.CS2KPERF.URI
Description
Full path to Nortel CS2K Performance Bulk input files
Component
UBA
Value
Detail
operates. The CS2KPERF.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for
the specified UBA to retrieve the Bulk input files that the Nortel CS2K Performance device generates. A related
parameter - CS2KPERF.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk
The CS2KPERF.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the CS2KPERF.URI parameter.
Performance: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: CS2KPERFAdaptor.js
Detail
Performance: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
Performance: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
Performance: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
Performance: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
Performance: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
Performance: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
PVG: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
PVG: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
PVG: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: PVGAdaptor.js
Detail
PVG: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
PVG: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
PVG: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
PVG: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
PVG: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
PVG: NORTEL_CS2000.PVG.DELETEONACQUIRE
Description
Deletes PVG Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The PVG.DELETEONACQUIRE parameter specifies whether the Bulk input files that the PVG device generates
should be preserved after the UBA acquires them. A related parameter - PVG.URI - specifies the location of these
Bulk input files.
PVG: NORTEL_CS2000.PVG.URI
Description
Full path to PVG Bulk input files
Component
UBA
Value
Detail
operates. The PVG.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Passport Packet Voice Gateway (PVG) device generates. A
related parameter - PVG.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk
The PVG.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the PVG.URI parameter.
PVG: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
SSL: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
SSL: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
SSL: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: SSLAdaptor.js
Detail
SSL: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
SSL: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
SSL: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
SSL: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
SSL: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
SSL: NORTEL_CS2000.SSL.DELETEONACQUIRE
Description
Deletes SSL Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The SSL.DELETEONACQUIRE parameter specifies whether the Bulk input files that the SSL device generates
should be preserved after the UBA acquires them. A related parameter - SSL.URI - specifies the location of these
Bulk input files.
SSL: NORTEL_CS2000.SSL.URI
Description
Full path to SSL Bulk input files
Component
UBA
Value
Detail
operates. The SSL.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for the
specified UBA to retrieve the Bulk input files that the Session Server Lines (SSL) device generates. A related
parameter - SSL.DELETEONACQUIRE - specifies whether the UBA application should delete these Bulk input files
The SSL.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the SSL.URI parameter.
SSL: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
USP: INSTANCES
Description
Group alias
Component
UBA
Value
Detail
technology pack.
USP: INVENTORY_SUBELEMENT_FLUSH_THRESHOLD
Description
Component
UBA
Value
Default: 200
Attribute: Writable
Detail
USP: NORTEL_CS2000.DESIGNFILE
Description
Component
UBA
Value
Default: USPPERFAdaptor.js
Detail
USP: NORTEL_CS2000.INPUT_DIRECTORY
Description
Component
UBA
Value
Attribute: Writable
Detail
be stored.
USP: NORTEL_CS2000.INPUT_FTP_PASSWORD
Description
Component
UBA
Value
Attribute: Writable
Detail
USP: NORTEL_CS2000.INPUT_FTP_USERNAME
Description
Component
UBA
Value
Attribute: Writable
Detail
USP: NORTEL_CS2000.INPUT_HOST
Description
Component
UBA
Value
Attribute: Writable
Detail
USP: NORTEL_CS2000.INPUT_USE_SECURE_FTP
Description
Component
UBA
Value
Default: false
Attribute: Writable
Detail
is false.
USP: NORTEL_CS2000.TIMEZONE
Description
Component
UBA
Value
Default: GMT
Attribute: Writable
Detail
USP: NORTEL_CS2000.USPPERF.DELETEONACQUIRE
Description
Deletes USP Bulk input files after acquisition
Component
UBA
Value
Default: false
Attribute: Writable
Detail
The USPPERF.DELETEONACQUIRE parameter specifies whether the Bulk input files that the USP device generates
should be preserved after the UBA acquires them. A related parameter - USPPERF.URI - specifies the location of
these Bulk input files.
USP: NORTEL_CS2000.USPPERF.URI
Description
Full path to USP Bulk input files
Component
UBA
Value
Detail
operates. The USPPERF.URI parameter specifies the location, in Universal Resource Identifier (URI) format, for
the specified UBA to retrieve the Bulk input files that the Universal Signaling Port (USP) device generates. A
related parameter - USPPERF.DELETEONACQUIRE - specifies whether the UBA application should delete these
Bulk input files after it acquires them.
The USPPERF.URI parameter is read-only. To change the transport mechanism (ftp or secure ftp), hostname,
INPUT_HOST
INPUT_FTP_USERNAME
INPUT_FTP_PASSWORD
INPUT_DIRECTORY
automatically specified in the USPPERF.URI parameter.
Appendix C: Template File Reference (Pre-443 Only)
You should be reading this appendix after you have opened the nortel_cs2000_sample_dc.cfg
template file for editing, as instructed to do so in Appendix A, Configuration.
This appendix provides a UNIX reference page that identifies the pack-specific UBA parameters you need to add
to the dc.cfg file and explains how to tailor the values to your specific deployment.
Pack-Specific UBA Parameters
Template File Name
nortel_cs2000_sample_dc.cfg
File Location
The nortel_cs2000_sample_dc.cfg template file resides in the following directory on the
DataChannel server:
DATA_CHANNEL_HOME/scripts (/opt/datachannel/scripts, by default)
You were instructed to copy the nortel_cs2000_sample_dc.cfg template file in a configuration step
(Copy technology-specific files from the DataMart server to the DataChannel server) described in Appendix A, Configuration.
CPR Device Configuration Settings
The nortel_cs2000_sample_dc.cfg template file provides the following pack-specific UBA
parameters for the CPR device:
# Nortel CS2K - CPR
UBA.<CHANNEL>.<COLLECTOR>.COLLECTOR_ALIAS=<COLLECTOR>
UBA.<CHANNEL>.<COLLECTOR>.COLLECTOR_LIST=<COLLECTOR>
UBA.<CHANNEL>.<COLLECTOR>.DB_PASSWORD=AAAC
UBA.<CHANNEL>.<COLLECTOR>.DB_USERNAME=PV_GUI
UBA.<CHANNEL>.<COLLECTOR>.DUAL_LOGGING=FALSE
UBA.<CHANNEL>.<COLLECTOR>.FC_FSLL=150000000
UBA.<CHANNEL>.<COLLECTOR>.FC_QUOTA=100000000
UBA.<CHANNEL>.<COLLECTOR>.FC_RETENTION_HOURS=72
UBA.<CHANNEL>.<COLLECTOR>.INSTANCES=NORTEL_CS2000
UBA.<CHANNEL>.<COLLECTOR>.INVENTORY_SUBELEMENT_FLUSH_THRESHOLD=200
UBA.<CHANNEL>.<COLLECTOR>.LOG_FILTER=FEWI 123
UBA.<CHANNEL>.<COLLECTOR>.MAX_LOGS=3
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CPR.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CPR.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP_
PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.csv
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=CPRAdaptor.js
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.TIMEZONE=GMT
UBA.<CHANNEL>.<COLLECTOR>.POLL_INTERVAL=60
UBA.<CHANNEL>.<COLLECTOR>.ROOT_DIRECTORY=/opt/datachannel
UBA.<CHANNEL>.<COLLECTOR>.RUNINTERVAL=60
UBA.<CHANNEL>.<COLLECTOR>.SERVICE_INSTANCE=GLOBAL
CS2K Performance Device Configuration Settings
parameters for the Nortel CS2K Performance device:
# Nortel CS2K - CS2K Performance
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2KPERF.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2KPERF.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT
_FTP_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.csv
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=CS2KPERFAdaptor.js
CS2K CDR Device Configuration Settings
parameters for the Nortel CS2K CDR device:
# Nortel CS2K - CDR
UBA.<CHANNEL>.<COLLECTOR>.COLLECTOR_ALIAS=<MASTER(COLLECTOR_NUMBER)>
UBA.<CHANNEL>.<COLLECTOR>.COLLECTOR_LIST=<MASTER(COLLECTOR_NUMBER)>
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2K.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2K.URI=ftp://<MASTER(INPUT_FTP_USERNAME)>:<M
ASTER(INPUT_FTP_PASSWORD)>@<MASTER(INPUT_HOST)>/<MASTER(INPUT_DIRECTORY)>/*.<INPUT_ID>
.csv
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=SimpleCS2KCDRAdaptor.js
Note: You must have an input URI statement defined for each of output streams configured in the
cs2kcdr.pl script file. For more information, see Appendix D, Configuring cs2kcdr.pl Script Execution.
CS2K CDR Stray Handler Configuration Settings
parameters for the Nortel CS2K CDR Stray Handler:
Note: The CS2K CDR Stray Handler must share the same collector alias as you defined for the CS2K CDR
Device.
# Nortel CS2K - CDR
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2K.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CS2K.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP
_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.STRAY.csv
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=SimpleCS2KCDRAdaptor.js
Nortel IEMS Device Configuration Settings
parameters for the Nortel Integrated Element Management System (IEMS) device:
# Nortel CS2K - IEMS
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.AMS.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.AMS.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP_
PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/ams/*.xml
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CICM.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.CICM.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP
_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/cicm/*.xml
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=IEMSPERFAdaptor.js
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.MS2000.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.MS2000.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_F
TP_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/ms2000/*.xml
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SPC.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SPC.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP_
PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/ngss/*.xml
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SAM21.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SAM21.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FT
P_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/sam21/*.xml
PVG Device Configuration Settings
parameters for the Passport Packet Voice Gateway (PVG) device:
# Nortel CS2K - PVG
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=PVGAdaptor.js
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.PVG.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.PVG.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP_
PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.csv
Nortel SSL Device Configuration Settings
parameters for the Nortel Session Server Lines (SSL) device:
# Nortel CS2K - SSL
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=SSLAdaptor.js
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SSL.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.SSL.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_FTP_
PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.xml
USP Device Configuration Settings
parameters for the Universal Signaling Point (USP) device:
# Nortel CS2K - USP
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.DESIGNFILE=USPPERFAdaptor.js
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.USPPERF.DELETEONACQUIRE=false
UBA.<CHANNEL>.<COLLECTOR>.NORTEL_CS2000.USPPERF.URI=ftp://<INPUT_FTP_USERNAME>:<INPUT_
FTP_PASSWORD>@<INPUT_HOST>/<INPUT_DIRECTORY>/*.txt
Pack-Specific UBA Parameter Values
Additional Information on UBA Parameters
INSTANCES
The DataChannel UBA application supports multiple instances of technology packs running in a single channel
component. Therefore, there must be a way to guarantee that the UBA parses the correct design file and reads
the appropriate Bulk input files. The INSTANCES parameter helps ensure that the DataChannel UBA application
performs the correct operation for a specific technology pack.
The Nortel CS2000 Technology Pack provides an INSTANCES parameter in its
nortel_cs2000_sample_dc.cfg template file. You supply an arbitrary string referred to as a group
UBA Parameter Value Meaning
<CHANNEL> Replace with the channel number that was configured for
this technology pack. This channel number appears in the
dc.cfg file.
<COLLECTOR> Replace with the UBA Bulk Collector number that was
configured for this technology pack. This collector
number appears in the dc.cfg file.
<INSTANCE> Replace with an arbitrary string that identifies a group alias
to be associated with subsequent lines in this section of the
dc.cfg file. See Additional Information on UBA
Parameters on page 803 for more information on this UBA
parameter value.
alias to the INSTANCES parameter. After you define the INSTANCES parameter with a specific string, make
sure you specify this string wherever <instance> appears in the template file.
You can associate this group alias with any arbitrary string. For example, you might associate this group alias with
the location (for example, BOSTON, LOWELL, BERLIN, PARIS, and so forth) of the data source.
URI
The DataChannel UBA application needs to know where to find the Bulk input files that the supported device
generates. Therefore, you must specify a Universal Resource Identifier (URI) for the location of the Bulk input
files. To define this location, the Nortel CS2000 Technology Pack provides a URI parameter in its
nortel_cs2000_sample_dc.cfg template file.
Follow these guidelines when specifying a URI in the template or dc.cfg file:
Use Internet-standard URIs.
Specify the file protocol, FTP (File Transfer Protocol), or SFTP (secure FTP).
The file protocol is appropriate only when specifying a path on the same host computer.
When using the file protocol, specify a full absolute path after the initial file://. This results in three
slashes after the word file, because the full path must begin with a slash.
When using FTP or SFTP, use the following syntax:
f t p: / / <username>: <encrypted_password>@<hostname>/ / f ul l / pat h/ t o/ di r ect or y/ speci f i c_st r i ng
sf t p: / / <username>: <encrypted_password>@<hostname>/ / f ul l / pat h/ t o/ di r ect or y/ speci f i c_st r i ng
where:
<username> Specifies the username that the server administrator assigned (using the ftp or sftp
utility) to the FTP or SFTP user. The FTP or SFTP user specifies this username to gain access to the
server on which the technology pack is installed.
<encrypted_password> Specifies the password that the server administrator assigned (using the ftp or
sftp utility) to the FTP or SFTP user. The FTP or SFTP user specifies this password to gain access to
the server on which the technology pack is installed. The password specified here should be the
encrypted password.
<hostname> Specifies the hostname of the server on which the Bulk input files reside. These are the
files that the UBA parses.
specific_string Refers to the string that ends an entry for the URI line.
NOTE: You cannot do the following:
Notes
Use the following guidelines to determine if you have the correct value for the
UBA.<CHANNEL>.<COLLECTOR>.DB_USERNAME parameter in the dc.cfg file:
The UBA technology pack requires the DataChannel UBA application to process metrics only. In this
scenario, the UBA technology pack provides a metrics schema in its design file. In this case, DB_USERNAME
must be set to PV_COLL.
The UBA technology pack requires the DataChannel UBA application to process both inventory and
metrics. In this scenario, the UBA technology pack provides metrics and inventory schemas in its design file.
In this case, DB_USERNAME must be set to PV_GUI.
For the Nortel CS2000 Technology Pack, DB_USERNAME should be set to PV_GUI.
NOTES
Appendix D: Configuring cs2kcdr.pl Script Execution
This appendix discusses the following topics:
Overview
This appendix describes how to configure and run the cs2kcdr.pl script that is delivered as part of the Nortel
CS2000 Technology Pack.
Configuration of the cs2kcdr.pl Script
You must configure the cs2kcdr.pl script as part of the tasks performed in Appendix A, Configuration.
The cs2kcdr.pl script runs as a daemon, so it will fork when it is run in standalone mode. The script requires
the following Perl modules available from http://www.cpan.org:
Net::FTP Date::Manip
The cs2kcdr.pl daemon retrieves files via Net::FTP. If your environment requires SFTP access, you can
optionally download the module via CPAN, and change the cs2kcdr.pl to call Net::SFTP instead of Net::FTP.
The Net::SFTP module is also available from http://www.cpan.org.
The cs2kcdr.pl can run on multiple platforms, provided perl and the appropriate modules are installed, and
that the systems running the UBA collectors have ftp (or file) access to the output CSV from the cs2kcdr.pl
script.
Note: Note that some of the directories specified in the configuration section of the cs2kcdr.pl file may need
to be created by hand.
The cs2kcdr.pl is configured by editing the cs2kcdr-config.pl script.
Editing the cs2kcdr-config.pl Script
To edit the cs2kcdr-config.pl script, follow these steps:
1. Log in to the Netcool/Proviso DataChannel server by entering the username and password that you
specified when installing and configuring a DataChannel. The default username and password are pvuser
and PV, respectively.
Topic Page
Overview 807
Configuration of the cs2kcdr.pl Script 807
2. Change your working directory to the DATA_CHANNEL_HOME/scripts directory by entering the
following command, replacing DATA_CHANNEL_HOME with the DataChannel home directory
(/opt/datachannel, by default):
$ cd DATA_CHANNEL_HOME/scripts
The cs2kcdr.pl and cs2kcdr-config.pl scripts were copied to the this directory as part of the
configuration tasks performed in Appendix A, Configuration.
3. Using the text editor of your choice open the cs2kcdr-config.pl script.
Note: Do not edit the cs2kcdr.pl script.
4. Locate the values of the cs2kcdr-config.pl script shown in the following table and edit the parameters
according to the requirements of your environment:
5. In the cs2kcdr-config.pl script locate the values found in the table below and edit the parameters
according to the requirements of your environment:
Parameter Description
$logDir = Specifies the location of the cs2kcdr.pl daemon log file.
$NNI = Specifies the sensor ID number for the switch.
$maxFilesPerRun = Specifies the number of IPDR and AMA files that are
processed in a single run.
$amaFilesPerRun = Specifies the number of AMA files that are processed in a
single run.
$runInterval = Specifies how often to run and collect input files.
$lagBehindDelay = Specifies the lag delay behind the UBA in seconds.
$globalAggrInterval = Specifies the aggregation period for metrics.
$amaJunkRecords = Specifies the number of junk records found in the header of
the AMA file.
$amapath = Specifies the path of the AMA output files.
$amadir = Specifies the location of the AMA output files.
$ipdrpath = Specifies the path of the temporary data store for IPDR files.
$ipdrdir = Specifies the location of the temporary data store for IPDR
files.
$numberOfOutputs = Specifies the number of separate output streams that will be
created for processing by separate UBA collectors.
$outputDir = Specifies the location of the CSV output files. The CSV files
use the suffix n.csv, where n is the number of the stream of
CSV files so the appropriate UBA can locate its input files via
the Input URI filter.
$exceptDir = Specifies the location of the exception output directory.
6. In the cs2kcdr-config.pl script locate the values for our $cdrConfig and edit the parameters
according to the requirements of your environment. The following table provides descriptions of the
our $cdrConfig parameters:
7. Locate the our $trunkConfig section of the cs2kcdr-config.pl script and edit the parameters
according to the requirements of your environment. The following table provides a description of the
parameter:
8. Locate the our $locationMap section of the cs2kcdr-config.pl script and edit the parameters
according to the requirements of your environment. The following table provides descriptions of the our
$locationMap parameters:
9. Once you are finished with your edits, write and quit the cs2kcdr-config.pl file.
10. Run the cs2kcdr.pl script.
$storeExceptionDetail = Specifies which termination codes are to be written to a
separate output file for examination.
$terminationCodeHash = Specifies the list of termination codes.
name Specifies a string that represents the identifier for the remote Nortel CS2000 servers.
This string should match the <SOFTSWITCH_NAME> value that is part of the
Universal Resource Identifier (URI) associated with the data source. Nortel CS2000
binary Automatic Message Accounting (AMA) file names are something like:
CS2K_<DDMMYYYY>_<NUMBER>_<SOFTSWITCH_NAME>.bin.
location
Specifies a string that represents the location for where the remote Nortel
CS2000 servers are installed.
zone
Specifies a string that represents the H.323 Zone for the remote Nortel
CS2000 servers.
name Specifies a string that represents the identifier for the remote Nortel
Communication Server 2000 (CS2K) Softswitch Trunks.
extensionPattern
Specifies the extension pattern for a CDR location.
extensionRange
Specifies an extension range for a CDR location.
NOTES
Appendix E: Reports Examples
Overview
The Nortel CS2000 Technology Pack supplies a set of reports suitable for displaying information about the
devices and activity associated with the Nortel CS2000 environment. This appendix provides examples of reports
for the Nortel CS2000 Technology Pack.
For information about understanding report types, creating reports, configuring reports, viewing and working
with reports, and deploying reports, see the Netcool/Proviso DataView Users Guide.
Note: The contents of the reports shown and discussed in this Technology Pack Users Guide may not match the
contents of the reports distributed with this release of the Technology Pack.
Report Navigation Tree
The Nortel CS2000 Technology Pack defines the report navigation tree with the main report groupings as shown
in Figure 4.
Note: The report navigation tree discussed in this and subsequent sections uses the tree structure provided by
the Netcool/Proviso DataMart Resource Editor.
Topic Page
Overview 811
Report Navigation Tree 811
VOIP Dashboard 829
Infrastructure Reports 830
User Experience Reports 850
Figure 4: NOC Reporting Tree Main Groupings
Figure 4 shows the NOC reporting tree for the Nortel CS2000 Technology Pack-related reports has the following
main report groupings:
Infrastructure
User Experience
The figure also shows that at the Carrier VOIP group level, users can choose the VOIP Dashboard.
The following sections briefly describe the these main report groupings.
Infrastructure
Figure 5 shows that the NOC Reporting->Carrier VOIP->Infrastructure report group level of the NOC reporting
tree has the following levels:
IP Centrex
Media Gateways
Media Servers
Signaling Gateways
Softswitch Platform
Figure 5: NOC Reporting Tree Infrastructure Level
Each of these levels is discussed in the following sections.
IP Centrex
Figure 6 shows that the NOC Reporting->Carrier VOIP->Infrastructure->IP Centrex level has an additional level
(->Nortel CICM) that allows users to select the Client Manager Quality report for Nortel Centrex IP Client
Manager (CICM) devices that operate in the Nortel CS2000 environment.
Figure 6: NOC Reporting Tree IP Centrex Level
Media Gateways
Figure 7 shows that the NOC Reporting->Carrier VOIP->Infrastructure->Media Gateways level has the following
additional levels:
Nortel PVG The Nortel PVG level offers four additional levels:
Card
Device
Interface
VSP
Figure 7: NOC Reporting Tree Media Gateways Level
Figure 8 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Media Gateways->Nortel PVG-
>Card level, users can select the PVG Card Quality and PVG Card Temperature reports.
Figure 8: NOC Reporting Tree Media Gateways->Nortel PVG->Card Level
>Device level, users can select the PVG Device Usage and PVG Device Call Signaling reports.
Figure 9: NOC Reporting Tree Media Gateways->Nortel PVG->Device Level
>Interface level, users can select the PVG Interface Usage report.
Figure 10: NOC Reporting Tree Media Gateways->Nortel PVG->Interface Level
>VSP level, users can select the PVG VSP Call Signaling and PVG VSP Quality reports.
Figure 11: NOC Reporting Tree Media Gateways->Nortel PVG->VSP Level
Media Servers
Figure 12 shows that the NOC Reporting->Carrier VOIP->Infrastructure->Media Servers level has the following
additional levels:
Nortel AMS The Nortel AMS level offers two additional levels:
Device
RAS Port
Nortel MS20xx Device
Figure 12: NOC Reporting Tree Media Servers Level
Figure 13 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Media Servers->Nortel AMS-
>Device level, users can select the System Performance and Stream Quality reports.
Figure 13: NOC Reporting Tree Media Servers->Nortel AMS->Device Level
Figure 14 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Media Servers->Nortel AMS->RAS
Port level, users can select the RAS Port Statistics report.
Figure 14: NOC Reporting Tree Media Servers->Nortel AMS->RAS Port
Figure 15 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Media Servers->Nortel MS20xx
Device level, users can select the MS2010 Device Quality and MS2010 RTP - MP Analysis reports.
Figure 15: NOC Reporting Tree Media Servers->Nortel MS20XX Level
Signaling Gateways
Figure 16 shows that the NOC Reporting->Carrier VOIP->Infrastructure->Signaling Gateways level has the
following additional levels:
Nortel USP The Nortel USP level offers four additional levels:
Device
Link
Linkset
Routeset
Figure 16: NOC Reporting Tree Signaling Gateways Level
Figure 17 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Signaling Gateways->Nortel USP-
>Device level, users can select the USP Device Quality report.
Figure 17: NOC Reporting Tree Signaling Gateways->Nortel USP->Device Level
>Link level, users can select the USP Link Quality report.
Figure 18: NOC Reporting Tree Signaling Gateways->Nortel USP->Link Level
>Linkset level, users can select the USP Linkset Quality report.
Figure 19: NOC Reporting Tree Signaling Gateways->Nortel USP->Linkset Level
>Routeset level, users can select the USP Routeset Metrics report.
Figure 20: NOC Reporting Tree Signaling Gateways->Nortel USP->Routeset Level
Softswitch Platform
Figure 21 shows that the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform level has the
following additional levels:
Nortel CS2K
Nortel SAM21
Nortel SPC
Figure 21: NOC Reporting Tree Softswitch Platform Level
Figure 22 shows that the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform->Nortel CS2K
level has the following additional levels:
Device
Trunk
Figure 22: NOC Reporting Tree Softswitch Platform->Nortel CS2K Level
Figure 23 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform->Nortel CS2K-
>Device level, users can select the CS2K Device Quality report.
Figure 23: NOC Reporting Tree Softswitch Platform->Nortel CS2K->Device Level
Figure 24 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform->Nortel CS2K-
>Trunk level, users can select the CS2K Trunk Quality report.
Figure 24: NOC Reporting Tree Softswitch Platform->Nortel CS2K->Trunk Level
Figure 25 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform->Nortel
SAM21 level, users can select the SAM21 Device Quality report.
Figure 25: NOC Reporting Tree Softswitch Platform->Nortel SAM21
Figure 26 shows that at the NOC Reporting->Carrier VOIP->Infrastructure->Softswitch Platform->Nortel SPC
level, users can select the Session Policy Controller Quality report.
Figure 26: NOC Reporting Tree Softswitch Platform->Nortel SPC Level
User Experience
Figure 27 shows that the NOC Reporting->Carrier VOIP->User Experience report group level of the NOC
reporting tree has the following levels:
User Experience->Call Signaling Level
User Experience->Service Usage Level
User Experience->Voice Quality Level
Note: An Active Testing level is shown n figures discussed in subsequent sections. See the Netcool/Proviso
Radcom Omni-Q Technology Pack Users Guide for descriptions of the reports that display at the Active Testing
levels of the NOC Reporting Tree.
Figure 27: NOC Reporting Tree User Experience Level
The following sections discuss each of these levels.
User Experience->Call Signaling Level
Figure 28 shows that the NOC Reporting->Carrier VOIP->User Experience->Call Signaling report group level of
the NOC reporting tree has the following levels:
CDR/IPDR The CDR/IPDR level has a Nortel CS2K level that offers two additional levels:
Call Setup Quality
Termination Cause
Figure 28: NOC Reporting Tree User Experience->Call Signaling Level
Figure 29 shows that at the NOC Reporting->Carrier VOIP->User Experience->Call Signaling->Call Setup
Quality level, users can select the TypeOfCall Call Setup and Termination report.
Figure 29: NOC Reporting Tree User Experience->Call Signaling->Call Setup Quality Level
Figure 30 shows that at the NOC Reporting->Carrier VOIP->User Experience->Call Signaling->Termination
Cause level, users can select the Termination Cause Analysis report.
Figure 30: NOC Reporting Tree User Experience->Call Signaling->Termination Cause Level
User Experience->Service Usage Level
Figure 31 shows that the NOC Reporting->Carrier VOIP->User Experience->Service Usage report group level of
CDR/IPDR The CDR/IPDR level offers seven additional levels:
By Customer Profile
By Extension
By Media Gateway
By Path
By Softswitch
By Zone
Call Distribution
Figure 31: NOC Reporting Tree User Experience->Service Usage Level
Figure 32 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Customer
Profile level, users can select the Customer Profile Analysis report.
Figure 32: NOC Reporting Tree User Experience->User Experience->Service Usage Level->By
Customer Profile Level
Figure 33 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Extension
level, users can select the Extension Utilization report.
Extension Level
Figure 34 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Media
Gateway level, users can select the MGW Call Utilization report.
Media Gateway Level
Figure 35 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Path level,
users can select the Path Call Utilization report.
Figure 35: NOC Reporting Tree User Experience->User Experience->Service Usage Level->By Path
Level
Figure 36 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Softswitch
level, users can select the Softswitch Call Utilization - MLH and Softswitch Call Utilization reports.
Softswitch Level
Figure 37 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->By Zone level,
users can select the Zone Utilization report.
Figure 37: NOC Reporting Tree User Experience->User Experience->Service Usage Level->By Zone
Level
Figure 38 shows that at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->Call Distribution
level, users can select the Call Distribution Analysis report.
Figure 38: NOC Reporting Tree User Experience->User Experience->Service Usage Level->Call
Distribution Level
User Experience->Voice Quality Level
Figure 39 shows that the NOC Reporting->Carrier VOIP->User Experience->Voice Quality report group level of
CDR/IPDR The CDR/IPDR level has a Nortel CS2K level that offers two additional levels:
Extension
Location
Softswitch Quality
Figure 39: NOC Reporting Tree User Experience->Voice Quality Level
Figure 40 shows that at the NOC Reporting->Carrier VOIP->User Experience->Voice Quality->Extension level,
users can select the Extension Quality report.
Figure 40: NOC Reporting Tree User Experience->User Experience->Voice Quality->Extension
Level
Figure 41 shows that at the NOC Reporting->Carrier VOIP->User Experience->Voice Quality->Location level,
users can select the Voice Quality Report and SLA Voice Quality Report.
Figure 41: NOC Reporting Tree User Experience->User Experience->Voice Quality->Location Level
Figure 42 shows that at the NOC Reporting->Carrier VOIP->User Experience->Voice Quality->Softswitch
Quality level, users can select the Voice Quality report.
Figure 42: NOC Reporting Tree User Experience->User Experience->Voice Quality->Softswitch
Quality Level
VOIP Dashboard
A Technology Pack Dashboard is a mechanism for providing a series of charts and reports that give users a quick
view into the performance and quality metrics relevant to the devices and technology that the Technology Pack
supports. The Nortel CS2000 Technology Pack, like other Netcool/Proviso Technology Packs, provides a
Dashboard unique to the devices and technologies that it supports namely Nortel CS2000.
This Technology Pack Users Guide does not provide any details about the reports and charts that make up the
Nortel CS2000 Dashboard. See the sections in this chapter that describe the specific reports and charts.
The Nortel CS2000 Technology Pack provides the dashboard shown in Figure 43.
Figure 43: VOIP Dashboard
Infrastructure Reports
The Nortel CS2000 Technology Pack provides the following report groups at the NOC Reporting->Carrier
VOIP->Infrastructure level of the NOC reporting tree:
IP Centrex Reports
Media Gateways Reports
Media Servers Reports
Signaling Gateways Reports
Softswitch Platform Reports
The following sections give examples of the reports associated with each of these groups.
IP Centrex Reports
The Nortel CS2000 Technology Pack provides the following report at the NOC Reporting->Carrier VOIP-
>Infrastructure->IP Centrex->Nortel CICM level of the NOC reporting tree:
Client Manager Quality Example
Client Manager Quality Example
Figure 44 shows an example of the Client Manager Quality report.
Figure 44: Client Manager Quality
As the figure shows, the Client Manager Quality displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel CICM
device. See Nortel CICM Sub-Element Name on page 180 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel CICM sub-element name.
Percentage CPU Used The Percentage CPU Used metric is obtained by the PercentageCpuUsed
collection formula. The PercentageCpuUsed collection formula calculates the percentage of the CPU
utilized on this Nortel CICM device.
Percentage Memory Used The Percentage Memory Used metric is obtained by the
PercentageMemoryUsed collection formula. The PercentageMemoryUsed collection formula
calculates the percentage of the CPU memory utilized on this Nortel CICM device.
Active Connections The Active Connections metric is obtained by the ActiveConnections collection
formula. The ActiveConnections collection formula counts the number of currently active connections
on this Nortel CICM device.
Active Sessions The Active Sessions metric is obtained by the ActiveSessions collection formula. The
ActiveSessions collection formula counts the number of currently active sessions on this Nortel CICM
device.
Half Call Attempts The Half Call Attempts metric is obtained by the HalfCallAttempts collection
formula. The HalfCallAttempts collection formula counts the number of half call attempts on this
Nortel CICM device.
Logged In Users The Logged In Users metric is obtained by the LoggedInUsers collection formula.
The LoggedInUsers collection formula counts the number of users logged into this Nortel CICM device.
See Bulk Collection Formulas on page 191 for more information on these Bulk collection formulas.
Users can drill to the Client Manager Quality - DC charts by selecting a Nortel CICM listed in the Name column.
Media Gateways Reports
The Media Gateways reports display quality, temperature, device usage, and call usage metrics associated with call
activity that occurs on a Passport Packet Voice Gateway (PVG) device. The PVG device operating in the Nortel
CS2000 environment is the Passport 1500 Multiservice switch. See Nortel SST on page 146 for a brief description
of this PVG device.
The Nortel CS2000 Technology Pack provides the following reports at the NOC Reporting->Carrier VOIP-
>Infrastructure->Media Gateways->Nortel PVG level of the NOC reporting tree:
Nortel PVG Card
PVG Card Quality Example
PVG Card Temperature Example
Nortel PVG Device
PVG Device Usage Example
PVG Device Call Signaling Example
PVG Interface Usage Example
Nortel PVG VSP
PVG VSP Call Signaling Example
PVG VSP Quality Example
The following sections give examples of each of these reports.
PVG Card Quality Example
Figure 45 shows an example of a PVG Card Quality report.
Figure 45: PVG Card Quality
As Figure 45 shows, the PVG Card Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Media Gateway
Shelf Card (SC) component of a PVG device. See Media Gateway SC Sub-Element Name on page 184 for an
explanation of the syntax the Nortel CS2000 Technology Pack uses to define a Media Gateway SC sub-
element name.
CPU Utilization (percent) The CPU Utilization (percent) metric is obtained by the CardUtilAvg
collection formula. The CardUtilAvg collection formula calculates the average CPU utilization percentage
(0 to 100 percent) of the control processor card associated with this Media Gateway SC operating on this
PVG device.
Message Block in Use (percent) The CPU Utilization (percent) metric is obtained by the LMBUtil
collection formula. The LMBUtil collection formula calculates the average percentage (0 to 100 percent)
of local message blocks in use on this Media Gateway SC operating on this PVG device.
Users can drill down to the PVG Card Quality - DC charts (Shelf Card CPU Usage (percent) and Local Message
Block in Use (percent) by selecting a Media Gateway SC listed in the Name column.
PVG Card Temperature Example
Figure 46 shows an example of a PVG Card Temperature report.
Figure 46: PVG Card Temperature
As Figure 46 shows, the PVG Card Temperature report displays the following information and metrics:
Fabric Card (FC) component of a PVG device. See Media Gateway FC Sub-Element Name on page 184 for an
explanation of the syntax the Nortel CS2000 Technology Pack uses to define a Media Gateway FC sub-
element name.
Temperature (degree Celsius) The Temperature (degree Celsius) metric is obtained by the MaxTemp
collection formula. The MaxTemp collection formula obtains the maximum temperature, in degrees (0 to
100) Celsius of the Media Gateway Fabric Card (FC) component of a PVG device, during the last interval.
See Bulk Collection Formulas on page 191 for more information on this formula.
Users can drill down to the PVG Card Temperature - DC chart by selecting a Media Gateway FC listed in the
Name column.
PVG Device Usage Example
Figure 47 shows an example of a PVG Device Usage report and associated bar graphs.
Figure 47: PVG Device Usage
As Figure 47 shows, the PVG Device Usage report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Passport Packet
Voice Gateway (PVG) device. See PVG Device Sub-Element Name on page 184 for an explanation of the syntax
the Nortel CS2000 Technology Pack uses to define a PVG sub-element name.
ShelfCard CPU Usage (percent) The ShelfCard CPU Usage (percent) metric is obtained by the
AvgCPUutilizationCardProcessing collection formula. The
AvgCPUutilizationCardProcessing collection formula calculates the average CPU utilization
percentage (0 to 100 percent) of all Media Gateway Shelf Cards operating on this PVG device.
VSP CPU Usage (percent) The VSP CPU Usage (percent) metric is obtained by the
AvgCPUutilizationVSPCard collection formula. The AvgCPUutilizationVSPCard collection
formula calculates the average CPU utilization (0 to 100 percent) of the processing component of the on-
board processor on the Media Gateway VSP Card Processor (CP) card associated with this PVG device.
Packets (Nb) The Packets (Nb) metric is obtained by the TotalPackets collection formula. The
TotalPackets collection formula counts the total number of packets incoming to and outgoing from the
Media Gateway Interface (MGI) associated with this PVG device.
Active Calls (Nb) The Active Calls (Nb) metric is obtained by the TotalActiveCalls collection
formula. The TotalActiveCalls collection formula counts the total number of media connections
successfully established by the Media Gateway Shelf Card (SC) associated with this PVG device and
acknowledged by the Media Gateway Controller (MGC) during the past interval. In this case, the Active Calls
(Nb) metric refers to the ATM cell activity that occurs on a Media Gateway Controller (MGC) component
of a PVG device.
Minutes Of Use (min) The Minutes Of Use (min) metric is obtained by the TotalMinutesOfUse
collection formula. The TotalMinutesOfUse collection formula counts the total average number of
active media calls that the device, interface, or card handles. In this case, the Minutes Of Use (min) metric
refers to the call activity that occurs on a Media Gateway Controller (MGC) component of a PVG device.
Failovers The Failovers metric is obtained by the Failovers collection formula. The Failovers
collection formula counts the total number of failover procedures. Specifically, this refers to the number of
times a Media Gateway Controller Card performs failover procedures and attempts contact with another
controller.
Figure 47 also shows that the TDM vs IP Network Failure Ratio and TCP-UDP-ICMP Packets Ratio charts
display the following metrics:
TDMCallFailures The TDMCallFailures metric is obtained by the TDMCallFailures collection
formula. The TDMCallFailures collection formula counts the total number of failover procedures.
Specifically, this refers to the number of times a Media Gateway Controller Card performs failover
procedures and attempts contact with another controller.
NetworkCallFailure The NetworkCallFailure metric is obtained by the NetworkCallFailure
collection formula. The NetworkCallFailure collection formula counts the total number of
connections lost to Gateway detectable network failures in the IP core, during the last interval.
TotalTCPPackets The TotalTCPPackets metric is obtained by the TotalTCPPackets collection
formula. The TotalTCPPackets collection formula counts the total number of Transmission Control
Protocol (TCP) packets incoming to and outgoing from this IP Interface. This IP interface connects to this
PVG device.
TotalUDPPackets The TotalUDPPackets metric is obtained by the TotalUDPPackets collection
formula. The TotalUDPPackets collection formula counts the total number of User Datagram Protocol
(UDP) packets incoming to and outgoing from the Media Gateway Interface (MGI) associated with this
PVG device.
TotalICMPPackets The TotalICMPPackets metric is obtained by the TotalICMPPackets collection
formula. The TotalICMPPackets collection formula counts the total number of Internet Control
Message Protocol (ICMP) packets incoming to and outgoing from this IP Interface. This IP interface
connects to this PVG device.
Users can drill down to the PVG Device Usage - DC charts by selecting a PVG device listed in the Name column.
PVG Device Call Signaling Example
Figure 48 shows an example of a PVG Device Call Signaling report.
Figure 48: PVG Device Call Signaling
As Figure 48 shows, the PVG Device Call Signaling report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Passport Packet
Voice Gateway (PVG) device. See PVG Device Sub-Element Name on page 184 for an explanation of the syntax
the Nortel CS2000 Technology Pack uses to define a PVG sub-element name.
Congested Seconds (sec) The CongestedSeconds metric is obtained by the CongestedSeconds
collection formula. The CongestedSeconds collection formula counts the total number of seconds
during which new media connection requests are rejected because the card is busy.
H248 Retransmissions (Nb) The H248Retransmission metric is obtained by the H248Retransmission
collection formula. The H248Retransmission collection formula counts the total number of H248
retransmissions that occurred on the device.
Successful Calls (Nb) The Successful Calls (Nb) metric is obtained by the TotalSuccessfulCalls
collection formula. The TotalSuccessfulCalls collection formula counts the total number of
successful calls that this device, interface, or card handles.
Failovers (Nb) The Failovers (Nb) metric is obtained by the Failovers collection formula. The
Failovers collection formula counts the total number of failover procedures. Specifically, this refers to
the number of times a Media Gateway Controller Card performs failover procedures and attempts contact
with another controller.
Overload Cmd Rejects (Nb) The Overload Cmd Rejects (Nb) metric is obtained by the
OverloadCmdRejected collection formula. The OverloadCmdRejected collection formula counts
the total number of Media Gateway Control Protocol commands that are rejected due to overload of the
input message buffer.
active media calls that the device, interface, or card handles.
Users can drill down to the PVG Device Call Signaling - DC charts by selecting a PVG device listed in the Name
column.
PVG Interface Usage Example
Figure 49 shows an example of a PVG Interface Usage report.
Figure 49: PVG Interface Usage
As Figure 49 shows, the PVG Interface Usage report displays the following information and metrics:
Interface (MGI) component of a PVG device. See MGI Sub-Element Name on page 185 for an explanation of
the syntax the Nortel CS2000 Technology Pack uses to define a MGI sub-element name.
Average Inbound Utilization The Average Inbound Utilization metric is obtained by the
AverageInboundUtilization collection formula. The AverageInboundUtilization collection
formula calculates the average number of bytes incoming to the physical interface. In this case, the Average
Inbound Utilization metric refers to the usage activity that occurs on a Media Gateway Interface (MGI)
component of a PVG device.
Average Outbound Utilization The Average Outbound Utilization metric is obtained by the
AverageOutboundUtilization collection formula. The AverageOutboundUtilization
collection formula calculates the average number of bytes outgoing from the physical interface. In this case,
the Average Outbound Utilization metric refers to the usage activity that occurs on a Media Gateway
Interface (MGI) component of a PVG device.
Total Packets Discarded The Total Packets Discarded metric is obtained by the
TotalNumberOfDiscardedPackets collection formula. The TotalNumberOfDiscardedPackets
collection formula counts the total number of discarded packets incoming to and outgoing from the physical
interface. In this case, the Total Packets Discarded metric refers to the usage activity that occurs on a Media
Gateway Interface (MGI) component of a PVG device.
Total Packet Exceptions The Total Packet Exceptions metric is obtained by the
TotalNumberOfPacketExceptions collection formula. The TotalNumberOfPacketExceptions
collection formula calculates the total number of exception packets received by the physical interface. These
exception packets include ICMP, host redirect, and forwarding. In this case, the Total Packet Exceptions
metric refers to the usage activity that occurs on a Media Gateway Interface (MGI) component of a PVG
device. Abnormally high counts of exception packets can indicate a denial of service attack or a broken route
in the network.
TotalTCPPackets The TotalTCPPackets metric is obtained by the TotalNumberOfTCPPackets
collection formula. The TotalNumberOfTCPPackets collection formula counts the total number of
Transmission Control Protocol (TCP) packets incoming to and outgoing from the physical interface. In this
case, the TotalTCPPackets metric refers to the usage activity that occurs on a Media Gateway Interface
(MGI) component of a PVG device.
TotalUDPPackets The TotalUDPPackets metric is obtained by the TotalNumberOfUDPPackets
collection formula. The TotalNumberOfUDPPackets collection formula counts the total number of User
Datagram Protocol (UDP) packets incoming to and outgoing from the physical interface. In this case, the
TotalUDPPackets metric refers to the usage activity that occurs on a Media Gateway Interface (MGI)
Users can drill to the PVG Interface Usage - DC charts by selecting a specific MGI listed in the Name column.
PVG VSP Call Signaling Example
Figure 50 shows an example of a PVG VSP Call Signaling report.
Figure 50: PVG VSP Call Signaling
As Figure 50 shows, the PVG VSP Call Signaling report displays the following information and metrics:
VSP CC component of a PVG device. See Media Gateway VSP CC Sub-Element Name on page 186 for an
explanation of the syntax the Nortel CS2000 Technology Pack uses to define a Media Gateway VSP PC sub-
element name.
Congested Seconds (sec) The Congested Seconds (sec) metric is obtained by the CongestedSeconds
collection formula. The CongestedSeconds collection formula counts the total number of seconds
during which new media connection requests are rejected because the card is busy. In this case, the Congested
Seconds (sec) metric refers to the usage activity that occurs on a Media Gateway VSP CC component of a
PVG device.
H248 Retransmissions (Nb) The H248 Retransmissions (Nb) metric is obtained by the
H248Retransmission collection formula. The H248Retransmission collection formula counts the
total number of H248 retransmissions that occurred on the device. In this case, the H248 Retransmissions
(Nb) metric refers to the usage activity that occurs on a Media Gateway VSP CC component of a PVG
device.
Successful Calls (Nb) The Successful Calls (Nb) metric is obtained by the TotalSuccessfulCalls
collection formula. The TotalSuccessfulCalls collection formula counts the average number of active
media calls handled by this card. In this case, the Successful Calls (Nb) metric refers to the usage activity that
occurs on a Media Gateway VSP CC component of a PVG device.
Failovers (Nb) The Failovers (Nb) metric is obtained by the Failovers collection formula. The
Failovers collection formula counts the total number of times a Media Gateway card performs failover
procedures and attempts contact with another controller, since the time an H.248 component is activated.
In this case, the Failovers (Nb) metric refers to the usage activity that occurs on a Media Gateway VSP CC
Overload Cmd Rejects (Nb) The Overload Cmd Rejects (Nb) metric is obtained by the
OverloadCmdRejected collection formula. The OverloadCmdRejected collection formula counts
the total number of Media Gateway Control Protocol commands that are rejected due to overload of the
input message buffer. In this case, the Overload Cmd Rejects (Nb) metric refers to the usage activity that
occurs on a Media Gateway VSP CC component of a PVG device.
active media calls that the device, interface, or card handles. In this case, the Minutes Of Use (min) metric
refers to the usage activity that occurs on a Media Gateway VSP CC component of a PVG device.
Figure 50 also shows the metrics associated with the TDM vs IP Network Failure Ratio bar graph:
TotalTDMCallFails (percent) The TotalTDMCallFails (percent) metric is obtained by the
TotalTDMCallFails collection formula. The TotalTDMCallFails collection formula counts the
total number of connections lost due to failure of a time division multiplexing (TDM) port, internal failure,
or deletion of a TDM port since the component was created. In this case, the TotalTDMCallFails (percent)
metric refers to the usage activity that occurs on a Media Gateway VSP CC component of a PVG device.
NetworkCallFailure (percent) The NetworkCallFailure (percent) metric is obtained by the
TotalNetworkCallFails collection formula. The TotalNetworkCallFails collection formula
counts the number of connections lost to Media Gateway-detectable network failures in the IP core, during
the last interval. In this case, the NetworkCallFailure (percent) metric refers to the usage activity that occurs
on a Media Gateway VSP CC component of a PVG device.
Users can drill down to the PVG VSP Call Signaling - DC charts by selecting a Media Gateway VSP CC listed in
the Name column.
PVG VSP Quality Example
Figure 51 shows an example of a PVG VSP Quality report.
Figure 51: PVG VSP Quality
As Figure 51 shows, the PVG VSP Quality report displays the following information and metrics:
VSP PC component of a PVG device. See Media Gateway VSP PC Sub-Element Name on page 186 for an
explanation of the syntax the Nortel CS2000 Technology Pack uses to define a Media Gateway VSP PC sub-
element name.
CPU Utilization (percent) The CPU Utilization (percent) metric is obtained by the
AvgCPUutilizationVSPCard collection formula. The AvgCPUutilizationVSPCard collection
formula calculates the average CPU utilization of the on-board processor on the VSP card. In this case, the
CPU Utilization (percent) metric refers to the usage activity that occurs on a Media Gateway VSP PC
See Bulk Collection Formulas on page 191 for more information on this Bulk collection formula.
Users can drill down to the PVG VSP Quality - DC charts by selecting a Media Gateway VSP PC listed in the
Name column.
Media Servers Reports
>Infrastructure->Media Servers->Nortel AMS level of the NOC reporting tree:
Device
System Performance Example
Stream Quality Example
RAS port
RAS Port Statistics Example
>Infrastructure->Media Servers->Nortel MS20xx Device level of the NOC reporting tree:
MS2010 Device Quality Example
MS2010 RTP - MP Analysis Example
System Performance Example
Figure 52 shows an example of a System Performance report.
Figure 52: System Performance
As Figure 52 shows, the System Performance report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel AMS
device. See Nortel AMS Sub-Element Name on page 179 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel AMS sub-element name.
Context Switches per second The Context Switches per second metric is obtained by the Context
Switches/sec collection formula. The Context Switches/sec collection formula calculates the
number of context switches, per second, handled by this Nortel AMS device.
Exception Dispatches per second The Exception Dispatches per second metric is obtained by the
Exception Dispatches/sec collection formula. The Exception Dispatches/sec collection
formula calculates the number of exception dispatches, per second, handled by this Nortel AMS device.
File Control Bytes per second The File Control Bytes per second metric is obtained by the File
Control Bytes/sec collection formula. The File Control Bytes/sec collection formula calculates
the number of file control bytes, per second, handled by this Nortel AMS device.
File Control Operations per second The File Control Operations per second metric is obtained by the
File Control Operations/sec collection formula. The File Control Operations/sec
collection formula calculates the number of file control operations, per second, handled by this Nortel AMS
device.
File Data Operations per second The File Data Operations per second metric is obtained by the File
Data Operations/sec collection formula. The File Data Operations/sec collection formula
calculates the number of file data operations, per second, handled by this Nortel AMS device.
System Calls per second The System Calls per second metric is obtained by the System Calls/sec
collection formula. The System Calls/sec collection formula calculates the number of system calls, per
second, handled by this Nortel AMS device.
Users can drill down to the System Performance - DC charts by selecting a Nortel AMS device listed in the Name
column.
Stream Quality Example
Figure 53 shows an example of a Stream Quality report.
Figure 53: Stream Quality
As Figure 53 shows, the Stream Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel AMS
device. See Nortel AMS Sub-Element Name on page 179 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel AMS sub-element name.
Total Files Transcoded The Total Files Transcoded metric is obtained by the TotalFilesTranscoded
collection formula. The TotalFilesTranscoded collection formula counts the total number of files
transcoded by this Nortel AMS device.
Active IVR MP Connections The Active IVR MP Connections metric is obtained by the
ActiveIvrMPConnections collection formula. The ActiveIvrMPConnections collection formula
counts the number of active Interactive Video Response (IVR) connections handled by this Nortel AMS
device.
Pending IVR MP Connections The Pending IVR MP Connections metric is obtained by the
PendingIvrMPConnections collection formula. The PendingIvrMPConnections collection
formula counts the number of pending Interactive Video Response (IVR) connections handled by this
Nortel AMS device.
Allocated Audio Buffers The Allocated Audio Buffers metric is obtained by the
AllocatedAudioBuffers collection formula. The AllocatedAudioBuffers collection formula
counts the number of allocated audio buffers handled by this Nortel AMS device.
Bytes Processed per second The Bytes Processed per second metric is obtained by the
BytesProcessedPerSecond collection formula. The BytesProcessedPerSecond collection
formula calculates the streamed byes processed, per second, by this Nortel AMS device.
Bytes Streamed per second The Bytes Streamed per second metric is obtained by the
BytesStreamedPerSecond collection formula. The BytesStreamedPerSecond collection formula
calculates the number of byes streamed, per second, by this Nortel AMS device.
Users can drill down to the Stream Quality - DC charts by selecting a Nortel AMS device listed in the Name
column.
RAS Port Statistics Example
Figure 54 shows an example of a RAS Port Statistics report.
Figure 54: RAS Port Statistics
As Figure 54 shows, the RAS Port Statistics report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel RAS
Port device. See Nortel RAS Port Sub-Element Name on page 181 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Nortel RAS Port sub-element name.
Bytes Received The Bytes Received metric is obtained by the Bytes Received collection formula. The
Bytes Received collection formula counts the number of bytes received on this Nortel RAS Port device.
Bytes Transmitted The Bytes Transmitted metric is obtained by the Bytes Transmitted collection
formula. The Bytes Transmitted collection formula counts the number of bytes transmitted on this
Nortel RAS Port device.
CRC Errors The CRC Errors metric is obtained by the CRC Errors collection formula. The CRC
Errors collection formula counts the number of CRC errors handled by this Nortel RAS Port device.
Buffer Overrun Errors The Buffer Overrun Errors metric is obtained by the Buffer Overrun Errors
collection formula. The Buffer Overrun Errors collection formula counts the number of buffer
overrun errors handled by this Nortel RAS Port device.
Timeout Errors The Timeout Errors metric is obtained by the Timeout Errors collection formula.
The Timeout Errors collection formula counts the number of RAS port timeout errors that occurred on
this Nortel RAS Port device.
Alignment Errors The Alignment Errors metric is obtained by the Alignment Errors collection
formula. The Alignment Errors collection formula counts the number of memory alignment errors that
occurred on this Nortel RAS Port device.
Users can drill down to the RAS Port Statistics - DC charts by selecting a Nortel RAS Port device listed in the
Name column.
MS2010 Device Quality Example
Figure 55 shows an example of a MS2010 Device Quality report.
Figure 55: MS2010 Device Quality
As Figure 55 shows, the MS2010 Device Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel MS 2010
device. See Nortel MS 20xx Device Sub-Element Name on page 181 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Nortel MS 2010 sub-element name.
BCT Requests The BCT Requests metric is obtained by the acPerfBctRequests collection formula.
The acPerfBctRequests collection formula counts the total number of BCT requests handled by this
Nortel MS 2010 device.
Conference Requests The Conference Requests metric is obtained by the acPerfConfRequests
collection formula. The acPerfConfRequests collection formula counts the total number of conference
requests handled by this Nortel MS 2010 device.
Play Collect Requests The Play Collect Requests metric is obtained by the
acPerfIvrPlayCollectRequests collection formula. The acPerfIvrPlayCollectRequests
collection formula counts the total number of Interactive Video Response (IVR) play collection requests
handled by this Nortel MS 2010 device.
Play Requests The Play Requests metric is obtained by the acPerfIvrPlayRequests collection
formula. The acPerfIvrPlayRequests collection formula counts the total number of Interactive Video
Response (IVR) play collection requests handled by this Nortel MS 2010 device.
TT Requests The TT Requests metric is obtained by the acPerfTtRequests collection formula. The
acPerfTtRequests collection formula counts the total number of TT requests handled by this Nortel MS
2010 device.
Endpoints In Use The Endpoints In Use metric is obtained by the
acPerfSystemPacketEndpointsInUse collection formula. The
acPerfSystemPacketEndpointsInUse collection formula counts the number of system packet
endpoints in use on this Nortel MS 2010 device.
Users can drill down to the MS2010 Device Quality - DC charts by selecting a Nortel MS 2010 device listed in
the Name column.
MS2010 RTP - MP Analysis Example
Figure 56 shows an example of a MS2010 RTP - MP Analysis report.
Figure 56: MS2010 RTP - MP Analysis
As Figure 56 shows, the MS2010 RTP - MP Analysis report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel MS 2010
device. See Nortel MS 20xx Device Sub-Element Name on page 181 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Nortel MS 2010 sub-element name.
RTP Failed Due To Lack Of Resources The RTP Failed Due To Lack Of Resources metric is obtained by
the acPerfRtpFailedDueToLackOfResources collection formula. The
acPerfRtpFailedDueToLackOfResources collection formula counts the number of RTP failures due
to lack of resources handled by this Nortel MS 2010 device.
RTP Receiver Lost Packets The RTP Receiver Lost Packets metric is obtained by the
acPerfRtpRcvrLostPackets collection formula. The acPerfRtpRcvrLostPackets collection
formula counts the number of RTP receiver lost packets handled by this Nortel MS 2010 device.
Users can drill down to the MS2010 RTP MP Analysis - DC charts by selecting a Nortel MS 2010 device listed
in the Name column.
Signaling Gateways Reports
The Signaling Gateway reports display performance metrics associated with call activity that occurs on a Universal
Signaling Point (USP). The USP is the Signaling Gateway component operating in the Nortel CS2000
environment.
>Infrastructure->Signaling Gateways->Nortel USP level of the NOC reporting tree:
Device
USP Device Quality Example
Link
USP Link Quality Example
Linkset
USP Linkset Quality Example
Routeset
USP Routeset Metrics Example
USP Device Quality Example
Figure 57 shows an example of a USP Device Quality report.
Figure 57: USP Device Quality
As Figure 57 shows, the USP Device Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the device
component of a USP. See USP Device Sub-Element Name on page 187 for an explanation of the syntax the
Nortel CS2000 Technology Pack uses to define a USP device sub-element name.
Total Messages Handled The Total Messages Handled metric is obtained by the
TotalMessagesHandled collection formula. The TotalMessagesHandled collection formula counts
the total number of messages handled by this USP device.
Total Messages Errors The Total Messages Errors metric is obtained by the TotalMessagesErrors
collection formula. The TotalMessagesErrors collection formula counts the total number of error
messages handled by this USP device. Examples of error messages include: Msg Incompatibility,
Routing Failure, Reassembly failed, etc.
Total Reassembly Failed The Total Reassembly Failed metric is obtained by the
TotalReassemblyFailed collection formula. The TotalReassemblyFailed collection formula
counts the total number of failed message reassembly attempts handled by this USP device.
Total Segmentation Failed The Total Segmentation Failed metric is obtained by the
TotalSegmentationFailed collection formula. The TotalSegmentationFailed collection
formula counts the total number of segmentation failures handled by this USP device.
Total GTT Performed The Total GTT Performed metric is obtained by the TotalGTTPerformed
collection formula. The TotalGTTPerformed collection formula counts the total number of Global Title
Translations (GTT) handled by this USP device.
Total Connection Messages Handled The Total Connection Messages Handled metric is obtained by the
TotalConnectionOrientedMessagesHandled collection formula. The
TotalConnectionOrientedMessagesHandled collection formula counts the total number of
connection messages handled by this USP device.
Users can drill to the USP Device Quality - DC charts by selecting a USP device listed in the Name column.
USP Link Quality Example
Figure 58 shows an example of a USP Link Quality report.
Figure 58: USP Link Quality
As Figure 58 shows, the USP Link Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the carrier link
component of a USP device. See USP Carrier Link Sub-Element Name on page 189 for an explanation of the
syntax the Nortel CS2000 Technology Pack uses to define a USP carrier link sub-element name.
Link Utilization (percent) The Link Utilization (percent) metric is obtained by the LinkUtilization
collection formula. The LinkUtilization collection formula calculates the percentage of link utilization
on this USP link.
Link Failures The Link Failures metric is obtained by the LinkFailureAllReasons collection
formula. The LinkFailureAllReasons collection formula counts the total number of link failures on
this USP link.
Link Unavailable Duration The Link Unavailable Duration metric is obtained by the
LinkUnavailableDuration collection formula. The LinkUnavailableDuration collection
formula calculates the duration of layer 1 unavailability on this USP link.
Line Errored Seconds The Line Errored Seconds metric is obtained by the LineErroredSeconds
collection formula. The LineErroredSeconds collection formula counts the total number of line errored
seconds on this USP link.
Line Severely Errored Seconds The Line Severely Errored Seconds metric is obtained by the
LineSeverelyErroredSeconds collection formula. The LineSeverelyErroredSeconds
collection formula counts the total number of line severely errored seconds on this USP link.
Line Code Violations The Line Code Violations metric is obtained by the LineCodeViolations
collection formula. The LineCodeViolations collection formula counts the total number of line code
violations on this USP link.
Users can drill to the USP Link Quality - DC charts by selecting a USP carrier link listed in the Name column.
USP Linkset Quality Example
Figure 59 shows an example of a USP Linkset Quality report.
Figure 59: USP Linkset Quality
As Figure 59 shows, the USP Linkset Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the linkset
component of a USP device. See USP Linkset Sub-Element Name on page 188 for an explanation of the syntax
the Nortel CS2000 Technology Pack uses to define a USP linkset sub-element name.
Transfer Control Transmitted The Transfer Control Transmitted metric is obtained by the
TransferControlledTransmitted collection formula. The TransferControlledTransmitted
collection formula counts the number of Transfer Controlled messages transmitted on this USP linkset.
RST Transmitted The RST Transmitted metric is obtained by the RSTTransmitted collection formula.
The RSTTransmitted collection formula counts the number of RST messages transmitted on this USP
linkset.
RST Received The RST Received metric is obtained by the RSTReceived collection formula. The
RSTReceived collection formula counts the number of RST messages received on this USP linkset.
Transfer Allowed Routing Avail Transmitted The Transfer Allowed Routing Avail Transmitted metric is
obtained by the TransferAllowedRoutingAvailableTransmitted collection formula. The
TransferAllowedRoutingAvailableTransmitted collection formula counts the total number of
messages transmitted informing that transfer requests are allowed and routing for destination is available on
this USP linkset.
Transfer Allowed Routing Avail Received The Transfer Allowed Routing Avail Received metric is obtained
by the TransferAllowedRoutingAvailableReceived collection formula. The
TransferAllowedRoutingAvailableReceived collection formula counts the total number of
messages received informing that transfer requests are allowed and routing for destination is available on this
USP linkset.
Linkset Inactivity Duration The Linkset Inactivity Duration metric is obtained by the
LinksetInactivityDuration collection formula. The LinksetInactivityDuration collection
formula counts the total duration of linkset inactivity on this USP linkset.
Users can drill to the USP Linkset Quality - DC charts by selecting a USP linkset listed in the Name column.
USP Routeset Metrics Example
Figure 60 shows an example of a USP Routeset Metrics report.
Figure 60: USP Routeset Metrics
As Figure 60 shows, the USP Routeset Metrics report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the routeset
component of a USP device. See USP Routeset Sub-Element Name on page 188 for an explanation of the syntax
the Nortel CS2000 Technology Pack uses to define a USP routeset sub-element name.
Total Routeset Manual Busy The Total Routeset Manual Busy metric is obtained by the
TotalRoutesetManualBusy collection formula. The TotalRoutesetManualBusy collection
formula counts the total number of times this USP routeset was manually busied.
Total Routeset Congested The Total Routeset Congested metric is obtained by the
TotalRoutesetCongested collection formula. The TotalRoutesetCongested collection formula
counts the total number of routeset congestion messages observed on this USP routeset.
Total Routeset Unavailability The Total Routeset Unavailability metric is obtained by the
TotalRoutesetUnavailability collection formula. The TotalRoutesetUnavailability
collection formula counts the total number of times that this USP routeset was found unavailable.
Total Routeset Unavailability Duration (seconds) The Total Routeset Unavailability Duration (seconds)
metric is obtained by the TotalRoutesetUnavailabilityDuration collection formula. The
TotalRoutesetUnavailabilityDuration collection formula counts the total number of seconds
that this USP routeset was unavailable.
Users can drill to the USP Routeset Metrics - DC charts by selecting a USP routeset listed in the Name column.
Softswitch Platform Reports
The Softswitch Platform reports display quality metrics associated with call activity that occurs on a Nortel
Communication Server 2000 (CS2K) Class 5 softswitch. The reports also display quality metrics associated with
a Nortel CS2000 Trunk.
>Infrastructure->Softswitch Platform->Nortel CS2K level of the NOC reporting tree:
Device
CS2K Device Quality Example
Trunk
CS2K Trunk Quality Example
>Infrastructure->Softswitch Platform->Nortel SAM21 level of the NOC reporting tree:
SAM21 Device Quality Example
>Infrastructure->Softswitch Platform->Nortel SPC level of the NOC reporting tree:
CS2K Device Quality Example
Figure 61 shows an example of a CS2K Device Quality report.
Figure 61: CS2K Device Quality
As Figure 61 shows, the CS2K Device Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel CS2000
device. See Nortel CS2000 Device Sub-Element Name on page 173 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Nortel CS2000 softswitch device sub-element name.
Active CPU Load - % The Active CPU Load - % metric is obtained by the
CPUutilizationForCallProcessing% collection formula. The
CPUutilizationForCallProcessing% collection formula calculates the percentage of CPU time spent
on call processing-related processes in a given time interval.
Total Successful Calls The Total Successful Calls metric is obtained by the
TotalSoftswitchSuccessfulCalls collection formula. The
TotalSoftswitchSuccessfulCalls collection formula counts the total number of successfully
completed calls made through this Nortel CS2000 softswitch or group of Nortel CS2000 softswitches.
Total Successful Calls % The Total Successful Calls % metric is obtained by the
TotalSoftswitchSuccessfulCalls% collection formula. The
TotalSoftswitchSuccessfulCalls% collection formula calculates the percentage of total successfully
completed calls made through this Nortel CS2000 softswitch or group of Nortel CS2000 softswitches.
Total Unsuccessful Calls The Total Unsuccessful Calls metric is obtained by the
TotalSoftswitchUnsuccessfulCalls collection formula. The
TotalSoftswitchUnsuccessfulCalls collection formula counts the total number of attempted calls
that terminated unsuccessfully through this Nortel CS2000 softswitch or group of Nortel CS2000
softswitches.
Total Unsuccessful Calls % The Total Unsuccessful Calls % metric is obtained by the
TotalSoftswitchUnsuccessfulCalls% collection formula. The
TotalSoftswitchUnsuccessfulCalls% collection formula calculates the percentage of total
attempted calls that terminated unsuccessfully through this Nortel CS2000 softswitch or group of Nortel
CS2000 softswitches.
Total Call Attempts The Total Call Attempts metric is obtained by the
TotalSoftswitchCallAttempts collection formula. The TotalSoftswitchCallAttempts
collection formula counts the total number of attempted calls made through this Nortel CS2000 softswitch
or group of Nortel CS2000 softswitches.
Users can drill to the CS2K Device Quality - DC charts by selecting a Nortel CS2000 softswitch device listed in
the Name column.
CS2K Trunk Quality Example
Figure 62 shows an example of a CS2K Trunk Quality report.
Figure 62: CS2K Trunk Quality
As Figure 62 shows, the CS2K Trunk Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the CS2K
Softswitch Trunk component of a Nortel CS2000 device. See CS2K Softswitch Trunk Sub-Element Name on
page 174 for an explanation of the syntax the Nortel CS2000 Technology Pack uses to define a CS2K
Softswitch Trunk sub-element name.
Incoming Successful Calls - % The Incoming Successful Calls - % metric is obtained by the
IncomingSuccessfulCalls% collection formula.The IncomingSuccessfulCalls% collection
formula calculates the percentage of inbound calls on this CS2K Softswitch Trunk or group of trunks that
completed successfully.
Outgoing Successful Calls - % The Outgoing Successful Calls - % metric is obtained by the
OutgoingSuccessfulCalls% collection formula. The OutgoingSuccessfulCalls% collection
formula calculates the percentage of outbound calls on this CS2K Softswitch Trunk or group of trunks that
completed successfully.
Total Trunk Routing Failure - % The Total Trunk Routing Failure - % metric is obtained by the
TotalCallTrunkRoutingFailure% collection formula. The TotalCallTrunkRoutingFailure%
collection formula calculates the percentage of total calls on this CS2K Softswitch Trunk or group of trunks
that failed due to trunk routing problems.
Incoming Answer Seizure Ratio - % The Incoming Answer Seizure Ratio - % metric is obtained by the
IncomingAnswerSeizureRatio% collection formula. The IncomingAnswerSeizureRatio%
collection formula calculates the ratio of inbound calls that were successfully answered to inbound calls that
were seized on this CS2K Softswitch Trunk or group of trunks.
Outing Answer Seizure Ratio - % The Outing Answer Seizure Ratio - % metric is obtained by the
OutgoingAnswerSeizureRatio% collection formula. The OutgoingAnswerSeizureRatio%
calculates the ratio of outbound calls that were successfully answered to outbound calls that were seized on
this CS2K Softswitch Trunk or group of trunks.
Total Call Bid Attempts The Total Call Bid Attempts metric is obtained by the TotalCallBidAttempts
collection formula. The TotalCallBidAttempts collection formula counts the total number of call bid
attempts on this CS2K Softswitch Trunk or group of trunks.
Users can drill to the CS2K Trunk Quality - DC charts by selecting a CS2K Softswitch Trunk listed in the Name
column.
SAM21 Device Quality Example
Figure 63 shows an example of a SAM21 Device Quality report.
Figure 63: SAM21 Device Quality
As Figure 63 shows, the SAM21 Device Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel SAM21
Shelf Controller device. See Nortel SAM21 Shelf Controller Sub-Element Name on page 182 for an explanation
of the syntax the Nortel CS2000 Technology Pack uses to define a Nortel SAM21 Shelf Controller sub-
element name.
Cell Drop Count The Cell Drop Count metric is obtained by the cellDropCount collection formula.
The cellDropCount collection formula counts the total number of cells dropped on this Nortel SAM21
Shelf Controller.
Oversized PDU Count The Oversized PDU Count metric is obtained by the oversizedPDUCount
collection formula. The oversizedPDUCount collection formula counts the number of oversized
Protocol Data Units (PDUs) on this Nortel SAM21 Shelf Controller.
Received Timeout Count The Received Timeout Count metric is obtained by the rxedTimeoutCount
collection formula. The rxedTimeoutCount collection formula counts the number of timeouts received
on this Nortel SAM21 Shelf Controller.
Bytes Received per second The Bytes Received per second metric is obtained by the bytesRxedPerSec
collection formula. The bytesRxedPerSec collection formula counts the number of bytes received, per
second, on this Nortel SAM21 Shelf Controller.
Bytes Transmitted per second The Bytes Transmitted per second metric is obtained by the
bytesSentPerSec collection formula. The bytesSentPerSec collection formula counts the number
of bytes sent, per second, from this Nortel SAM21 Shelf Controller.
Users can drill to the SAM21 Device Quality - DC charts by selecting a Nortel SAM21 Shelf Controller listed in
the Name column.
Figure 64 shows an example of a Session Policy Controller Quality report.
Figure 64: Session Policy Controller Quality
As Figure 64 shows, the Session Policy Controller Quality report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Nortel SPC
device. See Nortel SPC Sub-Element Name on page 182 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel SPC sub-element name.
Storage Allocation Failures The Storage Allocation Failures metric is obtained by the
hrStorageAllocationFailures collection formula. The hrStorageAllocationFailures
collection formula counts the number of storage allocation failures that occurred on this Nortel SPC.
Storage Used The Storage Used metric is obtained by the hrStorageUsed collection formula. The
hrStorageUsed collection formula calculates, in kilobytes, the amount of storage used on this Nortel SPC.
Users can drill to the Session Policy Controller Quality - DC charts by selecting a Nortel SPC listed in the Name
column.
User Experience Reports
The Nortel CS2000 Technology Pack provides the following report groups at the NOC Reporting->Carrier
VOIP->User Experience level of the NOC reporting tree:
Call Signaling CDR/IPDR Reports
Service Usage CDR/IPDR Reports
Voice Quality CDR/IPDR Reports
Note: See the Netcool/Proviso Radcom Omni-Q Technology Pack Users Guidee for information on the reports
located at the Active Testing levels of the NOC Reporting tree.
The following sections give examples of the reports associated with each of these reports groups.
Call Signaling CDR/IPDR Reports
The Call Signaling CDR/IPDR reports display performance metrics associated with call and termination cause
activity that occurs on a Nortel CS2000. The Nortel CS2000 is the Softswitch operating in the Nortel CS2000
environment.
The Nortel CS2000 Technology Pack provides the following reports at the NOC Reporting->Carrier VOIP->User
Experience->Call Signaling->CDR/IPDR->Nortel CS2K level of the NOC reporting tree:
Call Setup Quality
TypeOfCall Call Setup and Termination Example
Termination Cause
Termination Cause Analysis Example
The following sections discuss each of these reports.
TypeOfCall Call Setup and Termination Example
Figure 65 shows an example of a TypeOfCall Call Setup and Termination report.
Figure 65: TypeOfCall Call Setup and Termination
As Figure 65 shows, the TypeOfCall Call Setup and Termination report displays the following information and
metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the TypeOfCall.
See TypeOfCall Sub-Element Name on page 176 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a TypeOfCall sub-element name. In this report, each TypeOfCall is one sub-
element.
Total Calls (Nb) The Total Calls (Nb) metric is obtained by the TotalCall collection formula. The
TotalCall collection formula counts the total number of calls for this TypeOfCall.
Successful Calls (Nb) The Successful Calls (Nb) metric is obtained by the SuccessfulCall collection
formula. The SuccessfulCall collection formula counts the total number of calls for this TypeOfCall
that were set up and completed successfully.
Unsuccessful Calls (Nb) The Unsuccessful Calls (Nb) metric is obtained by the UnsuccessfulCall
collection formula. The UnsuccessfulCall collection formula counts the total number of calls for this
TypeOfCall that were not set up and failed to complete successfully.
Call Duration (seconds) The Call Duration (seconds) metric is obtained by the CallDuration
collection formula. The CallDuration collection formula counts the total length, in seconds, of a call for
this TypeOfCall.
Users can drill to the TypeOfCall Call Setup and Termination Quality - DC charts by selecting a TypeOfCall listed
in the Name column.
Termination Cause Analysis Example
Figure 66 shows an example of a Termination Cause Analysis report. The display also includes a Call Distribution
bar graph that shows the distribution percentage of different call activity that occurs on all Nortel CS2000 devices
Figure 66: Termination Cause Analysis
As Figure 66 shows, the Termination Cause Analysis report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Termination
Cause defined in the Q.931 protocol. See Termination Cause Sub-Element Name on page 175 for an explanation
of the syntax the Nortel CS2000 Technology Pack uses to define a Termination Cause sub-element name. In
this report, each Termination Cause is one sub-element.
TotalCall collection formula counts the total number of calls for each Termination Cause.
Incoming Calls (Nb) The Incoming Calls (Nb) metric is obtained by the IncomingCall collection
formula. The IncomingCall collection formula counts the total number of inbound call attempts for each
Termination Cause.
Outgoing Calls Nb The Outgoing Calls Nb metric is obtained by the OutgoingCall collection formula.
The OutgoingCall collection formula counts the total number of outgoing call attempts for each
Termination Cause.
Internal Calls (Nb) The Internal Calls (Nb) metric is obtained by the InternalCall collection formula.
The InternalCall collection formula counts the total number of internal calls for each Termination
Cause. Internal calls are those calls that originate and terminate within the fabric of this softswitch or device.
See Bulk Collection Formulas on page 191 for more information on the Bulk collection formulas that produce these
metrics.
Users can drill to the Termination Cause Analysis - DC charts by selecting a Termination Cause listed in the Name
column. The DC charts show the following additional metrics:
OffNetCall The OffNetCall metric is obtained by the OffNetCall collection formula. The
OffNetCall collection formula counts the total number of OffNet calls for each Termination Cause.
OnNetCall The OnNetCall metric is obtained by the OnNetCall collection formula. The OnNetCall
collection formula counts the total number of OnNet calls for each Termination Cause.
Service Usage CDR/IPDR Reports
The Service Usage CDR/IPDR reports display performance metrics associated with service usage that occurs on
devices operating in the Nortel CS2000 environment. The Nortel CS2000 Technology Pack provides the
following reports at the NOC Reporting->Carrier VOIP->User Experience->Service Usage->CDR/IPDR level of
the NOC reporting tree:
By Customer Profile
Customer Profile Analysis Example
By Extension
Extension Utilization Example
By Media Gateway
MGW Call Utilization Example
By Path
Path Call Utilization Example
By Softswitch
Softswitch Call Utilization Example
By Zone
Zone Utilization Example
Call Distribution
Call Distribution Analysis Example
The following sections discuss each of these reports.
Customer Profile Analysis Example
Figure 67 shows an example of a Customer Profile Analysis report. The display also includes a Call Distribution
bar graph that shows the distribution percentage of different call activity that occurs on all Nortel CS2000 devices
Figure 67: Customer Profile Analysis
As Figure 67 shows, the Customer Profile Analysis report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Customer
Profile. See Customer Profile Sub-Element Name on page 175 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Customer Profile sub-element name. In this report, each Customer Profile
is one sub-element.
TotalCall collection formula counts the total number of calls for each Customer Profile.
Incoming Calls (Nb) The Incoming Calls (Nb) metric is obtained by the IncomingCall collection
formula. The IncomingCall collection formula counts the total number of inbound call attempts for each
Customer Profile.
Outgoing Calls Nb The Outgoing Calls Nb metric is obtained by the OutgoingCall collection formula.
The OutgoingCall collection formula counts the total number of outgoing call attempts for each
Customer Profile.
Internal Calls (Nb) The Internal Calls (Nb) metric is obtained by the InternalCall collection formula.
The InternalCall collection formula counts the total number of internal calls for each Customer Profile.
Internal calls are those calls that originate and terminate within the fabric of this softswitch or device.
formula. The SuccessfulCall collection formula counts the total number of calls for this Customer
Profile that were set up and completed successfully.
Customer Profile that were not set up and failed to complete successfully.
See Bulk Collection Formulas on page 191 for more information on the Bulk collection formulas that produce these
metrics.
Users can drill to the Customer Profile Analysis - DC charts by selecting a Customer Profile listed in the Name
column. The DC charts show the following additional metrics:
InternationalCall The InternationalCall metric is obtained by the InternationalCall collection
formula.
MobileCall The MobileCall metric is obtained by the MobileCall collection formula.
NationalCall The NationalCall metric is obtained by the NationalCall collection formula.
Extension Utilization Example
Figure 68 shows an example of an Extension Utilization report. The display also includes two bar graphs:
Call Distribution This bar graph shows the distribution percentage of different call activity that occurs on
all Nortel CS2000 devices operating in the Nortel CS2000 environment.
Successful vs Unsuccessful Call Ratio This bar graph shows the ratio of successful calls to unsuccessful
calls.
Figure 68: Extension Utilization
As Figure 68 shows, the Extension Utilization report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Extension. See
Extension Sub-Element Name on page 178 for an explanation of the syntax the Nortel CS2000 Technology
Pack uses to define an Extension sub-element name. In this report, each Extension is one sub-element.
Number of Calls The Number of Calls metric is obtained by the TotalCall collection formula. The
TotalCall collection formula counts the total number of calls.
Minutes of Use The Minutes of Use metric is obtained by the CDR Extension Call Duration
Complex Metric Engine (CME) formula.
Successful Calls (percent) The Successful Calls (percent) metric is obtained by the CDR Extension
Successful Calls Percentage CME formula.
Short Calls The Short Calls metric is obtained by the ShortCall collection formula. The ShortCall
collection formula counts the total number of calls whose length is under two seconds.
formula.
SuccessfulCall The SuccessfulCall metric is obtained by the SuccessfulCall collection formula.
UnsuccessfulCall The UnsuccessfulCall metric is obtained by the UnsuccessfulCall collection
formula.
Users can drill to the Extension Utilization - DC charts by selecting an Extension listed in the Name column. The
DC charts show the following additional metrics:
UnsuccessfulCallBusy The UnsuccessfulCallBusy metric is obtained by the UnsuccessfulCallBusy
collection formula.
UnsuccessfulCallInvalidAddress The UnsuccessfulCallInvalidAddress metric is obtained by the
UnsuccessfulCallInvalidAddress collection formula.
UnsuccessfulCallNetwork The UnsuccessfulCallNetwork metric is obtained by the
UnsuccessfulCallNetwork collection formula.
UnsuccessfulCallNoAnswer The UnsuccessfulCallNoAnswer metric is obtained by the
UnsuccessfulCallNoAnswer collection formula.
MGW Call Utilization Example
Figure 69 shows an example of an MGW Call Utilization report. The display also includes two bar graphs:
Unsuccessful Call Type This bar graph shows the distribution percentage of different unsuccessful call
type activity that occurs on all Nortel CS2000 devices operating in the Nortel CS2000 environment.
Successful vs Unsuccessful Call Ratio This bar graph shows the percentage of successful versus
unsuccessful calls on all Media Gateways controlled by all Nortel CS2000 devices operating in the Nortel
CS2000 environment.
Figure 69: RST MGW Call Utilization
As Figure 69 shows, the MGW Call Utilization report displays the following information and metrics:
Trunk. See Media Gateway Trunk Sub-Element Name on page 177 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Media Gateway Trunk sub-element name.
TotalCall collection formula counts the total number of calls going through a specific Media Gateway.
This number is a summary of all call attempts (successful, unsuccessful, Incoming, Outgoing, and External)
through the specific Media Gateway.
formula. The SuccessfulCall collection formula counts the total number of successful calls (Internal,
Outgoing, Incoming, and External) processed by this Media Gateway. A successful call is an answered call,
where the timestamp for the connectionDate field is not empty or equal to the value 0 (zero).
collection formula. The UnsuccessfulCall collection formula counts the total number of unsuccessful
calls (Internal, Outgoing, Incoming, and External) processed by this Media Gateway. An unsuccessful call is
a call that has not been properly established, where the timestamp for the connectionDate field is empty
or equal to the value 0 (zero).
collection formula. The CallDuration collection formula calculates, in seconds, the duration of all calls
processed by this Media Gateway.
See Bulk Collection Formulas on page 191 for more information on the Bulk collection formulas that generate these
metrics.
The figure also shows the metrics that the two bar graphs display:
Users can drill to the MGW Call Utilization - DC charts by selecting an Media Gateway Trunk listed in the Name
column.
Path Call Utilization Example
Figure 70 shows an example of an Path Call Utilization report. The display also includes two bar graphs:
Unsuccessful Call Type This bar graph shows the distribution percentage of different unsuccessful call
type activity that occurs on all Nortel CS2000 devices operating in the Nortel CS2000 environment.
Successful vs Unsuccessful Call Ratio This bar graph shows the percentage of successful versus
unsuccessful calls on all Paths controlled by all Nortel CS2000 devices operating in the Nortel CS2000
environment.
Figure 70: Path Call Utilization
As Figure 70 shows, the Path Call Utilization report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Path. See Path
Sub-Element Name on page 178 for an explanation of the syntax the Nortel CS2000 Technology Pack uses to
define a Path sub-element name.
TotalCall collection formula counts the total number of calls going through a specific Path. This number
is a summary of all call attempts (successful, unsuccessful, Incoming, Outgoing, and External) through the
specific Path.
formula. The SuccessfulCall collection formula counts the total number of successful calls (Internal,
Outgoing, Incoming, and External) processed by this Path. A successful call is an answered call, where the
timestamp for the connectionDate field is not empty or equal to the value 0 (zero).
collection formula. The UnsuccessfulCall collection formula counts the total number of unsuccessful
calls (Internal, Outgoing, Incoming, and External) processed by this Path. An unsuccessful call is a call that
has not been properly established, where the timestamp for the connectionDate field is empty or equal
to the value 0 (zero).
collection formula. The CallDuration collection formula calculates, in seconds, the duration of all calls
processed by this Path.
The figure also shows the metrics that the two bar graphs display:
Users can drill to the Path Call Utilization - DC charts by selecting an Path listed in the Name column.
Figure 71 shows an example of an Softswitch Call Utilization - MLH report.
Figure 71: Softswitch Call Utilization - MLH
As Figure 71 shows, the Softswitch Call Utilization - MLH report displays the following information and metrics:
CDRs. See Nortel CS2000 Sub-Element Name on page 174 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel CS2000 CDR sub-element name.
Most Loaded Hour Displays the date and time that a specific CS2K CDR processed its greatest load.
TotalCall collection formula counts the total number of calls going through a specific Nortel CS2000
CDR. This number is a summary of all call attempts (successful, unsuccessful, Incoming, Outgoing, and
External) through the specific Nortel CS2000 CDR.
Users can drill to the Softswitch Call Utilization - DC charts by selecting a Nortel CS2000 CDR listed in the Name
column.
Softswitch Call Utilization Example
Figure 72 shows an example of an Softswitch Call Utilization report.
Figure 72: Softswitch Call Utilization
As Figure 72 shows, the Softswitch Call Utilization report displays the following information and metrics:
CDRs. See Nortel CS2000 Sub-Element Name on page 174 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Nortel CS2000 CDR sub-element name.
TotalCall collection formula counts the total number of calls going through a specific Nortel CS2000
CDR. This number is a summary of all call attempts (successful, unsuccessful, Incoming, Outgoing, and
External) through the specific Nortel CS2000 CDR.
Grade of Service / 1000 The Grade of Service / 1000 metric is obtained by the CDR Grade of Service
CME formula. The CDR Grade of Service CME formula produces a Grade of Service score, which is
the number of calls out of 1000 that may fail due to network conditions.
formula.
SuccessfulCall The SuccessfulCall metric is obtained by the SuccessfulCall collection formula.
UnsuccessfulCall The UnsuccessfulCall metric is obtained by the UnsuccessfulCall collection
formula.
Users can drill to the Softswitch Call Utilization - DC charts by selecting a Nortel CS2000 CDR listed in the Name
column.
Zone Utilization Example
Figure 73 shows an example of an Zone Utilization report.
Figure 73: Zone Utilization
As Figure 73 shows, the Zone Utilization report displays the following information and metrics:
Name Specifies the sub-element label (which is identical to the sub-element name) for the Subscriber
Zone. See Subscriber Zone Sub-Element Name on page 177 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a Subscriber Zone sub-element name.
TotalCall collection formula counts the total number of calls for this Subscriber Zone.
formula. The SuccessfulCall collection formula counts the total number of calls for this Subscriber
Zone that were set up and completed successfully.
Subscriber Zone that were not set up and failed to complete successfully.
Short Calls (Nb) The Short Calls (Nb) metric is obtained by the ShortCall collection formula. The
ShortCall collection formula counts the total number of calls whose length is under two seconds.
collection formula. The CallDuration collection formula counts the total length, in seconds, of a call for
this Subscriber Zone.
Mobile Calls (Nb) The Mobile Calls (Nb) metric is obtained by the MobileCall collection formula. The
MobileCall collection formula counts the number of calls made from a mobile device for this Subscriber
Zone.
formula.
Users can drill to the Zone Utilization - DC charts by selecting a Subscriber Zone listed in the Name column.
Call Distribution Analysis Example
Figure 74 shows an example of an Call Distribution Analysis report.
Figure 74: Call Distribution Analysis
As Figure 74 shows, the Call Distribution Analysis report displays the following information and metrics:
Name Specifies the sub-element name for the TypeOfCall, which categorizes the call according to its
direction. See TypeOfCall Sub-Element Name on page 176 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define a TypeOfCall sub-element name.
UnsuccessfulCallBusy The UnsuccessfulCallBusy metric is obtained by the UnsuccessfulCallBusy
collection formula.
UnsuccessfulCallInvalidAddress The UnsuccessfulCallInvalidAddress metric is obtained by the
UnsuccessfulCallInvalidAddress collection formula.
UnsuccessfulCallNetwork The UnsuccessfulCallNetwork metric is obtained by the
UnsuccessfulCallNetwork collection formula.
UnsuccessfulCallNoAnswer The UnsuccessfulCallNoAnswer metric is obtained by the
UnsuccessfulCallNoAnswer collection formula.
TotalCall collection formula counts the total number of calls processed by this Softswitch device for each
Type of Call (Incoming, Outgoing, Internal, and External). The formula counts successful and unsuccessful
calls.
See Bulk Collection Formulas on page 191 for more information on the collection formulas that produce these
metrics.
Users can drill to the Call Distribution Analysis - DC charts by selecting a TypeOfCall listed in the Name column.
Voice Quality CDR/IPDR Reports
The Voice Quality CDR/IPDR reports display voice quality metrics associated with call activity that occurs on
the Nortel CS2000 softswitch devices operating in the Nortel CS2000 environment. The Nortel CS2000
Technology Pack provides the following reports at the NOC Reporting->Carrier VOIP->User Experience->Voice
Quality->CDR/IPDR->Nortel CS2K level of the NOC reporting tree:
Extension
Extension Quality Example
Location
SLA Voice Quality - RST
Softswitch Quality
Voice Quality Example
Extension Quality Example
Figure 75 shows an example of an Extension Quality report.
Figure 75: Extension Quality
As Figure 75 shows, the Extension Quality report displays the following information and metrics:
Name Specifies the sub-element name for the Extension, which categorizes the call according to its
extension. See Extension Sub-Element Name on page 178 for an explanation of the syntax the Nortel CS2000
Technology Pack uses to define an Extension sub-element name.
Packet Latency (ms) The Packet Latency (ms) metric is obtained by the PacketLatency collection
formula.The PacketLatency collection formula calculates the average latency, in milliseconds, for VoIP
calls on this extension.
Lost Packets (Nb) The Lost Packets (Nb) metric is obtained by the LostPacket collection formula.The
LostPacket collection formula counts the total number of packets lost during VoIP conversations on this
extension.
Packet Delay Variations (ms) The Packet Delay Variations (ms) metric is obtained by the
PacketDelayVariation collection formula.The PacketDelayVariation collection formula
calculates the average delta in media packet latency, in milliseconds, for VoIP conversations on this extension.
Inbound Packets (Nb) The Inbound Packets (Nb) metric is obtained by the InboundPacket collection
formula.The InboundPacket collection formula counts the total number of inbound packets sent during
VoIP conversations on this extension.
Outbound Packets (Nb) The Outbound Packets (Nb) metric is obtained by the OutboundPacket
collection formula.The OutboundPacket collection formula counts the total number of outbound packets
sent during VoIP conversations on this extension.
metrics.
Users can drill to the Extension Quality - DC charts by selecting an Extension listed in the Name column.
Voice Quality Example
Figure 76 shows an example of an Voice Quality report.
Figure 76: Voice Quality
As Figure 76 shows, the Voice Quality report displays the following information and metrics:
Name Specifies the sub-element name for the Extension, which categorizes the call according to its
extension. See Nortel CS2000 Sub-Element Name on page 174 for an explanation of the syntax the Nortel
CS2000 Technology Pack uses to define a Nortel CS2000 device sub-element name.
Packet Latency (ms) The Packet Latency (ms) metric is obtained by the PacketLatency collection
formula.The PacketLatency collection formula calculates the length of time, in milliseconds (ms),
between received RTP media packets for VoIP calls on this Nortel CS2000 device. Calls where packet latency
is greater than 150 ms may have a noticeable impact on the caller and callee.
Lost Packets (Nb) The Lost Packets (Nb) metric is obtained by the LostPacket collection formula.The
LostPacket collection formula counts the total number of packets lost (never received) during VoIP
conversations on this Nortel CS2000 device.
Packet Delay Variations (ms) The Packet Delay Variations (ms) metric is obtained by the
PacketDelayVariation collection formula.The PacketDelayVariation collection formula
calculates the average delta in media packet latency, in milliseconds, for VoIP conversations on this extension.
Inbound Packets (Nb) The Inbound Packets (Nb) metric is obtained by the InboundPacket collection
formula.The InboundPacket collection formula counts the total number of inbound packets sent on
inbound media streams on this Nortel CS2000 device.
Outbound Packets (Nb) The Outbound Packets (Nb) metric is obtained by the OutboundPacket
collection formula.The OutboundPacket collection formula counts the total number of outbound packets
sent on this Nortel CS2000 device.
metrics.
Users can drill to the Voice Quality - DC charts by selecting a Nortel CS2000 device listed in the Name column.
NOTES
Appendix F: Bulk Collection Formula Mappings
Overview
An input file is a .csv or other file type containing data generated by the Nortel CS2000 device. A row of data
in an input file contains a number of fields. Each bulk collection formula is mapped to data in one or more fields
of an input file row.
Note: This section maps each bulk collection formula with the position of the corresponding field in a row of
data. You need to be aware of this mapping only if the format of the input file is modified for any reason.
Nortel CS2000 Device Bulk Collection Formula Mappings
The Nortel CS2000 Technology Pack provides Bulk collection formulas that map to the metrics attached to the
sub-elements associated with the Nortel Communication Server 2000 (CS2K) device and its associated
components. The Bulk collection formulas for the Nortel CS2000 device sub-element and associated component
sub-elements reside in appropriate subdirectories under this directory: FORMULAS->AP->Specific->Bulk-
>Carrier VOIP->Infrastructure->Softswitch Platform->Class 5 Softswitch->.
Specifically, the Nortel CS2000 Technology Pack defines:
Nortel CS2000 Device Sub-Element Bulk Collection Formula Mappings
CS2K Softswitch Trunk Sub-Element Bulk Collection Formula Mappings
Nortel GWC Bulk Collection Formula Mappings
Nortel MS 2010 (SDM) Bulk Collection Formula Mappings
Topic Page
Overview 869
Nortel CS2000 Device Bulk Collection Formula Mappings 869
Nortel CS2000 CDRs Bulk Collection Formula Mappings 876
Nortel IEMS Device Bulk Collection Formula Mappings 888
Nortel PVG Device Bulk Collection Formula Mappings 898
Nortel SST Device Sub-Element Bulk Collection Formula Mappings 903
Nortel USP Device Bulk Collection Formula Mappings 903
The following sections discuss the Bulk collection formulas for these sub-elements.
Nortel CS2000 Device Sub-Element Bulk Collection Formula Mappings
Nortel CS2000 device sub-element. The Nortel CS2000 device sub-element maps to a Nortel CS2000 device
operating in the Nortel CS2000 environment. The Bulk collection formulas for the Nortel CS2000 device sub-
element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->Softswitch Platform->Class 5 Softswitch->Device.
The Nortel CS2000 Technology Pack provides a Nortel CS2000 Performance Bulk Adaptor Design File that is
maintained by IBM Professional Services. The Nortel CS2000 Performance Bulk Adaptor Design File
implements the Nortel CS2000 device sub-element Bulk collection formulas. These Bulk collection formulas
operate on fields that reside in a file associated with a specific Nortel CS2000 device sub-element. The Bulk
collection formulas use these fields to map to the corresponding metrics.
Specifically, the Nortel CS2000 Performance Bulk Adaptor Design File works with Operational Management
(OM) groups. An OM group collects performance data exported to the input files. Nortel defines OM groups
in NTP-279-9051-8141 to NTP-279-9051-8146 documentation. Information about OM groups can also be found in
the NTP 297-8021-814 Operational Measurements Reference Manual.
Specifically, the Nortel CS2000 Technology Pack defines the Bulk collection formulas listed in Table 4. The table
shows the formula names, OM group(s) the formulas reference, and the specific register(s) the formula
references. Some of the metrics associated with these Bulk collection formulas display in the CS2K Device
Quality report.
Table 4: Formulas Associated with the Nortel CS2000 Device Sub-Element
Formula OM Group Register
AUXCP BRSTAT
XASTAT
BRSAUXCP
XAAUXCP
AverageHoldingTime NPILNS
NPILNS2
NPITRK
NPITRK2
LMTRU
NORIGATT
NTERMATT
ORIGABN
LMTRU2
NORIGATT2
NTERMATT2
ORIGABN2
CONNECT
INCATOT
TRU
CONNECT2
INCATOT2
TRU2
BusyCallHourAttempts OFZ NIN
NIN2
NORIG
NORIG2
CallAgentCPUUtilization BRSTAT BRSCAP
CallAgentMemoryUtilization STORE SPAREMB
CallCompletionRatio_EndOffice CD
CP
CP2
LMD
OFZ
SYSPERF
TRK
TRMTCM
TRMTRS
CCBOVFL
CPLOOVFL
ORIGDENY
ORIGDENY
ORIGBLK
ORIGFAIL
PERCLFL
TERMBLK
INLKT
NIN
NIN2
NORIG
NORIG2
ORIGLKT
CINTEGFL
INFAIL
OUTFAIL
TCMVACT
TRSGNCT
TRSNCRT
CallCompletionRatio_Tandem OFZ
TRK
TRNK2
NIN
NIN2
CONNECT
CONNECT2
CPUutilizationForCallProcessing% CPUSTAT CPSCPOCC
Delay TRK
TRKQOSOM
TRNK2
CONNECT
INCATOT
DELAYQOS
CONNECT2
INCATOT2
ENGCAP BRSTAT
XASTAT
BRSCAP
XASUTIL
HIOP IOCAP IOUTIL
IncomingTrunkToLineCallAttempts OTS INCTRM
IntraSwitchLineToLineCallAttempts OTS ORGTRM
Jitter TRK
TRKQOSOM
TRNK2
CONNECT
INCATOT
JITTER
CONNECT2
INCATOT2
LossOfEstablishedCalls SYSPERF CINTEGFL
NetworkEffectivenessRatio OFZ
TRK
TRMTFR
TRNK2
NIN
NIN2
ANSWER
TFRBUSY
ANSWER2
OriginatingAbandonsBeforeConnection LMD ORIGABN
OriginatingAttemptFailures LMD ORIGFAIL
OriginatingFailures LMD ORIGBLK
OriginatingLineCallAttempts LMD NORIGATT
OutgoingLineToTrunkCallAttempts OTS ORGOUT
PacketLoss TRK
TRKQOSOM
TRNK2
CONNECT
INCATOT
PKTLOSS
CONNECT2
INCATOT2
ProcessorElement XASTAT XASUTIL
SCAI SEIUTRAN SEIUMSGI
SEIUMSGO
ServiceFailureRate NPITRK
NPITRK2
INCATOT
INFAIL
NATTEMPT
NOVFLATB
OUTFAIL
INCATOT2
INFAIL2
NATTEMP2
NOVFLAT2
OUTFAIL2
SparingBandwidth TPCSPOM SP_MAX
TerminatingFailures LMD TERMBLK
CS2K Softswitch Trunk Sub-Element Bulk Collection Formula Mappings
CS2K Softswitch Trunk sub-element. The CS2K Softswitch Trunk sub-element maps to a Nortel
Communication Server 2000 (CS2K) Softswitch Trunk component associated with a Nortel CS2000 softswitch
device operating in the Nortel CS2000 environment. The Bulk collection formulas for the CS2K Softswitch
Trunk sub-element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->Softswitch Platform->Class 5 Softswitch->Trunk.
TotalSoftswitchCallAttempts OTS
OTS2
INCOUT
INCTRM
ORGOUT
ORGTRM
TotalSoftswitchSuccessfulCalls OTS2 INCOUTC
INCTRMC
ORGOUTC
ORGTRMC
TotalSoftswitchSuccessfulCalls% OTS
OTS2
INCTRM
INCTRMC
INCOUTC
ORGTRM
ORGTRMC
ORGOUT
ORGOUTC
TotalSoftswitchUnsuccessfulCalls OTS
OTS2
INCTRM
INCTRMC
INCOUT
INCOUTC
ORGTRM
ORGTRMC
ORGOUT
ORGOUTC
TotalSoftswitchUnsuccessfulCalls% OTS
OTS2
INCTRM
INCTRMC
INCOUT
INCOUTC
ORGTRM
ORGTRMC
ORGOUT
ORGOUTC
TrafficBusyUse LMD LMTRU
TransitTrunkToTrunkCallAttempts OTS INCOUT
TrunkOrCarrierBusy SYSPERF TKPCBU
implements the CS2K Softswitch Trunk sub-element Bulk collection formulas. These Bulk collection formulas
operate on fields that reside in a file associated with a specific CS2K Softswitch Trunk sub-element. The Bulk
collection formulas use these fields to map to the corresponding metrics.
(OM) groups. An OM group collects performance data exported to the input files. Nortel defines OM groups in
NTP-279-9051-8141 to NTP-279-9051-8146 documentation. Information about OM groups can also be found in the
NTP 297-8021-814 Operational Measurements Reference Manual.
references. Some of the metrics associated with these Bulk collection formulas display in the CS2K Trunk Quality
report.
Table 5: Formulas Associated with the CS2K Softswitch Trunk Sub-Element
Nortel GWC Bulk Collection Formula Mappings
Nortel GWC sub-element. The Nortel GWC sub-element maps to a Gateway Controller component associated
IncomingAnswerSeizureRatio% TRK2 NINCTRM
NINCTRMC
IncomingCallTrunkRoutingFailure TRK
TRK2
INCATOT
NINCTRM
IncomingSuccessfulCalls TRK2 NINCTRMC
IncomingSuccessfulCalls% TRK
TRK2
INCATOT
NINCTRMC
OutgoingAnswerSeizureRatio% TRK2 ANSWER
NORGOUTC
OutgoingCallTrunkRoutingFailure TRK2 ANSWER
NORGOUT
OutgoingSuccessfulCalls TRK2 NORGOUTC
OutgoingSuccessfulCalls% TRK2 NORGOUT
NORGOUTC
TotalCallBidAttempts TRK
TRK2
INCATOT
NORGOUT
TotalCallTrunkRoutingFailure% TRK
TRK2
ANSWER
INCATOT
NINCTRM
NORGOUT
TrunkOverflow OFZ2 OFZNCRT
TrunkGOS TRK
TRNK2
TRU
TRU2
with a Nortel CS2000 softswitch device operating in the Nortel CS2000 environment. The Bulk collection
formulas for the Nortel GWC sub-element reside in this directory: FORMULAS->AP->Specific->Bulk-
>Carrier VOIP->Infrastructure->Softswitch Platform->Class 5 Softswitch->GWC.
implements the Nortel GWC sub-element Bulk collection formulas. These Bulk collection formulas operate on
fields that reside in a file associated with a specific Nortel GWC sub-element. The Bulk collection formulas use
these fields to map to the corresponding metrics.
references. Some of the metrics associated with these Bulk collection formulas display in the Nortel GWC report.
Table 6: Formulas Associated with the Nortel GWC Sub-Element
Nortel MS 2010 (SDM) Bulk Collection Formula Mappings
SDM (described in this section), and one set from the IEMS (described in Nortel MS 2010 (IEMS) Bulk
Collection Formula Mappings on page 892).
Nortel MS 2010 sub-element. The Nortel MS 2010 sub-element maps to a Nortel Media Server 2010 component
associated with a Nortel CS2000 softswitch device operating in the Nortel CS2000 environment. The Bulk
collection formulas for the Nortel MS 2010 sub-element reside in this directory: FORMULAS->AP->Specific-
>Bulk->Carrier VOIP->Infrastructure->Softswitch Platform->Class 5 Softswitch-
>MS2010.
BHHCA XPMOCC
XPMOCC2
PMORIGS
PMTERMS
PMORIGS2
PMTERMS2
CCR XPKTFLOM DQOSCFL
ITACFL
OTHERCFL
PACKETC2
PACKETCA
PKTNTWCF
VCACCFL
Mid-call Failure Rate XPKTFLOM PACKETC2
PACKETCA
PKTDENDO
PKTDENDT
Processor XPMOCC AVGCPOCC
NUMRPTS
implements the Nortel MS 2010 sub-element Bulk collection formulas. These Bulk collection formulas operate
on fields that reside in a file associated with a specific Nortel MS 2010 sub-element. The Bulk collection formulas
use these fields to map to the corresponding metrics.
references. Some of the metrics associated with these Bulk collection formulas display in the Nortel MS 2010
report.
Table 7: Formulas Associated with the Nortel MS 2010 Sub-Element
Nortel CS2000 CDRs Bulk Collection Formula Mappings
sub-elements associated with the Nortel Communication Server 2000 (CS2K) Call Detail Records (CDRs) and its
associated components. The Bulk collection formulas for the Nortel CS2000 CDRs device sub-element and
associated component sub-elements reside in appropriate subdirectories under this directory: FORMULAS->AP-
>Specific->Bulk->Carrier VOIP->Infrastructure->Class 5 CDR>.
Nortel CS2000 CDR Device Sub-Element Bulk Collection Formula Mappings
Termination Cause Sub-Element Bulk Collection Formula Mappings
TypeOfCall Sub-Element Bulk Collection Formula Mappings
Media Gateway Trunk Sub-Element Bulk Collection Formula Mappings
Customer Profile Sub-Element Bulk Collection Formula Mappings
Subscriber Zone Sub-Element Bulk Collection Formula Mappings
3PortConfFailureRatio CF3P CNFOVFL
CNFSZRS
3PortOcc AUDSRVS CNF3INSU
CNF3TRU
6PortConfFailureRatio CF6P CNFOVFL
CNFSZRS
6PortOcc AUDSRVS CNF6INSU
CNF6TRU
ANNFailureRatio ANN ANNATT
ANNOVFL
ANNocc AUDSRVS ANNCINSU
ANNCTRU
Extension Sub-Element Bulk Collection Formula Mappings
Path Sub-Element Bulk Collection Formula Mappings
CDR Location Sub-Element Bulk Collection Formula Mappings
Nortel CS2000 CDR Device Sub-Element Bulk Collection Formula Mappings
Nortel CS2000 CDR device sub-element. The Nortel CS2000 device sub-element maps to a Nortel CS2000
device operating in the Nortel CS2000 environment. The Bulk collection formulas for the Nortel CS2000 device
sub-element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->Class 5 CDR>CDR Softswitch Device.
The Nortel CS2000 Technology Pack provides a Nortel CS2000 CDR Bulk Adaptor Design File that is
maintained by IBM Professional Services. The Nortel CS2000 CDR Bulk Adaptor Design File implements the
Nortel CS2000 device sub-element Bulk collection formulas. These Bulk collection formulas operate on fields
that reside in a Bulk input file associated with a specific Nortel CS2000 device sub-element. The Bulk collection
formulas use these fields to map to the corresponding metrics.
shows the formula names associated with the Nortel CS2000 device sub-element that the formulas use to map to
the corresponding metric. Some of the metrics produced by these Bulk collection formulas display in the
Softswitch Call Utilization - MLH and Termination Cause Analysis report.
Table 8: Formulas Associated with the Nortel CS2000 CDR Device Sub-Element
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
ExternalCall
InboundByte
InboundPacket
IncomingCall
InternalCall
InternationalCall
ListeningQualityMOS
LostPacket
MobileCall
Termination Cause Sub-Element Bulk Collection Formula Mappings
Termination Cause sub-element. The Termination Cause sub-element maps to a Termination Cause CDR
generated in the Nortel CS2000 environment. The Bulk collection formulas for the Termination Cause sub-
>Infrastructure->Class 5 CDR>CDR Termination Cause.
Termination Cause sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that
reside in a Bulk input file associated with a specific Termination Cause sub-element. The Bulk collection formulas
NationalCall
OffNetCall
OnNetCall
OutboundByte
OutboundPacket
OutgoingCall
PacketLatency
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
Formula
shows the formula names associated with the Termination Cause sub-element that the formulas use to map to
the corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the
Termination Cause Analysis report.
Table 9: Formulas Associated with the Termination Cause Sub-Element
TypeOfCall Sub-Element Bulk Collection Formula Mappings
The Nortel CS2000 Technology Pack provides Bulk collection formulas that calculate the metrics attached to the
TypeOfCall sub-element. The TypeOfCall sub-element maps to a TypeOfCall CDR generated in the Nortel
CS2000 environment. The Bulk collection formulas for the TypeOfCall sub-element reside in this directory:
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Class 5 CDR>CDR Type
of Call.
Formula
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
ExternalCall
IncomingCall
InternalCall
InternationalCall
ListeningQualityMOS
MobileCall
NationalCall
OffNetCall
OnNetCall
OutgoingCall
RoundTripAverage
ShortCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
TypeOfCall sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside
in a Bulk input file associated with a specific TypeOfCall sub-element. The Bulk collection formulas use these
fields to map to the corresponding metrics.
shows the formula names associated with the TypeOfCall sub-element that the formulas use to map to the
corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the Call
Distribution Analysis report.
Table 10: Formulas Associated with the TypeOfCall Sub-Element
Media Gateway Trunk Sub-Element Bulk Collection Formula Mappings
Media Gateway Trunk sub-element. The Media Gateway Trunk sub-element maps to a Media Gateway Trunk
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
MobileCall
NormalCall Termination
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
CDR generated in the Nortel CS2000 environment. The Bulk collection formulas for the Media Gateway Trunk
sub-element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->Class 5 CDR>CDR Media Gateway.
Media Gateway Trunk sub-element Bulk collection formulas. These Bulk collection formulas operate on fields
that reside in a Bulk input file associated with a specific Media Gateway Trunk sub-element. The Bulk collection
shows the formula names associated with the Media Gateway Trunk sub-element that the formulas use to map
to the corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the
MGW Call Utilization report.
Table 11: Formulas Associated with the Media Gateway Sub-Element
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
IncomingCall
InternalCall
InternationalCall
ListeningQualityMOS
MobileCall
NationalCall
OffNetCall
OnNetCall
OutgoingCall
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
Customer Profile Sub-Element Bulk Collection Formula Mappings
Customer Profile sub-element. The Customer Profile sub-element maps to a Customer Profile CDR generated
in the Nortel CS2000 environment. The Bulk collection formulas for the Customer Profile sub-element reside in
this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Class 5
CDR>CDR Customer Profile.
Customer Profile sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that
reside in a Bulk input file associated with a specific Customer Profile sub-element. The Bulk collection formulas
shows the formula names associated with the Customer Profile sub-element that the formulas use to map to the
corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the Customer
Profile Analysis report.
Table 12: Formulas Associated with the Customer Profile Sub-Element
UnsuccessfulCall
Formula
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
InboundByte
InboundPacket
IncomingCall
InternalCall
InternationalCall
ListeningQualityMOS
Subscriber Zone Sub-Element Bulk Collection Formula Mappings
Subscriber Zone sub-element. The Subscriber Zone sub-element maps to a Subscriber Zone CDR generated in
the Nortel CS2000 environment. The Bulk collection formulas for the Subscriber Zone sub-element reside in this
directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Class 5
CDR>CDR Zone.
Subscriber Zone sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that
LostPacket
MobileCall
NationalCall
OffNetCall
OnNetCall
OutboundByte
OutboundPacket
OutgoingCall
PacketLatency
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
Formula
reside in a Bulk input file associated with a specific Subscriber Zone sub-element. The Bulk collection formulas
shows the formula names associated with the Subscriber Zone sub-element that the formulas use to map to the
corresponding metric. Some of the metrics produced by these Bulk collection formulas display in the Zone
Utilization report.
Table 13: Formulas Associated with the Subscriber Zone Sub-Element
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
InboundByte
InboundPacket
InternationalCall
ListeningQualityMOS
LostPacket
MobileCall
NationalCall
OutboundByte
OutboundPacket
PacketLatency
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
Extension Sub-Element Bulk Collection Formula Mappings
Extension sub-element. The Extension sub-element maps to an Extension CDR generated in the Nortel CS2000
environment. The Bulk collection formulas for the Extension sub-element reside in this directory: FORMULAS-
>AP->Specific->Bulk->Carrier VOIP->Infrastructure->Class 5 CDR>CDR Extension.
Extension sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in
a Bulk input file associated with a specific Extension sub-element. The Bulk collection formulas use these fields
to map to the corresponding metrics.
shows the formula names associated with the Extension sub-element that the formulas use to map to the
corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the
Extension Quality report.
Table 14: Formulas Associated with the Extension Sub-Element
Formula
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
InboundByte
InboundPacket
IncomingCall
InternalCall
InternationalCall
ListeningQualityMOS
LostPacket
MobileCall
Path Sub-Element Bulk Collection Formula Mappings
Path sub-element. The Path sub-element maps to a Path CDR generated in the Nortel CS2000 environment. The
Bulk collection formulas for the Path sub-element reside in this directory: FORMULAS->AP->Specific-
>Bulk->Carrier VOIP->Infrastructure->Class 5 CDR>CDR Path.
Path sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a Bulk
input file associated with a specific Path sub-element. The Bulk collection formulas use these fields to map to the
corresponding metrics.
shows the formula names associated with the Path sub-element that the formulas use to map to the
NationalCall
OffNetCall
OnNetCall
OutboundByte
OutboundPacket
OutgoingCall
PacketLatency
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
Formula
corresponding metric. Some of the metrics associated with these Bulk collection formulas display in the Path Call
Utilization report.
Table 15: Formulas Associated with the Path Sub-Element
CDR Location Sub-Element Bulk Collection Formula Mappings
CDR location sub-element. The CDR location sub-element maps to the Nortel CS2000 Extended QoS. The Bulk
collection formulas for the CDR location sub-element reside in this directory: FORMULAS->AP->Specific-
>Bulk->Carrier VOIP->User Experience->Voice Quality->CDR/IPDR->Nortel CS2K-
>Location.
CDR location sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside
in a Bulk input file associated with a specific CDR location sub-element. The Bulk collection formulas use these
fields to map to the corresponding metrics.
Formula
AboveMOSpercentage
AverageLossRate
CallDuration
DropCall
EchoReturnLoss
EndSystemDelay
ListeningQualityMOS
RoundTripAverage
ShortCall
SuccessfulCall
TotalCall
TransmissionStreams
UnderMOSLimit
UnderMOSLimitOffnet
UnderMOSLimitOnnet
UnsuccessfulCall
shows the formula names associated with the CDR location sub-element that the formulas use to map to the
corresponding metric.
Table 16: Formulas Associated with the CDR Location Sub-Element
Nortel IEMS Device Bulk Collection Formula Mappings
sub-elements associated with the Nortel IEMS device and its associated components. The Bulk collection
formulas for the Nortel IEMS device sub-element and associated component sub-elements reside in appropriate
subdirectories under this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->IEMS.
hrSystem Bulk Collection Formula Mappings
Nortel AMS Bulk Collection Formulas
Nortel CICM Bulk Collection Formula Mappings
Nortel MS 2010 (IEMS) Bulk Collection Formula Mappings
Nortel SAM21 Bulk Collection Formula Mappings
Nortel SPC Bulk Collection Formula Mappings
Nortel SSL Bulk Collection Formula Mappings
Formula
AboveMOSpercentage
AverageLossRate
EchoReturnLoss
EndSystemDelay
JitterAverage
ListeningQualityMOS
RoundTripAverage
TransmissionStreams
hrSystem Bulk Collection Formula Mappings
hrSystem sub-element. The hrSystem sub-element maps to a component associated with a Nortel Integrated
Element Management System (IEMS) device operating in the Nortel CS2000 environment. The Bulk collection
formulas for the hrSystem sub-element reside in these directories:
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->AMS
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->CICM Mgr
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->MS2000
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->SAM21
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->Session
Server
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->SSL
The Nortel CS2000 Technology Pack provides a Nortel IEMS Bulk Adaptor Design File that is maintained by
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the hrSystem sub-element
Bulk collection formulas. However, these Bulk collection formulas are not used because the formula names and
the fields used to compute the metrics are extracted directly from the fields that reside in the input file associated
with a specific hrSystem sub-element.
Specifically, the Nortel CS2000 Technology Pack extracts the Bulk collection formulas listed in Table 17.
Nortel AMS Bulk Collection Formulas
sub-elements associated with the Nortel Announcement Media Server (AMS). The Bulk collection formulas for
the Nortel AMS sub-elements reside in appropriate subdirectories under this directory: FORMULAS->AP-
>Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->AMS.
Nortel RAS Port Bulk Collection Formula Mappings
Nortel AMS Stream Source Bulk Collection Formula Mappings
Nortel AMS Bulk Collection Formula Mappings
Nortel AMS TCP Bulk Collection Formula Mappings
Nortel RAS Port Bulk Collection Formula Mappings
Nortel RAS Port sub-element. The Nortel RAS Port sub-element maps to a Nortel Remote Access Server (RAS)
component associated with a Nortel Announcement Media Server (AMS) device operating in the Nortel CS2000
environment. The Bulk collection formulas for the Nortel RAS Port sub-element reside in this directory:
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->AMS->RAS Port.
Table 17: Formulas Associated with the hrSystem Sub-Element
Formula
hrSystemUptime
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel RAS Port sub-
element Bulk collection formulas. However, these Bulk collection formulas are not used because the formula
names and the fields used to compute the metrics are extracted directly from the fields that reside in the input file
associated with a specific Nortel RAS Port sub-element.
Nortel AMS Stream Source Bulk Collection Formula Mappings
Nortel AMS Stream Source sub-element. The Nortel AMS Stream Source sub-element maps to a Nortel
Announcement Media Server (AMS) Stream Source component associated with a Nortel Announcement Media
Server (AMS) device operating in the Nortel CS2000 environment. The Bulk collection formulas for the Nortel
AMS Stream Source sub-element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier
VOIP->Infrastructure->IEMS->AMS->StreamSource.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel AMS Stream
Source sub-element Bulk collection formulas. However, these Bulk collection formulas are not used because the
formula names and the fields used to compute the metrics are extracted directly from the fields that reside in the
input file associated with a specific Nortel AMS Stream Source sub-element.
Table 18: Formulas Associated with the Nortel RAS Port Sub-Element
Formula
Alignment Errors
Bytes Received
Bytes Transmitted
CRC Errors
Timeout Errors
Total Errors
Table 19: Formulas Associated with the Nortel AMS Stream Source Sub-Element
Formula
Nortel AMS Bulk Collection Formula Mappings
Nortel AMS sub-element. The Nortel AMS sub-element maps to a Nortel Announcement Media Server (AMS)
component associated with a Nortel Announcement Media Server (AMS) device operating in the Nortel CS2000
environment. The Bulk collection formulas for the Nortel AMS sub-element reside in this directory: FORMULAS-
>AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->AMS->System.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel AMS sub-element
with a specific Nortel AMS sub-element.
Nortel AMS TCP Bulk Collection Formula Mappings
Nortel AMS TCP sub-element. The Nortel AMS TCP sub-element maps to a Nortel Announcement Media
Server (AMS) TCP component associated with a Nortel Announcement Media Server (AMS) device operating in
the Nortel CS2000 environment. The Bulk collection formulas for the Nortel AMS TCP sub-element reside in
this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->AMS-
>TCP.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel AMS TCP sub-
associated with a specific Nortel AMS TCP sub-element.
Table 20: Formulas Associated with the Nortel AMS Sub-Element
Formula
Processes
System Calls/sec
Threads
Table 19: Formulas Associated with the Nortel AMS Stream Source Sub-Element
Formula
Nortel CICM Bulk Collection Formula Mappings
Nortel CICM sub-element. The Nortel CICM sub-element maps to a Nortel Centrex IP Client Manager (CICM)
component associated with a Nortel Integrated Element Management System (IEMS) device operating in the
Nortel CS2000 environment. The Bulk collection formulas for the Nortel CICM sub-element reside in this
directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->CICM
Mgr.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel CICM sub-
names are extracted directly from the fields that reside in the input file associated with a specific Nortel CICM
sub-element.
Nortel MS 2010 (IEMS) Bulk Collection Formula Mappings
SDM (described in Nortel MS 2010 (SDM) Bulk Collection Formula Mappings on page 875), and one set
from the IEMS (described in this section).
Nortel MS 2010 sub-element. The Nortel MS 2010 sub-element maps to a Nortel Media Server 2010 (MS 2010)
Nortel CS2000 environment. The Bulk collection formulas for the Nortel MS 2010 device sub-element and
associated component sub-elements reside in appropriate subdirectories under this directory: FORMULAS->AP-
>Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->MS2000.
Table 21: Formulas Associated with the Nortel AMS TCP Sub-Element
Formula
Connection Failures
Connections Active
Table 22: Formulas Associated with the Nortel CICM Sub-Element
Formula
ActiveConnections
ActiveSessions
HalfCallAttempts
LoggedInUsers
PercentageCpuUsed
acPerfBct Bulk Collection Formula Mappings
acPerfConf Bulk Collection Formula Mappings
acPerfIvr Bulk Collection Formula Mappings
acPerfRtp Bulk Collection Formula Mappings
acPerfSystem Bulk Collection Formula Mappings
acPerfTt Bulk Collection Formula Mappings
acPerfBct Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfBct Bulk collection formulas for the Nortel MS 2010 sub-element
reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure-
>IEMS->MS2000->acPerfBct.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel MS 2010 sub-
associated with a specific Nortel MS 2010 sub-element.
acPerfConf Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfConf Bulk collection formulas for the Nortel MS 2010 sub-element
>IEMS->MS2000->acPerfConf.
Table 23: Formulas Associated with the Nortel MS 2010 (acPerfBct) Sub-Element
Formula
acPerfBctRequests
acPerfIvr Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfIvr Bulk collection formulas for the Nortel MS 2010 sub-element
>IEMS->MS2000->acPerfIvr.
acPerfRtp Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfRtp Bulk collection formulas for the Nortel MS 2010 sub-element
>IEMS->MS2000->acPerfRtp.
Table 24: Formulas Associated with the Nortel MS 2010 (acPerfConf) Sub-Element
Formula
acPerfConfRequests
Table 25: Formulas Associated with the Nortel MS 2010 (acPerfIvr) Sub-Element
Formula
acPerfSystem Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfSystem Bulk collection formulas for the Nortel MS 2010 sub-element
>IEMS->MS2000->acPerfSystem.
Specifically, the Nortel CS2000 Technology Pack extracts the Bulk collection formula listed in Table 27.
acPerfTt Bulk Collection Formula Mappings
Nortel CS2000 environment. The acPerfTt Bulk collection formulas for the Nortel MS 2010 sub-element
>IEMS->MS2000->acPerfTt.
Table 26: Formulas Associated with the Nortel MS 2010 (acPerfRtp) Sub-Element
Formula
Table 27: Formulas Associated with the Nortel MS 2010 (acPerfSystem) Sub-Element
Formula
Nortel SAM21 Bulk Collection Formula Mappings
Nortel SAM21 sub-element. The Nortel SAM21 sub-element maps to a Nortel SAM21 Shelf Controller
Nortel CS2000 environment. The Bulk collection formulas for the Nortel SAM21 sub-element reside in this
directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->SAM21-
>voip.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel SAM21 sub-
names are extracted directly from the fields that reside in the input file associated with a specific Nortel SAM21
sub-element.
Table 29: Formulas Associated with the Nortel SAM21 Sub-Element
Nortel SPC Bulk Collection Formula Mappings
Nortel SPC sub-element. The Nortel SPC sub-element maps to a Nortel Session Policy Controller (SPC)
Nortel CS2000 environment. The Bulk collection formulas for the Nortel SPC sub-element reside in this
directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->Session
Server.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel SPC sub-element
Table 28: Formulas Associated with the Nortel MS 2010 (acPerfTt) Sub-Element
Formula
acPerfTtRequests
Formula
bytesRxedPerSec
bytesSentPerSec
cellDropCount
oversizedPDUCount
rxedTimeoutCount
totalBytesRxed
totalBytesSent
with a specific Nortel SPC sub-element.
Nortel SSL Bulk Collection Formula Mappings
Nortel SSL sub-element. The Nortel SSL sub-element maps to a Nortel Session Server Lines component
associated with a Nortel Integrated Element Management System (IEMS) device operating in the Nortel CS2000
environment. The Bulk collection formulas for the Nortel SSL sub-element reside in this directory: FORMULAS-
>AP->Specific->Bulk->Carrier VOIP->Infrastructure->IEMS->SSL.
IBM Professional Services. The Nortel IEMS Bulk Adaptor Design File implements the Nortel SSL sub-element
with a specific Nortel SSL sub-element.
Table 30: Formulas Associated with the Nortel SPC Sub-Element
Formula
hrStorageUsed
Table 31: Formulas Associated with the Nortel SSL Sub-Element
Formula
In_2xx
In_3xx
In_4xx
In_5xx
In_6xx
In_Unknown
InBYE
Invite200
Nortel PVG Device Bulk Collection Formula Mappings
sub-elements associated with the Nortel Passport Packet Voice Gateway (PVG) device and its associated
components. The Bulk collection formulas for the PVG device sub-element and associated component sub-
elements reside in appropriate subdirectories under this directory: FORMULAS->AP->Specific->Bulk-
>Carrier VOIP->Infrastructure->Media Gateway->.
PVG Device Sub-Element Bulk Collection Formula Mappings
Media Gateway FC Sub-Element Bulk Collection Formula Mappings
Media Gateway SC Sub-Element Bulk Collection Formula Mappings
MGI Sub-Element Bulk Collection Formula Mappings
Media Gateway VSP PC Sub-Element Bulk Collection Formula Mappings
Media Gateway VSP CC Sub-Element Bulk Collection Formula Mappings
Out_2xx
Out_3xx
Out_4xx
Out_5xx
Out_6xx
Out_Unknown
OutBYE
Processor
SSLOverload
TotalActive
TotalIn
TotalOut
totalRam
totalSwap
Transactions
Table 31: Formulas Associated with the Nortel SSL Sub-Element
Formula
PVG Device Sub-Element Bulk Collection Formula Mappings
PVG device sub-element. The PVG device sub-element maps to a Passport Packet Voice Gateway (PVG) device
operating in the Nortel CS2000 environment. The Bulk collection formulas for the PVG device sub-element
>Media Gateway->Device.
The Nortel CS2000 Technology Pack provides a PVG Performance Bulk Adaptor Design File that is maintained
by IBM Professional Services. The PVG Performance Bulk Adaptor Design File implements the PVG device sub-
element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a PVG
Performance file. A PVG Performance file is a Bulk input file associated with a specific PVG device sub-element.
The Bulk collection formulas use these fields to map to the corresponding metrics.
shows the formula names, field name(s), and field number(s) from the input file associated with the PVG device
sub-element that the formulas use to map to the corresponding metrics. Some of the metrics associated these
Bulk collection formulas display in the PVG Device Call Signaling and PVG Device Usage reports.
Table 32: Formulas Associated with the PVG Device Sub-Element
Formula Field Name Field Number
AvgCPUutilizationCardProcessing CARDUTILAVG 14
AvgCPUutilizationVSPCard VSPUTILAVG 136
CongestedSeconds CONGSECS 137
Failovers FAILOVERS 141
H248Retransmission INH248RETRAN
OUTH248RETRAN
140
139
NetworkCallFailure CALLFAILSNET 142
OverloadCmdRejected OVLDCMDSREJECTED 148
TDMCallFailures CALLFAILTDM 143
TotalActiveCalls ACTIVECALLAVG 146
TotalICMPPackets INICMPPACKETSLOCAL
OUTICMPPACKETSLOCAL
110
116
TotalMinutesOfUse ACTIVECALLAVG
LOG_TYPE
146
TotalPackets INPACKETS
OUTPACKETS
106
107
TotalSuccessfulCalls ACTIVECALLAVG
LOG_TYPE
146
TotalTCPPackets INTCPPACKETSLOCAL
OUTTCPPACKETSLOCAL
108
114
TotalUDPPackets INUDPPACKETSLOCAL
OUTUDPPACKETSLOCAL
109
115
Media Gateway FC Sub-Element Bulk Collection Formula Mappings
The Nortel CS2000 Technology Pack provides a Bulk collection formula that maps to the temperature metric
attached to the Media Gateway FC sub-element. The Media Gateway FC sub-element maps to a Media Gateway
Fabric Card (FC) component associated with a specific Passport Packet Voice Gateway (PVG) device operating
in the Nortel CS2000 environment. The Bulk collection formula for the Media Gateway FC sub-element resides
in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Media
Gateway->Fabric Card.
by IBM Professional Services. The PVG Performance Bulk Adaptor Design File implements the Media Gateway
FC sub-element Bulk collection formula. This Bulk collection formula operates on a field that resides in a PVG
Performance file. A PVG Performance file is a Bulk input file associated with a specific Media Gateway FC sub-
element. The Bulk collection formula uses this field to map to the corresponding metric.
Specifically, the Nortel CS2000 Technology Pack defines the Bulk collection formula listed in Table 33. The table
shows the formula name, field name, and field number from the input file associated with the Media Gateway FC
sub-element that the formula uses to map to the corresponding metric. This metric displays in the PVG Card
Temperature report.
Table 33: Formulas Associated with the Media Gateway FC Sub-Element
Media Gateway SC Sub-Element Bulk Collection Formula Mappings
Media Gateway SC sub-element. The Media Gateway SC sub-element maps to a Media Gateway Shelf Card (SC)
component associated with a Passport Packet Voice Gateway (PVG) device operating in the Nortel CS2000
environment. The Bulk collection formulas for the Media Gateway SC sub-element reside in this directory:
FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Media Gateway->Card.
SC sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a PVG
Performance file. A PVG Performance file is a Bulk input file associated with a specific Media Gateway SC sub-
element. The Bulk collection formulas use these fields to map to the corresponding metrics.
shows the formula names, field name(s), and field number(s) from the input file associated with the Media
Gateway SC sub-element that the formulas use to map to the corresponding metrics. Some of the metrics
associated with these Bulk collection formulas display in the PVG Card Quality report.
Table 34: Formulas Associated with the Media Gateway FC Sub-Element
MaxTemp MAXTEMP 13
CardUtilAvg CARDUTILAVG 14
LMBUtil LMBUTIL 15
MGI Sub-Element Bulk Collection Formula Mappings
MGI sub-element. The MGI sub-element maps to a Media Gateway Interface (MGI) component associated with
a Passport Packet Voice Gateway (PVG) device operating in the Nortel CS2000 environment. The Bulk collection
formulas for the MGI sub-element reside in this directory: FORMULAS->AP->Specific->Bulk->Carrier
VOIP->Infrastructure->Media Gateway->Interface.
by IBM Professional Services. The PVG Performance Bulk Adaptor Design File implements the MGI sub-
element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a PVG
Performance file. A PVG Performance file is a Bulk input file associated with a specific MGI sub-element. The
Bulk collection formulas use these fields to map to the corresponding metrics.
shows the formula names, field name(s), and field number(s) from the input file associated with the MGI sub-
element that the formulas use to map to the corresponding metrics. Some of the metrics produced by these Bulk
collection formulas display in the PVG Interface Usage report and associated charts.
Table 35: Formulas Associated with the MGI Sub-Element
Media Gateway VSP PC Sub-Element Bulk Collection Formula Mappings
Media Gateway VSP PC sub-element. The Media Gateway VSP PC sub-element maps to a Media Gateway VSP
Processor Card (PC) component associated with a specific Passport Packet Voice Gateway (PVG) device
operating in the Nortel CS2000 environment. The Bulk collection formulas for the Media Gateway VSP PC sub-
>Infrastructure->Media Gateway->VSP Processor Card.
VSP PC sub-element Bulk collection formula. This Bulk collection formula operates on a field that resides in a
AverageInboundUtilization INBYTES
IPLINKCAP
104
103
AverageOutboundUtilization OUTBYTES
IPLINKCAP
105
103
InboundPacketRate INPACKETS 106
OutboundPacketRate OUTPACKETS 107
TotalNumberOfDiscardedPackets INPACKETSDIS and
OUTPACKETSDIS
132
133
TotalNumberOfPacketExceptions INLOCALEXCEPTIONS and
INFWDEXCEPTIONS
134
135
TotalNumberOfTCPPackets INTCPPACKETSLOCAL
OUTTCPPACKETSLOCAL
108
114
TotalNumberOfUDPPackets INUDPPACKETSLOCAL and
OUTUDPPACKETSLOCAL
109
115
PVG Performance file. A PVG Performance file is a Bulk input file associated with a specific Media Gateway VSP
PC sub-element. The Bulk collection formula uses this field to map to the corresponding metric.
Specifically, the Nortel CS2000 Technology Pack defines the Bulk collection formula listed in Table 36. The table
shows the formula name, field name, and field number from the input file associated with the Media Gateway
VSP PC sub-element that the formula uses to map to the corresponding metric. This metric displays in the PVG
VSP Quality report.
Table 36: Formulas Associated with the Media Gateway VSP PC Sub-Element
Media Gateway VSP CC Sub-Element Bulk Collection Formula Mappings
Media Gateway VSP Call Card (CC) sub-element. The Media Gateway VSP CC sub-element maps to a Media
Gateway VSP CC component associated with a Passport Packet Voice Gateway (PVG) device operating in the
Nortel CS2000 environment. The Bulk collection formulas for the Media Gateway VSP CC sub-element reside
in this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Media
Gateway->VSP Call Signaling.
VSP CC sub-element Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a
PVG Performance file. A PVG Performance file is a Bulk input file associated with a specific Media Gateway VSP
CC sub-element. The Bulk collection formulas use these fields to map to the corresponding metrics.
shows the formula names, field name(s), and field number(s) from the input file associated with the Media
Gateway VSP CC sub-element that the formulas use to map to the corresponding metrics. Some of the metrics
produced by these Bulk collection formulas display in the PVG VSP Call Signaling report.
Table 37: Formulas Associated with the Media Gateway VSP CC Sub-Element
AvgCPUutilizationVSPCard VSPUTILAVG 136
CongestedSeconds CONGSECS 137
Failovers FAILOVERS 141
H248Retransmission INH248RETRAN
OUTH248RETRAN
140
139
NetworkCallFailure CALLFAILSNET 142
OverloadCmdRejected OVLDCMDSREJECTED 138
TotalMinutesOfUse ACTIVECALLAVG
LOG_TYPE
146
TotalSuccessfulCalls ACTIVECALLAVG
LOG_TYPE
146
TotalTDMCallFails CALLFAILTDM 143
Nortel SST Device Sub-Element Bulk Collection Formula Mappings
Nortel SST device sub-element. The Nortel SST device sub-element maps to a Nortel Session Server Trunk
device operating in the Nortel CS2000 environment. The Bulk collection formulas for the Nortel SST device sub-
>Infrastructure->SessionServer.
The Nortel CS2000 Technology Pack provides a Nortel SST Bulk Adaptor Design File that is maintained by IBM
Professional Services. The Nortel SST Bulk Adaptor Design File implements the Nortel SST device sub-element
Bulk collection formulas. These Bulk collection formulas operate on fields that reside in a Nortel SST file. A
Nortel SST file is a Bulk input file associated with a specific Nortel SST device sub-element. The Bulk collection
Specifically, the Nortel CS2000 Technology Pack defines the Bulk collection formulas listed in Table 38.
Nortel USP Device Bulk Collection Formula Mappings
sub-elements associated with the Universal Signaling Point (USP) device and its associated components. The Bulk
collection formulas for the USP device sub-element and associated component sub-elements reside in
Table 38: Formulas Associated with the Nortel SST Sub-Element
Formula
CallsReleasedBySST
Processor
SimultaneousCalls
appropriate subdirectories under this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP-
>Infrastructure->Signaling Gateway->.
USP Device Sub-Element Bulk Collection Formula Mappings
USP Linkset Sub-Element Bulk Collection Formula Mappings
USP Routeset Sub-Element Bulk Collection Formula Mappings
USP Carrier Link Sub-Element Bulk Collection Formula Mappings
USP Device Sub-Element Bulk Collection Formula Mappings
USP device sub-element. The USP device sub-element maps to a Universal Signaling Point (USP) device
operating in the Nortel CS2000 environment. The Bulk collection formulas for the USP sub-element reside in
this directory: FORMULAS->AP->Specific->Bulk->Carrier VOIP->Infrastructure->Signaling
Gateway->Device.
The Nortel CS2000 Technology Pack provides a USP Bulk Adaptor Design File that is maintained by IBM
Professional Services. The USP Bulk Adaptor Design File implements the USP device sub-element Bulk
collection formulas. These Bulk collection formulas operate on fields that reside in a Bulk input file associated
with a specific USP device sub-element. The Bulk collection formulas use these fields to map to the
shows the formula names and the field name(s) from the input file associated with the USP device sub-element
that the formulas use to map to the corresponding metric. Some of the metrics associated with these Bulk
collection formulas display in the USP Device Quality report.
Table 39: Formulas Associated with the USP Device Sub-Element
Formula Field Name(s)
TotalConnectionOrientedIPDistributionViolations Conn-Orient IP Dist Viol Count
TotalConnectionOrientedMessagesHandled Conn-Orient Msg Handled Count
TotalConnectionOrientedMessagesRoutingFailure Conn-Orient Msg Rtg Fail Count
TotalGTTAlternateRoutingOnCongestion Alt Routing on Cong Count
TotalGTTHopCounterViolation Hop Counter Violation Count
TotalGTTNoTranslationForAddress TFC Transmitted Count
TotalGTTPerformed GTT Performed Count
TotalGTTTranslationTypeNotFound Trans Type Not Found Count
TotalMessagesErrors The TotalMessagesErrors collection
formula calculates the resulting metric from
an internally defined messageErrors
array.
TotalMessagesHandled Total messages handled
USP Linkset Sub-Element Bulk Collection Formula Mappings
USP Linkset sub-element. The USP Linkset sub-element maps to a USP Linkset component associated with a
Universal Signaling Point (USP) device operating in the Nortel CS2000 environment. The Bulk collection
formulas for the USP Linkset sub-element reside in this directory: FORMULAS->AP->Specific->Bulk-
>Carrier VOIP->Infrastructure->Signaling Gateway->Linkset.
Professional Services. The USP Bulk Adaptor Design File implements the USP Linkset sub-element Bulk
with a specific USP Linkset sub-element. The Bulk collection formulas use these fields to map to the
shows the formula names and the field name(s) from the input file associated with the USP Linkset sub-element
that the formulas use to map to the corresponding metric. Some of the metrics associated with these Bulk
collection formulas display in the USP Linkset Quality report.
Table 40: Formulas Associated with the USP Linkset Sub-Element
TotalMessagesIncompatibility Msg Incompatibility
TotalMessagesTooLargeForSegmentation Msg too large for segmentation
TotalMSUDiscardedSCCPMessages Discarded MSUs Count
TotalOutOfSequenceSCCPMessages Out of sequence SCCP msg count
TotalReassemblyBufferUnavailable Reassembly buffer unavailable
TotalReassemblyFailed Reassembly failed
TotalReassemblyTimerExpired Reassembly Timer Expired
TotalSCCPRoutingFailure SCCP Routing Failure Count
TotalSegmentationFailed Segmentation failed
LinksetInactivityDuration Linkset Inactivity Duration
RSTReceived RST Received
RSTTransmitted RST Transmitted Count
TransferAllowedRoutingAvailableReceived TFA and TCA Received Count
TransferAllowedRoutingAvailableTransmitted TFA and TCA Transmitted Count
TransferControlledTransmitted TFC Transmitted Count
TransferProhibitedRoutingNotAvailableReceived TFP and TCP Received Count
TransferProhibitedRoutingNotAvailableTransmitted TFP and TCP Transmitted Count
USP Routeset Sub-Element Bulk Collection Formula Mappings
USP Routeset sub-element. The USP Routeset sub-element maps to a USP Routeset component associated with
a Universal Signaling Point (USP) device operating in the Nortel CS2000 environment. The Bulk collection
formulas for the USP Routeset sub-element reside in this directory: FORMULAS->AP->Specific->Bulk-
>Carrier VOIP->Infrastructure->Signaling Gateway->Routeset.
Professional Services. The USP Bulk Adaptor Design File implements the USP Routeset sub-element Bulk
with a specific USP Routeset sub-element. The Bulk collection formulas use these fields to map to the
shows the formula names and the field name(s) from the input file associated with the USP Routeset sub-element
that the formulas use to map to the corresponding metric. All of the metrics associated with these Bulk collection
formulas display in the USP Routeset Metrics report.
Table 41: Formulas Associated with the USP Routeset Sub-Element
USP Carrier Link Sub-Element Bulk Collection Formula Mappings
USP Carrier Link sub-element. The USP Carrier Link sub-element maps to a USP Carrier Link component
associated with a Universal Signaling Point (USP) device operating in the Nortel CS2000 environment. The Bulk
collection formulas for the USP Carrier Link sub-element reside in this directory: FORMULAS->AP-
>Specific->Bulk->Carrier VOIP->Infrastructure->Signaling Gateway->Link.
Professional Services. The USP Bulk Adaptor Design File implements the USP Carrier Link sub-element Bulk
with a specific USP Carrier Link sub-element. The Bulk collection formulas use these fields to map to the
shows the formula names and the field name(s) from the input file associated with the USP Carrier Link sub-
TransferRestrictedReceived TFR and TCR Received Count
TransferRestrictedTransmitted TFR and TCR Transmitted Count
TotalRoutesetCongested RouteSet Congested Count
TotalRoutesetManualBusy Routeset Man-busied Count
TotalRoutesetUnavailability Routset Unavailability Count
TotalRoutesetUnavailabilityDuration Routeset Unavailability Dur.
element that the formulas use to map to the corresponding metric. Some of the metrics associated with these Bulk
collection formulas display in the USP Linkset Quality report.
Table 42: Formulas Associated with the USP Carrier Link Sub-Element
LineCodeViolations Line - Code Violations
LineErroredSeconds Line - Errored Seconds
LineLossOfSignalSeconds Line - Loss of Signal Seconds
LineSeverelyErroredSeconds Line - Severely Errored Seconds
LinkFailureAllReasons SL failure-All reasons
LinkMSUreceived MSUs Received Count
LinkMSUtransmitted MSU Transmitted Count
LinkUnavailableDuration Unavailable Duration
LinkUtilization Link utilization
NOTES
Additional Copyright Information
The following copyright information is for software used by Netcool/Proviso.
Tcl 8.3.3, Combat/TCL 0.7.3, Combat/TCL 0.7.5, TclX 8.3, TK 8.3.3
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., Scriptics Corporation, and
other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any
purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any
distributions. No written agreement, license, or royalty fee is required for any of the authorized uses. Modifications to this software
may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly
indicated on the first page of each file where they apply.
IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT,
SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS
DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS,
OR MODIFICATIONS.
GOVERNMENT USE: If you are acquiring this software on behalf of the U.S. government, the Government shall have only
"Restricted Rights" in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause
52.227.19 (c) (2). If you are acquiring the software on behalf of the Department of Defense, the software shall be classified as
"Commercial Computer Software" and the Government shall have only "Restricted Rights" as defined in Clause 252.227-7013 (c)
(1) of DFARs. Notwithstanding the foregoing, the authors grant the U.S. Government and others acting in its behalf permission to
use and distribute the software in accordance with the terms specified in this license.
SCOTTY Stack
This software is copyrighted by Juergen Schoenwaelder, the Technical University of Braunschweig, the University of Twente, and
other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN AS IS BASIS, AND THE AUTHORS AND
Additional Copyright information
OR MODIFICATIONS.
Various copyrights apply to this package, listed in 3 separate parts below. Please make sure that you include all the parts. Up until
2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project
has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP
community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under
a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001.
Part 1: CMU/UCD copyright notice: (BSD like)
Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000
Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission
notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be
used in advertising or publicity pertaining to distribution of the software without specific written permission.
CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD
TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL,
INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS
OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS
ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Part 2: Networks Associates Technology, Inc copyright notice (BSD)
Copyright 2001, Networks Associates Technology, Inc
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of the NAI Labs nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Part 3: Cambridge Broadband Ltd. copyright notice (BSD)
Portions of this code are copyright 2001, Cambridge Broadband Ltd.
All rights reserved.
conditions are met:
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without
specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER AS IS AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
BLT 2.4u
Portions (c) 1993 AT&T, (c) 1993 - 1998 Lucent Technologies, (c) 1994-1998 Sun Microsystems, Inc., and (c) 1987-1993 The
Regents of the University of California.
notice appear in supporting documentation, and that the names of AT&T, Lucent Technologies Inc., Sun Microsystems, Inc. and
The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without
specific written permission.
THE COPYRIGHT HOLDERS AND OTHER CONTRIBUTORS DISCLAIM ALL WARRANTIES WITH REGARD TO
THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO
EVENT SHALL THE COPYRIGHT HOLDERS OR OTHER CONTRIBUTORS BE LIABLE FOR ANY SPECIAL,
CMU-SNMP 1.14
CMU/UCD copyright notice: (BSD like) Copyright 1989, 1991, 1992 by Carnegie Mellon University
Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California
All Rights Reserved
Scotty 2.8, incrTCL 3.0, [incr TCL] 3.2
Portions Copyright (c) 1987-1994 The Regents of the University of California. Copyright (c) 1994-1995 Sun Microsystems, Inc.
This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following
terms apply to all files associated with the software unless explicitly disclaimed in individual files.
AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND
OR MODIFICATIONS.
RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in
subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS 252.227-7013 and FAR 52.227-
19.
Portions Copyright (c) 1993-1998 Lucent Technologies, Inc.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both that the copyright notice and warranty
disclaimer appear in supporting documentation, and that the names of Lucent Technologies any of their entities not be used in
advertising or publicity pertaining to distribution of the software without specific, written prior permission.
Lucent disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness. In no
event shall Lucent be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of
use, data or profits, whether in an action of contract, negligence or other tortuous action, arising out of or in connection with the
use or performance of this software.
UCD SNMP 4.2.5
Portions Copyright 1989, 1991, 1992 by Carnegie Mellon University. Derivative Work - 1996, 1998-2000, Copyright 1996, 1998-
2000 The Regents of the University of California All Rights Reserved
Portions Copyright: (c) 2001-2003, Networks Associates Technology, Inc, (c) 2001-2003, Cambridge Broadband Ltd, (c) 2003-
2005, Sparta, Inc., (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications,
(c) Fabasoft R&D Software GmbH & Co KG, 2003 oss@fabasoft.com. All rights reserved.
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
3. Neither the names of Networks Associates Technology, Inc, Cambridge Broadband Ltd., Sparta, Inc., Cisco, Inc, Beijing
University of Posts and Telecommunications, Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product
names, nor the names of their contributors may be used to endorse or promote products derived from this software without specific
prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS `ÀS IS'' AND ANY
THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
JDOM 1.0
Copyright (C) 2000-2004 Jason Hunter & Brett McLaughlin. All rights reserved.
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that follows
these conditions in the documentation and/or other materials provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written
permission. For written permission, please contact <request_AT_jdom_DOT_org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior written
permission from the JDOM Project Management <request_AT_jdom_DOT_org>.
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution and/or
in the software itself an acknowledgement equivalent to the following:
"This product includes software developed by the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment
may be graphical using the logos available at http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED `ÀS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally
created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more
information on the JDOM Project, please see <http://www.jdom.org/>.
Regex 1.1a
Copyright (C) 1996, 1999 Vassili Bykov. It is provided to the Smalltalk community in hope it will be useful.
1. This license applies to the package as a whole, as well as to any component of it. By performing any of the activities described
below, you accept the terms of this agreement.
2. The software is provided free of charge, and `às is'', in hope that it will be useful, with ABSOLUTELY NO WARRANTY. The
entire risk and all responsibility for the use of the software is with you. Under no circumstances the author may be held responsible
for loss of data, loss of profit, or any other damage resulting directly or indirectly from the use of the software, even if the damage
is caused by defects in the software.
3. You may use this software in any applications you build.
4. You may distribute this software provided that the software documentation and copyright notices are included and intact.
5. You may create and distribute modified versions of the software, such as ports to other Smalltalk dialects or derived work,
provided that:
a. any modified version is expressly marked as such and is not misrepresented as the original software;
b. credit is given to the original software in the source code and documentation of the derived work;
c. the copyright notice at the top of this document accompanies copyright notices of any modified version.
Xwpick
Copyright 1993, 1994 by Evgeni Chernyaev
Permission to use, copy, modify, and distribute this software and its documentation for non-commercial purpose is hereby granted
without fee, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission
notice appear in supporting documentation. Xwpick is used for printing utilities.
Sieve of Erastothenes
Copyright Frank Pilhofer, fp@fpx.de
conditions are met:
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
Neither the name of Frank Pilhofer nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,

NetcoolProviso Nortel - CS2K 43X PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetcoolProviso Nortel - CS2K 43X PDF

Uploaded by

Copyright:

Available Formats

IBM

may not offer the

, the IBM logo

, the Tivoli logo

is a registered trademark of Intel Corporation or

is a registered trademark of The Open Group in

and all Java-based

You might also like