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 |
|
Valid Parameters for Trap Logging Messages
When configuring Trap Logging messages, consider using SNMP Trap Incident information as part of the message. NNMi provides the following parameter values. Use these parameters as variables when formatting an incident message.
Tip See the Using the Incident Form for more information about the parameter values.
Note NNMi stores varbind values as custom incident attributes (CIAs).
See Configure Trap Logging for more information about configuring messages.
Parameter strings are available for the following:
Note See the following tables to view the valid parameters for Trap Logging messages: Parameter Strings for all Incidents (Attributes from an Incident form), Parameter Strings for Node Source Objects (Attributes from a Node form), and Parameter Strings for all Incidents (Attributes not Visible from any form).
-
Parameter strings for all incidents (Incident form attributes) (Click here for a list of choices.)
-
Parameter Strings for Node Source Objects (Node form attributes) (Click here for a list of choices.)
-
Parameter Strings for all incidents (Additional information that is not visible in any form) (Click here for a list of choices.)
-
Information established in varbinds (Click here for a list of choices.)
Parameter Strings for varbinds
Parameter String Description $<position _number> Value of the position number for a varbind . For example, to indicate you want to use the varbind in position 1, enter:
$1
If you know the varbind position number, use this parameter.
$<varbind_name> Value of the name that is used for the varbind. $<varbind_oid> Value of the object identifier for a specified varbind. For example, $.1.3.6.1.6.3.1.1.5.1.
Use this parameter when you are not certain of a varbind position number.$* Used to indicate you want all of the varbind values, to be passed to the action configuration. -
Functions to generate values (Click here for a list of choices.)
The function described in the following table replaces the specified numeric value with the associated text value stored in the varbind.
Note: The associated MIB must have been loaded using the nnmloadmib.ovpl command.
Functions to Generate Values Within the Incident Message Function Description $oidtext($<position_number>) A <position_number> argument specifies the numeric value of the position number for a specific varbind . For example,
$oidtext($2)
.Note The position number you enter must represent a varbind that contains an Object Identifier (OID) value.
NNMi returns the textual value of the OID for the varbind specified.
Note the following:
- If the MIB is not loaded, NNMi returns the numeric OID value.
- If the OID has a MIB instance, the number representing the MIB instance is appended to the textual OID value.
$oidtext($<varbind_oid>) The <varbind_oid> argument specifies the Object Identifier (OID) for a specific varbind. For example,
$oidtext($.1.3.6.1.6.3.1.1.5.1.)
Tip Use this argument to the $oidtext() function when you are not certain of a varbind position number.
NNMi replaces the numeric value with the textual value of the OID you specify.
Note the following:
- If the MIB is not loaded, NNMi returns the numeric OID value.
- If the OID has a MIB instance, the number representing the MIB instance is appended to the textual OID value.
$text($<position_number>) The <position_number> argument specifies the numeric value of the varbind position number. For example, to indicate you want to use the varbind in position 1, enter:
$1.
NNMi replaces the numeric value with the text value stored in the varbind.
Note If a text value is not available, NNMi returns the numeric value.
$text($<varbind_oid>) The <varbind_oid> argument specifies the object identifier for a specific varbind. For example,
$.1.3.6.1.6.3.1.1.5.1.
Use this argument to the $text function when you are not certain of a varbind position number.
NNMi replaces the numeric value with the text value stored in the varbind.
Note If a text value is not available, NNMi returns the numeric value.
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: