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

62 Chapter 2 Fault Management System

P0609330 2.0

Event sources

All BCM components can be a source of BCM event information. An event is defined as a

notification of an error or anomaly in operation, or a condition that may lead to an error or

anomaly. The terms “event” and “alarm” are used interchangeably in the BCM environment.

Refer to Figure 16 when reviewing the following description:

• BCM events derived from the operating system, drivers, services and applications, are

captured in the NT Event Log (item 5).

• The BCM events are recorded in the BCM Alarm database (item 7) and displayed as alarms in

the Alarm Banner (item 8). See also Figure 18.

• The BCM events, or alarms, can also be made available to remote fault management systems

as SNMP traps (item 10).

MSC events

Core telephony services, which run on the Media Services Card (MSC) (item 1 of Figure 16)

represent one of the major BCM components that act as a source of events. Referred to as MSC

events or core telephony events, these events are assigned an MSC event id and an event priority

from P1 to P9, where P9 is the most severe. If an MSC event is serious enough to be considered an

alarm, the system also assigns the MSC event an MSC alarm id.

Refer to Figure 16 when reviewing the following description:

• All core telephony (MSC) events, including telephony alarms, are recorded in a set of core

system telephony logs (items 2 & 3).

• All core telephony (MSC) events designated as alarms are also written into the NT Event log

(item 4). In most cases, the MSC alarm id, assigned by the core telephony (MSC) service, is

re-used as the NT Event ID.

• Some of the core telephony (MSC) events, which are not alarms, are also written into the NT

Event log, primarily those MSC events of priority P5 and higher (item 4). MSC events of

priority P4 and lower can only be seen in the MSC logs - see “MSC (core telephony) logs” on

page 63). MSC events that are visible to the alarm service can also generate SNMP traps.

Due to the interaction between the MSC system and the BCM alarm system, an event in the NT

event database which originates from the core telephony services (MSC) will have an NT event

ID. An event will also have an associated core telephony (MSC) services event ID, and possibly

also an MSC alarm id.

MSC event and alarm conditions

• Software errors that do not affect system operation

• Software errors that affect system operation: feature failure dropped calls, or system resets.

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

Sem comentários

Avaya BCM Management Guia do Utilizador Página 66