List-Based Discovery

With list-based discovery, you explicitly specify (as a discovery seed) each node that NNMi should discover.

Note NNMi uses tenancy to support networks with overlapping address domains that may exist within static Network Address Translation (NAT), dynamic Network Address Translation (NAT), or Port Address Translation (PAT) areas of your network management domain. If you have such networks, put the overlapping address domains into different tenants (this is done using seeded discovery). See the NNMi help for more information.

Note If you are using NNMi to manage VMware Hypervisor-Based Virtual Networks, see the "Tenants within Virtual Environments" help topic in the Help for Administrators.

Tip If you plan to configure multi-tenancy, list-based discovery is the recommended discovery approach.

Benefits of using only list-based discovery include:

  • Provides very tight control over what NNMi manages.
  • Supports the specification of a non-default tenant at discovery time.
  • Simplest configuration.
  • Good for fairly static networks.
  • A good way to start using NNMi. You can add auto-discovery rules over time.

Disadvantages of using only list-based discovery include:

  • NNMi does not discover new nodes as they are added to the network.
  • You must provide the complete list of nodes to be discovered.