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 |
|
- Access Device Details
- Node Form
- Interface Form
- IP Address Form
- SNMP Agent Form
- Web Agent Form (NNMi Advanced)
- IP Subnet Form
- VLAN Form
- Chassis Form
- Card Form
- Port Form
- Node Sensor Form
- Physical Sensor Form
- Layer 2 Connection Form
- Chassis Redundancy Group Form
- Card Redundancy Group Form
- Router Redundancy Group Form (NNMi Advanced)
- Node Group Form
- Interface Group Form
- MPLS WAN Cloud Form (NNMi Advanced)
- Custom Node Collections Form
Custom Node Collections Form
[This is the Context-Sensitive Help topic for the Custom Poller Node form.]
The Custom Node Collections form provides details about the Custom Node Collection you selected from the Monitoring workspace. A Custom Node Collection identifies a topology node that has at least one associated Custom Poller Policy. Because a topology node can be associated with more than one Policy, the same topology node might appear in multiple Custom Node Collections. This topic includes the following sections:
The following table describes the attributes included on the Custom Node Collection form.
For information about each tab: See Also
Attribute | Description |
---|---|
Node |
Name of the topology node from which the Custom Poller Policy information is being collected. This is the current value in the NNMi database for the Name attribute of the node. The value could be a DNS name, a MIB-II sysName, or an address (depending on how your NNMi administrator configured the discovery process). Click the Lookup icon and select Show Analysis or Open to display more information about the node. |
Active State |
The Active State for the associated Custom Collect Policy. Possible values are described below: Active - Indicates the Custom Poller Policy is in use. At the time the Active State attribute is set to Active, NNMi applies the Custom Poller Policy to the nodes in the specified Node Group to determine which instances should be polled. Inactive - Indicates the Custom Poller Policy is not in use. NNMi removes all Polled Instances associated with the Policy. Suspended - Indicates someone on your team changed this Custom Poller Policy's Active State to |
Status |
The most severe State value returned from the Custom Poller Polled Instances for this Custom Node Collection. Possible values are: Normal Warning Minor Major Critical |
Policy |
A Policy specifies the Node Group and Polling Interval that NNMi should use when polling the results of the MIB Expression configured for the current Custom Poller Collection. If the NNMi Security configuration permits, click the Lookup icon and select Show Analysis or Open to display more information about the current Custom Poller Node's Policy. |
Discovery State |
Indicates the progress toward collecting data associated with this Polled Instances Tab (discovery using the MIB Expression objects for which you are collecting information). Possible values include: Created - NNMi has not yet discovered any data for this new Polled Instance. In progress - NNMi is currently collecting data for this Polled Instance. Completed - NNMi gathered the data associated with this Polled Instance and placed it in the NNMi database. Unresponsive - The SNMP agent did not respond when NNMi attempted to gather the data associated with this Polled Instance. Failed - NNMi is unable to gather the data associated with this Polled Instance. Look in the Discovery State Information field for details. |
Discovery State Last Modified | The date and time when the Discovery State value was last modified. |
Discovery State Information |
Indicates any problems contributing to the Discovery State calculation. |
Incidents Tab
[This is the Context-Sensitive Help topic for the Custom Poller Node form, Polled Incidents tab.]
The Custom Node Collections Form provides details about the selected Custom Node Collection.
For information about each tab: See Also
Description |
---|
Table view of the incidents associated with the selected Custom Node Collection. These incidents are sorted by creation time so that you can view the incidents in chronological order. Use this view to determine which incidents are still open for the selected Custom Node Collection. To see more information about an incident, double-click the row representing an incident. The Incident Form displays all details about the selected incident. |
Status Tab
[This is the Context-Sensitive Help topic for the Custom Poller Node form, Status tab.]
The Custom Node Collections Form provides details about the selected Custom Node Collection.
For information about each tab: See Also
Attribute | Description |
---|---|
Status |
The most severe value returned from the Polled Instances for this Custom Node Collection. Possible values are: Normal Warning Minor Major Critical |
Status Last Modified | Date and time indicating when the status was last set. |
Attribute | Description |
---|---|
Status History |
List of up to the last 30 changes in status for the selected Custom Node Collection. This view is useful for obtaining a summary of the Custom Node Collection Status so that you can better determine any patterns in node behavior and activity. Double-click a row representing a Status History. The Status History form displays all details about the selected Status. |
Conclusions Tab
[This is the Context-Sensitive Help topic for the Custom Poller Node form, Conclusions tab.]
The Custom Node Collections Form provides details about the selected Custom Node Collection.
For information about each tab: See Also
Attribute | Description | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Outstanding Status Conclusions |
The dynamically generated list of summary statuses of the Custom Node Collection that contributed to the current overall Status of the selected Custom Node Collection. Each Conclusion listed is still outstanding and applies to the current overall Status. This view is useful for obtaining a quick summary of the Status and problem description that led up to the Custom Node Collection's most current Status. The Status value is correlated based on the most critical outstanding Conclusions. Double-click the row representing a Conclusion. The Conclusion form displays all details about the selected Conclusion. The following table describes the possible Conclusions that might appear for a Custom Node Collection object. A Y in the Incident? column indicates that the Conclusion results in an incident.Critical Status Conclusions
Major Status Conclusions
Minor Status Conclusions
Warning Status Conclusions
Normal Status Conclusions
|
Polled Instances Tab
[This is the Context-Sensitive Help topic for the Custom Poller Node form, Polled Instance tab.]
The Custom Node Collections Form provides details about the selected Custom Node Collection.
For more information about Custom Polled Instances, click here.
The first time a MIB Expression is validated with discovery information, the results appear in the Monitoring workspace's Custom Polled Instances view.
Each Custom Polled Instance:
- Updates whenever a change in State occurs (defined using Threshold or Comparison Maps settings).
- Includes the most recent polled value that caused the State to change.
These results are then used to determine the Status of the associated Custom Node Collection.
For example, you can specify that each time the hrDeviceStatus
for a COM (communication) port returns a value of 5 (down), the State of the Polled Instance becomes Critical, which automatically affects the Status of the associated Custom Node Collection.
For information about each tab: See Also
Attribute | Description |
---|---|
Polled Instances List |
Information about Custom Poller Policy information being collected. This table is useful for obtaining a quick summary. Double-click the row representing a Polled Instance. The Custom Polled Instance Form displays all details about the selected Polled Instance. |
[This is the Context-Sensitive Help topic for the Custom Poller Polled Instance form.]
The Custom Polled InstanceA Custom Polled Instance represents the results of a MIB variable when it is evaluated against a node. The first time a MIB variable is validated with discovery information, the results appear in the Monitoring workspace's Custom Polled Instances view. The Custom Polled Instance is updated whenever a change in State occurs and includes the most recent polled value that caused the State to change. These results are then used to determine the Status of the associated Custom Node Collection. form provides details about the Custom Polled Instance you selected from the Monitoring workspace. The following table describes the attributes included on the Polled Instance form.
(NNMi Advanced - Global Network Management feature) Any Custom Polled Instances are not sent from a Regional Manager (NNMi management server) to the Global Manager. From the Global Manager, use Actions → Open from Regional Manager to see the list of Custom Polled Instances on the Regional Manager.
For information about each tab: See Also
Note the following about Custom Polled Instances:
- The first time a MIB Expression is validated with discovery information, the results appear in the Monitoring workspace's Custom Polled Instances view.
-
Each Custom Polled Instance:
- Updates whenever a change in State occurs (defined using Threshold or Comparison Maps settings).
- Includes the most recent polled value that caused the State to change.
-
These results are then used to determine the Status of the associated Custom Node Collection.
For example, you can specify that each time the
hrDeviceStatus
for a COM (communication) port returns a value of 5 (down), the State of the Polled Instance becomes Critical, which automatically affects the Status of the associated Custom Node Collection.
Attribute | Description |
---|---|
Node |
Name of the topology node on which the Custom Poller Policy information is being collected. This is the current value in the NNMi database for the Name attribute of the node. The value could be a DNS name, a MIB-II sysName, or an address (depending on how your NNMi administrator configured the discovery process). Click the Lookup icon and select Show Analysis or Open to display more information about the topology node. |
MIB Instance |
This attribute contains the multiple filtered instances for the MIB Expression. Each instance value identifies a row in the MIB table. If a MIB expression includes multiple MIB Variables that have multiple instances, each instance value that is valid across all MIB Variables for a node is listed here. If NNMi is unable to find the same instance for all MIB Variables in the expression, a Polled Instance is not created. This is because NNMi cannot correctly evaluate a MIB Expression with missing values. If Polled Instances are not created as expected, check the Custom Node Collection view for Discovery State and Discovery State Information values. |
Filter Value | The instance of a MIB Variable value after the MIB Filter is applied. |
Display Attribute |
The MIB Variable that contains the values NNMi displays when generating Custom Polled Instance or Line Graph results. The NNMi administrator selects this Display Variable when configuring the MIB Expression for a Custom Poller Collection. |
Active State | Specifies whether a Custom Poller Policy is enabled. |
Custom Node Collection |
Name of the associated Custom Node Collection.A Custom Node Collection identifies a topology node that has at least one associated Custom Poller Policy. Because a topology node can be associated with more than one Policy, the same topology node might appear in multiple Custom Node Collections. Click the Lookup icon and select Show Analysis or Open to display more information about the Custom Node Collection. |
MIB Variable | The MIB Variable that is associated with this Custom Poller Instance. See Specify the MIB Variable Information for a Custom Poller Collection for more information. |
Custom Poller Policy | Name of the associated Custom Poller Policy. The Custom Poller Policy defines the Node Group from which the MIB information is polled. |
Custom Poller Collection |
Name of the Custom Poller Collection.A Custom Poller Collection defines the information you want to gather (poll) as well as how you want NNMi to handle the results. Click the Lookup icon and select Show Analysis or Open to display more information about the Custom Poller Collection. |
Status |
Overall status for the current Custom Polled Instance. NNMi follows the ISO standard for status classification. See theStatus Tab for more information. Possible values are: Normal Warning Minor Major Critical Status reflects the most serious outstanding conclusion. The icons are displayed only in table views |
State |
The State of the Custom Polled Instance as determined by any Thresholds (High State / Low State value) or Comparison Maps (State Mapping = the NNMi administrator assigns a State value for each possible Polled Instance value) configured for the current Custom Poller Collection's MIB Expression. Possible State values for a Polled Instance (Threshold = High State/Low State; or Comparison Map = State Mapping) are: Normal Warning Minor Major Critical The most severe Threshold High State or Low State value or Comparison Map State Mapping value returned from the Polled Instances for a Custom Node Collection becomes the Custom Node Collection Status. |
Last State Change Value |
The value from the MIB Expression that most recently caused the State to change. A value of null indicates that a value was unavailable or an error occurred while evaluating the MIB Expression. |
State Last Modified | The date and time the Polled Instance was last modified. |
[This is the Context-Sensitive Help topic for the Custom Polled Instances form, Polled Incidents tab.]
The Custom Polled Instance Form provides details about the selected Custom Polled Instance.
The Name of the Source Object for a Custom Polled Instance Incident is the display value that is determined using the Instance Display Configuration for the associated MIB Expression.
If the Instance Display Configuration is not set, NNMi identifies the Source Object using the topology Node Name followed by the MIB Instance value in the format: <node_name> -.<MIB_instance_value>.
The Name that NNMi uses to identify the Custom Polled Instance Incident’s Source Object is not stored in the NNMi database as the Custom Polled Instance object Name.
For information about each tab: See Also
Description |
---|
Table view of the incidents associated with the selected Custom Polled Instance. These incidents are sorted by creation time so that you can view the incidents in chronological order. Use this view to determine which incident is still open for the selected Custom Polled Instance. To see more information about an incident, double-click the row representing an incident. The Incident Form displays all details about the selected incident. |
[This is the Context-Sensitive Help topic for the Custom Polled Instance form, Status tab.]
The "Custom Polled Instance Form" provides details about the selected Custom Polled Instance.
For information about each tab: See Also
Attribute | Description |
---|---|
Status |
The most severe value returned from the Custom Polled Instance. Possible values are: Normal Warning Minor Major Critical |
Status Last Modified |
Date and time indicating when the status was last set. |
Attribute | Description |
Status History |
List of up to the last 30 changes in status for the selected Custom Polled Instance. This view is useful for obtaining a summary of the Custom Polled Instance Status so that you can better determine any patterns in node behavior and activity. Double-click a row representing a Status History. The Status History form displays all details about the selected Status. |
[This is the Context-Sensitive Help topic for the Custom Polled Instance form, Conclusions tab.]
The Custom Polled Instance Form provides details about the selected Custom Polled Instance.
For information about each tab: See Also
Attribute | Description | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Outstanding Status Conclusions |
The dynamically generated list of summary statuses of the Custom Polled Instance that contributed to the current overall Status of the selected Custom Polled Instance. Each Conclusion listed is still outstanding and applies to the current overall Status. This view is useful for obtaining a quick summary of the Status and problem description that led up to the Custom Polled Instances most current Status. The Status value is correlated based on the most critical outstanding Conclusions. Double-click the row representing a Conclusion. The Conclusion form displays all details about the selected Conclusion. The following table describes the possible Conclusions that might appear for a Custom Polled Instance object. A Y in the Incident? column indicates that the Conclusion can result in an incident. An NNMi administrator can configure whether incidents are generated. See Configure Basic Settings for a Custom Poller Collection for more information.Critical Status Conclusions
Major Status Conclusions
Minor Status Conclusions
Warning Status Conclusions
Normal Status Conclusions
|
The NNMi Custom Polling feature enables your NNMi administrator to take a proactive approach to network management by gathering additional device information using SNMP MIB Expressions. For example, an NNMi administrator might want NNMi to monitor the Status of COM (communication) ports on all of your Windows servers or determine disk utilization on a specified group of servers.
A Custom Poller Collection defines the additional SNMP MIB information that NNMi should gather (Custom Poll) as well as how NNMi reacts to the gathered data.
For information about each tab: See Also
If the Security configuration permits, you can access a Comparison Map form from the Comparison Maps tab.
The following tables describe the attributes included on the Custom Polled Collection form.
Attribute | Description |
---|---|
Name |
The name for the Custom Poller Collection configuration. The Custom Poller Collection name appears in any incidents generated as a result of the collection. |
Affect Node Status |
Used to indicate whether each Polled Instance affects the associated Node's Status. The first time a MIB Expression is validated with discovery information, the results appear in a Polled Instance object. The Polled Instance object is updated whenever a change in State occurs and includes the most recent polled value that caused the State to change. |
Generate Incident |
Used to indicate whether NNMi generates an incident:
|
Export Custom Poller Collection |
If enabled , NNMi exports the Custom Poller Collection to a comma-separated values (CSV) file If disabled , NNMi does not export the Custom Poller Collection information. |
Compress Export File |
If enabled , NNMi exports the Custom Poller Collection in compressed format and appends .gz to the .csv file suffix. If disabled , NNMi does not compress the CSV file. |
Attribute | Description |
---|---|
MIB Expression |
MIB Expressions specify what additional information NNMi should gather. |
MIB Filter Variable |
The MIB Filter Variable is the MIB variable that has a value you want to use as a filter to determine which instances of the MIB expression to Custom Poll. |
Custom Poller enables the NNMi administrator to map the returned value of a MIB Expression to a Custom Poller Polled Instance State. NNMi uses Comparison Map values to determine when to generate an incident, as well as the State of the Polled Instance.
Click here for more information about Polled Instances.
The first time a MIB Expression is validated with discovery information, the results appear in a Polled Instance object. The Polled Instance object is updated whenever a change in State occurs and includes the most recent polled value that caused the State to change.
For example, the NNMi administrator might configure a Custom Polled Collection so that the hrDeviceStatus value of 5 (down) is mapped to a Critical State. This means that NNMi changes the State of the Polled Collection Instance to Critical each time the hrDeviceStatus returns a value of 5 when polled.
The following tables describe the attributes included on the Comparison Map form.
Attribute | Description |
---|---|
Ordering |
The order in which the State mapping (Comparison Maps) operations should be performed. NNMi uses the Ordering value to determine which State mapping to use. The lower the number, the higher the priority. For example, 1 is the highest priority. |
Comparison Operator | Operator used to evaluate the polled value and subsequently determine its State. For example, the < (less than) Comparison Operator indicates the polled value returned must be less than the Comparison Value to change the Custom Poller Polled Instance to the state specified using the State Mapping value. |
Comparison Value | The value to which the polled value is compared. |
State Mapping |
The State to assign to the Custom Poller Polled Instance when the polled value meets the comparison criteria. For example, each time the value 3 (warning) is returned when NNMi polls hrDeviceStatus, you can specify that you want NNMi to change the State of the Polled Instance to Warning. Possible State values for a Polled Instance (Threshold = High State/Low State; or Comparison Map = State Mapping) are: Normal Warning Minor Major Critical |
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: