Cisco Cisco Prime Unified Operations Manager 8.7 White Paper
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 35 of 112
• The DCR inventory—To view, select Devices > Device Credentials.
Deleting a device in Operations Manager (Devices > Device Management >
View/Rediscover/Delete) does not remove it from the DCR.
Deleting a device in the DCR (Devices > Device Credentials) removes it from both the
Operations Manager inventory and the DCR.
Once a device is in the DCR, you can select it to be monitored by Operations Manager.
Periodically, Operation Manager performs inventory collection, polling for relevant
information from the devices.
5.3.1 Network Discovery Options
5.3.1.1 CDP-Based Discovery
Operations Manager device discovery is based on CDP, route table, and ARP table using
a seed device. Operation Manager uses CDP neighbors, ARP table, and route table
entries to discover the network from the seed device.
a seed device. Operation Manager uses CDP neighbors, ARP table, and route table
entries to discover the network from the seed device.
5.3.1.2 Ping based discovery
You can choose to add a ping sweep (by selecting the use Ping Sweep check box) in
addition to or instead of the CDP, ARP table, and route table discovery process.
When using a ping sweep discovery, IP phones and other nonvoice devices (for example,
network printers, Sun servers, or PCs) with an IP address in the specified ping sweep
range will also be discovered. These devices are populated in the DCR and are placed in
the Unmanaged device state in Operations Manager.
Note that Operations Manager manages and discovers IP phones indirectly. Operations
Manager discovers IP phones through querying the Layer 2 switch (to which the phones
are connected) and the Cisco CallManager (to which the phones are registered).
Operations Manager does not directly manage the IP phones, since SNMP is not currently
supported on the IP phones. IP phones are discovered because they respond to an ICMP
ping.
To avoid populating the DCR with network printers and other nonvoice network devices,
use the IP Exclude filter on the Discovery page.
In IP telephony deployments, phones acquire their IP addresses from a DHCP server.
This DHCP server usually has a pool of IP addresses configured for IP phones. The IP
phone address pool can be specified in the IP exclude filter, thereby preventing IP phones
from being populated in the DCR.
Considerations for using the automatic discovery IP include and exclude filters are
described in more detail in Section 5.3.1.3.1.
addition to or instead of the CDP, ARP table, and route table discovery process.
When using a ping sweep discovery, IP phones and other nonvoice devices (for example,
network printers, Sun servers, or PCs) with an IP address in the specified ping sweep
range will also be discovered. These devices are populated in the DCR and are placed in
the Unmanaged device state in Operations Manager.
Note that Operations Manager manages and discovers IP phones indirectly. Operations
Manager discovers IP phones through querying the Layer 2 switch (to which the phones
are connected) and the Cisco CallManager (to which the phones are registered).
Operations Manager does not directly manage the IP phones, since SNMP is not currently
supported on the IP phones. IP phones are discovered because they respond to an ICMP
ping.
To avoid populating the DCR with network printers and other nonvoice network devices,
use the IP Exclude filter on the Discovery page.
In IP telephony deployments, phones acquire their IP addresses from a DHCP server.
This DHCP server usually has a pool of IP addresses configured for IP phones. The IP
phone address pool can be specified in the IP exclude filter, thereby preventing IP phones
from being populated in the DCR.
Considerations for using the automatic discovery IP include and exclude filters are
described in more detail in Section 5.3.1.3.1.