NetcoolProviso-Lucent Stinger Device 1.1.1.0 Tech Pack User Guide

Netcool®/Proviso®
4.3-U
Lucent Stinger DSL Application Pack User’s Guide

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

in source language, which illustrate programming
Trademarks
AIX®, DB2®, developerWorks®, eServer, i5/OS®,
IBM®, the IBM logo®, IBMLink, iSeries®, Lotus®,
Netcool®, Netcool/Proviso®, OMEGAMON®, Java™ and all Java-based
Passport Advantage®, pSeries®, Rational®, Redbooks®, trademarks and logos are
OS/390®, OS/400®, Tivoli®, the Tivoli logo®, Tivoli trademarks or registered
Enterprise Console®, WebSphere®, and zSeries® are trademarks of Sun Microsystems,
trademarks or registered trademarks of International Inc. in the United States, other
Business Machines Corporation in the United States, countries, or both.
other countries, or both.
UNIX® is a registered trademark of The Open Group in
Intel® is a registered trademark of Intel Corporation or the United States and other countries.
its subsidiaries in the United States, other countries, or
both. Other company, product, and service names may be
trademarks or service marks of others.
Linux is a trademark of Linus Torvalds in the United
States, other countries, or both.
Microsoft® and Windows® are registered trademarks of Copyright International Business Machines
Microsoft Corporation in the United States, other Corporation 2008. All rights reserved.
countries, or both. US Government Users Restricted Rights — Use,
duplication or disclosure restricted by GSA ADP
Schedule Contract with IBM Corp.
Contents
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
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
Reporter Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Bit Health Reporter Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Bit Throughput Reporter Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Packet Throughput Reporter Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Packet Health Reporter Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Report Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Health (Octets) Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Health (Packet) Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Health Distribution Range - Inbound Errors (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Health Distribution Range - Inbound Errors (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Health Distribution Range - Outbound Errors (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Health Distribution Range - Outbound Errors (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Health Summary Group (Bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Health Summary Group (Packet). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U v
Health Summary Resource (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Health Summary Resource (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Threshold Violation - Inbound Errors (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Threshold Violation - Inbound Errors (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Threshold Violation - Outbound Errors (Bit). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Threshold Violation - Outbound Errors (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Throughput (Octets) Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Throughput (Packet) Details. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Throughput Distribution Range - Inbound Utilization (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Throughput Distribution Range - Outbound Utilization (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Throughput Summary Group (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Throughput Summary Group (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Throughput Summary Resource (Bit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Throughput Summary Resource (Packet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 3: Devices and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Summary of Device Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Supported MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
RFC1213-MIB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
IF-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
ASCEND-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ASCEND-CHASSIS-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
ASCEND-DEBUG-MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Chapter 4: Element and Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Lucent Stinger® DSL Access Concentrator Device Element Properties . . . . . . . . . . . . . . . . . . . . . . 35
Lucent Stinger® DSL Access Concentrator Device Sub-Element Properties . . . . . . . . . . . . . . . . . . 36
Stinger DSL Device Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Stinger Ethernet Interface DSLAM Card Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . 37
Stinger Ethernet Interface Uplink Card Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . 39
Chapter 5: Sub-Element Grouping Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Sub-Element Collection Grouping Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Stinger Ethernet Interface DSLAM Card Sub-Element Collection Grouping Rules . . . . . . . . . . 44
vi Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
IGS Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
LucentStinger Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DSLAM Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Stinger Ethernet Interface Uplink Card Sub-Element Collection Grouping Rules . . . . . . . . . . . 45
IGS Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
LucentStinger Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Uplinks Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Sub-Element NOC Reporting Grouping Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Bit Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Lucent Stinger Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Bit Metrics Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
UpLinks Grouping Rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
%(Element.NAME) Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Packet Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Lucent Stinger Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Packet Metrics Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Uplinks Grouping Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Chapter 6: Defined Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Sub-Element Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Stinger DSL Device Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Stinger Ethernet Interface DSLAM Card Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Stinger Ethernet Interface Uplink Card Sub-Element Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Sub-Element Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Stinger DSL Device Sub-Element Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Stinger Ethernet Interface DSLAM Card Sub-Element Label. . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Stinger Ethernet Interface Uplink Card Sub-Element Label . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Sub-Element Family Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Chapter 7: SNMP Collection Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Netcool/Proviso Formula Tree for the Lucent Stinger Application Pack. . . . . . . . . . . . . . . . . . . . . . 59
Generic Formulas and Specific Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U vii
Formula Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Delivered Packets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Delivered U/M/B HC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Delivered U/M/B LC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Delivered U/NU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Inbound Broadcast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Inbound Broadcast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Inbound Broadcast LC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Inbound Discarded (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Inbound Discards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Inbound Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Inbound Errors (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Inbound Multicast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Inbound Multicast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Inbound Multicast LC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Inbound Non-Unicast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Inbound Throughput (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Inbound Throughput HC (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Inbound Throughput LC (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Inbound Unicast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Inbound Unicast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Inbound Unicast LC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Inbound Utilization (percent). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Inbound Utilization HC (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Inbound Utilization HC/HS (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Inbound Utilization LC (percent). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Inbound Volume (octets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Inbound Volume HC (octets). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Inbound Volume LC (octets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Outbound Broadcast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Outbound Broadcast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Outbound Broadcast LC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Outbound Discarded (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Outbound Discards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Outbound Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Outbound Errors (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
viii Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
Outbound Multicast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Outbound Multicast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Outbound Multicast LC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Outbound Non-Unicast (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Outbound Throughput (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Outbound Throughput HC (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Outbound Throughput LC (bps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Outbound Unicast (pps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Outbound Unicast HC (pps) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Outbound Unicast LC (pps). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Outbound Utilization (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Outbound Utilization HC (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Outbound Utilization HC/HS (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Outbound Utilization LC (percent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Outbound Volume (octets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Outbound Volume (PDUs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Outbound Volume HC (octets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Outbound Volume LC (octets) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Transmitted U/M/B/D/E HC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Transmitted U/M/B/D/E LC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Transmitted U/NU/D/E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 8: Discovery Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
Netcool/Proviso Discovery Formula Tree for the Lucent Stinger Application Pack . . . . . . . . . . . . 141
Discovery Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
LucentStinger_disc_device_formula Discovery Formula. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
LucentStinger_disc_ports_formula Discovery Formula . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Appendix A: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Configure the Application Pack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Other Tasks and Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Verifying Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Changing Predefined Threshold Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U ix
x Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
Preface
This manual describes the Netcool/Proviso Lucent Stinger Application Pack, focusing on the Lucent Stinger®
DSL Access Concentrator environment. Specifically, the manual describes the reports for displaying information
about the devices and technologies that operate in the Lucent Stinger® DSL Access Concentrator environment.
The manual also describes the data collection model, properties, resources, collection formulas, and metrics that
the Lucent Stinger Application Pack provides to create the associated reporter sets.
Audience
The audiences for this manual are the network administration engineers at Micromuse customer sites who will
install, configure, and use the Lucent Stinger Application Pack as part of their Netcool/Proviso installation.
Micromuse Professional Services engineers may also find this manual useful.
To install and use the Lucent Stinger Application 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 Lucent Stinger Application Pack deals
with, in this case Lucent Stinger® DSL Access Concentrator.
Organization
This guide is organized as follows:
• Chapter 1, Introduction
Provides a general introduction to application packs.
• Chapter 2, Supported Reports
Provides information about the reports that the Lucent Stinger Application Pack provides for each device
operating in the Lucent Stinger® DSL Access Concentrator environment.
• Chapter 3, Devices and Services
Describes the devices and services that the Lucent Stinger Application Pack supports.
• Chapter 4, Element and Sub-Element Properties
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U xi
Preface
Describes the properties that the Lucent Stinger Application Pack discovers during the inventory process.
• Chapter 5, Sub-Element Grouping Rules
Describes the sub-element collection grouping rules and the NOC reporting grouping rules that the Lucent
Stinger Application Pack defines.
• Chapter 6, Defined Resources
Provides information about the elements and sub-elements that the application pack defines in the Proviso
database.
• Chapter 7, SNMP Collection Formulas
Provides information about the SNMP collection formulas that the Lucent Stinger Application Pack
provides for devices operating in the Lucent Stinger® DSL Access Concentrator environment that use an
SNMP Agent.
• Chapter 8, Discovery Formulas
Provides information about the Discovery formulas that the Lucent Stinger Application Pack provides for
devices operating in the Lucent Stinger® DSL Access Concentrator environment.
• Appendix A, Configuration
Describes how to configure the Lucent Stinger Application Pack.
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.
• 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 Application 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.
xii Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
Preface
Figure 1: Netcool/Proviso Modules

DataLoad DataChannel DataMart DataView
collects computes provides data produces and
network data. aggregations management manages reports.
and stores data and applications.
in DataMart.
Netcool/Proviso Documentation
Netcool/Proviso documentations 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
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U xiii
Preface
xiv Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
Chapter 1: Introduction
This chapter discusses the following topics:
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
Overview
Netcool/Proviso Application Packs are individually installed modules that contain discovery, grouping,
collection, and reporting instructions created by Application Pack developers or Professional Services personnel
for a specific network technology or network equipment provider, such as Lucent Stinger® DSL Access
Concentrator.
Once installed, an Application 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 Application 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 Application 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 Application Pack has been installed, an inventory process must be run so that the
Application Pack’s 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, an Application 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
Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U 1
the database, the inventory process organizes the sub-elements according to the grouping rules provided by
an Application 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, an Application 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 an
Application Pack’s target network resources. An Application 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, an Application 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, an Application 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 an Application 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.
2 Netcool/Proviso Lucent Stinger DSL Application Pack User’s Guide, Version 4.3-U
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-element’s 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
Application Pack.
An Application 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.
An Application 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 Application 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
Topic Page
Reporter Sets 5
Report Descriptions 7
Overview
The Lucent Stinger Application Pack supplies a set of reports suitable for displaying information about the
devices and activity associated with the Lucent Stinger® DSL Access Concentrator environment.
Reports contain metrics that are generated by the formulas that this application 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 User’s Guide. This Application Pack User’s Guide
assumes an understanding of the report-related topics discussed in the Netcool/Proviso DataView User’s Guide.
Reporter Sets
A reporter set contains a group of reporters that together provide information about a specific technology or a
vendor device. Application pack developers use the Reporter Set Wizard to choose the type of template upon
which to base the reporter set.
Specifically, the Lucent Stinger Application Pack uses reporter sets as the framework for defining the reports that
display in meaningful ways on a WWW portal the collected information about the devices and technologies that
operate in the Lucent Stinger® DSL Access Concentrator environment.
See the Netcool/Proviso DataView User’s Guide for more information about reporter sets and the Reporter Set Wizard.
The Lucent Stinger Application Pack provides the following reporter sets:
• Bit Health Reporter Set
• Bit Throughput Reporter Set
• Packet Health Reporter Set
• Packet Throughput Reporter Set
The following sections briefly describe each of the reporter sets that the Lucent Stinger Application Pack
provides.
Bit Health Reporter Set

The Bit Health Reporter Set contains the following seven reporters:
• Health (Octets) Details
• Health Summary Group (Bit)
• Health Summary Resource (Bit)
• Threshold Violation - Inbound Errors (Bit)
• Threshold Violation - Outbound Errors (Bit)
• Health Distribution Range - Inbound Errors (Bit)
• Health Distribution Range - Outbound Errors (Bit)
See Report Descriptions on page 7 for more information on these reporters.
Bit Throughput Reporter Set

The Bit Throughput Reporter Set contains the following five reporters:
• Throughput Summary Group (Bit)
• Throughput Summary Resource (Bit)
• Throughput (Octets) Details
• Throughput Distribution Range - Inbound Utilization (Bit)
• Throughput Distribution Range - Outbound Utilization (Bit)
Packet Throughput Reporter Set

The Packet Throughput Reporter Set contains the following three reporters:
• Throughput Summary Group (Packet)
• Throughput Summary Resource (Packet)
• Throughput (Packet) Details
Packet Health Reporter Set

The Packet Health Reporter Set contains the following seven reporters:
• Health (Packet) Details
• Health Summary Group (Packet)
• Health Summary Resource (Packet)

• Threshold Violation - Inbound Errors (Packet)
• Threshold Violation - Outbound Errors (Packet)
• Health Distribution Range - Inbound Errors (Packet)
• Health Distribution Range - Outbound Errors (Packet)
Report Descriptions
The sections that follow provide reference information about the reports that the Lucent Stinger Application
Pack provides.
The following list identifies the information provided for each report:
• Report Name — Specifies the report name.
• Deployed At — Specifies the location or locations in the NOC Reporting tree where the report is deployed.
The report may not be currently deployed, in which case this section specifies: Report is not deployed.
• Report Description — Provides a brief description of the report.
• Metrics Displayed on Report — Identifies the metrics (using the Generic formula or SNMP collection
formula name (including the path in the Formula tree).
Health (Octets) Details
Deployed At
These timeseries charts are accessed through drilldowns from other reports.
Report Description
The Health (Octets) Details report displays a number of Resource Timeseries charts.
Metrics Displayed on Report

This report displays the following metrics:
• FORMULAS->AP->Generic->Universal->Errors->Inbound Errors (PDUs)
For more information, see Inbound Errors (PDUs) on page 72.
• FORMULAS->AP->Generic->Universal->Throughput->Outbound Volume (octets)
For more information, see Outbound Volume (octets) on page 130.
• FORMULAS->AP->Generic->Universal->Errors->Outbound Errors (PDUs)
For more information, see Outbound Errors (PDUs) on page 106.
• FORMULAS->AP->Generic->Universal->Throughput->Inbound Volume (octets)
For more information, see Inbound Volume (octets) on page 94.
Health (Packet) Details
Deployed At
These timeseries charts are accessed through drilldowns from other reports.
Report Description
The Health (Packet) Details report displays a number of Resource Timeseries charts.

• FORMULAS->AP->Generic->Universal->Throughput->Outbound Volume (PDUs)
For more information, see Outbound Volume (PDUs) on page 131.)
• FORMULAS->AP->Generic->Universal->Congestion Discards->Inbound Discarded
(PDUs)
For more information, see Inbound Discarded (PDUs) on page 68.
• FORMULAS->AP->Generic->Interface->Delivered Packets
For more information, see Delivered Packets on page 61.
• FORMULAS->AP->Generic->Universal->Congestion Discards->Outbound Discarded
(PDUs)
For more information, see Outbound Discarded (PDUs) on page 102.
Health Distribution Range - Inbound Errors (Bit)
Deployed At
These charts are accessed through drilldowns from other reports.
Report Description
The Health Distribution Range - Inbound Errors (Bit) report displays TopN chart/table pairs.

This report displays the following metric:
Health Distribution Range - Inbound Errors (Packet)
Deployed At
Report Description
The Health Distribution Range - Inbound Errors (Packet) report displays TopN chart/table pairs.

Health Distribution Range - Outbound Errors (Bit)
Deployed At
Report Description
The Health Distribution Range - Outbound Errors (Bit) report displays TopN chart/table pairs.

Health Distribution Range - Outbound Errors (Packet)
Deployed At
Report Description
The Health Distribution Range - Outbound Errors (Packet) report displays TopN chart/table pairs.

Health Summary Group (Bit)
Deployed At
This report is deployed at the following locations in the NOC Reporting tree:
• NOC Reporting->Lucent Stinger->Bit Metrics->DSLAM
• NOC Reporting->Lucent Stinger->Bit Metrics->UpLinks
Report Description
The Health Summary Group (Bit) report displays a pair of Resource Distribution charts over a Group Summary
Table (GST).

• For more information, see Inbound Volume (octets) on page 94.
Note that the metric names listed are the Generic or SNMP collection formula names and paths as they exist in
the Formula tree.
Health Summary Group (Packet)
Deployed At
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM->UpLinks
Report Description
The Health Summary Group (Packet) report displays a pair of Resource Distribution charts over a Group
Summary Table (GST).

For more information, see Outbound Volume (PDUs) on page 131.
(PDUs)
For more information, see Inbound Discarded (PDUs) on page 68.
(PDUs)
• For more information, see Outbound Errors (PDUs) on page 106.
Health Summary Resource (Bit)
Deployed At
• NOC Reporting->Lucent Stinger->Bit Metrics->DSLAM->%(Element.NAME)
• NOC Reporting->Lucent Stinger->Bit Metrics->DSLAM->%(Element.NAME)-
>%(IGS_LucentStingerDSLAMCard)
• NOC Reporting->Lucent Stinger->Bit Metrics->UpLinks->%(Element.NAME)
>%(IGS_LucentStingerUpLinkCard)
The deployment locations make use of the IGS_LucentStingerDSLAMCard and
IGS_LucentStingerDSLAMCard properties.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 and Stinger Ethernet Interface DSLAM Card Sub-
Element Properties on page 37 for more information.
Report Description
The Health Summary Resource (Bit) report displays a pair of Resource Distribution charts over a Resource
Summary Table (RST).

For more information, see Inbound Volume (octets) on page 94.
Health Summary Resource (Packet)
Deployed At
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM->%(Element.NAME)
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM->%(Element.NAME)-
• NOC Reporting->Lucent Stinger->Packet Metrics->UpLinks->%(Element.NAME)
Report Description
The Health Summary Resource (Bit) report displays a pair of Resource Distribution charts over a Resource
Summary Table (RST). A Resource Distribution chart (often referred to as a pie chart) shows the distribution of
resources across specific ranges. Typically, a legend for the Resource Distribution chart appears in the report.

For more information, see Outbound Volume (PDUs) on page 131.
(PDUs) (For more information, see Inbound Discarded (PDUs) on page 68.)
(PDUs)
Threshold Violation - Inbound Errors (Bit)
Deployed At
The RTT is typically accessed through drilldowns from other reports.
Report Description
The Threshold Violation - Inbound Errors (Bit) report displays a RTT (Resource Threshhold Table).

Threshold Violation - Inbound Errors (Packet)
Deployed At
Report Description
The Threshold Violation - Inbound Errors (Packet) report displays a RTT (Resource Threshhold Table).

Threshold Violation - Outbound Errors (Bit)
Deployed At
Report Description
The Threshold Violation - Outbound Errors (Bit) report displays a RTT (Threshold Violation table).

Threshold Violation - Outbound Errors (Packet)
Deployed At
Report Description
The Threshold Violation - Outbound Errors (Packet) report displays a RTT (Threshold Violation table).

Throughput (Octets) Details
Deployed At
Report Description
The Throughput (Octets) Details report displays a pair of Ratio (pie) charts above a number of Resource
Timeseries charts.

• FORMULAS->AP->Generic->Universal->Utilization->Outbound Utilization (percent)
For more information, see Outbound Utilization (percent) on page 123.
• FORMULAS->AP->Generic->Universal->Throughput->Outbound Throughput (bps)
For more information, see Outbound Throughput (bps) on page 114.
• FORMULAS->AP->Generic->Universal->Throughput->Inbound Throughput (bps)
For more information, see Inbound Throughput (bps) on page 78.
• FORMULAS->AP->Generic->Universal->Utilization->Inbound Utilization (percent)
For more information, see Inbound Utilization (percent) on page 87.
Throughput (Packet) Details
Deployed At
Report Description
The Throughput (Packet) Details report displays a pair of Ratio (pie) charts above a number of Resource
Timeseries charts.

• FORMULAS->AP->Generic->Interface->Inbound Multicast (pps)
For more information, see Inbound Multicast (pps) on page 73.
• FORMULAS->AP->Generic->Interface->Inbound Broadcast (pps)
For more information, see Inbound Broadcast (pps) on page 65.
• FORMULAS->AP->Generic->Interface->Inbound Unicast (pps)
For more information, see Inbound Unicast (pps) on page 83.
• FORMULAS->AP->Generic->Interface->Outbound Multicast (pps)
For more information, see Outbound Multicast (pps) on page 107.
• FORMULAS->AP->Generic->Interface->Outbound Broadcast (pps)
For more information, see Outbound Broadcast (pps) on page 97.
• FORMULAS->AP->Generic->Interface->Outbound Unicast (pps)
For more information, see Outbound Unicast (pps) on page 119.
Throughput Distribution Range - Inbound Utilization (Bit)
Deployed At
Report Description
The Throughput Distribution Range - Inbound Utilization (Bit) report displays TopN chart/table pairs.

Throughput Distribution Range - Outbound Utilization (Bit)
Deployed At
Report Description
The Throughput Distribution Range - Outbound Utilization (Bit) report displays TopN chart/table pairs.

Throughput Summary Group (Bit)
Deployed At
• NOC Reporting->Lucent Stinger->Bit Metrics->DSLAM
• NOC Reporting->Lucent Stinger->Bit Metrics->UpLinks
Report Description
The Throughput Summary Group (Bit) report displays a pair of Resource Distribution charts over a Group

• FORMULAS->AP->Generic->Universal->Utilization->Outbound Throughput (bps)
• FORMULAS->AP->Generic->Universal->Utilization->Inbound Throughput (bps)
Throughput Summary Group (Packet)
Deployed At
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM
• NOC Reporting->Lucent Stinger->Packet Metrics->UpLinks
Report Description
The Throughput Summary Group (Packet) report displays a pair of Resource Distribution charts over a Group

For more information, see Inbound Multicast (pps) on page 73.
Throughput Summary Resource (Bit)
Deployed At
• NOC Reporting->Lucent Stinger->Bit Metrics->DSLAM->%(Element.NAME)
• NOC Reporting->Lucent Stinger->Bit Metrics->UpLinks->%(Element.NAME)
Report Description
The Throughput Summary Resource (Bit) report displays a pair of Resource Distribution charts over a Resource
Summary Table (RST).

• FORMULAS->AP->Generic->Universal->Throughput->Outbound Throughput (bps)
• FORMULAS->AP->Generic->Universal->Throughput->Inbound Throughput (bps)
Throughput Summary Resource (Packet)
Deployed At
• NOC Reporting->Lucent Stinger->Packet Metrics->DSLAM->%(Element.NAME)
• NOC Reporting->Lucent Stinger->Packet Metrics->UpLinks->%(Element.NAME)
Report Description
The Throughput Summary Resource (Packet) report displays a pair of Ratio charts over a Resource Summary
Table (RST).

For more information, see Inbound Multicast (pps) on page 73.)
NOTES
Chapter 3: Devices and Services
Topic Page
Summary of Device Technology 31
Supported MIBs 32
Overview
The Lucent Stinger® DSL Access Concentrator technology is embodied in a number of different device models.
Each model offers cost-effective Digital Subscriber Line (DSL) networking services for a variety of businesses
and residential customers.
This chapter provides a summary of the Lucent Stinger® DSL Access Concentrator device technology and the
associated Management Information Bases (MIBs), which the Lucent Stinger Application Pack is designed to
support.
Note: The Lucent Stinger Application Pack operates with Lucent Stinger® DSL Access Concentrator devices
running Version 3.4.1 of the operating system.
Summary of Device Technology

Lucent Stinger® DSL Access Concentrator device technology is embodied in the following devices:
• Stinger® LS/LS+ DSL Access Concentrator — The Stinger® LS/LS+ DSL Access Concentrator is a high-
capacity, mid-sized Asynchronous Transfer Mode (ATM) standards-based access concentrator for DSL
services. The Stinger LS+/LS is ideal for small central offices and multi-tenant, multi-dwelling building
deployments.
• Stinger® RT DSL Access Concentrator — The Stinger® RT DSL Access Concentrator chassis Model 1 and
Model 2 are hardened versions of the Stinger LS chassis and are designed for use in outdoor cabinets. These
chassis models have a space-saving front-loadable design that is ideal for locations with depth and rear access
restrictions. With the use of the new Line Interface Protection Module (LIPM), the Stinger LS+ provides
substantially increased port density along with flexible mounting options including wall and back-to-back
scenarios.
• Stinger RT Model 1 chassis — The Stinger RT Model 1 chassis is designed to fit 19-inch racks used in
worldwide markets and supports up to 240 ports.
• Stinger RT Model 2 chassis — The Stinger RT Model 2 chassis supports up to 336 ports and is designed to
fit the 23-inch racks used primarily in U.S. markets.
The Lucent Stinger Application Pack is designed to work with the Lucent Stinger® DSL Access Concentrator
technology embodied in these devices by reporting such device-related metrics as CPU utilization (percent), CPU
memory utilization (percent), and so forth.
Note: It is impractical and beyond the scope of this Application Pack User’s Guide to provide exhaustive
descriptions and explanations of the Lucent Stinger® DSL Access Concentrator 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.
Supported MIBs
The Lucent Stinger Application Pack collects performance, usage, and environmental metrics using an SNMP
collection model. This Application Pack requires read-only access to the SNMP Agents associated with the
Lucent Stinger® DSL Access Concentrator devices that provide SNMP Agent support, as defined in the
following Management Information Bases (MIBs):
• RFC1213-MIB
• IF-MIB
• ASCEND-MIB
• ASCEND-CHASSIS-MIB
• ASCEND-DEBUG-MIB
RFC1213-MIB
The RFC1213-MIB (located in the file named rfc1213-MIB-II) is a Management Information Base (MIB) that
defines objects associated with a variety of groups. The following list provides examples of these groups:
• system
• interfaces
• at
• ip
• icmp
The Lucent Stinger Application Pack makes use of the system group that the RFC1213-MIB defines as objects
associated with system operation, including system uptime, system name, system services, and so forth. The
following list provides examples of the system group objects:
• sysUpTime
• sysName
• sysLocation
• sysServices
IF-MIB
The IF-MIB (located in the file named rfc2233-IF-MIB) describes generic objects for network interface
sublayers. This MIB is an updated version of the MIB-II’s ifTable, and incorporates the extensions defined in
the RFC1229-MIB (located in the file named rfc1229-GINTF).
ASCEND-MIB
The ASCEND-MIB (generated automatically from ascend.mib.in and *.mibdef) defines objects related
to the Ascend Communications enterprise OID. These objects include the following:
• Ascend family object
• Ascend notification objects
• Ascend chassis slot objects
• Ascend host type objects
• Ascend LAN type objects
ASCEND-CHASSIS-MIB
The ASCEND-CHASSIS-MIB (generated automatically from chassis.mib.in and *.mibdef) defines
objects that manage the slots associated with the Lucent Stinger® DSL Access Concentrator devices. The Lucent
Stinger Application Pack makes use of some objects from the ASCEND-CHASSIS-MIB including the following:
• slotIfIndex
• slotIfItemIndex
• slotIfSlotIndex
• slotIfShelfNumber
The Lucent Stinger Application Pack makes use of these objects in Discovery formulas. See Chapter 8, Discovery
Formulas for more information.
ASCEND-DEBUG-MIB
The ASCEND-DEBUG-MIB (located in the file named debug.mib) is part of the Ascend Enterprise MIB. It
reports debug information on the system.
NOTES
Chapter 4: Element and Sub-Element
Properties
Topic Page
Lucent Stinger® DSL Access Concentrator Device Element Properties 35
Lucent Stinger® DSL Access Concentrator Device Sub-Element Properties 36
Overview
A Netcool/Proviso property is an attribute or characteristic of an element or sub-element. Typically, a

Netcool/Proviso Application Pack uses an inventory process to collect information generated by the devices,
interfaces, and services operating in the technology environment it supports.
An application 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 Lucent Stinger Application Pack attaches Netcool/Proviso properties to sub-elements associated with the
devices and components that operate in the Lucent Stinger® DSL Access Concentrator 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.
Note: The following sections refer to sub-element names and sub-element properties without using the word
Netcool/Proviso. The following sections assume that these are Netcool/Proviso defined property names.
Lucent Stinger® DSL Access Concentrator Device Element Properties

The Lucent Stinger Application Pack does not define any properties for Lucent Stinger® DSL Access
Concentrator device elements.
Chapter 4: Element and Sub-Element Properties
Lucent Stinger® DSL Access Concentrator Device Sub-Element

Properties
The Lucent Stinger Application Pack defines properties for the following sub-elements associated with each
Lucent Stinger® DSL Access Concentrator device element:
• Stinger DSL Device Sub-Element Properties
• Stinger Ethernet Interface DSLAM Card Sub-Element Properties
• Stinger Ethernet Interface Uplink Card Sub-Element Properties
The following sections discuss the defined properties for these sub-elements.
Stinger DSL Device Sub-Element Properties

The Lucent Stinger Application Pack provides a LucentStinger_disc_device_formula Discovery
formula that defines the characteristics of and discovers information related to Stinger DSL Device sub-elements.
The Stinger DSL Device sub-element maps to a specific Lucent Stinger® DSL Access Concentrator device
running in the network. There is one Stinger DSL Device sub-element for each device operating in the Lucent
Stinger® DSL Access Concentrator environment.
The Lucent Stinger Application Pack uses the LucentStinger_disc_device_formula Discovery
formula to attach the properties listed in Table 1 to the Stinger DSL Device sub-element. The
LucentStinger_disc_device_formula Discovery formula makes use of MIB objects defined in the
following MIBs:
• RFC1213-MIB (located in the file named rfc1213-MIB-II)

• ASCEND-CHASSIS-MIB (generated automatically from chassis.mib.in and *.mibdef)
See LucentStinger_disc_device_formula Discovery Formula on page 142 for information about the
LucentStinger_disc_device_formula Discovery formula.
The table lists the Netcool/Proviso property name along with a short description of its meaning.
Table 1: Stinger DSL Device Sub-Element Properties
Netcool/Proviso Property Description
AP_EDP Specifies the ID of the external application pack developer. The

Discovery formula specifies the string IGS. This property is used in
NOC reporting grouping rules.
IGS_VendorName Specifies the name of the device vendor. The Discovery formula
specifies the string Lucent_Stinger. This property is used in
sub-element collection and NOC reporting grouping rules.
Stinger Ethernet Interface DSLAM Card Sub-Element Properties

The Lucent Stinger Application Pack provides a LucentStinger_disc_ports_formula Discovery
formula that defines the characteristics of and discovers information related to Stinger Ethernet Interface
DSLAM Card sub-elements. The Stinger Ethernet Interface DSLAM Card sub-element maps to the DSLAM
Ethernet network interface card associated with a specific Lucent Stinger® DSL Access Concentrator device
running in the network. There is one Stinger Ethernet Interface DSLAM Card sub-element for each DSLAM
Ethernet network interface card operating in the Lucent Stinger® DSL Access Concentrator environment.
The Lucent Stinger Application Pack uses the LucentStinger_disc_ports_formula Discovery
formula to attach the properties listed in Table 2 to the Stinger Ethernet Interface DSLAM Card sub-element.
The LucentStinger_disc_ports_formula Discovery formula makes use of MIB objects defined in
the following MIBs:

LucentStinger_disc_ports_formula Discovery formula.
Table 2: Stinger Ethernet Interface DSLAM Card Sub-Element Properties

sub-element collection and sub-element NOC reporting grouping
rules.
See the following sections:

• IGS Grouping Rule on page 44 (Stinger Ethernet Interface
DSLAM Card)
• Lucent Stinger Grouping Rule on page 47 (Bit Metrics)
• Lucent Stinger Grouping Rule on page 49 (Packet Metrics)
AP_ifSpeed Specifies the speed of the network interface. This value varies,
depending on the network interface. Possible values include
“1000000”.
The MIB-II application pack defines this property.
AP_ifStatus Specifies the desired state of the network interface. Possible values
include: up:up and up:down.
DisplaySpeed Specifies the AP_ifSpeed property value in a readable format.

Possible values include "100 Mbps" and "10 Mbps".
The Discovery formula uses %LinkSpeed Mbps to calculate

the speed of the network interface. See LucentStinger_disc_ports_formula
Discovery Formula on page 143 for more information.
EtherSpeed The Discovery formula uses the ifSpeed OID from the
RFC1213-MIB.
See LucentStinger_disc_ports_formula Discovery Formula on page 143 for

more information.
IGS_LucentStingerDSLAMCard Specifies the number of the slot for this DSLAM card. The
Discovery formula uses the slotIfIndex,
IfAdminStatus, and slotIfSlotIndex OIDs from
the RFC1213-MIB and ASCEND-CHASSIS-MIB to obtain the slot
number for the DSLAM card associated with this Stinger Ethernet
Interface DSLAM Card sub-element.
This property is used in sub-element NOC reporting grouping rules.

• DSLAM Grouping Rule on page 48 (Bit Metrics)
• DSLAM Grouping Rule on page 50 (Packet Metrics)
IGS_LucentStingerDSLAMCardPort Specifies the number of the port for this DSLAM card. The
Discovery formula uses the slotIfItemIndex and
IfAdminStatus OIDs from the RFC1213-MIB and
ASCEND-CHASSIS-MIB to obtain the port number for the
DSLAM card associated with this Stinger Ethernet Interface
DSLAM Card sub-element.

See the following section:
• %(Element.NAME) Grouping Rule on page 49 (Bit Metrics)

• %(Element.NAME) Grouping Rule on page 51 (Packet Metrics)
IGS_LucentStingerPortType Specifies the type of port. The Discovery formula uses the string
DSLAM_Port to indicate that the port connects to a DSLAM card.
This property is used in sub-element collection and sub-element


• DSLAM Grouping Rule on page 45 (Stinger Ethernet Interface
DSLAM Card)
• DSLAM Grouping Rule on page 48 (Bit Metrics)
• DSLAM Grouping Rule on page 48 (Packet Metrics)

• LucentStinger Grouping Rule on page 44 (Stinger Ethernet
Interface DSLAM Card)
LinkSpeed The Discovery formula uses %EtherSpeed.

more information.
Stinger Ethernet Interface Uplink Card Sub-Element Properties

formula that defines the characteristics of and discovers information related to Stinger Ethernet Interface Uplink
Card sub-elements. The Stinger Ethernet Interface Uplink Card sub-element maps to the Uplink Ethernet
network interface card associated with a specific Lucent Stinger® DSL Access Concentrator device running in
the network. There is one Stinger Ethernet Interface Uplink Card sub-element for each Uplink Ethernet network
interface card operating in the Lucent Stinger® DSL Access Concentrator environment.
The Lucent Stinger Application Pack uses the LucentStinger_disc_ports_formula Discovery
formula to attach the properties listed in Table 3 to the Stinger Ethernet Interface Uplink Card sub-element. The
LucentStinger_disc_ports_formula Discovery formula makes use of MIB objects defined in the
the following MIBs:

Table 3: Stinger Ethernet Interface Uplink Card Sub-Element Properties

sub-element collection and sub-element NOC reporting grouping
rules.

• IGS Grouping Rule on page 45 (Stinger Ethernet Interface Uplink
Card)
AP_ifSpeed Specifies the speed of the network interface. This value varies,
depending on the network interface. Possible values include
“1000000”.
AP_ifStatus Specifies the desired state of the network interface. Possible values
include: up:up and up:down.
DisplaySpeed Specifies the AP_ifSpeed property value in a readable format.

Possible values include "100 Mbps" and "10 Mbps".
The Discovery formula uses %LinkSpeed Mbps to calculate

the speed of the network interface. See LucentStinger_disc_ports_formula
Discovery Formula on page 143 for more information.
EtherSpeed The Discovery formula uses the ifSpeed OID from the
RFC1213-MIB.

more information.
IGS_LucentStingerPortType Specifies the type of port. The Discovery formula uses the string
UPLink_Port to indicate that the port connects to an Uplink
card.
This property is used in sub-element collection and sub-element


• Uplinks Grouping Rule on page 46 (Stinger Ethernet Interface
Uplink Card)
• UpLinks Grouping Rule on page 48 (Bit Metrics)
• UpLinks Grouping Rule on page 48 (Packet Metrics)
IGS_LucentStingerUpLinkCard Specifies the number of the slot for this Uplink card. The Discovery
formula uses the slotIfIndex, IfAdminStatus, and
slotIfSlotIndex OIDs from the RFC1213-MIB and
ASCEND-CHASSIS-MIB to obtain the slot number for the Uplink
card associated with this Stinger Ethernet Interface Uplink Card sub-
element.

• UpLinks Grouping Rule on page 48 (Bit Metrics)
• Uplinks Grouping Rule on page 50 (Packet Metrics)
IGS_LucentStingerUpLinkCardPort Specifies the number of the port for this Uplink card. The Discovery
formula uses the slotIfItemIndex and
IfAdminStatus OIDs from the RFC1213-MIB and
ASCEND-CHASSIS-MIB to obtain the port number for the Uplink
card associated with this Stinger Ethernet Interface Uplink Card sub-
element.

See the following section:
• %(Element.NAME) Grouping Rule on page 48 (Bit Metrics)

• %(Element.NAME) Grouping Rule on page 50 (Packet Metrics)

• LucentStinger Grouping Rule on page 46 (Stinger Ethernet
Interface Uplink Card)
LinkSpeed The Discovery formula uses %EtherSpeed.

more information.
Chapter 5: Sub-Element Grouping Rules
Topic Page
Sub-Element Collection Grouping Rules 43
Sub-Element NOC Reporting Grouping Rules 46
Overview
Typically, a Netcool/Proviso Application Pack defines sub-element grouping rules. Grouping rules organize and
filter networking data into a structure that makes it easier to collect data on thousands or millions of resources.
Sub-element grouping rules organize data in tree structures. Each folder (branch) in the tree is associated with a
rule or condition. If a sub-element property satisfies the rule or condition associated with a folder in the grouping
tree, the sub-element is placed in the folder. The sub-element is then tested against the rule or condition in the
next folder below. If the sub-element passes that test, it is tested against the rule or condition in the next folder,
and so on.
The Lucent Stinger Application Pack uses some of its Netcool/Proviso properties to define sub-element
grouping rules. Grouping rule names appear in the Name field (Rule Sub-Element view) of the Netcool/Proviso
DataMart Rule Editor. For information on how to use the Netcool/Proviso DataMart Rule Editor, see the
Netcool/Proviso DataMart Configuration Guide.
The Rule Editor contains two grouping rule trees — the NOC reporting tree and the sub-element collect tree.
The following sections describe the filtering rules and conditions in these trees.
Note: The following sections refer to sub-element names and sub-element properties without using the word
Netcool/Proviso. The following sections assume that these are Netcool/Proviso defined property names.
Sub-Element Collection Grouping Rules
Typically, a Netcool/Proviso Application Pack defines sub-element collection grouping rules. Sub-element
collection grouping rules make it possible to organize and filter networking data into a structure that makes it
easier to collect on thousands or millions of resources. The Lucent Stinger Application Pack uses some of its
Netcool/Proviso properties to define sub-element collection grouping rules. The Lucent Stinger Application
Pack defines collection grouping rules for the Netcool/Proviso sub-elements that map to the devices and services
that operate in the Lucent Stinger® DSL Access Concentrator environment.
The collection grouping rule name or names discussed in this chapter display in the Name field (Rule Sub-
Element view) of the Netcool/Proviso DataMart Rule Editor. The collection grouping rule names for the Lucent
Stinger Application Pack reside in this directory: SUB-ELEMENTS->Sub-Element Collect->IGS-
>LucentStinger. For information on how to use the Netcool/Proviso DataMart Rule Editor to define sub-
element collection grouping rules, see the Netcool/Proviso DataMart Configuration Guide.
The Lucent Stinger Application Pack supplies:
• Stinger Ethernet Interface DSLAM Card Sub-Element Collection Grouping Rules
• Stinger Ethernet Interface Uplink Card Sub-Element Collection Grouping Rules
The following sections discuss each of these categories of sub-element collection grouping rules.
Stinger Ethernet Interface DSLAM Card Sub-Element Collection Grouping

Rules
Table 4 lists the Stinger Ethernet Interface DSLAM Card sub-element collection grouping rule names along with
their associated conditions. These grouping rule conditions allow the collection of resources associated with
Stinger Ethernet Interface DSLAM Card sub-elements.
Following the table are sections that provide brief descriptions of each grouping rule.
Table 4: Stinger Ethernet Interface DSLAM CardSub-Element Collection Grouping Rules
Grouping Rule Name Condition
IGS %(AP_EDP) = 'IGS'
LucentStinger %(IGS_VendorName) = 'Lucent_Stinger'
DSLAM %(IGS_LucentStingerPortType) = 'DSLAM_Port'
IGS Grouping Rule
The IGS grouping rule indicates that any sub-element whose AP_EDP property equals IGS passes the condition
test and is placed in the IGS folder. The % (percent) character signifies a wildcard. Otherwise, the sub-element fails
the test and is not included in this grouping rule folder.
The IGS grouping rule has the following effect:
• It captures all sub-elements that the Lucent Stinger Application Pack defines because their associated
Discovery formulas explicitly set their AP_EDP property values to the string IGS.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 for a discussion of the AD_EDP property.
LucentStinger Grouping Rule
The LucentStinger grouping rule indicates that any sub-element whose IGS_VendorName property evaluates
to Lucent_Stinger passes the condition test and is placed in the LucentStinger folder. Otherwise, the sub-
element has already failed one of the previous tests, was never included in a previous result, and never reached this grouping
rule.
The LucentStinger grouping rule has the following effects:
• It captures all Stinger Ethernet Interface DSLAM Card and Stinger Ethernet Interface Uplink Card sub-
elements because their associated Discovery formulas explicitly set their IGS_VendorName property values
to Lucent_Stinger.
• It filters out all other application pack sub-elements because their associated Discovery formulas do not
define an IGS_VendorName property. Therefore, sub-elements generated by other application packs can
never pass this condition test.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 for a discussion of the IGS_VendorName
property.
DSLAM Grouping Rule

The DSLAM grouping rule indicates that any sub-element whose IGS_LucentStingerPortType property
evaluates to the string DSLAM_Port passes the condition test and is placed in the DSLAM folder. Otherwise, the
sub-element fails the test and is not included in this grouping rule folder.
The DSLAM grouping rule has the following effects:
• It captures all Stinger Ethernet Interface DSLAM Card sub-elements because the
LucentStinger_disc_ports_formula Discovery formula explicitly sets the
IGS_LucentStingerPortType property value to DSLAM_Port.
• It filters out Stinger Ethernet Interface Uplink Card sub-elements because the
IGS_LucentStingerPortType property value to DSLAM_Port.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 for a discussion of the
IGS_LucentStingerPortType property.
Stinger Ethernet Interface Uplink Card Sub-Element Collection Grouping Rules

Table 5 lists the Stinger Ethernet Interface Uplink Card sub-element collection grouping rule names along with
their associated conditions. These grouping rule conditions allow the collection of resources associated with
Stinger Ethernet Interface Uplink Card sub-elements.
Table 5: Stinger Ethernet Interface Uplink CardSub-Element Collection Grouping Rules
IGS %(AP_EDP) = 'IGS'
LucentStinger %(IGS_VendorName) = 'Lucent_Stinger'
Uplinks %(IGS_LucentStingerPortType) = 'UPLink_Port'
IGS Grouping Rule
The IGS grouping rule indicates that any sub-element whose AP_EDP property equals IGS passes the condition
test and is placed in the IGS folder. The % (percent) character signifies a wildcard. Otherwise, the sub-element fails
the test and is not included in this grouping rule folder.
The IGS grouping rule has the following effect:
• It captures all sub-elements that the Lucent Stinger Application Pack defines because their associated
Discovery formulas explicitly set their AP_EDP property values to the string IGS.
See Stinger Ethernet Interface Uplink Card Sub-Element Properties on page 39 for a discussion of the AD_EDP property.
LucentStinger Grouping Rule
The LucentStinger grouping rule indicates that any sub-element whose IGS_VendorName property evaluates
to Lucent_Stinger passes the condition test and is placed in the LucentStinger folder. Otherwise, the sub-
element has already failed one of the previous tests, was never included in a previous result, and never reached this grouping
rule.
The LucentStinger grouping rule has the following effects:
elements because their associated Discovery formulas explicitly set their IGS_VendorName property values
to Lucent_Stinger.
• It filters out all other application pack sub-elements because their associated Discovery formulas do not
define an IGS_VendorName property. Therefore, sub-elements generated by other application packs can
never pass this condition test.
See Stinger Ethernet Interface Uplink Card Sub-Element Properties on page 39 for a discussion of the IGS_VendorName
property.
Uplinks Grouping Rule

The Uplinks grouping rule indicates that any sub-element whose IGS_LucentStingerPortType property
evaluates to the string UPLink_Port passes the condition test and is placed in the Uplinks folder. Otherwise, the
sub-element fails the test and is not included in this grouping rule folder.
The Uplinks grouping rule has the following effects:
• It captures all Stinger Ethernet Interface Uplink Card sub-elements because the
IGS_LucentStingerPortType property value to D500SDSL.
• It filters out Stinger Ethernet Interface DSLAM Card sub-elements because the
IGS_LucentStingerPortType property value to UPLink_Port.
See Stinger Ethernet Interface Uplink Card Sub-Element Properties on page 39 for a discussion of the
Sub-Element NOC Reporting Grouping Rules
Typically, a Netcool/Proviso Application Pack defines sub-element NOC reporting grouping rules. Sub-element
NOC reporting grouping rules make it possible to organize and filter networking data into a structure that makes
it easier to report on thousands or millions of resources. The Lucent Stinger Application Pack uses some of its
Netcool/Proviso properties to define sub-element NOC reporting grouping rules. The Lucent Stinger
Application Pack defines NOC reporting grouping rules for the Netcool/Proviso sub-elements that map to the
devices and services that operate in the Lucent Stinger® DSL Access Concentrator environment. The NOC
reporting grouping rule name or names discussed in this chapter display in the Name field (Rule Sub-Element
view) of the Netcool/Proviso DataMart Rule Editor.
The NOC reporting grouping rule names for the Lucent Stinger Application Pack reside in this directory: SUB-
ELEMENTS->NOC Reporting->LucentStinger. For information on how to use the Netcool/Proviso
DataMart Rule Editor to define sub-element NOC reporting grouping rules, see the Netcool/Proviso DataMart
Configuration Guide.
The NOC Reporting Tree provides the framework on which a user navigates to find reports. The current NOC
Reporting tree's root folder is labeled NOC Reporting. Its immediate child folders are the major technologies
supported in Application Packs developed by Micromuse.
Each folder in the tree is associated with a rule that includes a condition test. The test is against a sub-element.
If the sub-element passes the condition test, then it gets placed in the folder. For a path of folders, for example,
Root~Folder1~Folder2~Folder3, the sub-element must pass the condition tests at each level to be in Folder3.
The Lucent Stinger Application Pack defines sub-element NOC reporting grouping rules according to the
following views:
• Bit Metrics
• Packet Metrics
The following sections discuss the sub-element NOC reporting grouping rules for each of these views.
Bit Metrics
Table 6 lists the Bit Metrics grouping rule names and their associated conditions. These grouping rule conditions
allow the collection of resources associated with Stinger Ethernet Interface DSLAM Card and Stinger Ethernet
Interface Uplink Card sub-elements. Following the table are sections that provide brief descriptions of each
grouping rule.
Table 6: Bit Metrics View NOC Reporting Sub-Element Grouping Rules
Lucent Stinger %(AP_EDP) = 'IGS' AND %(IGS_VendorName) = 'Lucent_Stinger'
Bit Metrics No explicit condition
UpLinks %(IGS_LucentStingerPortType) = 'UPLink_Port'
%(Element.NAME) %(IGS_LucentStingerUplinkCard)
%(Element.NAME) %(IGS_LucentStingerDSLAMCard)
Lucent Stinger Grouping Rule
The Lucent Stinger grouping rule indicates that any sub-element whose AP_EDP and IGS_VendorName
properties evaluate to IGS and Lucent_Stinger passes the condition test and is placed in the Lucent Stinger
folder. Otherwise, the sub-element has already failed one of the previous tests, was never included in a previous result, and
never reached this grouping rule.
The Lucent Stinger grouping rule has the following effects:
elements because their associated Discovery formula explicitly sets their AP_EDP and IGS_VendorName
property values to IGS and Lucent_Stinger.
• It filters out all other application pack sub-elements because their associated Discovery formulas most likely
do not define AP_EDP and IGS_VendorName properties. If these other application packs define these
properties they would most likely assign them different values. Therefore, sub-elements generated by other
application packs would most likely never pass this condition test.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 and Stinger Ethernet Interface Uplink Card Sub-
Element Properties on page 39 for discussions of the AP_EDP and IGS_VendorName properties.
Bit Metrics Grouping Rule

The Bit Metrics grouping rule has no explicit condition. Thus, any sub-element that passes the Lucent Stinger
grouping rule is placed in the Bit Metrics folder. Otherwise, the sub-element has already failed one of the previous
tests, was never included in a previous result, and never reached this grouping rule.
UpLinks Grouping Rule
The UpLinks grouping rule indicates that any sub-element whose IGS_LucentStingerPortType property
equals UPLink_Port passes the condition test and is placed in the UpLinks folder. The % (percent) character
signifies a wildcard. Otherwise, the sub-element has already failed one of the previous tests, was never included
in a previous result, and never reached this grouping rule.
The UpLinks grouping rule has the following effects:
LucentStinger_disc_ports_formula Discovery formula sets their
IGS_LucentStingerPortType properties to UPLink_Port.
• It filters out all of the Stinger Ethernet Interface DSLAM Card sub-elements because their
IGS_LucentStingerPortType properties do not equal UPLink_Port. Therefore, the Stinger Ethernet
Interface DSLAM Card sub-elements can never pass this condition test.
%(Element.NAME) Grouping Rule
The %(Element.NAME) grouping rule substitutes Element.NAME with the value of

%(IGS_LucentStingerUplinkCard). The %(IGS_LucentStingerUplinkCard) condition evaluates to an IP address.
Thus, for each Stinger Ethernet Interface Uplink Card operating in the Lucent Stinger® DSL Access
Concentrator environment there is a corresponding IP address folder.
DSLAM Grouping Rule
equals DSLAM_Port passes the condition test and is placed in the DSLAM folder. The % (percent) character
IGS_LucentStingerPortType properties to DSLAM_Port.
• It filters out all of the Stinger Ethernet Interface Uplink Card sub-elements because their
IGS_LucentStingerPortType properties do not equal DSLAM_Port. Therefore, the Stinger Ethernet
Interface Uplink Card sub-elements can never pass this condition test.

%(IGS_LucentStingerDSLAMCard). The %(IGS_LucentStingerDSLAMCard) condition evaluates to an IP
address. Thus, for each Stinger Ethernet Interface DSLAM Card operating in the Lucent Stinger® DSL Access
Packet Metrics
Table 7 lists the Packets Metrics view NOC reporting sub-element grouping rule names along with their
associated conditions. These grouping rule conditions allow the collection of resources associated with Stinger
Ethernet Interface DSLAM Card and Stinger Ethernet Interface Uplink Card sub-elements.
Table 7: Packet Metrics View NOC Reporting Sub-Element Grouping Rules
Lucent Stinger %(AP_EDP) = 'IGS' AND %(IGS_VendorName) = 'Lucent_Stinger'
Packet Metrics No explicit condition
UpLinks %(IGS_LucentStingerPortType) = 'UPLink_Port'
%(Element.NAME) %(IGS_LucentStingerUplinkCard)
%(Element.NAME) %(IGS_LucentStingerDSLAMCard)
Lucent Stinger Grouping Rule
The Lucent Stinger grouping rule indicates that any sub-element whose AP_EDP and IGS_VendorName
properties evaluate to IGS and Lucent_Stinger passes the condition test and is placed in the Lucent Stinger
folder. Otherwise, the sub-element has already failed one of the previous tests, was never included in a previous result, and
never reached this grouping rule.
The Lucent Stinger grouping rule has the following effects:
elements because their associated Discovery formula explicitly sets their AP_EDP and IGS_VendorName
property values to IGS and Lucent_Stinger.
• It filters out all other application pack sub-elements because their associated Discovery formulas most likely
do not define AP_EDP and IGS_VendorName properties. If these other application packs define these
properties they would most likely assign them different values. Therefore, sub-elements generated by other
application packs would most likely never pass this condition test.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 and Stinger Ethernet Interface Uplink Card Sub-
Element Properties on page 39 for discussions of the AP_EDP and IGS_VendorName properties.
Packet Metrics Grouping Rule

The Packet Metrics grouping rule has no explicit condition. Thus, any sub-element that passes the Lucent Stinger
grouping rule is placed in the Packet Metrics folder. Otherwise, the sub-element has already failed one of the
previous tests, was never included in a previous result, and never reached this grouping rule.
Uplinks Grouping Rule
The UpLinks grouping rule indicates that any sub-element whose IGS_LucentStingerPortType property
equals UPLink_Port passes the condition test and is placed in the UpLinks folder. The % (percent) character
The UpLinks grouping rule has the following effects:
IGS_LucentStingerPortType properties to UPLink_Port.
• It filters out all of the Stinger Ethernet Interface DSLAM Card sub-elements because their
IGS_LucentStingerPortType properties do not equal UPLink_Port. Therefore, the Stinger Ethernet
Interface DSLAM Card sub-elements can never pass this condition test.

%(IGS_LucentStingerUplinkCard). The %(IGS_LucentStingerUplinkCard) condition evaluates to an IP address.
Thus, for each Stinger Ethernet Interface Uplink Card operating in the Lucent Stinger® DSL Access
DSLAM Grouping Rule
equals DSLAM_Port passes the condition test and is placed in the DSLAM folder. The % (percent) character
IGS_LucentStingerPortType properties to DSLAM_Port.
• It filters out all of the Stinger Ethernet Interface Uplink Card sub-elements because their
IGS_LucentStingerPortType properties do not equal DSLAM_Port. Therefore, the Stinger Ethernet
Interface Uplink Card sub-elements can never pass this condition test.

%(IGS_LucentStingerDSLAMCard). The %(IGS_LucentStingerDSLAMCard) condition evaluates to an IP
address. Thus, for each Stinger Ethernet Interface DSLAM Card operating in the Lucent Stinger® DSL Access
NOTES
Chapter 6: Defined Resources
Topic Page
Element Names 53
Sub-Element Names 54
Sub-Element Labels 56
Sub-Element Family Names 58
Overview
A Netcool/Proviso resource is a network element or sub-element, such as a router or a hub. Typically, a

Micromuse Application 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 Micromuse support engineers to:
• Configure (using the Netcool/Proviso DataMart Request Editor) data collection requests for the sub-
elements associated with each Application Pack
• View (using the Netcool/Proviso DataMart Resource Editor) sub-elements and sub-element groups
associated with each Application 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
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
Lucent Stinger Application Pack defines a group of Netcool/Proviso elements, sub-elements, and properties that
map to the devices and services that operate in the Lucent Stinger® DSL Access Concentrator 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 Lucent Stinger Application Pack defines an element name for each Stinger DSL Device device operating in
the network. The Lucent Stinger Application Pack defines the element name for a Stinger DSL Device device by
using the following syntax:
ipaddress
where:
• ipaddress — Specifies the IP address of the Stinger DSL Device device. An SNMP Agent runs on each Stinger
DSL Device device.
The following examples use the ipaddress to define the element names for two Stinger DSL Device devices running
in a network:
192.168.200.51
192.168.200.56
Sub-Element Names
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 Lucent Stinger Application 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 Lucent Stinger Application Pack defines sub-element names for the devices and components associated with
the Lucent Stinger® DSL Access Concentrator environment. Specifically, the Lucent Stinger Application Pack
defines:
• Stinger DSL Device Sub-Element Name
• Stinger Ethernet Interface DSLAM Card Sub-Element Name
• Stinger Ethernet Interface Uplink Card Sub-Element Name
Stinger DSL Device Sub-Element Name

The Lucent Stinger Application Pack defines sub-element names for each Stinger DSL device running in the
network. The Lucent Stinger Application Pack uses the syntax from the first field of the
LucentStinger_disc_device_formula Discovery formula’s Sub-Elements Results Line section to
define Stinger DSL Device sub-element names:
elementname_<NULL>
where:
• elementname — Specifies the element name for the Stinger DSL Device. Typically, the element name is some
IP address (for example, 192.168.200.51). The element name is followed by an underscore character
(_).
• NULL — Specifies that the LucentStinger_disc_device_formula Discovery formula sets the
sub-element instance string to the value NULL in the first field of its Sub-Elements Results Line section. The
LucentStinger_disc_device_formula Discovery formula encloses the value NULL within angle
brackets (<>).
The following examples use the previously described syntax to define Stinger DSL Device sub-element names:
192.168.200.71 <NULL>
192.168.200.72 <NULL>
See LucentStinger_disc_device_formula Discovery Formula on page 142 for more information on the
LucentStinger_disc_device_formula Discovery formula.
Stinger Ethernet Interface DSLAM Card Sub-Element Name

The Lucent Stinger Application Pack defines sub-element names for the DSLAM Card Ethernet interface
component associated with each Stinger DSL Device device running in the network. The Lucent Stinger
Application Pack uses the syntax from the first field of the LucentStinger_disc_ports_formula
Discovery formula’s Sub-Elements Results Line section to define Stinger Ethernet Interface DSLAM Card sub-
element names:
If<PortNum>
where:
• If — Specifies a string that indicates this sub-element is some Ethernet network interface.
• PortNum — Specifies an instance of an Ethernet network interface that uses a Digital Subscriber Line Access
Multiplexer (DSLAM) card. The PortNum value is the result of an expression stored in a temporary variable
in the OID Gathering section of the LucentStinger_disc_ports_formula Discovery formula.
The following examples use the previously described syntax to define Stinger Ethernet Interface DSLAM Card
sub-element names:
If<71>
If<72>
See LucentStinger_disc_ports_formula Discovery Formula on page 143 for more information on the
Stinger Ethernet Interface Uplink Card Sub-Element Name

The Lucent Stinger Application Pack defines sub-element names for the Uplink Card Ethernet interface
component associated with each Stinger DSL Device device running in the network. The Lucent Stinger
Application Pack uses the syntax from the first field of the LucentStinger_disc_ports_formula
Discovery formula’s Sub-Elements Results Line section to define Stinger Ethernet Interface Uplink Card sub-
element names:
If<PortNum>
where:
• If — Specifies a string that indicates this sub-element is some Ethernet network interface.
• PortNum — Specifies an instance of an Ethernet network interface that uses an Uplink card. The PortNum value
is the result of an expression stored in a temporary variable in the OID Gathering section of the
The following examples use the previously described syntax to define Stinger Ethernet Interface Uplink Card
sub-element names:
If<80>
If<81>
See LucentStinger_disc_ports_formula Discovery Formula on page 143 for more information on the
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 Lucent Stinger Application 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 Lucent Stinger Application Pack defines:

• Stinger DSL Device Sub-Element Label
• Stinger Ethernet Interface DSLAM Card Sub-Element Label
• Stinger Ethernet Interface Uplink Card Sub-Element Label
Stinger DSL Device Sub-Element Label

The Lucent Stinger Application Pack defines sub-element labels for each Stinger DSL device running in the
network. The Lucent Stinger Application Pack uses the syntax from the second field of the
define Stinger DSL Device sub-element labels. In this case, the
LucentStinger_disc_device_formula Discovery formula uses a hardcoded string to define a
Stinger DSL Device sub-element label:
Lucent_Stinger
See Stinger DSL Device Sub-Element Properties on page 36 for more information on the properties defined for Stinger
DSL Device sub-elements. See LucentStinger_disc_device_formula Discovery Formula on page 142 for more information on
the LucentStinger_disc_device_formula Discovery formula.
Stinger Ethernet Interface DSLAM Card Sub-Element Label

The Lucent Stinger Application Pack uses the syntax from the second field of the
define Stinger Ethernet Interface DSLAM Card sub-element labels:
elementname_IF: SlotNum:PortNum(LinkSpeed Mbps)
where:
• elementname — Specifies the element name for the Lucent Stinger DSL device. Typically, the element name is
some IP address (for example, 192.168.200.71). The element name is followed by an underscore character
(_).
• IF: — Specifies a string that the LucentStinger_disc_device_formula Discovery formula
creates in the second field of its Sub-Elements Results Line section. The string is followed by a colon (:).
• SlotNum: — Specifies the index number of the slot on which the Ethernet network interface resides. This
number is unique and represents an instance of a DSLAM Ethernet network interface card associated with
this Stinger Ethernet Interface DSLAM Card sub-element. The string is followed by a colon (:).
• PortNum — Specifies the index number of the port on which the Ethernet network interface resides. This
this Stinger Ethernet Interface DSLAM Card sub-element.
• LinkSpeed — Specifies an estimate of the Ethernet network interface’s current bandwidth. The
LucentStinger_disc_device_formula Discovery formula performs an appropriate conversion so
that the speed is expressed in megabits per second (Mbps). The LinkSpeed is followed by the string Mbps.
sub-element labels:
192.168.200.71_IF:8:1101 (1000 Mbps)
192.168.200.72_IF:9:1101 (1000 Mbps)
Typically, the Lucent Stinger Application Pack uses the Stinger Ethernet Interface DSLAM Card sub-element
label in reports.
See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 for more information on the properties
defined for Stinger Ethernet Interface DSLAM Card sub-elements. See LucentStinger_disc_ports_formula Discovery
Formula on page 143 for more information on the LucentStinger_disc_ports_formula Discovery
formula.
Stinger Ethernet Interface Uplink Card Sub-Element Label

The Lucent Stinger Application Pack uses the syntax from the second field of the
define Stinger Ethernet Interface Uplink Card sub-element labels:
elementname_IF: SlotNum:PortNum(LinkSpeed Mbps)
where:
• elementname — Specifies the element name for the Lucent Stinger DSL device. Typically, the element name is
some IP address (for example, 192.168.200.71). The element name is followed by an underscore character
(_).
• IF: — Specifies a string that the LucentStinger_disc_device_formula Discovery formula
creates in the second field of its Sub-Elements Results Line section. The string is followed by a colon (:).
• SlotNum: — Specifies the index number of the slot on which the Ethernet network interface resides. This
this Stinger Ethernet Interface DSLAM Card sub-element. The string is followed by a colon (:).
• PortNum — Specifies the index number of the port on which the Ethernet network interface resides. This
this Stinger Ethernet Interface DSLAM Card sub-element.
• LinkSpeed — Specifies an estimate of the Ethernet network interface’s current bandwidth. The
LucentStinger_disc_device_formula Discovery formula performs an appropriate conversion so
that the speed is expressed in megabits per second (Mbps). The LinkSpeed is followed by the string Mbps.
sub-element labels:
192.168.200.71_IF:8:1101 (1000 Mbps)
192.168.200.72_IF:9:1101 (1000 Mbps)
Typically, the Lucent Stinger Application Pack uses the Stinger Ethernet Interface DSLAM Card sub-element
label in reports.
See Stinger Ethernet Interface Uplink Card Sub-Element Properties on page 39 for more information on the properties defined
for Stinger Ethernet Interface Uplink Card sub-elements. See LucentStinger_disc_ports_formula Discovery Formula on
page 143 for more information on the LucentStinger_disc_ports_formula Discovery formula.
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 8 defines the family names for each sub-element that the Lucent Stinger Application Pack defines.
Table 8: Sub-Element Family Names
Sub-Element Family Name
Stinger DSL Device Lucent_Stinger
Stinger Ethernet Interface DSLAM Card Lucent_Stinger
Stinger Ethernet Interface Uplink Card Lucent_Stinger
Chapter 7: SNMP Collection Formulas
Topic Page
Netcool/Proviso Formula Tree for the Lucent Stinger Application Pack 59
Generic Formulas and Specific Formulas 59
Formula Reference 60
Overview
The Lucent Stinger Application Pack provides SNMP collection formulas specific to the associated network
devices and technologies on which it operates. These SNMP collection formulas are installed with the Lucent
Stinger Application Pack.
Netcool/Proviso Formula Tree for the Lucent Stinger Application

Pack
The Lucent Stinger Application Pack provides a formula tree where the SNMP 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.
Generic Formulas and Specific Formulas
The Lucent Stinger Application Pack makes use of Generic and Specific formulas. A Generic formula has a
formula ID, but no formula instructions. Thus, the Generic formula does not report any results. This feature
allows application packs to create specific SNMP collection formulas that have formula instructions that report
results using the formula IDs associated with specific Generic formulas. For example, an SNMP collection
formula called Outbound Multicast HC with a formula ID of 10237 might report its results using the
Outbound Multicast (pps) generic formula ID of 10090.
SNMP collection formulas that use Generic formula IDs to report their results use the DEF SaveAlias
statement. This statement takes a Generic formula ID. The following example shows how the DEF SaveAlias
statement maps the formula ID of the Outbound Multicast HC SNMP collection formula to the formula
ID of the Outbound Multicast (pps) generic formula ID:
DEF SaveAlias 10090
Formula Reference
The sections that follow provide reference information about the Generic formulas and Specific SNMP
collection formulas that the Lucent Stinger Application Pack provides.
The following list identifies the information provided for the Generic formulas:
• Formula Name — Specifies the Generic formula name along with its associated formula ID.
• Type — Specifies Generic for a Generic formula.
• Location in the Formula Tree — Specifies where the Generic formula is located in the Formula tree.
• Formula Description — Provides a brief description of the Generic formula.
• Metrics Appear in These Reports — Identifies the report or reports in which the metric associated with this
Generic formula display.
• Aliased SNMP Formulas — Identifies the SNMP collection formulas that alias (map back to) this Generic
formula.
The following list identifies the information provided for the SNMP (Specific) collection formulas:
• Formula Name — Specifies the SNMP collection formula name along with its associated formula ID.
• Type — Specifies SNMP (collect) for an SNMP collection formula.
• Location in the Formula Tree — Specifies where the Generic formula is located in the Formula tree.
• Mibs — Specifies the Management Information Bases (MIBs) in which the OIDs used in the SNMP
collection formula reside.
• Generic Formula — Specifies the name (and path) of the Generic formula to which this SNMP collection
formula is aliased.
• Formula Description — Provides a brief description of the SNMP collection formula.
• Formula Syntax — Provides the syntax for the SNMP collection formula.
• Metrics Appear in These Reports — Identifies the report or reports in which the metric or metrics associated
with this SNMP collection formula display.
The Generic formula and Specific formula IDs display in the ID and Generic fields of the Netcool/Proviso
DataMart Request Editor. See the Netcool/Proviso DataMart Configuration Guide for more information on the Request
Editor. See the Netcool/Proviso Application Pack Starter Kit User’s Guide for more information about Generic and Specific
formulas.
Delivered Packets
Type
Generic
Location in the Formula Tree

FORMULAS->AP->Generic->Interface
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the total number of packets
delivered to a higher layer, during the last polling period. This metric excludes any packets that were received by
an interface, but were not passed on.
Metrics Appear in These Reports

The metrics that this Generic formula’s associated SNMP collection formulas calculate display in the following
reports:
• Health Summary Group (Packet) (See Health Summary Group (Packet) on page 15.)
• Health Summary Resource (Packet) (See Health Summary Resource (Packet) on page 17.)
• Health (Packet) Details (See Health (Packet) Details on page 9.)
Aliased SNMP Formulas

The following SNMP collection formulas are aliased to the Delivered Packets Generic formula:
• Delivered U/M/B HC
• Delivered U/NU
• Delivered U/M/B LC
Delivered U/M/B HC
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Inbound->Packets
Mibs
The Delivered U/M/B HC formula makes use of the following Management Information Bases (MIBs):
• IF-MIB (located in the file named rfc2233-IF-MIB)
Generic Formula
The Delivered U/M/B HC formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Delivered Packets
Formula Description
The Delivered U/M/B HC formula calculates the total number of packets delivered to a higher layer, during
the last polling period. This metric excludes any packets that were received by an interface, but were not passed on.
Formula Syntax
The Delivered U/M/B HC formula is defined as follows. See the listed MIB or MIBs for more information
on the OIDs that the formula uses.
DEF SaveAlias 10093;
Dim I1 AS Integer Default *;
distrib(delta(sysUpTime.0), "default:1") * (delta(ifHCInUcastPkts.%I1) +
delta(ifHCInMulticastPkts.%I1) + delta(ifHCInBroadcastPkts.%I1))

The metrics that the Delivered U/M/B HC formula calculates display in the following reports:
Delivered U/M/B LC
Type
SNMP (collect)

Mibs
The Delivered U/M/B LC formula makes use of the following Management Information Bases (MIBs):
Generic Formula
The Delivered U/M/B LC formula is aliased to the following Generic formula:
Formula Description
The Delivered U/M/B LC formula calculates the total number of packets delivered to a higher layer, during
the last polling period. This metric excludes any packets that were received by an interface, but were not passed on.
Formula Syntax
The Delivered U/M/B LC formula is defined as follows. See the listed MIB or MIBs for more information
distrib(delta(sysUpTime.0), "default:1") * (delta(ifInUcastPkts.%I1) +
delta(ifInMulticastPkts.%I1) + delta(ifInBroadcastPkts.%I1))

The metrics that the Delivered U/M/B LC formula calculates display in the following reports:
Delivered U/NU
Type
SNMP (collect)

Mibs
The Delivered U/NU formula makes use of the following Management Information Base (MIB):
Generic Formula
The Delivered U/NU formula is aliased to the following Generic formula:
Formula Description
The Delivered U/NU formula calculates the total number of packets delivered to a higher layer, during the
last polling period. This metric excludes any packets that were received by an interface, but were not passed on.
Formula Syntax
The Delivered U/NU formula is defined as follows. See the listed MIB or MIBs for more information on
the OIDs that the formula uses.
distrib(delta(sysUpTime.0), "default:1") * (delta(ifInUcastPkts.%I1) +
delta(ifInNUcastPkts.%I1))

The metrics that the Delivered U/M/B LC formula calculates display in the following reports:
Inbound Broadcast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of packets received
on a network interface and delivered to a higher layer. These packets were addressed to a broadcast address at this
layer.

reports:
• Throughput Summary Group (Packet) (See Throughput Summary Group (Packet) on page 27.)
• Throughput Summary Resource (Packet) (See Throughput Summary Resource (Packet) on page 29.)
• Throughput (Packet) Details (See Throughput (Packet) Details on page 23.)

The following SNMP collection formulas are aliased to the Inbound Broadcast (pps) Generic formula:
• Inbound Broadcast HC (pps)
• Inbound Broadcast LC (pps)
Inbound Broadcast HC (pps)
Type
SNMP (collect)

Mibs
The Inbound Broadcast HC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Broadcast HC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Inbound Broadcast (pps)
Formula Description
The Inbound Broadcast HC (pps) formula calculates the rate, per second, at which the inbound
broadcast packets at this layer were delivered to a higher layer, during the last polling period.
Formula Syntax
The Inbound Broadcast HC (pps) formula is defined as follows. See the listed MIB or MIBs for more
information on the OIDs that the formula uses.
# Factor of 100 to convert pkts per decisecond to pkts per second;
delta(ifHCInBroadcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Inbound Broadcast HC (pps) formula calculates display in the following reports:
Inbound Broadcast LC (pps)
Type
SNMP (collect)

Mibs
The Inbound Broadcast LC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Broadcast LC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Inbound Broadcast (pps)
Formula Description
The Inbound Broadcast LC (pps) formula calculates the rate, per second, at which the inbound
broadcast packets at this layer were delivered to a higher layer, during the last polling period.
Formula Syntax
The Inbound Broadcast LC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifInBroadcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Inbound Broadcast LC (pps) formula calculates display in the following reports:
Inbound Discarded (PDUs)
Type
Generic

FORMULAS->AP->Generic->Universal->Congestion Discards
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of incoming
Protocol Data Units (PDUs) dropped due to congestion or resource limitations.

reports:

The following SNMP collection formula is aliased to the Inbound Discarded (PDUs) Generic formula:
• Inbound Discards
Inbound Discards
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Inbound->Errors
Mibs
The Inbound Discards formula makes use of the following Management Information Base (MIB):
Generic Formula
The Inbound Discards formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Congestion Discards->Inbound
Discarded (PDUs)
Formula Description
The Inbound Discards formula calculates the number of error-free packets dropped during the last polling
period. Packets may be dropped for capacity reasons (for example, no buffer space) or for traffic-shaping reasons.
Formula Syntax
The Inbound Discards formula is defined as follows. See the listed MIB or MIBs for more information on
DEF SaveAlias 2218;
Dim I1 AS Integer Default * NAME Interface;
distrib(delta(sysUpTime.0), "default:1") * delta(ifInDiscards.%I1)

The metrics that the Inbound Discards formula calculates display in the following reports:
Inbound Errors
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Inbound->Errors
Mibs
The Inbound Errors formula makes use of the following Management Information Base (MIB):
Generic Formula
The Inbound Errors formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Errors->Inbound Errors (PDUs)
Formula Description
The Inbound Errors formula calculates the number of errors that occurred on the inbound interface. For
packet-oriented interfaces, errors are counted in packets. For character-oriented interfaces, errors are counted in
octets. For fixed-length interfaces, errors are counted in transmission units (where the transmission unit is the size
of the fixed-length transmission).
Formula Syntax
The Inbound Errors formula is defined as follows. See the listed MIB or MIBs for more information on
DEF SaveAlias 2214;
distrib(delta(sysUpTime.0), "default:1") * delta(ifInErrors.%I1)

The metrics that the Inbound Discards formula calculates display in the following reports:
• Health (Octets) Details (See Health (Octets) Details on page 8.)

• Health Summary Group (Bit) (See Health Summary Group (Bit) on page 14.)
• Health Summary Resource (Bit) (See Health Summary Resource (Bit) on page 16.)
• Threshold Violation - Inbound Errors (Bit) (See Threshold Violation - Inbound Errors (Bit) on page 18.)
• Health Distribution Range - Inbound Errors (Bit) (See Health Distribution Range - Inbound Errors (Bit) on page 10.)
• Threshold Violation - Inbound Errors (Packet) (See Threshold Violation - Inbound Errors (Packet) on page 19.)
Inbound Errors (PDUs)
Type
Generic

FORMULAS->AP->Generic->Universal->Errors
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of incoming
Protocol Data Units (PDUs) that were discarded due to errors.

reports:

• Threshold Violation - Inbound Errors (Bit) (See Threshold Violation - Inbound Errors (Bit) on page 18.)
• Threshold Violation - Inbound Errors (Packet) (See Threshold Violation - Inbound Errors (Packet) on page 19.)

The following SNMP collection formula is aliased to the Inbound Errors (PDUs) Generic formula:
• Inbound Errors
Inbound Multicast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of packets received
on an interface and delivered to a higher layer. These received packets were addressed to a multicast address at
this layer.

reports:

The following SNMP collection formulas are aliased to the Inbound Multicast (pps) Generic formula:
• Inbound Non-Unicast (pps)
• Inbound Multicast HC (pps)
• Inbound Multicast LC (pps)
Inbound Multicast HC (pps)
Type
SNMP (collect)

Mibs
The Inbound Multicast HC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Multicast HC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Inbound Multicast (pps)
Formula Description
The Inbound Broadcast HC (pps) formula calculates the rate, per second, at which the inbound
multicast packets at this layer were delivered to a higher layer, during the last polling period.
Formula Syntax
The Inbound Multicast HC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifHCInMulticastPkts.%I1) / delta(sysUpTime.0) * 100
Inbound Multicast LC (pps)
Type
SNMP (collect)

Mibs
The Inbound Multicast LC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Multicast LC (pps) formula is aliased to the following Generic formula:
Formula Description
The Inbound Broadcast LC (pps) formula calculates the rate, per second, at which the inbound
multicast packets at this layer were delivered to a higher layer, during the last polling period.
Formula Syntax
The Inbound Multicast LC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifInMulticastPkts.%I1) / delta(sysUpTime.0) * 100
Inbound Non-Unicast (pps)
Type
SNMP (collect)

Mibs
The Inbound Non-Unicast (pps)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Inbound Non-Unicast (pps) formula is aliased to the following Generic formula:
Formula Description
The Inbound Non-Unicast (pps) formula calculates the rate, per second, at which non-unicast packets
at this layer were delivered to a higher layer during the last polling period.
This formula uses ifInNUcastPkts, which has no HC equivalent so there are no LC/HC variants of the
formula. Note that the Inbound Non-Unicast (pps) formula maps to the same Generic formula as the
SNMP Multicast collection formulas.
Formula Syntax
The Inbound Non-Unicast (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifInNUcastPkts.%I1) / delta(sysUpTime.0) * 100
Inbound Throughput (bps)
Type
Generic

FORMULAS->AP->Generic->Universal->Throughput
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the average rate, in bits-per-
second, of inbound traffic on this resource during the last polling period.

reports:
• Throughput Summary Group (Bit) (See Throughput Summary Group (Bit) on page 26.)
• Throughput Summary Resource (Bit) (See Health Summary Resource (Bit) on page 16.)
• Throughput (Octets) Details (See Throughput (Octets) Details on page 22.)

The following SNMP collection formulas are aliased to the Inbound Throughput (bps) Generic
formula:
• Inbound Throughput HC (bps)
• Inbound Throughput LC (bps)
Inbound Throughput HC (bps)
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Inbound->Octets
Mibs
The Inbound Throughput HC (bps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Inbound Throughput HC (bps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Inbound Throughput
(bps)
Formula Description
The Inbound Throughput HC (bps) formula calculates the average rate, in bits-per-second, of inbound
traffic on this resource during the last polling period.
Formula Syntax
The Inbound Throughput HC (bps) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2208;
# 800 is 8 for octets to bits times 100 for division by seconds instead of
deciseconds;
800 * delta(ifHCInOctets.%I1) / delta(sysUpTime.0)

The metrics that the Inbound Throughput HC (bps) formula calculates display in the following reports:
Inbound Throughput LC (bps)
Type
SNMP (collect)

Mibs
The Inbound Throughput HC (bps)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Inbound Throughput LC (bps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Inbound Throughput
(bps)
Formula Description
The Inbound Throughput LC (bps) formula calculates the average rate, in bits-per-second, of inbound
traffic on this resource during the last polling period.
Formula Syntax
The Inbound Throughput LC (bps) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2208;
deciseconds;
800 * delta(ifInOctets.%I1) / delta(sysUpTime.0)

The metrics that the Inbound Throughput LC (bps) formula calculates display in the following reports:
Inbound Unicast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the rate, per second, at which
inbound packets were received and delivered to a higher layer during the last polling period. The calculation does
not include packets addressed to a multicast or broadcast address at this layer.

reports:

The following SNMP collection formulas are aliased to the Inbound Unicast (pps) Generic formula:
• Inbound Unicast HC (pps)
• Inbound Unicast LC (pps)
Inbound Unicast HC (pps)
Type
SNMP (collect)

Mibs
The Inbound Unicast HC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Unicast HC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Inbound Unicast (pps)
Formula Description
The Inbound Unicast HC (pps)formula calculates the rate, per second, at which inbound packets were
received and delivered to a higher layer during the last polling period. The calculation does not include packets
addressed to a multicast or broadcast address at this layer.
Formula Syntax
The Inbound Unicast HC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifHCInUcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Inbound Unicast HC (pps) formula calculates display in the following reports:
Inbound Unicast LC (pps)
Type
SNMP (collect)

Mibs
The Inbound Unicast LC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Inbound Unicast LC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Inbound Unicast (pps)
Formula Description
The Inbound Unicast LC (pps)formula calculates the rate, per second, at which inbound packets were
received and delivered to a higher layer during the last polling period. The calculation does not include packets
addressed to a multicast or broadcast address at this layer.
Formula Syntax
The Inbound Unicast LC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifInUcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Inbound Unicast LC (pps) formula calculates display in the following reports:
Inbound Utilization (percent)
Type
Generic

FORMULAS->AP->Generic->Universal->Utilization
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the average percentage of the
inbound bandwidth (capacity) used on this interface during the last polling period. The percentage is valid only if
the interface has a defined bandwidth (that is, ifSpeed is non-zero).
Half-Duplex Note: For full-duplex network interfaces such as Ethernet, this formula only reports the
percentage of the interface’s total capacity used by incoming traffic. This percentage needs to be added to the
outbound utilization percentage to determine the total utilization on a full-duplex interface.

reports:
• Throughput Summary Resource (Bit) (See Throughput Summary Resource (Bit) on page 28.)
• Throughput Distribution Range - Inbound Utilization (Bit) (See Throughput Distribution Range - Inbound Utilization
(Bit) on page 24.)

The following SNMP collection formulas are aliased to the Inbound Utilization (percent) Generic
formula:
• Inbound Utilization HC (percent)
• Inbound Utilization HC/HS (percent)
• Inbound Utilization LC (percent)
Inbound Utilization HC (percent)
Type
SNMP (collect)

Mibs
The Inbound Utilization HC (percent)formula makes use of the following Management
Information Bases (MIBs):
Generic Formula
The Inbound Utilization HC (percent) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Utilization->Inbound Utilization
(percent)
Formula Description
The Inbound Utilization HC (percent) formula calculates the average percentage of the inbound
bandwidth (capacity) used on this interface during the last polling period. The percentage is valid only if the
interface has a defined bandwidth (that is, ifSpeed is non-zero).
Formula Syntax
The Inbound Utilization HC (percent) formula is defined as follows. See the listed MIB or MIBs
for more information on the OIDs that the formula uses.
DEF SaveAlias 2206;
800 * delta(ifHCInOctets.%I1) / delta(sysUpTime.0) / distrib(ifSpeed.%I1,
">0:*") * 100

The metrics that the Inbound Utilization HC (percent) formula calculates display in the following
reports:
(Bit) on page 24.)
Inbound Utilization HC/HS (percent)
Type
SNMP (collect)

Mibs
The Inbound Utilization HC/HS (percent)formula makes use of the following Management
Generic Formula
The Inbound Utilization HC/HS (percent) formula is aliased to the following Generic formula:
(percent)
Formula Description
The Inbound Utilization HC/HS (percent) formula calculates the average percentage of the
inbound bandwidth (capacity) used on this interface during the last polling period. The percentage is valid only if
the interface has a defined bandwidth (that is, ifSpeed is non-zero).
Formula Syntax
The Inbound Utilization HC/HS (percent) formula is defined as follows. See the listed MIB or
MIBs for more information on the OIDs that the formula uses.
DEF SaveAlias 2206;
# Times 800 to get from octets to bits and deciseconds to seconds;
# Divide 10000 to get bits per sec from megabits per sec and do percentage;
800 * delta(ifHCInOctets.%I1) / delta(sysUpTime.0) / distrib(ifHighSpeed.%I1,
">0:*") / 10000

The metrics that the Inbound Utilization HC/HS (percent) formula calculates display in the
following reports:
(Bit) on page 24.)
Inbound Utilization LC (percent)
Type
SNMP (collect)

Mibs
The Inbound Utilization LC (percent)formula makes use of the following Management
Information Base (MIB):
Generic Formula
The Inbound Utilization LC (percent) formula is aliased to the following Generic formula:
(percent)
Formula Description
The Inbound Utilization LC (percent) formula calculates the average percentage of the inbound
bandwidth (capacity) used on this interface during the last polling period. The percentage is valid only if the
interface has a defined bandwidth (that is, ifSpeed is non-zero).
Formula Syntax
The Inbound Utilization LC (percent) formula is defined as follows. See the listed MIB or MIBs
DEF SaveAlias 2206;
(800 * delta(ifInOctets.%I1) / delta(sysUpTime.0)) / distrib(ifSpeed.%I1,
">0:*") * 100

The metrics that the Inbound Utilization HC/HS (percent) formula calculates display in the
following reports:

(Bit) on page 24.)
Inbound Volume (octets)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the volume of traffic, in octets,
in the Ingress/Inbound direction to this resource.

reports:


The following SNMP collection formulas are aliased to the Inbound Volume (octets) Generic formula:
• Inbound Volume HC (octets)
• Inbound Volume LC (octets)
Inbound Volume HC (octets)
Type
SNMP (collect)

Mibs
The Inbound Volume HC (octets)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Inbound Volume HC (octets) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Inbound Volume (octets)
Formula Description
The Inbound Volume HC (octets) formula calculates the number of octets (bytes) received on this
interface since the last successful retrieval of this value.
Formula Syntax
The Inbound Volume HC (octets) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2210;
distrib(delta(sysUpTime.0), "default:1") * delta(ifHCInOctets.%I1)

The metrics that the Inbound Volume HC (octets) formula calculates display in the following reports:

Inbound Volume LC (octets)
Type
SNMP (collect)

Mibs
The Inbound Volume LC (octets)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Inbound Volume LC (octets) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Inbound Volume (octets)
Formula Description
The Inbound Volume LC (octets) formula calculates the number of octets (bytes) received on this
interface since the last successful retrieval of this value.
Formula Syntax
The Inbound Volume LC (octets) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2210;
distrib(delta(sysUpTime.0), "default:1") * delta(ifInOctets.%I1)

The metrics that the Inbound Volume HC (octets) formula calculates display in the following reports:

Outbound Broadcast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of packets presented
to an interface for transmission, including those packets that were not transmitted. These packets were addressed
to a broadcast address at this layer.

reports:
• Throughput Summary Resource (Packet) (See Health Summary Resource (Packet) on page 17.)

The following SNMP collection formulas are aliased to the Outbound Broadcast (pps) Generic
formula:
• Outbound Broadcast HC (pps)
• Outbound Broadcast LC (pps)
Outbound Broadcast HC (pps)
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Outbound->Packets
Mibs
The Outbound Broadcast HC (pps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Broadcast HC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Outbound Broadcast (pps)
Formula Description
The Outbound Broadcast HC (pps) formula calculates the rate, per second, at which the outbound
broadcast packets at this layer were delivered to a higher layer, during the last polling period. The delivered packets
include those packets that were dropped and not transmitted.
Formula Syntax
The Outbound Broadcast HC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifHCOutBroadcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Inbound Broadcast HC (pps) formula calculates display in the following reports:
Outbound Broadcast LC (pps)
Type
SNMP (collect)

Mibs
The Outbound Broadcast LC (pps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Broadcast LC (pps) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Outbound Broadcast (pps)
Formula Description
The Outbound Broadcast LC (pps) formula calculates the rate, per second, at which the outbound
broadcast packets at this layer were delivered to a higher layer, during the last polling period. The delivered packets
include those packets that were dropped and not transmitted.
Formula Syntax
The Outbound Broadcast LC (pps) formula is defined as follows. See the listed MIB or MIBs for more
delta(ifOutBroadcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Broadcast LC (pps)formula calculates display in the following reports:
Outbound Discarded (PDUs)
Type
Generic

FORMULAS->AP->Generic->Universal->Congestion Discards
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of outgoing PDUs
dropped due to congestion or resource limitations.

reports:

The following SNMP collection formulas are aliased to the Outbound Discarded (PDUs) Generic
formula:
• Outbound Discards
Outbound Discards
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Outbound->Errors
Mibs
The Outbound Discards formula makes use of the following Management Information Base (MIB):
Generic Formula
The Outbound Discards formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Congestion Discards->Outbound
Discarded (PDUs)
Formula Description
The Outbound Discards formula calculates the number of error-free packets dropped during the last
polling period. Packets may be dropped for capacity reasons (no buffer space) or for traffic-shaping reasons. This
metric is valid only on packet-oriented interfaces.
Formula Syntax
The Outbound Discards formula is defined as follows. See the listed MIB or MIBs for more information
DEF SaveAlias 2219;
distrib(delta(sysUpTime.0), "default:1") * delta(ifOutDiscards.%I1)

The metrics that the Outbound Discards formula calculates display in the following reports:
Outbound Errors
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Outbound->Errors
Mibs
The Outbound Errors formula makes use of the following Management Information Base (MIB):
Generic Formula
The Outbound Errors formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Errors->Outbound Errors (PDUs)
Formula Description
The Outbound Errors formula calculates the number of errors that occurred on the outbound interface.
For packet-oriented interfaces, errors are counted in packets. For character-oriented interfaces, errors are counted
in octets. For fixed-length interfaces, errors are counted in transmission units (where the transmission unit is the
size of the fixed-length transmission).
Formula Syntax
The Outbound Errors formula is defined as follows. See the listed MIB or MIBs for more information on
DEF SaveAlias 2215;
distrib(delta(sysUpTime.0), "default:1") * delta(ifOutErrors.%I1)

The metrics that the Outbound Errors formula calculates display in the following reports:

• Threshold Violation - Outbound Errors (Bit) (See Threshold Violation - Outbound Errors (Bit) on page 20.)
• Health Distribution Range - Outbound Errors (Bit) (See Health Distribution Range - Outbound Errors (Bit) on
page 12.)
• Threshold Violation - Outbound Errors (Packet) (See Threshold Violation - Outbound Errors (Packet) on page 21.)
• Health Distribution Range - Outbound Errors (Packet) (See Health Distribution Range - Outbound Errors (Packet) on
page 13.)
Outbound Errors (PDUs)
Type
Generic

FORMULAS->AP->Generic->Universal->Errors
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of outgoing Protocol
Data Units (PDUs) that were discarded due to errors.

reports:

• Threshold Violation - Outbound Errors (Bit) (See Threshold Violation - Outbound Errors (Bit) on page 20.)
• Health Distribution Range - Outbound Errors (Bit) (See Health Distribution Range - Outbound Errors (Bit) on
page 12.)
• Threshold Violation - Outbound Errors (Packet) (See Threshold Violation - Outbound Errors (Packet) on page 21.)
• Health Distribution Range - Outbound Errors (Packet) (See Health Distribution Range - Outbound Errors (Packet) on
page 13.)

The following SNMP collection formulas are aliased to the Outbound Errors (PDUs) Generic formula:
• Outbound Errors
Outbound Multicast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of packets presented
to an interface for transmission, including packets that were not transmitted, that were addressed to a multicast
address at this layer.

reports:

The following SNMP collection formulas are aliased to the Outbound Multicast (pps) Generic
formula:
• Outbound Multicast HC (pps)
• Outbound Multicast LC (pps)
• Outbound Non-Unicast (pps)
Outbound Multicast HC (pps)
Type
SNMP (collect)

Mibs
The Outbound Multicast HC (pps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Multicast HC (pps)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Outbound Multicast (pps)
Formula Description
The Outbound Multicast HC (pps)formula calculates the rate, per second, at which the outbound
multicast packets were delivered to this interface, during the last polling period. These packets include packets
that were dropped and not transmitted.
Formula Syntax
The Outbound Multicast HC (pps)formula is defined as follows. See the listed MIB or MIBs for more
delta(ifHCOutMulticastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Multicast HC (pps)formula calculates display in the following reports:
Outbound Multicast LC (pps)
Type
SNMP (collect)

Mibs
The Outbound Multicast LC (pps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Multicast LC (pps)formula is aliased to the following Generic formula:
Formula Description
The Outbound Multicast LC (pps)formula calculates the rate, per second, at which the outbound
multicast packets were delivered to this interface, during the last polling period. These packets include packets
that were dropped and not transmitted.
Formula Syntax
The Outbound Multicast LC (pps)formula is defined as follows. See the listed MIB or MIBs for more
delta(ifOutMulticastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Multicast LC (pps)formula calculates display in the following reports:
Outbound Non-Unicast (pps)
Type
SNMP (collect)

Mibs
The Outbound Non-Unicast (pps)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Outbound Non-Unicast (pps)formula is aliased to the following Generic formula:
Formula Description
The Outbound Non-Unicast (pps)formula calculates the rate, per second, at which non-unicast packets
at this layer were delivered to this interface during the last polling period.
This formula uses ifOutNUcastPkts, which has no HC equivalent so there are no LC/HC variants of the
formula. Note that the Outbound Non-Unicast (pps) formula maps to the same Generic formula as
the SNMP Multicast collection formulas.
Formula Syntax
The Outbound Non-Unicast (pps)formula is defined as follows. See the listed MIB or MIBs for more
delta(ifOutNUcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Multicast LC (pps)formula calculates display in the following reports:
Outbound Throughput (bps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the average rate, in bits-per-
second, of outbound traffic on this resource during the last polling period.

reports:
• Throughput Summary Group (Bit) (See Health Summary Group (Bit) on page 14.)

The following SNMP collection formulas are aliased to the Outbound Throughput (bps) Generic
formula:
• Outbound Throughput HC (bps)
• Outbound Throughput LC (bps)
Outbound Throughput HC (bps)
Type
SNMP (collect)

FORMULAS->AP->Specific->SNMP->Interfaces->Outbound->Octets
Mibs
The Outbound Throughput HC (bps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Throughput HC (bps)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Outbound Throughput
(bps)
Formula Description
The Outbound Throughput HC (bps)formula calculates the average rate, in bits-per-second, of
outbound traffic on this resource during the last polling period.
Formula Syntax
The Outbound Throughput HC (bps)formula is defined as follows. See the listed MIB or MIBs for
more information on the OIDs that the formula uses.
DEF SaveAlias 2209;
deciseconds;
800 * delta(ifHCOutOctets.%I1) / delta(sysUpTime.0)

The metrics that the Outbound Throughput HC (bps)formula calculates display in the following
reports:
Outbound Throughput LC (bps)
Type
SNMP (collect)

Mibs
The Outbound Throughput LC (bps)formula makes use of the following Management Information
Bases (MIBs):
Generic Formula
The Outbound Throughput LC (bps)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Outbound Throughput (bps)
Formula Description
The Outbound Throughput LC (bps)formula calculates the average rate, in bits-per-second, of
outbound traffic on this resource during the last polling period.
Formula Syntax
The Outbound Throughput LC (bps)formula is defined as follows. See the listed MIB or MIBs for
more information on the OIDs that the formula uses.
DEF SaveAlias 2209;
deciseconds;
800 * delta(ifOutOctets.%I1) / delta(sysUpTime.0)

The metrics that the Outbound Throughput LC (bps)formula calculates display in the following
reports:
Outbound Unicast (pps)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of outbound packets
presented to an interface for transmission, including those that were not transmitted, during the last polling
period. The calculation does not include packets addressed to a multicast or broadcast address at this layer.

reports:

The following SNMP collection formulas are aliased to the Outbound Unicast (pps)Generic formula:
• Outbound Unicast HC (pps)
• Outbound Unicast LC (pps)
Outbound Unicast HC (pps)
Type
SNMP (collect)

Mibs
The Outbound Unicast HC (pps)formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Outbound Unicast HC (pps)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Outbound Unicast (pps)
Formula Description
The Outbound Unicast HC (pps)formula calculates the rate, per second, at which outbound packets
were presented to this interface during the last polling period. The calculation does not include packets addressed
to a multicast or broadcast address at this layer, but does include dropped packets that were not transmitted.
Formula Syntax
The Outbound Unicast HC (pps)formula is defined as follows. See the listed MIB or MIBs for more
delta(ifHCOutUcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Unicast HC (pps)formula calculates display in the following reports:
Outbound Unicast LC (pps)
Type
SNMP (collect)

Mibs
The Outbound Unicast LC (pps)formula makes use of the following Management Information Base
(MIB):
Generic Formula
The Outbound Unicast LC (pps)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Interface->Outbound Unicast (pps)
Formula Description
The Outbound Unicast LC (pps)formula calculates the rate, per second, at which outbound packets
were presented to this interface during the last polling period. The calculation does not include packets addressed
to a multicast or broadcast address at this layer, but does include dropped packets that were not transmitted.
Formula Syntax
The Outbound Unicast LC (pps)formula is defined as follows. See the listed MIB or MIBs for more
delta(ifOutUcastPkts.%I1) / delta(sysUpTime.0) * 100

The metrics that the Outbound Unicast LC (pps)formula calculates display in the following reports:
Outbound Utilization (percent)
Type
Generic

FORMULAS->AP->Generic->Universal->Utilization
Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the average percentage of the
outbound bandwidth (capacity) used on this resource on this interface during the last polling period. This
percentage is valid only if the interface has a defined bandwidth, that is, the ifSpeed OID (defined in the
RFC1213-MIB) is non-zero.
For full-duplex network interfaces such as Ethernet, this formula only reports the percentage of the interface’s
total capacity used by outgoing traffic. This percentage needs to be added to the inbound utilization percentage
to determine the total utilization on a full-duplex interface.

reports:
• Throughput Distribution Range - Outbound Utilization (Bit) (See Throughput Distribution Range - Outbound
Utilization (Bit) on page 25.)

The following SNMP collection formulas are aliased to the Outbound Utilization (percent)
Generic formula:
• Outbound Utilization HC (percent)
• Outbound Utilization HC/HS (percent)
• Outbound Utilization LC (percent)
Outbound Utilization HC (percent)
Type
SNMP (collect)

Mibs
The Outbound Utilization HC (percent)formula makes use of the following Management
Generic Formula
The Outbound Utilization HC (percent)formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Utilization->Outbound Utilization
(percent)
Formula Description
The Outbound Utilization HC (percent)formula calculates the average percentage of the
Formula Syntax
The Outbound Utilization HC (percent)formula is defined as follows. See the listed MIB or MIBs
DEF SaveAlias 2207;
(800 * delta(ifHCOutOctets.%I1) / delta(sysUpTime.0)) / distrib(ifSpeed.%I1,
">0:*") * 100

The metrics that the Outbound Utilization HC (percent)formula calculates display in the following
reports:
Outbound Utilization HC/HS (percent)
Type
SNMP (collect)

Mibs
The Outbound Utilization HC/HS (percent)formula makes use of the following Management
Generic Formula
The Outbound Utilization HC/HS (percent)formula is aliased to the following Generic formula:
(percent)
Formula Description
The Outbound Utilization HC/HS (percent)formula calculates the average percentage of the
Formula Syntax
The Outbound Utilization HC/HS (percent) formula is defined as follows. See the listed MIB or
MIBs for more information on the OIDs that the formula uses.
DEF SaveAlias 2207;
(800 * delta(ifHCOutOctets.%I1) / delta(sysUpTime.0)) /
distrib(ifHighSpeed.%I1, ">0:*") / 10000

The metrics that the Outbound Utilization HC/HS (percent) formula calculates display in the
following reports:
Outbound Utilization LC (percent)
Type
SNMP (collect)

Mibs
The Outbound Utilization LC (percent)formula makes use of the following Management
Information Base (MIB):
Generic Formula
The Outbound Utilization LC (percent) formula is aliased to the following Generic formula:
(percent)
Formula Description
The Outbound Utilization LC (percent)formula calculates the average percentage of the
Formula Syntax
The Outbound Utilization LC (percent) formula is defined as follows. See the listed MIB or MIBs
DEF SaveAlias 2207;
(800 * delta(ifOutOctets.%I1) / delta(sysUpTime.0)) / distrib(ifSpeed.%I1,
">0:*") * 100

The metrics that the Outbound Utilization LC (percent) formula calculates display in the
following reports:

Outbound Volume (octets)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the volume of traffic, in octets,
in the Egress/Outbound direction from this resource.

reports:


The following SNMP collection formulas are aliased to the Outbound Volume (octets)Generic formula:
• Outbound Volume HC (octets)
• Outbound Volume LC (octets)
Outbound Volume (PDUs)
Type
Generic

Formula Description
Each of the SNMP collection formulas that alias this Generic formula calculates the number of Protocol Data
Units (PDUs) (packets, cells, frames, and so forth) that this resource transmits.

reports:

The following SNMP collection formulas are aliased to the Outbound Volume (PDUs)Generic formula:
• Transmitted U/M/B/D/E HC
• Transmitted U/M/B/D/E LC
• Transmitted U/NU/D/E
Outbound Volume HC (octets)
Type
SNMP (collect)

Mibs
The Outbound Volume HC (octets) formula makes use of the following Management Information
Base (MIB):
Generic Formula
The Outbound Volume HC (octets) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Outbound Volume (octets)
Formula Description
The Outbound Volume HC (octets) formula calculates the number of octets (bytes) transmitted out of
this interface during the last polling period.
Formula Syntax
The Outbound Volume HC (octets) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2211;
distrib(delta(sysUpTime.0), "default:1") * delta(ifHCOutOctets.%I1)

The metrics that the Outbound Volume HC (octets) formula calculates display in the following reports:

Outbound Volume LC (octets)
Type
SNMP (collect)

Mibs
The Outbound Volume LC (octets) formula makes use of the following Management Information
Base (MIB):
Generic Formula
The Outbound Volume LC (octets) formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Outbound Volume (octets)
Formula Description
The Outbound Volume LC (octets) formula calculates the number of octets (bytes) transmitted out of
this interface during the last polling period.
Formula Syntax
The Outbound Volume LC (octets) formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2211;
distrib(delta(sysUpTime.0), "default:1") * delta(ifOutOctets.%I1)

The metrics that the Outbound Volume LC (octets) formula calculates display in the following reports:

Transmitted U/M/B/D/E HC
Type
SNMP (collect)

Mibs
The Transmitted U/M/B/D/E HC formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Transmitted U/M/B/D/E HC formula is aliased to the following Generic formula:
FORMULAS->AP->Generic->Universal->Throughput->Outbound Volume (PDUs)
Formula Description
The Transmitted U/M/B/D/E HC formula calculates the total packets (all packets) transmitted out of this
interface during the last polling period.
Formula Syntax
The Transmitted U/M/B/D/E LC formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2198;
distrib(delta(sysUpTime.0), "default:1") * (delta(ifHCOutUcastPkts.%I1) +
delta(ifHCOutMulticastPkts.%I1) + delta(ifHCOutBroadcastPkts.%I1) -
delta(ifOutDiscards.%I1) - delta(ifOutErrors.%I1))

The metrics that the Transmitted U/M/B/D/E LC formula calculates display in the following reports:
Transmitted U/M/B/D/E LC
Type
SNMP (collect)

Mibs
The Transmitted U/M/B/D/E LC formula makes use of the following Management Information Bases
(MIBs):
Generic Formula
The Transmitted U/M/B/D/E LC formula is aliased to the following Generic formula:
Formula Description
The Transmitted U/M/B/D/E LC formula calculates the total packets (all packets) transmitted out of this
Formula Syntax
The Transmitted U/M/B/D/E LC formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2198;
distrib(delta(sysUpTime.0), "default:1") * (delta(ifOutUcastPkts.%I1) +
delta(ifOutMulticastPkts.%I1) + delta(ifOutBroadcastPkts.%I1) -
delta(ifOutDiscards.%I1) - delta(ifOutErrors.%I1))

The metrics that the Transmitted U/M/B/D/E LC formula calculates display in the following reports:
Transmitted U/NU/D/E
Type
SNMP (collect)

Mibs
The Transmitted U/NU/D/E formula makes use of the following Management Information Base (MIB):
Generic Formula
The Transmitted U/NU/D/E formula is aliased to the following Generic formula:
Formula Description
The Transmitted U/NU/D/E formula calculates the total packets (all packets) transmitted out of this
Formula Syntax
The Transmitted U/NU/D/E formula is defined as follows. See the listed MIB or MIBs for more
DEF SaveAlias 2198;
distrib(delta(sysUpTime.0), "default:1") * (delta(ifOutUcastPkts.%I1) +
delta(ifOutNUcastPkts.%I1) - delta(ifOutDiscards.%I1) -
delta(ifOutErrors.%I1))

The metrics that the Transmitted U/NU/D/E formula calculates display in the following reports:
NOTES
Chapter 8: Discovery Formulas
Topic Page
Netcool/Proviso Discovery Formula Tree for the Lucent Stinger Application 141
Pack
Discovery Formulas 141
Overview
A discovery formula (also called an inventory formula) allows Netcool/Proviso to recognize resources specific
to the target devices and technologies supported in the Lucent Stinger® DSL Access Concentrator environment
so that information can then be collected on those resources. A discovery formula runs during the inventory
process - the process of discovering and analyzing the network. Discovery formulas for some network interfaces
and devices (for example, Frame Relay) are already included with Netcool/Proviso DataMart.
The Lucent Stinger Application Pack provides discovery formulas specific to the devices and technologies that
operate in the Lucent Stinger® DSL Access Concentrator environment. This user guide discusses the discovery
formulas that the Lucent Stinger Application Pack provides.
Netcool/Proviso Discovery Formula Tree for the Lucent Stinger

Application Pack
The Lucent Stinger Application Pack provides a formula tree where the Discovery 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.
Discovery Formulas
The Lucent Stinger Application Pack provides Discovery formulas that recognize resources specific to the target
devices and technologies that operate in a specific network environment. The Discovery formulas for the devices
that the Lucent Stinger Application Pack supports reside in this directory: FORMULAS->Alias Instance
and Label Inventory->AP->IGS->Lucent.
Specifically, the Lucent Stinger Application Pack provides:
• LucentStinger_disc_device_formula Discovery Formula
• LucentStinger_disc_ports_formula Discovery Formula
The following sections discuss each of these Discovery formulas.
LucentStinger_disc_device_formula Discovery Formula

The Lucent Stinger Application Pack provides a LucentStinger_disc_device_formula Discovery
formula that defines the characteristics of and discovers information related to Stinger DSL Device sub-elements.
The LucentStinger_disc_device_formula Discovery formula defines OIDVAL expression lines
that reference OID objects defined in the following MIBs:

Furthermore, the LucentStinger_disc_device_formula Discovery formula attaches

Netcool/Proviso properties to each Stinger DSL Device sub-element. Some of these Netcool/Proviso properties
display values associated with the defined OID objects. See Stinger DSL Device Sub-Element Properties on page 36 for
descriptions of the Netcool/Proviso properties that the LucentStinger_disc_device_formula
Discovery formula attaches to Stinger DSL Device sub-elements.
The LucentStinger_disc_device_formula Discovery formula provides an OID Gathering section
and a Sub-Elements Results Line section. The LucentStinger_disc_device_formula Discovery
formula is defined as follows. Line breaks appear to make the formula more readable. The numbers that appear
in square brackets in the formula map to a numbered list that describes tasks that the formula performs.
# OID Gathering Section

LucentStinger=OIDVAL(chassisDesc.0);
# Sub-Elements Results Line Section

%LucentStinger index “<NULL>|| [1]
Lucent_Stinger|| [2]
IGS_VendorName<Lucent_Stinger>AP_EDP<IGS> [3]
||”; [4]

LucentStinger=OIDVAL(sysObjectID.0);

%LucentStinger index “<NULL>|| [1]
Lucent_Stinger|| [2]
IGS_VendorName<Lucent_Stinger>AP_EDP<IGS> [3]
||”; [4]
1. Specifies the first field of the Sub-Elements Results Line Section. The first field specifies the sub-element
instance string transmitted to each collection formula when the specified sub-element is deployed for
collection. This instance string displays in the instance field (Sub-element view) of the Netcool/Proviso
DataMart Resource Editor for each deployed Stinger DSL Device sub-element. In this case, the instance
string displays as <NULL>.
2. Specifies the second field of the Sub-Elements Results Line Section. The second field specifies the custom
label of the sub-element. The custom label displays in the label field (Sub-element view) of the
Netcool/Proviso DataMart Resource Editor for each deployed Stinger DSL Device sub-element. The
customer label may also display in reports that show statistics related to Stinger DSL Device sub-elements.
The custom label typically displays under some Name, Device Name, or some similar column. See Stinger DSL
Device Sub-Element Label on page 56 for more information on the syntax used to construct these sub-element
labels.
The label is the string Lucent_Stinger.

3. Specifies the third field of the Sub-Elements Results Line Section. The third field defines the property list
(property name and property value pair). This property list displays in the Properties list (Sub-Element view)
of the Netcool/Proviso DataMart Resource Editor for each Stinger DSL Device sub-element. See Stinger DSL
Device Sub-Element Properties on page 36 for more information on these properties.
4. Specifies an optional fourth field of the Sub-Elements Results Line Section. If specified, this field contains
the invariant of the sub-element. The invariant is used during the synchronization process to detect a change
of element properties, including the instance string (the first field). The
LucentStinger_disc_device_formula Discovery formula does not specify an invariant.
LucentStinger_disc_ports_formula Discovery Formula

formula that defines the characteristics of and discovers information related to Stinger Ethernet Interface
DSLAM Card and Stinger Ethernet Interface Uplink Card sub-elements. The
LucentStinger_disc_ports_formula Discovery formula defines OIDVAL expression lines that
reference OID objects defined in the following MIBs:

Furthermore, the LucentStinger_disc_ports_formula Discovery formula attaches

Netcool/Proviso properties to each Stinger Ethernet Interface DSLAM Card and Stinger Ethernet Interface
Uplink Card sub-element. Some of these Netcool/Proviso properties display values associated with the defined
OID objects. See Stinger Ethernet Interface DSLAM Card Sub-Element Properties on page 37 for descriptions of the
Netcool/Proviso properties that the LucentStinger_disc_ports_formula Discovery formula
attaches to Stinger Ethernet Interface DSLAM Card and Stinger Ethernet Interface Uplink Card sub-elements.
The LucentStinger_disc_ports_formula Discovery formula provides a Dim section, an OID
Gathering section, and a Sub-Elements Results Line section. The
LucentStinger_disc_ports_formula Discovery formula is defined as follows. Line breaks appear to
make the formula more readable. The numbers that appear in square brackets in the formula map to a numbered
list that describes tasks that the formula performs.
# Dim Section
Dim I1 As Integer Default *;
Def AllowCreationOfSE No;
IfIndex = OIDINST(slotIfIndex.%I1);

V001 = OIDINST(ifAdminStatus.%IfIndex == 1);
PortNum = OIDVAL(slotIfItemIndex.%V001);
SlotNum = OIDVAL(slotIfSlotIndex.%V001);
ShelfNum = OIDVAL(slotIfShelfNumber.%V001);
EtherSpeed = OIDVAL(ifSpeed.%V001);
LinkSpeed = OIDVAL(%EtherSpeed/1000000);
DSLAMCard = distrib( slotIfSlotIndex.%V001, "< 8:*" );

UpLinkCard = distrib( slotIfSlotIndex.%V001, ">18:,>7:*" );

%UpLinkCard index "If<%V001>|| [1]
IF: %SlotNum:%PortNum (%LinkSpeed Mbps) || [2]
IGS_VendorName<Lucent_Stinger>
IGS_LucentStingerUpLinkCard<UpLinkCard: %UpLinkCard>
IGS_LucentStingerUpLinkCardPort<UpLinkCardPort: %PortNum>
AP_EDP<IGS>
IGS_LucentStingerPortType<UPLink_Port> [3]
||”; [4]

%DSLAMCard index "If<%V001>|| [1]
IF: %SlotNum:%PortNum (%LinkSpeed Mbps) || [2]
IGS_VendorName<Lucent_Stinger>
IGS_LucentStingerDSLAMCard<DSLAMCard: %DSLAMCard>
IGS_LucentStingerDSLAMCardPort<DSLAMCardPort: %PortNum>
AP_EDP<IGS>
IGS_LucentStingerPortType<DSLAM_Port> [3]
||”; [4]
1. Specifies the first field of the Sub-Elements Results Line Section. The first field specifies the sub-element
instance string transmitted to each collection formula when the specified sub-element is deployed for
collection. This instance string displays in the instance field (Sub-element view) of the Netcool/Proviso
DataMart Resource Editor for each deployed Stinger Ethernet Interface DSLAM Card and Stinger Ethernet
Interface Uplink Card sub-element.
The instance string is the result of an expression stored in the V001 temporary variable defined in the OID
Gathering section.
2. Specifies the second field of the Sub-Elements Results Line Section. The second field specifies the custom
label of the sub-element. The custom label displays in the label field (Sub-element view) of the
Netcool/Proviso DataMart Resource Editor for each deployed Stinger Ethernet Interface DSLAM Card and
Stinger Ethernet Interface Uplink Card sub-element. The custom label can also display in reports that show
statistics related to Stinger Ethernet Interface DSLAM Card and Stinger Ethernet Interface Uplink Card sub-
elements. See Stinger Ethernet Interface DSLAM Card Sub-Element Label on page 56 and Stinger Ethernet Interface Uplink
Card Sub-Element Label on page 57 for more information on the syntax used to construct these sub-element
labels.
3. Specifies the third field of the Sub-Elements Results Line Section. The third field defines the property list
(property name and property value pair). This property list displays in the Properties list (Sub-Element view)
of the Netcool/Proviso DataMart Resource Editor for each deployed Stinger Ethernet Interface DSLAM
Card and Stinger Ethernet Interface Uplink Card sub-element. See Stinger Ethernet Interface DSLAM Card Sub-
Element Properties on page 37 and Stinger Ethernet Interface Uplink Card Sub-Element Properties on page 39 for more
information on these properties.
4. Specifies an optional fourth field of the Sub-Elements Results Line Section. If specified, this field contains
the invariant of the sub-element. The invariant is used during the synchronization process to detect a change
of element properties, including the instance string (the first field). The
LucentStinger_disc_ports_formula Discovery formula does not specify an invariant.
NOTES
Appendix A: Configuration
This appendix explains how to configure the Lucent Stinger Application Pack and consists of the following
topics:
Topic Page
Overview 147
Before You Begin 147
Configure the Application Pack 148
Other Tasks and Considerations 150
Overview
The Lucent Stinger Application Pack is a MIB-based, SNMP pack, and its configuration is relatively
straightforward.
Before You Begin
Before configuring the Lucent Stinger Application Pack, ensure that you:
• Have the following software or guides:
— The release notes for the current application pack release.
— The version of the Netcool/Proviso DataMart Configuration Guide that corresponds to your version of
Netcool/Proviso.
Important: You will need to refer to this guide in order to run an SNMP inventory profile.
— Access to the Netcool/Proviso DataMart server.

— An X Window server on the DataMart server.
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:

— Installed the current version of the Netcool/Proviso components, as described in the Netcool/Proviso
Installation Guide.
— Installed the MIB-II application pack
Note: Starting with version 4.3-T, the MIB-II Application Pack no longer resides in the single bundled jar
file. It is a stand-alone application pack that is contained in its own jar file.
— Installed the Lucent Stinger Application Pack.

— Configured at least one DataChannel.
— Configured an SNMP Collector subchannel.
Configure the Application Pack
To configure the Lucent Stinger Application Pack, follow these steps:
Important: Localization is now done automatically during installation of the application 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. Activate data collection requests.

During installation of the application 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:
2-a. Change your working directory to $PVMHOME/bin (/opt/datamart/bin, by default) on the
DataMart server.
2-b. Invoke the DataMart GUI by entering the following command and pressing Enter:
pvm
2-c. Click the Configuration tab, then click Request Editor to open the Request Editor.
2-d. Click the Collection tab.
2-e. Click Refresh.

The predefined data collection requests are loaded into the Request Editor from the database.
2-f. Click the Inactive button in the Filter group box to display only idle requests.
2-g. In the Sub-Element Groups pane, select all idle data collection requests in the following group or
groups:
Root->Sub-Element Collect->Interfaces->Traffic In and Interfaces->Traffic

Out
2-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.
2-i. Click Save.
3. (Requires the Netcool/Proviso DataMart Configuration Guide) Run the initial SNMP inventory and initiate a
discovery.
An inventory collects data about the network resources that the application pack monitors. After you install
an SNMP application pack, you must create an inventory profile using the Inventory Tool Wizard and then
initiate a discovery by executing the inventory profile using the Inventory Tool.
Running the initial inventory against SNMP objects is an intricate task and unfortunately beyond the scope
of this configuration appendix. For instructions on using the Inventory Tool Wizard to create an inventory
profile and the Inventory Tool to execute the inventory profile, see the Netcool/Proviso DataMart Configuration
Guide.
4. Deploy reports.
After the application 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 Editor’s
NOC Reporting tree.
To deploy the Lucent Stinger Application Pack reports, follow these steps:
4-a. Open the Netcool/Proviso DataMart Resource Editor.
4-b. Click the ReportSEGroup tab.
4-c. Move the cursor to the left pane and scroll up to select any group under the SUB-ELEMENTS->NOC
Reporting tree.
4-d. Right-click and select the AutoGrouping option from the menu. The AutoGrouping option places the
reports in dynamically generated groups created during inventory.
4-e. Click Yes to continue.
4-f. Click Close to exit the message box, or click Details to view a description of any errors.
4-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
• Changing Predefined Threshold Requests
Verifying Resources
Use the Netcool/Proviso DataMart Resource Editor to determine if the application pack’s 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.
Changing Predefined Threshold Requests
The Lucent Stinger Application Pack supplies predefined threshold requests. The setup program automatically
loads these predefined threshold requests into the database and configures them for you. You do not need to
activate them, but you can use the Netcool/Proviso DataMart Resource Editor to change them.
See the Netcool/Proviso DataMart Configuration Guide for information on working with predefined threshold
requests.
Additional Copyright Information
The following copyright information is for software used by Netcool/Proviso DataMart.
TCL and TK
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.
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.
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.
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.
Additional Copyright information
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.
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.
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.
• 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 POSSIBILITY OF
SUCH DAMAGE.

NetcoolProviso-Lucent Stinger Device 1.1.1.0 Tech Pack User Guide

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

NetcoolProviso-Lucent Stinger Device 1.1.1.0 Tech Pack User Guide

Încărcat de

Drepturi de autor:

Formate disponibile

Netcool®/Proviso®

Lucent Stinger DSL Application Pack User’s Guide

This information contains sample application programs

Chapter 2: Supported Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 3: Devices and Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

Chapter 4: Element and Sub-Element Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Chapter 5: Sub-Element Grouping Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Chapter 6: Defined Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 7: SNMP Collection Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Chapter 8: Discovery Formulas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Appendix A: Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Provides a general introduction to application packs.

• Chapter 2, Supported Reports

• Chapter 3, Devices and Services

• Chapter 4, Element and Sub-Element Properties

• Chapter 5, Sub-Element Grouping Rules

• Chapter 6, Defined Resources

• Chapter 7, SNMP Collection Formulas

• Chapter 8, Discovery Formulas

Describes how to configure the Lucent Stinger Application Pack.

The Netcool/Proviso Product Suite

Figure 1: Netcool/Proviso Modules

This chapter discusses the following topics:

How is the Data Collected? 1

How is the Data Processed and Loaded into the Database? 2

How is the Data Reported? 3

How is the Data Collected?

How is the Data Processed and Loaded into the Database?

How is the Data Reported?

This chapter discusses the following topics:

Bit Health Reporter Set

Bit Throughput Reporter Set

Packet Throughput Reporter Set

Packet Health Reporter Set

• Health Summary Resource (Packet)

Health (Octets) Details

Metrics Displayed on Report

Health (Packet) Details

Metrics Displayed on Report

Health Distribution Range - Inbound Errors (Bit)

Metrics Displayed on Report

Health Distribution Range - Inbound Errors (Packet)

Metrics Displayed on Report

Health Distribution Range - Outbound Errors (Bit)

Metrics Displayed on Report

Health Distribution Range - Outbound Errors (Packet)

Metrics Displayed on Report

Health Summary Group (Bit)

Metrics Displayed on Report

Health Summary Group (Packet)

Metrics Displayed on Report

Health Summary Resource (Bit)

Metrics Displayed on Report

Health Summary Resource (Packet)

Metrics Displayed on Report

Threshold Violation - Inbound Errors (Bit)

Metrics Displayed on Report

Threshold Violation - Inbound Errors (Packet)

Metrics Displayed on Report

Threshold Violation - Outbound Errors (Bit)

Metrics Displayed on Report

Threshold Violation - Outbound Errors (Packet)

Metrics Displayed on Report