White Paper

White Paper

2. Use your system documentation to configure NTP on the Windows Server 2003 system where

Service Monitor will be installed. Configure NTP with the time server being used by call

manager in your network. You might find How to configure an authoritative time server in

Windows Server 2003 at

http://support.microsoft.com/kb/816042 useful.

Connectivity

Ensure that the Service Monitor server can reach the TFTP server and the phones or devices in the

IP address range where the Cisco 1040 would be deployed.

Terminal Server Services

Remote Desktop Service and/or Virtual Network Computing (VNC) Services are recommended to

remotely manage the Service Monitor server. VNC Services and Remote Desktop can be used to

remotely install the Operations Manager and Service Monitor software.

Antivirus and Platform Agents

You should enable virus protection on the Service Monitor server, using antivirus software. Active

scanning of drives and memory should be performed during off-peak hours. Please exclude from

scanning the “CSCOpx” folder. You may experience delays, and performance may be degraded,

when the virus protection software is scanning all files. Service Monitor has undergone

interoperability testing with the following:

●

Third-party virus protection software:

◦ Symantec Antivirus Corporate Edition Version 9.0

◦ McAfee VirusScan Enterprise 8.0

●

Platform Agents:

◦ (Optional) Cisco Security Agent 4.0.3 (build 736)

Check Routing and Firewalls

Make sure that any firewalls between the Service Monitor server and the call manager, TFTP

server, and Cisco 1040s are configured to allow management traffic through. See the “Port

Availability” section below for information on which ports should be opened.

Also make sure that there is connectivity between devices and the Service Monitor server. Even if a

route exists to a network behind a device, it does not mean that one exists to (and from) the device

itself.

Port Availability

Table 2 lists the ports used by Service Monitor. These ports should not be scanned.

Table 2. Service Monitor Port Usage

Protocol Port Number Service Name

UDP 22 SSH

UDP 53 DNS

UDP 67 and 68 DHCP

UDP 5666 Syslog—Service Monitor receives syslog messages from Cisco 1040

TCP 2000 SCCP—Service Monitor uses SCCP to communicate with Cisco 1040s

TCP 43459 Database.

TCP 5665-5680 Interprocess communication between the user interface and back-end processes