Installation Guide for IP Communications Operations Manager
Getting Started
Downloads: This chapterpdf (PDF - 356.0KB) The complete bookPDF (PDF - 0.97MB) | Feedback

Getting Started

Table Of Contents

Getting Started

Configuring Operations Manager to Monitor Devices

Supported NMS Environments for Device Import

Sharing the DCR with Other CiscoWorks Applications

Scenario—Operations Manager in a DCR Management Domain

Configuring the DCR in Master and Slave Mode

Adding Devices to the DCR from Operations Manager

Running Operations Manager Physical Discovery

Configuring Automatic or Manual Device Selection in Operations Manager

Adding Devices Manually from the DCR to Operations Manager

Verifying Devices Added to Operations Manager

Starting the Service Level View

Scheduling Inventory Collection

Editing the Device Inventory Collection Schedule

Adding a Phone Discovery Schedule

Troubleshooting Device Discovery

Starting Operations Manager

Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone

Understanding and Configuring Security

Supported NMS Integration

Configuring SNMP Trap Receiving and Forwarding

Updating the SNMP Trap Receiving Port

Enabling Devices to Send Traps to Operations Manager

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons

Configuring SNMP Trap Forwarding

Viewing Alerts

What's Next?


Getting Started


This section provides a minimum number of steps for setting up IP Communications Operations Manager (Operations Manager) and viewing diagnostic results. It includes:

Configuring Operations Manager to Monitor Devices

Starting Operations Manager

Understanding and Configuring Security

Supported NMS Integration

Configuring SNMP Trap Receiving and Forwarding

Viewing Alerts

What's Next?

Configuring Operations Manager to Monitor Devices

Operations Manager obtains devices to monitor from the CiscoWorks Common Services Device and Credentials Repository (DCR). The DCR is a common repository of devices and their credentials for use by individual applications.

Before Operations Manager can start to monitor your network:

You need to configure the DCR and Operations Manager device selection. Configuring DCR involves understanding the options and deciding what makes the most sense for your site.

Operations Manager must complete inventory collection.

Table 3-1 lists all the steps you need to complete.

Table 3-1 How to Start Monitoring Devices

 
Description
References

Step 1 

Add devices to the DCR.

You have three options:

 

Use Operations Manager to add devices to the DCR. This is called physical discovery.

Adding Devices to the DCR from Operations Manager

Share a master repository with applications on other servers.

Sharing the DCR with Other CiscoWorks Applications

Bulk import using a seed file to import devices into the DCR.

See the instructions in the Common Services online help.

Step 2 

Configure device selection.

Configuring Automatic or Manual Device Selection in Operations Manager

Step 3 

Allow inventory collection to complete and start to monitor devices.

 

Step 4 

Verify device import by using the Service Level View.

Verifying Devices Added to Operations Manager

Supported NMS Environments for Device Import

DCR enables you to share device lists with other applications as follows:

You can import devices to the DCR from:

A network management system (NMS)—DCR supports import from remote NetView and HP OpenView installations.(Supported versions are displayed on the user interface.)

A file—Files can be exported from another product and formatted for import to the DCR. The file format is documented in User Guide for CiscoWorks Common Services.


Note Operations Manager physical device discovery also adds the devices it finds to the DCR.


You can configure a DCR server to host a master list of all devices and share the list with clients (other instances of DCR in the same management domain that are configured as slaves).

Sharing the DCR with Other CiscoWorks Applications

DCR enables CiscoWorks network management applications to share a device list and credentials through a client-server mechanism. On the Operations Manager server, by default, DCR is configured as a standalone or independent repository.

Optionally, you can configure the DCR to participate in a management domain that includes:

One shared master repository.

One or more client repositories that are exact replicas and remain synchronized with the master repository.

The following scenario illustrates using Operations Manager in a DCR management domain.

Scenario—Operations Manager in a DCR Management Domain

This scenario illustrates one possible way to configure Operations Manager and another CiscoWorks application to share a device list and device credentials using DCR.

Operations Manager (which must be installed on a dedicated system) and CiscoWorks Resource Manager Essentials (RME) are installed on separate systems. On the RME system, DCR is configured as a server (master). On the Operations Manager system, DCR is configured as a client (slave) to the DCR server on the RME system. Additionally, the Operations Manager system is configured for manual selection of devices from DCR.

If you import devices to the DCR on the RME system, the devices are also added to the DCR client on the Operations Manager system. With Operations Manager configured for manual selection of devices, devices are not added to Operations Manager inventory unless you manually select them.

Configuring the DCR in Master and Slave Mode

By default, the DCR on the Operations Manager server is configured as a standalone or independent repository. If you decide to configure the DCR for Operations Manager as a master or a slave, the procedures for doing so are thoroughly documented in online help and in User Guide for CiscoWorks Common Services. You must perform prerequisite tasks and you must configure the master and the slave in the proper order. The following procedure can help you get started and locate the information you need in the online help.


Note To start Operations Manager, see Starting Operations Manager.



Step 1 From the Operations Manager home page, click the CiscoWorks link in the top right corner of the page. The CiscoWorks home page appears in another window.

Step 2 On the CiscoWorks home page, select Common Services > Device and Credentials > Admin. The Admin page appears.

Step 3 Select Mode Settings from the TOC in the left-hand pane. The Mode Settings window appears.

Step 4 Click the Help link in the top right corner of the page. Find the instructions for completing the master-slave configuration prerequisites. These include:

Adding a peer server user on the system with the master DCR.

Creating a System Identity User on the system with the slave DCR.

Copying security certificates.

Follow the instructions in the online help to complete the prerequisites and to configure a master and a slave in the correct order.


Adding Devices to the DCR from Operations Manager

Operations Manager adds devices to the DCR through physical discovery.


Note To add devices to the DCR using bulk import (importing from an NMS or from a file), use the instructions in the Common Services online help.


Running Operations Manager Physical Discovery


Step 1 Select Devices > Device Management. The Device Management: Summary page appears.

Step 2 Click the Configure button next to the Last Discovery and Next Discovery fields. The Discovery page appears.

Step 3 Enter data described in the following table.

Field
Action/Description
Seed Devices

Enter a comma-separated list of IP addresses, or select the Use all devices currently in Device and Credentials Repository check box.

Ping Sweep

(Optional) This is an alternative to using seed device-based discovery.

Check the Use Ping Sweep check box and specify a comma-separated list of IP address ranges using the /netmask specification.

For example, use 172.20.57.1/24 to specify a ping sweep range starting at 172.20.57.1 and ending at 172.20.57.255.

IP Address

(Optional) Enter comma-separated IP addresses or IP address ranges for devices that you want to:

Include—In the auto-discovery process.

Exclude—From the auto-discovery process.

You can use wildcards when specifying the IP address range.

An asterisk (*) denotes the octet range of 1-255. Also, the octet range can be constrained using the [xxx-yyy] notation.

For example:

To include all devices in the 172.20.57/24 subnet in the auto-discovery process, enter an include filter of 172.20.57.*.

To exclude devices in the IP address range of 172.20.57.224 - 172.20.57.255 from the auto-discovery processing, enter an exclude filter of 172.20.57.[224-255].

Both types of wildcards can be used in the same range specification; for example, 172.20.[55-57].*. If both include and exclude filters are specified, the exclude filter is applied first, before the include filter. Once a filter is applied to an auto-discovered device, no other filter criterion will be applied to the device. If a device has multiple IP addresses, the device will be processed for auto-discovery as long as it has one IP address that satisfies the include filter.

DNS Domain

(Optional) Enter comma-separated DNS domain names for devices that you want to:

Include—In auto-discovery processing.

Exclude—From auto-discovery processing.

The DNS names can be specified using wildcards. An asterisk (*) matches any combination of mixed uppercase and lowercase alphanumeric characters along with the hyphen (-) and underscore (_) characters of an arbitrary length. A question mark (?) matches a single uppercase or lowercase alphanumeric character or a hyphen or an underscore character. For example:

*.cisco.com matches any DNS name ending with .cisco.com.

*.?abc.com matches any DNS name ending with .aabc.com, or .babc.com, etc.

SysLocation

(Optional) Enter comma-separated strings that will match the string value stored in the sysLocation OID in MIB-II, for devices that you want to:

Include—In auto-discovery processing.

Exclude—From auto-discovery processing.

The location strings can be specified using wildcards. An asterisk (*) matches up to an arbitrary length any combination of mixed uppercase and lowercase alphanumeric characters, hyphen (-), underscore (_), and white space (spaces and tabs). A question mark (?) wildcard matches a single occurrence of any of the above characters. For example, a SysLocation filter of San *, will match all SysLocation strings starting with San Francisco, San Jose, etc.

Run

Select a radio button and enter the schedule:

Now—Select to run immediately.

Daily—Enter time and select days on which to run (Sun, Tue...Sat).

Weekly—Enter the weekly frequency (every N weeks), the time, and the day on which to run.


Step 4 Click OK. Physical discovery starts to run and takes some time to complete. (Check the status of discovery on the Device Management: Summary page.)


Configuring Automatic or Manual Device Selection in Operations Manager

To add devices to Operations Manager inventory from the DCR, you need to configure Operations Manager device selection as one of the following:

Automatic—Add supported devices to inventory as they are added to the DCR. (Automatic selection enables you to also maintain a list of devices to exclude from Operations Manager.)

Manual—Add only the devices that you select.


Note If you are running the synchronization process for the first time, it may take several hours for Operations Manager to collect inventory for all of the devices, depending on how many devices are being added to Operations Manager.



Note Devices must exist in the DCR before you can add them to Operations Manager.



Step 1 Select Devices > Device Management. The Device Management: Summary page appears.

Step 2 Click the Configure button next to the Device Selection field. The Device Selection page appears.

Step 3 Activate the Automatic radio button.

Step 4 Click Apply. Operations Manager will be synchronized with the DCR; any DCR devices currently not in Operations Manager will be added. Operations Manager will perform inventory collection for the new devices that are being added.


Adding Devices Manually from the DCR to Operations Manager

If you configured Operations Manager for automatic device selection, you do not need to perform this procedure. With manual device selection, you need to manually select devices to monitor. You will need to do this periodically after devices have been added to the DCR. For example, if you run Operations Manager physical discovery on a weekly basis, you should consider checking for new devices that you want to monitor after discovery completes.


Note Devices must exist in the DCR before you can add them to Operations Manager.



Step 1 Select Devices > Device Management.

Step 2 Click the Configure button next to the Device Selection field. The Device Selection page appears.

Step 3 Select the Manual radio button. All devices that are not in Operations Manager inventory are available through the device selector.

Step 4 Select devices in either of the following ways:

Entering device names or IP addresses in the Device Display Name, and clicking Filter.

Using the group selector.

Step 5 If you want to see the devices you have selected, click the Selection tab, and a list of devices appears.

Step 6 Click Select. Operations Manager will perform inventory collection on the devices that are being added.


For more information, see User Guide for IP Communications Operations Manager.

Verifying Devices Added to Operations Manager

One way you can verify that your devices have been added to Operations Manager inventory is by looking at the Service Level View. This also provides you with quick access to many of the Operations Manager tools.

If you find that problems have occurred during inventory collection, see Troubleshooting Device Discovery.

Starting the Service Level View


Step 1 Select Monitoring Dashboard > Service Level View. The Service Level View display appears, displaying a logical topology view of your IP telephony implementation.


For more information, see User Guide for IP Communications Operations Manager or the Operations Manager online help.

Scheduling Inventory Collection

There are separate inventory collection schedules for devices and phones. There is only one inventory collection schedule for devices. You cannot create additional schedules; you can only edit the existing schedule. For IP phones, you can create multiple inventory collection schedules.

On the Inventory Collection Schedule page (Devices > Device Management > Device), you can edit, suspend, or resume the device inventory collection schedule. (See Editing the Device Inventory Collection Schedule.)

On the IP Phone Discovery Schedule page (Devices  > Device Management  > IP Phone Details), you can add, edit, or delete the IP Phone discovery schedules. (See Adding a Phone Discovery Schedule.)

Editing the Device Inventory Collection Schedule


Step 1 Select Devices > Device Management > Device. The Device Inventory Collection page appears.

Step 2 Click Edit. The Inventory Collection Schedule: Edit page appears.

Step 3 Change the desired scheduling information.

Step 4 Click OK.

Step 5 Click Yes.


Adding a Phone Discovery Schedule


Step 1 Select Devices > Device Management > IP Phone Details. The IP Phone Discovery Schedule page appears.

Step 2 Click Add. The Add Schedule dialog box appears.

Step 3 Enter the following:

A name for the discovery schedule

The day of the week when you want discovery to occur

The time of the day when you want discovery to occur

Step 4 Click OK.


Troubleshooting Device Discovery

Problems might occur during physical discovery (Operations Manager adds devices to the DCR) and can also occur during inventory collection (Operations Manager adds devices to its inventory for monitoring).

To troubleshoot device inventory collection, try the following:

If a device is not responding, confirm all device credentials and readd the device. See Changing Device Credentials.

If device inventory collection times out for several devices, increase SNMP timeout settings. See Modifying SNMP Timeout and Retries.

View device error information on the View/Refresh/Delete Device page. See Performing Inventory Collection on a Device.

Verify that the device is operational during the import and that it supports MIB II.

Check the reason for devices being in the Unreachable state. See Understanding Inventory Collection Messages.

After troubleshooting the problem, check the device status. See Verifying Devices Added to Operations Manager.

Changing Device Credentials

You change device credentials using Common Services DCR. See the Common Services online help.

Modifying SNMP Timeout and Retries

If an SNMP query does not respond in time, Operations Manager times out. Operations Manager retries contacting the device for as many times as you indicate. The timeout period is doubled for every subsequent retry.

For example, if the timeout value is 4 seconds and the retries value is 3 seconds, Operations Manager waits 4 seconds before the first retry, 8 seconds before the second retry, and 16 seconds before the third retry.

The SNMP timeout and retry values are global settings. Change these values as follows:


Step 1 Select Devices > Device Management > SNMP Configuration. The SNMP Configuration page appears.

Step 2 Select a new SNMP timeout setting. The default is 4 seconds.

Step 3 Select a new Number of Retries setting. The default is 3 retries.

Step 4 Click Apply. Click Yes to confirm.


Performing Inventory Collection on a Device

Through the View/Refresh/Delete Devices page, you can launch inventory collection for devices or device groups. When inventory collection takes place, if there are any changes to a device or group configuration, the new settings will overwrite any previous settings.

Inventory collection occurs only for active devices. Operations Manager does not collect inventory for suspended devices. If some of the devices you are selecting for inventory collection are suspended devices, Operations Manager displays messages indicating that only the active devices will go through discovery.


Note Do not confuse the Operations Manager inventory collection process with the DCR synchronization process. Operations Manager inventory collection is a process that affects only the Operations Manager inventory.



Step 1 Select Devices > Device Management > View/Refresh/Delete. The View/Refresh/Delete Devices page appears.

Step 2 Select the device or group for which you want to run inventory collection.

Step 3 Click Update. Inventory collection is started.


Understanding Inventory Collection Messages

Table 3-2 lists messages that might be shown for devices that are in the Unreachable state.

Table 3-2 Inventory Collection Error Messages 

Message
Meaning
Action

SNMP Timeout

The device is in the Unreachable state because the SNMP read-only community string for the device is incorrect.

See Changing Device Credentials to enter the correct read community string for the device.

Others: Missing IP Address or Data Collector Timeout

The device is in the Unreachable state because of some other reason. It could be that DNS resolution for the device failed or the data collector timed out.

Click the device on the Rediscover/Delete Devices page. The error message displays the exact problem.

If the IP address is missing:

Readd the device with the correct IP address.

or

Make sure that Operations Manager can resolve the device name: try adding the domain name as part of the device name.

If the data collector times out, restart the daemon manager to get all data collectors in sync.


Starting Operations Manager

To start Operations Manager, from the Windows desktop select Start > Programs > IPC Operations Manager 1.0 and Service Monitor 1.0 > IPC Operations Manager 1.0 and Service Monitor 1.0.


Note If Enhanced Security is enabled on the Windows 2003 system, you must add the Operations Manager home page to the Internet Explorer Trusted Sites Zone. You will not be able to access the IP Communications Operations Manager home page until it is added to the trusted sites.


Adding the Operations Manager Home Page to the Internet Explorer Trusted Site Zone

If Enhanced Security is enabled on the Windows 2003 system, you must perform the following procedure before you can access the Operations Manager home page.


Step 1 Open Operations Manager and select Start > Programs > IPC Operations Manager 1.0 and Service Monitor 1.0 > IPC Operations Manager 1.0 and Service Monitor 1.0.

Step 2 From the File menu, select Add this site to.

Step 3 Click Trusted Sites Zone.

Step 4 In the Trusted Sites dialog box, click Add to move the site to the list.

Step 5 Click Close.

Step 6 Refresh the page to view the site from its new zone.

Step 7 Check the Status bar of the browser to confirm that the site is in the Trusted Sites Zone.


Understanding and Configuring Security

Operations Manager supports the following security-related mechanisms:

SNMPv3 protocol (Authentication/No-Privacy option)—Operations Manager supports the Authentication/No-Privacy option between the server and the device.

Security on the CiscoWorks server—You can configure the following aspects of security for the server on which Operations Manager resides:

Secure Socket Layer (SSL)—Operations Manager can use SSL protocol between the server and the browser. You can enable and disable SSL for the server. If you enable SSL, you should set up a self-signed security certificate to enable SSL communication. For more information, see User Guide for IP Communications Operations Manager.

Local security or Cisco Secure ACS—Access to tasks within Operations Manager is either controlled by local security, or provided by Common Services or Cisco Security ACS. Local security is enabled on the server by default. Operations Manager supports integration with Cisco Secure ACS. For more information, see Configuring Operations Manager with Cisco Secure ACS.


Note For more information, see User Guide for IP Communications Operations Manager.


Supported NMS Integration

Operations Manager supports integration with network management systems (NMSs) as follows:

Operations Manager listens for traps from managed devices on port 162 (the default). If another NMS on the system with Operations Manager uses port 162:

The installation script warns you that this is the case.

You must specify a different port for Operations Manager trap receiving after the installation completes. See Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons.

Operations Manager forwards traps to destinations that you specify, as follows:

To forward pass-through traps, see Configuring SNMP Trap Receiving and Forwarding.

To forward processed traps, see "Managing SNMP Trap Notifications" in the "Using Notification Services" chapter of User Guide for IP Communications Operations Manager.

For more information on pass-through and processed traps, see the appendix "Processed and Pass-through Traps, and Other Unidentified Traps and Events" in User Guide for IP Communications Operations Manager.

If the standard User Datagram Protocol (UDP) trap port (162) is being used by another NMS, you must configure Operations Manager SNMP trap receiving to use a different UDP port, such as port 9000. See Configuring SNMP Trap Receiving and Forwarding.

Configuring SNMP Trap Receiving and Forwarding

Operations Manager can receive traps on any available port and forward them to a list of devices and ports. This capability enables Operations Manager to easily work with other trap processing applications. However, you must enable SNMP on your devices and configure SNMP to send traps either directly to Operations Manager or to one of the following:

An NMS

A trap daemon

To send traps directly to Operations Manager, perform the tasks in Enabling Devices to Send Traps to Operations Manager. To integrate SNMP trap receiving with an NMS or a trap daemon, follow the instructions in Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons.

Updating the SNMP Trap Receiving Port

By default, Operations Manager receives SNMP traps on port 162. If you need to change the port (for example, to port 9000), you can do so.


Step 1 Select Administration > Preferences. The System Preferences page appears.

Step 2 In the Trap Receiving Port field, enter the port number.

Step 3 Click Apply.


For a list of ports that Operations Manager uses, see Verifying TCP and UDP Ports that Operations Manager Uses.

Enabling Devices to Send Traps to Operations Manager

Because Operations Manager uses SNMP MIB variables and traps to determine device health, you must configure devices to provide this information. For any Cisco devices that you want Operations Manager to monitor, SNMP must be enabled and the device must be configured to send SNMP traps to the Operations Manager server.

Make sure your devices are enabled to send traps to Operations Manager by using the command line or GUI interface appropriate for your device:

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

Enabling Cisco IOS-Based Devices to Send Traps to Operations Manager

For devices running Cisco IOS software, provide the following commands:

(config)# snmp-server [community string] ro
(config)# snmp-server enable traps
(config)# snmp-server host [a.b.c.d] traps [community string]

where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the Operations Manager server).

For more information, see the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Products & Solutions > Cisco IOS Software.

Step 3 Select the Cisco IOS Software release version used by your Cisco IOS-based devices.

Step 4 Select Technical Documentation and select the appropriate command reference guide.


Enabling Catalyst Devices to Send SNMP Traps to Operations Manager

For devices running Catalyst software, provide the following commands:

(enable)# set snmp community read-only [community string]
(enable)# set snmp trap enable all
(enable)# set snmp trap [a.b.c.d] [community string]

Where [community string] indicates an SNMP read-only community string and [a.b.c.d] indicates the SNMP trap receiving host (the Operations Manager server).

For more information, see the appropriate command reference guide.


Step 1 Log in to Cisco.com.

Step 2 Select Products & Solutions > Switches.

Step 3 Select the appropriate Cisco Catalyst series switch.

Step 4 Select Technical Documentation and select the appropriate command reference guide.


Integrating Operations Manager Trap Receiving with NMSs or Trap Daemons

You might need to complete one or more of the following steps to integrate SNMP trap receiving with other trap daemons and other Network Management Systems (NMSs):

Add the host where Operations Manager is running to the list of trap destinations in your network devices. See Enabling Devices to Send Traps to Operations Manager. Specify port 162 as the destination trap port.

If another NMS is already listening for traps on the standard UDP trap port (162), you must configure Operations Manager to use another port, such as port 9000. See Updating the SNMP Trap Receiving Port.

If your network devices are already sending traps to another management application, configure that application to forward traps to Operations Manager.

Table 3-3 describes scenarios for SNMP trap receiving and lists the advantages of each.

Table 3-3 Configuration Scenarios for Trap Receiving 

Scenario
Advantages

Network devices send traps to port 162 of the host where Operations Manager is running. Operations Manager receives the traps and forwards them to the NMS.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

Operations Manager provides a reliable trap reception, storage, and forwarding mechanism.

NMS continues to receive traps on port 162.

Network devices continue to send traps to port 162.

The NMS receives traps on default port 162 and forwards them to port 162 on the host where Operations Manager is running.

No reconfiguration of the NMS is required.

No reconfiguration of network devices is required.

Operations Manager does not receive traps dropped by the NMS.


Configuring SNMP Trap Forwarding

By default, Operations Manager does not forward unprocessed SNMP traps. However, you can configure it to do so.


Step 1 Select Administration  > Preferences. The System Preferences page appears.

Step 2 Under Trap Forwarding Parameters enter:

An IP address or DNS name for the server.

A port number on which the server can receive traps.

Step 3 Click the Apply button.


Viewing Alerts

You can view alerts using the monitoring dashboard displays. Select Monitoring Dashboard and choose from the following displays:

Service Level View

Alerts and Events

Service Quality Alerts

IP Phone Status

What's Next?

After you complete the tasks in this chapter, Operations Manager will be ready to monitor and analyze events and provide notification of alerts.

Table 3-4 summarizes how to continue setting up Operations Manager.

Table 3-4 Setting Up Operations Manager 

Task
Description

Configure views for the Monitoring Dashboard displays

Views are logical groupings of devices that appear in the Monitoring Dashboard displays (Service Level View, Alerts and Events, Phone Activities, and Service Quality Alerts). Whenever you create a new user-defined group on the Group Administration and Configuration page, a corresponding view is created.

Configure notifications

In addition to learning about alerts by monitoring the Monitoring Dashboard displays, you can subscribe users to receive e-mail and hosts to receive Operations Manager-generated SNMP traps in response to alerts.

Configure polling parameters and thresholds

Operations Manager provides default values for polling parameters and threshold values. However, you can update the values as needed for your network. You should plan to apply the changes when activity on the Operations Manager server is low.

By default, Operations Manager sets the voice utilization polling settings. If you want to use Operations Manager's performance monitoring capabilities, you must first enable voice utilization polling.

Configure purging

By default, Operations Manager purges the database daily at midnight. You can modify the schedule.

Configure inventory collection

Operations Manager provides a single default schedule for inventory collection. You can use that schedule, or you can suspend it.


To use Operations Manager more fully, you might want to perform additional configuration tasks. See the online help or User Guide for IP Communications Operations Manager for information on using and configuring Operations Manager.