The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco VVB Serviceability provides configuration details for the following functionality:
Configuring alarms for local and remote Syslogs.
Configuration trace settings for VVB components. After these settings are enabled, you can collect and view trace information using the Real-Time Monitoring Tool (RTMT).
Configuring and managing log profiles for different VVB components.
Managing and controlling network services.
Setting parameters for different platform services.
Setting Java Virtual Machine (JVM) parameters for different VVB services to collect thread and memory traces.
Log in to Cisco VVB with the application user credentials configured during installation.
To access Cisco VVB Serviceability, log in to Cisco VVB Serviceability page using the following URL format: https://<server name or IP address>/uccxservice/.
You can view alarm information by using the SysLog Viewer in Cisco Unified Real-Time Monitoring Tool (RTMT). See "Real-Time Monitoring Tool" section for detailed information on how to view alarm information.
Use the Alarm Configuration web page in Cisco VVB Serviceability to view and configure alarm server settings for different Cisco VVB components.
Note | To find more information on the Alarm messages in the system, use Alarm Definition page in Cisco Unified Serviceability. |
Use the Alarm Configuration page to modify alarm settings.
Setting |
Description |
---|---|
Enable Alarm for Local Syslogs |
Enables the alarms to be stored as syslog messages locally. This setting can be viewed in the Application logs within Syslog viewer from the RTMT tool. For information about viewing logs with the SysLog Viewer, see "Real-Time Monitoring Tool" topic. |
Enable Alarm for Remote Syslogs |
Enable the alarm messages to be sent to the configured Syslog server. Server Name field - Provide the IP / hostname of the Syslog server to which the system should send the alarm messages. |
Alarm Event Level |
Alarm event level messages range from severity 0 (most severe) to severity 7 (least severe). See the description below for each alarm event level option. When you choose a severity level, all messages of that severity level and higher are sent. For example, if you choose ERROR_ALARM (Severity 3), all messages of severity 3, severity 2, severity 1, and severity 0 are sent. The default is INFORMATIONAL_ALARM (Severity 6), which will send messages on all severity levels starting from 6 to severity level 0.
|
A trace file is a log file that records activity from the Cisco VVB components. Trace files provide detailed information about specific errors and help you troubleshoot the errors.
The Cisco VVB system also generates information about all threads that are running in the system. This information is stored in the thread dump file and is useful for troubleshooting.
The component trace file contains information about each component. You can create a trace file for any of the following Cisco VVB components:
To update trace file information and to activate and deactivate logging, follow this procedure:
A trace file that records all information for a component, such as the Cisco VVB Engine, can become large and difficult to read. To help you manage the trace file, the Cisco VVB system lets you specify the subfacilities for which you want to record information using Trace Level Options page.
For each component, you can select one or more Debugging trace level options. The selections in the Trace Level page specify the level of details in the debugging messages that the system sends to a trace file. For instance, if you select Debugging option, the system sends only the basic error messages, while if you select XDebugging5 option, the system will send errors, warnings, informational, debugging, verbose messages and so on in detail to the trace file.
You can collect and view trace information using the Real-Time Monitoring Tool (RTMT).
The trace files contain information in standard Syslog format. The file includes some or all of the following information for each event that is recorded:
Log profile is an aggregated entity that preserves multiple trace settings of the following Cisco VVB services:
Cisco VVB Engine (Traces termed as MIVR)
Cisco VVB Administration (Traces termed as MADM)
Cisco VVB Cluster View Daemon (Traces termed as MCVD)
Log profiles in Cisco VVB can be one of the following two types:
Custom Log Profiles: If the trace settings generated by system profiles are not sufficient in a particular scenario, you can create custom log profiles for better troubleshooting. You can create and enable these custom log profiles as needed.
Note | You cannot delete the profile if the selected log profile is the last-enabled profile in the system. |
Network services include services that the system requires to function and are activated by default.
After you install your application, network services start automatically.
Choose Cisco VVB Serviceability menu to manage network services.
from theTip | You may need to manage services in both Cisco VVB Serviceability and Cisco Unified Serviceability to troubleshoot a problem. The Cisco Unified Serviceability services are described in the Cisco Unified Serviceability Administration Guide. |
Note | You cannot start or stop Cisco VVB Serviceability service using the Cisco VVB Serviceability web interface and you need to use CLI. For a list of services that you can start and stop using the CLI and for detailed instructions, see "Command Line Interface Reference" section. |
Use the Performance Configuration and Logging page to configure Java Virtual Machine (JVM) parameters and dump Thread and Memory traces for performance monitoring of Cisco VVB servers.
Use the following procedure to configure JVM parameters for a particular service on a particular server.
Step 1 | Choose and select the server and a service for which you want to get the JVM options. |
Step 2 | Click Dump Thread Trace to dump the thread traces for the selected service in the selected server. You can collect the corresponding jvm.log from the log folder for that facility using Real-Time Monitoring Tool (RTMT). |
Step 3 | Click Dump Memory Trace to dump the memory traces. This creates the following two logs in the log folder for that facility. |
Step 4 | Click Enable or Disable radio buttons in this page to change the JVM options. |
Step 5 | Click Update JVM Options to update the new settings for selected service on selected node. |
Simple Network Management Protocol (SNMP) is an industry-standard interface for exchanging management information between network devices. SNMP enables you to monitor and manage the Cisco VVB system. You also can set up SNMP traps to automatically notify any high-severity messages and errors that are generated by the Cisco VVB system.
You can configure the SNMP settings using the Cisco Unified Serviceability web interface.
A Management Information Base (MIB) designates a collection of information that is organized hierarchically. MIBs are made up of managed objects, which are referenced by object identifiers. Managed objects are made up of one or more object instances, which are essentially variables. MIBs provide status monitoring, provisioning, and notification.
MIB |
Agent Service |
---|---|
CISCO-VOICE-APPS-MIB |
Cisco VVB Voice Subagent |
CISCO-CDP-MIB |
Cisco CDP Agent |
CISCO-SYSLOG-MIB |
Cisco Syslog Agent |
SYSAPPL-MIB |
System Application Agent |
MIB-II |
MIB2 Agent |
HOST-RESOURCES-MIB |
Host Resources Agent |
Note |
|
The following section describes CISCO-VOICE-APPS-MIB. For more information about other Cisco VVB supported MIBs, see Cisco Unified CM SNMP chapter in the Cisco Unified Serviceability Administration Guide available here:
The CISCO-VOICE-APPS-MIB provides information associated with the installed workflow applications provisioned on the Cisco VVB Server. It also provides information on the supported SNMP Traps on Cisco VVB. You can manage CISCO-VOICE-APPS-MIB through Cisco VVB Serviceability web interface.
Cisco VVB Voice Subagent
Cisco VVB Voice Subagent service implements the CISCO-VOICE-APPS-MIB. Cisco VVB Voice Subagent Service communicates with the SNMP Master Agent through Cisco VVB SNMP Java Adaptor. The Cisco VVB SNMP Java Adaptor service should be up and running for the Cisco VVB Voice Subagent to work properly.
For more information about the CISCO-VOICE-APPS-MIB, see this URL: ftp://ftp.cisco.com/pub/mibs/v2/CISCO-VOICE-APPS-MIB.my.
Note |
|
Subsystems, which are the functional blocks of Cisco VVB, sends out alarms that are routed to the Syslog or as SNMP Traps. SNMP Traps are generated when any Cisco VVB Subsystem or module or processes start or stop or runtime failure occurs for a module. These failures can be tracked for each major component to track the health of the Cisco VVB system.
The following Traps are supported as part of the CISCO-VOICE-APPS-MIB:
Trap Name |
Description |
---|---|
cvaModuleStart |
A cvaModuleStart notification signifies that an application module or subsystem has successfully started and transitioned into in-service state. |
cvaModuleStop |
A cvaModuleStop notification signifies that an application module or subsystem has stopped. If cause of the failure is known then, it will be specified as part of the Trap message. |
cvaModuleRunTimeFailure |
cvaModuleRunTimeFailure notification signifies that a run time failure has occurred. If cause of the failure is known then it will be specified as part of the Trap message. |
cvaProcessStart |
A cvaProcessStart notification signifies that a process has just started. |
cvaProcessStop |
A cvaProcessStop notification signifies that a process has just stopped. |
The ModuleStart and ModuleStop traps are generated when the key Cisco VVB services including Cisco VVB Engine, Cisco VVB Cluster View Daemon and, Cisco VVB Administration and their modules/subsystems are started and stopped respectively.
The ProcessStart and ProcessStop traps are generated when the key Cisco VVB services including Cisco VVB Engine, Cisco VVB Administration are started and stopped.
You can configure the notification destinations by using the SNMP Notification Destination Configuration page in Cisco Unified Serviceability.
Note | SNMP Traps are not generated for events when the Cisco VVB services and/or their subsystems go Out of Service or are In Service. These events are sent as Remote Syslog messages and can be viewed through any third-party Syslog Viewers. You can refer to the list of Cisco VVB services and their subsystems/modules from the Cisco VVB Serviceability under . |
Note |
|
For all notifications, the system sends traps immediately if the corresponding trap flags are enabled. Before you configure notification destination, verify that the required SNMP services are activated and running. Also, make sure that you configured the privileges for the community string or user correctly.
For more information related to SNMP such as SNMP Version 1, Version 2C, Version 3, SNMP system group configuration, SNMP informs and SNMP trap parameters, see Cisco Unified Serviceability Administration Guide available here: