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 > Monitor Network Health > Configure NNMi Monitoring Behavior > Interface Settings for Monitoring

Interface Settings for Monitoring

[This is the Context-Sensitive Help topic for the Monitoring Configuration: Interface Settings form. WARNING: Do not change bookmark names. They are used in the alias.flali file.]

Before you start, you must establish one or more Interface Group definitions that identify the interface types to which these monitoring settings will apply. NNMi provides nearly 250 interface types to choose from. Interface monitoring applies to matching interfaces and the IP addresses that are hosted on those interfaces. See also, Interface Groups Provided by NNMi.

Tip (Global Network Management) If you have enabled the Discovery of unnumbered Interfaces, on each Regional Manager consider creating an Interface Group based on the Custom Attribute: UnnumberedNextHop and monitoring that Interface Group. Global Managers can be configured to show status for L2 Connections between unnumbered interfaces discovered on all Regional Managers. For more information: See Also

Tip NNMi administrators can check network latency for an Interface Group by adjusting the following for the management addresses associated with the specified group of interfaces:

ICMP polling frequency
ICMP echo request packet data payload size

See the "Maintaining NNMi" chapter in the Network Node Manager i Software Deployment Reference for more information.

Tip (NNMi Advanced) Global Network Management feature - When viewing maps on the Global Manager, if you want to monitor important WAN interface connections between Regional Managers, then within each Regional Manager's Monitoring Configuration settings, enable NNMi's Poll Unconnected Interfaces for each of those WAN interfaces.

To establish monitoring behavior for one or more predefined Interface Groups:

Navigate to the Interface Settings form.
1. From the workspace navigation panel, select the Configuration workspace.
2. Expand the Monitoring folder.
3. Select Monitoring Configuration.
4. Locate the Interface Settings tab.
5. Do one of the following:
  - To create an Interface Settings definition, click the New icon.
  - To edit an Interface Settings definition, select a row and click the Open icon.
  - To delete an Interface Settings definition, select a row and click the Delete button
Establish the appropriate settings to identify this Interface Group Setting definition (see Basics table).
Optional. Configure the Fault Monitoring behavior for this Interface Group Setting definition (see Fault Monitoring table).
(NNM iSPI Performance for Metrics) If the Network Node Manager iSPI Performance for Metrics Software is installed:
- Configure the Performance Monitoring behavior for this Interface Group Setting definition. See Performance Monitoring table.
- Configure the Baseline Settings. Navigate to the Baseline Settings tab. See Configure Baseline Settings for Interfaces.
Optional. Configure thresholds. Navigate to the Threshold Settings tab. See Configure Threshold Monitoring for Interface Groups for more information.
By default, NNMi monitors only interfaces that are connected to other interfaces. When polling is enabled, NNMi automatically detects most connections. See Add or Delete a Layer 2 Connection for information about manual overrides.

Optional. If you want to expand monitoring behavior for this group to include unconnected Interfaces, indicate your choices in the Extend the Scope of Polling Beyond Connected Interfaces group box.
Click Save and Close to return to the Monitoring Configuration form.
Click Save and Close. NNMi applies your changes. The next regularly scheduled monitoring cycle uses the new settings.

Caution When you establish monitoring configuration settings, NNMi must recalculate the settings for all affected objects. This can take some time and slow down your system. Consider making this change during a slow time in your network environment.

To verify that State Poller is working as expected, see Help → System Information and select the the State Poller tab. NNMi displays a report with current details about the State Poller process.
(NNMi Advanced - Global Network Management feature) On each Regional Manager, consider creating an Interface Group based on the Custom Attribute: UnnumberedNextHop and monitoring that Interface Group (Interface Settings for Monitoring):
- To easily share your Interface Group definitions, see Export and Import Configuration Settings.
- The Global Manager's maps can successfully show status for L2 Connections between unnumbered interfaces discovered on all Regional Managers, see Global Manager: Configure Custom Attribute Replication.

Optional. Customize the node monitoring behavior. See Node Settings for Monitoring. Also see Detect Interface Changes.

Basics
Attribute	Description
Ordering	Enter a unique string (any length), characters 0 through 9. Consider using increments of 100 for the flexibility to insert additional items between existing items over time. NNMi decides which monitoring configurations apply to a node or interface based on the ordering number assigned to the configuration definitions. NNMi monitors the device according to the first match (checked from lowest number to highest number within each category). Categories are read in sequence. Click here for a description of the sequence. Interface Settings: NNMi monitors each of the Node's Interfaces and IP Addresses based on the first matching Interface Settings definition. The first match is the Interface Settings definition with the lowest Ordering number, then Baseline Settings. Node Settings: NNMi monitors each Node and each previously unmatched Interface or IP Address based on the first matching Node Settings definition. The first match is the Node Settings definition with the lowest Ordering number, then Baseline Settings. Note Child node groups are included in the Ordering hierarchy. This means that if the parent node group has a lower Ordering number (for example, parent=10, child=20), then the monitoring configuration specified for the parent node group also applies to the nodes in the child node group. To override a parent node group monitoring configuration, set the Ordering number for the child node group to a number that is lower than the parent (for example, parent=20, child=10). Default Settings: If no match is found for a Node, Interface, or IP Address in 1 or 2, NNMi applies the default Monitoring Configuration settings. No duplicate Ordering numbers are permitted. Each Interface Setting ordering number must be unique.
Interface Group	Choose one predefined Interface Group from the list. See Create Interface Groups for more information.

Fault Monitoring
Attribute		Description
Enable ICMP Monitoring:	Enable IP Address Fault Polling	Note This monitoring option is useful for devices that do not support SNMP. If enabled, State Poller issues ICMP (ping) requests to verify the availability of discovered IP address. Note In the Global Control section of this form, the Enable State Polling attribute must be enabled, too. If disabled, State Poller does the following: IP addresses (both previously discovered and newly discovered) have a State attribute value of "Not Polled" and a Status attribute value of "No Status" with the color of the IP address map-symbol set to beige. See Layer 3 Neighbor View. If both ICMP and SNMP are disabled for a Node, the Node has a Status attribute value of "No Status" and the color of the Node map-symbol background shape is set to beige. Tip To turn off ICMP polling within a subset of your network environment, use the Communication Configuration workspace Region definitions. You can define your own Regions that identify any unreachable addresses in your management domain (for example, the private IP addressesThese are IPv4 addresses that can be reused in home and office local area networks (LANs). Following the standards set by RFC 1918 and RFC 4193 (10..., 169.254.., 172.16-31.., and 192.168..*)).
Fault Monitoring:	Enable Interface Fault Polling	If enabled, State Poller monitors all interfaces by issuing SNMP read-only queries to devices assigned to this level of the monitoring hierarchy. By default, any connected interface is monitored for MIB-II ifAdminStatus and ifOperStatus. (ifAdminStatus is set by the device administrator. ifOperStatus indicates the operational status of interface health.) If you have unconnected interfaces that you want to monitor, expand NNMi monitoring behavior with the Poll Unconnected Interfaces and the Poll Interfaces Hosting IP Addresses attributes. Note The following attributes must also be enabled: In the Global Control section of this form, the Enable State Polling attribute must be enabled, too. See Layer 2 Neighbor View. (See Global Control Settings for Monitoring for more information.) In the Communication Configuration view, enable State Poller queries with the applicable Enable SNMP Communication attributes (see Configure communication protocol for more information). If disabled, for devices assigned to this level of the monitoring hierarchy: Causal Engine calculates Status based only on IP address State. The Interface objects previously discovered change to a State attribute value of "Not Polled" and a Status attribute value of "No Status" (plus any related map-symbol changes to a beige color).
Fault Polling Interval		The time that State Poller waits between issuing queries to gather information for any of the following that are enabled: ICMP Polling, SNMP Polling, Poll Unconnected Interfaces, and Poll Interfaces Hosting IP addresses. The default Fault Polling Interval is 5 minutes, except for the Node Group named Microsoft Windows Systems which is 10 minutes. Note NNMi monitors SNMP agents (Management Addresses) according to this Fault Polling Interval, even if ICMP Polling, SNMP Polling, Poll Unconnected Interfaces, and Poll Interfaces Hosting IP addresses are all disabled. To prevent an SNMP Agent's address from being monitored, one of the following must be true: State Polling is disabled, current Communication Configuration settings turn off SNMP for the SNMP agent's address, the parent Node is set to Not Managed or Out of Service, or the parent node belongs to a Monitoring Configuration's Node Group with Enable SNMP and Web Polling on Node disabled.

Performance Monitoring (*NNM iSPI Performance for Metrics*)
Attribute		Description
Requires Network Node Manager iSPI Performance for Metrics Software (NNM iSPI Performance for Metrics). To populate performance data in the dashboard views or enhance NNM iSPI Performance for Metrics reports by sharing NNMi configuration settings, install the optional Network Performance Server (NPS).
LAN Performance Monitoring	Enable Interface Performance Polling	(NNM iSPI Performance for Metrics) Use this attribute to extend the range of polling data that NNMi collects. NNM iSPI Performance for Metrics uses the additional data in a series of performance reports. See Purchase Network Node Manager i Smart Plug-ins and More for more information. When enabled, network traffic increases on your network because NNMi gathers performance data about each member of this group on a regular schedule. If enabled, NNMi gathers basic Interface performance data from Interfaces in devices assigned to this level of the monitoring hierarchy. If disabled, NNMi does not extend data collection behavior to include performance data about Interfaces assigned to this level of the monitoring hierarchy. Note The Enable State Polling field must be enabled, too. By default the performance of connected interfaces and addresses is monitored. If you have unconnected interfaces that you want to monitor, expand NNMi monitoring behavior by enabling Poll Unconnected Interfaces.
WAN Performance Monitoring	Enable DSx Interface Performance Polling	(NNM iSPI Performance for Metrics) Use this attribute to extend the range of polling data that NNMi collects. NNM iSPI Performance for Metrics uses the additional data in a series of performance reports. When enabled, network traffic increases on your network because NNMi gathers performance data about each member of the DSx Interfaces interface group on a regular schedule. See Interface Groups Provided by NNMi for more information. If enabled, NNMi gathers DSx performance data from DSx Interfaces assigned to this level of the monitoring hierarchy. If disabled, NNMi does not gather DSx performance data from DSx Interfaces assigned to this level of the monitoring hierarchy.
	Enable SONET Interface Performance Polling	(NNM iSPI Performance for Metrics) Use this attribute to extend the range of polling data that NNMi collects. NNM iSPI Performance for Metrics uses the additional data in a series of performance reports. When enabled, network traffic increases on your network because NNMi gathers performance data about each member of the SONET Interfaces interface group on a regular schedule. See Interface Groups Provided by NNMi for more information. If enabled, NNMi gathers SONET performance data from SONET Interfaces assigned to this level of the monitoring hierarchy. If disabled, NNMi does not gather SONET performance data from SONET Interfaces assigned to this level of the monitoring hierarchy.
	Enable ATM Interface Performance Polling	(NNM iSPI Performance for Metrics) Use this attribute to extend the range of polling data that NNMi collects. NNM iSPI Performance for Metrics uses the additional data in a series of performance reports. When enabled, network traffic increases on your network because NNMi gathers performance data for each ATM Interface. If enabled, NNMi gathers ATM performance data from ATM Interfaces assigned to this level of the monitoring hierarchy. If disabled, NNMi does not gather ATM performance data from ATM Interfaces assigned to this level of the monitoring hierarchy. Note This option gathers metrics from ATM-MIB and CISCO-AAL5-MIB. See also Configure Discovery of ATM/Frame Relay Interfaces.
	Enable Frame Relay Interface Performance Polling	(NNM iSPI Performance for Metrics) Use this attribute to extend the range of polling data that NNMi collects. NNM iSPI Performance for Metrics uses the additional data in a series of performance reports. When enabled, network traffic increases on your network because NNMi gathers performance data for each Frame Relay Interface. If enabled, NNMi gathers Frame Relay performance data from Frame Relay Interfaces assigned to this level of the monitoring hierarchy. If disabled, NNMi does not gather Frame Relay performance data from Frame Relay Interfaces assigned to this level of the monitoring hierarchy. This option gathers the following types of metrics: Circuit in and out octets, errors, and discards Committed Information Rate (CIR) and Extended Information Rate (EIR) utilization Forward Error Congestion Notification (FECN) and Backward Error Congestion Notification (BECN) counts See also Configure Discovery of ATM/Frame Relay Interfaces.
Performance Polling Interval		(NNM iSPI Performance for Metrics) Use this field to set the time period that NNMi waits between issuing network traffic to gather performance data for the NNM iSPI Performance for Metrics. The default Performance Polling Interval is 5 minutes, except for the Node Group named Microsoft Windows Systems which is 10 minutes.

Extend the Scope of Polling Beyond Connected Interfaces
Attribute	Description
Poll Unconnected Interfaces	If enabled, NNMi monitors all interfaces within discovered devices (both connected and unconnected). All interfaces are monitored for MIB-II ifAdminStatus and ifOperStatus. (ifAdminStatus is set by the device administrator. ifOperStatus indicates the operational status of interface health.) Note The Enable State Polling field must be enabled, and SNMP polling of some type must be enabled (for example, Enable SNMP Fault Monitoring and Enable SNMP Performance Polling). If disabled, State Poller polls according to other configuration settings. Tip Your discovery configuration choices might need to be adjusted to get the results you want. For example, to meet the “connected” criteria for interfaces in switches that do not have an IP address you must add the device to which the interface is connected as a discovery seed. See Specify discovery seeds.
Poll Interfaces Hosting IP Addresses	Note This monitoring option is useful for Router interfaces. If enabled, any unconnected interface that has one or more addresses associated with it is monitored for MIB-II ifAdminStatus and ifOperStatus. (ifAdminStatus is set by the device administrator. ifOperStatus indicates the operational status of interface health.) Note The Enable State Polling field must be enabled, and SNMP polling of some type must be enabled (for example, Enable SNMP Fault Monitoring and Enable SNMP Performance Polling). By monitoring the Interface (in addition to the IP address), NNMi can make more informed decisions about the health of each IP address associated with an unconnected interface. If disabled, State Poller polls according to other configuration settings. Tip The Communication Configuration workspace provides a method of overriding this setting for specific Regions. You can define your own Region to easily turn off polling to any unreachable addresses in your management domain (for example, the private IP addressesThese are IPv4 addresses that can be reused in home and office local area networks (LANs). Following the standards set by RFC 1918 and RFC 4193 (10..., 169.254.., 172.16-31.., and 192.168..*)).
Poll Link Aggregation Interfaces (NNMi Advanced)	If enabled, NNMi monitors any unconnected Link AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG. member interfaces in switch-to-switch and server-to-switch connections: Aggregate member interfaces not connected outside the context of the Aggregator membership. Aggregate member interfaces connected to an undiscovered node (for example, the SLAG upstream switch stack). Tip NNMi calculates the Aggregator status based on current status of all members. This means NNMi changes the status of the Aggregator when one member interface is down, even though the Aggregator is currently functioning well by using the other member interfaces. If disabled, you must ensure that other Monitoring Configuration settings allow NNMi to manage each Aggregator member interface (none accidentally excluded or missed). Otherwise, NNMi calculates Aggregator status based on overall Aggregator behavior.

Send Help Center feedback