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 |
|
- Administer
- License
- Set Up Application Failover
- Configure NNMi in a High Availability Cluster
- NNMi and NNM iSPI Default Ports
- General Concepts for Configuration
- Configure NNMi to Use a Different Java Development Kit
- NNMi Communications
- NNMi Discovery
- NNMi State Polling
- NNMi Incidents
- Configure NNMi Console
- NNMi Auditing
- Manage Certificates
- Use Single Sign-On (SSO) with NNMi
- Configure NNMi to Support Public Key Infrastructure User Authentication
- Configuring the Telnet and SSH Protocols for Use by NNMi
- Integrate NNMi with a Directory Service through LDAP
- Multihomed NNMi Management Server
- Managing Overlapping IP Addresses in NAT Environments
- NNMi Security and Multi-Tenancy
- Configure NNMi to Work in a GNM Environment
- Configuring NNMi Advanced for IPv6
- Quick Start Configuration Wizard
- Manage environment variables
- Console features useful for configuration tasks
- Actions provided by NNMi
- Processes and services
- Connect multiple NNMi Management Servers (NNMi Advanced)
- Configure communication protocol
- Configure default SNMP, management address, and ICMP settings
- Configure default community strings for SNMPv1 or SNMPv2c
- Configure default SNMPv3 settings
- Configure the default device credentials
- Configure the default trusted certificates
- Configure regions
- Configure specific nodes
- Load communication settings from a file
- Restrict SNMP communication for a node
- Verify communication settings
- Discover your network
- Configure Device Profiles (sysObjectIDs)
- Create Groups of Nodes or Interfaces
- Monitor Network Health
- Configure the NNMi User Interface
- Configure Security
- Configure Incidents
- Use RAMS with NNMi Advanced
- Extend NNMi Capabilities
- Integrate NNMi Elsewhere with URLs
- Administer SNMP Traps
- Maintain NNMi
- Security Configuration
- Modify Default Settings
- NNMi Logging
- NNMi Northbound Interface
- Use Operations Bridge Reporter to View Reports
- Network Node Manager i Reference Pages
- Administer NPS
- Administer the NNM iSPI Performance for QA
- Administer the NNM iSPI Performance for Traffic
- Administer the NNM iSPI for MPLS
- Administer the NNM iSPI for IP Multicast
- Administer the NNM iSPI for IP Telephony
Configure communication protocol
[This is the Context-Sensitive Help topic for the Communication Configuration form.]
NNMi uses the following protocols to discover your network and monitor the health of your network environment:
-
Simple Network Management Protocol (SNMPv1 and SNMPv2c)
-
Read-only queries, also known as "Get" commands.
SNMPv1 and SNMPv2c require the use of a read community string to authenticate messages that are sent between NNMi and SNMP agents. NNMi cannot discover information about the SNMPv1 and SNMPv2c devices in your network environment until you provide the appropriate read community strings. During discovery and monitoring, NNMi uses the read community strings you provide in the Communication Configurations option of the Configuration workspace. When a device is first discovered, NNMi tries all appropriate read community strings and makes a record of the first read community string that works. To keep network traffic to a minimum, from then on NNMi uses the recorded read community string when communicating with that device using SNMP. If at some point the device no longer responds to the recorded read community string, NNMi tries all appropriate read community strings and makes a record of the first read community string that now works.
-
Write commands, also known as "Set" commands.
SNMPv1 and SNMPv2c require the use of a write community string to authenticate messages that are sent between the nnmsnmpset.ovpl command and SNMP agents.
-
- SNMPv3 requires the use of user-based security model (USM) user names instead of SNMPv1/SNMPv2c community strings to authenticate messages that are sent between NNMi and SNMP agents. NNMi cannot discover information about the SNMPv3 devices in your network environment until you provide the appropriate user name and authentication. During discovery and monitoring, NNMi uses the SNMPv3 User Name attribute value and authentication that the NNMi administrator provides in the Communication Configuration workspace. When a device is first discovered, NNMi tries all appropriate USM user names and makes a record of the first USM user name that works. To keep network traffic to a minimum, from then on NNMi uses the recorded SNMPv3 User Name attribute value when communicating with that device using SNMP. If at some point the device no longer responds to the recorded SNMPv3 User Name attribute value, NNMi tries all appropriate USM user names and makes a record of the one that now works.
- Internet Control Message Protocol (ICMP) ping commands
- If Web Agents are configured (in addition to SNMP Agents), NNMi can use additional protocols. For example, SOAP protocol for VMware environments.
If NNMi discovers a device for which no SNMP authentication was provided in the Communication Configuration workspace, that device is treated as a non-SNMP device.
You control the amount of traffic NNMi generates on your network. You can modify the settings to meet your needs.
As an NNMi administrator, you can over-ride the Communication Configuration settings for a Node, using the Mode attribute in the SNMP Agent Form.
To configure the way NNMi uses ICMP and SNMP protocols, do the following:
-
Navigate to the Communication Configuration form.
- From the workspace navigation panel, select the Configuration workspace.
- Select the Communication Configuration.
-
Make your configuration choices. The Communication Configuration settings determine whether each NNMi Rediscovery cycle automatically detects the best SNMP choice (v1, v2, or v3) for each Node (automatically detects any upgrade to the SNMP agent on each Node), or uses only the SNMP version that you specify.
Click here for a list of choices .
Tip For the alternate method of configuring communication settings from the command line, see the nnmcommunication.ovpl Reference Page.
-
Click Save and Close to apply your changes.
You control the amount of network traffic generated by NNMi by designating the Rediscovery Interval setting and making choices when you configure NNMi monitoring behavior.
Related topics
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: