Brocade Network Advisor SAN + IP User Manual v12.1.0 - Manual (Page 137)

70 Brocade Network Advisor SAN + IP User Manual
53-1002949-01
IP discovery overview
4
Similarly, if you configure discovery to search for neighbor addresses (refer to “Configuring
advanced discovery profile preferences” on page 116), the third query scans the device’s SNMP
LLDP, FDP, and CDP tables. Any neighbor IP address is added to the list of candidate IP addresses
to probe. Discovery adds any IP address from the LLDP, FDP, and CDP tables to the list of candidate
IP addresses.
Discovery also tries to determine the host name of the device by requesting the Management
application server operating system to perform various mappings of the device IP addresses to
host names and host names back to IP addresses, using whatever mechanism the operating
system uses (typically Domain Name Server) to determine the host name for a device.
If discovery determines that the device is reachable and manageable, then discovery uses the full
set of SNMP queries to collect asset information from the device. Discovery then adds or updates
the device in the database and sends notification to other applications.
Rediscovery updates can occur using any of the following methods:
• Lazy polling.
• Adaptive discovery (triggered by snmp traps).
• Manual rediscovery (refer to “IP Rediscovery” on page 146).
Configuration requirements
Before configuring discovery, obtain the following information:
• SNMPv1 and SNMPv2c read-write community strings or SNMPv3 read-write credentials for the
devices to be included in discovery. Make sure that devices you want to manage have the
SNMP credentials configured. For more information, refer to
“IP SNMP credentials” on
page 83.
• Device IP addresses and subnets to probe during discovery. For more information, refer to
“Configuring address ranges” on page 104, “Adding user credentials” on page 89, and
“Defining global setting preferences” on page 97.
Discovery of IPv6 addresses
The Management application discovers both IPv4 and IPv6 addresses of devices that have the IPv6
MIB objects implemented. The Management application discovers IPv4 addresses of devices
running IPv6 that do not have IPv6 MIB support. For more information, refer to
“Defining global
setting preferences” on page 97.
NOTE
IronWare IPv6 devices must support the set of MIBs presented in Table 23 on page 71. To determine
IPv6 MIB object support on the device, refer to the release notes and user documentation for your
IPv6 product.
NOTE
Third-party IPv6 devices must support the set of MIBs presented in Table 24 on page 73.