|
Server
|
From
the drop-down list, choose the server (node) for which you want to configure
the alarm; then, click
Go.
|
|
Service Group
|
Cisco Unity
Connection supports only the following service groups: Database and
Admin Services, Performance and Monitoring Services, Backup and Restore
Services, System Services, and Platform Services.
From
the drop-down list, choose the category of services, for example, Database and
Admin Services, for which you want to configure the alarm; then, click
Go.
|
|
Service
|
From
the Service drop-down list, choose the service for which you want to configure
the alarm; then, click
Go.
Only
services that support the service group and your configuration display.
| Tip
|
The
drop-down list displays both active and inactive services.
|
|
|
Cisco Unified Communications Manager and Cisco
Cisco Unified Communications Manager IM and Presence Service only:
Apply to All Nodes
|
To
apply the alarm settings for the service to all nodes in a cluster, check the
check box.
|
|
Enable Alarm for Local Syslogs
|
The
SysLog viewer serves as the alarm destination. The program logs errors in the
Application Logs within SysLog Viewer and provides a description of the alarm
and a recommended action. You can access the SysLog Viewer from the
Cisco Unified Real-Time
Monitoring Tool.
For
information on viewing logs with the SysLog Viewer, refer to the
Cisco
Unified Real-Time Monitoring Tool Administration Guide.
|
|
Enable Alarm for Remote Syslogs
|
The
Syslog file serves as the alarm destination. Check this check box to enable the
Syslog messages to be stored on a Syslog server and to specify the Syslog
server name. If this destination is enabled and no server name is specified,
Cisco Unified
Serviceability does not send the Syslog messages.
The
configured AMC primary and failover collectors use the remote syslog settings.
The remote syslog settings used by the collectors are those configured on the
respective individual nodes.
If
the remote syslog is only configured on AMC primary collector without
configuring remote syslog on AMC failover collector and failover occurs in AMC
primary collector, then no remote syslogs will be generated.
You
must configure exactly the same settings on all nodes, to send the remote
syslog alarms to the same remote syslog server.
When
failover occurs in AMC controller or when the collector configuration changes
to a different node, the remote syslog settings on a backup or newly configured
node is used.
To
prevent too many alarms flooding the system, you can check the
Exclude End Point Alarms check box. This ensures
that the endpoint phone-related events get logged into a separate file.
Exclude End Point Alarms
check box is displayed only for the CallManager services, and is not checked by
default. You need to check the
Apply to All Nodes also, when you check this check
box. The configuration options for endpoint alarms are listed in Alarm
configuration settings.
| Tip
|
Do not
specify a Cisco
Cisco Unified Communications Manager or a Cisco
Cisco Unified Communications Manager IM and Presence Service node as
the destination because the node does not accept syslog messages from another
node.
|
|
|
Remote Syslog
Servers
|
In each of the
Server Name 1, Server Name 2, Server Name 3, Server Name 4, and Server Name 5
fields, enter the name or IP address of the remote syslog server that you want
to use to accept syslog messages. For example, if you want to send the alarms
to Cisco Unified Operations Manager, specify the Cisco Unified Operations
Manager as the server name.
| Tip
|
Do not
specify a Cisco
Cisco Unified Communications Manager or a Cisco
Cisco Unified Communications Manager IM and Presence Service node as
the destination because the node does not accept syslog messages from another
node.
|
|
|
Enable Alarm for SDI Trace
|
The
SDI trace library serves as the alarm destination.
To
log alarms, check this check box and check the Trace On check box in the Trace
Configuration window for the chosen service. For information on configuring
settings in the Trace Configuration window in
Cisco Unified
Serviceability, see Set up trace parameters.
|
|
Cisco Unified Communications Manager and
Cisco Unified Communications Manager BE only:
Enable Alarm for SDL Trace
|
The SDL trace library serves as the alarm destination. This
destination applies only to the Cisco CallManager service and the CTIManager
service. Configure this alarm destination by using Trace SDL configuration. To
log alarms in the SDL trace log file, check this check box and check the Trace
On check box in the Trace Configuration window for the chosen service. For
information on configuring settings in the Trace Configuration window in
Cisco Unified
Serviceability, see the Set up trace parameters.
|
|
Alarm Event Level
|
From the drop-down list, choose one of the following options:
- Emergency
-
This
level designates system as unusable.
- Alert
-
This
level indicates that immediate action is needed.
- Critical
-
The
system detects a critical condition.
- Error
-
This
level signifies that error condition exists.
- Warning
-
This
level indicates that a warning condition is detected.
- Notice
-
This
level designates a normal but significant condition.
- Informational
-
This
level designates information messages only.
- Debug
-
This
level designates detailed event information that Cisco Technical Assistance
Center engineers use for debugging.
|