Avaya BCM Management Guia do Utilizador descarregar pdf (Página 67)

Chapter 2 Fault Management System 63

Business Communications Manager - Management User Guide

• Events caused by hardware-related problems, but are not of sufficient severity as to be marked

as an alarm condition. Installers, however, may need to know of these events as they may

indicate a hardware problem (e.g., bad messages received on a signalling channel) or a PSTN-

or private network- related problem (e.g., no battery feed, no dial tone, invalid disconnect

sequence).

• Events that are not of sufficient severity as to marked as an alarm condition, but where the

problem is related to system limits affected by system usage patterns, administration, or lack

of resource. Examples are running out of autodialler/speed dialer bins, LHD nodes, DTMF/

dial tone receivers. These events may not be apparent to users, but a degraded level of service

will likely result.

• Information events, concerning a user action, typically in **ADMIN or **CONFIG. (e.g.,

admin log cleared, user attempted to enter **ADMIN with wrong password).

• Permanent, service affecting events that an installer can rectify. Typically these will also be

alarms, but that is not a prerequisite. An example of the latter is the defaulting of a portion of

administration, without a cold start (installer action: re-administer the data).

MSC (core telephony) logs

Refer to Figure 16 when reviewing the following description:

• MSC logs (item 3) are maintained on the Media Services card, MSC, which is the telephony

side of the Business Communications Manager system.

• The MSC logs are actually a set of three logs, the MSC System Test, MSC System

Administration, and MSC Network Event log. These logs capture all of the core telephony

(MSC) system events, (including alarms). For further information, refer to “Media service

card (core telephony) logs” on page 309.

• Note that core telephony (MSC) events, designated as MSC alarms, are sent to the NT Event

events of priority 5 (P5) and higher are sent to the NT Event log (item 4). MSC events are

shown in the BCM alarms under component id “Voice Software”.

NT Event log database

When the alarm service is enabled, all BCM alarms are recorded into the NT Event Log (item 5 of

Figure 16).

For further information about how to view NT Event Logs, see “Obtaining NT Event Logs from

Archlog” on page 327.

Alarm manager

Refer to Figure 16 when reviewing the following description:

• The system forwards events from the NT Event log to the Alarm Manager.

• The Alarm Manager applies system filters based on configuration inputs.

1 2 ... 62 63 64 65 66 67 68 69 70 71 72 ... 487 488

Sem comentários

Avaya BCM Management Guia do Utilizador Página 67