Monitoring Cisco Server Load Balancing Devices

: Where:
: server_name is the name of the server where CiscoWorks2000 and the CFM server software are running.
: port_number is the port number to use for communicating with the CFM server. By default, the port_number is 1741.

The CiscoWorks2000 Login window (Figure 3-1) is displayed.

Figure 3-1: CiscoWorks2000 Login Window

Step 4 Enter your username and password and click OK. The CiscoWorks2000 Main window (Figure 3-2) is displayed.

Figure 3-2: CiscoWorks2000 Main Window

Step 5 Click Content Flow Monitor. The Content Flow Monitor menu (Figure 3-3) is displayed.

Figure 3-3: Content Flow Monitor Menu

Step 6 Click Client. The CFM Services Managers window (Figure 3-4) is displayed.

Figure 3-4: CFM Services Managers Window

Step 7 Click Load Balancing Manager to use CFM to monitor Cisco server load balancing devices. The CFM Main window (Figure 3-5) is displayed.

Figure 3-5: CFM Main Window

The CFM Main window displays status and availability for all discovered Cisco server load balancing devices. For more information on the fields and options provided on the CFM Main window, see the "CFM Main Window" section.

Monitoring the Status of Devices

CFM monitors Cisco server load balancing devices actively. CFM actively monitors resources by polling devices on a regular basis to determine their status and to gather statistics.

You can determine how often polling occurs by setting the monitoring interval. For more information on setting the monitoring interval, refer to the "Defining the Monitoring Interval" section.

The CFM Main window (Figure 3-5) displays status information for Cisco server load balancing devices and shows the associations between the devices.

To view status information for an individual device:

Step 1 From the CFM Main window, select the device type of the device that you want to view.

Step 2 Press Enter or click on the device type. The list of devices expands to show all of the devices of that type currently being monitored by CFM. The status and availability for each device is also displayed.

For example, to view status information for a virtual server, click on Virtuals. The expanded list of virtual servers and their associated status information is displayed (Figure 3-6).

Figure 3-6: CFM Main Window---Expanded

Note If you click on a specific virtual server, the list expands to show all forwarding agents, LocalDirectors, and real servers associated with that virtual server.

Table 3-1: CFM Status and Color Definitions

Color Status Definition

Green

Normal

CFM can communicate with the device and the device is up and running.

Yellow

Degraded

Device is active, but CFM has detected a performance-related problem for the CPU or memory utilization thresholds.

Magenta

Unknown

Device has not been defined to CFM and CFM is not able to determine the device type through discovery.

CFM obtains status information for virtual servers and real servers from their associated LocalDirector. If a LocalDirector stops responding to polls, then the status for all associated virtual servers and real servers becomes Unknown. The real servers might be up and running normally, but it is impossible for CFM to determine their status without information from the associated LocalDirector.

Red

Unavailable

CFM cannot communicate with the device. The device might be down.

Color	Status	Definition
Green	Normal	CFM can communicate with the device and the device is up and running.
Yellow	Degraded	Device is active, but CFM has detected a performance-related problem for the CPU or memory utilization thresholds.
Magenta	Unknown	Device has not been defined to CFM and CFM is not able to determine the device type through discovery. CFM obtains status information for virtual servers and real servers from their associated LocalDirector. If a LocalDirector stops responding to polls, then the status for all associated virtual servers and real servers becomes Unknown. The real servers might be up and running normally, but it is impossible for CFM to determine their status without information from the associated LocalDirector.
Red	Unavailable	CFM cannot communicate with the device. The device might be down.