Administer > NNMi Discovery > Evaluate Discovery > Are All Connections and VLANs Correct? > NNMi Discovery and Duplicate MAC Addresses

NNMi Discovery and Duplicate MAC Addresses

The information in this section is shared with the NNMi help. If there are any changes to the content in this section, please contact Wendy Studinski to discuss the changes. The help file is located at SharedFilesSource\Content\Resources\Snippets\SharedFiles\Duplicate-MAC-addresses.flsnp

Discovery takes MAC Addresses into account for the following benefits:

  • Improves support for DHCP or other nodes that change IP addresses.
  • Improves node identity for nodes configured with duplicate IP addresses.
  • Improves support for devices that do not report hosted IP addresses.

During discovery, NNMi reads the Forwarding Database (FDB) tables from Ethernet switches within a network to help NNMi determine communication paths between network devices. NNMi searches these FDB tables for information about discovered nodes. When an NNMi management server finds FDB references to duplicate Media Access Control (MAC) addresses, it does the following:

  • If two or more discovered nodes contain an interface associated with the same Media Access Control (MAC) address within the same Tenant or with one of those nodes in Default Tenant and one in any other Tenant, NNMi disregards the communication paths reported for those duplicate MAC addresses in the FDB. This might result in missing connections on NNMi maps in network areas that include those duplicate MAC addresses.

    NNMi Advanced or NNMi Premium - Global Network Management feature: If two NNMi management servers discover nodes that contain an interface associated with the same Media Access Control (MAC) address, the Global NNMi management server's maps could be missing connections that are visible on the Regional NNMi management server's maps.

  • If a single node contains multiple interfaces that have the same MAC address, NNMi gathers all communication path information for those interfaces and displays that information on NNMi maps.

Forwarding Database (FDB) information can cause NNMi to establish wrong L2 Connections in the following cases:

  • When the FDB is configured as cache and contains obsolete data.
  • In network environments with hardware from a variety of vendors, each generating different and sometimes conflicting FDB data.

Optional: NNMi administrators can configure Discovery to ignore this FDB data for one Node Group.