In this document the Avaya G860 Media Gateway corresponds
to the Mediant 5000. Only information that applies to the
Mediant 5000 a
lies to the Avaya G860 Media Gateway.
Notice
This docume nt describes and explain s the use of the Element Management System (EMS ),
available from AudioCodes. 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 the accuracy of printed material after the Date
Published nor can it accept responsibility for errors or omiss ions. Updates to this document
and other documents can be viewed and downloaded by registered Technical Support
customers at www.AudioCodes.com.
This document is subject to change without notice.
Refer to the current release notes that may be included with your documentation or hardware
delivery.
Date Published: Feb-14-2006 Date Printed: Feb-15-2006
EMS Alarm Guide General
Tip: When viewing this manual on CD, Web site or on any other electronic copy,
all cross-references are hyperlinked. Click on the page or section numbers
(shown in blue) to reach the individual cross-referenced item directly. To
Note: The Element Management System supports the following products:
return back to the point from where you accessed the cross-reference, press
Alt + Å .
1. Mediant 5000 Media Gateway and Mediant 8000 Media Gateway
2. Mediant 3000 Media Gateway
3. IPmedia 3000 Media Server
4. Mediant 2000 Media Gateway
5. IPmedia 2000 Media Server
6. Mediant 1000 Media Gateway
7. MediaPack.
Trademarks
AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant,
MediaPack, MP-MLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect, are
trademarks or registered trademarks of AudioCodes Limited.
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 support@AudioCodes.com.
Abbreviations and Terminology
Each abbreviation, unless widely used, is spelled out in full when first used. Only industrystandard terms are used throughout this manual. Hexadecimal notation is indicated by 0x
preceding the number.
When the term ‘Trunking Gateway’ is used in this manual, it refers to the Mediant 5000
Media Gateway and Mediant 8000 Media Gateway.
When ‘MG’ is used in this manual, it refers to ‘media gateway’.
MediaPack collectively refers to the MP-102 (FXS), MP-104 (FXS and FXO), MP-108 (FXS
and FXO), MP-112 (FXS), MP-114 (FXS), MP-118 (FXS) and MP-124 (FXS).
The term 'DS3' is synonymous with the term 'T3'.
Version 3.2 3 October 2007
EMS
Related Documentation
Manual Name
Mediant 5000 / 8000 Media Gateway Installation, Operation & Maintenance Manual
Mediant 5000 / 8000 Media Gateway Release Notes
Mediant 3000 User’s Manual
IPmedia 3000 Media Server User’s Manual
Mediant 2000 User’s Manual
IPmedia 2000 Media Server User’s Manual
MediaPack MGCP-MEGACO User’s Manual
MediaPack User’s Manual
Element Management System (EMS) Server Installation & Maintenance Manual
Element Management System (EMS) Product Description
Element Management System (EMS) Release Notes
Element Management System (EMS) Online Help
Mediant 5000 / 8000 Media Gateway Programmer's User Manual
EMS Parameter Guide for the Mediant 5000 and Mediant 8000 Gateways
EMS Parameter Guide for Mediant 1000, Mediant 2000, Mediant 3000, IPmedia 3000 and IPmedia
In the Software Manager, check that the Call Agent version is defined.
If not, define it.
Verify that an SNMP connection between the EMS and gateway
exists, that community strings are valid (check gateway details from
the EMS tree).
Check product compat ability: Call Agent Board should have
sysDescr field compatible to Mediant 5000 / 8000 sysDescr.
Mediant 5000 / 8000 Broadband Access Gateways
Version 3.2 11 October 2007
EMS
1.3 Connection Lost
Table 1-3: Connection Lost
Textual Description Originated by the EMS when an SNMP Timeout occurs for the first time
in the Media Gateway
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.3
Connection Lost
Communications Alarm
Media Gateway
Communications Subsystem Failure
Critical
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 network and power cables are in place and plugged
in.
All the gateways managed by the EMS
EMS Alarm Guide 12 Document #: 94602
EMS Alarm Guide 1. EMS Alarms
1.4 Connection Established
Table 1-4: Connection Established
Textual Description
Originated by the EMS when a previously lost Media Gateway
connection is re- es tablished.
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.4
Connection Lost
Communications Alarm
Media Gateway
Communications Subsystem Failur e
Critical
-
All the gateways managed by the EMS
1.5 Software Mismatch
Table 1-5: Software Mismatch
Textual Description
Generated when the EMS detects a software version mismatch
between the actual and the previous definition of the Media Gateway
(for example, Version 4.0.353 instead of the previously defined
4.0.278). This is also in the case that the new version is not defined in
the Software Manager.
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
1.3.6.1.4.1.5003.9.20.3.2.0.5
Software Mismatch
Equipment Alarm
Media Gateway
Version Mismatch
Major
-
Define the detected version in the EMS Software Manager
Perform a Software Upgrade on the gateway with one of the
supported v er sions.
Media Gateways
All gateways
Version 3.2 13 October 2007
EMS
1.6 Hardware Mismatch
Table 1-6: Hardware Mismatch
Textual Description Generated 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
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.6
Hardware Mismatch
Equipment Alarm
Media Gateway
Equipment Malfunction
Major
-
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 presented in the error message.
All the gateways managed by the EMS.
EMS Alarm Guide 14 Document #: 94602
EMS Alarm Guide 1. EMS Alarms
1.7 Configuration Mismatch
Table 1-7: Configuration Mismatch
Textual Description
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
Generated when the EMS detects a configuration mismatch between
the actual parameter values provisioned and previous parameter
values provisioned.
1.3.6.1.4.1.5003.9.20.3.2.0.7
Configuration Mismatch
Equipment Alarm
Media Gateway
Software Error
Warning
-
Run Configuration Verification command in order to compare EMS
configuration and actual MG configuration:
MG configuration is wrong: use configuration download to
update MG with correct configuration saved in EMS database.
MG is correct, EMS is not updated: use configuration upload to
save a correct MG configuration in the EMS database.
Check the Actions Journal for recent updates of the gateway.
Textual Description Originated by the EMS, when the user performs a MediaPack media
gateway predefinition in the EMS.
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.8
Predefine Mismatch
Equipment Alarm
Media Gateway
Other
Info
No action should be taken; this is an information alarm only.
MediaPack
1.9 Mismatch Cleared
Table 1-9: Mismatch Cleared
Textual Description
SNMP OID
AlarmTitle
Generated when the EMS detects that a hardware, software, predefine
or configuration mismatch is cleared.
1.3.6.1.4.1.5003.9.20.3.2.0.9
EMS Server Started
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Equipment Alarm
Media Gateway
Other
Clear
Clears all mismatched alarms previously originated by the EMS on a
certain gateway.
Media Gateways
All the gateways managed by the EMS.
EMS Alarm Guide 16 Document #: 94602
EMS Alarm Guide 1. EMS Alarms
1.10 Changed MIB Version
Table 1-10: Changed MIB Version
Textual Description
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
Originated when a major software version change is detected by the
EMS.
1.3.6.1.4.1.5003.9.20.3.2.0.10
Change MIB Version
Equipment Alarm
Media Gateway
Version Mismatch
Info
-
All the gateways managed by the EMS.
Version 3.2 17 October 2007
EMS
1.11 EMS Server Started
Table 1-11: EMS Server Started
Textual Description Originated each time the server is started or restarted (warm
boot/reboot) by the EMS Watchdog Process
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.11
EMS Server Started
Communications Alarm
EMS Server
Other
Major
-
All the gateways managed by the EMS.
1.12 Insufficient Disk Space
Table 1-12: Insufficient Disk Space
Textual Description
SNMP OID
AlarmTitle
ItuAlarmType
Originated when the EMS server hard disk capacity is almost full.
1.3.6.1.4.1.5003.9.20.3.2.0.12
Disk Space Alarm
Environment Alarm
AlarmSource
Probable Cause
Severity
EMS Server
Critical - disk usage > 80 %
Major - disk usage > 70 %
Additional Info
Corrective Action
Media Gateways
-
Clean all unnecessary files
Expand the hard disk
All the gateways managed by the EMS.
EMS Alarm Guide 18 Document #: 94602
EMS Alarm Guide 1. EMS Alarms
1.13 Software Upgraded
Table 1-13: Software Upgraded
Textual Description
Indicates Mediant 5000 / 8000 Online Software Upgrade procedures
and version information.
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.13
EMS Server Started
Equipment Alarm
EMS Server
Version Mismatch
Info
Started / Fi nished / Aborte d
No action should be taken; this is an information alarm
Mediant 5000 / 8000
1.14 Software Replaced
Table 1-14: Software Replaced
Textual Description
Originates when the EMS discovers a software version replace
between boa rd versions, for example, from V4.6.009.004 to
V4.6.152.0 0 3 ( wh en b ot h ve rs i ons are manage d by t he E MS).
Software Replace old version : <old version> new version <new
version>
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
1.3.6.1.4.1.5003.9.20.3.2.0.14
EMS Server Started
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.
Corrective Action
Media Gateways
No action should be taken; this is an information alarm.
All the gateways managed by the EMS.
Version 3.2 19 October 2007
EMS
1.15 Hardware Replaced
Table 1-15: Hardware Replaced
Textual Description Originates when the EMS discovers a different gateway (according to
the MAC address) to what was initially defined, while the Hardware
Type remains the same.
Hardware Replace is discovered by the MAC address and performed
during Board Started trap.
SNMP OID
AlarmTitle
ItuAlarmType
AlarmSource
Probable Cause
Severity
Additional Info
Corrective Action
Media Gateways
1.3.6.1.4.1.5003.9.20.3.2.0.15
Hardware Replacement Alarm
Equipment Alarm
Media Gateway
Other
Major