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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure communication protocol > Configure default community strings for SNMPv1 or SNMPv2c

Configure default community strings for SNMPv1 or SNMPv2c

[This is the Context-Sensitive Help topic for the Default Community String tab on the Communication Configuration form.]

Use the Default Community Strings tab to provide default SNMPv1 and SNMPv2c community strings. For each address, NNMi checks the communication configuration settings in this order: communication protocols for specific nodes, communication protocols for network regions, and if no match is found, NNMi tries these default community strings. If NNMi discovers a device for which no SNMP settings are provided, that device is treated as a Non-SNMP device.

During initial discovery, NNMi tries many community strings until a match is found. After a match is identified for a node, the information is recorded to prevent future authentication errors.

If you provide a read community string for a specific device, NNMi honors your choice and does not try any Region or Default community strings for that device.

NNMi uses SNMP read-only queries (Get commands) for ongoing discovery and monitoring of your network environment. SNMP read community strings are the validation passwords used to authenticate messages sent from NNMi to an SNMP agent. NNMi uses SNMP to gather useful information about the devices in your network environment. After receiving an SNMP request, an SNMP agent compares the read community string in the request to the read community strings that are configured for that SNMP agent. The SNMP agent responds to the request only when the request is accompanied by a valid community string.

During NNMi installation, any community strings that were provided are automatically stored in the table on the Default Community Strings tab.

Provide any number of additional community strings that are used broadly in your environment (for example, by default). The order in which your read community string settings appear in the table does not matter. NNMi checks all Default read community strings in parallel.

Having a large number of default community strings can negatively impact discovery performance. Instead of entering many default community strings, consider fine tuning the community string configuration for particular areas of your network by using the Regions or Specific Nodes settings.

NNMi uses the SNMPv2c settings to discover the SNMPv2c information about your network. This also determines whether NNMi receives or discards incoming SNMPv2c traps. Click here for more information.

If the incoming trap's Source Node (and sometimes Source Object, such as card or interface) has not yet been discovered by NNMi, NNMi discards the trap.
If the Source Node was not discovered using SNMv3, NNMi discards any incoming SNMPv3 traps from that Node.
NNMi discards traps that have no incident configuration or with an incident configuration set to Disabled. To ensure that NNMi retains all received Trap instances when your network environment includes SNMP agents using a variety of SNMPv1, SNMPv2c, and SNMPv3 protocol, you must configure two Incidents: one for the SNMPv1 version and one for the SNMPv2c/3 version of that trap.
If either the Source Node or Source Object has Management Mode set to Not Managed or Out of Service in the NNMi database, NNMi always discards the incoming trap.

NNMi provides the Management Mode workspace so that you can quickly view lists of all nodes, interfaces, IP addresses, chassis, cards, node sensors, or physical sensors that NNMi is not currently discovering or monitoring.
NNMi discards most incoming traps from network objects that are not monitored. For example, you can configure NNMi to exclude specified interfaces from being monitored.

To configure default SNMPv1 or SNMPv2c community strings for your environment:

Navigate to the Communication Configuration form.
1. From the workspace navigation panel, select the Configuration workspace.
2. Select the Communication Configuration.
Locate the Default SNMPv1/v2c Community Strings tab.
To provide a default read community string, navigate to the Read Community Strings table and do one of the following:
- To establish a community string setting, click the New icon. In the Default Read Community String form, provide the required information.
- To edit a community string setting, click the Open icon in the row representing the community string setting you want to edit. In the Default Read Community String form, provide the required information.
- To delete a community string setting, select a row and click the Delete icon.
To provide a default write community string, navigate to the Write Community String attribute.
Click Save and Close to return to the Communication Configuration form.
Click Save and Close to apply your changes.

Default SNMPv1 or SNMPv2c Community Strings
Attribute	Description
Read Community String	Note As an NNMi administrator, you can over-ride this setting and specify the Read Community String on a per-node basis using the SNMP Agent Form. The SNMPv1 or SNMPv2c "Get" (read-only) Community String that is used as the default value for each SNMP Agent (case-sensitive). Many proxy vendors use the read community string for specifying remote target information. NNMi supports substitution parameters within read community strings for SNMPv1 or SNMPv2c proxy environments. Click here for more information. Copy and paste these codes at the end of your read community string to provide the values required by your proxy environment. NNMi substitutes the actual attribute values from the NNMi database at runtime: ${contextName} = Used for specifying VLAN context for switches (VLAN associated with the remote target node) ${managementAddress} = Node form, Management Address attribute value (the remote target node) ${snmpPort} = SNMP Agent form, UDP Port attribute value (SNMP agent associated with the remote target node) Type a maximum of 255 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Ordering	Optional. During the Discovery process, NNMi tries Read Community Strings in priority order (lowest to highest). Then, NNMi tries all unordered Read Community Strings (treated as though they had the same Ordering number). These unordered requests are sent in parallel, with NNMi using the first response.
Write Community String	Optional. For use with the nnmsnmpset.ovpl command line tool The SNMPv1 or SNMPv2c "Set" (write) Community String that is used as the default value for each SNMP Agent (case-sensitive). SNMP Agents are often configured with different community strings for "Set" requests than for "Get" (read) requests. SNMPv1 and SNMPv2c require that you know the SNMP agent's write community string before you can change settings on any device. The nnmsnmpset.ovpl command can use the value you provide here, rather than requiring that you type the write community string each time you invoke the command. Type a maximum of 255 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted. Because this is a type of password, you must enter the value twice.

Default Read Community String form

[This is the Context-Sensitive Help topic for the Communication Default Community String form.]

For each IP address, NNMi checks the communication configuration settings in this order: communication protocols for specific devices, communication protocols for network regions, and if no match is found, NNMi tries the default community strings. If NNMi discovers a device for which no community string is provided, that device is treated as a Non-SNMP device.

To provide a default community string for your environment:

Navigate to the Default Read Community String form.
1. From the workspace navigation panel, select the Configuration workspace.
2. Select the Communication Configuration.
3. Navigate to the Default SNMPv1/v2c Community Strings tab.
4. Navigate to the Read Community Strings table.
5. Do one of the following:
  - To establish a community string setting, click the New icon.
  - To edit a community string setting, select a row, click the Open icon in the row representing the configuration you want to edit.
Provide the read community string.

Provide any number of additional SNMPv1 or SNMPv2c read community strings that are used broadly in your environment (for example, by default).
Click either:
- Save and Close to return to the Communication Configuration form.
- Save and New to add another community string.
Click Save and Close to apply your changes.

To determine which Community Strings are relevant for a node, select the node in an NNMi map or table view, and click Actions > Configuration Details > Communication Settings. In the Communities list, Ordering number is in parentheses. For example: communityString (200).

Default Read Community String
Attribute	Description
Read Community String	Note As an NNMi administrator, you can over-ride this setting and specify the Read Community String on a per-node basis using the SNMP Agent Form. The SNMP "Get" (read-only) Community String that is used in your network environment (case-sensitive). Many proxy vendors use the read community string for specifying remote target information. NNMi supports substitution parameters within read community strings for SNMPv1 or SNMPv2c proxy environments. Click here for more information. Copy and paste these codes at the end of your read community string to provide the values required by your proxy environment. NNMi substitutes the actual attribute values from the NNMi database at runtime: ${contextName} = Used for specifying VLAN context for switches (VLAN associated with the remote target node) ${managementAddress} = Node form, Management Address attribute value (the remote target node) ${snmpPort} = SNMP Agent form, UDP Port attribute value (SNMP agent associated with the remote target node) Type a maximum of 255 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Ordering	Optional. A numeric value. NNMi uses the first Community String that results in successful SNMP communication: Each ordering number must be unique (no duplicate numbers). NNMi tries the provided Community Strings in the order you define (lowest number first). Consider incrementing by 10s or 100s to provide flexibility when adding new Read Community Strings over time. If no Ordering numbers are specified, NNMi tries all community strings in parallel. If some but not all the community strings have an Ordering number, NNMi tries the community strings with a specified Ordering number first. Then, NNMi tries all the community strings without an Ordering number in parallel.

Configure default community strings for SNMPv1 or SNMPv2c

Default Read Community String form

Related topics