Cisco Cisco Prime Unified Operations Manager 8.7 Libro blanco
All contents are Copyright © 1992–2006 Cisco Systems, Inc. All rights reserved.
Page 37 of 112
default *.*.*.*
Result
― Included
Included
Excluded
Case 3: Exclude filter not specified, so the exclude filter is not applied.
Device
― 14.14.14.14
20.20.20.20
12.12.12.12
Exclude Filter
Not specified
Not applied
Not applied
Not applied
Include Filter
14.*.*.*
Within range
Out of range
Out of range
Result
― Included
Excluded
Excluded
Case 4: No filters are specified, so all devices are included.
5.3.1.3.1.1 sysLocation Filter
The sysLocation filter is applied after the MIB II system table is queried from a device.
Like the IP address filter, you can set include and exclude filters. The exclude filter is
applied first. If the sysLocation of a device satisfies any of the specified exclude filters,
the device is filtered out. The include filter is applied only if no exclude filters apply to
the device. The device will be populated in the DCR if its sysLocation field matches one
of the include filters.
The sysLocation filter is applied after the MIB II system table is queried from a device.
Like the IP address filter, you can set include and exclude filters. The exclude filter is
applied first. If the sysLocation of a device satisfies any of the specified exclude filters,
the device is filtered out. The include filter is applied only if no exclude filters apply to
the device. The device will be populated in the DCR if its sysLocation field matches one
of the include filters.
5.3.1.3.1.2 DNS Domain Filter
The DNS filter works in a similar manner to the IP address and sysLocation filters. It
performs a DNS lookup with a given IP address to resolve a DNS name, then checks the
specified include or exclude filters with the DNS domain name. The exclude filter is
applied before the include filter.
If multiple filters are specified, the IP address filters are applied first. The sysLocation
filter is applied next, and finally, the DNS domain filter is applied. Because other filters
are not applied after a filter specification is satisfied for a device, you should not specify
a sysLocation filter and/or a DNS domain filter once the IP filters are specified. The
sysLocation filter and the DNS domain filters will be applied (in that order) only if the IP
address filters are not specified.
The DNS filter works in a similar manner to the IP address and sysLocation filters. It
performs a DNS lookup with a given IP address to resolve a DNS name, then checks the
specified include or exclude filters with the DNS domain name. The exclude filter is
applied before the include filter.
If multiple filters are specified, the IP address filters are applied first. The sysLocation
filter is applied next, and finally, the DNS domain filter is applied. Because other filters
are not applied after a filter specification is satisfied for a device, you should not specify
a sysLocation filter and/or a DNS domain filter once the IP filters are specified. The
sysLocation filter and the DNS domain filters will be applied (in that order) only if the IP
address filters are not specified.
5.3.1.4 Phone Discovery
Phone discovery is performed separately from device discovery. Phone discovery starts
after device discovery completes. In Operations Manager, go to Devices > Device
Management > Inventory Collection > IP Phone to check the status of the last
completed phone discovery.
When phones are discovered using a ping device discovery, those phones are placed in
the Unknown state.
after device discovery completes. In Operations Manager, go to Devices > Device
Management > Inventory Collection > IP Phone to check the status of the last
completed phone discovery.
When phones are discovered using a ping device discovery, those phones are placed in
the Unknown state.
5.3.1.5 Cisco Catalyst 6000 Discovery
When discovering a Cisco CallManager, Operations Manager discovers the trunk cards
on a Cisco Catalyst as gateways. If the Cisco Catalyst is not being monitored in
Operations Manager, the trunk cards will appear as grayed out gateways in the Service
on a Cisco Catalyst as gateways. If the Cisco Catalyst is not being monitored in
Operations Manager, the trunk cards will appear as grayed out gateways in the Service