AudioCodes Mediant 3000 TP-6310, Руководство по мониторингу работы и системе оповещения

Страница: 82 / 158

Performance Monitoring and Alarms 82 Document #: LTRT-32111
Mediant 3000 with TP-6310
3.2.10 PM Polling Error
PM Polling Error
Textual Description Originated when a PM History stops collecting performance summary
data from MG. Possible reasons are: NTP synchronization lost,
Connection Loss, SW Mismatch, etc..
SNMP OID acEMSPmHistoryAlarm - 1.3.6.1.4.1.5003.9.20.3.2.0.19
AlarmTitle [Event] PM Polling Error
ItuAlarmType Other
AlarmSource EMS Server
Probable Cause Other
Severity Minor
Additional Info
Corrective Action 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 activate every 15 minutes unless you fix
the problem or manually stop PM polling of the Gateway.
Media Gateways
All Gateways