Use the command-line interface to set trace level settings for Live Data services. There is no method in OAMP to set the log levels for the Live Data components.

Setting the loglevel

Required Minimum Privilege Level: Advanced

Example: admin:set live-data trace dataprocessing loglevel DEBUG

Setting the tracemask

Required Minimum Privilege Level: Advanced

You can set detailed log levels by enabling trace flags, which allows debug statements to appear in the logs. You can control debug tracing for specific functionalities by specifying a TRACE flag name within specific subsystem components. See Infrastructure Trace Definitions in the Administration Console User Guide for Cisco Unified Intelligence Center at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-intelligence-center/products-maintenance-guides-list.html.

Command Syntax

set live-data trace subsystem tracemask value

subsystem

communications, dataprocessing, or database

value

For each of the three subsystems specify one of several tracemasks:

dataprocessing

• TIP_APPL_MESSAGE_TRACEMASK
• CAMEL_JMS_TRACEMASK
• STORM_SPOUT_TRACEMASK
• TIP_PROTOCOL_TRACEMASK
• FAILOVER_HB_TRACEMASK

database

• DB_UCCE_AW_TRACEMASK

communications

• JMS_COMMUNICATION_TRACEMASK
• FAILOVER_TOS_TRACEMASK

To set multiple tracemasks, separate them with a space.

Example: admin: set live-data trace dataprocessing tracemask TIP_APPL_MESSAGE_TRACEMASK CAMEL_JMS_TRACEMASK

To clear all tracemasks, use the tracemask command without parameters, for example:

set live-data trace dataprocessing tracemask

You can list the trace masks available for each subsystem using the command help option, for example:

set live-data trace dataprocessing tracemask ?

Show the loglevel

Required Minimum Privilege Level: Ordinary

To display the current loglevel or tracemask, use the show live-data trace command, for example:

admin:show live-data trace dataprocessing loglevel

admin:show live-data trace dataprocessing tracemask

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific agents.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace agent 5037 6000

Output: Enable detailed traces for agent(s) with the following id(s): 5037 6000

Show Agents Currently Set

Required Minimum Privilege Level: Ordinary

This command shows the IDs of the agents that have detailed trace turned on.

show live-data trace agent

No parameters are required.

Example: admin:show live-data trace agent

Output: Detailed traces are turned on for the agent(s) with the following id(s): 5037

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all agents.

unset live-data trace agent

No parameters are required.

Example: admin:unset live-data trace agent

Output: Disable detailed traces for all agent(s)

Help Command

unset live-data trace agent ?

Example: admin:set live-data trace agent ?

Output: This command is used to set the trace level for Agents.

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific skill-groups.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a skill-group with many agents, for example, more than one hundred, adds a large number of messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: set live-data trace skill-group 5037 6000

Output: Enable detailed traces for skill-group(s) with the following id(s): 5037 6000

Show Skill-Groups Currently Set

Required Minimum Privilege Level: Ordinary

show live-data trace skill-group

No parameters are required.

Example: admin:show live-data trace skill-group

Output: Detailed traces are turned on for the skill-group(s) with the following id(s): 11962

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed tracing for all skill-groups.

unset live-data trace skill-group

No parameters are required.

Example: admin:unset live-data trace skill-group

Output: Disable detailed traces for all skill-group(s)

Help Command

unset live-data trace skill-group ?

Example: admin:set live-data trace skill-group ?

Output: This command is used to set the trace level for skill-groups.

Required Minimum Privilege Level: Advanced

Use this command to enable tracing for specific precision-queues.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a precision-queue adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace precision-queue 5037 6000

Output: Enable detailed traces for precision-queue(s) with the following id(s): 5037 6000

Show Precision-Queues Currently Set

Required Minimum Privilege Level: Ordinary

Show the IDs of the precision-queues that have detailed trace turned on.

show live-data trace precision-queue

No parameters are required.

Example: admin:show live-data trace precision-queue

Output: Detailed traces are turned on for the precision-queue(s) with the following id(s): 5000

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all precision-queues.

unset live-data trace precision-queue

No parameters are required.

Example: admin:unset live-data trace precision-queue

Output: Disable detailed traces for all precision-queue(s)

Help Command

unset live-data trace precision-queue ?

Example: admin:set live-data trace precision-queue ?

Output: This command is used to set the trace level for precision-queues.

Required Minimum Privilege Level: Advanced

Use this command to enable Live Data failover. This command automatically sets the system to run in duplex mode. Run this command on both Side A and Side B.

Command Syntax

set live-data failover

There are no required parameters.

Required Minimum Privilege Level: Advanced

Use this command to unset Live Data failover. This command automatically sets the system to run in simplex mode. Run this command on both Side A and Side B.

Command Syntax

unset live-data failover

There are no required parameters.

Required Minimum Privilege Level: Ordinary

Use this command to display the Live Data cluster failover status and settings.

The command returns information on the Live Data server on which you run the command. The Live Data server information includes the current Live Data cluster settings, the status of the ActiveMQ connection, and the state of the cluster.

The console output after you run this command on the publisher side of a Live Data system is similar to the following:

admin:show live-data failover
# Failover settings..
Cluster failover enabled: true
Cluster ID: A
Remote side addr: not applicable for the publisher in auto-config
Auto config enabled: true

# ActiveMQ NetBridge..
Established

# Cluster state..
PAIRED-ACTIVE

Sample console output on the subscriber side is as follows:

admin:show live-data failover
# Failover settings..
Cluster failover enabled: true
Cluster ID: B
Remote side addr: cuic1
Auto config enabled: true

# ActiveMQ NetBridge..
Established

# Cluster state..
PAIRED-STANDBY

Required Minimum Privilege Level: Advanced

Use this command to set syslog configuration.

set live-data syslog-server syslogHostPrimary [syslogPortPrimary] [syslogHostSecondary syslogPortSecondary]

syslogHostPrimary

Specifies the primary host (fully-qualified domain name or IP address) for syslog.

syslogPortPrimary

The syslogPortPrimary parameter is optional. Specifies the port for syslog. The default value is 514.

syslogHostSecondary

The syslogHostSecondary parameter is optional. Specifies the secondary host (fully-qualified domain name or IP address) for syslog.

syslogPortSecondary

The syslogPortSecondary parameter is optional. Specifies the port for syslog. The default value is 514.

Required Minimum Privilege Level: Advanced

Use this command to unset syslog configuration.

unset live-data syslog-server syslogHostQualifier {primary | secondary | all}

primary

Unset the primary host information (fully-qualified domain name and port).

secondary

Unset the secondary host information (fully-qualified domain name and port).

all

Unset the primary and secondary host information (fully-qualified domain name and port).

Required Minimum Privilege Level: Ordinary

Use this command to show the current configuration for the Live Data syslog server.

show live-data syslog-server

There are no required parameters.

Required Minimum Privilege Level: Advanced

Use this command to start the nmon capture.

Command Syntax

utils live-data nmon start s [seconds] c [count]

s

Specifies the time interval (1 to 60 seconds) between each collection.

c

Specifies the number of collections that you want to perform. Each collection requires about 1 Kilobyte of disk space.

Required Minimum Privilege Level: Advanced

Use this command to stop the nmon capture. The data that you capture in this nmon session is saved in nmon_output.nmon.

Command Syntax

utils live-data nmon stop

There are no required parameters.

Required Minimum Privilege Level: Ordinary

Use this command to show the Socket.IO service status.

show socketio status

There are no required parameters.

Note	If the server cannot establish a JMX connection, the server status is Unavailable. No other status is displayed. If the JMS Brokers, Active Broker, Client Count, or Polling Client Count are not available, the information related to that status does not display.

The console output is similar to the following:

Server Status: Active
JMS Brokers: tcp://localhost:61616,tcp://192.168.1.56:61616
Active Broker: Local
Client Count: 2001 (polling: 312)

Each of these tables is described in more detail below.

Note	The MIB defines a single notification type; all nodes in all clusters may emit notifications. The number of entries within each table may change over time, adapting to changes within the cluster.

The CISCO-LIVEDATA-MIB notification type (cldEventNotif) defines a set of objects that are contained within a Live Data SNMP notification. Live Data notifications are "stateful." A "raise" state event indicates a problem and a "clear" state event follows when the problem resolves or after the component engages fault-tolerance mechanisms to self-heal. To maintain an accurate state at the network management station, you can write rules to automatically correlate "clear" state events to existing "raise" state events and acknowledge those notifications at the management station.

The following notification type objects are used for event correlation.

Live Data events are numerically identified in ascending order where "raise" state events have an odd value and "clear" state events have an even value. If a "raise" state event has a matching "clear" state event, the "clear" state event has the next (higher) even value. "Single-state raise" events are "raise" state events with no matching "clear" state event. A "single-state raise" event is an error condition that typically requires manual intervention to resolve.

To match "clear" state events to existing "raise" state events, match the object cldServerName (from the same device), cldEventAppName (from the same application), and cldEventName (the same event group) value from each event. In many cases, "clear" state events map to "raise" state events. The matching "raise" state event is that event with an even valued EventID that is less than the EventID value of the "clear" state event (for example, 202 is matched to 201). There may be more than one "raise" state event associated with that "clear" state event. The "clear" state event correlates with all existing "raise" state events with the matching ServerName, EventAppName and EventName. For example, assume that the "raise" state events #301 and #303 generate, followed by the "clear" state event #304. In this case, #304 correlates to both #301 and #303, acknowledging both "raise" state events.

To understand the relationship between certain "raise and "clear" state events, see the table of Live Data events and use the "See Also" field to relate events. Each event has a textual label to identify and relate each event in the table.

Events may have certain parameters associated with the event, such as a server IP address or a service state. These parameters are expressed as "tags" within the message text. A "tag" is a name/value pair surrounded by brackets, for example: [server_address=192.168.0.1]. The parameters are expressed this way to facilitate easier (automated) parsing of event text. Because the parameters are generalized across the full set of events, a separate table describes the parameters with labels associated for easy cross-referencing of an event with the parameters used.

This table summarizes the parameters passed into the Live Data SNMP notifications.

Use the command-line interface to set trace level settings for Live Data services. There is no method in OAMP to set the log levels for the Live Data components.

Setting the loglevel

Required Minimum Privilege Level: Advanced

Example: admin:set live-data trace dataprocessing loglevel DEBUG

Setting the tracemask

Required Minimum Privilege Level: Advanced

You can set detailed log levels by enabling trace flags, which allows debug statements to appear in the logs. You can control debug tracing for specific functionalities by specifying a TRACE flag name within specific subsystem components. See Infrastructure Trace Definitions in the Administration Console User Guide for Cisco Unified Intelligence Center at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-intelligence-center/products-maintenance-guides-list.html.

Command Syntax

set live-data trace subsystem tracemask value

subsystem

communications, dataprocessing, or database

value

For each of the three subsystems specify one of several tracemasks:

dataprocessing

• TIP_APPL_MESSAGE_TRACEMASK
• CAMEL_JMS_TRACEMASK
• STORM_SPOUT_TRACEMASK
• TIP_PROTOCOL_TRACEMASK
• FAILOVER_HB_TRACEMASK

database

• DB_UCCE_AW_TRACEMASK

communications

• JMS_COMMUNICATION_TRACEMASK
• FAILOVER_TOS_TRACEMASK

To set multiple tracemasks, separate them with a space.

Example: admin: set live-data trace dataprocessing tracemask TIP_APPL_MESSAGE_TRACEMASK CAMEL_JMS_TRACEMASK

To clear all tracemasks, use the tracemask command without parameters, for example:

set live-data trace dataprocessing tracemask

You can list the trace masks available for each subsystem using the command help option, for example:

set live-data trace dataprocessing tracemask ?

Show the loglevel

Required Minimum Privilege Level: Ordinary

To display the current loglevel or tracemask, use the show live-data trace command, for example:

admin:show live-data trace dataprocessing loglevel

admin:show live-data trace dataprocessing tracemask

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific agents.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace agent 5037 6000

Output: Enable detailed traces for agent(s) with the following id(s): 5037 6000

Show Agents Currently Set

Required Minimum Privilege Level: Ordinary

This command shows the IDs of the agents that have detailed trace turned on.

show live-data trace agent

No parameters are required.

Example: admin:show live-data trace agent

Output: Detailed traces are turned on for the agent(s) with the following id(s): 5037

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all agents.

unset live-data trace agent

No parameters are required.

Example: admin:unset live-data trace agent

Output: Disable detailed traces for all agent(s)

Help Command

unset live-data trace agent ?

Example: admin:set live-data trace agent ?

Output: This command is used to set the trace level for Agents.

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific skill-groups.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a skill-group with many agents, for example, more than one hundred, adds a large number of messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: set live-data trace skill-group 5037 6000

Output: Enable detailed traces for skill-group(s) with the following id(s): 5037 6000

Show Skill-Groups Currently Set

Required Minimum Privilege Level: Ordinary

show live-data trace skill-group

No parameters are required.

Example: admin:show live-data trace skill-group

Output: Detailed traces are turned on for the skill-group(s) with the following id(s): 11962

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed tracing for all skill-groups.

unset live-data trace skill-group

No parameters are required.

Example: admin:unset live-data trace skill-group

Output: Disable detailed traces for all skill-group(s)

Help Command

unset live-data trace skill-group ?

Example: admin:set live-data trace skill-group ?

Output: This command is used to set the trace level for skill-groups.

Required Minimum Privilege Level: Advanced

Use this command to enable tracing for specific precision-queues.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a precision-queue adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace precision-queue 5037 6000

Output: Enable detailed traces for precision-queue(s) with the following id(s): 5037 6000

Show Precision-Queues Currently Set

Required Minimum Privilege Level: Ordinary

Show the IDs of the precision-queues that have detailed trace turned on.

show live-data trace precision-queue

No parameters are required.

Example: admin:show live-data trace precision-queue

Output: Detailed traces are turned on for the precision-queue(s) with the following id(s): 5000

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all precision-queues.

unset live-data trace precision-queue

No parameters are required.

Example: admin:unset live-data trace precision-queue

Output: Disable detailed traces for all precision-queue(s)

Help Command

unset live-data trace precision-queue ?

Example: admin:set live-data trace precision-queue ?

Output: This command is used to set the trace level for precision-queues.

Required Minimum Privilege Level: Advanced

Use this command to set syslog configuration.

set live-data syslog-server syslogHostPrimary [syslogPortPrimary] [syslogHostSecondary syslogPortSecondary]

syslogHostPrimary

Specifies the primary host (fully-qualified domain name or IP address) for syslog.

syslogPortPrimary

The syslogPortPrimary parameter is optional. Specifies the port for syslog. The default value is 514.

syslogHostSecondary

The syslogHostSecondary parameter is optional. Specifies the secondary host (fully-qualified domain name or IP address) for syslog.

syslogPortSecondary

The syslogPortSecondary parameter is optional. Specifies the port for syslog. The default value is 514.

Required Minimum Privilege Level: Advanced

Use this command to unset syslog configuration.

unset live-data syslog-server syslogHostQualifier {primary | secondary | all}

primary

Unset the primary host information (fully-qualified domain name and port).

secondary

Unset the secondary host information (fully-qualified domain name and port).

all

Unset the primary and secondary host information (fully-qualified domain name and port).

Required Minimum Privilege Level: Ordinary

Use this command to show the current configuration for the Live Data syslog server.

show live-data syslog-server

There are no required parameters.

Required Minimum Privilege Level: Ordinary

Use this command to show the Socket.IO service status.

show socketio status

There are no required parameters.

Note	If the server cannot establish a JMX connection, the server status is Unavailable. No other status is displayed. If the JMS Brokers, Active Broker, Client Count, or Polling Client Count are not available, the information related to that status does not display.

The console output is similar to the following:

Server Status: Active
JMS Brokers: tcp://localhost:61616,tcp://192.168.1.56:61616
Active Broker: Local
Client Count: 2001 (polling: 312)

Use the command-line interface to set trace level settings for Live Data services. There is no method in OAMP to set the log levels for the Live Data components.

Setting the loglevel

Required Minimum Privilege Level: Advanced

Example: admin:set live-data trace dataprocessing loglevel DEBUG

Setting the tracemask

Required Minimum Privilege Level: Advanced

You can set detailed log levels by enabling trace flags, which allows debug statements to appear in the logs. You can control debug tracing for specific functionalities by specifying a TRACE flag name within specific subsystem components. See Infrastructure Trace Definitions in the Administration Console User Guide for Cisco Unified Intelligence Center at https://www.cisco.com/c/en/us/support/customer-collaboration/unified-intelligence-center/products-maintenance-guides-list.html.

Command Syntax

set live-data trace subsystem tracemask value

subsystem

communications, dataprocessing, or database

value

For each of the three subsystems specify one of several tracemasks:

dataprocessing

• TIP_APPL_MESSAGE_TRACEMASK
• CAMEL_JMS_TRACEMASK
• STORM_SPOUT_TRACEMASK
• TIP_PROTOCOL_TRACEMASK
• FAILOVER_HB_TRACEMASK

database

• DB_UCCE_AW_TRACEMASK

communications

• JMS_COMMUNICATION_TRACEMASK
• FAILOVER_TOS_TRACEMASK

To set multiple tracemasks, separate them with a space.

Example: admin: set live-data trace dataprocessing tracemask TIP_APPL_MESSAGE_TRACEMASK CAMEL_JMS_TRACEMASK

To clear all tracemasks, use the tracemask command without parameters, for example:

set live-data trace dataprocessing tracemask

You can list the trace masks available for each subsystem using the command help option, for example:

set live-data trace dataprocessing tracemask ?

Show the loglevel

Required Minimum Privilege Level: Ordinary

To display the current loglevel or tracemask, use the show live-data trace command, for example:

admin:show live-data trace dataprocessing loglevel

admin:show live-data trace dataprocessing tracemask

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific agents.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace agent 5037 6000

Output: Enable detailed traces for agent(s) with the following id(s): 5037 6000

Show Agents Currently Set

Required Minimum Privilege Level: Ordinary

This command shows the IDs of the agents that have detailed trace turned on.

show live-data trace agent

No parameters are required.

Example: admin:show live-data trace agent

Output: Detailed traces are turned on for the agent(s) with the following id(s): 5037

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all agents.

unset live-data trace agent

No parameters are required.

Example: admin:unset live-data trace agent

Output: Disable detailed traces for all agent(s)

Help Command

unset live-data trace agent ?

Example: admin:set live-data trace agent ?

Output: This command is used to set the trace level for Agents.

Required Minimum Privilege Level: Advanced

Use this command to enable detailed tracing for specific skill-groups.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a skill-group with many agents, for example, more than one hundred, adds a large number of messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: set live-data trace skill-group 5037 6000

Output: Enable detailed traces for skill-group(s) with the following id(s): 5037 6000

Show Skill-Groups Currently Set

Required Minimum Privilege Level: Ordinary

show live-data trace skill-group

No parameters are required.

Example: admin:show live-data trace skill-group

Output: Detailed traces are turned on for the skill-group(s) with the following id(s): 11962

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed tracing for all skill-groups.

unset live-data trace skill-group

No parameters are required.

Example: admin:unset live-data trace skill-group

Output: Disable detailed traces for all skill-group(s)

Help Command

unset live-data trace skill-group ?

Example: admin:set live-data trace skill-group ?

Output: This command is used to set the trace level for skill-groups.

Required Minimum Privilege Level: Advanced

Use this command to enable tracing for specific precision-queues.

Note

This command requires in-depth system knowledge. Use detailed tracing only for advanced troubleshooting. Enabling detailed tracing for a precision-queue adds many messages to the log files. The system may quickly exceed limits on the size and number of log files, causing the oldest log files to be overwritten. As a result, running detailed tracing shortens the history covered by the log files.

Note	Running this command overwrites any previous setting.

Example: admin:set live-data trace precision-queue 5037 6000

Output: Enable detailed traces for precision-queue(s) with the following id(s): 5037 6000

Show Precision-Queues Currently Set

Required Minimum Privilege Level: Ordinary

Show the IDs of the precision-queues that have detailed trace turned on.

show live-data trace precision-queue

No parameters are required.

Example: admin:show live-data trace precision-queue

Output: Detailed traces are turned on for the precision-queue(s) with the following id(s): 5000

Unset Trace

Required Minimum Privilege Level: Advanced

This command turns off detailed traces for all precision-queues.

unset live-data trace precision-queue

No parameters are required.

Example: admin:unset live-data trace precision-queue

Output: Disable detailed traces for all precision-queue(s)

Help Command

unset live-data trace precision-queue ?

Example: admin:set live-data trace precision-queue ?

Output: This command is used to set the trace level for precision-queues.

Required Minimum Privilege Level: Advanced

Use this command to enable Live Data failover. This command automatically sets the system to run in duplex mode. Run this command on both Side A and Side B.

Command Syntax

set live-data failover

There are no required parameters.

Required Minimum Privilege Level: Advanced

Use this command to unset Live Data failover. This command automatically sets the system to run in simplex mode. Run this command on both Side A and Side B.

Command Syntax

unset live-data failover

There are no required parameters.

Required Minimum Privilege Level: Ordinary

Use this command to display the Live Data cluster failover status and settings.

The command returns information on the Live Data server on which you run the command. The Live Data server information includes the current Live Data cluster settings, the status of the ActiveMQ connection, and the state of the cluster.

The console output after you run this command on the publisher side of a Live Data system is similar to the following:

admin:show live-data failover
# Failover settings..
Cluster failover enabled: true
Cluster ID: A
Remote side addr: not applicable for the publisher in auto-config
Auto config enabled: true

# ActiveMQ NetBridge..
Established

# Cluster state..
PAIRED-ACTIVE

Sample console output on the subscriber side is as follows:

admin:show live-data failover
# Failover settings..
Cluster failover enabled: true
Cluster ID: B
Remote side addr: cuic1
Auto config enabled: true

# ActiveMQ NetBridge..
Established

# Cluster state..
PAIRED-STANDBY

Required Minimum Privilege Level: Advanced

Use this command to set syslog configuration.

set live-data syslog-server syslogHostPrimary [syslogPortPrimary] [syslogHostSecondary syslogPortSecondary]

syslogHostPrimary

Specifies the primary host (fully-qualified domain name or IP address) for syslog.

syslogPortPrimary

The syslogPortPrimary parameter is optional. Specifies the port for syslog. The default value is 514.

syslogHostSecondary

The syslogHostSecondary parameter is optional. Specifies the secondary host (fully-qualified domain name or IP address) for syslog.

syslogPortSecondary

The syslogPortSecondary parameter is optional. Specifies the port for syslog. The default value is 514.

Required Minimum Privilege Level: Advanced

Use this command to unset syslog configuration.

unset live-data syslog-server syslogHostQualifier {primary | secondary | all}

primary

Unset the primary host information (fully-qualified domain name and port).

secondary

Unset the secondary host information (fully-qualified domain name and port).

all

Unset the primary and secondary host information (fully-qualified domain name and port).

Required Minimum Privilege Level: Ordinary

Use this command to show the current configuration for the Live Data syslog server.

show live-data syslog-server

There are no required parameters.

Required Minimum Privilege Level: Advanced

Use this command to start the nmon capture.

Command Syntax

utils live-data nmon start s [seconds] c [count]

s

Specifies the time interval (1 to 60 seconds) between each collection.

c

Specifies the number of collections that you want to perform. Each collection requires about 1 Kilobyte of disk space.

Required Minimum Privilege Level: Advanced

Use this command to stop the nmon capture. The data that you capture in this nmon session is saved in nmon_output.nmon.

Command Syntax

utils live-data nmon stop

There are no required parameters.

Required Minimum Privilege Level: Ordinary

Use this command to show the Socket.IO service status.

show socketio status

There are no required parameters.

Note	If the server cannot establish a JMX connection, the server status is Unavailable. No other status is displayed. If the JMS Brokers, Active Broker, Client Count, or Polling Client Count are not available, the information related to that status does not display.

The console output is similar to the following:

Server Status: Active
JMS Brokers: tcp://localhost:61616,tcp://192.168.1.56:61616
Active Broker: Local
Client Count: 2001 (polling: 312)

Each of these tables is described in more detail below.

Note	The MIB defines a single notification type; all nodes in all clusters may emit notifications. The number of entries within each table may change over time, adapting to changes within the cluster.

The CISCO-LIVEDATA-MIB notification type (cldEventNotif) defines a set of objects that are contained within a Live Data SNMP notification. Live Data notifications are "stateful." A "raise" state event indicates a problem and a "clear" state event follows when the problem resolves or after the component engages fault-tolerance mechanisms to self-heal. To maintain an accurate state at the network management station, you can write rules to automatically correlate "clear" state events to existing "raise" state events and acknowledge those notifications at the management station.

The following notification type objects are used for event correlation.

Live Data events are numerically identified in ascending order where "raise" state events have an odd value and "clear" state events have an even value. If a "raise" state event has a matching "clear" state event, the "clear" state event has the next (higher) even value. "Single-state raise" events are "raise" state events with no matching "clear" state event. A "single-state raise" event is an error condition that typically requires manual intervention to resolve.

To match "clear" state events to existing "raise" state events, match the object cldServerName (from the same device), cldEventAppName (from the same application), and cldEventName (the same event group) value from each event. In many cases, "clear" state events map to "raise" state events. The matching "raise" state event is that event with an even valued EventID that is less than the EventID value of the "clear" state event (for example, 202 is matched to 201). There may be more than one "raise" state event associated with that "clear" state event. The "clear" state event correlates with all existing "raise" state events with the matching ServerName, EventAppName and EventName. For example, assume that the "raise" state events #301 and #303 generate, followed by the "clear" state event #304. In this case, #304 correlates to both #301 and #303, acknowledging both "raise" state events.

To understand the relationship between certain "raise and "clear" state events, see the table of Live Data events and use the "See Also" field to relate events. Each event has a textual label to identify and relate each event in the table.

Events may have certain parameters associated with the event, such as a server IP address or a service state. These parameters are expressed as "tags" within the message text. A "tag" is a name/value pair surrounded by brackets, for example: [server_address=192.168.0.1]. The parameters are expressed this way to facilitate easier (automated) parsing of event text. Because the parameters are generalized across the full set of events, a separate table describes the parameters with labels associated for easy cross-referencing of an event with the parameters used.

This table summarizes the parameters passed into the Live Data SNMP notifications.