Managing Sensors

Service Monitor analyzes data that it receives from Cisco 1040 Sensors (Cisco 1040s) installed in your voice network. Each licensed instance of Service Monitor acts as a primary Service Monitor for multiple Cisco 1040s. A Service Monitor can also be configured to act as a secondary Service Monitor for Cisco 1040s that are managed by other licensed instances of Service Monitor. When a Service Monitor becomes unavailable, Cisco 1040s temporarily fail over to secondary Service Monitors until the primary Service Monitor becomes available again.

Service Monitor examines the data it receives from Cisco 1040s, comparing Mean Opinion Scores (MOS)—computed by Cisco 1040s for each RTP stream—against a user-specified threshold value. When MOS drops below the threshold, Service Monitor generates SNMP traps and sends them to up to four trap receivers. Optionally, Service Monitor stores the call metrics it receives from Cisco 1040s to disk files.

To further analyze, display, and act on Service Monitor data, you can use Cisco Unified Operation Manager (Operations Manager), by configuring it as a trap receiver for Service Monitor. Operations Manager can generate events for Service Monitor traps, display the events on the Service Quality Alerts dashboard, and store and display event history. For more information, see User Guide for Cisco Unified Operations Manager.

Figure 4-1 shows Service Monitor and Cisco 1040s installed with Operations Manager.

Performing Initial Configuration in Service Monitor for Sensors

1	Cisco 1040 monitors actual voice calls.	3	Operations Manager presents alert information.
2	Service Monitor evaluates MOS values and sends SNMP traps when a threshold is violated. Service Monitor also sends an SNMP trap when a Cisco 1040 is unreachable.	—	—

Copy the binary image file from the Service Monitor server to each TFTP server that you added in step 1.

Service Monitor copies sensor configuration files to each TFTP server that you configure. When a sensor connects to the network, it downloads a configuration file from a TFTP server before registering to a service monitor. For more information, see Understanding How a Sensor Registers with Service Monitor.

Configuring TFTP Servers for Sensor Configuration and Image Files

Service Monitor uses one or more TFTP servers to provide configuration files and binary image files for sensors. You must define at least one TFTP server for Service Monitor to use. You can configure additional TFTP servers either as backup or if you have more than one DHCP scope.

After you add or edit a sensor, Service Monitor updates the configuration file locally, on its server, before copying the configuration file to all known TFTP servers. Keeping copies of the configuration files on each TFTP server enables sensors to fail over efficiently to a secondary Service Monitor.

You can use the configuration files that Service Monitor keeps on the server to recover if there is a write failure on the TFTP server. In this case, you can manually copy configuration files from Service Monitor to each TFTP server that is configured for Service Monitor. (To verify the contents of a configuration file on the TFTP server, see Viewing the Configuration File on the TFTP Server from a Sensor.)

Step 1

Select Configuration > Sensor > TFTP Servers. The TFTP Server Setup page appears, displaying the information in the following table.


GUI Element	Description/Action
Check box	Select when you want to delete a TFTP server.
TFTP Server	IP address or DNS name.
Port	The customary port number is 69.
Add button	Click to add a TFTP server.
Delete button	Select a check box and click to delete the selected TFTP server.

Adding a TFTP Server

To enable sensors to register with Service Monitor, you must define at least one TFTP server where Service Monitor can provide sensor configuration files. You can configure additional TFTP servers; for example, to serve as backup or if you have more than one DHCP scope.

Note You can use a Unified Communications Manager 6.x, 5.x, or 4.2 as a TFTP server. Security settings on Unified Communications Manager can prevent Service Monitor from uploading configuration files. You must manually copy configuration and image files from Service Monitor to Unified Communications Manager TFTP server.

Step 1

Select Configuration > Sensor > TFTP Servers. The TFTP Server Setup page appears.

Note Copy the binary image file to each TFTP server that you add to Service Monitor.

Copying the Binary Image File to the TFTP Server

Step 1

Copy the binary image file, SvcMonAA2_nn.img, from NMSROOT\ImageDir on the Service Monitor server to the root location on the TFTP server. (NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx; nn is the minor version number for the binary image.) For the name of the most recently supported binary image file, see Release Notes for Cisco Unified Service Monitor 2.0.1.

Deleting a TFTP Server

Step 1

Select Configuration > Sensor > TFTP Servers. The TFTP Server Setup page appears.

Setting Up the Sensor Default Configuration

•

Enable or disable call metrics archiving—Service Monitor saves MOS data in the database. Optionally, you can also save the data to files.

•

View the directory path for the archive data file and the Cisco 1040 image file.

•

Create the default configuration file—QOVDefault.CNF specifies the primary and secondary Service Monitor to which a sensor can register.


GUI Element	Description/Action
Call Metrics Archiving radio buttons	Select one of the following: •Enable—After analysis, Service Monitor saves data from Cisco 1040s to disk files. •Disable—After analysis, Service Monitor discards data. Default: Disable.
Data File Directory	Directory where files are stored if call metrics archiving is enabled. You cannot edit this field. Note Call metrics are archived to NMSROOT/DataDir. (NMSROOT is the directory where Service Monitor is installed. Its default location is C:\Program Files\CSCOpx.)
Image File Directory	Directory where sensor binary image file and configuration files are stored locally: NMSROOT/ImageDir—NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx. You cannot edit this field.
Send traps every n minutes per endpoint	Enter a number greater than or equal to 5. Sensors send data to Service Monitor every 60 seconds. Service Monitor determines whether a violation has occurred and can potentially send a trap-a-minute for each endpoint. Use this setting to reduce the number of traps that Service Monitor sends for each endpoint. For a given endpoint, a trap is sent every n minutes and additional traps during that time are suppressed (not sent).
Default Configuration to TFTP Server
Image Filename	Enter the image filename if you are using a new image (for example, after a product upgrade).
Primary Service Monitor	IP address or DNS name for the primary Service Monitor.
Secondary Service Monitor	IP address or DNS name for the secondary Service Monitor; blank if not set. (See Editing the Configuration for a Specific Sensor.)

Note

If you are using Unified Communications Manager 6.x, 5.x, or 4.2 as a TFTP server, you must manually upload the default configuration from the image file directory on the Service Monitor server to Unified Communications Manager TFTP server.

Configuring Sensors in Service Monitor

Note You must configure DHCP and DNS correctly for Cisco 1040s to work properly. For more information, see Quick Start Guide for Cisco 1040 Sensor.

Understanding the Cisco 1040 Sensor Details Page

Step 1

Select Configuration > Sensor > Management. The Cisco 1040 Sensor Details page displays information listed in the following table.


GUI Element	Description/Action
	Exports data from the Cisco 1040 Sensor Details page to a CSV or PDF file. See Exporting Data to a CSV or PDF File.
	Opens a printer-friendly version of the data in another window; for printing from a browser window.
Check box column	Select Cisco 1040s that you want to edit, reset, or delete.
Name column	Click the name link to view details of the Cisco 1040 configuration. See Viewing Details in Service Monitor for a Specific Sensor.
Sensor Address columns	Displays MAC and IP addresses for Cisco 1040. Click the MAC address link to launch an HTML page on the Cisco 1040. (See Viewing the Configuration Using the Sensor Web Interface.)
Service Monitor columns	Displays the following: •Primary—IP address or hostame of the primary Service Monitor defined for the Cisco 1040. •Secondary—IP address or hostame of the secondary Service Monitor defined for the Cisco 1040. •Registered with—IP address or hostame of the Service Monitor to which the Cisco 1040 is currently sending data. If the sensor is not yet registered, Waiting is displayed. Note If you have recently changed the time on your system or, in rapid succession, stopped and started the QOVR process, Service Monitor might display a Cisco 1040 as registered with Waiting, while still receiving and processing syslog messages from the Cisco 1040. To fix this problem, see Restarting Processes to Update Sensor Registration Information in Service Monitor.
Reset Time column	The last date and time the Cisco 1040 was rebooted.
Edit button	Click to edit the Cisco 1040 configuration. See Editing the Configuration for a Specific Sensor.

Restarting Processes to Update Sensor Registration Information in Service Monitor

Service Monitor might show a Cisco 1040 waiting to register while receiving and processing syslogs from it; this problem can occur after a user does one of the following:

•

Uses pdterm to stop the QOVR process, and, in quick succession, uses pdexec to start it again. To prevent this problem, wait at least 5 minutes between stopping and starting the QOVR process. To correct this problem:

From the command line, stop the QOVR process again, by entering this command:

•

Changes the time on the system where Service Monitor is installed without subsequently stopping and restarting the daemon manager. To correct this problem, stop and start the daemon manager from the command line by issuing the following commands:

Step 2

Browse to the location where you want to store the file and click OK.

Adding a Sensor to Service Monitor

If a sensor is already registered with Service Monitor, you must select it and click the Edit button to update it. For more information, see Editing the Configuration for a Specific Sensor.

Step 1

Select Configuration > Sensor > Management. The Cisco 1040 Sensor Detail page appears.


GUI Element	Description/Action
Sensor Name	Enter up to 20 characters. This name is used on Service Monitor windows, such as reports. Note Sensor names do not need to be unique. Sensors that register to Service Monitor using the default configuration file each use the name Cisco 1040.
Image File Name	Enter the binary image filename. The filename format is SvcMonAA2_nn.img where nn is a revision number. For the name of the most recently supported binary image file, see Release Notes for Cisco Unified Service Monitor 2.0.1. For more information, see Viewing the Configuration Using the Sensor Web Interface.
MAC Address	Enter the MAC address for the Cisco 1040 that you are adding.
Primary Service Monitor	Enter an IP address or DNS name of a host where Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor unless it becomes unreachable.
Secondary Service Monitor	(Optional) Enter an IP address or DNS name of a host where another instance of Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor only if the primary Service Monitor becomes unreachable. For more information, see Viewing the Configuration Using the Sensor Web Interface
Description	Enter up to 80 characters.

Note

If you are using Unified Communications Manager 6.x, 5.x, or 4.2 as a TFTP server, you must manually upload the MAC-specific configuration file from the image file directory on the Service Monitor server to Unified Communications Manager TFTP server. The image file directory is NMSROOT/ImageDir; NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx.

Editing the Configuration for a Specific Sensor

If you want to update the configurations for multiple sensors—for example, so that they all use a new binary image file or a different primary or secondary Service Monitor—see Editing Configurations for Multiple Sensors.

Note Do not edit a Cisco 1040 configuration file using a text editor. Edit a Cisco 1040 configuration file using this procedure or the procedure documented in Editing Configurations for Multiple Sensors.

Use this procedure to update the configuration, including the sensor name and description, for a single sensor.


Fields	Description/Action
Sensor Name	If you want to change the name, enter up to 20 characters. This name is used on Service Monitor windows, such as reports.
MAC Address	Cisco 1040 MAC address. Note You cannot edit this field.
IP Address	Cisco 1040 IP address. Note You cannot edit this field. To update the IP address for a sensor, delete the sensor from Service Monitor and add it again.
Image File Name	Enter the binary image filename. The filename format is SvcMonAA2_nn.img where nn is a revision number. For the name of the most recently supported binary image file, see Release Notes for Cisco Unified Service Monitor 2.0.1. For more information, see Viewing the Configuration Using the Sensor Web Interface.
Primary Service Monitor	Enter an IP address or DNS name of a host where Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor unless it becomes unreachable.
Secondary Service Monitor	(Optional) Enter an IP address or DNS name of a host where Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor only if the primary Service Monitor becomes unreachable.
Description	Enter up to 80 characters.

Step 4

Click OK. Service Monitor saves the configuration file on the local server and copies it to all TFTP servers. Then Service Monitor resets the sensor, so that it loads the updated configuration.

Note

If you are using Unified Communications Manager 6.x, 5.x, or 4.2 as a TFTP server, you must manually upload the updated configuration file from the image file directory on the Service Monitor server to Unified Communications Manager TFTP server. Afterward, you must reset the sensor. (The image file directory is NMSROOT/ImageDir; NMSROOT is the directory where Service Monitor is installed; its default location is C:\Program Files\CSCOpx.)

Editing Configurations for Multiple Sensors

Note Do not edit a Cisco 1040 configuration file using a text editor. Edit a Cisco 1040 configuration file using this procedure or the procedure documented in Editing the Configuration for a Specific Sensor.


Fields	Description/Action
Image File Name	Enter the binary image filename. The filename format is SvcMonAA2_nn.img where nn is a revision number. For the name of the most recently supported binary image file, see Release Notes for Cisco Unified Service Monitor 2.0.1. For more information, see Viewing the Configuration Using the Sensor Web Interface.
Primary Service Monitor	Enter an IP address or DNS name of a host where Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor unless it becomes unreachable.
Secondary Service Monitor	(Optional) Enter an IP address or DNS name of a host where Service Monitor is installed. The Cisco 1040 sends data to this Service Monitor only if the primary Service Monitor becomes unreachable.

Step 4

Click OK. Service Monitor saves the configuration files on the local server copies it to all TFTP servers. Then Service Monitor resets the sensors, so that they load the updated configuration.

Note

Resetting Sensors

Use this procedure to boot one or more Cisco 1040s. After a Cisco 1040 boots, it first uses DHCP to obtain the IP address of the TFTP server. From the TFTP server, Cisco 1040 obtains a configuration file. If the configuration file specifies a binary image file that is different from the currently installed image, Cisco 1040 also obtains the binary image file from the TFTP server.

Note When you reset a sensor, the sensor obtains the time from the Service Monitor system. To synchronize the system and the sensors, reset sensors after any time change on the Service Monitor system. Reset sensors after entering or exiting Daylight Saving Time.

Deleting a Sensor

Note After you delete a sensor, it can no longer automatically register to the Service Monitor from which it has been deleted. To enable such a sensor to register with this Service Monitor again, you must add the sensor manually; see Adding a Sensor to Service Monitor.

Before you delete a sensor, consider how the sensor will be used in the network. Use the information in Table 4-1 to decide whether to delete the sensor and to determine whether you must perform additional actions.

Table 4-1 Considerations and Actions Before Deleting a Sensor
Planned Sensor Configuration		Recommended Action
Primary Receiver	Secondary Receiver	Recommended Action
Another instance of Service Monitor	One of these: •Another instance of Service Monitor •None	Ensure that the sensor is communicating with the other instance of Service Monitor—the primary receiver—before you delete the sensor. Note If, at a later point, you reconfigure the sensor to use this Service Monitor as a primary or secondary receiver, you must manually add the sensor to this Service Monitor.
Another instance of Service Monitor	This Service Monitor	Do not delete the sensor from this Service Monitor. Otherwise, failover is delayed until a user manually adds the sensor to this Service Monitor.
None	None	Before you delete the sensor, you must shut the switch port that physically connects to the 10/100-1 Fast Ethernet port on the sensor: 1. To identify the port, get the switch IP address and the switch port from the sensor web interface. See Viewing the Configuration Using the Sensor Web Interface. 2. To shut the port, use the CLI on the switch. Note Do not delete the sensor from Service Monitor until you shut the switch port. You should also either shut or reconfigure the SPAN or RSPAN destination port on the switch. For information about configuring SPAN and RSPAN on Cisco Catalyst switches and modules, see http://www.cisco.com/en/US/products/hw/switches/ps708/ products_tech_note09186a008015c612.shtml.

•

An error message appears, displaying a list of sensor threshold groups to which the sensor belongs. You will need to remove the sensor from these sensor threshold groups and repeat this procedure.

Viewing the Configuration for a Sensor

Configuration data for a Cisco 1040 Sensor is stored in Service Monitor, is copied to a configuration file for the sensor on each TFTP server, and is copied down to the sensor (the sensor downloads the configuration from the TFTP server). You can look at the configuration details that are stored for a Cisco 1040 Sensor on each point: Service Monitor, TFTP server, and the sensor itself:

Viewing Details in Service Monitor for a Specific Sensor

To open the Cisco 1040 Sensor Detail dialog box, click the name link on the Cisco 1040 Sensor Details page. The Cisco 1040 Sensor Detail dialog box displays the Cisco 1040 Sensor Information table described here.


Field	Description/Action
	Exports data from the Cisco 1040 Sensor Information table to a CSV or PDF file. See Exporting Data to a CSV or PDF File.
	Opens a printer-friendly version of the data in another window; for printing from a browser window.
	Opens context-sensitive online help.
Name link	Cisco 1040 user-entered name—Click to open a web interface on the Cisco 1040. See Viewing the Configuration Using the Sensor Web Interface.
MAC Address	Cisco 1040 MAC address.
IP Address	Cisco 1040 IP address.
Primary Service Monitor	IP address or DNS name for the primary Service Monitor.
Secondary Service Monitor	IP address or DNS name for the secondary Service Monitor; blank if not set. (See Editing the Configuration for a Specific Sensor.)
Registered with	IP address or DNS name for the Service Monitor that this Cisco 1040 is registered with.
Image File Name	Name of the image file installed on the Cisco 1040. Note If there is a more recent image file available on the TFTP server, you must edit the configuration file for the Cisco 1040, specifying the filename for the more recent image, and you must reset the Cisco 1040. (See Editing the Configuration for a Specific Sensor.)
Last Reset Time	Date and time that the Cisco 1040 was last reset. (See Resetting Sensors.)
Description	User-entered description for the Cisco 1040. (See Editing the Configuration for a Specific Sensor.)

Viewing the Configuration File on the TFTP Server from a Sensor

Step 1

From your browser, enter http://<IP address or DNS name>/Communication where IP address is the address of your Cisco 1040 and DNS name is the DNS name for the Cisco 1040. For example:

Step 2

The Communication Log File window displays the following information from the configuration file on the TFTP server for this Cisco 1040:

•

Receiver—IP address or DNS name of each Service Monitor—primary and secondary—defined in the configuration file, separated by semicolons.

•

Image—Name of the binary image file that the Cisco 1040 should download and run from the TFTP server.

•

Last Updated—The last time that this configuration file was updated on the Service Monitor system.

•

CDPGlobalRunState—States whether CDP is enabled (true) or disabled (false).

•

SyslogPort—States the port protocol (UDP) and port number used for sending syslogs to Service Monitor.

•

SkinnyPort—States the port protocol (TCP) and port number used to communicate with Service Monitor.

Viewing the Configuration Using the Sensor Web Interface

You can open a web interface to view the information stored on a Cisco 1040 in one of the following ways:

•

Enter http://<IP address> in your browser where IP address is the address of your Cisco 1040.

The Cisco 1040 web interface displays a Cisco 1040 Information window with the following information:

–

operational—Cisco 1040 is receiving RTP streams, analyzing data, and sending data to Service Monitor.

•

Current Service Monitor—Name of the Service Monitor to which the Cisco 1040 is sending data; this could be the primary or secondary Service Monitor.

•

TFTP IP Address—TFTP server from which the Cisco 1040 downloads its binary image file and configuration file.

•

Software Version—Name of the binary image file installed on the Cisco 1040.

Understanding How Sensors Register with Service Monitors

After you have configured a default sensor configuration file, QOVDefault.CNF, sensors can register with Service Monitor automatically. When a sensor registers automatically, Service Monitor uses the information in the default configuration file and creates a MAC-specific configuration file, QOVmacaddress.CNF, for the newly registered sensor. After a default sensor configuration file is created, if you want to add a sensor to Service Monitor manually, do so before plugging the sensor in.

After it is connected to a switch, a Cisco 1040 uses DHCP to obtain the IP address of the TFTP server. The Cisco 1040 checks the TFTP server for a configuration file, using the first of the following files that it finds:

Understanding How a Sensor Registers with Service Monitor

A newly connected sensor registers to a Service Monitor using a specific configuration file for that sensor, QOV<MAC address>.CNF or using the default configuration file, QOVDefault.CNF. If using the default configuration file, from it, Service Monitor creates a MAC-specific configuration file, QOV<MAC address>.CNF, for the sensor.

There can be only one default configuration file on the TFTP server. The default configuration file specifies the primary Service Monitor. Therefore, sensors that use same TFTP server also use the same default configuration file and register with the same primary Service Monitor.

Understanding Sensor Failover to a Secondary Service Monitor

A Cisco 1040 sends keepalive messages to the Service Monitor to which it is registered and receives acknowledgements from the Service Monitor. After sending three keepalives without receiving any acknowledgement, a Cisco 1040 starts a failover process to a secondary Service Monitor:

The Cisco 1040 sends a keepalive to the secondary Service Monitor that is listed in its configuration file and, upon acknowledgement, registers with that Service Monitor.

The secondary Service Monitor obtains the latest configuration file for this Cisco 1040 from the TFTP server, registering the Cisco 1040 as a failover Cisco 1040.

The Cisco 1040 starts sending syslog messages to the secondary Service Monitor while continuing to send keepalives to the primary Service Monitor to determine whether it is back up. The secondary Service Monitor processes the syslog messages from the failed-over Cisco 1040.

When the primary Service Monitor is back up, the Cisco 1040 unregisters from the secondary Service Monitor and registers to the primary Service Monitor again.

Moving a Sensor from One Location to Another

Warning Before moving a sensor, read the regulatory compliance and safety information in Quick Start Guide for Cisco 1040 Sensor.

Step 1

(Optional) Perform this step if you want to configure the Cisco 1040 to point to a new primary Service Monitor. Edit the configuration file for the Cisco 1040; for more information, see Editing the Configuration for a Specific Sensor.

Step 3

Plug in the Cisco 1040 at a new location. The Cisco 1040 downloads its configuration file from the TFTP server.

Understanding Sensor Call Metrics Archive Files

Service Monitor stores the data it receives from Cisco 1040s in the database, where it remains available for reports for a number of days; for more information, see Configuring and Viewing Other Settings. Service Monitor can also save the data to files in a directory on the server if you have enabled call metrics archiving. To enable or disable call metrics archiving, see Setting Up the Sensor Default Configuration.

Service Monitor creates a new data file daily at midnight. The data filename is QoV_YYYYMMDD.csv where YYYY is the 4-digit year, MM is the two-digit month and DD is the two-digit day. For example, QOV_20061101.csv is a data file for November 1, 2006. Service Monitor also backs up data files that exceed a size limit and deletes older data files; for more information, see Understanding Sensor Archive File Purging, page 6-7.

You can use the data for further analysis or you can disable archiving. (Service Monitor does not send the archived data to other applications.) Table 4-2 lists the format for call metrics data files.

Table 4-2 Service Monitor Archived Call Metric File Format
Description	Value
Cisco 1040 MAC address	MAC address of the Cisco 1040 Sensor
Time stamp	Date and time
Source device IP address	IPv4 address; for example: `172.020.119.043`
Destination device IP address	IPv4 address, for example: `172.020.119.025`
Codec of call data record	2: G711Alaw 64k 3: G711Alaw 56k 4: G711Ulaw 64k 5: G711Ulaw 56k 6: G722 64k 7: G722 56k 8: G722 48k 10: G728 11: G729 12: G729AnnexA 15: G.729AnnexB 16: G729AnnexAwAnnexB
Calculated MOS score	2-digit number with an implied decimal point between the first and second digit
Primary cause of call degradation	J: Jitter P: Packet loss
Actual packet loss in the previous minute	<numeric value>
Actual jitter, in milliseconds, in the previous minute	<numeric value>

Note Call metrics data files remain on disk for 30 days. Service Monitor deletes them thereafter. If you would like to save these files, you must back them up using whatever method your normally use to back up your disk. For more information, see Understanding Sensor Archive File Purging, page 6-7.

Understanding Cisco 1040 Unreachable Trap

Note If you configure Operations Manager to receive traps from Service Monitor, the Cisco 1040 Unreachable trap is displayed on the Alerts and Events monitoring dashboard under the unidentified trap device type.

Table Of Contents