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 Prime Collaboration uses the data that it receives from Cisco 1040 Sensors to determine the voice transmission quality in your network.
For the Cisco 1040 Sensor to operate as desired, the switch connected to Cisco 1040 must be managed and configured in Cisco Prime Collaboration Assurance. For more details, see the Cisco Prime Collaboration Assurance and Analytics Install and Upgrade Guide:
Note | The Cisco 1040 Sensor management is not applicable if you have installed Cisco Prime Collaboration in MSP mode. |
Cisco 1040 Sensor is now end of sale. For more information, see End-of-Sale and End-of-Life Announcement for the Cisco 1040 Sensor page.
The Cisco Prime NAM/vNAM replaces the Cisco 1040 Sensor and fills the missing capabilities gap. You can use Cisco Prime Network Analysis Module (NAM) and Cisco Prime Collaboration together to monitor and troubleshoot voice and other network-related issues. For more information, see the Using Cisco Prime Virtual Network Analysis Module and Cisco Prime Collaboration to Monitor and Troubleshoot Voice and Video white paper.
Note | For Cisco Prime Collaboration Release 11.5 and later Cisco Prime NAM/vNAM is not supported in FIPS compliant setup. |
To know about what information you can get from the NAM reports, see NAM & Sensor Report.
For initial configuration of Cisco 1040 Sensors, do the following:
Step 1 | Add one or more TFTP servers for Cisco Prime Collaboration and Cisco 1040 Sensors to use. See Configure TFTP Servers for Cisco 1040 Configuration and Image Files. |
Step 2 | Create a default
configuration file. See
Set
Up the Cisco 1040 Sensor Default Configuration.
When a Cisco 1040 connects to the network, it downloads a configuration file from a TFTP server before registering to Cisco Prime Collaboration. |
Cisco Prime Collaboration uses one or more TFTP servers to provide configuration files and binary image files for Cisco 1040s. You must define at least one TFTP server for Cisco Prime Collaboration to use. You can configure additional TFTP servers if you either want a backup server or have more than one DHCP scope.
You can use the configuration files that Cisco Prime Collaboration 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 Cisco Prime Collaboration to each TFTP server that is configured for Cisco Prime Collaboration.
To enable Cisco 1040s to register with Cisco Prime Collaboration, you must define at least one TFTP server where Cisco Prime Collaboration can provide Cisco 1040 configuration files (and the binary image file).
Enable or disable call metrics archiving—Cisco Prime Collaboration 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 Cisco Prime Collaboration to which a Cisco 1040 can register.
Cisco Prime Collaboration analyzes data that it receives from Cisco 1040 Sensors installed in your voice network. Cisco Prime Collaboration manages multiple Cisco 1040 Sensors.
To see Cisco 1040 Sensor details, choose . The Cisco 1040 Sensor Details page displays information listed in the following table:
Description |
|
---|---|
|
Exports data from the Cisco 1040 Sensor/NAM Details page to a CSV or PDF file. |
|
Opens a printer-friendly version of the data in another window; for printing from a browser window. |
Click the name link to view details of the Cisco 1040 configuration. |
|
Displays MAC and IP addresses for Cisco 1040. Click the MAC address link to launch an HTML page on the Cisco 1040. |
|
The last date and time that Cisco Prime Collaboration sent a reset command to the Cisco 1040. |
|
See Reset Cisco 1040s. |
|
Cisco Prime Collaboration might show a Cisco 1040 Sensors 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:
pdterm QOVR
pdexec QOVR
Changes the time on the system where Cisco Prime Collaboration is installed without subsequently stopping and restarting the daemon manager. To correct this problem, login as admin and execute the following commands:
<hostname>/admin#application stop cpcm <hostname>/admin#application start cpcm
To add a Cisco 1040 Sensor to Cisco Prime Collaboration, perform the following procedure.
Step 1 | Select . The Cisco 1040 Sensor/NAM Details page is displayed. |
Step 2 | Click Add. The Add a Cisco 1040 Sensor dialog box is displayed. |
Step 3 | Enter data listed in the following table: |
Step 4 | Click OK. The configuration file is saved on the server where Cisco Prime Collaboration is installed and is copied to all TFTP servers. (See Configure TFTP Servers for Cisco 1040 Configuration and Image Files.) The configuration file is named QOV<MAC address>.CNF, where <MAC address> is the MAC address for the Cisco 1040. Similarly, for updating the configuration, select one or more check boxes and click Edit. |
Note |
If you use Unified CM as a TFTP server, you must manually upload the updated configuration file from the image file directory on the Cisco Prime Collaboration server to the root location on Unified CM TFTP server. Afterward, you must reset the Cisco 1040. (The image file directory is NMSROOT/ImageDir. NMSROOT is the directory where Cisco Prime Collaboration is installed; its default location is C:\Program Files\CSCOpx.) If the Cisco 1040 does not register or does not load the latest files, restart the TFTP Server.
Do not edit a Cisco 1040 configuration file using a text editor. Edit a Cisco 1040 configuration file using this procedure only.
Step 1 | Select . |
Step 2 | Select check boxes for more than one Cisco 1040 and click Edit. |
Step 3 | Update any of the fields. |
Step 4 | Click OK. Cisco Prime Collaboration saves the configuration files on the local server copies it to all TFTP servers. Then Cisco Prime Collaboration resets the Cisco 1040s, so that they load the updated configuration. |
Enter the binary image filename. The filename format is SvcMonAB2_nnn.img where nnn is a revision number. For the name of the most recently supported binary image file, see Cisco Prime Unified Service Monitor 2.3 Compatibility Matrix. |
|
Enter an IP address or DNS name of a host where Cisco Prime Collaboration is installed. The Cisco 1040 sends data to this Cisco Prime Collaboration unless it becomes unreachable. |
|
(Optional) Enter an IP address or DNS name of a host where Cisco Prime Collaboration is installed. The Cisco 1040 sends data to this Cisco Prime Collaboration only if the primary Cisco Prime Collaboration becomes unreachable. |
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. Cisco 1040 obtains a configuration file from the TFTP server. If the configuration file specifies a binary image file that is different from the currently installed image, the Cisco 1040 obtains the binary image file from the TFTP server.
Step 1 | Select . | ||
Step 2 | Select check boxes for the Cisco 1040s that you want to reset. | ||
Step 3 | Click
Reset. The Cisco
1040 will take a few minutes to complete the startup sequence, reconfigure (if
necessary), and register with Cisco Prime Collaboration.
When you reset a Cisco 1040, Cisco Prime Collaboration sends the most recent time to the sensor. The Cisco 1040 resets its clock as needed. |
Before you delete a Cisco 1040 Sensor from Cisco Prime Collaboration, you must shut the switch port that physically connects to the 10/100-1 Fast Ethernet port on the Cisco 1040:
Step 1 | To identify the port, get the switch IP address and the switch port from the Cisco 1040 web interface. | ||||
Step 2 | To shut the
port, use the CLI on the switch.
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. After you delete a Cisco 1040, it cannot automatically register again to the Cisco Prime Collaboration from which it has been deleted. To enable such a Cisco 1040 to register with this Cisco Prime Collaboration again, you must add the Cisco 1040 Sensor manually. See Add a Cisco 1040 Sensor. To delete, select . Select check boxes for the Cisco 1040s that you want to delete from the Cisco 1040 Sensor Details page and click Delete.
Cisco Prime Collaboration sends a time synchronization message to each Cisco 1040 Sensor hourly. Cisco Prime Collaboration also sends a time synchronization message when a Cisco 1040 registers. A Cisco 1040 registers when it is added to the network and when it has been reset. The Cisco 1040 receives the time from Cisco Prime Collaboration and resets its clock as needed. |
To view the diagnostics stored on a Cisco 1040, enter http://<IP address>/Diagnostics in your browser, where IP address is the address of your Cisco 1040.
The Cisco 1040 web interface displays a Diagnostics Information window with the following information:
Seconds of drift and the last time and date that the clock was reset; for example, “1 second(s) updated at 9:23:37 03/16/2009”. |
|
Number of RTP streams that were analyzed during the last interval. |
|
Time and date when the sensor last received an ACK or timeSet message, or any supported message from the Cisco Prime Collaboration. |
|
Time and date that the Cisco 1040 last sent data to Cisco Prime Collaboration. |
|
Destination hostname or IP address and port number to which the report was sent. |
|
Number of packets that the Cisco 1040 received during the last interval. |
|
Number of errors received on the monitoring interface as reported by pcap. |
|
Number of packets dropped on the monitoring interface as reported by pcap. |
|
Number of buffer overruns on the monitoring interface as reported by pcap. |
|
Number of framing errors on the monitoring interface as reported by pcap. |
|
Monitoring interface is in promiscuous mode (yes) or not (no). |