Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Discover your network
- How Spiral Discovery Works
- Prerequisites for discovery
- Overlapping Address Mapping
- Configure tenants
- Configure Discovery
- Establish Global Defaults for Spiral Discovery
- Configure Schedule Settings
- Configure Auto-Discovery Rules
- Configure Subnet Connection Rules
- Configure Unnumbered Interface Node Groups
- Configure an Excluded IP Addresses Filter
- Configure an Included Interface Ranges Filter
- Configure an Excluded Interfaces Filter
- Choose Techniques to Launch Discovery
- Specify Discovery Seeds
- Examine Discovery Results
- Manage topology
- Discover and monitor VMware hypervisor-based virtual networks
Configure discovery
[This is the Context-Sensitive Help topic for the Discovery Configuration form.]
NNMi uses Simple Network Management Protocol (SNMP read-only queries), and a variety of communication protocols to discover the physical and virtual devices within the network management domain that you define.
NNMi provides one predefined Tenant, the Default Tenant. Each Node must be assigned to a Tenant. If you choose to use Auto-Discovery Rules, those rules apply only to the nodes within the Default Tenant. All other Discovery configuration settings apply to the nodes within all Tenants.
During discovery, NNMi processes 200 nodes at a time. If you want to discover a very large number of nodes—for example, more than 10000—you can run discovery on nodes in smaller batches, each containing up to 500 nodes. This method helps you discover high-priority nodes in the first run of discovery.
Tip Optional. Establish additional Tenant configurations to identify overlapping address domains or to fine tune Layer 2 connections between devices in your network domain.
Devices that belong to the Default Tenant can have Layer 2 Connections to any device in any Tenant. Devices within any Tenant other than Default Tenant can have Layer 2 Connections only to devices within the same Tenant or the Default Tenant.
Task | How |
---|---|
Prerequisites for Discovery |
Complete all prerequisites.. |
Establish Global Defaults for Spiral Discovery |
Use the Global Control panel to review the default values that NNMi provides. Determine if those defaults work for Spiral Discovery in your network environment. NNMi administrators can change the default settings at any time. |
Configure Schedule Settings |
Use the Schedule Settings tab to review the default values that NNMi provides for Spiral Discovery's Schedule Settings. Determine if those defaults work for Spiral Discovery in your network environment. NNMi administrators can change the default settings at any time. |
Configure Auto-Discovery Rules |
Optional. Use the Auto-Discovery Rules tab to to specify ranges of IP addresses or MIB-II NNMi assigns each node found by Auto-Discovery to the Default Tenant (and whichever Security Group attribute value is currently configured for the Default Tenant = the Default Security Group out-of-box). |
Configure IPv4 Subnet Connection Rules | Optional. Use the IPv4 Subnet Connection Rules tab to establish connections between interfaces on devices that do not respond to Layer 2 discovery protocols (see the list of Topology Source protocols in Layer 2 Connection Form). For example, use Subnet Connection Rules to establish connections to WAN edge devices that NNMi would not automatically detect. |
Configure an Excluded IP Addresses Filter |
Optional. Use the Excluded IP Addresses tab to provide a list of specific addresses or ranges of addresses that you want NNMi to never discover or monitor. This filter applies to all nodes in all Tenants. |
Configure an Included Interface Ranges Filter |
Optional. Use the Included Interface Ranges tab to provide a MIB-II This filter applies to all nodes in all Tenants. |
Configure an Excluded Interfaces Filter |
Optional. Use the Excluded Interfaces tab to provide a list of specific interfaces that you want NNMi to never discover or monitor. This filter applies to all nodes in all Tenants. |
Choose Techniques to Launch Discovery |
You control Spiral Discovery's starting points:
Default Tenant only: If you choose to use Auto-Discovery, there are two choices for launching discovery. Seeds can provide the starting points from which Auto-Discovery gathers information about neighboring devices to expand discovery. Or Ping Sweep settings can enable Auto-Discovery to find any device that responds to Ping commands.
|
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: