Cisco Cisco Unified Customer Voice Portal 10.5(1)
7-3
Cisco Customer Voice Portal (CVP) Release 3.0(0) Configuration and Administration Guide
Chapter 7 Alarm Handling and Logging
Overview: The Standalone Distributed Diagnostics and Services Network (SDDSN)
•
Configuring SDDSN in the Application Server. For more information, see
Note
For more information about VB Admin, see
For more
information about Application Administration, see
Understanding SDDSN Retry Settings
Another SDDSN setting that may need to be configured on the Application Server and Voice Browser is
SDDSN Ascending Retries. This setting relates to how the components communicate with instances.
SDDSN Ascending Retries. This setting relates to how the components communicate with instances.
SDDSN can have two instances for redundancy. When the Voice Browser and Application Server report
alarms to SDDSN, they try one instance and—if unable to connect—then the second SDDSN instance.
Each time the retry timer expires, the Voice Browser or Application Server attempts to connect again.
alarms to SDDSN, they try one instance and—if unable to connect—then the second SDDSN instance.
Each time the retry timer expires, the Voice Browser or Application Server attempts to connect again.
The retries follow a geometric growth for the time between retries. For the Voice Browser, the upper time
limit for retries is defined through the SetAscendRetries command; for the Application Server, this limit
is defined through the SDDSN Ascending Retries field on the Engine Administration’s Log
Configuration page.
limit for retries is defined through the SetAscendRetries command; for the Application Server, this limit
is defined through the SDDSN Ascending Retries field on the Engine Administration’s Log
Configuration page.
In both cases, a the default value is 5. This means, when both SDDSN instances are having problems,
the Voice Browser/Application Server will retry after 1 minute, then 4 (2*2) minutes, 9 (3*3) minutes,
16 (4*4) minutes, then 25 (5*5) minutes. Since the default value is 5, all subsequent retry attempts will
be spaced 25 minutes apart.
the Voice Browser/Application Server will retry after 1 minute, then 4 (2*2) minutes, 9 (3*3) minutes,
16 (4*4) minutes, then 25 (5*5) minutes. Since the default value is 5, all subsequent retry attempts will
be spaced 25 minutes apart.
For example if you changed SetAscendRetries command/SDDSN Ascending Retries field to 4, the
Voice Browser/Application Server will retry after 1 minute, 4 minutes, 9 minutes, 16 minutes and every
16 minutes—the upper limit of 4*4—thereafter.
Voice Browser/Application Server will retry after 1 minute, 4 minutes, 9 minutes, 16 minutes and every
16 minutes—the upper limit of 4*4—thereafter.
Event Management System (EMS)
The NAM/ICM Event Management System (EMS) logs events from processes throughout the system
and stores the event data. For example, a typical EMS event might record that a system component has
been disconnected.
and stores the event data. For example, a typical EMS event might record that a system component has
been disconnected.
The EMS also saves events from individual processes, such as the Voice Browser or Application Server,
in per-process log files on the local computer. These files document events for a specific process running
on that specific computer.
in per-process log files on the local computer. These files document events for a specific process running
on that specific computer.
EMS funnels error messages and log entries into a log file ending with the suffix .ems. This is a file of
Event Source Records (ESRs). The ESR are the readable strings themselves; to view the events, you must
use the dumplog utility.
Event Source Records (ESRs). The ESR are the readable strings themselves; to view the events, you must
use the dumplog utility.
Note
Instructions for using the dumplog utility are given later in this chapter.