Avaya Proactive Contact Release 5.x

Transcription

1 Avaya Proactive Contact Release 5.x Overview of Alarms framework and SNMP Issue 1.1

2 Notice: While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer: Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. Link disclaimer: Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. Warranty: Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available through the Avaya Support Web site: License: USE OR INSTALLATION OF THE PRODUCT INDICATES THEEND USER'S ACCEPTANCE OF THE TERMS SET FORTHHEREIN AND THE GENERAL LICENSE TERMS AVAILABLEON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). IF YOU DO NOT WISH TO BE BOUND BY THESE TERMS, YOU MUST RETURN THE PRODUCT(S) TO THE POINT OF PURCHASE WITHIN TEN (10) DAYS OF DELIVERY FOR A REFUND OR CREDIT. Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single standalone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s) Designated System(s) License (DS): End User may install and use each copy of the Software on only one Designated Processor, unless a different number of Designated Processors is indicated in the Documentation or other materials available to End User. Avaya may require the Designated Processor(s) to be identified by type, serial number, feature key, location or other specific designation, or to be provided by End User to Avaya through electronic means established by Avaya specifically or this purpose. Concurrent User License (CU): End User may install and use the Software on multiple Designated Processors or one or more Servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses and can be, without limitation, an agent, port or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL): Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. CPU License (CP): End User may install and use each copy of the Software on a number of Servers up to the number indicated by Avaya provided that the performance capacity of the Server(s) does not exceed the performance capacity specified for the Software. End User may not re-install or operate the Software on Server(s) with a larger performance capacity without Avaya's prior consent and payment of an upgrade fee. Named User License (NU): Customer may: (i) install and use the Software on a single Designated Processor or Server per authorized Named User (defined below); or (ii) install and use the Software on a Server so long as only authorized Named Users access and use the Software. "Named User," means a user or device that has been expressly authorized by Avaya to access and use the Software. At Avaya's sole discretion, a "Named User" may be, without limitation, designated by name, corporate function (e.g., webmaster or helpdesk), an or voice mail account in the name of a person or corporate function, or a directory entry in the administrative database utilized by the Product that permits one user to interface with the Product. Shrinkwrap License (SR): With respect to Software that contains elements provided by third party suppliers, End User may install and use the Software in accordance with the terms and conditions of the applicable license agreements, such as "shrinkwrap" or "clickwrap" license accompanying or applicable to the Software ("Shrinkwrap License"). The text of the Shrinkwrap License will be available from Avaya upon End User s request (see Third-party Components" for more information). Copyright: Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components: Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Preventing toll fraud: "Toll fraud" is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there can be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya fraud intervention: If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. For additional support telephone numbers, see the Avaya Support Web site: Trademarks: Avaya and the Avaya logo are either registered trademarks or trademarks of Avaya Inc. in the United States of America and/or other jurisdictions. All other trademarks are the property of their respective owners. Downloading documents: For the most current versions of documentation, see the Avaya Support Web site: Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 2

3 Contents Alarms framework... 4 Defining Events, Faults, and Alarms... 4 Integration with SNMP... 4 The Proactive Contact Dialer MIB v Support for System Inventory and Resources... 8 PG230 Switch Alarms... 9 Dialer Alarms Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 3

4 Alarms framework Defining Events, Faults, and Alarms In simple terms, a significant occurrence or happening of interest is an event. If it is a result of a deviation from normal operation resulting in a lasting error or warning condition, it is a fault. An event or a fault may generate an alarm. An alarm is a persistent indication of an interesting fault or an event that clears only when the triggering condition has been resolved. A current list of interesting events occurring on a system is often maintained in the form of an active alarm list. A notification may be sent not only when an alarm is raised, but also when it has been resolved and the condition cleared. Starting from release 5.0, the dialer now has an alarm framework to help monitor interesting events and faults. Any process may now be equipped to raise and clear an alarm condition, and thereby notify observers of events and faults. The framework may be extended easily after deployment to allow raising new alarms that may not be available out of the box. An alarm may be raised by any process using the alarms API, or even from a shell script using a utility program for the same. The alarms are maintained by the alarms daemon 'alarmd', and administered by the 'alarmadm'. The alarms may be queried, cleared or notifications sent using SNMP. Please refer to the PC Dialer documentation and handbooks for configuring the alarm framework. Integration with SNMP The new PC MIB may be found on the dialer at /opt/avaya/pds/config/snmp/pcmib_v1_1.mib. By default, SNMP notifications may be sent when the alarm state changes, ie, when an ACTIVE alarm gets CLEARED, or a CLEAR alarm becomes ACTIVE. It may even be configured if desired for a notification to be sent every time an alarm is RAISED, even if never CLEARED. An ACTIVE alarm may be cleared remotely through an SNMP SET operation on its severity using the string "Clear", that is on OIDs apcpg230alarmseverity ( [1-110]) and apcdialeralarmseverity ( [1-64]). SNMP integration of the alarm framework is achieved through Net-SNMP (net-snmp el5). Please visit for detailed tutorials, samples and online documentation. Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 4

5 The Proactive Contact Dialer MIB v 1.1 Listed below is the dialer MIB translated into a tree form: +--pcmib1(1) +--apcnotifications(1) +--apctraps(0) +--apcpg230traps(1) +--apctrapq230e00001(1). +--apctrapq230e00120(120) +--apcdialertraps(2) +--apctrapqpc000d0001(1). +--apctrapqpc000d0064(64) +--apcalarms(2) +--apcpg230alarms(1) +--apcpg230alarmtable(1) +--apcpg230alarmentry(1) Index: apcpg230alarmid +-- -R-- EnumVal apcpg230alarmid(1) Values: insuffmem( )... reserved78( ) +-- -R-- String apcpg230alarmseverity(2) Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 5

6 +-- -R-- String apcpg230alarmcategory(3) +-- -R-- String apcpg230alarmtext(4) +-- -R-- String apcpg230alarmraw(5) +-- -R-- String apcpg230alarmlocation(6) +-- -R-- String apcpg230alarmfirstraised(7) +-- -R-- String apcpg230alarmlastraised(8) +-- -R-- Integer32 apcpg230alarmnumraised(9) +--apcdialeralarms(2) +--apcdialeralarmtable(1) +--apcdialeralarmentry(1) Index: apcdialeralarmid +-- -R-- EnumVal apcdialeralarmid(1) Values: dalr000d0001(851969)... dalr000d0064(852068) +-- -R-- String apcdialeralarmseverity(2) +-- -R-- String apcdialeralarmcategory(3) +-- -R-- String apcdialeralarmtext(4) +-- -R-- String apcdialeralarmraw(5) +-- -R-- String apcdialeralarmlocation(6) +-- -R-- String apcdialeralarmfirstraised(7) +-- -R-- String apcdialeralarmlastraised(8) +-- -R-- Integer32 apcdialeralarmnumraised(9) The PG230 alarms are presented in the table OID apcpg230alarmtable, and the Dialer alarms are presented in the table OID apcdialeralarmtable. Either of these tables, or any specific OID there, may be queried to obtain alarm status of any specific alarm. Each of the notification OIDs under apcpg230traps and apcdialertraps will be packed with the entire row from the respective tables. Therefore, each notification comprises of the following information: Field Alarm ID Information A unique identifier for each alarm originating on the dialer or the PG230 switch that corresponds to a specific event or a fault. Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 6

7 Field Severity Category Text Raw Location First Raised Last Raised Num Raised Information When clear, it is clear (0), and when active (raised), every alarm has a specific severity corresponding to the event or the fault condition, in the following range: fatal (1), critical (2), major (3), minor (4), warning (5), info (6), unknown (7). Category of the alarm that helps in classifying the event or the fault. Every alarm may further have an instance specific text associated with it. An alarm may further have an instance specific raw bytes associated which may be parsed to extract additional information. Alarm origin hostname. The first time the alarm was raised and became active. The last time the alarm was raised. Number of times the alarm was raised between the first and the last timestamps. As mentioned earlier, if SNMP notifications are enabled, the default behavior is that a notification will be sent to the destination(s) every time the alarm state changes, that is, every time an alarm is raised or cleared. For example, it will be sent the first time alarm is raised, but not on any subsequent occurrences, and the time it is cleared. This default behavior may be changed to generate a notification every time the alarm is raised. Repeated clearing of the alarm will not generate repeated notifications for the alarm getting cleared again. Note: SNMP query operations using WALKs on the MIB are CPU intensive. Subscribing to notifications is the preferred and optimal way to monitor alarms. Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 7

8 Support for System Inventory and Resources The Host Resources MIB defines a uniform set of objects useful for the management of host computers. Host computers are independent of the operating system, network services, or any software application. The Host Resources MIB defines objects which are common across many computer system architectures. The mib is located at /usr/share/snmp/mibs/host-resources-mib.txt. In addition, there are objects in the SNMPv2-MIB [RFC1907] and IF-MIB [RFC2233] which also provide host management functionality. MIB-2 [RFC1213] too is supported by Net-SNMP. These MIBs are located in the /usr/share/snmp/mibs directory and the integration provided by Net-SNMP packages. Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 8

9 Complete List of Alarms PG230 Switch Alarms Listed below is the complete list of alarms generated by the PG230 switch, which are fetch on to the dialer. ID Severity Defined Category Defined Description QPC230E0001 minor System Watchdog Alarms Insufficient Timed IPC Memory QPC230E0002 fatal System Watchdog Alarms Network Manager Failure QPC230E0003 fatal System Watchdog Alarms Host Manager Failure QPC230E0004 minor System Watchdog Alarms Redundancy Manager Failure QPC230E0010 minor Host Manager Alarms Host Communications Failure QPC230E0011 major Host Manager Alarms No Hosts QPC230E0012 major Host Manager Alarms ADLC Sub-System Failure QPC230E0013 major Host Manager Alarms Ethernet Sub-System Failure QPC230E0014 major Host Manager Alarms Overlay Sub-System Failure QPC230E0015 warning Host Manager Alarms TeleRouter Resource Warning QPC230E0016 warning Host Manager Alarms TeleRouter Resource Exhausted QPC230E0017 warning Host Manager Alarms Host Ethernet Internet Ping Failure QPC230E0020 major Network Manager Alarms Start Record Exhaust QPC230E0021 major Network Manager Alarms End Record Exhaust QPC230E0022 major Network Manager Alarms ISDN D-Channel Pool Exhaust QPC230E0023 fatal Network Manager Alarms NBC Does Not Respond QPC230E0024 fatal Network Manager Alarms NBC DMA Output Failure QPC230E0025 critical Network Manager Alarms CP Transmit Overrun QPC230E0026 critical Network Manager Alarms No NBC In System QPC230E0027 fatal Network Manager Alarms NBC Failure QPC230E0028 fatal Network Manager Alarms NBC Loss Of Internal Sync Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 9

10 ID Severity Defined Category Defined Description QPC230E0029 minor Network Manager Alarms NBC Comm Bus Failure QPC230E0030 critical Network Manager Alarms No Tone Card In System QPC230E0031 critical Network Manager Alarms Rack 1, Level 2 Failure QPC230E0032 critical Network Manager Alarms Rack 1, Level 3 Failure QPC230E0033 critical Network Manager Alarms Rack 2, Level 0 Failure QPC230E0034 critical Network Manager Alarms Rack 2, Level 1 Failure QPC230E0035 critical Network Manager Alarms Rack 2, Level 2 Failure QPC230E0036 critical Network Manager Alarms Rack 2, Level 3 Failure QPC230E0037 minor Network Manager Alarms Standby System Failure QPC230E0038 major Network Manager Alarms PRI -D-Channel Failure QPC230E0039 major Network Manager Alarms PRI/T1 Carrier Lost QPC230E0040 major Network Manager Alarms PRI/T1 Card Failure QPC230E0041 minor Network Manager Alarms PRI/T1 Remote Alarm QPC230E0042 minor Network Manager Alarms PRI/T1 Out Of Frame QPC230E0043 minor Network Manager Alarms PRI/T1 Signalling Bit Alarm QPC230E0044 minor Network Manager Alarms PRI/T1 Slip Maint. Threshold QPC230E0045 minor Network Manager Alarms PRI/T1 OOF Maint. Threshold QPC230E0046 minor Network Manager Alarms PRI/T1/BPV Maint. Threshold QPC230E0047 minor Network Manager Alarms Loss Of All Call Progress Analyzers QPC230E0048 minor Network Manager Alarms Loss Of All Speech Recognizers QPC230E0049 minor Network Manager Alarms Loss Of All MF Receivers QPC230E0050 minor Network Manager Alarms Loss Of All DTMF Receivers QPC230E0051 minor Network Manager Alarms Loss Of Announcement Capability QPC230E0052 minor Network Manager Alarms Card Failure In System QPC230E0053 fatal Network Manager Alarms Fatal Host Alarm Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 10

11 ID Severity Defined Category Defined Description QPC230E0054 critical Network Manager Alarms Critical Host Alarm QPC230E0055 major Network Manager Alarms Major Host Alarm QPC230E0056 minor Network Manager Alarms Minor Host Alarm QPC230E0057 warning Network Manager Alarms Aux-1 Host Alarm QPC230E0058 warning Network Manager Alarms Aux-2 Host Alarm QPC230E0059 minor Network Manager Alarms Port Failure In System QPC230E0060 critical Network Manager Alarms NFAS D-Channel Failure QPC230E0061 minor Network Manager Alarms Loss Of All MFCR2 Transceivers QPC230E0062 minor Network Manager Alarms T1/E1/PRI Blue Alarm QPC230E0063 minor Network Manager Alarms All Ports Deactivated Alarm QPC230E0064 minor Network Manager Alarms E1 CRC Alarm QPC230E0080 minor Redundancy Manager Alarms Update Channel Failure QPC230E0081 minor Redundancy Manager Alarms UPD DMA Output Failure QPC230E0082 minor Redundancy Manager Alarms UPD Transmit Overrun QPC230E0083 minor Redundancy Manager Alarms UPD Receive Overrun QPC230E0084 minor Redundancy Manager Alarms UPD Receive Timeout QPC230E0085 minor Redundancy Manager Alarms UPD DMA Timeout QPC230E0090 warning Redundancy Manager Alarms Printer Off-line QPC230E0091 minor Redundancy Manager Alarms Disk A Failure QPC230E0092 minor Redundancy Manager Alarms Disk C Failure QPC230E0100 fatal System Alarms Queue Overflow QPC230E0101 critical System Alarms Queue Overflow QPC230E0102 major System Alarms Queue Overflow QPC230E0103 minor System Alarms Queue Overflow QPC230E0104 warning System Alarms Queue Overflow Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 11

12 ID Severity Defined Category Defined Description QPC230E0105 fatal System Alarms Memory Allocation Failure QPC230E0106 critical System Alarms Memory Allocation Failure QPC230E0107 major System Alarms Memory Allocation Failure QPC230E0108 minor System Alarms Memory Allocation Failure QPC230E0109 warning System Alarms Memory Allocation Failure Dialer Alarms ID Severity Defined Category Defined Description QPC000D0001 info Dialer Services Services started - PDS QPC000D0002 info Dialer Services Services started - MTS QPC000D0003 info Dialer Services Services started - DB QPC000D0004 info Dialer Services Services starting - PDS QPC000D0005 info Dialer Services Services starting - MTS QPC000D0006 info Dialer Services Services starting - DB QPC000D0007 info Dialer Services Services stopping - PDS QPC000D0008 info Dialer Services Services stopping - MTS QPC000D0009 info Dialer Services Services stopping - DB QPC000D0010 info Dialer Services Services stopped - PDS QPC000D0011 info Dialer Services Services stopped - MTS QPC000D0012 info Dialer Services Services stopped - DB QPC000D0013 info Dynamic Logging Dyanamic logging log-level modified QPC000D0014 info Dynamic Logging Dyanamic logging de-initializing QPC000D0015 info Dynamic Logging Dyanamic logging initializing QPC000D0016 info System Bootup Operating system halting QPC000D0017 info System Bootup Operating system booting up Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 12

13 ID Severity Defined Category Defined Description QPC000D0018 fatal Generic Generic *** FATAL *** alarm QPC000D0019 critical Generic Generic *** CRITICAL *** alarm QPC000D0020 major Generic Generic *** MAJOR *** alarm QPC000D0021 minor Generic Generic *** MINOR *** alarm QPC000D0022 warning Generic Generic *** WARNING *** alarm QPC000D0023 warning Agent Activity Illegal agent logoff QPC000D0024 warning Agent Activity Illegal agent handset on-hook QPC000D0025 warning Licensing Dialer license in grace mode QPC000D0026 warning Licensing Dialer license expired QPC000D0027 warning Alarms Framework PDS Alarms RESET QPC000D0028 warning NOT-DEFINED NOT-DEFINED QPC000D0029 warning NOT-DEFINED NOT-DEFINED QPC000D0030 warning NOT-DEFINED NOT-DEFINED QPC000D0031 warning NOT-DEFINED NOT-DEFINED QPC000D0032 warning NOT-DEFINED NOT-DEFINED QPC000D0033 warning NOT-DEFINED NOT-DEFINED QPC000D0034 warning NOT-DEFINED NOT-DEFINED QPC000D0035 warning NOT-DEFINED NOT-DEFINED QPC000D0036 warning NOT-DEFINED NOT-DEFINED QPC000D0037 warning NOT-DEFINED NOT-DEFINED QPC000D0038 warning NOT-DEFINED NOT-DEFINED QPC000D0039 warning NOT-DEFINED NOT-DEFINED QPC000D0040 warning NOT-DEFINED NOT-DEFINED QPC000D0041 warning NOT-DEFINED NOT-DEFINED QPC000D0042 warning NOT-DEFINED NOT-DEFINED Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 13

14 ID Severity Defined Category Defined Description QPC000D0043 warning NOT-DEFINED NOT-DEFINED QPC000D0044 warning NOT-DEFINED NOT-DEFINED QPC000D0045 warning NOT-DEFINED NOT-DEFINED QPC000D0046 warning NOT-DEFINED NOT-DEFINED QPC000D0047 warning NOT-DEFINED NOT-DEFINED QPC000D0048 warning NOT-DEFINED NOT-DEFINED QPC000D0049 warning NOT-DEFINED NOT-DEFINED QPC000D0050 warning NOT-DEFINED NOT-DEFINED QPC000D0051 warning NOT-DEFINED NOT-DEFINED QPC000D0052 warning NOT-DEFINED NOT-DEFINED QPC000D0053 warning NOT-DEFINED NOT-DEFINED QPC000D0054 warning NOT-DEFINED NOT-DEFINED QPC000D0055 warning NOT-DEFINED NOT-DEFINED QPC000D0056 warning NOT-DEFINED NOT-DEFINED QPC000D0057 warning NOT-DEFINED NOT-DEFINED QPC000D0058 warning NOT-DEFINED NOT-DEFINED QPC000D0059 warning NOT-DEFINED NOT-DEFINED QPC000D0060 warning NOT-DEFINED NOT-DEFINED QPC000D0061 warning NOT-DEFINED NOT-DEFINED QPC000D0062 warning NOT-DEFINED NOT-DEFINED QPC000D0063 warning NOT-DEFINED NOT-DEFINED QPC000D0064 warning NOT-DEFINED NOT-DEFINED QPC0000ABCD info Test Alarms TEST ALARM - QPC0000ABCD QPC0000CAFE info Test Alarms TEST ALARM - QPC0000CAFE Overview of Alarms framework and SNMP in Avaya Proactive Contact 5.x 14