Table of Contents

Setting Up the Collection Manager

Setting Up the Collection Manager

This chapter describes common scenarios to help you configure your system. It contains:

• Collection Manager Overview
  
  
• Configuring Collection Managers
  
  
• Testing Connectivity (localhost)
  
  
• Adding a Collection Manager
  
  
• Testing Connectivity (Remote CM)
  
  
• Viewing Collection Manager Status
  
  
• Modifying a Collection Manager
  
  
• Reassigning Devices
  
  
• Disabling the Local Collection Manager
  
  
• Changing Passwords
  
  
• Removing a Collection Manager
  
  

Collection Manager Overview

SLM works in conjunction with the collection manager (CM), a software bundle designed to perform data collection and aggregation functions for network management applications. It is used by SLM to collect performance data needed to monitor SLAs that you have established with your service providers.

The SLM server ships with an embedded CM as part of the Service Management Solution (SMS). A remote CM can also be installed on any remote device that meets CM server requirements. (See Installing Service Level Manager on Windows 2000, Windows NT, and Solaris for a list of specifications.) This distributed data collection and aggregation system provides a cost-effective, scalable solution.

Several CMs can be deployed in your network. Figure 6-1 shows a sample network configuration using a SLM server with an embedded CM and two remote CMs.

The embedded CM, which is also referred to as the local CM (localhost), requires no configuration. This is the default CM to which devices in Essentials Inventory are automatically assigned. If you decide to add a remote CM to your network, you can change the default setting from the local CM to the remote CM.

Note   The CM is not backward-compatible with prior SLM releases.

Each CM collects the appropriate service-level metrics from its assigned set of SA Agent-enabled network devices using SNMP. The SLM server periodically collects data from the CMs using HTTP. This architecture enables collection of management data across VPNs and firewalls.

The data, however, might not arrive on the server immediately because of lags inherent to the polling cycle. Because of this lag, you might not see all data available until the next polling cycle.

In addition to periodic polling to retrieve SA Agent data, the CM also supports fast polling to assure that SA Agent operations are recreated after an IOS device is reset. This reduces data being lost.

SLM configures SLA source devices to set traps for threshold violations. When an SLA is defined, the CM configures the SA Agent source device to generate an SNMP trap if the hourly latency threshold is exceeded. When the SA Agent detects a threshold violation, an SNMP trap alerts third-parties and applications.

The SNMP trap notification feature is enabled by default, but you have the option to disable this feature at any time. See "Disabling the Trap Feature for SLM Threshold Violations."

Although this feature is already enabled on the CM, additional configuration is needed to generate SNMP traps on Cisco routers supporting SA Agent capability. The procedure for enabling and disabling traps on Cisco devices is discussed in the chapter "Setting Up Service Level Contracts and Service Level Agreements."

Configuring Collection Managers

The SLM application installs an embedded CM named "localhost" on the local SLM server during initial installation. The embedded CM (also referred to as the local CM) needs no configuration. It is the default CM.

If you decide to install another CM, (which requires that you contact your sales representative), you'll need to configure it using the SLM administrative GUI. (See "Adding a Collection Manager.")

The Configure Collection Manager window opens to display "localhost" in the Collection Managers column. Localhost is listed in bold text, which represents the default CM. (See Figure 6-2.)

From the Configure Collection Manager window, you can perform any of the following:

• Add a new CM. (See "Adding a Collection Manager.")
  
  
• Modify an existing CM. (See "Modifying a Collection Manager.")
  
  
• Remove a CM. (See "Removing a Collection Manager.")
  
  

  ---

  Note   You cannot delete the local CM or any CM set as default.

  ---

Table 6-1 defines the Configure Collection Manager window elements.

Testing Connectivity (localhost)

Although the CM requires no configuration, you have the option to test connectivity between the SLM server and the embedded CM. This also verifies the authentication process and that the embedded CM is up and responding to queries. You can modify the timeout setting when testing connectivity, which has a default value of 60 seconds.

Note   This procedure assumes you are already viewing the Configure Collection Manager window and that only the local CM is installed.

Procedure

The Add or Modify Collection Manager (localhost) window opens. (See Figure 6-3.)

---

Note   If you are adding a remote CM to your network, or if you are modifying a remote CM on your network not set as default, the Add or Modify Collection Manager window and elements appear differently to accommodate for additional configuration needs. (See Fi gure 6-6.)

---

Table 6-2 defines the Add or Modify Collection Manager (localhost) window elements.

Step 2   Click Test Connectivity. You can also use the shortcut keys.

The Test Manager Connectivity dialog box appears. (See Figure 6-4.)

Table 6-3 defines Test Manager Connectivity dialog box elements.

Step 3   Do one of the following:

• Click OK to test the connection using the default value. You are prompted that your connection was successful. Click OK.
  
• Modify the timeout value, then click OK to test the connection using the new value. You are prompted that your connection was successful. Click OK.
  
• Click Cancel to return to the Add or Modify Collection Manager window.
  

  ---

  Note   If you do not change the timeout value, clicking OK or Cancel recognizes the default timeout value.

  ---

You are returned to the Add or Modify Collection Manager window.

Step 4   From the Add or Modify Collection Manager window, click OK.

The Add or Modify Collection Manager window closes and you are returned to the Configure Collection Manager window.

Step 5   Close the window after viewing.

Adding a Collection Manager

You might want to add another CM (remote CM) to your network thus providing a more distributed architecture while off loading the SLM server. After you have installed a remote CM, you must configure it using the SLM administrative GUI.

Note   The remote CM must be purchased separately. Contact your sales representative for more information.

Before You Begin

• Verify that you have met the system requirements. (See the chapter "Product Overview," in Installing Service Level Manager on Windows 2000, Windows NT, and Solaris.
  
  
• See the chapter "Installing and Uninstalling Remote Collection Managers," in Installing Service Level Manager on Windows 2000, Windows NT, and Solaris.
  
  

Procedure

The Configure Collection Manager window opens. (See Figure 6-5.)

Step 2   Click Add to add a remote CM to your network. You can also use the shortcut keys.

---

Note   The Add or Modify Collection Manager window is also used to modify existing CMs configured on the network. For more information, see "M odifying a Collection Manager."

---

The Add or Modify Collection Manager window (for a Remote CM) opens. (See Figure 6-6.)

Note   The Add or Modify Collection Manager window elements appear differently if you only have the local CM installed.

Table 6-4 defines the Add or Modify Collection Manager window elements.

Step 3   Enter the information in the fields provided.

---

Note   If you have not already set the username and password, see the chapter "Setting Up Remote Collection Managers," in Installing Service Level Manager on Windows 2000, Windows NT, and Solaris.

---

Step 4   Select the device(s) to assign to the newly added CM, then click the >> button.

---

Note   To help you manage your device selection, you can select a device type using the View drop-down list box, which displays only those device types in the left column.

---

The selected devices are moved from the left column to the Devices for this manager column (right column), and reassigned to the new CM.

Step 5   Click OK. You can also use the shortcut keys.

The Add or Modify Collection Manager window closes and you are returned to the Configure Collection Manager window with the new information displayed.

Testing Connectivity (Remote CM)

Procedure

The Add or Modify Collection Manager window opens. (See Figure 6-7.)

---

Note   The Add or Modify Collection Manager window elements appear differently if you only have the local CM installed.

---

Step 2   Click Test Connectivity. You can also use the shortcut keys.

The Test Manager Connectivity dialog box appears. (See Figure 6-8.)

Table 6-5 defines Test Manager Connectivity dialog box elements.

Step 3   Do one of the following:

• Click OK to test the connection using the default value. You are prompted that your connection was successful. Click OK.
  
• Modify the timeout value, then click OK to test the connection using the new value. You are prompted that your connection was successful. Click OK.
  
• Click Cancel to return to the Add or Modify Collection Manager window.
  

  ---

  Note   If you do not change the timeout value, clicking OK or Cancel recognizes the default timeout value.

  ---

You are returned to the Add or Modify Collection Manager window.

Step 4   From the Add or Modify Collection Manager window, click OK.

The Add or Modify Collection Manager window closes and you are returned to the Configure Collection Manager window.

Step 5   Close the window after viewing.

What To Do if Connectivity Fails

If your connection is not successful, verify the following:

• On the SLM server:
  
  
  • Hostname or username and password fields are correctly entered in the Add or Modify Collection Manager window.
    
    
• On the remote CM server:
  
  
  • The remote CM server is up and running.
    
    
  • The remote CM name can be accessed from the SLM server.
    
    
  • A user with System Admin or Network Admin privileges has been added.
    
    
• On the network:
  
  
  • Connectivity between the SLM server and remote CM (ping, telnet, HTTP).
    
    

Viewing Collection Manager Status

Viewing CM status allows you to check the status of all CMs configured on your network. It provides the following information for each CM:

• Software status—lists CM modules and versions
  
  
• Collection status—provides information on number of jobs and device pairs monitored by the CM
  
  

  ---

  Note   It is recommended that you view CM status after adding an additional CM to verify it is connected and running.

  ---

Procedure

The Collection Manager Status window opens. (See Figure 6-9.)

Table 6-6 defines the Collection Manager Status window elements.

Step 2   Close the window after viewing CM status.

Modifying a Collection Manager

There are several reasons for modifying a CM:

• You might want to set another CM as a default device.
  
  
• You might want to reassign source devices to another CM for data collection.
  
  
• You might want to remove a CM from your network.
  
  
• You might want to change the username or password.
  
  

If source devices are reassigned to another CM, SLM deletes the collection request from the old CM, then sets up a new collection request on the new CM. This results in SA Agent operation changes to the source device. The setup and tear-down changes affect the ability to maintain data collection for that time, which creates a gap when report information is viewed. Your SLCs and SLAs, however, remain intact.

Before You Begin

• Consider your CM setup carefully when associating source devices for polling. Changing to a different CM results in gaps in the collected data.
  
  
• Be aware of administrative overhead costs. Reduce network traffic by installing the CM near the devices that they are responsible for monitoring.
  
  

Setting a New Collection Manager As Default

SLM requires at least one CM for monitoring SLA device pairs. The embedded CM (localhost), which is automatically installed on the local SLM server, serves this purpose. The local CM is the default device responsible for monitoring all device pairs that are not assigned to a particular CM. You cannot delete the local CM. In addition, you cannot delete any CM set as default.

If you want to delete a CM set as default, you must first reassign the default setting to another CM. If you set another CM as default, any newly defined device pairs are assigned to it. Previously assigned device pairs remain unchanged.

Note   SLA device pairs already defined and assigned to a default CM are not reassigned when a new CM is set to default.

Procedure

In this example, you want to change the default setting from the local CM (localhost) to another CM (slam-u1).

The Configure Collection Manager window opens. (See Figure 6-10.)

Table 6-7 defines the Configure Collection Manager window elements.

Step 2   Select the CM (slam-u1) from the Collection Managers column, then click Select as Default.

A dialog box prompts you to verify the request.

Step 3   Click Yes.

The newly selected CM is shown in bold text, confirming it as the default CM.

Reassigning Devices

SLM allows you to modify source devices assigned to a CM. You have the option of using two different windows for this purpose, depending on where you are working in the SLM application.

Tips If you have only two CMs installed, see "Reassigning Source Devices to Another Collection Manager."

Note   SLA device pairs already defined and assigned to a default CM are not reassigned when a new CM is set to default.

Procedure

In this example, you have three CMs installed and you want to reassign devices from the nondefault CM (209.165.200.224) to another nondefault CM (slam-u1).

The Reassign Devices window opens. (See Figure 6-11.)

Table 6-8 defines the Reassign Devices window elements.

Step 2   Select the source device(s) to reassign from the View drop-down list box.

Step 3   Assign the new CM to the source devices using the Assign selected device(s) drop-down list box, then click Apply or use the shortcut keys.

A dialog box prompts you to verify the request.

Step 4   Click Yes.

The newly assigned CM is shown as the assigned CM for the devices selected.

Step 5   Close the Reassign Devices window.

Reassigning Source Devices to Another Collection Manager

Note   If source devices are reassigned to another CM, the ability to maintain data collection for that time is affected, which results in a gap when report information is viewed.

Before You Begin

Consider the following situations when reassigning source devices to another CM:

• You want to reassign devices from your nondefault CM to the default CM. See "Reassigning Devices to a Collection Manager Set As Default (2 CMs)."
  
  
• You want to reassign devices from your default CM to a nondefault CM. See "Reassigning Devices to a Collection Manager Not Set As Default (2 CMs)."
  
  
• You want to reassign devices from your nondefault CM to another nondefault CM. See "Reassigning Devices to a Collection Manager Not Set As Default (3+ CMs)."
  
  

Reassigning Devices to a Collection Manager Set As Default (2 CMs)

This procedure assumes you have two CMs configured on your network and you want to reassign source devices from a nondefault CM to a default CM.

Note   You can also reassign these source devices by selecting Service Level Management > Administration > Collection Manager > Reassign Devices from the CiscoWorks2000 Server desktop. See "Reassigni ng Devices."

Note   SLA device pairs already defined and assigned to a default CM are not reassigned when a new CM is set to default.

Procedure

In this example, you want to reassign devices from the nondefault CM (slam-u1) to the default CM (localhost).

Step 2   Select the nondefault CM (slam-u1) listed in the Collection Manager column, then click Modify.

The Add or Modify Collection Manager window opens. Use this window to reassign source devices. (See Figure 6-12.)

Table 6-9 defines the Add or Modify Collection Manager window elements.

Step 3   Update any information in any of the fields if needed (for example, if your password has changed).

Step 4   Select devices to reassign from the Devices for this manager column (right column), then click the << button.

The selected devices are moved to the left column, which represents the default CM.

Step 5   Click OK.

The Add or Modify Collection Manager window closes and you are returned to the Configure Collection Manager window with the modified information listed in the Collection Manager Information field.

Step 6   Close the Configure Collection Manager window.

Note   All jobs are moved to the newly assigned CM.

Reassigning Devices to a Collection Manager Not Set As Default (2 CMs)

This procedure assumes you have two CMs configured on your network and you want to reassign source devices from the default CM to a nondefault CM.

Note   You can also reassign these source devices by selecting Service Level Management > Administration > Collection Manager > Reassign Devices from the CiscoWorks2000 Server desktop. See "Reassigni ng Devices."

Note   SLA device pairs already defined and assigned to a default CM are not reassigned when a new CM is set to default.

Procedure

In this example, you want to reassign devices from the default CM (localhost) to the nondefault CM (slam-u1).

Step 2   Select the nondefault CM (slam-u1), then click Modify.

The Add or Modify Collection Manager window opens. Use this window to reassign source devices. (See Figure 6-13.)

Table 6-10 defines the Add or Modify Collection Manager window elements.

Step 3   Update any information in any of the fields if needed. (for example, if your password has changed).

Step 4   Select devices from the left column to reassign, then click the >> button.

The selected devices are moved from the left column to the Devices for this manager column (right column), and reassigned to the new CM (slam-u1).

Step 5   Click OK.

The Add or Modify Collection Manager window closes and you are returned to the Configure Collection Manager window with the modified information listed in the Collection Manager Information field.

Step 6   Close the Configure Collection Manager window.

Note   All jobs are moved to the newly assigned CM.

Reassigning Devices to a Collection Manager Not Set As Default (3+ CMs)

This procedure assumes you have three or more CMs configured on your network and you want to reassign source devices from a nondefault CM to another nondefault CM.

Note   You can reassign devices to any CM using the Reassign Devices window; however, using this method instead of the method described for the other scenarios might take longer.

Procedure

In this example, you have three CMs installed and you want to reassign devices from the nondefault CM (209.165.200.224) to another nondefault CM (slam-u1).

Note   SLA device pairs already defined and assigned to a default CM are not reassigned when a new CM is set to default.

The Reassign Devices window opens. (See Figure 6-14.)

Table 6-11 defines the Reassign Devices window elements.

Step 2   Select the source device(s) to reassign from the View drop-down list box.

Step 3   Assign the new CM to the source devices using the Assign selected device(s) drop-down list box, then click Apply or use the shortcut keys.

A dialog box prompts you to verify the request.

Step 4   Click Yes.

The newly assigned CM is shown as the assigned CM for the devices selected.

Step 5   Close the Reassign Devices window.

Note   All jobs are moved to the newly assigned CM.

Disabling the Local Collection Manager

You might want to off load jobs from the local CM and distribute polling to a remote CM. Although the local CM cannot be deleted, you can disable it. To do this:

• Add a remote CM to your network, if you have not already done so.
  
  
• Reassign all devices to the remote CM.
  
  
• Set the remote CM to default.
  
  

  ---

  Note   You have the option to stop the CM process from running on the SLM server. From the CiscoWorks2000 Server desktop, select Server Configuration > Administration > Process Management > Stop Process. Select "CollectionMgr" from the drop-down list box, then click Finish.

  ---

Changing Passwords

It is recommended that you change the password from the factory-setting "admin" to something new to ensure system security. This is the password used when configuring CMs using the administrative GUI windows.

To do this, see the chapter "Migrating SLM Files," in Installing Service Level Manager on Windows 2000, Windows NT, and Solaris.

Removing a Collection Manager

As your network changes, you might need to remove a CM. This can be done without disturbing any jobs; however, certain conditions must apply.

• You cannot remove the local CM (localhost).
  
  
• You cannot remove a CM set as default. You must first assign another CM as default.
  
  

Three basic steps are applied when preparing to remove a remote CM. (See Table 6-12.)

This section provides three scenarios for removing a CM:

• Removing a Collection Manager Set As Default (2 CMs)
  
  
• Removing a Collection Manager Set As Nondefault (2 CMs)
  
  
• Removing a Collection Manager Set As Nondefault (3+ CMs)
  
  

Removing a Collection Manager Set As Default (2 CMs)

SLM does not allow you to remove a remote CM set as default. As a result, you must first assign another CM as the default device.

Before You Begin

• Add a remote CM if you have not already done so. (See "Adding a Collection Manager.")
  
  

  ---

  Note   You cannot remove the local CM (localhost) installed on the SLM server, and you cannot remove a remote CM set as default.

  ---

Procedure

In this example, you want to remove the default CM (slam-u1).

The Configure Collection Manager window opens. (See Figure 6-15.)

Table 6-13 defines the Configure Collection Manager window elements.

Step 2   Select the CM from the Collection Managers column that you want to set as default (localhost), then click Select as Default.

A dialog box prompts you to verify the request.

Step 3   Click Yes.

The newly selected CM is listed in bold, designating it as the new default CM.

Step 4   Select the CM that you want to remove, (slam-u1), then click Delete.

The CM is deleted from the Collection Managers column. All previously associated source devices and jobs are reassigned to the new default CM (localhost).

Removing a Collection Manager Set As Nondefault (2 CMs)

This procedure assumes you have two CMs configured on your network and you want to remove the nondefault CM.

Procedure

In this example, you want to remove the remote CM (slam-u1) from the network.

The Configure Collection Manager window opens. (See Figure 6-16.)

Table 6-14 defines the Configure Collection Manager window elements.

Step 2   Select the nondefault CM (slam-u1) from the Collection Managers column, then click Delete.

A dialog box prompts you to verify the request.

Step 3   Click Yes.

The CM is deleted from the Collection Managers column. All previously associated source devices and jobs are reassigned to the default CM (localhost).

Removing a Collection Manager Set As Nondefault (3+ CMs)

This example assumes you have two remote CMs configured on your network and you want to remove a nondefault CM, but you want to reassign the source devices to another nondefault CM.

Procedure

In this example, you want to remove the remote CM (209.165.200.224) from the network, but you want to reassign the devices to another remote CM (slam-u1).

The Reassign Devices window opens. (See Figure 6-17.)

Table 6-15 defines the Reassign Devices window elements.

Step 2   Select the source device(s) to reassign from the View drop-down list box.

Step 3   Assign the new CM to the source devices using the Assign selected device(s) drop-down list box, then click Apply or use the shortcut keys.

A dialog box prompts you to verify the request.

Step 4   Click Yes.

The newly assigned CM is shown as the assigned CM for the devices selected.

Step 5   Close the Reassign Devices window.

Step 6   From the CiscoWorks2000 Server desktop, select Service Level Management > Administration > Collection Manager > Configure Collection Manager.

The Configure Collection Manager window opens.

Step 7   Select the CM you want to delete.

Step 8   Click Delete.

A dialog box prompts you to verify the request.

Step 9   Click Yes.

The selected CM is deleted from the list of configured CMs. All previously associated source devices and jobs are reassigned to the new CM.