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

Use > Access Device Details > Node Sensor Form

Node Sensor Form

[This is the context-sensitive link for the Node Sensor Form]

This form describes the fault and performance metrics used to monitor Node Sensors. NNMi obtains fault metrics from the node's SNMP agent (MIB files). This topic includes the following sections:

Monitored Attributes Tab
Physical Components Tab
Incidents Tab
Status Tab
Conclusions Tab
Registration Tab

For information about each tab: See Also

Node Sensors are displayed in three views: Node Sensors View, Non-Normal Node Sensors View, and Unmanaged Node Sensors View.

Basic Attributes
Attribute	Description
Status	Overall status for the current Node 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 Node Sensor that has the health attribute being measured, For example, NNMi measures fault metrics. (NNM iSPI Performance for Metrics) If licensed and installed, Network Node Manager iSPI Performance for Metrics Software also measures performance metrics for CPU, disk, memory, and buffer utilization as well as for buffer failures and misses. When possible, NNMi obtains the Name value for the Node Sensor from the associated SNMP agent. The number of MIBs available and subsequently the number of health attributes that are measured for each Node Sensor vary. For example, if the Node Sensor is of type Buffer, up to five MIBs that contain information about Buffers (Small, Medium, Large, Big, and Huge). NNMi collects information from each MIB that is available and lists a Node Sensor Name value for each. For example, If all five MIBs are available, you see the following Node Sensors listed in the Node Sensor table: Small Buffers, Medium Buffers, Large Buffers, Big Buffers, and Huge Buffers. 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. (NNM iSPI Performance for Metrics) The following examples require an Network Node Manager iSPI Performance for Metrics Software license: Buffer See Also Buffer Failure Rate Buffer Miss Rate Buffer Utilization CPU utilization See Also CPU 1Min Utilization CPU 5Min Utilization CPU 5Sec Utilization Disk Space Utilization See Also Memory Utilization See Also
Management Mode	The calculated Management Mode for the node sensor according to the Management Mode Hierarchy. This value reflects the current management mode of this node sensor's parent object (the Hosted On 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 node sensor. Possible values are: Inherited – Used to indicate that the Node Sensor should inherit the Management Mode from this node sensor's parent object (the Hosted On Node). Not Managed – Used to indicate that NNMi does not discover or monitor the Node Sensor. Out of Service – Used to indicate a Node Sensor is unavailable because it is out of service or participating in a Scheduled Node Outage. NNMi does not discover or monitor this Node 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.
Hosted On Node	Node on which the health metric is being measured. This is the current value in NNMi’s database for the Name attribute of the host device. See Node Form for more information. The NNMi administrator can set Physical Sensor thresholds. For more information, see Node Form: Node Sensors Tab, Chassis Form: Node Sensors Tab and Card Form: Node Sensors Tab.

Monitored Attributes Tab

[This is the Context-Sensitive Help topic for the Node Sensor form, Monitored Attributes tab.]

The Node Sensor Form provides details about the monitored attributes (for example, Memory Utilization) related to the current Node Sensor. The State of monitored attributes can be influenced by thresholds configured by your NNMi administrator.

For information about each tab: See Also

Attributes Table
Description
Table view of the Name, State, and Last Modified time for each monitored attribute associated with the selected Node Sensor. Use this view to determine the State of each monitored attribute. Double-click the row representing a Monitored Attribute. The Node Sensor Monitored Attribute Form displays all details about the selected Monitored Attribute.

Node Sensor Monitored Attribute Form

[This is the Context-Sensitive Help topic for the Node Sensor Monitored Attribute form.]

The Node Sensor Monitored Attribute form displays information about the attribute selected on the Node Sensor Form: Monitored Attributes Tab.

NNMi obtains fault metric information from the associated MIB.

(NNM iSPI Performance for Metrics) If the Network Node Manager iSPI Performance for Metrics Software is installed and configured within your environment, the Node Component: Monitored Attributes tab also displays information about node health related to the following performance metrics. The NNMi administrator sets the threshold for node sensors related to performance metrics:

Buffer Failure Rate
Buffer Miss Rate
Buffer Utilization
CPU 5Sec Utilization
CPU 1Min Utilization
CPU 5Min Utilization
Disk Space Utilization
Memory Utilization

Basics Attributes
Attribute	Description
Label	Name used to identify the attribute being monitored. See Node Sensor Form for more information. The Name of each health attribute identifies the attribute being measured as well as the type of MIB used to gather this information. For example, when monitoring CPU utilization, NNMi uses values measured for 1-minute, 5-minute, and 5-second intervals. Each of these values might be available from an old, standard, or most recent (revised) MIB file. The following example health attribute names indicate the CPU measurement interval as well as the fact that the information was collected from the most recent (revised) MIB: CPU Revised 1 Minute CPU Revised 5 Minute CPU Revised 5 Second
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 Monitored Attribute. 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. (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.

Physical Components Tab

[This is the Context-Sensitive Help topic for the Node Sensor form, Physical Components tab.]

The Node Sensor Form provides details about the monitored attribute (for example, Memory Utilization) related to the current Node Sensor.

For information about each tab: See Also

Physical Components Table
Description
Table of all of the Physical Components (Chassis and Cards) that are associated with the selected Node Sensor. Use this table to access information about each Chassis or Card that is associated with the selected Node Sensor. The information displayed includes, but is not limited to, the physical component State, Status, model, type, and serial number, as well as the firmware, software, and hardware version. Double-click the row representing a the Physical Component of interest. The Chassis Form displays all details about the selected Chassis. The Card Form displays all details about the selected Card.

Incidents Tab

[This is the Context-Sensitive Help topic for the Node Sensor form, Incidents tab.]

The Node Sensor Form provides details about the selected node sensor.

For information about each tab:See Also

Incidents Associated with this Node Sensor
Attribute	Description
Incidents	Table of the Incidents associated with the selected node 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 node 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 Node Sensor form, Status tab.]

The Node Sensor Form provides details about the selected Node Sensor.

For information about each tab:See Also

Overall Status
Attribute	Description
Status	Overall status for the current Node 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 Node Sensors using the Monitoring Configuration workspace. The status of the Node Sensor contributes to the parent Node's overall status. For information about how the current status was determined, see the Node 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.

Status History Table
Attribute	Description
Status History	List of the last 30 changes in the status for the Node Sensor. This view is useful for obtaining a summary of the Node Sensor status so that you can better determine any patterns in behavior and activity. Double-click the row representing a Status History. The Node Sensor Status History Form displays all details about the selected Status.

Node Sensor Status History Form

[This is the Context-Sensitive Help topic for the Node Sensor Status History Form form.]

The Node Sensor Status History form displays information about the selected Status History entry on the Node Sensor Form: Status Tab .

Overall Status
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 Node Sensors using the Monitoring Configuration workspace. The status of the Node Sensor contributes to the parent Node's overall status. For information about how the current status was determined, see the Node 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 Node Sensor Form provides details about the selected health metric for the current Node Sensor.

For information about each tab: See Also

Outstanding Status Conclusion Values

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 Node 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 Node 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 Node Sensor Status Conclusion Form displays all details about the selected Status Conclusion.

The following table describes the possible Conclusions that might appear for a Node Sensor object.

A Y in the Incident? column indicates that the Conclusion results in an incident.

Critical Status Conclusions

Conclusion	Description	Status	Incident?
BufferOutOfRangeOrMalfunctioning	The buffer pool monitored attributes are outside of the threshold range configured for the device. This incident indicates the buffer pool is exhausted or cannot meet the demand.	Critical	Y
CpuOutOfRangeOrMalfunctioning	Any of the following utilization averages is above the threshold range configured for the device: CPU 5 second utilization CPU 1 minute utilization CPU 5 minute utilization	Critical	Y
DiskOutOfRangeOrMalfunctioning	The disk monitored attributes are outside of the threshold range configured for the device.	Critical	Y
MemoryOutOfRangeOrMalfunctioning	The Source Node's memory pool is outside of the threshold range configured for the device. This incident indicates the memory pool is exhausted or cannot meet the demand for use.	Critical	Y

Warning Status Conclusions

Conclusion	Description	Status	Incident?
BufferAbnormal	The buffer utilization is abnormal based on the computed baseline.	Warning	Y
CpuAbnormal	The CPU utilization is abnormal based on the computed baseline for one of the following: CPU 5 second utilization CPU 1 minute utilization CPU 5 minute utilization	Warning	Y
DiskAbnormal	The disk space utilization is abnormal based on the computed baseline.	Warning	Y
MemoryAbnormal	The memory utilization is abnormal based on the computed baseline.	Warning	Y

Normal Status Conclusions

Conclusion	Description	Status	Incident?
BufferInRangeAndFunctioning	The buffer pool is operating within the threshold range configured for the device.	Normal	N
BufferNormal	The buffer utilization is normal based on the computed baseline.	Normal	N
CpuInRangeAndFunctioning	All of the following utilization averages are within the threshold range configured for the device: CPU 5 second utilization CPU 1 minute utilization CPU 5 minute utilization	Normal	N
CpuNormal	The CPU utilization is normal based on the computed baseline for the following: CPU 5 second utilization CPU 1 minute utilization CPU 5 minute utilization	Normal	N
DiskInRangeAndFunctioning	The disk monitored attributes are within the threshold range configured for the device.	Normal	N
DiskNormal	The disk space utilization is normal based on the computed baseline.	Normal	N
MemoryInRangeAndFunctioning	The specified memory pool is operating within the threshold range configured for the device.	Normal	N
MemoryNormal	The memory utilization is normal based on the computed baseline.	Normal	N

Node Sensor Status Conclusion Form

[This is the context-sensitive link for the Physical Sensor Conclusion form.]

The current Conclusion contributes towards the overall Status of the selected Node Sensor (see Node Sensor Form: Status Tab ).

Outstanding Status Conclusion Values
Attribute	Description
Time Stamp	The time of the last change in Status.
Conclusion	For more information see the Node Sensor Form: Conclusions Tab.

Registration Tab

[This is the Context-Sensitive Help topic for the Node Sensor form: Registration tab.]

The Node Sensor Form provides details about the selected Node Sensor.

For information about each tab:See Also

Registration Attributes
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: When a node is rediscovered, the Last Modified time is the same as the Discovery Completed time. This is because the node’s Discovery State changes from Started to Completed. When a Node is initially discovered, the Last Modified time is slightly later than the Created time. This is because node discovery does not complete until after the Node is created.

Object Identifiers Attributes
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.

Send Help Center feedback