Avaya G860, Installing And Operating

Page: 177 / 214

Issue 1 October 2007 177
16. Diagnostics & Troubleshooting
System User’s Manual , Document #: LTRT-910xx, and EMS Alarm Guide , Document
#: LTRT 946xx .
16.5 Log Utilities in Avaya G860 Media Gateway
The Avaya G860 Media Gateway Media Gateway supports Log utilities for different
software and hardware components in the system. The main purpose of these
software-generated logs is troubleshooting and are instrumental for Avaya technical
support and field engineers to assist you.
All of the Avaya G860 Media Gateway logs reside at the System Controller (SC) board
level (local). There are logs collected for the redundant SC board as well. All log
information is stored on the local hard disk of each SC board.
The logs are active by default. (There is no need for you to activate it manually.) In
some situations, a technical support person may ask you to increase the level of a
certain log to product more information about a specific occurrence.
16.5.1 Log Areas
The following entities are logged on the SC board (in directories labeled,
Project/bin/logs# ):
16.5.1.1 Customer’s Log Area
„
‘trap’ – the directory that logs all the information provided via SNMP traps. It includes
the information about system’s maintenance activity, changes in certain components
state, chassis activities and health (e.g., chassis over-heating, Media Gateway board
switch-over, trunks or other system’s elements failure, etc.). This is the only type of log
information that should be normally and directly accessed by user in order to obtain
system’s operational information. For more information on the trap log, refer to the
EMS Alarm Guide - Document # LTRT-946xx .
16.5.1.2 Avaya Technical Support Log Areas
„
‘alarm’ – the directory that logs all of the activities at the chassis management level
(e.g., power supplier, fans, etc.)
„
‘boardsLog’ - this directory includes sub-directories for each Media Gateway board in
the Avaya G860 Media Gateway chassis. It includes all of the information set from a
certain board. It is parallel to the syslog information provided by board.
„
‘bootp’ – the directory that logs information regarding the BootP process at the SC
board (for the SC board’s booting and initialization)
„
‘core’ – the directory that logs information regarding the main configuration and MOs
handling activities. It is responsible for the ‘core’ process of the SC software.
„
‘hbg’ – the directory that logs information regarding the Heartbeat generator activities
(toward the redundant, standby SC board)
„
‘hbm’ – the directory that logs information regarding the Heartbeat monitor activities
(Heartbeats from redundant, standby SC board and chassis resident Media Gateway
boards)
„
‘pstnTrace’ - the directory that logs recorded PSTN traces for certain calls