Cisco Cisco Unified Operations Manager 8.0 White Paper
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 51 of 112
6 Cisco Unified Communications Service Monitor
When the Cisco 1040 Sensor boots up, it uses DHCP option 150 to TFTP its
configuration and image files. Note that the Cisco 1040 does not support CDP and thus
does not receive any Auxiliary VLAN information from the switch that it is plugged into.
If you are using two VLANs, one for voice and a second for data, make sure that a single
VLAN is configured on the switch port that the Cisco 1040 is plugged into. Make sure
that this VLAN has a DHCP server configured for that subnet/VLAN.
Similar to the way that an IP phone registers with a Cisco CallManager, a Cisco 1040
Sensor registers (also using SCCP) to the Service Monitor application. On the TFTP
server, the Cisco 1040 first looks for its configuration file, named QoV [Cisco 1040 MAC
address].CNF. If that file does not exist, the Cisco 1040 looks for a file named
QOVDefault.CNF. This is a generic configuration file to be used when the “auto
registration” option is selected within the Service Monitor application. These .CNF files
provide the image filename for the Cisco 1040 to download, in addition to the Service
Monitor IP addresses. The Cisco 1040 then downloads this image and registers to the
Service Monitor, just like a phone registers to a Cisco CallManager, using SCCP.
The following are some important points that you should be aware of when you are
configuring a Cisco 1040:
1. The Cisco 1040 has two Ethernet ports. The first port is for DHCP and TFTP; port #1
is the IP address for the sensor. This port is also for PoE (IEEE PoE).
On a Catalyst 3550, you might need to configure the switch port that is connected to the
sensor's port #1. If port #1 on the Cisco 1040 flaps when plugged into a Catalyst 3550
switch port, configure the Catalyst 3550 switch port using the following Cisco IOS CLI:
power inline delay shutdown 20 initial 30.
configuration and image files. Note that the Cisco 1040 does not support CDP and thus
does not receive any Auxiliary VLAN information from the switch that it is plugged into.
If you are using two VLANs, one for voice and a second for data, make sure that a single
VLAN is configured on the switch port that the Cisco 1040 is plugged into. Make sure
that this VLAN has a DHCP server configured for that subnet/VLAN.
Similar to the way that an IP phone registers with a Cisco CallManager, a Cisco 1040
Sensor registers (also using SCCP) to the Service Monitor application. On the TFTP
server, the Cisco 1040 first looks for its configuration file, named QoV [Cisco 1040 MAC
address].CNF. If that file does not exist, the Cisco 1040 looks for a file named
QOVDefault.CNF. This is a generic configuration file to be used when the “auto
registration” option is selected within the Service Monitor application. These .CNF files
provide the image filename for the Cisco 1040 to download, in addition to the Service
Monitor IP addresses. The Cisco 1040 then downloads this image and registers to the
Service Monitor, just like a phone registers to a Cisco CallManager, using SCCP.
The following are some important points that you should be aware of when you are
configuring a Cisco 1040:
1. The Cisco 1040 has two Ethernet ports. The first port is for DHCP and TFTP; port #1
is the IP address for the sensor. This port is also for PoE (IEEE PoE).
On a Catalyst 3550, you might need to configure the switch port that is connected to the
sensor's port #1. If port #1 on the Cisco 1040 flaps when plugged into a Catalyst 3550
switch port, configure the Catalyst 3550 switch port using the following Cisco IOS CLI:
power inline delay shutdown 20 initial 30.
2. The 2nd port has no IP address and is used to connect to the switch using a span port
that spans phone ports, gateway ports, or VLAN with Real-Time Transport Protocol
(RTP), basically spanning any port(s) that has RTP flowing through it. The closer to the
phone port, the more consistent the MOS calculated by the Cisco 1040 will be to that of
the end user experience
that spans phone ports, gateway ports, or VLAN with Real-Time Transport Protocol
(RTP), basically spanning any port(s) that has RTP flowing through it. The closer to the
phone port, the more consistent the MOS calculated by the Cisco 1040 will be to that of
the end user experience
.
Choose the phones/phone calls that you want to monitor, choose
a port to span, and configure that span port. This is an example of performing the
configuration using the Cisco IOS CLI:
configuration using the Cisco IOS CLI:
Cisco Internetwork Operating System Software IOS (tm) C3550 Software
monitor session 1 source interface Fa0/18 , Fa0/22 rx
monitor session 1 source interface Fa0/4
monitor session 1 source vlan 1 rx
monitor session 1 destination interface Fa0/9
3. Place the image file (.img) and the configuration file (.cnf) on the TFTP server that the
phones are using. For Cisco CallManager, it is usually the C:\Program
Files\Cisco\TFTPPath directory. For Cisco CallManager Express (CME), it is usually the
router’s flash.
phones are using. For Cisco CallManager, it is usually the C:\Program
Files\Cisco\TFTPPath directory. For Cisco CallManager Express (CME), it is usually the
router’s flash.