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
Physical Sensor Form
[This is the context-sensitive link for the Physical Sensor Form]
This form describes the fault and performance metrics used to monitor Physical Sensors. NNMi obtains fault metrics from the node's SNMP agent (MIB files). This topic includes the following sections:
For information about each tab: See Also
The NNMi administrator can set Physical Sensor thresholds. Physical Sensors are displayed in three views: Physical Sensors View, Non-Normal Physical Sensors View, and Unmanaged Physical Sensors View.
Attribute |
Description |
---|---|
Status |
Overall status for the current Physical Sensor. NNMi follows the ISO standard for status classification. See Status Color for Objects for more information. Possible values are: No Status Normal Disabled Unknown Warning Minor Major Critical For information about how the current status was determined, see the Conclusions tab. Status reflects the most serious outstanding conclusion. See Watch Status Colors for more information about possible status values. The icons are displayed only in table views. |
Name |
Name of the Physical Sensor that has the health attribute being measured, For example, NNMi measures fault metrics for Fan, Power Supply, Temperature, and Voltage. (NNM iSPI Performance for Metrics) If licensed and installed, Network Node Manager iSPI Performance for Metrics Software also measures performance metrics for Backplane. When possible, NNMi obtains the Name value for the Physical Sensor from the associated SNMP agent. The number of MIBs available and subsequently the number of health attributes that are measured for each Physical Sensor vary. If the associated MIB file does not provide a name value, NNMi uses the value provided by the Type attribute. |
Type |
Identifies the health aspect that is being monitored. Possible values include: (NNM iSPI Performance for Metrics) Health monitoring of the following requires an Network Node Manager iSPI Performance for Metrics Software license:
|
Management Mode |
The calculated Management Mode for the physical sensor according to the Management Mode Hierarchy. This value reflects the current management mode of this physical sensor's parent object (either the Hosted On chassis or card, or the Managed By node). See How NNMi Assigns the Management Mode to an Object. (NNMi Advanced - Global Network Management feature) Any change to this Management Mode setting is sent from a Regional Manager to the Global Manager during the next Spiral Discovery cycle on the Regional Manager. If the NNMi Security configuration permits, you can change this setting using Actions → Management Mode. You can also right-click any object in a table or map view to access the items available within the Actions menu. |
Direct Management Mode |
Indicates whether or not NNMi is currently monitoring the physical sensor. Possible values are: Inherited – Used to indicate that the Physical Sensor should inherit the Management Mode from the physical sensor's parent object (either the Hosted On chassis or card, or the Managed By node). Not Managed – Used to indicate that NNMi does not discover or monitor the Physical Sensor. Out of Service – Used to indicate a Physical Sensor is unavailable because it is out of service or participating in a Scheduled Node Outage. NNMi does not discover or monitor this Physical Sensor. NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting. If you change the Direct Management Mode using Actions → Management Mode, NNMi updates the calculated Management Mode on the form. If you manually set the Direct Management Mode and then Save your changes, the Management Mode value is not updated until you refresh the form. |
Managed By |
The node using this chassis or the node assigned to the Agent that is managing this chassis. This is the current value in NNMi’s database for the Name attribute of the host 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. |
Hosted On |
Chassis or card on which the health metric is being measured. This is the current value in NNMi’s database for the Name attribute of the chassis or card. See Chassis Form or Card Form for more information. The NNMi administrator can set Physical Sensor thresholds. For more information, see Chassis Form: Physical Sensors Tab and Card Form: Physical Sensors Tab. |
Monitored Attributes Tab
[This is the Context-Sensitive Help topic for the Physical Sensor form, Monitored Attributes tab.]
The Physical Sensor Form provides details about the monitored attributes related to the current Physical Sensor. The State of monitored attributes can be influenced by thresholds configured by your NNMi administrator.
For information about each tab:See Also
Description |
---|
Table view of the Name, State, and Last Modified time for each monitored attribute associated with the selected Physical Sensor. Use this view to determine the State of each monitored attribute. Double-click the row representing a Monitored Attribute. The Physical Sensor Monitored Attribute Form displays all details about the selected Monitored Attribute. |
Physical Sensor Monitored Attribute Form
[This is the Context-Sensitive Help topic for the Physical Sensor Monitored Attribute form.]
The Physical Sensor Monitored Attribute form displays information about the attribute selected on the Physical Sensor Form: Monitored Attributes Tab.
Physical Sensors for fault monitoring include the following:
- Fan
- Power Supply
- Temperature
- Voltage
(NNM iSPI Performance for Metrics) If the Network Node Manager iSPI Performance for Metrics Software is installed and configured within your environment, the NNMi administrator can also configure Performance monitoring and thresholds for the following:
-
Backplane Utilization
Threshold based on the percentage of backplane usage compared to the total amount of available backplane resources.
NNMi obtains fault metric information from the associated MIB.
Attribute |
Description |
---|---|
Label |
Name used to identify the attribute being monitored. The Name of each health attribute identifies the attribute being measured as well as the type of MIB used to gather this information. |
Unique Key | Used as a unique identifier for the Monitored Attribute. Any Monitored Attribute provided by NNMi begins with the prefix com.hp.nms . |
State |
Normalized value used to indicate the State of the attribute of the selected node. Possible values are listed below. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendor-specific nodes.Normal - Indicates there are no known problems related to the associated object. Warning - Indicates there might be a problem related to the associated object. Minor - Indicates NNMi has detected problems related to the associated object that require further investigation. Major - Indicates NNMi detected problems that could precede a critical situation. Critical - Indicates NNMi detected problems that require immediate attention. The following values indicate NNMi could not gather the required data: Agent Error – Indicates an error was returned in response to the query. No Polling Policy - No polling policy exists for this monitored attribute. Not Polled - Indicates that this attribute is intentionally not polled, based on current Monitoring Configuration settings, current Communication Configuration settings, or because the parent Node is set to Not Managed or Out of Service. This object attribute might or might not have an associated polling policy. Not Provided — The device does not support providing information for this monitored attribute. Unavailable - The agent responded with a value outside the range of possible values or returned a null value. Unset – Currently not used by NNMi. State is determined by the State Poller Service. Only the Physical Sensor States for Fan and Power Supply contribute towards the status calculation for the host node. See the Status tab for more information. (NNM iSPI Performance for Metrics) Additional States for performance metrics include the following (Warning and Critical states are not used for performance metrics): Abnormal Range – Indicates State Poller has collected values outside the normal range when compared to the baseline data collected for the current object. Normal - Indicates there are no known problems related to the associated object. Normal Range - Indicates State Poller collected values within the normal range when compared to the baseline data collected for the current object. High - The High threshold was crossed. Low - The Low threshold was crossed. None - The threshold value returned is zero. |
Last Modified | The most recent date and time when the State of this Monitored Attribute changed. |
Incidents Tab
[This is the Context-Sensitive Help topic for the Physical Sensor form, Incidents tab.]
The Physical Sensor Form provides details about the selected physical sensor.
For information about each tab: See Also
Attribute | Description |
---|---|
Incidents |
Table of the Incidents associated with the selected physical sensor. These Incidents are sorted by creation time so that you can view the Incidents in chronological order. Use this table to determine which Incidents are still open for the selected physical sensor Double-click the row representing an incident. The Incident Form displays all details about the selected incident. See Incident Form for more details about the incident attributes that appear in the incident table's column headings. |
Status Tab
[This is the Context-Sensitive Help topic for the Physical Sensor form, Status tab.]
The Physical Sensor Form provides details about the selected Physical Sensor.
For information about each tab:See Also
Attribute | Description |
---|---|
Status |
Overall status for the current Physical Sensor. NNMi follows the ISO standard for status classification. Possible values are: No Status Normal Disabled Unknown Warning Minor Major Critical Your NNMi administrator might have disabled polling of Physical Sensors using the Monitoring Configuration workspace.The status of the Physical Sensor contributes to the parent Chassis's overall status. For information about how the current status was determined, see the Physical Sensor Form: Conclusions Tab. Status reflects the most serious outstanding conclusion. See Watch Status Colors for more information about possible status values. The icons are displayed only in table views. |
Status Last Modified | Date and time indicating when the status was last set. |
Attribute | Description |
---|---|
Status History |
List of the last 30 changes in the status for the Physical Sensor. This view is useful for obtaining a summary of the Physical Sensor status so that you can better determine any patterns in behavior and activity. Double-click the row representing a Status History. The Physical Sensor Status History Form displays all details about the selected Status. |
Physical Sensor Status History Form
[This is the Context-Sensitive Help topic for the Physical Sensor Status History Form form.]
The Physical Sensor Status History form displays information about the selected Status History entry on the Physical Sensor Form: Status Tab .
Attribute | Description |
---|---|
Status |
Status for the selected Status History entry. NNMi follows the ISO standard for status classification. Possible values are: No Status Normal Disabled Unknown Warning Minor Major Critical Your NNMi administrator might have disabled polling of Physical Sensors using the Monitoring Configuration workspace. The status of the Physical Sensor contributes to the parent Chassis's overall status. For information about how the current status was determined, see the Physical Sensor Form: Conclusions Tab. Status reflects the most serious outstanding conclusion. See Watch Status Colors for more information about possible status values. The Status icons are displayed only in table views. |
Time Stamp | Date and time indicating when the Status History entry was established. |
Conclusions Tab
[This is the Context-Sensitive Help topic for the Physical Sensor form, Conclusions tab.]
The Physical Sensor Form provides details about the selected health metric for the current Physical Sensor.
For information about each tab: See Also
Attribute |
Description |
||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Outstanding Status Conclusions |
The dynamically generated list of summary statuses of the monitored attribute that contributed to the current overall status of the selected Physical Sensor. Status is set by the Causal Engine. Each Conclusion listed is outstanding and contributes to the current overall Status. This view is useful for obtaining a quick summary of the problem description for the current monitored attribute that led up to the Physical Sensor's most current Status. The status value is correlated based on the most critical conclusions. Double-click the row representing a Status Conclusion. The Physical Sensor Status Conclusions Form displays all details about the selected Status Conclusion. The following table describes the possible Conclusions that might appear for a Physical Sensor object. A Y in the Incident? column indicates that the Conclusion results in an incident. Critical Status Conclusions Warning Status Conclusions
Normal Status Conclusions
|
Physical Sensor Status Conclusions Form
[This is the context-sensitive link for the Physical Sensor Status Conclusions form.]
The current Conclusion contributes towards the overall Status of the selected Physical Sensor (see Physical Sensor Form: Status Tab ).
Attribute |
Description |
---|---|
Time Stamp |
The time of the last change in Status. |
Conclusion |
For more information see the Physical Sensor Form: Conclusions Tab. |
Registration Tab
[This is the Context-Sensitive Help topic for the Node form, Registration tab.]
The Physical Sensor Form provides details about the selected Physical Sensor.
For information about each tab:See Also
Attribute | Description |
---|---|
Created |
Date and time the selected object instance was created. NNMi uses the locale of the client and the date and time from the NNMi management server. This value does not change when a node is rediscovered. This is because the Node object is modified, but not created. |
Last Modified |
Date the selected object instance was last modified. NNMi uses the locale of the client and the date and time from the NNMi management server. Note the following:
|
Attribute | Description |
---|---|
ID |
The Unique Object Identifier, which is unique within the NNMi database. |
UUID |
The Universally Unique Object Identifier, which is unique across all databases. |
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: