Cisco Cisco Prime Infrastructure 3.0 White Paper

 

 

© 2015 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. 

Page 34 of 83 

If you want to discover all of the subnets but would like to have a way to import information on certain devices 

based on their IP address, system location, type of device, or DNS, you can use filters to do just that. 

 TIP: If you are running discovery for the first time, pick a smaller range or hop count to begin with. Do not use 

filters in this discovery. Once the results are what you expect, go back and edit that profile to add filters as needed. 

Credentials are also an important part of the discovery. Please refer to the credential matrix from the Protocol 

Check section and enter the credentials appropriately. If this is not done, devices in the Device Work Center will 
error out with “Managing with Credential Errors.” You can configure multiple community strings for the same 

network. This really helps to manage multiple devices without having to worry about which community is configured 

on what device. 

 

For example, in the figure above, you could add another SNMP string for the 10.1.2.

*

 network in addition to the one 

already configured. 

 

The last thing to configure before we run discovery is the preferred management IP. Once the devices are 

discovered and added to the inventory, how do you want to manage them? Do you want to see the device list with 

DNS, loopback IP, or local hostname configured on the devices (also called sysName)? If DNS is not used on your 

network devices, go ahead and select sysName. If devices have a specific management VLAN and all the devices 

have loopback configured for that, it would be a good idea to use that. DNS is the last choice as the device names 

become very long and it clutters up the device selector.