Mediant 5000/8000 Alarm and Performance Monitoring Guide

Transcription

1 EMS for AudioCodes Media Gateways and Servers EMS Element Management System Mediant 5000/8000 Alarm and Performance Monitoring Guide Version 6.6 Document #: LTRT-23703

2

3 Alarm and Performance Monitoring Guide Contents Contents 1 Introduction Alarms Standard Traps Cold Start Link Down Link Up Authentication Failure EMS Alarms EMS Trap Receiver Binding Error GW Connection Alarm GW Mismatch Alarm EMS Server Started Disk Space Alarm Software Replaced PM File Generated PM Polling Error Cold Start Missed GW Backup Event EMS And GW Server IP Mismatch Security Alarm Security Event Topology Update Event Topology File Event Synchronizing Alarms Event Synchronizing Active Alarms Event License Key Alarm Mediant 5000/8000 Alarms Board Failure Admin State Change Operative State Change Trunk Alarm Configuration Error Operational Info Voltage Alarm Fan Alarm Ethernet External Link Alarm Ethernet Internal Link Alarm Power Supply Alarm Push Button Alarm Board Temperature Alarm Fiber Group Link Alarm Board Diagnostics Alarm NTP Server Status Alarm Switchover Alarm Configuration Change SS7 Activity State Change SS7 Local Inhibit State Change SS7 Remote Inhibit State Change SS7 Congestion State Change Active Alarms Overflow Trap Security Alarm Power Entry Module Alarm External Interface (BITS/SETS) Alarm Timing Module Clock Alarm Timing Module Alignment Alarm Version December 2012

4 Mediant 5000 and 8000 Media Gateways Board Restart Alarm Hardware Error Alarm High Availability Alarm Security Event Line Sync Reference Clock Alarm DS3 Alarm SIP Call Resource Alarm SIP Proxy Failure Alarm SIP Overload Alarm D-Channel Status MGC Connection Alarm Alarm Throttling Limit Exceeded Board CPU Overload Alarm Trunk Activity State Change Switch Board Alarm License Key Alarm AAA Alarm PM Threshold Configuration Backdoor Event B Channel Alarm Performance Monitoring Parameters Frame: DS3 Monitoring (History) Tab: DS3 Statistics Frame: DS3 Monitoring (Real-Time) Tab: DS3 Statistics Frame: ES Board Port Monitoring (History) Tab: ES Board Port Performance Frame: ES Board Port Monitoring (Real-Time) Tab: ES Board Port Performance Frame: ES Port Monitoring (Real-Time) Tab: ES Port Frame: Fiber Group Monitoring (Real-Time) Tab: PSTN Fiber Group Frame: Media Realm Monitoring (History) Tab: Media Realm Performance Frame: Media Realm Monitoring (Real-Time) Tab: Media Realm Performance Frame: MG Background Monitoring (History) Tab: SC Performance Frame: MG Global Monitoring (Real-Time) Tab: MG Calls Performance Frame: MG History PM (Configuration) Tab: MG IP Tab: Media Realm Tab: MG VoP Call Statistics &IPSec Tab: MG Control Tab: MG MGCP Control Tab: MG H.248 Control Tab: SC Performance Tab: TP H.248 & MGCP Control Tab: TP H.248 Control Tab: TP MGCP Control Tab: TP Utilization IPSec & Streaming Tab: TP VoP Call Statistics Alarm and Performance Monitoring Guide 4 Document #: LTRT-23703

5 Alarm and Performance Monitoring Guide Contents Tab: TP SIP Tel to IP Tab: TP SIP IP to Tel Tab: SIP SRD Tab: SIP IP Group Tab: ES Port Tab: Trunk Statistics Tab: DS3 Statistics Tab: S77 Data Link Tab: SS7 Statistics Tab: ES Board Port Frame: MG Monitoring (History) Tab: MG IP Tab: MG VoP Call Statistics &IPSec Tab: MG Control Tab: MG MGCP Control Tab: MG H.248 Control Frame: MG Monitoring (Real-Time) Tab: MG IP Tab: MG Rtp Dsp Tab: MG Control Frame: MG Monitoring (Real-Time) Tab: MG IP Tab: MG Rtp Dsp Tab: MG Control Frame: MG - TPM Monitoring (History) Tab: TP H.248 & MGCP Control Tab: TP H.248 Control Tab: TP MGCP Control Tab: TP Utilization IPSec & Streaming Tab: TP VoP Call Statistics Tab: TP SIP Tel to IP Tab: TP SIP IP to Tel Frame: MG TPM Monitoring (Real-Time) Tab: TP H.248 & MGCP Control Tab: TP H.248 Control Tab: TP MGCP Control Tab: TP VoP Call Statistics Tab: TP IVR Tab: TP Conference Tab: TP Ip IPSec Dsp Frame: MG - TPM Monitoring MEGACO (History) Tab: TP H.248 & MGCP Control Tab: TP H.248 Control Tab: TP VoP Call Statistics Tab: TP Utilization IPSec & Streaming Frame: MG TPM Monitoring MEGACO (Real-Time) Tab: TP H.248 & MGCP Control Tab: TP H.248 Control Tab: TP VoP Call Statistics Tab: TP IVR Tab: TP Conference Tab: TP Ip IPSec Dsp Frame: MG - TPM Monitoring MGCP (History) Tab: TP H.248 & MGCP Control Tab: TP MGCP Control Tab: TP VoP Call Statistics Version December 2012

6 Mediant 5000 and 8000 Media Gateways Tab: TP Utilization IPSec & Streaming Frame: MG TPM Monitoring MGCP (Real-Time) Tab: TP H.248 & MGCP Control Tab: TP MGCP Control Tab: TP VoP Call Statistics Tab: TP IVR Tab: TP Conference Tab: TP IPSec Dsp Ip Frame: MG - TPM Monitoring SIP (History) Tab: TP VoP Call Statistics Tab: TP SIP Tel to IP Tab: TP SIP IP to Tel Tab: TP Utilization IPSec & Streaming Frame: MG TPM Monitoring SIP (Real-Time) Tab: TP VoP Call Statistics Tab: TP IVR Tab: TP Conference Tab: TP IPSec Dsp Ip Frame: MG - Trunk Background Monitoring (History) Tab: Trunk Utilization Tab: Trunk Errors Frame: MG - Trunk Monitoring (Real-Time) Tab: Trunk Utilization Tab: Trunk Errors Frame: MG - Trunk Monitoring (Real-Time Board Level) Tab: Trunk Performance Frame: SIP IP Group Monitoring (History) Tab: IP Group Frame: SIP SRD Monitoring (History) Tab: SIP SRD Frame: SS7 Data Link Monitoring (History) Tab: SS7 Data Link Frame: SS7 Data Link Monitoring (Real-Time) Tab: SS7 Data Link Frame: SS7 Linkset Monitoring (History) Tab: SS7 Statistics Frame: SS7 Node Monitoring (History) Tab: SS7 Node Frame: SS7 Node Monitoring (Real-Time) Tab: SS7 Node Alarm and Performance Monitoring Guide 6 Document #: LTRT-23703

7 Alarm and Performance Monitoring Guide Notices Notice This document describes the alarms and Performance Monitoring parameters for the Mediant 5000 and Mediant 8000 products. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions. Updates to this document and other documents can be viewed by registered customers at AudioCodes Inc. All rights reserved This document is subject to change without notice. Date Published: December Note: The Element Management System supports the following products: 1. Mediant 8000 Media Gateway and E-SBC 2. Mediant 5000 Media Gateway and E-SBC 3. Mediant 4000 E-SBC 4. Mediant 3000 Media Gateway and E-SBC 5. Mediant 2000 Media Gateway 6. Mediant 1000 Media Gateway 7. Mediant 1000 MSBG 8. Mediant 1000 E-SBC 9. Mediant 800 MSBG 10. Mediant 800 E-SBC 11. Mediant 600 Media Gateway 12. MediaPack Media Gateways MP-112 (FXS), MP-114 (FXS and FXO), MP-118 (FXS and FXO), MP-124 (FXS) collectively referred to as MediaPack. Trademarks AudioCodes, AC, AudioCoded, Ardito, CTI2, CTI², CTI Squared, HD VoIP, HD VoIP Sounds Better, InTouch, IPmedia, Mediant, MediaPack, NetCoder, Netrake, Nuera, Open Solutions Network, OSN, Stretto, TrunkPack, VMAS, VoicePacketizer, VoIPerfect, VoIPerfectHD, What s Inside Matters, Your Gateway To VoIP and 3GX are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners. WEEE EU Directive Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of with unsorted waste. Please contact your local recycling authority for disposal of this product. Version December 2012

8 Mediant 5000 and 8000 Media Gateways Customer Support Customer technical support and service are provided by AudioCodes Distributors, Partners, and Resellers from whom the product was purchased. For Customer support for products purchased directly from AudioCodes, contact Abbreviations and Terminology Term Trunking Gateway MG MediaPack CPE (Customer Premises Equipment) 'Frame' and 'Screen' Description Refers to the Mediant 5000 Media Gateway and Mediant 8000 Media Gateway. Refers to the Media Gateway. MediaPack Media Gateways MP-112 (FXS), MP-114 (FXS and FXO), MP-118 (FXS and FXO), MP-124 (FXS) collectively referred to as MediaPack. CPE refers to the following: Mediant 4000 E-SBC Mediant 3000 Media Gateways Mediant 2000 Media Gateways Mediant 1000, Mediant 1000 E-SBC and Mediant 1000 MSBG Mediant 800 E-SBC and Mediant 800 MSBG Mediant 600 MediaPack 11x Media Gateway Sometimes used interchangeably Alarm and Performance Monitoring Guide 8 Document #: LTRT-23703

9 Alarm and Performance Monitoring Guide Notices Related Documentation Manual Name Mediant 600 and 1000 SIP User's Manual Mediant 800 Gateway and E-SBC User's Manual Mediant 800 MSBG SIP User's Manual Mediant 1000 Gateway and E-SBC User's Manual Mediant 1000 MSBG SIP User's Manual Mediant 2000 User's Manual Mediant 3000 User's Manual Mediant 4000 E-SBC User's Manual MediaPack User's Manual Element Management System (EMS) Server Installation, Operation and Maintenance Manual Element Management System (EMS) Product Description Element Management System (EMS) OAMP Integration Guide Element Management System (EMS) User's Manual Element Management System (EMS) Online Help Mediant 5000 / 8000 Media Gateway Installation, Operation and Maintenance Manual Mediant 5000 / 8000 Media Gateway Release Notes Mediant 5000 / 8000 Media Gateway Programmer's User Manual Mediant CLI Reference Guide Mediant 5000 and Mediant 8000 Alarm and Performance Monitoring Guide Mediant 3000 TP-8410 OAM Guide Mediant 3000 TP-6310 OAM Guide Mediant 4000 E-SBC OAM Guide Mediant 2000 OAM Guide Mediant 1000 E-SBC OAM Guide Mediant 1000 MSBG OAM Guide Mediant 800 E-SBC OAM Guide Mediant 800 MSBG OAM Guide Mediant 600 OAM Guide Version December 2012

10 Mediant 5000 and 8000 Media Gateways Reader's Notes Alarm and Performance Monitoring Guide 10 Document #: LTRT-23703

11 Alarm and Performance Monitoring Guide 1. Introduction 1 Introduction This document describes the Alarms and Performance Monitoring parameters associated with the Mediant 5000 and Mediant 8000 Gateways. Version December 2012

12 Mediant 5000 and 8000 Media Gateways Reader s Notes Alarm and Performance Monitoring Guide 12 Document #: LTRT-23703

13 Alarm and Performance Monitoring Guide 2. Alarms 2 Alarms System alarms associated with the Media Gateways and can be displayed, viewed, tracked and troubleshooted in the EMS's Alarm Browser. Supported alarms / events fall into one of following categories: Standard traps: traps originated by the media gateway / server - all the standard traps are treated as events. Proprietary alarms / events: traps originated by the media gateway / server and defined in the gateway's / server's proprietary MIB. EMS alarms / events : traps originated by the EMS application and defined in the EMS proprietary MIB. To determine which traps are defined as Events refer to the 'Alarm Name' or 'Alarm Title' fields in the table. All the events are marked with the [Event] prefix. This is how events are marked in the EMS Alarms Browser and Alarms History windows. Each alarm / event described in this section includes the following information: Information Included in Each Alarm Alarm Name Alarm Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name SNMP Trap OID Corrective Action The alarm name, as it appears in the EMS Alarm Browser. Possible values of sources if applicable to a specific alarm. This value is displayed from the variable-binding tgtrapglobalssource. For the complete list of Managed Objects, refer to the Mediant 5000 / 8000 Programmers' User Manual. Possible values of severities. This value is displayed from the variablebinding tgtrapglobalsseverity. Alarm type according to ITU X.733 definition. This value is displayed from the variable-binding tgtrapglobalstype. Alarm probable cause according to ITU X.733 definition. This value is displayed from the variable-binding tgtrapglobalsprobablecause. Textual description of specific problem. This value is displayed from the variable-binding tgtrapglobalstextualdescription. The document includes a few examples of the possible values of this field. Additional information fields provided by MG application, depending on the specific scenario. These values are displayed from tgtrapglobalsadditionalinfo1, tgtrapglobalsadditionalinfo2 and tgtrapglobalsadditionalinfo3. The document includes a few examples of the possible values of this field. NOTIFICATION-TYPE Name as it appears in the MIB. NOTIFICATION-TYPE OID as it appears in the MIB. Possible corrective action when applicable. Version December 2012

14 Mediant 5000 and 8000 Media Gateways 2.1 Standard Traps Cold Start Description SNMP Alarm Cold Start SNMPv2-MIB: A coldstart trap signifies that the SNMP entity, supporting a notification originator application, is reinitializing itself and that its configuration may have been altered. coldstart SNMP OID Alarm Title Alarm Type Alarm Source Probable Cause Severity Additional Info1,2,3 Corrective Action [Event] Cold Start Communication Alarm Other Clear Link Down Description SNMP Alarm Link Down SNMPv2-MIB: A linkdown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifoperstatus object for one of its communication links is about to enter the down state from some other state (but not from the notpresent state). This other state is indicated by the included value of ifoperstatus. This trap is supported for External Ethernet Links. [Event] linkdown SNMP OID Alarm Title Alarm Type Alarm Source Probable Cause Severity Additional Info1,2,3 Corrective Action Link Down Communication Alarm Other Major Alarm and Performance Monitoring Guide 14 Document #: LTRT-23703

15 Alarm and Performance Monitoring Guide 2. Alarms Link Up Description SNMP Alarm Link Up SNMPv2-MIB: A linkup trap signifies that the SNMP entity, acting in an agent role, has detected that the ifoperstatus object for one of its communication links, left the down state and transitioned into some other state (but not into the notpresent state). This other state is indicated by the included value of ifoperstatus. This trap is supported for External Ethernet Links. [Event] linkup SNMP OID Alarm Title Alarm Type Alarm Source Probable Cause Severity Additional Info1,2,3 Corrective Action Link Up Communication Alarm Other Clear Description SNMP Alarm Link Down SNMPv2-MIB: A linkdown trap signifies that the SNMP entity, acting in an agent role, has detected that the ifoperstatus object for one of its communication links is about to enter the down state from some other state (but not from the notpresent state). This other state is indicated by the included value of ifoperstatus. This trap is supported for External Ethernet Links. [Event] linkdown SNMP OID Alarm Title Alarm Type Alarm Source Probable Cause Severity Additional Info1,2,3 Corrective Action Link Down Communication Alarm Other Major Version December 2012

16 Mediant 5000 and 8000 Media Gateways Authentication Failure Authentication Failure Description SNMP Alarm SNMPv2-MIB: An authenticationfailure trap signifies that the SNMP entity has received a protocol message that is no properly authenticated. While all implementations of SNMP entities MAY be capable of generating this trap, the snmpenableauthentraps object indicates whether this trap will be generated. [Event] authenticationfailure SNMP OID Alarm Title Authentication Failure Alarm Type Communication Alarm Alarm Source Probable Cause Other Severity Major Additional Info1,2,3 Corrective Action Alarm and Performance Monitoring Guide 16 Document #: LTRT-23703

17 Alarm and Performance Monitoring Guide 2. Alarms 2.2 EMS Alarms EMS Trap Receiver Binding Error EMS Trap Receiver Binding Error Textual Description This alarm is generated during server startup if an error occurs indicating that the SNMP trap receiver port is already taken. SNMP OID acemssnmpcannotbinderror AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity [Event] EMS Trap Receiver Binding Error Environmental Alarm EMS Server Application Subsystem Failure Critical Additional Info - Corrective Action Media Gateways Run netstats command to verify which application uses alarms reception port (by default UDP post 162). EMS application: If it's busy, check which application uses this port. If it's not freed by the EMS application, restart the EMS Server application according to the equipment installation manual. Other network management application: Change the EMS application and all managed gateways' default alarm reception ports. All the gateways managed by the EMS Version December 2012

18 Mediant 5000 and 8000 Media Gateways GW Connection Alarm GW Connection Alarm Textual Description Originated by the EMS when an SNMP Timeout occurs for the first time in the Media Gateway SNMP OID acemsnodeconnectionlostalarm AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity GW Connection Alarm Communications Alarm Media Gateway Communications Subsystem Failure Critical Additional Info - Corrective Action Media Gateways Communication problem: Try to ping the gateway to check if there is network communication. Default gateway alive: Open the network screen. Check the default gateway IP address and ping it. SNMP Community Strings: Verify that the community string defined in the EMS for the gateway match the actual gateway community strings. To check the community string, right-click on the gateway, select the 'Details' menu. Default community strings: read = public, write = private. Hardware Problem: Check that the gateway is alive according to the LEDs. Verify that the network and power cables are in place and plugged in. All the gateways managed by the EMS Alarm and Performance Monitoring Guide 18 Document #: LTRT-23703

19 Alarm and Performance Monitoring Guide 2. Alarms GW Mismatch Alarm GW Mismatch Alarm Textual Description Activated when the EMS detects a hardware, software, predefine or configuration mismatch. 1. Software Mismatch: Activated when the EMS detects a software version mismatch between the actual and the previous definition of the Media Gateway (for example, Version instead of the previously defined ). This is also the case when the new version is not defined in the Software Manager. 2. Hardware Mismatch Activated when the EMS detects a hardware mismatch between the actual and the previous definition of a Media Gateway (MP-102 became Mediant 2000). SNMP OID acemsnomismatchnodealarm AlarmTitle ItuAlarmType AlarmSource GW Mismatch Alarm Equipment Alarm Media Gateway/Software Media Gateway/Hardware Probable Cause Severity Other Clear Additional Info - Corrective Action Software Mismatch: Define the detected version in the EMS Software Manager Perform a Software Upgrade on the gateway with one of the supported versions. Hardware Mismatch: Perform remove / add a gateway from the EMS tree in order to resync EMS and the gateway status Verify in the Software Manager that an appropriate version exists for the hardware type displayed in the error message Media Gateways All the gateways managed by the EMS. Version December 2012

20 Mediant 5000 and 8000 Media Gateways EMS Server Started Textual Description EMS Server Started Originated each time the server is started or restarted (warm boot/reboot) by the EMS Watchdog Process SNMP OID acemsserverstartup AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info - Corrective Action - Media Gateways [Event] EMS Server Started Communications Alarm EMS Server Other Major All the gateways managed by the EMS Disk Space Alarm Textual Description Disk Space Alarm Originated when the EMS Server hard disk capacity is almost full. SNMP OID acemsnotenoughdiskspacealarm AlarmTitle ItuAlarmType AlarmSource Probable Cause - Disk Space Alarm Environment Alarm EMS Server Severity Critical - disk usage > 80 % Major - disk usage > 70 % Additional Info - Corrective Action Clean all unnecessary files Expand the hard disk Media Gateways All the gateways managed by the EMS. Alarm and Performance Monitoring Guide 20 Document #: LTRT-23703

21 Alarm and Performance Monitoring Guide 2. Alarms Software Replaced Textual Description Software Replaced Originated when the EMS discovers a software version replace between board versions, for example, from V to V (when both versions are managed by the EMS). Software Replace old version : <old version> new version <new version> SNMP OID acemssoftwarereplacealarm AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action Media Gateways [Event] Software Replaced Communications Alarm EMS Server Other Info If you initiated a performance measurements polling process before you initiated the software replacement process,the polling process is stopped. No action should be taken; this is an information alarm. All the gateways managed by the EMS PM File Generated Textual Description PM File Generated Originated when a PM file is generated in the EMS Server, and it can be retrieved by a higher level management system. SNMP OID acemspmfilegenerate AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action - Media Gateways [Event] PM File Generated Other EMS Server Other Info The performance summary data from<start polling interval time> to<timestempfileto> of media gateway<nodeipadd> was saved in PM file <filename>. All Gateways Version December 2012

22 Mediant 5000 and 8000 Media Gateways PM Polling Error Textual Description PM Polling Error Originated when a PM History stops collecting performance summary data from the Media Gateway. Possible reasons are: NTP synchronization lost, Connection Loss, SW Mismatch, etc. SNMP OID acemspmhistoryalarm AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action Media Gateways [Event] PM Polling Error Other EMS Server Other Minor Verify in the 'Textual Description' (see above) the reason why the PM history stopped. When the reason is 'NTP synchronization lost', verify that the Gateway and the EMS Server machine are synchronized to the same NTP server and have accurate time definitions. When the reason is 'Software Mismatch', you can stop the PM history collection until the new version is added to the Software Manager. When the reason is 'Connection Loss' between the EMS Server and the gateway, polling continues automatically when the connection is re-established; the purpose of the alarm in this case is to inform users of missing samples. Note: The alarm continues to generate every 15 minutes unless you fix the problem or manually stop PM polling of the gateway. All Gateways Alarm and Performance Monitoring Guide 22 Document #: LTRT-23703

23 Alarm and Performance Monitoring Guide 2. Alarms Cold Start Missed Textual Description Cold Start Missed Originated when the Carrier Grade Alarm System recognized that the coldstart trap is missing SNMP OID acemsnodecoldstartmissedalarm AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action Media Gateways [Event] Cold Start Missed Other Receive failure Clear All the managed Gateways GW Backup Event Textual Description GW Backup Event Originated when the MG backup file is placed into the EMS Server, and it can be retrieved by a higher level management system, or in case of an error transferring this file to the EMS Server. SNMP OID acemsmgbackupevent AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action Media Gateways [Event] GW Backup Event Other Other Indeterminate, Minor Version December 2012

24 Mediant 5000 and 8000 Media Gateways EMS And GW Server IP Mismatch Textual Description EMS And GW Server IP Mismatch Originated when a MG is added to the tree with an Ems Server IP address that is not identical to the actual EMS Server IP. SNMP OID acemsmgemsipmismatchalarm AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action [Event] EMS And GW Server IP Mismatch Other Other Indeterminate Media Gateways Mediant 5000 / Security Alarm Textual Description Security Alarm Activated when one of more Radius servers are not reachable. When none of the radius servers can be reached, Critical Severity alarm is generated SNMP OID acemssecurityalarm AlarmTitle ItuAlarmType Security Alarm Processing Error Alarm AlarmSource EMS Server / Radius <#> Probable Cause Severity Additional Info Corrective Action Media Gateways Other Minor, Major, Critical Alarm and Performance Monitoring Guide 24 Document #: LTRT-23703

25 Alarm and Performance Monitoring Guide 2. Alarms Security Event Textual Description Security Event This event is generated when a certain user is blocked after reaching a maximal number of login attempts, or when EMS failed to sync EMS and Mediant 5000 / 8000 users. SNMP OID acemssecurityevent AlarmTitle ItuAlarmType AlarmSource Probable Cause Severity Additional Info Corrective Action Media Gateways [Event] Security Event Other EMS Server / User Name, EMS Sever / User Sync Other Indeterminate Topology Update Event Textual Description Topology Update Event This event is issued by the EMS when a Gateway or Region are added/removed/updated in the EMS application, and includes the following information: Action: Add / Remove / Update GW or Region Region Name GW Name GW IP Note: For opening EMS client in the MG context, GW IP should be provided. SNMP OID acemstopologyupdateevent Alarm Title Alarm Source Severity Alarm Type Probable Cause [Event] Topology Update EMS Server Indeterminate Other Other Version December 2012

26 Mediant 5000 and 8000 Media Gateways Additional Info Additional Info 1 field will include following details: Region: X1 'X2' [GW: Y1 'Y2' 'Y3' 'Y4'] X1 = Region ID (unique identifier in the EMS data base used for region identification) X2 = Region name as it defined by EMS operator Y1 = GW ID (unique identifier in the EMS data base used for GW identification) Y2 = GW Name as it defined by EMS operator Y3 = GW IP as it defined by EMS operator Y4 = GW Type as it identified by EMS during the first connection to the GW. If the initial connection was not successful during the add operation, it will cause 'Add GW' event with Unknown GW type, and 'Update GW' event once the initial connection to the GW has been successfull. The following GWs will be supported: MP,M1K, M2K, M3K, M5K, M8K Region details will always be part of the alarm, while GW info will be displayed when the event is GW related. All the fields related to the GW will always be displayed to allow easy parsing. Examples: (Description=Add Region) Region: 7 'Test Lab' (Description=Update Region) Region: 7 'My Updated Region' (Description=Add GW) Region: 7 'My Updated Region', GW: 22 'MG14' ' ' 'Unknown', PM Polling: disabled (Description=Update GW) Region: 7 'My Updated Region', GW: 22 'My MG 15' ' ' 'M3K' (Description=Update GW) Region: 7 'My Updated Region', GW: 22 'My MG 15' ' ', PM Polling: enabled (Description=Remove GW) Region: 7 'My Updated Region', GW: 22 'My MG 15' ' ' 'M3K', Polling: enabled (Description=Remove Region) Region: 7 'My Updated Region' Corrective Action Media Gateways Alarm and Performance Monitoring Guide 26 Document #: LTRT-23703

27 Alarm and Performance Monitoring Guide 2. Alarms Topology File Event Textual Description Topology File Event This event is issued by EMS when the Topology File is Updated on the EMS Server machine. SNMP OID acemstopologyfileevent Alarm Title Alarm Source Severity Alarm Type Probable Cause Additional Info Corrective Action Media Gateways [Event] Topology File Indeterminate Other Other File Name: MGsTopologyList.csv Synchronizing Alarms Event Textual Description Synchronizing Alarms Event This event is issued when EMS is not able to retrieve the entire missing alarms list from the History table. Information regarding the number of retrieved alarms, and number of alarms EMS failed to retrieve is provided in the Additional Info field. SNMP OID acemssyncalarmevent Alarm Title Alarm Source Severity Alarm Type Probable Cause Additional Info Corrective Action Media Gateways [Event] Synchronizing Alarms EMS ServerT Indeterminate Other Other Retrieved x missing alarms, failed to get y alarms. Version December 2012

28 Mediant 5000 and 8000 Media Gateways Synchronizing Active Alarms Event Textual Description Synchronizing Active Alarms Event This event is issued when EMS is not able to perform synchronization with the History alarms table, and instead performed synchronization with the Active Alarms Table. SNMP OID acemssyncactivealarmevent Alarm Title Alarm Source Severity Alarm Type Probable Cause Additional Info Corrective Action Media Gateways [Event] Synchronizing Active Alarms Indeterminate Other Other License Key Alarm Textual Description License Key Alarm This alarm is raised when one of the following occurs:: EMS Application License is expired. EMS Application License will be expired within one month. Gateway management is not covered by the current EMS Application License (the maximum number of EMS licenses to manage this gateway has been exceeded). SNMP OID acemslicensekeyalarm Alarm Title Alarm Source Severity Alarm Type Probable Cause Additional Info Corrective Action Media Gateways EMS License Key Alarm Major/Critical Other keyexpired Alarm and Performance Monitoring Guide 28 Document #: LTRT-23703

29 Alarm and Performance Monitoring Guide 2. Alarms 2.3 Mediant 5000/8000 Alarms Board Failure Board Failure Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Board Failure Board#x Critical Other Other Example1: Board extraction from chassis is underway (release button pressed) Additional Info SNMP Trap Name Example 2: Fatal error message received from board tgtpboardfailuretrap SNMP Trap OID Corrective Action Lock the board and then unlock it to restart the board diagnostic tests. If the board successfully passes the diagnostic tests, it returns into service as a redundant board. If not and the board does not return to service, there's a hardware issue involved. Version December 2012

30 Mediant 5000 and 8000 Media Gateways Admin State Change Alarm Name Source Severity Alarm Type This trap is reported when modifying the administrative state of the MIB elements (Managed Objects). Possible states are: Lock or Unlock. Alarm Probable Cause Description Additional Info SNMP Trap Name Admin State Change Administrative State Change Exact MO Path, for example: Board#5/Trunk#7 Raise = Lock - depending on the MO Type ('lock for MGCW = Critical, for Board = Major and for Board/Trunk = Minor), Clear = Unlock (severity clear) Other Lock = underlying resource unavailable Unlock = Other Example 1: ASP Unlocked Example 2: Administrative State Change on SS7 Link moadminstatechange SNMP Trap OID Corrective Action If the new state is Locked (by the administrator), it makes the resource unavailable. To return the entity into service, activate Unlock. Alarm and Performance Monitoring Guide 30 Document #: LTRT-23703

31 Alarm and Performance Monitoring Guide 2. Alarms Operative State Change Alarm Name Source Severity Alarm Type This trap is reported when a certain media gateway resource undergoes an operational state change, reflected by its MO (Managed Object) and MIB. Possible states are: Enable, Disable Alarm Probable Cause Description Additional Info SNMP Trap Name Operative State Change Operative State Change Exact MO Path, for example: Board#5/Trunk#7 Raise = Disable - depending on the MO Type ('lock for MGW = Critical, for Board = Major and for Board/Trunk = Minor), Clear = Enabled (severity clear) Other Disabled = Underlying resource unavailable Enabled = Other Example 1: SwitchBoard disabled Example 2: SC enabled mooperativestatechange SNMP Trap OID Corrective Action If the new operative state is disabled, it means the entity is out of service. To analyze the problem, check the communication alarms for an interface entity failure. If an FRU entity has failed, check to see that the unit is firmly and correctly inserted inside the chassis. Furthermore, check the unit's LED status indicators. Refer to the Troubleshooting tables in the Installation & Operation Manual. Version December 2012

32 Mediant 5000 and 8000 Media Gateways Trunk Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Indicates events/alarms on the T1/E1 trunks in the VoIP boards: Critical: LOS, LOF Minor: AIS, RAI, RAI_CRC Major: RED Minor: BLUE, Yellow Trunk Alarm Board#X/Trunk#Y Trunk Alarm 'LOS' or 'LOF' = 'red alarm' = Major 'AIS' = 'blue alarm' = Major 'RAI' or 'RAI_CRC' = 'yellow alarm' = Minor Everything is cleared = Clear communicationsalarm degradedsignal PSTN alarm on Trunk Bitmap indicating alarms set/cleared according to the following standard: 1 dsx1noalarm 2 dsx1rcvfarendlof 4 dsx1xmtfarendlof 8 dsx1rcvais 16 dsx1xmtais 32 dsx1lossofframe 64 dsx1lossofsignal 128 dsx1loopbackstate 256 dsx1t16ais 512 dsx1rcvfarendlomf 1024 dsx1xmtfarendlomf 2048 dsx1rcvtestcode 4096 dsx1otherfailure 8192 dsx1unavailsigstate dsx1netequipoos dsx1rcvpayloadais dsx1ds2perfthreshold tgtrunkalarm SNMP Trap OID Corrective Action If the alarm is set, check its bitmap. If the loopback bit in the RcvTestCode code alarm - diagnostics is in process, lock and unlock the trunk for recovery. If the alarm is at the payload level, start looking for the problem in the MUX equipment. If the AIS alarm bit is set, check the interfaced equipment. In other cases, check the link quality. Alarm and Performance Monitoring Guide 32 Document #: LTRT-23703

33 Alarm and Performance Monitoring Guide 2. Alarms Configuration Error Alarm Name Source Severity Alarm Type This trap is issued when a configuration error or configuration inconsistency is caused by the user (via the EMS or MIB Browser). It's a general alarm. The problem description is provided in 'text' form (Additional Info). Alarm Probable Cause Description Additional Info SNMP Trap Name Configuration Error [Event] Configuration Error MO Path Indeterminate Processing error alarm Configuration or customization error Example 1: Can't load Voice Prompt File to the board. Example 2: Manually provision Switch Board's IP address through RS232 console, then repeat LOCK/UNLOCK action tgconfigurationerror SNMP Trap OID Corrective Action For a set alarm, correct the configuration using the guidelines contained in the field 'Additional Info' Operational Info Alarm Name Source Severity Alarm Type In the current version, this alarm gathers all events (not only errors) caused by actions performed by operators or caused by operation of the media gateway itself. All operational events are reported through this alarm. For example, an SC failure is reported through Operational Info. The problem description is provided in 'text' form (Additional Info). Alarm Probable Cause Description Additional Info SNMP Trap Name Operational Info [Event] Operational Info MO Path Indeterminate Processing error alarm Other Example 1: Operational Info of SS7 Link Example 2: Start LOCK action Example 1: Failed to lock SS7 Linkset - board refused to perform requested command tgoperationalinfo SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual. Version December 2012

34 Mediant 5000 and 8000 Media Gateways Voltage Alarm Alarm Name This alarm specifies the midplane voltages that are out of range. Voltage Alarm Voltage Alarm Source SAT / Voltage +12V / -12V / +5V / +3.3V / Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Warning, Minor, Major or Cleared Equipment alarm Power problem Example 1: Voltage alarm Example 2: +5V Midplane Voltage is out of nominal range (active alarm) Additional Info 1 Example: Voltage +12V passed to Warning state, Voltage = %.2f Additional Info 2 Example: Voltage +12V Ranges: Low Error %.2f; Low Warning %.2f; High Warning %.2f; High Error %.2f tgvoltagealarm SNMP Trap OID Corrective Action In the case of a set alarm, check the Alarm History. Try identify if there's a periodical or single error. In the case of a repetitive alarm, report to AudioCodes' Technical Support Call Center. Alarm and Performance Monitoring Guide 34 Document #: LTRT-23703

35 Alarm and Performance Monitoring Guide 2. Alarms Fan Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Fan Alarm Fan Alarm SAT/Fan (location description) Mediant 8000: Minor, Major or Cleared Mediant 5000: Critical when the large front fan fails. Equipment Alarm Power problem Example 1: Fan Tray 1 not all fans are working! Example 2: Fan Tray 1 is up and working! tgfanalarm SNMP Trap OID Corrective Action If the alarm is set, check the chassis air filter. Version December 2012

36 Mediant 5000 and 8000 Media Gateways Ethernet External Link Alarm Alarm Name Source Severity Alarm Type This alarm is originated when the link between the ES and the external network device has been established/has failed. Alarm Probable Cause Description Ethernet External Link Alarm Ethernet External Link Alarm Board#X/Link#Y Major for disable, Cleared for enable Communication Alarm Loss of signal Example 1: Link #1 is Down Example 2: Link #1 is Up Additional Info Additional Info 1 Example 1: MG Slots Ethernet links status:1,2 = 00, = Additional Info 2 Example 1: ES Ports (ES Leds) status:1..26 = Additional Info 1 Example 2: MG Slots Ethernet links status:1,2 = 10, = Additional Info 2 Example 2: ES Ports (ES Leds) status:1..26 = SNMP Trap Name tgethernetexternallinkalarm SNMP Trap OID Corrective Action If set, check the LED of the port and both fiber cables. Lock and unlock the port to restart the Ethernet port's auto negotiation process Alarm and Performance Monitoring Guide 36 Document #: LTRT-23703

37 Alarm and Performance Monitoring Guide 2. Alarms Ethernet Internal Link Alarm Alarm Name Source Severity Alarm Type This alarm is sent when the Ethernet link between the ES and the Media Gateway board has failed / has been established. Alarm Probable Cause Description Ethernet Internal Link Alarm Ethernet Internal Link Alarm Board#X/Link#Y Major for disable, Cleared for enable Communication Alarm Loss of signal Example 1: Link #1 is Down Example 2: Link #1 is Up Additional Info Additional Info 1 Example 1: MG Slots Ethernet links status:1,2 = 00, = Additional Info 2 Example 1: ES Ports (ES Leds) status:1..26 = Additional Info 1 Example 2: MG Slots Ethernet links status:1,2 = 10, = Additional Info 2 Example 2: ES Ports (ES Leds) status:1..26 = SNMP Trap Name tgethernetinternallinkalarm SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual. Version December 2012

38 Mediant 5000 and 8000 Media Gateways Power Supply Alarm Power Supply Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Power supply alarm SAT/PS/'location description' Major for FAIL and EXIST; Minor for DEG; Cleared Equipment alarm Power problem Example 1: Power Supply cassette 1 power failure Example 2: Power Supply cassette 1 not degraded Additional Info 1 Example 1:Current status of PS cassette: Not Exist Additional Info 2 Example 1: Status of PS cassettes: Bottom=OK, Middle=Not Exist, Top=OK Additional Info 1 Example 2: Current status of PS cassette: Exist Additional Info 2 Example 2: Status of PS cassettes: Bottom=OK, Middle=Not Exist, Top=OK tgpowersupplyalarm SNMP Trap OID Corrective Action If set, check the LED indicators of the suspected PS. If blinking or off, unplug and plug in again. Otherwise replace the unit. Alarm and Performance Monitoring Guide 38 Document #: LTRT-23703

39 Alarm and Performance Monitoring Guide 2. Alarms Push Button Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Push Button Alarm Push Button Alarm SAT/Pushbutton [Cutoff] [Switchover] Indeterminate equipmentalarm Pushbutton pressed Alarm relays manually deactivated Additional Info 1 Example: Previous state of alarm relays: minor=connect, major=connect, critical=connect Additional Info 2 Example: Previous state of alarm LEDs: minor=green, major=green, critical=green tgpushbuttonalarm SNMP Trap Corrective Action Board Temperature Alarm Alarm Name The alarm is triggered when the temperature exceeds 55 degrees Celsius and ceases when the temperature falls below 55 degrees Celsius again. Source Board # Severity Alarm Type Alarm Probable Cause Description Board Temperature Alarm Board Temperature Alarm Critical Equipment alarm Unacceptable temperature Example 1: Board temperature is out of nominal range (active alarm). Board will reset itself Example 2: Shutting down system due to fan failure and no temperature reading from TPs Additional Info Additional Info 1 Example 1: Measured temperature: 56 (deg C) Additional Info 2 Example 1:Configured threshold= 50 (deg C) SNMP Trap Name tgboardtemperaturealarm SNMP Trap OID Corrective Action If triggered, check the ambient temperature and chassis ventilation. If the ambient temperature is normal, clean the air filters and double check that all the air baffles and blank panels are correctly placed in the chassis. Finally, check for fan speed alarms to validate normal fan operation Version December 2012

40 Mediant 5000 and 8000 Media Gateways Fiber Group Link Alarm Alarm Name Source Severity Alarm Type Indicates events/alarms on the ATM - OC3 links or PSTN STM-1 links on the TP-6310 boards. Alarm Probable Cause Description Additional Info SNMP Trap Name Fiber Group Link Alarm Fiber Group Link Alarm Path indicating affected link. 'Board#X/ATM or PSTN FbrGrp#Y/ FbrLink# or TUG3# (0 fro SDH and 0,1,2 for Sonet)' For example: Board#17/PSTN FbrGrp#1/TUG3#3/TUG2#3/TU12#4 Board#17/PSTN FbrGrp#1/FbrLink-B/RS All local alarms - Major All remote alarms - Minor, or Cleared communicationsalarm degradedsignal Textual value of the Link Alarm. For example: LOF, RS-LOS, Clear. Bitmap decoded Link Alarm and the textual value of the alarm. For example: Loss of Frame, Loss of Signal. tgstm1linkalarm SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual. Alarm and Performance Monitoring Guide 40 Document #: LTRT-23703

41 Alarm and Performance Monitoring Guide 2. Alarms Board Diagnostics Alarm Alarm Name Source Severity Alarm Type Indicates that the board's health diagnostics tests have failed/solved. TP-1610/TP-6310/ES/SC health diagnostics test failed - failure alarm TP-1610/TP-6310/ES/SC health diagnostics failure cleared - for cleared alarm Alarm Probable Cause Description Additional Info SNMP Trap Name Board Diagnostics Alarm [Event] Board Diagnostics Alarm Board# Major for fails, Cleared when changed to normal Equipment failure Equipment malfunction Example 1: VoP board Health Diagnostics test passed successfully. Startup Diagnostics Additional Info 1 Example 1: Fault element (from last diagnostics test): Master TPM: CONFERENCE_CHANNEL(NotChecked) Slave TPM: CONFERENCE_CHANNEL(NotChecked) Additional Info 2 Example 1: Test Initiative: Startup tgboarddiagnosticsalarm SNMP Trap OID Corrective Action If triggered, restart the board with a lock and unlock sequence. If the alarm repeats, extract and insert the board again into the chassis. If the alarm continues, report to the service center. Version December 2012

42 Mediant 5000 and 8000 Media Gateways NTP Server Status Alarm Alarm Name Source Severity Alarm Type This alarm is issued when the connection with the NTP server is lost but Internal Clock synchronization is continuing or the NTP server has been restored. Alarm Probable Cause Description Additional Info SNMP Trap Name NTP Server Status Changed NTP Server Status Changed Warning (when the connection with the NTP server is lost; see Textual Description above) or Clear (when the NTP server has been restored; see Textual Description above) Communications alarm Other Example 1: Internal clock synchronization has been stopped Example 2: NTP server has been restored tgntpserverstatuschanged SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual Switchover Alarm Alarm Name Source Severity Alarm Type This alarm is issued when Ethernet switch/shelf Controller/TP board switchover occurs. Alarm Probable Cause Description Additional Info SNMP Trap Name Switchover Alarm GW Switchover Alarm Board# of the active board Major for fails, Cleared when changed to normal Equipment failure Equipment malfunction Example 1: Ethernet switch switchover Example 2: TP board switchover to redundant board. tggwswitchoveralarm SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual. Alarm and Performance Monitoring Guide 42 Document #: LTRT-23703

43 Alarm and Performance Monitoring Guide 2. Alarms Configuration Change Alarm Name Source Severity Alarm Type This trap is generated when a configuration change is performed on any gateway's MO. One trap is generated for each modified parameter. It includes the MO name, parameter name, new and old values. Alarm Probable Cause Description Additional Info SNMP Trap Name Configuration Change [Event] Configuration Change MO Path Indeterminate Other Other Example 1: tgtpboardname (Board FQDN) changed from none to mg1.audiocodes.com Example 2: tgtpboarddspversiontemplatenumber (DSP Load File Version) changed from 0 to 1 tgconfigurationchange SNMP Trap OID Corrective Action Refer to the Mediant 5000/8000 IO&M Manual SS7 Activity State Change Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name SS7 Activity State Change SS7 Activity State Change Board#X/SignalingLink#Y or MTP3Group#A/SS7Node#B/LinkSet#C Minor on raise, Clear on clear Other Underlying Resource Unavailable on raise, Other on clear. Activity State Change of SS7 Link (or Linkset) DEACTIVATED on raise, ACTIVATED on Clear tgss7activitystatechange SNMP Trap OID Corrective Action Perform an Activate / Deactivate action on the reported object SS7 Local Inhibit State Change SS7 Local Inhibit State Change Alarm Name SS7 Local Inhibit State Change Version December 2012

44 Mediant 5000 and 8000 Media Gateways Alarm Name SS7 Local Inhibit State Change Source Board#X/SignalingLink#Y Severity Minor on raise, Clear on clear Alarm Type Other Alarm Probable Cause Underlying Resource Unavailable on raise, Other on clear Description Local Inhibit State Change of SS7 Link Additional Info INHIBITED on raise, UNINHIBITED on clear SNMP Trap Name tgss7localinhibitstatechange SNMP Trap OID Corrective Action Perform an Inhibit / Uninhibit action on the reported Signaling Link SS7 Remote Inhibit State Change Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name SS7 Remote Inhibit State Change SS7 Remote Inhibit State Change Board#X/SignalingLink#Y Minor on raise, Clear on clear Other Underlying Resource Unavailable on raise, Other on clear Remote Inhibit State Change of SS7 Link INHIBITED on raise, UNINHIBITED on clear tgss7remoteinhibitstatechange SNMP Trap OID Corrective Action Perform an Inhibit / Uninhibit action on the far side of the reported signaling link. Alarm and Performance Monitoring Guide 44 Document #: LTRT-23703

45 Alarm and Performance Monitoring Guide 2. Alarms SS7 Congestion State Change SS7 Congestion State Change Alarm Name SS7 Congestion State Change Source Board#X/SignalingLink#Y Severity Minor on raise, Clear on clear Alarm Type Other Alarm Probable Cause Underlying Resource Unavailable on raise, Other on clear Description Congestion State Change of SS7 Link Additional Info CONGESTED on raise, UNCONGESTED on clear SNMP Trap Name tgss7congestionstatechange SNMP Trap OID Corrective Action Reduce traffic to prevent congestion on the signaling link Active Alarms Overflow Trap Alarm Name Source Severity Alarm Type This alarm is generated by the media gateway when the maximum length of the active alarm list is reached. Alarm Probable Cause Description Additional Info SNMP Trap Name Active Alarms Overflow Trap [Event] Active Alarms Overflow Trap Critical (no clear for this alarm until SC reset) Other Other Reached maximum size possible of the active alarm list tgactivealarmsoverflowtrap SNMP Trap OID Corrective Action Investigate the reason as to why so many alarms are raised. Thereafter, restart the SC application to clear this alarm. Version December 2012

46 Mediant 5000 and 8000 Media Gateways Security Alarm Alarm Name Source Severity Alarm Type In the case of any security-related event, the Security Alarm is generated. This alarm is released either by the gateway-level application or by the specific SC board. When the source is X.509, the alarm is related to X.509 certificates. When the source includes 'Board#', it means that this alarm is related to that specific board. The first alarm is related to periodic scanning of the SC file system. The second alarm is related to an SC Audit check. Alarm Probable Cause Description Additional Info SNMP Trap Name Security Alarm 1. Board# /Filesystem 2. Board#/Audit 3. X.509/MG 4. X.509/TrustedRoot 5. X.509/NTP Security Alarm 1. Major / Clear 2. Info 3. Major / Warning / Clear 4. Major / Warning / Clear 5. Info 1. Integrity Violation 2. Security Service Or Mechanism Violation 3. Time Domain Violation 4. Time Domain Violation 5. Time Domain Violation 1. Information Modification Detected 2. Application Subsystem Failure 3. Key Expired 4. Key Expired 5. Timing Problem 1. File Integrity Violation Detected 2. Audit subsystem failure 3. X.509 Certificate of Media Gateway [ is expired / is going to expire / was replaced] 4. X.509 Certificate of Trusted Root [ is expired / is going to expire / was replaced] 5. X.509 Certificates may be invalid because NTP server is currently disconnected List of the modified files. 1. OS Audit error description 2. Expires in X days (for raise alarm) 3. Expires in X days (for raise alarm) 4. None tgsecurityalarm SNMP Trap OID Alarm and Performance Monitoring Guide 46 Document #: LTRT-23703

47 Alarm and Performance Monitoring Guide 2. Alarms Corrective Action For X.509 related alarms, replace the appropriate certificate or check the NTP server status Power Entry Module Alarm Power Entry Module Alarm Alarm Name Source Power Entry Module Alarm Mediant 5000 Rev B "SAT/PEM/Bottom" "SAT/PEM/Top" Mediant 8000 Rev B "SAT/PEM/Left" "SAT/PEM/Right" Severity Alarm Type Alarm Probable Cause Description Major on raise, Clear on clear Equipment failure Equipment malfunction One of the following will appear (raise / clear): Power Entry Module 1 or 2. Power input polarity inversed / is correct Power Entry Module 1 or 2. Power input is not detected / detected Power Entry Module 1 or 2. Is not responding / responding. Additional Info SNMP Trap Name tgpowerentrymodulealarm SNMP Trap OID Corrective Action Check the power entry module's cabling and polarity. Version December 2012

48 Mediant 5000 and 8000 Media Gateways External Interface (BITS/SETS) Alarm External Interface (BITS/SETS) Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description External Interface (BITS/SETS) Alarm TimingModule# /ExternalReference# Critical: LOF, LOS and Not valid Major: AIS Clear: Normal/Locked or Normal/Not Locked Equipment failure Equipment malfunction One of the following descriptions appears: External Interface state is normal and the Timing Module is using it External Interface state is normal and the Timing Module is not using it External Interface has [LOS/ Invalid clock/ LOF/LMFA (irrelevant in T12)] alarm External Interface has AIS alarm (irrelevant in T12) Additional Info SNMP Trap Name tgexternalreferenceclockalarm SNMP Trap OID Corrective Action If set, check the status of connected external references. Alarm and Performance Monitoring Guide 48 Document #: LTRT-23703

49 Alarm and Performance Monitoring Guide 2. Alarms Timing Module Clock Alarm Timing Module Clock Alarm Alarm Name Source Timing Module Clock Alarm TimingModule# -> SystemClock/TimingModule# Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Warning: Hold-Over Minor: Free-Run Critical: Clock Error Clear: Synchronization Equipment failure -> equipmentalarm Equipment malfunction One of the following appears: Timing Module Clock synchronization state is Synchronized Timing Module Clock synchronization state is Hold-Over Timing Module Clock synchronization state is Free-Run Timing Module Clock synchronization state is Clock Previous State is displayed tgclocksynchronizationalarm SNMP Trap OID Corrective Action If set (with Timing System State change between FullActive A and B), check the status of connected external references. If there's no problem with external references, check the status of the failed board and restart the board with a lock and unlock sequence. If the alarm is not cleared, extract and insert the board again into the chassis. If the alarm continues, report to the Technical Support Call Center. Version December 2012

50 Mediant 5000 and 8000 Media Gateways Timing Module Alignment Alarm Timing Module Alignment Alarm Alarm Name Source Timing Module Alignment Alarm Board# or TimingModule# SystemClock/TimingModule# or SystemClock/ Board # Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Major: TimingModule Alignment Failure Clear: Normal Equipment failure-> equipmentalarm Equipment malfunction One of the following appears: Elements are not aligned to the active Timing Module -> All Elements are not aligned to the active Timing Module Board is not aligned to the active Timing Module Elements are aligned to the active Timing Module Intended Timing Module #, Actual Timing Module #.-> intended to sync on %v actual sync on %v tgtmalignmentalarm SNMP Trap OID Corrective Action Lock the board and then unlock it to restart the board diagnostic tests. If the board successfully passes the diagnostic tests, it returns to service as a redundant board. If the board does pass the tests and therefore not return to service, then a hardware issue is involved. Alarm and Performance Monitoring Guide 50 Document #: LTRT-23703

51 Alarm and Performance Monitoring Guide 2. Alarms Board Restart Alarm Board Restart Alarm Alarm Name Board Restart Alarm Source Board # Severity Indeterminate: Progress of board restart Warning: Minor problem during board restart Clear: Normal Alarm Type Alarm Probable Cause Description Other Other Board restart status and progress, e.g.: Board is restarting Sending file <filename> (<percent>% completed) Failed to send file <filename> Board restart is over Additional Info SNMP Trap Name tgboardrestartalarm SNMP Trap OID Corrective Action Lock and unlock the board to restart it Hardware Error Alarm Hardware Error Alarm Alarm Name Hardware Error Alarm Source Board # Severity Alarm Type Could be send at any severity Equipment Alarm Alarm Probable Cause Equipment Malfunction Description Detailed hardware error description, e.g. Hard Disk Drive Error Additional Info SNMP Trap Name tghardwareerroralarm SNMP Trap OID Corrective Action Examine operational information logs from the specific Board. If the errors occur continuously, RMA the board. Otherwise use the cleanerrors action to clear the alarm. Version December 2012

52 Mediant 5000 and 8000 Media Gateways High Availability Alarm Alarm Name Source Board # Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name High Availability Alarm High Availability Alarm Warning, Minor Processing Error Alarm Other HA Status of Board#<slot> changed to <new status> tghighavailabilityalarm SNMP Trap OID Corrective Action Use Redundancy screen to examine HA status of all VoP boards. Ensure that the redundant board is Unlocked/Enabled and properly configured to provide HOT redundancy for all available VoP boards Security Event Security Event Alarm Name Source Severity Alarm Type Security Event Board# Any Security Service Or Mechanism Violation Alarm Probable Cause Intrusion Detection Description Detailed security event description, e.g. Security IDS Event Additional Info SNMP Trap Name tgsecurityevent SNMP Trap OID Corrective Action Examine and eliminate security problem. Alarm and Performance Monitoring Guide 52 Document #: LTRT-23703

53 Alarm and Performance Monitoring Guide 2. Alarms Line Sync Reference Clock Alarm Line Sync Reference Clock Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name Line Sync Interface Clock Alarm SystemClock/[Interface#/] / Board# /Trunk# or SystemClock/Interface#/ Board# /FiberGr# or SystemClock/Interface# /Board# /T3#/Trunk# Critical: LOF, LOS and Not valid Major: AIS Clear: Normal/Locked or Normal/Not Locked Equipment failure Equipment malfunction When System Timing Mode is either in Stand Alone Board Sync or Timing Module Line Sync or Line Sync modes, one of the following descriptions appears: LineSync Interface state is normal and the Timing Module is using it LineSync Interface state is normal and the Timing Module is not using it LineSync Interface has [LOS/ Invalid clock/ LOF/LMFA] alarm LineSync Interface has AIS alarm. System Timing Mode = TimingModuleLineSync, LineSync In TimingModuleLineSync mode - Timing interface qualifier Status (- BITSync_CLOCK_STATUS). tglinesyncreferenceclockalarm SNMP Trap OID Corrective Action If set, check the status of the PSTN Line. Version December 2012

54 Mediant 5000 and 8000 Media Gateways DS3 Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause DS3 Alarm Board#/DS3# DS3 Alarm 'LOS' or 'LOF' = 'red alarm' = Major 'AIS' = 'blue alarm' = Major 'RAI' or 'RAI_CRC' = 'yellow alarm' = Minor Everything is cleared = Clear communicationsalarm degradedsignal Description PSTN alarm on Trunk Additional Info SNMP Trap Name Bitmap indicating alarms set/cleared according to the following standard: 1 dsx3noalarm No alarm present 2 dsx3rcvraifailure Receiving Yellow/Remote Alarm 4 dsx3xmitraialarm Transmitting Yellow/Remote Alarm 8 dsx3rcvais Receiving AIS failure state 16 dsx3xmitais Transmitting AIS 32 dsx3lof Receiving LOF failure state 64 dsx3los Receiving LOS failure state 128 dsx3loopbackstate Looping the received signal 256 dsx3rcvtestcode Receiving a Test Pattern 512 dsx3otherfailure Other Failure 1024 dsx3unavailsigstate Near End in Unavailable Signal State 2048 dsx3netequipoos Carrier Equipment Out of Service tgds3alarm SNMP Trap OID Corrective Action Alarm and Performance Monitoring Guide 54 Document #: LTRT-23703

55 Alarm and Performance Monitoring Guide 2. Alarms SIP Call Resource Alarm SIP Call Resource Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SIP Call Resource Alarm Board#x Major / Clear Other Other Almost no free resources for the call are available. Activated only if the parameter EnableRai is set. The threshold is determined according to parameters RAIHIGHTHRESHOLD and RAILOWTHRESHOLD. SNMP Trap Name tgsipcallresourcealarm SNMP Trap OID Corrective Action SIP Proxy Failure Alarm SIP Proxy Failure Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SIP Proxy Failure Alarm Board#X Major / Clear Other Other The SIP Proxy is not found or registration has failed. The Internal routing table may be used for routing. 'Proxy lost. Looking for another proxy' 'Proxy not found. Use internal routing' 'Proxy found. ip:a.b.c.d' 'Gatekeeper not found. ip:a.b.c.d' 'Gatekeeper not found. ip:a.b.c.d Fallback to internal routing used' 'Gatekeeper not found. ip:a.b.c.d Redundant Gatekeeper enabled' 'Gatekeeper found. ip:a.b.c.d' SNMP Trap Name tgsipproxyfailurealarm SNMP Trap OID Corrective Action Version December 2012

56 Mediant 5000 and 8000 Media Gateways SIP Overload Alarm SIP Overload Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SIP Overload Alarm Board#X Major / Clear Other Other Overload in one or more of the system's components. SNMP Trap Name tgsipoverloadalarm SNMP Trap OID Corrective Action D-Channel Status Applies to digital media gateways. D-Channel Status Description D-Channel un-established / established SNMP Alarm acdchannelstatus SNMP OID Alarm Title D-Channel Status Alarm Source Trunk no.<m> where m is the trunk number (from 0 up). Alarm Type Communications Alarm Probable Cause Communications Protocol Error Severity Minor on raise, Clear on clear Additional Info - Corrective Action - Alarm and Performance Monitoring Guide 56 Document #: LTRT-23703

57 Alarm and Performance Monitoring Guide 2. Alarms MGC Connection Alarm MGC Connection Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info MGC Connection Alarm Major / Clear Communication Alarm Out Of Service Indicates an MG loss communication with one of the provisioned Call Agents (MGC Media Gateway Controller). The Alarm message includes the call Agent IP Address. This Alarm is relevant for MEGACO control protocol. SNMP Trap Name tgmgcconnectionalarm SNMP Trap OID Corrective Action Version December 2012

58 Mediant 5000 and 8000 Media Gateways Alarm Throttling Limit Exceeded Alarm Throttling Limit Exceeded Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info Alarm Throttling Limit Exceeded Any Managed Object (MO) which issues alarms. Major / Clear Other Threshold Crossed On raise: Alarm throttling limit has exceeded. Alarm sending for this MO is blocked. On clear: Alarm throttling has returned to normal. SNMP Trap Name tgalarmthrottlinglimitexceededalarm SNMP Trap OID Corrective Action Alarm and Performance Monitoring Guide 58 Document #: LTRT-23703

59 Alarm and Performance Monitoring Guide 2. Alarms Board CPU Overload Alarm Board CPU Overload Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info Board CPU Overload Alarm. Board#x Minor / Clear Other Other This alarm is issued for TP boards. On raise: Board CPU overload On clear: Board CPU returned to normal SNMP Trap Name tgboardcpuoverloadalarm SNMP Trap OID Corrective Action Trunk Activity State Change Trunk Activity State Change Alarm Name Trunk Activity State Change Source Board#x/Trunk#y Severity major/clear Alarm Type processingerroralarm Alarm Probable Cause underlyingresourceunavailable Description Trunk is DEACTIVATED / Trunk is ACTIVATED Additional Info SNMP Trap Name tgtrunkactivitystatechange SNMP Trap OID Corrective Action Perform the Activate action to return the trunk to service. Version December 2012

60 Mediant 5000 and 8000 Media Gateways Switch Board Alarm Switch Board Alarm Alarm Name Switch Board Alarm Source Severity Alarm Type Board#x (ES Board) Minor / Major processingerroralarm Alarm Probable Cause communicationsprotocolerror / configurationorcustomizationerror / softwareerror Description Incorrect configuration on ES board Slot number mismatch on %v - board is inserted in slot %v instead of %v Failed to build ES board configuration scripts Invalid interfaces division (%v) %v does not establish physical link activity after reset %v provisioned with IP %v does not respond to PING and/or SNMP properly Failed to upload ES files to %v (%v) through FTP Additional Info SNMP Trap Name tgswitchboardalarm SNMP Trap OID Corrective Action Fix configuration and/or operational error and lock/unlock ES board to apply new configuration. Alarm and Performance Monitoring Guide 60 Document #: LTRT-23703

61 Alarm and Performance Monitoring Guide 2. Alarms License Key Alarm Alarm Name Source Severity Alarm Type Alarm Probable Cause License Key Alarm Board#x (TP board) Major processingerroralarm License Key Alarm configurationorcustomizationerror Description License key doesn't match current configuration. Additional Info SNMP Trap Name License key in redundant %v has less features than in normal %v. Detailed mismatch description. tglicensekeyalarm SNMP Trap OID Corrective Action Upload new (correct) license key file to the TP board, Version December 2012

62 Mediant 5000 and 8000 Media Gateways AAA Alarm Aaa Alarm Alarm Name Aaa Alarm Source Severity Alarm Type Alarm Probable Cause GW Minor processingerroralarm communicationsprotocolerror Description Can't connect to any AAA server Additional Info SNMP Trap Name tgaaaalarm SNMP Trap OID Corrective Action Bring AAA servers into service. Ensure that provisioned AAA server credentials (IP addresses and password) are correct. Ensure that network communication between Media Gateway and AAA servers is not blocked by some network device (e.g. firewall) PM Threshold Alarm Name Source Severity Alarm Type Alarm Probable Cause Description Additional Info SNMP Trap Name PM Threshold Alarm PM Threshold Alarm Any History PM MO (e.g. moss7datalinkhistorypm) Configurable by user (as part of PM threshold configuration). processingerroralarm thresholdcrossed PM <name> on <MO name> is out of valid range. PM <name> on <MO name> returned to the valid range. Value <value>. Threshold <threshold>. <user-configurable text>. tgpmthresholdalarm SNMP Trap OID Corrective Action Make specific PM fall below the threshold value (specific action is PM-dependent). Alarm and Performance Monitoring Guide 62 Document #: LTRT-23703

63 Alarm and Performance Monitoring Guide 2. Alarms Configuration Backdoor Event Configuration Backdoor Event Alarm Name Configuration Backdoor Event Source Board#x (TP board) Severity indeterminate Alarm Type other Alarm Probable Cause other Description Board#%v is unlocked with ConfigurationBackdoor Additional Info SNMP Trap Name tgconfigurationbackdooralarm SNMP Trap OID Corrective Action Adding new attribute configuration to the TP board B Channel Alarm B Channel Alarm Alarm Name B Channel Alarm Source Board#x/Trunk#y/B-Channel#x Severity Minor / cleared Alarm Type communicationsalarm Alarm Probable Cause outofservice Description B-Channel Alarm Additional Info %v (B-channel is Out Of Service / B-channel is In Service ) SNMP Trap Name tgbchannelstatusalarm SNMP Trap OID Corrective Action Trunk sends B-channel alarm status. Version December 2012

64 Mediant 5000 and 8000 Media Gateways Reader's Notes Alarm and Performance Monitoring Guide 64 Document #: LTRT-23703

65 Alarm and Performance Monitoring Guide 3. Performance Monitoring Parameters 3 Performance Monitoring Parameters Customers are often faced with a complex VoIP network with little or no information on the status and capacities of each component in it. PM helps the system architect design a better network. PM helps operators discover malfunctioning devices before they start causing a problem on the production network. The system provides two types of performance measurements: Gauges: Gauges represent the current state of a PM parameter in the system. Gauges, unlike counters, can decrease in value, and like counters, can increase. s: s always increase in value and are cumulative. s, unlike gauges, never decrease in value unless the system is reset. The counters are then zeroed. Performance measurements are available for the EMS or for a 3rd party performance monitoring system through an SNMP interface. These measurements can be polled at scheduled intervals by an external poller or utility in a media server or another off-device system. PM measurements can be divided into two main groups: Real-Time PM Measurements - supply the current value of the PM entity. When requested, the entity is sampled and the current value is received. History PM Measurements - supply statistical data of the PM entity during the last interval period. These measurements include the Average, Minimum and Maximum values of the entity during the last The default interval length is 15 minutes. Figure 1: History PM Measurements History Performance is measured in a constant time interval of 15 minutes to which all elements in the network are synchronized. Intervals commence precisely every 15 minutes, for example, 12:00:00, 12:15:00, 12:30:00, 12:45:00, etc. This allows synchronization of several management systems to the same interval time frame. Note that the first interval after start-up is always shorter (in the example above, the first interval only lasts 6 minutes - so that a new interval can start exactly on the 15 minute interval, in this case 11:30:00). During the initial start-up interval i.e. 6 minutes in the example above, polling is not performed. Version December 2012