Chapter 5: Accessing Device Details. Hewlett Packard Enterprise 10.20
Reklama
Reklama
Chapter 5: Accessing Device Details
NNMi provides forms that help you easily view all details associated with a managed object, such as a node,
SNMP agent, interface, address, subnet, or connection.
NNMi also provides an Analysis Pane that displays related information about an object. NNMi performs the appropriate analysis on the object and determines the related information to display. See
Pane " on page 482 for more information.
From a table view, to view all details associated with an object:
1. From the workspace navigation panel, select a workspace containing a view of the object of interest.
2. Select a view that contains the specific object (for example, Inventory workspace, Nodes view).
3. Double-click the row representing an object.
4. The form displays, containing details of all information related to the object.
5. View or edit the details of the selected object:
•
•
•
•
•
Web Agent Form (NNMi Advanced)
•
•
•
•
•
•
•
•
•
•
•
Router Redundancy Group Form (NNMi Advanced)
•
•
•
MPLS WAN Cloud (RAMS) Form (NNMi Advanced)
•
You can also access: l
"MIB Variable Form" on page 329
l
"Router Redundancy Member Form (NNMi Advanced)" on page 281
HPE Network Node Manager i Software (10.20) Page 62 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
From a map view, to view all details associated with an object:
1. Display a map using the Topology Maps or Troubleshooting workspace, or the Actions → menu.
Tip: You can also right-click any object in a table or map view to access the items available within the Actions menu.
Note: If the map requires a starting node before it displays, enter the name or
IP Address for the starting node you want to use.
2. After the map displays, select the object and click the
Open icon in the tool bar.
3. The form displays, containing details of all information related to the object.
4. View or edit the details of the selected object.
From an Analysis Pane, to view all details associated with an object:
1.
l
Access the Analysis Pane from a table view:
i. Select the workspace of interest (for example,
Inventory).
ii. Select the view that contains the object of interest (for example, the Nodes view).
iii. Select the row that contains the object of interest.
iv. NNMi displays detailed information at the bottom of the view in the Analysis Pane.
l
Access the Analysis Pane in a map view:
i. Select the workspace of interest (for example,
Topology Maps).
ii. Select a map view (for example, select Routers).
Note: If the map requires a starting node before it opens, enter the name or
IP Address for the starting node you want to use.
iii. Click the map object of interest.
iv. NNMi displays detailed information at the bottom of the view in the Analysis Pane.
l
Access the Analysis Pane in a form:
o
Click the form's toolbar Show Analysis icon to display information about the current form's toplevel object in the Analysis Pane.
Note:
Show Analysis always displays the top-level object's information.
o
Click a row in a table on one of the form's tabs to display detailed information about the selected object in the Analysis Pane.
NNMi displays detailed information at the bottom of the form in the Analysis Pane. See Working with
Objects for more information about forms.
HPE Network Node Manager i Software (10.20)
Page 63 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
2. Open the Analysis Pane if necessary by clicking the expand button in the Analysis Pane banner bar:
If you change views, NNMi clears the Analysis Pane. The Analysis Pane remains blank unless an object is selected.
If you select multiple objects, the Analysis Pane displays data about the first selected object.
3. Using the Analysis Pane: l
To resize, place your mouse cursor over the title bar to display the ↕ symbol and drag to adjust the size.
l
To refresh a subset of information in the Analysis Pane, click any displayed Refresh icon .
To refresh all data in the Analysis Pane, open the object's form and click Refresh or Save.
l
To launch an SNMP Line Graph for the selected metric, click the icon that appears at the bottom of each gauge.
l
To select and copy the tooltip information, double-click the gauge. NNMi opens a text window that enables you to select and copy the tooltip information.
l
The Gauges tab shows real-time SNMP gauges to display State Poller and Custom Poller SNMP data.
o
These gauges are displayed for Nodes, Interfaces, Custom Node Collections, and for Node
Sensors of type CPU, Memory, or Buffers, and Physical Sensors of type Backplane.
o
NNMi displays a gauge for each significant MIB Object Identifier (OID) that the node or interface supports, up to the default maximum of 24.
Tip: If you are an NNMi administrator, for information about using the nms-ui.properties
file to change this default, see the "NNMi Console" chapter in the HPE Network Node
Manager i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
o
Each gauge displays the current OID value, using the default refresh rate of 15 seconds.
Tip: If you are an NNMi administrator, for information about using the nms-ui.properties
file to change this default, see the "NNMi Console" chapter of the HPE Network Node
Manager i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
o o o
The value range displayed indicates the OID minimum and maximum values that NNMi has encountered.
For any gauge that tracks percentage values, NNMi uses a red line to indicate where the OID value is near 100 percent.
There is not a one-to-one match between the OIDs used to analyze monitoring thresholds and those displayed in the Analysis Pane. For example, the Analysis Pane might display a Cisco
HPE Network Node Manager i Software (10.20)
Page 64 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Memory Pool OID value that does not match the value used to calculate whether the Memory
Utilization Monitored Attribute threshold is reached or exceeded. This is because some threshold metrics require more complex calculations than a single OID allows.
If a gauge label appears to be a duplicate value, mouse over the label to view the more complete tooltip name that appears.
Tip: If you are an NNMi administrator, to change the gauge title - for example, to the SNMP
MIB variable name - see the "Maintaining NNMi" chapter of the HPE Network Node Manager
i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.)
Related Topics:
Using Table Views
Using Map Views
Node Form
The Node form provides details about the selected node. It also provides details about the
, the
SNMP Agent
1
, the
Web Agent
2
, the
, and the
associated with this node.
If your role permits, you can use this form to modify the
for a node (for example to indicate it will be temporarily out of service) or add
to communicate information about this node to your team.
For information about each tab:
Tip: To see details about the SNMP Agent and Web Agent associated with the node, go to the Managing
Agents section in the
. Click on the Agent Name in any row to see more details about the status of each agent by opening the
or
Basic Attributes
Attribute Description
Name The dynamically generated name assigned to this device.
The NNMi administrator configures how NNMi populates this attribute through two configuration settings: (1) The Node Name Resolution attributes in Discovery
Configuration (full or short DNS name, full or short sysName, IP address). (2) The Name
might be converted to all uppercase or all lowercase (depending on how the NNMi administrator configured settings in the nms-topology.properties file). See the
1
Simple Network Management Protocol (SNMP) is an Internet-standard protocol used to manage devices on
IP networks. The SNMP Agent uses this protocol to report information to authorized management programs.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 65 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Hostname
"Modifying NNMi Normalization Properties" section of the HPE Network Node Manager i
Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
This name is used in table views and maps.
The fully-qualified hostname currently stored in the NNMi database for this device
(according to any hostname resolution strategy currently in use in your network environment; for example, DNS).
NNMi follows a set of rules to dynamically generate the value stored in the NNMi database for each Node's Hostname.
Click here for details.
l
If the Node supports SNMP, NNMi requests the Hostname using the IP Address of the associated SNMP agent (the Management Address attribute value on the Node form).
When the NNMi administrator chooses Enable SNMP Address Rediscovery in the
Communication Configuration: l
If the SNMP Agent does not respond, NNMi checks for another Management
Address to request the Hostname, and the Hostname could change.
l
If the SNMP Agent associated with the node changes, the Management Address and
Hostname could change.
When the NNMi administrator disables Enable SNMP Address Rediscovery in the
Communication Configuration, when the current management address (SNMP agent) becomes unreachable, NNMi does not check for other potential management addresses.
l
If the Node does not support SNMP, no Management Address is available. NNMi requests a Hostname starting with the lowest IP Address associated with the node (a
Discovery Seed value or an IP address value gathered from a neighboring device). NNMi uses the first Hostname provided. The Hostname might change during a future discovery cycle.
Note: NNMi administrators can use NNMi property file settings to change the way
NNMi determines Hostname values: l l nms-topology.properties file settings:
If DNS is the source of the Node's Hostname, there are three choices. By default
NNMi uses the exact Hostname from your network configuration. It is possible to change NNMi behavior to convert Hostnames to all uppercase or all lowercase. See the "Modifying NNMi Normalization Properties" section of the HPE Network Node
Manager i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
nms-disco.properties file settings:
The Hostname is either requested from the Node's lowest loopback interface IP address that resolves to a Hostname or requested from the Node's designated
Management Address (SNMP agent address). With either choice, when no IP address resolves to a Hostname, the IP address itself becomes the Hostname. See
HPE Network Node Manager i Software (10.20)
Page 66 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
the "Maintaining NNMi" chapter of the HPE Network Node Manager i Software
Deployment Reference, which is available at: http://softwaresupport.hpe.com.
Management
Address
IP address NNMi uses to communicate with this node through SNMP. This is the IP address of the device's SNMP agent.
Tip: The NNMi administrator can specify an address (Communication Configurations workspace, Specific Node Settings tab), or NNMi can dynamically select one.
When NNMi first discovers a node, the seed address (provided by the NNMi administrator) or discovered address (for non-seeded nodes) becomes the initial Management Address of the node. After NNMi builds an inventory of all IP addresses associated with the node,
NNMi follows a set of rules to determine which address is the best choice as the node's
Management Address.
Click here for details.
Note: (NNMi Advanced) The NNMi administrator specifies whether NNMi prefers IPv4 addresses, IPv6 addresses, or dual-stack (both) when selecting the Management
Address. See Configure Default SNMP, Management Address, and ICMP Settings .
1. NNMi ignores the following addresses when determining which Management Address is most appropriate: l
Any address of an administratively-down interface.
l
Any address that is virtual (for example,
VRRP
1
).
l
Any IPv4
Anycast Rendezvous Point IP Address
2 or IPv6 Anycast address.
l
Any address in the reserved loopback network range. IPv4 uses 127/24
( 127.*.*.*) and IPv6 uses ::1.
l
Any
IPv6 link-local address
3
.
2. If the NNMi Administrator chooses Enable SNMP Address Rediscovery
in
Communication Configuration, NNMi prefers the last-known Management Address (if any).
3. If the Management Address does not respond and the NNMi Administrator specifies
1
Virtual Router Redundancy Protocol
2
Rendezvous Point addresses are loopback addresses used for routers in multi-cast network configurations.
3
A non-routable IPv6 unicast address only used for communication with other nodes on the same link (LAN or
VLAN). Link local addresses cannot be used for communication that must be forwarded through a router. IPv6 auto-configuration automatically assigns a unique link local address in the fe80::/10 address space to each
IPv6-enabled interface on a system.
HPE Network Node Manager i Software (10.20)
Page 67 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Enable SNMP Address Rediscovery in Communication Configuration, NNMi uses the
Communication Configuration settings for Management Address Selection. The NNMi
Administrator chooses the order in which NNMi checks the following: l
Seed IP / Management IP - If the NNMi Administrator configures a Seed, NNMi uses the Seed address (either a specified IP address or the DNS address associated with a specified hostname) only during initial Discovery. NNMi then requests the current Management Address (the address from which the node's
SNMP Agent responds) and uses that IP address for all communication after initial discovery.
l
Lowest Loopback - If a node supports multiple
loopback address
1
, NNMi queries each loopback addresses, starting with the lowest number. NNMi uses the loopback address with the lowest number from which the SNMP agent responds
(for example, 10.16.42.197 is a lower number than 10.16.197.42).
l
Highest Loopback - If a node supports multiple
loopback address
2
, NNMi queries each loopback addresses, starting with the highest number. NNMi uses the loopback address with the highest number from which the SNMP agent responds.
l
Interface Matching - The NNMi Administrator chooses which interface MIB variable
NNMi queries to detect changes. NNMi can use the following MIB-II attribute values: ifIndex, ifName, ifDescr, ifAlias, or a combination of these (ifName or ifDescr, ifName or ifDescr or ifAlias). NNMi searches current database entries for information about the interface in this order: index, alias, name, and description.
If multiple IP addresses are associated with the interface, NNMi starts by querying the lowest IP address and selects the first responding address in ascending order.
4. If no response, NNMi queries any remaining IP addresses in the node's IP address inventory, starting with the lowest number. NNMi uses the address with the lowest number from which the SNMP agent responds.
5. If no response, NNMi checks for any Mapped Address configured for one of the currently known addresses (see the Mapped Address column in the Custom
IP Addresses view).
1
The address associated with the loopback interface. The loopback interface is a virtual interface on a device that provides a route for internal communication. Many vendors provide a specially configured loopback for management purposes. Exact details of how loopbacks are configured varies by vendor and model. See each device's documentation for details. NNMi identifies these loopback addresses by using ifType Number 24, softwareloopback from the IANA ifType-MIB.
2
The address associated with the loopback interface. The loopback interface is a virtual interface on a device that provides a route for internal communication. Many vendors provide a specially configured loopback for management purposes. Exact details of how loopbacks are configured varies by vendor and model. See each device's documentation for details. NNMi identifies these loopback addresses by using ifType Number 24, softwareloopback from the IANA ifType-MIB.
HPE Network Node Manager i Software (10.20)
Page 68 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Status
Note: The address represents a static Network Address Translation (NAT) pair's
external IP address from the internal/external IP address pair. NNMi
Administrators configure these pairs using the Overlapping IP Address Mapping form. NNMi uses this list of addresses starting with IPv4 from low to high, then
IPv6 from low to high.
6. If no response, NNMi might be configured to repeat the sequence using SNMPv1,
SNMPv2c, or SNMPv3 in the order specified by the NNMi administrator
(Communication Configurations SNMP Minimum Security Level settings).
7. When all else fails, NNMi retains the last known Management Address (if any) and automatically changes the State of that SNMP Agent object to Critical.
This process is repeated during each Spiral Discovery cycle, and the Management Address can change. For example, NNMi's inventory of addresses for the node expands, or the current Management Address does not respond to SNMP queries due to network problems or node reconfiguration. The NNMi administrator can prevent changes to the management address using the Communication Configurations Enable SNMP Address Rediscovery
(disabled) or Preferred Management Address setting.
If this field shows unexpected results: l
Use the Actions → Polling → Configuration Poll command to gather the most current information about this node.
Tip: You can also right-click any object in a table or map view to access the items available within the Actions menu.
l
Check with your NNMi administrator. The NNMi administrator can configure a specific management address for this node in the Communication Configuration settings.
Note: If the device does not support SNMP, this field is empty.
Overall status for the current node. NNMi follows the ISO standard for status classification.
See the
"Node Form: Status Tab" on page 93
for more information. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
HPE Network Node Manager i Software (10.20)
Page 69 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Major
Critical
The status of all IP addresses and the SNMP associated with this node contribute to node status. For information about how the current status was determined, see the
. Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
(NNMi Advanced) If a Web Agent is associated and the node is a Virtual Machine, note that the following categories indirectly indicate the current condition of the
hypervisor
1
:
Indicates that the hypervisor is Up
Indicates that the hypervisor is Down
Indicates a Null value in hypervisor state
Note: The icons are displayed only in table views.
Power State (NNMi Advanced) NNMi displays this attribute only in Node forms of VMware virtual machines:
Powered On – Indicates the device is turned on.
Powered Off – Indicates the device is turned off.
Suspended – Indicates the device is suspended.
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.
1
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 70 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Node
Management
Mode
Indicates whether or not NNMi is currently monitoring the node. Possible values are:
Managed – Indicates the node is managed by NNMi.
Not Managed – Indicates the node is intentionally not managed. For example, the node might not be accessible because it is in a private network. NNMi does not update discovery information or monitor these nodes.
Out of Service – Indicates a node is unavailable because it is out of service or participating in a
Scheduled Node Outage . NNMi does not update discovery
information or monitor these nodes. See the
for more details.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting. NNMi uses this setting in a variety of ways. See
"How NNMi Assigns the Management Mode to an Object" on page 591
.
(NNMi Advanced - Global Network Management feature) Any change to the Node's
Management Mode setting is immediately sent from a Regional Manager (NNMi management server) to the Global Manager. (Changes to Management Mode for other objects are sent during the next Spiral Discovery cycle on the Regional Manager.)
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode. To change the Management Mode back to Managed for the selected Node object and change the Management Mode back to Managed or
Inherited for all associated interfaces and addresses, use the Actions →
Management Mode → Managed (Reset All).
Device
Profile
Security
Group
Name of the device profile that determines how devices of this type are managed and the icon and background shape displayed on maps.
Click the Lookup icon and select Open to display the
"Device Profile Form" on page 107
for more information.
Security Group Mappings specify which User Groups have access a node. NNMi users see only those nodes assigned to their Security Group Mapping. You see a node and its associated incidents only if one of the User Groups to which you belong is mapped to that node's Security Group.
NNMi administrators assign each node to a Security Group. Each node is associated with only one Security Group. An NNMi administrator can use this attribute to change the
Security Group for a node.
Note: This attribute displays after the NNMi administrator defines more than one
Security Group.
Hosted On
Node
(NNMi Advanced) This attribute appears when you are viewing a node form for either: l a partitioned virtual instance of another node
HPE Network Node Manager i Software (10.20)
Page 71 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
l a
virtual machine
1
(hosted by a
hypervisor
2
)
This attribute is the Name of the node hosting (providing) this virtual 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 host node.
Tip: When the form you are viewing represents a virtual machine (hosted by a hypervisor), this attribute might temporarily not be known. For example: l
NNMi might discover the virtual machine before discovering the hypervisor.
l
The hypervisor owning this virtual machine has recently changed. NNMi has not yet gathered details from the new hypervisor.
Tenant Tenants enable NNMi administrators to partition a network across multiple customers.
A Tenant is the top-level organization to which a Node belongs.
NNMi administrators can use this drop-down to change the Tenant assignment for a Node, or use the Lookup icon and select New to create a new Tenant. Use caution when changing the Tenant assignment, see Change Tenant Assignment for a Node .
Devices that belong to the Default Tenant can have Layer 2 Connections to any device in any Tenant. Devices within any Tenant other than Default Tenant can have Layer 2
Connections only to devices within the same Tenant or the Default Tenant.
NNMi
Management
Server
(NNMi Advanced) This attribute only appears if the Global Network Management feature is enabled and you are using a Global Manager. See
"NNMi's Global Network Management
Feature (NNMi Advanced)" on page 29
for more information.
Local = The NNMi management server you are currently signed into.
<name> = The name your NNMi administrator assigned to a Regional Manager (NNMi management server). If you see a <name> value, it means that you are currently signed into a Global Manager, and other NNMi management servers report to this NNMi management server.
1
A device that utilizes components from multiple physical devices. Depending on the manufacture's implementation, the virtual machine may be static or dynamic.
2
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 72 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Discovery Attribute
Attribute Description
Discovery
State
Current discovery status for the node. Possible values are:
Newly Created – Indicates the node's hostname and associated IP addresses are in the
NNMi database, but NNMi needs to collect more information before determining state, status, and connectivity to other devices in your network environment.
Discovery Completed – Indicates that NNMi collected all of the required information about the node.
Rediscovery in Process – Indicates NNMi is updating information about the node.
Last
Completed
Time of the last discovery cycle.
Notes Attribute
Attribute Description
Notes (NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
Provided for network operators to use for any additional notes required to further explain the node. Information might include why the node is important, if applicable, or to what customer, department, or service the node is related. Additional information might include where the nodes is located, who is responsible for it, and its serial number. You might also track maintenance history using this attribute.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your node table views based on this value. Therefore, you might want to include keywords for this attribute value.
Node Form: General Tab
The
provides details about the selected node.
For information about each tab:
System Properties
Attribute Description
System
Name
The MIB II sysName value returned from the device's SNMP agent. This attribute is set by the device administrator.
If sysName is part of the strategy used to populate the node Name attribute value, NNMi avoids populating the NNMi database with multiple devices having the same manufacturer's
HPE Network Node Manager i Software (10.20)
Page 73 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
System Properties, continued
Attribute Description
System
Contact default name by following a set of rules.
Click here for details.
For each device type, NNMi has a Device Profile that includes a record of the manufacturer's default sysName. Other settings within the Device Profile can change the way NNMi determines sysName values.
To view the Device Profile associated with this node, locate the
in the
Basics section of the Node form, and click the can make changes to a Device Profile, if necessary.
Lookup icon. Your NNMi administrator
Optional MIB-II sysContact value. This attribute is set by the device administrator. It usually includes the contact person for the managed node as well as information about how to contact this person.
Optional MIB sysLocation value for the physical location of the current node. For example,
Building K, 3rd floor. This attribute is set by the device administrator.
System
Location
System
Object ID
MIB-II sysObjectID value provided by the vendor. This value identifies the device vendor, type, and model. For example, all Cisco 6509 devices have the same system object ID.
System
Description
Optional MIB-II sysDescr value for the device description. This attribute is set by the device administrator.
Managing Agents
Attribute Description
Agent Type Type of the agent (SNMP or Web).
Tip:
l l
Each physical device configured with an SNMP Agent will have an SNMP Agent.
Each
hypervisor
1 could have two agents: l
SNMP Agent gathering
SNMP
2 data.
l
Web Agent gathering
SOAP
3 data from the VMware VSphere® WebService.
l
Each virtual machine provided by the hypervisor has only the Web Agent.
Agent Name Indicates whether the agent is an SNMP Agent or Web Agent.
For Web Agents hosted on VMware hypervisors, the field shows VMware vSphere.
1
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
2
3
Simple Network Management Protocol
Simple Object Access Protocol
HPE Network Node Manager i Software (10.20)
Page 74 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Managing Agents, continued
Attribute Description
For SNMP Agents, the field shows the combination of the SNMP version used by the agent
(for example, SNMPv2c) and the IP address of the agent.
To see more details about an
SNMP Agent
1 or
Web Agent
2
, click the agent name to open the
or
The FQDN or IP address of the system that hosts the agent.
Hosted On
Agent Status The status of the node that hosts the agent.
Agent State Indicates whether the agent assigned to this node is available and how NNMi is interacting with this agent. Possible values are:
For the SNMP Agent:
Normal – Indicates that the agent responds to requests requiring authentication and login.
Not Responding – Indicates that the SNMP agent does not respond to requests requiring authentication and login.
Not Polled – Indicates that this SNMP Agent's address 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. The SNMP Agent’s address might or might not have an associated polling policy.
No Polling Policy – Indicates that this SNMP Agent's address is being polled, but no polling policy exists in any Monitoring Configuration settings for this monitored attribute.
Unset – Currently not used by NNMi.
For the Web Agent:
Normal – Indicates that the agent responds to requests requiring authentication and login.
Not Responding – Indicates that the Web Agent does not respond to requests requiring authentication and login.
Not Polled – Indicates that this Web Agent 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. The Web Agent might or might not have an associated polling policy.
No Polling Policy– Indicates that this Web Agent is being polled, but no polling policy
1
Simple Network Management Protocol (SNMP) is an Internet-standard protocol used to manage devices on
IP networks. The SNMP Agent uses this protocol to report information to authorized management programs.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 75 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Managing Agents, continued
Attribute Description
exists.
Unset – Currently not used by NNMi.
State is determined by the State Poller Service. The current state contributes towards the status calculation for the node. See the
for more information.
SNMP Agent
Enabled
Indicates whether the agent is set up to communicate with NNMi.
Node Form: IP Addresses Tab
The
provides details about the selected node.
(NNMi Advanced) This table could include all associated IPv4 addresses and IPv6 addresses.
For information about each tab:
IP Addresses Table
Attribute Description
IP
Addresses
Table view of the IP addresses associated with the selected node. You can use this table to determine the status, state, address, interface, and subnet for each address associated with the selected node.
Double-click the row representing an IP address. The
displays all details about the selected IP address.
Node Form: Interfaces Tab
The
provides details about the selected node.
For information about each tab:
Interfaces Table
Attribute Description
Interfaces Table view of all of the interfaces associated with the current node.
If the interface is physical, you can use this table to determine the status, administrative state, operational state, name, type, interface speed, and Layer 2 Connection for each interface associated with the selected node.
If NNMi is also managing a virtual environment, use this table to also view the details about any interface that represents a virtual switch. These interfaces will have either a blank or 0 bps
IfSpeed value.
Double-click the row representing an interface. The
displays all details about the selected interface.
HPE Network Node Manager i Software (10.20)
Page 76 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Node Form: Virtual Switches Tab
(NNMi Advanced) The
provides details about the selected
hypervisor
1 node.
Note the following: l
Use the Virtual Switches tab to view details of the virtual switch (also known as virtual bridge)
configured on the selected node.
l
For devices that implement virtual switches (or bridges) as a network interface, these interfaces are identified using the Virtual Bridge capability.
l
When you select a virtual switch from the table, the Analysis Pane includes tabs for the associated
Uplinks and Virtual Ports.
For information about each tab:
Virtual Switches Table
Attribute Description
Interfaces Table view of all of the interfaces representing a virtual switch that is configured on the selected hypervisor.
Double-click the row representing a virtual switch. The
"Virtual Switch's Interface Form (NNMi
displays all details about the selected interface that represents a virtual switch.
Node Form: Chassis Tab
The
provides details about the selected node.
When more than one Chassis is listed in this tab, the map icon changes to a stacked image:
Node Switch Switch-Router
Click to display the entire group of Chassis. If your NNMi role allows, click the Save Map toolbar button to keep the Chassis visible when you return to that map in the future. For example:
1
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 77 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
Tip: If the current node reports a list of
, this is the group of chassis used by this node and all its hosted nodes.
Chassis Table
Attribute Description
Chassis Table view of all of the Chassis associated with the current Node.
Double-click the row representing a Chassis. The
displays all details about the selected Chassis.
Node Form: Cards Tab
The
provides details about the selected node.
For information about each tab:
Tip: If the current node reports a list of
, this is the group of cards used by this node and all its hosted nodes.
Cards Table
Attribute Description
Cards Table view of all of the cards associated with the current node.
Double-click the row representing a Card. The
displays all details about the selected Card.
Node Form: Ports Tab
The
provides details about the selected node.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 78 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Ports Table
Attribute Description
Ports Table view of all of the ports associated with the selected node. Use this table to access information about each port associated with the selected node.
Double-click the row representing a port. The
displays all details about the selected port.
Node Form: VLAN Ports Tab
Tip: The
provides details about the selected node.
For information about each tab:
(NNMi Advanced - Global Network Management feature) There might be slight differences between the VLAN information shown on Regional Managers and Global Managers, because the VLAN calculations use
data.
VLAN Ports Table
Attribute Description
VLAN
Ports
Table view of all of the VLAN ports associated with the current node. Use this table to determine all port and VLAN combinations associated with this node.
Double-click the row representing a VLAN port. The
displays all details about the selected VLAN port.
VLAN Port Form
The VLAN Port form provides details about the VLAN port you selected on the Node or Interface form. The following table describes the fields included on the VLAN Port form.
Basic Attributes
Attribute Description
Local
VLAN
Name
VLAN connections are determined by a common VLAN Id. The name assigned to that
VLAN can be designated by each participating Node/Interface's configuration settings for that
VLAN Id.
Local VLAN Name = the VLAN name assigned by the configuration settings on the currently selected Node/Interface.
Tip: If you see an attribute named Global VLAN name = NNMi uses the lowest sort-order name from all available names designated by member Nodes assigned to that VLAN.
VLAN Id The identification value for the current VLAN. This value is taken directly from the MIB file provided by the Vendor.
HPE Network Node Manager i Software (10.20)
Page 79 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Port
Name
Click the Lookup icon and select Show Analysis or Open to display more information about the VLAN.
The port name consists of <Card-number / Port-number>.
Click the Lookup icon and select Show Analysis or Open to display more information about the VLAN.
Related Topics:
Node Form: Router Redundancy Group Tab (
NNMi
Advanced)
The
provides details about the selected node.
For information about each tab:
Router Redundancy Table
Attribute Description
Router
Redundancy
Table view of all of the Router Redundancy Groups associated with the current Node. Use this table to determine all Router Redundancy Groups to which the current Node belongs.
Double-click the row representing a Router Redundancy Group. The
Group Form (NNMi Advanced)" on page 279
displays all details about the selected Router
Redundancy Group.
Node Form: Capabilities Tab
The
provides details about the selected node.
For information about each tab:
The Node Form: Capabilities Tab displays a table view of any capabilities added to the node object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about a node than is initially stored in the NNMi database.
For example, NNMi Advanced uses the capability com.hp.nnm.capability.rrp.hsrp when a node is a member of an
HSRP
1
group.
1
Hot Standby Router Protocol
HPE Network Node Manager i Software (10.20)
Page 80 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Capabilities Table
Attribute Description
Capability Table of all of the capabilities associated with the selected Node. Use this table to access information about each Capability.
Double-click the row representing a Node Capability to open the
"Node Capability Form" on page 83
and view more information.
For more information, see
"Node Capabilities Provided by NNMi" below .
Node Capabilities Provided by NNMi
The
"Node Form: Capabilities Tab" on the previous page
displays a table of any Capabilities added to a particular node object. Capabilities enable NNMi and application programmers to provide more information about a node than what is initially stored in the NNMi database. For more information, click any of the following: l
Basic Node Capability Attribute Values
l
Node Capability Attribute Values that are assigned to Nodes (*)
These Node Capabilities assist in determining Node Sensor metrics. See
"Node Form: Node Sensors Tab" on page 84
for more information about health metrics.
l
Card Capability Attribute Values that are assigned to Nodes
(*) l l
(NNMi Advanced) Router Redundancy Protocol Capability Attribute Values
( NNMi Advanced) VMware ESX Host and Virtual Machine Capability Attribute Values
External applications can also add Capabilities.
The CISCO-STACK-MIB is associated with multiple Capabilities because NNMi uses the CISCO-STACK-
MIB for both card and metrics data.
KEY: com.hp.<product>.capability.<content>.<vendor/org>.<MIB/feature>
Any Capability provided by NNMi begins with the prefix com.hp.nnm.capability.
<product> = Either NNMi or the NNM iSPI providing this capability.
<content> = chassis, card, ipaddr (address), iface (interface), lag (
Link Aggregation
1
Aggregation
2 or
Split Link
interface), node, rrp (Router Redundancy), or metric (Node Sensor or Physical Sensor).
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 81 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
<vendor/org> = Standards organization or vendor defining the MIB or feature associated with the capability.
<MIB/feature> = What this capability measures.
Note: The following tables show a few examples of the Capabilities provided by NNMi.
Basic Node Capability Attribute Values
Unique Key Capability Description
com.hp.nnm.capability.node.ipforwarding IP
Forwarding
(Layer 3)
Value that indicates NNMi identified the selected node as a router that forwards
Layer 3 data. NNMi evaluates SNMP MIB-
II sysServices and other clues to determine this value and set the symbols in map views. The NNMi administrator can override this value using the Device Profile form, Force Device attribute (see
com.hp.nnm.capability.node.lanswitching LAN
Switching
(Layer 2)
Value that indicates NNMi identified the selected node as a switch for Layer 2 data.
NNMi evaluates SNMP MIB-II sysServices and other clues to determine this value and set the symbols in map views. The NNMi administrator can override this value using the Device Profile form, Force Device attribute (see
Node Sensor Capability Attribute Values that are assigned to Nodes
Unique Key Capability Description
com.hp.nnm.capability.rams.node.ramsmplswancen
ode
MPLS WAN CE No de
(NNMi Advanced, plus
HPE Route Analytics
Management System
(RAMS) for MPLS
WAN) The node supports HPE Router
Analytics Management
System (RAMS) and
MPLS WAN.
If you are an NNMi administrator, see
HPE RAMS
MPLS WAN Configurati on (NNMi Advanced) for information about configuring RAMS.
HPE Network Node Manager i Software (10.20)
Page 82 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Card Capability Attribute Values that are assigned to Nodes
Unique Key Capability Description
com.hp.nnm.capability.card.ietf.entity
IETF
Entity com.hp.nnm.capability.card.ietf.entitystate IETF
Entity
State
NNMi discovers but cannot monitor using the Internet Engineering Task
Force (IETF) ENTITY-MIB.
The node supports card monitoring using the Internet Engineering Task
Force (IETF) ENTITY-STATE-MIB.
(NNMi Advanced) Router Redundancy Protocol Capability Attribute Values
Unique Key Capability Description
com.hp.nnm.capability.rrp.vrrp VRRP (NNMi Advanced) The node is a member of a Virtual
Router Redundancy Protocol (VRRP)group.
(NNMi Advanced) VMware ESX Host and Virtual Machine Capability Attribute Values
Unique Key Capability Description
com.hp.nnm.capability.node.VM
Virtual
Machine com.hp.nnm.capability.node.hypervisor.vmware.ESX VMware
ESX Host
(NNMi Advanced) The node is a
virtual machine
1 being hosted on a
hypervisor
2
. Nodes with this capability become a member of the Node Group named Virtual Machines.
(NNMi Advanced) A VMware
ESXi server that is hosting virtual machines. Nodes with this capability become a member of the Node Group named VMware ESX Hosts.
Node Capability Form
This form describes a capability added to the node object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about a node than what is initially stored in the NNMi database.
For example, NNMi Advanced uses the capability com.hp.nnm.capability.rrp.hsrp to identify when a node is a member of an
HSRP
3 group.
1
A device that utilizes components from multiple physical devices. Depending on the manufacture's implementation, the virtual machine may be static or dynamic.
2
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
3
Hot Standby Router Protocol
HPE Network Node Manager i Software (10.20)
Page 83 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Node Capability Attributes
Attribute Description
Capability Label used to identify the Capability that was added to the node object.
"Node Form: Capabilities Tab" on page 80
shows a list of all available Capabilities for that node.
For more information, see
"Node Capabilities Provided by NNMi" on page 81
.
Unique
Key
Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.
For more information, see
"Node Capabilities Provided by NNMi" on page 81
.
Node Form: Node Groups Tab
The
provides details about the selected node.
For information about each tab:
Node Groups Table
Attribute Description
Node
Groups
Table view of all Node Groups to which this node belongs.
Double-click the row representing a Node Group. The
displays all details about the selected Node Group.
Caution: If you click Delete from this table view, the Node Group is deleted.
Node Form: Node Sensors Tab
The
provides details about the selected node.
For information about each tab:
The Node Form: Node Sensors tab displays information about node fault and performance metrics: l
Management Address ICMP Response Time
Threshold based on elapsed time (in milliseconds) for receiving a node's reply to an Internet Control
Message Protocol (ICMP) echo request. The address queried is the node's Management Address attribute value. See the node's
Node form, Basic Attributes section
for the currently configured address.
l
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics
HPE Network Node Manager i Software (10.20)
Page 84 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Software is installed and configured within your environment, the NNMi administrator can configure threshold for the following performance metrics ( click here for more information ): l
Buffer Failure Rate
Threshold based on the percentage of a node's buffer failures compared to the total number of attempts to create new buffers. These failures are caused by insufficient memory when the device tried to create new buffers.
l
Buffer Miss Rate
Threshold based on the percentage of a Node's buffer misses compared to the total attempts at buffer access. Crossing this threshold indicates the number of available buffers are dropping below a minimum level required for successful operation.
l
Buffer Utilization
Threshold based on the percentage of a Node's buffers that are currently in use, compared to the total number of available buffers.
l
CPU 5Sec Utilization
Threshold based on the percentage of a node's CPU usage compared to the total amount of available
CPU capacity. This percentage is the average CPU utilization over the prior 5-seconds.
l
CPU 1Min Utilization
Threshold based on the percentage of a node's CPU usage compared to the total amount of available
CPU capacity. This percentage is the average CPU utilization over the prior 1-minute.
l
CPU 5Min Utilization
Threshold based on the percentage of a node's CPU usage compared to the total amount of available
CPU capacity. This percentage is the average CPU utilization over the prior 5-minutes.
l
Disk Space Utilization
Threshold based on the percentage of a node's disk space usage compared to the total amount of available disk space.
l
Memory Utilization
Threshold based on the percentage of a node's memory usage compared to the total amount of available memory.
Tip: See
"Node Sensor Form" on page 232
for more details about the node sensor attributes that appear in this view's column headings. Node Sensors are displayed in three views:
"Node Sensors View" on page 47
,
"Non-Normal Node Sensors View" on page 393 , and
"Unmanaged Node Sensors View" on page
.
Node Sensors Table
Attribute Description
Node Table view of the fault and performance metrics associated with the current node. You can use
HPE Network Node Manager i Software (10.20)
Page 85 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Node Sensors Table, continued
Attribute Description
Sensors this table to determine the Status, Name, and Type for each Node Sensor metric associated with the selected node.
Double-click the row representing a Node Sensor. The
displays all details about the selected Node Sensor.
Note: The NNMi administrator can set Node Sensor thresholds. For more information, see
"Node Form: Node Sensors Tab" on page 84
,
"Chassis Form: Node Sensors Tab" on page
, and
"Card Form: Node Sensors Tab" on page 223
.
Node Form: Hosted Nodes Tab
(NNMi Advanced) The Node Form: Hosted Nodes tab appears if the Node is hosting other Nodes. For example, a virtual device.
For information about each tab:
The Nodes listed on this tab will have a
attribute showing the Hostname of the hosting
Node.
Tip: These nodes share the group of Chassis and Cards managed by the hosting node.
Hosted Nodes Table
Attribute Description
Status See the Status information in
.
Device Category
Name
Hostname
Management
Address
System Location
Device Profile
SNMP Agent
Enabled
Status Last
Modified
Notes
The NNMi administrator specifies this attribute value. See Configure Device
Category Icons .
See the Name information in
See the Hostname information in
.
See the Management Address information in
.
See the System Location information in
"Node Form: General Tab" on page 73
.
See the Device Profile information in
See the SNMP Agent Enabled information in
.
See the Status Last Modified information in
"Node Form: Status Tab" on page 93
.
See the Notes information in
HPE Network Node Manager i Software (10.20)
Page 86 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Node Form: Custom Attributes Tab
Custom Attributes enable an NNMi administrator to add information to the Node object. Custom Attributes can also be set by external applications that have been integrated with NNMi. See
.
The Node Form: Custom Attributes tab displays a table view of any Custom Attributes that have been added to the selected node.
Note: If your role permits, you can edit a Custom Attribute. Only users assigned to the NNMi
Administrator role can add a Custom Attribute.
For information about each tab:
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Custom Attributes Table
Attribute Description
Name
Value
Name used to identify the Custom Attribute. This name appears in the table view on the
Custom Attributes tab in Node forms. Limit 50 of any combination of keyboard entries including spaces.
Value assigned to the Custom Attribute for the selected node. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Custom Node Attributes Form" below
.
The Custom Attributes tab for a virtual machine or a hypervisor node shows three following default attributes:
PartitionHost, PartitionID, and PartitionName.
Default Custom Attributes
Attribute Description
PartitionHost l
For a virtual machine: UUID of the hypervisor that hosts the virtual machine l
For a hypervisor: UUID of the hypervisor
PartitionID UUID of the node
PartitionName Hostname of the node
Custom Node Attributes Form
Custom Attributes enable an NNMi administrator to add information to a node object. Custom Attributes can also be set by external applications that have been integrated with NNMi. See
HPE Network Node Manager i Software (10.20)
Page 87 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
.
The required settings for these attributes are described in the table below.
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Basics Attributes
Attribute Description
Name
Value
Name used to identify the Custom Attribute. This name appears in the table view on the
Custom Attributes tab in Node forms. Limit 50 of any combination of keyboard entries including spaces.
Value assigned to the Custom Attribute for the selected node. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Node Form: Custom Attributes Tab" on the previous page .
Custom Node Attribute Samples
Custom Attributes provide additional information about an object instance: l
To make inventory tasks easier:
For example, your NNMi administrator might have added the following: l
Name: Serial Number l
Value: UHF536697J3 l
To customize a device icon on the NNMi maps.
For example, your NNMi administrator can use Custom Attributes to customize the Device Profile icon for one or more nodes ( Customize Device Profile Icons ): l
Name:
NNM_ICON l
Value =
<filename of the icon for the selected nodes>
To view the list of available device profile icons, see View the Device Profile Icons Available .
l
External applications that have been integrated with NNMi can associate custom information with the
Interface.
For example, when HPE Network Node Manager iSPI Performance for Metrics Software is installed, your NNMi administrator can provide additional Node or Interface information in NNM iSPI
Performance for Metrics reports:
HPE Network Node Manager i Software (10.20)
Page 88 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
Name = NPS Annotation l
Value = <text to appear in the reports>.
See the help topic: Annotate NNM iSPI Performance for Metrics Reports Reports .
l
To make configuring a Scheduled Outage easier by making the Node's Time Zone visible in the Scheduled
Node Outage dialog:
For example, your NNMi administrator might have added the following: l
Name: com.hp.nnm.topo.TZ
l
Value: <any Java Time Zone designator>
The list of valid Java Time Zones changes over time. Open the Scheduled Node Outage dialog and click the Time Zone drop-down to display the list of valid choices at this time. See
Outages for Nodes or Node Groups" on page 322
.
To check NNMi's current Java Time Zone version number, on the server where NNMi is installed, use the following command line tool (see About Environment Variables for more information)
Windows:
%NnmInstallDir%\jdk\hpsw\bin\java –version
Linux:
$NnmInstallDir/jdk/hpsw/bin/java –version
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Related Topics:
"Node Form: Custom Attributes Tab" on page 87 .
"Custom Node Attributes Form" on page 87
Node Form: Custom Polled Instances Tab
Tip: The
"Custom Polled Instance Form" on page 312
provides details about the selected Polled
Instance.
For information about each tab:
(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.
HPE Network Node Manager i Software (10.20)
Page 89 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes
Attribute Description
Node
State
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).
The State of the Custom Polled Instance as determined by any Thresholds ( High 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
Note: The most severe Threshold
or
value or Comparison Map
State Mapping value returned from the Polled Instances for a
becomes the Custom Node Collection Status.
MIB Variable Represents the MIB Expression that NNMi polls according to configuration settings.
Additional information associated with the MIB Variable includes the MIB Expression Name and any Threshold settings configured for the Custom Poller Collection.
MIB
Instance
Click the Lookup icon and select Show Analysis or Open to display more information about the MIB Variable.
See
"MIB Variable Form" on page 329
for more information about the MIB Variable attribute.
This attribute contains the multiple filtered instances for the MIB Expression. Each instance value identifies a row in the MIB table.
Note: 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.
Last State The value from the MIB Expression that caused the State to change.
HPE Network Node Manager i Software (10.20)
Page 90 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Change
Value
Note: 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.
Node Form: Diagnostics Tab
The
provides details about the selected node.
When you access the Node Form: Diagnostics Tab, you can view the history of all the NNM iSPI NET
Diagnostic reports that have been run for this Node. Diagnostics are sets of automated commands specific to one or more device types, including Cisco routers and switches, Cisco switch/routers, and Nortel switches.
To generate a new instance of these Diagnostics reports, click Actions → Run Diagnostics.
Tip: You can also right-click any object in a table or map view to access the items available within the
Actions menu.
For information about each tab:
(NNMi Advanced - Global Network Management feature) Any NNM iSPI Diagnostics Flows 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 NNM iSPI Diagnostics Flows on the Regional
Manager.
Diagnostics Table
Attribute Description
Node
Diagnostic
Results
Requires HPE Network Node Manager iSPI Network Engineering Toolset Software
(NNM iSPI NET) and requires installation of a Diagnostic Server -click here for more information .
Table view of the Node Diagnostic Results associated with the selected node. You can use this table to determine the start time, definition, status, report name, and last update time for each Node Diagnostic Result associated with the selected node.
Double-click the row representing a Node Diagnostic Result . The
displays all details about the selected Node Diagnostic
Result.
Node Diagnostic Results Form (Flow Run Result)
Requires HPE Network Node Manager iSPI Network Engineering Toolset Software (NNM iSPI NET) and
HPE Network Node Manager i Software (10.20)
Page 91 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details requires installation of a Diagnostic Server -click here for more information .
NNM iSPI NET automatically prepares diagnostic reports about the source node when certain incidents are generated and when using Actions → Run Diagnostics. This form shows details about the currently selected diagnostic report instance.
Tip: You can also right-click any object in a table or map view to access the items available within the
Actions menu.
Note: Because the values on this form are generated by NNM iSPI NET, these attribute values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any NNM iSPI Diagnostics Flows 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 NNM iSPI Diagnostics Flows on the Regional
Manager.
See
"Node Form: Diagnostics Tab" on the previous page
for more information.
Diagnostics Table
Attribute Description
Start Time Date and time NNM iSPI NET created this instance of the Diagnostics report. NNM iSPI NET uses the locale of the client and the date and time from the NNMi management server.
Definition The name of the NNM iSPI NET Diagnostics report definition.
Status The current status of this NNM iSPI NET Diagnostics report. Possible values include: l
The Diagnostic is in the queue, but is not yet running l l
The Diagnostic has been submitted and is not finished running
The Diagnostic has finished running l
An error condition prevented the Diagnostic from being submitted l
NNMi was unable to submit or run the Diagnostic due to a timeout error. The timeout limit for submitting a Diagnostic is one hour. The timeout limit for running a Diagnostic is four hours.
Tip: Example error conditions include the following: l
The number of Diagnostics in the queue might prevent NNMI from submitting the
Diagnostic.
l
A configuration error, such as an incorrect user name or password, might prevent
NNMi from accessing the required Operations Orchestration server.
Contact your NNMi administrator for Diagnostic log file information.
Report Click this link to open the actual report. NNM iSPI NET uses this text string to display the selected instance of the diagnostics report in a browser window.
HPE Network Node Manager i Software (10.20)
Page 92 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Diagnostics Table, continued
Attribute Description
Lifecycle
State
Last
Update
Time
Incident
of the target Incident.
If the incident's Lifecycle State matches the value specified here, the Diagnostic runs.
The Diagnostic automatically runs on each applicable Source Node in the specified Node
Group if the incident has the Lifecycle State currently configured in this attribute of the
Diagnostic (Flow Definition - set of automated commands).
Date and time NNM iSPI NET last updated this instance of the Diagnostics report. NNM iSPI
NET uses the locale of the client and the date and time from the NNMi management server.
Node Form: Incidents Tab
Tip: See
for more details about the incident attributes that appear in the incident table view's column headings.
The
provides details about the selected node.
For information about each tab:
Incidents Table
Description
Table view of the incidents associated with the selected node. 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 node.
Double-click the row representing an incident. The
displays all details about the selected incident.
Node Form: Status Tab
The
provides details about the selected node.
For information about each tab:
Overall Status
Attribute
Description
Status Overall status for the current node. NNMi follows the ISO standard for status classification.
Possible values are:
No Status
HPE Network Node Manager i Software (10.20)
Page 93 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute
Description
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
The status of all IP addresses and the SNMP Agent associated with this node, and well as interface health contribute to node status. For information about how the current status was determined, see the
"Node Form: Conclusions Tab" on the next page
. Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Your NNMi administrator might configure Custom Poller so that the Status of a Custom Node
Collection effects the topology node's Status.
Click here to view the effect of a Custom Node
Collection's Status on the topology node's Status. See About Custom Poller for more information.
The effect of a Custom Node Collection's Status on the topology node's Status is determined as follows: l
If at least one Custom Collection Node's Status is Critical, the topology node Conclusion
Status is Critical.
l
If at least one Custom Collection Node's Status is Major, but none are Critical, the topology node Conclusion Status is Major.
l
If at least one Custom Collection Node's Status is Minor, but none are Critical or Major, the topology node Conclusion Status is Minor.
l
At least one Custom Collection Node's Status is Warning, but none are Critical, Major, or
Minor, the topology node Conclusion Status is Warning.
l
If the Status of all Custom Collection Nodes are Normal, the topology node Conclusion
Status is Normal.
Note: The icons are displayed only in table views.
Status
Last
Modified
Date and time indicating when the status was last set.
HPE Network Node Manager i Software (10.20)
Page 94 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status History Table
Attribute
Description
Status
History
List of up to the last 30 changes in status for the selected node. This view is useful for obtaining a summary of the node status so that you can better determine any patterns in node behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
Node Form: Conclusions Tab
The
provides details about the selected node.
All relevant Conclusions are shown in the table on this tab. The most severe Status in the current group of conclusions becomes the overall Node status. Some Node conclusions for routers can propagate to relevant
Router Redundancy Groups:
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses of the node that contributed to the current overall Status of the selected node. Status is set by the Causal Engine.
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 for the current node that led up to the node's most current Status.
The Status value is correlated based on the most critical 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 node object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
CustomPollingOnNodeCritical At least one Custom Polled
Instance associated with the physical node has a Status of
Critical.
NodeDown The NNMi Causal Engine has
Status Incident?
Critical N
Critical Y
HPE Network Node Manager i Software (10.20)
Page 95 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
NodeOrConnectionDown
Description
determined the node is down based on the following analysis: l
100% of the addresses assigned to this node are unreachable l
NNMi is communicating with at least two of the neighboring devices.
A node is not responding to an
ICMP or SNMP query. It also indicates that NNMi is communicating with only one neighbor. Therefore, NNMi cannot determine whether the node or the connection is down.
Status Incident?
Critical Y
Major Status Conclusions
Conclusion
BadPowerSupplyOnHostedNode
BadTemperatureOnHostedNode
BadFanOnHostedNode
Description
At least one of the monitored attributes for a fan on the hosting node
(Managed By) or a
is outside of the threshold range set on the
Status Incident?
At least one of the power supply’s monitored attributes on the hosting node (Managed By) or a
is outside of the threshold range set on the device.
Major N
At least one of the monitored attributes for a temperature sensor on the hosting node (Managed By) or a
is outside of the threshold range set on the device.
Major N
Major N
HPE Network Node Manager i Software (10.20)
Page 96 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
BadVoltageOnHostedNode
BadBackplaneOnHostedNode
CardBadBackplaneOnHostedNode
CardBadFanOnHostedNode
Description
device.
Status Incident?
At least one of the monitored attributes for a voltage sensor on the hosting node (Managed By) or a
is outside of the threshold range set on the device.
Major N
At least one of the monitored attributes for the backplane on the hosting node (Managed By) or a
is outside of the threshold range set on the device.
Major N
At least one of the monitored attributes for a backplane on the card is outside of the threshold range set on the device.
Major N
At least one of the monitored attributes for a fan on the card is outside of the threshold range set on the device.
Major N
CardBadPowerSupplyOnHostedNode At least one of the power supply’s monitored attributes on the hosting node is outside of the threshold range set on the device.
Major N
CardBadTemperatureOnHostedNode At least one of the monitored attributes for a temperatuere sensor on the card is outside of the threshold range set on the device.
Major N
CardBadVoltageOnHostedNode At least one of the Major N
HPE Network Node Manager i Software (10.20)
Page 97 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
ChassisMajorInNode
CustomPollingOnNodeMajor
NodeWithBadMemory
Description
monitored attributes for a voltage sensor on the card is outside of the threshold range set on the device.
At least one chassis is major in the node.
Status
Major
Incident?
N
At least one Custom Polled
Instance associated with the physical node has a
Status of Major.
Major N
At least one memory pool on the node is outside the threshold range configured for the device. This incident indicates the memory pool is exhausted or cannot meet the demand for use.
Major N
Minor Status Conclusions
Conclusion
AllUnresponsiveAddressesInNode
CardDownOnHostedNode
Description Status Incident?
Minor N None of the addresses associated with the selected node respond to
ICMP ping.
The
Operational
State of a
Card on a
is
Down.
Minor N
HPE Network Node Manager i Software (10.20)
Page 98 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
ChassisDownOnHostedNode
CustomPollingOnNodeMinor
ChassisDownInNode
Description Status Incident?
Note:
CardDo wn only propaga tes to a
Hosted
Node when a port hosted on that card is used by an interfac e associa ted with the node.
The
Operational
State of a
Chassis on a
is
Down.
Minor N
At least one
Custom
Polled
Instance associated with the physical node has a
Status of
Minor.
Minor N
The
Operational
Minor N
HPE Network Node Manager i Software (10.20)
Page 99 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfacesDownInNode
OneOrMoreCardsDownOnHostedNode
SNMPAgentPingUnresponsiveInNode
Note:
CardDo wn only propaga tes to a
Hosted
Node when a port hosted on that card is used by an interfac e associa ted with the node.
Description Status Incident?
State of a
Chassis is
Down.
At least one interface contained in the node has an
Operational
State of
Down.
Minor N
At least one card in a
has an
Operational
State of
Down.
Minor N
The Minor N
HPE Network Node Manager i Software (10.20)
Page 100 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
SomeInterfacesOutsideThresholdBoundariesInNod e
SomeUnresponsiveAddressesInNode
UnresponsiveAgentInNode
UnresponsiveWebAgentInNode
The
SNMP
Agent
1 associated with this node is not responding to SNMP requests.
The
Web
Agent
2 associated with this node is not responding
Description Status Incident?
management address on the node is not responding to ICMP.
At least one interface on the node has a threshold outside the range specified for the device.
Minor N
At least one, but not all addresses, in the node are not responding to ICMP.
Minor N
Minor N
Minor N
1
Simple Network Management Protocol (SNMP) is an Internet-standard protocol used to manage devices on
IP networks. The SNMP Agent uses this protocol to report information to authorized management programs.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 101 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
StackMinorInNode
Description Status Incident?
to requests.
A Chassis
Redundancy
Group contained in the Node has a Status of Minor.
Minor N
Warning Status Conclusions
Conclusion
CrgMalfunctionInNode
Description Status Incident?
A Card Redundancy Group in the node has a Status other than
Normal.
Warning N
Warning N CustomPollingOnNodeWarning At least one Custom Polled
Instance associated with the physical node has a Status of
Warning.
ChassisWarningInNode One card in a chassis has a status of CardDown, but not all cards are down.
Warning N
ChassisDegradedInNode
StackDegradedInNode
More than one card in a chassis has a status of CardDown.
Perhaps all cards have a status of CardDown.
Warning N
NNMi has detected that a
Chassis Redundancy Group contained in the Node is degraded. See
for more information.
Warning N
Disabled Status Conclusions (NNMi Advanced)
Conclusion Description
NodePoweredDown The Power State of the virtual machine is set to Powered Off.
Status Incident?
Disabled Y
HPE Network Node Manager i Software (10.20)
Page 102 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
NodePaused
Description
For example: The virtual machine is turned off.
The Power State of the virtual machine is set to Suspended.
For example: The virtual machine is paused.
Status Incident?
Disabled Y
Unknown Status Conclusions
Conclusion Description
NodeUnmanageable The node cannot be reached because
NNMi has determined that the node on which it depends to route its traffic is down. This condition is known as “in the shadow”.
Note: The status of any node “in the shadow” of a node that is down is always Unknown and the conclusion on each of the nodes in the shadow is
NodeUnmanageable.
Status Incident?
Unknown N
Normal Status Conclusions
Conclusion Description
AllInterfacesWithinThresholdBoundariesInNode All of the interfaces within the selected node are within the allowable threshold range configured by the administrator.
AllResponsiveAddressesInNode All of the addresses associated with the selected
Status
Normal
Incident?
N
Normal N
HPE Network Node Manager i Software (10.20)
Page 103 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
CrgNormalInNode
CustomPollingOnNodeNormal
InterfacesUpInNode
NodeUp
ResponsiveAgentInNode
ResponsiveWebAgentInNode
Description
node respond to
ICMP ping.
Status Incident?
All Card
Redundancy
Groups in the node are functioning properly.
Normal N
All Custom
Polled Instances associated with the physical node have a
Status of
Normal.
Normal N
All interfaces in the node have an
Operational
State of Up.
Normal N
Normal N The node and its sensors are functioning properly.
The node’s
SNMP Agent
1 is responding.
Normal N
The node’s
Web
Agent
2 is responding.
Normal N
Multiple Node conclusions can appear for the same node object. For example, if a node is functioning properly and it has monitored addresses, interfaces, at least one card, and a card redundancy group, you would see these conclusions together: l
SNMPAgentResponding
1
Simple Network Management Protocol (SNMP) is an Internet-standard protocol used to manage devices on
IP networks. The SNMP Agent uses this protocol to report information to authorized management programs.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 104 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
l
AllResponsiveAddressesInNode l l
InterfacesUpInNode
CardsUpInNode l
CrgNormalInNode
Node Form: Scheduled Outage Tab
The
provides details about the selected node.
This tab provides a record of all the Node's past, present, and future Scheduled Node Outages. See the
"Node Form: Outage History Tab" below
for more details.
See also
"Scheduling Outages for Nodes or Node Groups" on page 322
and
"Scheduled Node Outages View" on page 586 .
See
"Understand the Effects of Setting the Management Mode to Not Managed or Out of Service" on page
For information about each tab:
Scheduled Outage Table
Attribute Description
Name
Outage Start Time
Outage End Time
Duration
The name assigned to this scheduled outage instance.
The date and time that this Scheduled Outage is configured to start.
The date and time that this Scheduled Outage is configured to end.
The length of time that the Scheduled Outage is configured to last.
Node Form: Outage History Tab
The
provides details about the selected node.
This tab provides a record of all this Node's past, present, and future outages (including
).
For information about each tab:
Outage History Table
Attribute Description
Timestamp
Management Mode
Scheduled Outage
The date and time at which the
changed for this Node.
The name of the Management Mode change associated with this history instance.
One of the following:
HPE Network Node Manager i Software (10.20)
Page 105 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outage History Table, continued
Attribute Description
Name
Modified By l
The name assigned to the Scheduled Outage whose start or stop history is being recorded here.
l
For all other Management Mode changes, this value is empty (blank).
The NNMi User Name of the person who initiated the Node State change.
Note: If caused by a
Scheduled Node Outage , the value is
system.
Node Form: Registration Tab
The
provides details about the selected node.
For information about each tab:
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.
Note: 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: l
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.
l
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.
HPE Network Node Manager i Software (10.20)
Page 106 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Device Profile Form
According to industry standards (MIB-II), each combination of vendor, device type, and model number is assigned a unique SNMP system object ID ( sysObjectID). For example, all Cisco 6500 series switches have the same sysObjectID prefix: .1.3.6.1.4.1.9.* See the
.
NNMi uses the
to make decisions about how devices are discovered and depicted on the
NNMi maps.
Tip: Each
has a link to the appropriate Device Profile form.
Basic Attributes
Attribute Description
Device
Model
SNMP
Object ID
Device model name or number designator, determined by the vendor.
MIB-II sysObjectID number issued for this device type. These numbers are unique across all vendors.
Description The description, based on information from the MIB-II sysDescr string provided by the vendor.
Maximum length is 255 characters: alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -)
Device
Family
Device family name provided by the vendor; for example Cisco Catalyst 6500 Series
Switches or HP AdvanceStack Routers.
Device
Vendor
Device
Category
OUI
Author
Click the details.
Lookup icon to access the
"Device Family Form" on page 111
Name of the vendor that manufactures the device.
for more
Click the details.
Lookup icon to access the
"Device Vendor Form" on page 111
for more
The value of this attribute determines which background shape NNMi uses for the map icon representing devices of this type. See About Map Symbols for more information about the possible values.
Click the details.
Lookup icon to access the
"Device Category Form" on page 112
for more
Organizationally unique identifier. The first three octets of the MAC address for the device that identify the device's vendor.
Indicates who created or last modified the device profile.
HPE Network Node Manager i Software (10.20)
Page 107 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes , continued
Attribute Description
Caution: If the Author attribute value is HP Network Node Manager, any changes are at risk of being overwritten in the future.
l
Click Lookup and select Show Analysis to display details about the currently selected Author.
l l
Click Quick Find to access the list of existing Author values.
Click New to create an Author value.
Advanced Settings Tab
Attribute Description
Use of SNMP SysName for Node Name Resolution
Never Use sysName
If enabled, Spiral Discovery does not use a MIB-II for discovered Nodes of this type. If sysName is part of the current node Name strategy, NNMi uses the next designated node Name choice in the strategy established by your NNMi administrator.
sysName value for the Name attribute
If disabled, MIB-II sysName can potentially be used as the Name attribute value for nodes of this type.
Do not Use sysName
Starting
With
The vendor's default sysName text string, from MIB-II sysName.
If the SNMP agent responds to a sysName request with a value that matches or starts with the entry in this field (case-sensitive), Spiral Discovery ignores the sysName and considers sysName to be unset. As a result, NNMi instead tries to find a DNS name or IP address for this node (according to the strategy established by your NNMi administrator).
For example, when an SNMP agent responds with a default sysName, NNMi's maps might display multiple icons with the same name (one for every device of that type in your environment that responded to an SNMP query with the default sysName). Usually, the device administrator changes the default sysName value to something more meaningful, so this problem is avoided.
Device Behaviors
Force
Device
This attribute enables the NNMi administrator to override the IP Forwarding (Layer 3) and
LAN Switching (Layer 2) Capability settings provided by Spiral Discovery (displayed on the
"Node Form: Capabilities Tab" on page 80 ).
Note the following: l
The Force Device attribute does not affect default membership for the Node Groups provided by NNMi. For example, the Force to router settings does not add the Node to the Routers Node Group. NNMi uses the Device Category to determine Node Group membership for the Node Groups it provides.
HPE Network Node Manager i Software (10.20)
Page 108 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Advanced Settings Tab , continued
Attribute Description
l
The Force Device setting does not affect the background shapes displayed on an NNMi map. NNMi uses the Device Category specified in the Device Profile to determine the map background shapes displayed.
The following table describes the possible Force Device settings and subsequent behavior:
Force Device Settings and Behavior
Setting Behavior
Do not force
Ignores the Force Device setting.
Force to router l
Adds the IP Forwarding (Layer 3) Capability to the Node l l
Displays the device in Layer 3 Neighbor View maps
Checks the Router Redundancy Protocol configuration for information about the Node
Adds the LAN Switching (Layer 2) Capability to the Node Force to switch
Force to end node l
Removes either of the following Capabilities if they are configured on the
Node: l
IP Forwarding (Layer 3) l
LAN Switching (Layer 2)
Force to switch and router l
Ignores this Node during Auto-Discovery unless you select "Discover Any
SNMP Device" or include the Node’s System Object ID in the Auto-
Discovery Rule.
l l
Adds the IP Forwarding (Layer 3) Capability to the Node
Adds the LAN Switching (Layer 2) Capability to the Node l
Displays the Node in Layer 3 Neighbor View maps l
Checks the Router Redundancy Protocol configuration for information about the Node
An NNMi administrator might want to use this attribute to override the IP Forwarding (Layer 3) and LAN Switching (Layer 2) capabilities setting for the device under the following circumstances: l l l
The sysServices setting in MIB-II that is used to determine the IP Forwarding (Layer 3) and LAN Switching (Layer 2) capability during discovery is not accurate due to a firmware defect on the device.
The device serves as a router, switch, or switch and router and the NNMi administrator wants to force the device to be treated as only one of the following: 1) a router, 2) a switch, or 3) a switch and router.
The device serves as a virtual router, but should not be managed as a router.
HPE Network Node Manager i Software (10.20)
Page 109 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Advanced Settings Tab , continued
Attribute Description
Setting the Force Device attribute to Force to end node enables the NNMi administrator to configure Spiral Discovery to ignore this device (unless the device is within the Default
Tenant and an Auto-Discovery Rule is configured to "Discover Any SNMP Device" or configured to include the matching System Object ID).
Interface
Reindexing
Type
Your NNMi administrator chooses which interface MIB variable the NNMi State Poller queries to detect interface changes. NNMi can use the following MIB-II attribute values: ifIndex, ifName, ifDescr, ifAlias, or a combination of these (ifName or ifDescr, ifName or ifDescr or ifAlias). See the General Interface Attributes (SNMP Values) in
Form: General Tab" on page 118
for information about these four MIB-II attributes that are available to use for this setting.
If you are an Administrator, see Detect Interface Changes for more information.
Prefer
LLDP
A network device's interfaces can be configured with proprietary Layer 2 discovery protocols, instead of or in addition to the industry standard LLDP (see the list of Topology Source protocols in
).
By default, NNMi checks the interface for standard LLDP and vendor-specific IEEE 802
Layer 2 protocol. NNMi uses data from both protocols to calculate the Layer 2 Connection, but by default prefers the data provided through LLDP.
Note: Forwarding Database (FDB) information can cause NNMi to establish wrong
Layer 2 Connections in the following cases: l
When the FDB is configured as cache and contains obsolete data.
l
In network environments with hardware from a variety of vendors, when each vendor generates different and sometimes conflicting FDB data.
Optional: NNMi administrators can configure Spiral Discovery to ignore the FDB data from one Node Group when calculating Layer 2 Connections (the FDB data is still included in other calculations).
(NNMi Advanced - Global Network Management feature) NNMi must read the
Forwarding Database (FDB) tables from Ethernet switches within the network before accurate communication paths between these network devices can be calculated.
Because the FDB data is involved, NNMi can produce different results on a Regional
Manager as opposed to the Global Manager.
If NNMi discovers more than one IEEE 802 Layer 2 protocol being used by a particular device's interface, the Device Profile's setting controls NNMi's protocol preference:
Prefer LLDP = Enabled: NNMi gives priority to the LLDP data.
Prefer LLDP = Disabled: NNMi gives priority to the vendor-specific IEEE 802 Layer 2 protocol data.
Tip: If NNMi detects incorrect neighbors, make sure that the interfaces at both ends of the Layer 2 Connection are using the same configuration for Layer 2 discovery protocol.
For more information, see Troubleshooting Layer 2 Connections .
HPE Network Node Manager i Software (10.20)
Page 110 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Device Family Form
The Device Family attribute value indicates the family name assigned by the vendor when the device was manufactured; for example, the Cisco Catalyst 6500 Series Switches.
l l
NNMi monitoring behavior can be configured differently for each family.
Membership in a Node Group can be determined by device family.
This form is accessed from the
"Device Profile Form" on page 107
.
Device Family Definition
Attribute Description
Label Device family name. For example, Cisco Catalyst 6500 Series Switches or HP
AdvanceStack Routers.
Maximum length is 255 characters. Alpha-numeric, spaces, and underline characters are permitted.
Unique Key The required unique identifier that is important when exporting and importing device profile information within NNMi.
The value must be unique. One possible strategy is to use the Java name space convention. For example: com.<your_company_name>.nnm.device_profile.family.<family_label>
Maximum length is 80 characters. Alpha-numeric characters and periods are permitted.
Spaces are not permitted.
Management
URL
Optional. The URL to the device's management page (provided by the vendor). This page is used to provide configuration information for the device and is usually organized by device family.
Icon Displays the icon that is associated with the Device Family.
If you are an NNMi administrator, you can customize the icon. See Customize Device
Profile Icons for more information.
Device Vendor Form
The Device Vendor attribute value indicates the name of the manufacturer of this device type; for example,
HPE or Cisco. l
NNMi monitoring behavior can be configured differently for each vendor.
l
Membership in a Node Group can be determined by device vendor.
This form is accessed from the
"Device Profile Form" on page 107
.
Device Vendor Definition
Attribute Description
Label Vendor name.
HPE Network Node Manager i Software (10.20)
Page 111 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Device Vendor Definition , continued
Attribute Description
Unique
Key
Icon
Maximum length is 255 characters. Alpha-numeric, spaces, and underline characters are permitted.
The required unique identifier that is important when exporting and importing device profile information within NNMi.
The value must be unique. One possible strategy is to use the Java name space convention.
For example: com.<your_company_name>.nnm.device_profile.vendor.<vendor_label>
Maximum length is 80 characters. Alpha-numeric characters and periods are permitted. Spaces are not permitted.
Displays the icon that is associated with the Device Vendor.
If you are an NNMi administrator, you can customize the icon. See Customize Device Profile
Icons for more information.
Device Category Form
The Device Category attribute value indicates the category of this device; for example, router, switch, or printer. This attribute: l
In Map views, determines which background shape NNMi uses for the icon representing devices of this type.
l
In table views, the category value can be used when sorting/filtering the Category column.
l l
During discovery, NNMi behavior changes based on the device category. For example, routers and switches are discovered by default.
NNMi monitoring behavior can be configured differently for each category.
l
Membership in a Node Group can be determined by device category.
This form is accessed from the
"Device Profile Form" on page 107
.
Device Category Definition
Attribute Description
Label Category name.
Maximum length 255 is characters. Alpha-numeric, spaces, and underline characters are permitted.
Unique
Key
The required unique identifier that is important when exporting and importing device profile information within NNMi.
The value must be unique. One possible strategy is to use the Java name space convention.
For example: com.<your_company_name>.nnm.device_profile.category.<category_label>
Maximum length is 80 characters. Alpha-numeric characters and periods are permitted. Spaces
HPE Network Node Manager i Software (10.20)
Page 112 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Device Category Definition , continued
Attribute Description
Icon are not permitted.
Displays the icon that is associated with the Device Category.
If you are an NNMi administrator, you can customize the icon. See Customize Device Profile
Icons for more information.
Interface Form
Click the link to the object type you selected prior to opening the Interface form: l
— might be a physical or virtual interface
For example, the interface might be a virtual port or an uplink provided by a
hypervisor
1
.
l
Interface Form
The Interface form provides details about the physical or virtual network interface selected. From this form you can access more details about the parent
,
associated with this interface.
If your role permits, you can use this form to modify the
for an interface (for example to indicate it will be temporarily out of service) or add
to communicate information about this interface.
If you see several blank columns for an interface in a table view, note the following: l
The interface might be in a non-SNMP node.
For interfaces on non-SNMP nodes, note the following: l
The interface index ( ifIndex) value is always set to 0 (zero).
l
The interface type ( ifType) is set to Other.
l
The interface Name ( ifName), if none is available, is set to Pseudo Interface.
Note: For Pseudo Interface, NNMi attempts to obtain additional information using a variety of
discovery protocols (see the list of Topology Source protocols in
l
If the interface hosts an IP address, the interface Alias ( ifAlias) is set to the IP address. Otherwise,
1
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 113 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details the interface Alias ( ifAlias) is set with information from neighboring SNMP devices.
l
NNMi obtains the MAC address if the IP address can be resolved using ARP cache.
l
The interface might be a Nortel private interface.
For Nortel SNMP interfaces, note the following: l
The interface index ( ifIndex) value is set according the Nortel private MIB.
l
NNMi tries to collect the MAC address and interface name using Nortel's private MIBs.
l
(NNMi Advanced) The interface might be an IPv-6 interface.
A small number of IPv6 devices do not support the standard RFC 2863 IF-MIB for IPv6 interfaces. In this case, NNMi uses the RFC 2465 IPv6-MIB. When this happens, note the following: l
Interface index ( ifIndex) and description (ifDescr) are set according to the RFC 2465 IPv6 MIB.
l
Interface type ( ifType) is set to Other (no specific type is available).
l
Interface Name ( ifName), Alias (ifAlias), and Speed (ifSpeed) are blank (not available).
l
NNMi monitors the Status of this interface, but Performance metrics are not available.
When an IP Address has the Interface Name ( ifName) attribute set to blank, NNMi constructs an alternate string for the IP Address's In Interface attribute ( Other[<ifIndex_value>]).
For information about each tab:
Basic Attributes
Attribute Description
Name
Status
The most accurate interface name available to the initial discovery process. First choice is the IF MIB ifName value. Second choice is the ifAlias value. Third choice is a combination of the ifType[ifIndex] value (for example, ethernetCsmacd[17]).
Overall status for the current interface. NNMi follows the ISO standard for status classification. See the
"Interface Form: Status Tab" on page 140
for more information.
Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
HPE Network Node Manager i Software (10.20)
Page 114 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Interface status is derived from SNMP polling results for
and
, as well as from any conclusions. Status reflects the most serious outstanding conclusion.
See the
"Interface Form: Conclusions Tab" on page 141
for information about how the current status was determined. See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views.
Management
Mode
The calculated Management Mode for the interface according to the Management Mode
Hierarchy. This value reflects the current management mode of this interface's parent object (the Hosted On Node). See
"How NNMi Assigns the Management Mode to an
.
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: 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 interface. Possible values are:
Inherited – Used to indicate that the interface should inherit the Management Mode from this interface's parent object (the Hosted On Node).
Not Managed – Used to indicate that NNMi does not discover or monitor the interface.
For example, the interface might not be accessible because it is in a private network.
Out of Service – Used to indicate an interface is unavailable because it is out of service or participating in a
. NNMi does not discover or monitor this
Interface.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.
Note: 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
The node in which the interface resides. This is the current value in the NNMi database for the Name attribute of the host device. The value could be a DNS name, a MIB-II sysName,
HPE Network Node Manager i Software (10.20)
Page 115 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
or an address (depending on how your NNMi administrator configured the discovery process).
Physical
Address
Layer 2
Connection
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
The interface address at the physical layer, also known as the MAC address. This is the globally unique serial number assigned to each interface at the factory.
Used to indicate whether the selected interface is part of a Layer 2 Connection. If the interface is part of a connection, use this attribute to access information about its Layer 2
Connection and the neighboring device.
Click here for instructions.
1. Navigate to the Layer 2 Connection attribute. Click the select Open.
Lookup icon, and
2. In the Layer 2 Connection form, locate the Interfaces tab.
3. Double-click the row representing the other interface participating in this connection.
4. In the Interface form, locate the Hosted On Node attribute.
5. The Node form contains all known information about the neighboring node.
Interface State Attributes
Attribute Description
Administrative
State
The current Administrative State provided by: l
The managing
l
The managing
(NNMi Advanced) l
Set by the device's administrator
This value contributes towards the status calculation for this interface. See the
for more information.
Possible values are:
Up – The interface is ready to pass packets of data.
Down – The interface is not available to pass packets of data.
Testing – The interface is in test mode.
Other – The Administrative State reported is not a recognized value.
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
HPE Network Node Manager i Software (10.20)
Page 116 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface State Attributes, continued
Attribute Description
Operational
State
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.
The current Operational State provided by: l
The managing
l
The managing
This value contributes towards the status calculation for this interface. See the
for more information.
Possible values are:
Up – Ready to receive and send network traffic: the physical or virtual interface is operationally up.
Down – The physical or virtual interface is operationally down.
Dormant – Indicates interface is in a "pending” state, waiting for some external event.
Lower Layer Down – Indicates the interface is down due to the state of lower-level interfaces.
Minor Fault – The interface is still functional, but a minor concern was detected.
Check the device, itself, for more details.
Not Present – Indicates that the interface is missing.
Other – The Operational State reported is not a recognized value.
Testing – The interface is in test mode.
Unknown – The Operational State value could not be detected.
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.
HPE Network Node Manager i Software (10.20)
Page 117 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface State Attributes, continued
Attribute Description
State Last
Modified
Notes
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.
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
The date and time when the Administrative State, Operational State, or both were last modified.
Provided for network operators to use for any additional notes required to further explain the interface. Information might include to what service or customer the interface is connected.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your interface table views based on this value. Therefore, you might want to include keywords for this attribute value.
Interface Form: General Tab
The
provides details about the selected network interface.
For information about each tab:
General SNMP Values
Attribute Description
ifName iIfAlias ifDescr ifIndex
Optional Interface MIB variable for ifName () assigned to the interface by the vendor. If no IfName value is provided, SNMP uses the ifType+ifIndex which is dynamically configured and can change. This name is not guaranteed to be unique or consistent across reboots.
Optional Interface MIB variable for ifAlias assigned to the interface. This value is set by the device administrator. An ifAlias could be useful if the interface vendor did not provide an ifName value.
Optional Interface MIB variable for ifDescr (1.3.6.1.2.1.2.2.1.2) for the interface. This attribute is set by the device administrator.
Interface MIB variable for the row number in the interface table (ifTable)
HPE Network Node Manager i Software (10.20)
Page 118 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
General SNMP Values, continued
Attribute Description
for this interface. The row number can change. If you are an
Administrator, see Accurately Detect Interface Changes for more information.
Note: Interfaces on non-SNMP nodes have an ifIndex value of 0
(zero).
ifSpeed ifType
Interface MIB variable for the interface’s bandwidth in bits per second.
Depending on the device vendor, this value might indicate current speed or potential speed.
Interface MIB variable for the physical link protocol type of the interface.
Possible values include: Ethernet and frameRelay.
Note: Interfaces on non-SNMP nodes have an ifType value of other.
Requires HPE 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) -click here for more information .
Input Speed (NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics Software is installed and configured within your environment, you can type an integer value to override the input speed value returned by the device's SNMP agent. Indicate the speed this interface is capable of receiving data in bits per second.
For example, you might want to override the Input Speed value for the following reason:
Sometimes the value returned by the device's SNMP agent is not accurate or causes problems when NNM iSPI Performance for Metrics calculates performance monitoring. For example, the input speed might be restricted due to circumstances in your environment, or bandwidth controls might limit the connection speed regardless of what the physical connection is capable of (such as within a WAN).
Note: (NNMi Advanced - Global Network Management) If you change this value for an Interface monitored by a Regional Manager,
NNMi forwards the updated information to the Global Manager at the next Discovery Interval.
If you are an NNMi administrator, you can set input speeds for multiple interfaces using the nnmsetiospeed.ovpl
command. Also see
HPE Network Node Manager i Software (10.20)
Page 119 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
General SNMP Values, continued
Attribute Description
Output Speed
"Maintaining NNMi" in the HPE Network Node Manager i Software
Deployment Reference for more information.
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics Software is installed and configured within your environment, you can type an integer value to override the output speed value returned by the device's SNMP agent. Indicate the speed this interface is capable of transmitting data in bits per second.
For example, you might want to override the Output Speed value for the following reason:
Sometimes the value returned by the device's SNMP agent is not accurate or causes problems when NNM iSPI Performance for Metrics calculates performance monitoring. For example, the output speed might be restricted due to circumstances in your environment, or bandwidth controls might limit the connection speed regardless of what the physical connection is capable of (such as within a WAN).
Note: (NNMi Advanced - Global Network Management) If you change this value for an Interface monitored by a Regional Manager,
NNMi forwards the updated information to the Global Manager at the next Discovery Interval.
If you are an NNMi administrator, you can set output speeds for multiple interfaces using the nnmsetiospeed.ovpl
command. Also see
"Maintaining NNMi" in the HPE Network Node Manager i Software
Deployment Reference for more information.
Interface Form: IP Addresses Tab
The
provides details about the selected network interface.
For information about each tab:
IP Addresses Table
Attribute Description
IP
Address
Table view of the IP addresses associated with the selected interface. You can use this table to determine the state and address for each IP address.
Double-click the row representing an IP address. The
displays all details about the selected IP address.
Interface Form: Ports Tab
The
provides details about the selected network interface.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 120 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Ports Table
Attribute Description
Ports Table view of all of the ports associated with the selected interface. Use this table to access information about each port associated with the selected interface.
Double-click the row representing a port. The
displays all details about the selected port.
Interface Form: VLAN Ports Tab
Tip: The
provides details about the selected network interface.
For information about each tab:
(NNMi Advanced - Global Network Management feature) There might be slight differences between the VLAN information shown on Regional Managers and Global Managers, because the VLAN calculations use
data.
VLAN Ports Table
Attribute
Description
VLAN
Ports
Table view of all of the VLAN ports associated with the current interface. Use this table to determine all port and VLAN combinations associated with this interface.
Double-click the row representing a VLAN port. The
displays all details about the selected VLAN port.
Interface Form: Link Aggregation Tab ( NNMi Advanced )
The
provides details about the selected network interface.
For more information about each tab:
The Interface Form: Link Aggregation Tab appears if the selected interface uses a Link Aggregation protocol.
HPE Network Node Manager i Software (10.20)
Page 121 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
On a Layer 2 map, a thick line with a superimposed ellipse represents a
Link Aggregation
1
Aggregation
2 or
Split Link
(group of multiple Layer 2 Connections that are functioning as one). The icon representing an
Interface at either end of the thick line is an Aggregator Interface (a logical interface comprised of many physical interfaces that are functioning as one).
Two endpoints: Three endpoints: More than three endpoints:
The selected object's role in the Link Aggregation determines the contents of the tab:
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 122 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
Aggregation Member, click here for details .
Attribute
Link
Aggregation
Protocol
Description
The
Link Aggregation
1 or
Split Link Aggregation
2
Protocol currently in use. These protocols allow network administrators to configure a set of interfaces on a switch as one
Aggregator Interface, creating an Aggregator Layer 2 Connection to another device using multiple interfaces in parallel to increase bandwidth, increase the speed at which data travels, and increase redundancy:
Text Represents This Protocol
Cisco Port Aggregation Protocol
Nortel Multi-Link Trunking
Split MLT
Cisco Systems Port Aggregation Protocol
(pagp)
Nortel Multi-Link Trunk technology (mlt)
Split Multi-Link Trunk: configuration technology
(splitMlt)
Split Multi-Link Trunk: inter-switch trunk (istMlt) Inter-Switch Trunk MLT
802.3ad Link Aggregation Control
Protocol
Static/Manual Configured Link
Aggregation
IEEE 802.3ad Link Aggregation Control protocol
(LACP)
Static/Manual Configured Link Aggregation
Unknown Protocol Link Aggregation unknown
Note: It is possible for a Layer 2 Connection to connect sets of Aggregator/Member
Interfaces that are configured using different Link Aggregation protocols. In that case, this attribute value contains multiple protocols separated with a slash (/).
Aggregator Name of the Aggregator that contains the selected participating Aggregation Member: l
Aggregator Interface - represents multiple member interfaces l
Aggregator Layer 2 Connection - thick line on the Layer 2 map represents multiple member Layer 2 Connections
See Layer 2 Neighbor View Map Objects for more information.
Click the Lookup icon, and choose Open to open the form for the Aggregator.
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 123 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
Aggregator (representing multiple members), click here for details .
Attribute
Link
Aggregation
Protocol
Description
The
Link Aggregation
1 or
Split Link Aggregation
2
Protocol currently in use. These protocols allow network administrators to configure a set of interfaces on a switch as one
Aggregator Interface, creating an Aggregator Layer 2 Connection to another device using multiple interfaces in parallel to increase bandwidth, increase the speed at which data travels, and increase redundancy:
Text Represents This Protocol
Cisco Port Aggregation Protocol
Nortel Multi-Link Trunking
Split MLT
Cisco Systems Port Aggregation Protocol
(pagp)
Nortel Multi-Link Trunk technology (mlt)
Split Multi-Link Trunk: configuration technology
(splitMlt)
Split Multi-Link Trunk: inter-switch trunk (istMlt) Inter-Switch Trunk MLT
802.3ad Link Aggregation Control
Protocol
Static/Manual Configured Link
Aggregation
IEEE 802.3ad Link Aggregation Control protocol
(LACP)
Static/Manual Configured Link Aggregation
Unknown Protocol Link Aggregation unknown
Note: It is possible for a Layer 2 Connection to connect sets of Aggregator/Member
Interfaces that are configured using different Link Aggregation protocols. In that case, this attribute value contains multiple protocols separated with a slash (/).
Available
Bandwidth
Maximum
Bandwidth
Sum of the interface Input Speed attribute values of the Member Interfaces that have a
MIB-II ifOperStatus that is not Down. If the sum of the interface Output Speed attribute values is different, NNMi displays separate Available Input Bandwidth and Available
Output Bandwidth attributes.
Sum of the interface Input Speed attribute values of the Member Interfaces, regardless of
MIB-II ifOperStatus. If the sum of the interface Output Speed attribute values is different, NNMi displays separate Maximum Input Bandwidth and Maximum Output
Bandwidth attributes.
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 124 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Attribute Description
Available
Bandwidth
Percentage
Percentage value computed using Available Bandwidth divided by the Maximum
Bandwidth.
Members Table view of the Aggregation Members.
For more information, double-click the row representing an Aggregation Member: l
The
displays all details about the selected Interface.
l
The
"Layer 2 Connection Form" on page 255
displays all details about the selected
Layer 2 Connection.
Interface Form: Performance Tab (
NNM iSPI Performance for
Metrics )
Requires HPE 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) -click here for more information .
The
provides details about the selected network interface.
Tip: This information is also visible in the Monitoring workspace, Interface Performance view.
For information about each tab:
The Performance tab displays data if the HPE Network Node Manager iSPI Performance for Metrics
Software software is installed and configured within your environment.
The icons on the Performance tab indicate the value from the most recent polling interval for interface performance states:
High - The High threshold was crossed.
Abnormal Range - This interface is abnormal based on the computed baseline for the specified threshold.
Nominal -
Measured within healthy range.
(Or no thresholds are being monitored.)
Normal Range - This interface is normal based on the computed baseline for the specified threshold.
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.
Low - The Low threshold was crossed.
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
HPE Network Node Manager i Software (10.20)
Page 125 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
None - The value returned was zero.
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.
Tip: NNMi can generate incidents based on threshold results
Optional: The NNMi administrator can configure thresholds for the metrics described in the following list. If you want to see the threshold configuration settings for the currently selected Interface, click Actions →
Configuration Details → Monitoring Settings, then scroll down to the Count-Based Threshold Settings table and Time-Based Threshold Settings table: l
FCS LAN Error Rate
Local Area Network interfaces only.Threshold based on the percentage of incoming frames with a bad checksum (
CRC
1 value) compared to the total number of incoming frames. Possible causes include collisions at half-duplex, a duplex mismatch, bad hardware (
NIC
2
, cable, or port), or a connected device generating frames with bad Frame Check Sequence.
l
FCS WLAN Error Rate
Wireless Local Area Network Interfaces only. Threshold based on the percentage of incoming frames with a bad checksum (
CRC
3 value) compared to the total number of incoming frames. Possible causes include wireless communication interference, bad hardware (
NIC
4
, cable or port), or a connected device generating frames with bad Frame Check Sequence.
l
Input Discard Rate
Threshold based on the percentage of the interface's discarded input packet count compared to the total number of packets received. Packets might be discarded because of a variety of issues, including receivebuffer overflows, congestion, or system specific issues.
l
Input Error Rate
Threshold based on the percentage of the interface's input packet error count compared to the total number of packets received. What constitutes an error is system specific, but likely includes such issues as bad packet checksums, incorrect header information, and packets that are too small.
l
Input Queue Drops Rate
Threshold based on the percentage of the interface's dropped input packets compared to the total number of packets received. Possible causes include the input queue being full.
l
Input Utilization
1
Cyclic Redundancy Check
2
Network Interface Controller
3
Cyclic Redundancy Check
4
Network Interface Controller
HPE Network Node Manager i Software (10.20)
Page 126 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Threshold based on the percentage of the interface's total incoming octets compared to the maximum number of octets possible (determined by the MIB being used to query ifSpeed of the device and whether the host system supports high-speed counters for interfaces).
Tip: Sometimes the ifSpeed value returned by the device's SNMP agent is not accurate and causes problems with thresholds. If your NNMi role allows, you can override the ifSpeed reported by the
SNMP agent: a. Open the problem interface's Interface form.
b. Select the
c. Locate the Input/Output Speed section.
d. Change the Input Speed or Output Speed setting.
l
Output Discard Rate
Threshold based on the percentage of the interface's discarded output packet count compared to the total number of outgoing packets. Packets might be discarded because of a variety of issues, including transmission buffer overflows, congestion, or system specific issues.
l
Output Error Rate
Threshold based on the percentage of the interface's output packet error count compared to the total number of outgoing packets. What constitutes an error is system specific, but likely includes such issues as as collisions and buffer errors.
l
Output Queue Drops Rate
Threshold based on the percentage of the interface's dropped output packets compared to the total number of outgoing packets. Possible causes include all buffers allocated to the interface being full.
l
Output Utilization
Threshold based on the percentage of the interface's total outgoing octets compared to the maximum number of octets possible (determined by the MIB being used to query ifSpeed of the device and whether the host system supports high-speed counters for interfaces).
Tip: Sometimes the ifSpeed value returned by the device's SNMP agent is not accurate and causes problems with thresholds. If your NNMi role allows, you can override the ifSpeed reported by the
SNMP agent: a. Open the problem interface's Interface form.
b. Select the
c. Locate the Input/Output Speed section.
d. Change the Input Speed or Output Speed setting.
Interface Form: IP Addresses Tab
The
provides details about the selected network interface.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 127 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
IP Addresses Table
Attribute Description
IP
Address
Table view of the IP addresses associated with the selected interface. You can use this table to determine the state and address for each IP address.
Double-click the row representing an IP address. The
displays all details about the selected IP address.
Interface Form: Capabilities Tab
The
provides details about the selected interface.
For information about each tab:
The Interface Form: Capabilities Tab displays a table view of any capabilities added to the interface object by
NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about an interface than is initially stored in the NNMi database.
For example, NNMi uses the capability feature to identify interfaces for which NNMi can obtain only limited information. Examples of these interfaces include Nortel interfaces as well as any interface on a non-SNMP node. To help identify these interfaces, NNMi assigns the interface the capability of com.hp.nnm.capability.iface.private.
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Capabilities Table
Attribute Description
Capability Table of all of the capabilities associated with the selected Interface. Use this table to access information about each Capability.
Double-click the row representing a Capability. The
"Interface Capability Form" on page 134
displays all details about the selected Capability.
For more information, see
"Interface Capabilities Provided by NNMi" below
.
Interface Capabilities Provided by NNMi
The
"Interface Form: Capabilities Tab" above
displays a table of any capabilities added to a particular interface object. Capabilities enable NNMi and application programmers to provide more information about an interface than what is initially stored in the NNMi database.
Additional vendor-specific capabilities may appear from device extension settings.
External applications can also add capabilities.
KEY: com.hp.<product>.capability.<content>.<vendor/org>.<MIB/feature>
Any Capability provided by NNMi begins with the prefix com.hp.nnm.capability.
HPE Network Node Manager i Software (10.20)
Page 128 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
<product> = Either NNMi or the NNM iSPI providing this capability.
<content> = chassis, card, ipaddr (address), iface (interface), lag (
Link Aggregation
1
Aggregation
2 or
Split Link
interface), node, rrp (Router Redundancy), or metric (Node Sensor or Physical Sensor).
<vendor/org> = Standards organization or vendor defining the MIB or feature associated with the capability.
<MIB/feature> = What this capability measures.
Note: The following tables show a few examples of the Capabilities provided by NNMi.
Interface Capability Attribute Values
Unique Key
com.hp.nnm.capability.iface.private
Capability
Private
Description
Indicates the interface was discovered in either a non-
SNMP node or a Nortel node.
Private interfaces are not monitored for Status.
For interfaces on non-SNMP nodes, note the following: l
The interface index ( ifIndex) value is always set to 0
(zero).
l
The interface type ( ifType) is set to Other.
l
The interface Name
( ifName), if none is available, is set to Pseudo Interface.
Note: For Pseudo
Interface, NNMi attempts to obtain additional information using a variety of
discovery protocols (see the list of Topology
Source protocols in
).
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 129 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Capability Attribute Values, continued
Unique Key
com.hp.nnm.capability.iface.ietf.NON-
DEFAULT-CONTEXT-RFC1213 com.hp.nnm.capability.iface.PE
Capability
RFC 1213
Interface from
Non-default
Context
PE Interface
Description
l l
If the interface hosts an
IP address, the interface
Alias ( ifAlias) is set to the
IP address. Otherwise, the interface Alias ( ifAlias) is set with information from neighboring SNMP devices.
NNMi obtains the MAC address if the IP address can be resolved using
ARP cache.
For Nortel SNMP interfaces, note the following: l
The interface index ( ifIndex) value is set according the
Nortel private MIB.
l
NNMi tries to collect the
MAC address and interface name using Nortel's private
MIBs.
Indicates the following: l
NNMi discovered the interface from the RFC1213
MIB.
l
The interface has a context other than default.
Note:
l
NNMi collects context values using the vacmContextTable in the SNMP-VIEW-
BASED-ACM-MIB defined in RFC2575.
l
NNMi does not monitor interfaces under a nondefault context.
Indicates that the interface is
HPE Network Node Manager i Software (10.20)
Page 130 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Capability Attribute Values, continued
Unique Key
com.hp.nnm.capability.br.bridge
com.hp.nnm.capability.br.port
Capability Description
serving as a Provider Edge
(
PE
1
). NNMi's Subnet
Connection Rules use this information.
Virtual Bridge
Virtual Bridge Port Indicates that the interface represents any interface associated with a virtual bridge.
VM Virtual
Machine Interface
Indicates that the interface represents a virtual bridge (also known as a virtual switch).
Requires HPE 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) -click here for more information .
com.hp.nnm.capability.iface.ietf.DS1
DS1 Interface
Metrics com.hp.nnm.capability.iface.ietf.DS3
DS3 Interface
Metrics com.hp.nnm.capability.iface.ietf.ETHERLIKE EtherLike
Interface Metrics com.hp.nnm.capability.iface.ietf.IEEE80211 IEEE 802.11
Interface Metrics
Interface that supports the DS1
(T1) MIB for gathering performance data. This data is used by NNM iSPI Performance for Metrics.
Interface that supports the DS3
(T3) MIB for gathering performance data. This data is used by NNM iSPI Performance for Metrics.
Interface that supports the
Etherlike MIB for gathering performance data. NNMi uses this MIB to monitor LAN errors.
This data is used by NNM iSPI
Performance for Metrics.
Interface that supports the IEEE
802.11 Interface Metrics MIB.
NNMi can monitor for WLAN metrics. This data is used by
NNM iSPI Performance for
1
Provider Edge router. The Internet Service Provider's router that receives your data on the path to your data's final desination. The Customer Edge (CE) router in your network connects to this PE.
HPE Network Node Manager i Software (10.20)
Page 131 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Capability Attribute Values, continued
Unique Key
com.hp.nnm.capability.iface.ietf.SONET
com.hp.nnm.capability.iface.ietf.SONET-
PATH
Capability Description
Metrics.
SONET Interface
Metrics
SDH Interface
Metrics
Interface that supports the
SONET-MIB interval monitoring metrics. This capability determines membership in the
SONET interface group. This data is used by NNM iSPI
Performance for Metrics.
Interface that supports the
SONET-PATH-MIB metrics.
This data is used by NNM iSPI
Performance for Metrics.
(NNMi Advanced) IPv6
Unique Key Capability Description
com.hp.nnm.capability.iface.ipv6.rfc2465 RFC2465-
IPv6-
Interface
Indicates the interface is an IPv6 interface, discovered using only the RFC
2465 IPv6-MIB and not the standard RFC
2863 IF-MIB.
A small number of IPv6 devices do not support the standard RFC 2863 IF-MIB for
IPv6 interfaces. In this case, NNMi uses the RFC 2465 IPv6-MIB. When this happens, note the following: l
Interface index ( ifIndex) and description ( ifDescr) are set according to the RFC 2465 IPv6 MIB.
l l
Interface type ( ifType) is set to Other
(no specific type is available).
Interface Name ( ifName), Alias
( ifAlias), and Speed (ifSpeed) are blank (not available).
l
NNMi monitors the Status of this interface, but Performance metrics are not available.
When an IP Address has the Interface
Name ( ifName) attribute set to blank,
NNMi constructs an alternate string for the IP Address's In Interface attribute
( Other[<ifIndex_value>]).
HPE Network Node Manager i Software (10.20)
Page 132 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
(NNMi Advanced) The capabilities in the following table identify how the interface is participating in a
Link
Aggregation
1 or
Split Link Aggregation
2
.
(NNMi Advanced) Link Aggregation Interface Capabilities: Roles
Unique Key Capability Description
com.hp.nnm.capability.lag.aggregator Aggregator com.hp.nnm.capability.lag.member
Interface
Indicates the interface represents a collection of participating interfaces at one end of an
Aggregator Layer 2 Connection.
See Layer 2 Neighbor View Map Objects for more information.
Aggregation
Member
Indicates the interface is a physical interface that is a member of an Aggregator Interface.
See Layer 2 Neighbor View Map Objects for more information.
(NNMi Advanced) The capabilities in the following table are used when
Link Aggregation
3
Aggregation
4 protocol is available.
or
Split Link
(NNMi Advanced) Link Aggregation Interface Capabilities: Protocols
Unique Key Capability Description
com.hp.nnm.capability.lag.protocol.lacp
com.hp.nnm.capability.lag.protocol.static
Static/Manual
Configured
Link
Aggregation com.hp.nnm.capability.lag.protocol.pagp
802.3ad Link
Aggregation
Control
Protocol
Cisco Port
Aggregation
Protocol
Indicates an interface using the
IEEE 802.3ad Link Aggregation
Control protocol (LACP).
Indicates the device has been configured with Static/Manual
Configured Link Aggregation
(static).
Cisco Systems Port Aggregation
Protocol (pagp)
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
3
Protocols 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).
4
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 133 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
(NNMi Advanced) Link Aggregation Interface Capabilities: Protocols, continued
Unique Key Capability Description
com.hp.nnm.capability.lag.protocol.mlt
Nortel Multi-
Link Trunking com.hp.nnm.capability.lag.protocol.istmlt
Inter-Switch
Trunk MLT com.hp.nnm.capability.lag.protocol.smlt
Split MLT com.hp.nnm.capability.lag.protocol.unknown Unknown
Protocol Link
Aggregation
Nortel Multi-Link Trunk technology
(mlt)
Split Multi-Link Trunk: inter-switch trunk (istMlt)
Split Multi-Link Trunk: configuration technology (splitMlt)
Indicates the hosting interface is a member of Link Aggregation with unknown protocol.
Interface Capability Form
This form describes a capability added to the interface object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about a card than what is initially stored in the NNMi database.
For example, NNMi uses the capability feature to identify interfaces for which NNMi can obtain only limited information. Examples of these interfaces include Nortel interfaces as well as any interface on a non-SNMP node. To help identify these interfaces, NNMi assigns the interface the capability of com.hp.nnm.capability.iface.private.
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Interface Capability Attributes
Attribute Description
Capability Label used to identify the Capability that was added to the interface object.
"Interface Form: Capabilities Tab" on page 128
shows a list of all available Capabilities for that interface.
For more information, see
"Interface Capabilities Provided by NNMi" on page 128 .
Unique
Key
Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.
For more information, see
"Interface Capabilities Provided by NNMi" on page 128 .
Interface Form: Custom Attributes Tab
Custom Attributes enable an NNMi administrator to add information to the Interface object. Custom Attributes can also be set by external applications that have been integrated with NNMi. See
HPE Network Node Manager i Software (10.20)
Page 134 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Attribute Samples" on page 136 .
The Interface Form: Custom Attributes tab displays a table view of any Custom Attributes that have been added to the selected interface.
Note: If your role permits, you can edit a Custom Attribute. Only users assigned to the NNMi
Administrator role can add a Custom Attribute.
For information about each tab:
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Custom Attributes Table
Attribute Description
Name
Value
Name used to identify the Custom Attribute. This name appears in the table view on the
Custom Attributes tab in Interface forms. Limit 50 of any combination of keyboard entries including spaces.
The actual value for the Custom Attribute for the selected interface. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Custom Interface Attributes Form" below .
Custom Interface Attributes Form
Custom Attributes enable an NNMi administrator to add information to a node object. Custom Attributes can also be set by external applications that have been integrated with NNMi. See
.
The required settings for these attributes are described in the table below.
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Basics Attributes
Attribute Description
Name Name used to identify the Custom Attribute. This name appears in the table view on the
Custom Attributes tab in the Interface forms. Limit 50 of any combination of keyboard entries including spaces.
Value Value assigned to the Custom Attribute for the selected interface object. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Interface Form: Custom Attributes Tab" on the previous page
.
HPE Network Node Manager i Software (10.20)
Page 135 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Custom Interface Attribute Samples
Custom Attributes provide additional information about an object instance: l
NNMi administrators can associate custom information with the Interface for their network management team's benefit.
For example, your NNMi administrator might have added the following: l
Name:
Assignment l
Value:
WAN interface to the London office.
l
External applications that have been integrated with NNMi can associate custom information with the
Interface.
For example, when HPE Network Node Manager iSPI Performance for Metrics Software is installed, your NNMi administrator can provide additional Node or Interface information in NNM iSPI
Performance for Metrics reports: l
Name =
NPS Annotation l
Value =
<text to appear in the reports>.
See the help topic: Annotate NNM iSPI Performance for Metrics Reports .
l
NNMi can associate custom information about an Interface.
For example, if the NNMi administrator enables the Discovery and Monitoring of unnumbered interfaces, you will see this Custom Attribute associated with each unnumbered interface: l
Name: UnnumberedNextHop l
Value: <IP address of the neighboring device>
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Related Topics:
"Interface Form: Custom Attributes Tab" on page 134
"Custom Interface Attributes Form" on the previous page
Interface Form: Interface Groups Tab
The
provides details about the selected network interface.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 136 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Groups Membership Table
Attribute Description
Interface
Groups
Table view of Interface Groups to which the selected interface belongs. Interface groups are based on specific characteristics of interfaces.
Double-click the row representing an Interface Group. The
"Interface Group Form" on page 302
displays all details about the selected Interface Group.
Interface Form: Performance Tab ( NNM iSPI Performance for
Metrics )
Requires HPE 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) -click here for more information .
The
provides details about the selected network interface.
Tip: This information is also visible in the Monitoring workspace, Interface Performance view.
For information about each tab:
The Performance tab displays data if the HPE Network Node Manager iSPI Performance for Metrics
Software software is installed and configured within your environment.
The icons on the Performance tab indicate the value from the most recent polling interval for interface performance states:
High - The High threshold was crossed.
Low - The Low threshold was crossed.
Abnormal Range - This interface is abnormal based on the computed baseline for the specified threshold.
Nominal -
Measured within healthy range.
(Or no thresholds are being monitored.)
Normal Range - This interface is normal based on the computed baseline for the specified threshold.
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.
None - The value returned was zero.
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
HPE Network Node Manager i Software (10.20)
Page 137 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details values or returned a null value.
Unset – Currently not used by NNMi.
Tip: NNMi can generate incidents based on threshold results
Optional: The NNMi administrator can configure thresholds for the metrics described in the following list. If you want to see the threshold configuration settings for the currently selected Interface, click Actions →
Configuration Details → Monitoring Settings, then scroll down to the Count-Based Threshold Settings table and Time-Based Threshold Settings table: l
FCS LAN Error Rate
Local Area Network interfaces only.Threshold based on the percentage of incoming frames with a bad checksum (
CRC
1 value) compared to the total number of incoming frames. Possible causes include collisions at half-duplex, a duplex mismatch, bad hardware (
NIC
2
, cable, or port), or a connected device generating frames with bad Frame Check Sequence.
l
FCS WLAN Error Rate
Wireless Local Area Network Interfaces only. Threshold based on the percentage of incoming frames with a bad checksum (
CRC
3 value) compared to the total number of incoming frames. Possible causes include wireless communication interference, bad hardware (
NIC
4
, cable or port), or a connected device generating frames with bad Frame Check Sequence.
l
Input Discard Rate
Threshold based on the percentage of the interface's discarded input packet count compared to the total number of packets received. Packets might be discarded because of a variety of issues, including receivebuffer overflows, congestion, or system specific issues.
l
Input Error Rate
Threshold based on the percentage of the interface's input packet error count compared to the total number of packets received. What constitutes an error is system specific, but likely includes such issues as bad packet checksums, incorrect header information, and packets that are too small.
l
Input Queue Drops Rate
Threshold based on the percentage of the interface's dropped input packets compared to the total number of packets received. Possible causes include the input queue being full.
l
Input Utilization
Threshold based on the percentage of the interface's total incoming octets compared to the maximum number of octets possible (determined by the MIB being used to query ifSpeed of the device and whether the host system supports high-speed counters for interfaces).
Tip: Sometimes the ifSpeed value returned by the device's SNMP agent is not accurate and causes
1
Cyclic Redundancy Check
2
Network Interface Controller
3
Cyclic Redundancy Check
4
Network Interface Controller
HPE Network Node Manager i Software (10.20)
Page 138 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details problems with thresholds. If your NNMi role allows, you can override the ifSpeed reported by the
SNMP agent: a. Open the problem interface's Interface form.
b. Select the
c. Locate the Input/Output Speed section.
d. Change the Input Speed or Output Speed setting.
l
Output Discard Rate
Threshold based on the percentage of the interface's discarded output packet count compared to the total number of outgoing packets. Packets might be discarded because of a variety of issues, including transmission buffer overflows, congestion, or system specific issues.
l
Output Error Rate
Threshold based on the percentage of the interface's output packet error count compared to the total number of outgoing packets. What constitutes an error is system specific, but likely includes such issues as as collisions and buffer errors.
l
Output Queue Drops Rate
Threshold based on the percentage of the interface's dropped output packets compared to the total number of outgoing packets. Possible causes include all buffers allocated to the interface being full.
l
Output Utilization
Threshold based on the percentage of the interface's total outgoing octets compared to the maximum number of octets possible (determined by the MIB being used to query ifSpeed of the device and whether the host system supports high-speed counters for interfaces).
Tip: Sometimes the ifSpeed value returned by the device's SNMP agent is not accurate and causes problems with thresholds. If your NNMi role allows, you can override the ifSpeed reported by the
SNMP agent: a. Open the problem interface's Interface form.
b. Select the
c. Locate the Input/Output Speed section.
d. Change the Input Speed or Output Speed setting.
Interface Form: Incidents Tab
The
provides details about the selected network interface.
For information about each tab:
Incidents Table
Attribute Description
Associated Table view of the incidents associated with the selected interface. These incidents are sorted
HPE Network Node Manager i Software (10.20)
Page 139 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Incidents Table, continued
Attribute Description
Incidents 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 interface.
Double-click the row representing an incident. The
displays all details about the selected incident.
Interface Form: Status Tab
The
provides details about the selected network interface.
For information about each tab:
Status Tab
Attribute Description
Status Overall status for the current interface. NNMi follows the ISO standard for status classification.
Possible values are:
Note: The icons are displayed only in table views.
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Interface status is derived from SNMP polling results for
and
well as any conclusions. For information about how the current status was determined, see the
"Interface Form: Conclusions Tab" on the next page
. Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
(NNMi Advanced)
HPE Network Node Manager i Software (10.20)
Page 140 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status Tab, continued
Attribute Description
l
Link Aggregation
1 or
Split Link Aggregation
2
: If the Interface is an Aggregator, the
Status is calculated using the combined Status of all Aggregation Member Interfaces. For
more information, see "Interface Form: Link Aggregation Tab (NNMi Advanced)" on page 121
and Status Color for Link Aggregation Objects .
l
If the interface is a virtual interface, note that the following categories indirectly indicate the current condition of the
hypervisor
3
:
Indicates that the hypervisor is Up
Indicates that the hypervisor is Down
Indicates a Null value in hypervisor state
Status
Last
Modified
Date and time indicating when the status was last set.
Status History Table
Attribute
Description
Status
History
List of up to the last 30 changes in the status for the interface. This view is useful for obtaining a summary of the interface status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
Interface Form: Conclusions Tab
The
provides details about the selected network interface.
All relevant conclusions are shown in the table on this tab. The most severe Status in the current group of conclusions becomes the overall Interface status. Some Interface conclusions propagate to other object types:
For information about each tab:
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
3
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 141 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses of the interface that contributed to the current overall status of the selected interface. Status is set by the Causal Engine.
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 for the current node’s interfaces that led up to the interface’s most current Status.
The Status value is correlated based on the most critical 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 an interface object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
AggregatorDown
Link Aggregation
1 or
Split Link
Aggregation
2
: The Operational State of the
Aggregator Interface is Down (if monitored), or all of the Aggregation Member Interfaces are Down. For more information, see
"Interface Form: Link Aggregation Tab
.
InterfaceDown The interface Operational State is Down.
Status Incident?
Critical Y
Critical Y
Major Status Conclusions (NNM iSPI Performance for Metrics)
Conclusion
InterfaceFCSLANErrorRateHigh
Description Status Incident?
Local Area Network.
Indicates a Frame
Check Sequence (FCS) error rate on the
Major Y
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 142 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceFCSWLANErrorRateHigh
InterfaceInputDiscardRateHigh
Description
interface has gone above a threshold setting.
The error rate is based on the number of frames that were received with a bad checksum (
CRC
1 value). Possible causes include collisions at half-duplex, a duplex mismatch, bad hardware (
NIC
2
, cable, or port), or a connected device generating frames with bad FCS.
Status Incident?
Wireless Local Area
Network. A Frame
Check Sequence (FCS) error rate on the interface has gone above a threshold setting.
The error rate is based on the number of frames that were received with a bad checksum (
CRC
3 value). Possible causes include collisions at half-duplex, a duplex mismatch, bad hardware (
NIC
4
, cable, or port), or a connected device generating frames with bad FCS.
Major Y
The input discard rate on the interface has
Major Y
1
Cyclic Redundancy Check
2
Network Interface Controller
3
Cyclic Redundancy Check
4
Network Interface Controller
HPE Network Node Manager i Software (10.20)
Page 143 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
exceeded a threshold setting.
This rate is based on the reported change in the number of input packets on the interface and the discarded packet count.
Status Incident?
InterfaceInputErrorRateHigh The input error rate on the interface has exceeded a threshold setting.
This rate is based on the reported change in the number of input packets on the interface and the packet error count.
Major Y
Major Y InterfaceInputQueueDropsRateHigh The number of input queue drops on the interface has exceeded a threshold setting.
This range is based on the number of packets dropped because of a full queue. Possible causes include that the number of packet buffers allocated to the interface is exhausted or has reached its maximum threshold.
InterfaceInputUtilizationHigh The input utilization on the interface has exceeded a threshold setting.
This percentage is based on the interface speed and the reported
Major Y
HPE Network Node Manager i Software (10.20)
Page 144 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceInputUtilizationLow
InterfaceInputUtilizationNone
InterfaceOutputDiscardRateHigh
InterfaceOutputErrorRateHigh
Description
change in the number of input bytes on the interface.
Status Incident?
The input utilization on the interface is below a threshold setting.
This percentage is based on the interface speed and the reported change in the number of input bytes on the interface.
Major Y
The input utilization for the interface is zero (0).
This value is based on the interface speed and the reported change in the number of input bytes on the interface.
Major Y
The output discard rate on the interface has exceeded a threshold setting.
This rate is based on the reported change in the number of input packets on the interface and the discarded packet count.
Major Y
The output error rate on the interface has exceeded a threshold setting.
This rate is based on the reported change in the number of output packets on the interface and the packet error count.
Major Y
HPE Network Node Manager i Software (10.20)
Page 145 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
InterfaceOutputQueueDropsRateHigh The number of output queue drops on the interface has exceeded a threshold setting.
This number is based on the number of packets dropped because of a full queue.
Status Incident?
Major Y
InterfaceOutputUtilizationHigh
InterfaceOutputUtilizationLow
InterfaceOutputUtilizationNone
The output utilization on the interface has exceeded a threshold setting.
This percentage is based on the interface speed and the reported change in the number of output bytes on the interface.
Major Y
The output utilization on the interface is below a threshold setting.
This percentage is based on the interface speed and the reported change in the number of output bytes on the interface.
Major Y
The output utilization on the interface is zero (0).
This value is based on the interface speed and the reported change in the number of output bytes on the interface.
Major Y
Minor Status Conclusions
HPE Network Node Manager i Software (10.20)
Page 146 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
AggregatorDegraded
Link Aggregation
1 or
Split Link
Aggregation
2
: One or more (but not all)
Aggregation Member Interfaces that are part of the Aggregator Interface have an
Operational State of Down. For more information, see
Aggregation Tab (NNMi Advanced)" on page 121 .
vSwitchDegraded (NNMi Advanced).
The Operational State of the virtual switch is Down.
This occurs when the Operational State of all uplinks on the virtual switch is
Down.
Status Incident?
Minor Y
Minor N
Warning Status Conclusions (NNM iSPI Performance for Metrics)
Conclusion Description Status
InterfaceInputUtilizationAbnormal The input utilization on the interface is abnormal based on the computed baseline.
Warning
This range is based on the interface speed and the reported change in the number of input bytes on the interface.
InterfaceOutputUtilizationAbnormal The output utilization on the interface is abnormal based on the computed baseline.
Warning
Incident?
Y
Y
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 147 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
This range is based on the interface speed, and the reported change in the number of output bytes on the interface.
Status Incident?
Warning Status Conclusions (NNMi Advanced)
Conclusion Description
vSwitchWarning The Operational State of at least one uplink on the virtual switch is Down.
Status Incident?
Warning N
Disabled Status Conclusions
Conclusion Description
InterfaceDisabled The interface has been explicitly disabled by the device administrator.
Status
Disabled
Incident?
Y vSwitchDisabled (NNMi Advanced). The Administrative
State of the virtual switch is Down.
This occurs when the Administrative State of all of the uplinks associated with the virtual switch is Down.
Disabled N
Unknown Status Conclusions
Conclusion Description
InterfaceUnmanagable The agent associated with the interface is not responding to queries.
Status
Unknown
Incident?
N
Normal Status Conclusions
HPE Network Node Manager i Software (10.20)
Page 148 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
AggregatorUp vSwitchUp
Description
Link
Aggregation
1 or
Split Link
Aggregation
2
:
The Aggregator
Interface and all
Aggregation
Member Interfaces have an
Operational State of Up. For more information, see
Status Incident?
Normal N
(NNMi Advanced).
Indicates the
Operational State of the virtual switch is Up.
This occurs when the Operational
State of all uplinks on the virtual switch is Up.
Normal N
Requires HPE 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) -click here for more information .
InterfaceEnabled The interface has Normal N
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 149 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceFCSLANErrorRateInRange
InterfaceFCSWANErrorRateInRange
InterfaceInputDiscardRateLow
InterfaceInputDiscardRateNominal
Description
an Administrative
State of Up.
Status Incident?
(NNM iSPI
Performance for
Metrics) The
Frame Check
Sequence error rate for the interface is within the allowable range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The
Frame Check
Sequence error rate for the interface is within the allowable range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The input discard rate for the interface is below the allowable low range set by the administrator.
(NNM iSPI
Performance for
Metrics) The input discard rate for the interface is within the allowable threshold range set by the administrator.
Normal N
Normal N
HPE Network Node Manager i Software (10.20)
Page 150 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceInputDiscardRateNone
InterfaceInputErrorRateLow
InterfaceInputErrorRateNominal
Description Status Incident?
(NNM iSPI
.
Performance for
Metrics) The input discard rate for the interface is zero (0)
Normal N
(NNM iSPI
Performance for
Metrics) The input error rate for the interface is below the allowable threshold range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The input error rate for the interface is within the allowable threshold range set by the administrator.
Normal N
InterfaceInputErrorRateNone (NNM iSPI
Performance for
Metrics) The input error rate for the interface is zero
(0).
Normal N
InterfaceInputQueueDropsRateInRange (NNM iSPI
Performance for
Metrics) The number of input queue drops for the interface is within the allowable range set by the administrator.
Normal N
HPE Network Node Manager i Software (10.20)
Page 151 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceInputUtilizationNominal
InterfaceInputUtilizationNormal
InterfaceOutputDiscardRateLow
InterfaceOutputDiscardRateNominal
Description
(NNM iSPI
Performance for
Metrics) The input utilization for the interface is within the allowable threshold range set by the administrator.
Status Incident?
Normal N
(NNM iSPI
Performance for
Metrics) The input utilization on the interface is normal based on the computed baseline. This range is based on the interface speed and the reported change in the number of input bytes on the interface.
Normal N
(NNM iSPI
Performance for
Metrics) The output discard rate for the interface is below the allowable threshold range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The output discard rate for the interface is within the allowable threshold range set by the
Normal N
HPE Network Node Manager i Software (10.20)
Page 152 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceOutputDiscardRateNone
InterfaceOutputErrorRateLow
Description
administrator.
Status Incident?
(NNM iSPI
Performance for
Metrics) The output discard rate for the interface is zero
(0).
Normal N
(NNM iSPI
Performance for
Metrics) The output error rate for the interface is below the allowable low range set by the administrator.
Normal N
InterfaceOutputErrorRateNominal
InterfaceOutputErrorRateNone
(NNM iSPI
Performance for
Metrics) The output error rate for the interface is within the allowable threshold range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The output error rate for the interface is zero
(0).
Normal N
InterfaceOutputQueueDropsRateInRange (NNM iSPI
Performance for
Metrics) The number of output queue drops for the interface is within the allowable threshold range set by the administrator.
Normal N
HPE Network Node Manager i Software (10.20)
Page 153 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
InterfaceOutputUtilizationNominal
InterfaceOutUtilizationNormal
InterfaceUp
Description Status Incident?
(NNM iSPI
Performance for
Metrics) The output utilization for the interface is within the allowable threshold range set by the administrator.
Normal N
(NNM iSPI
Performance for
Metrics) The output utilization for the interface is within the allowable threshold range set by the administrator.
Normal N
The Operational
State of the interface is Up.
Normal N
Interface Form: Registration Tab
The
provides details about the selected network interface.
For information about each tab:
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.
Note: 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: l
When a node is rediscovered, the Last Modified time is the same as the Discovery
HPE Network Node Manager i Software (10.20)
Page 154 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Registration Attributes, continued
Attribute Description
Completed time. This is because the node’s Discovery State changes from Started to
Completed.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
Virtual Switch's Interface Form (NNMi Advanced)
When the
provides details about a virtual switch, two additional tabs appear: l
Uplinks
l
Virtual Ports
The virtual switch is identified with the Virtual Bridge capability (see
"Interface Form: Capabilities Tab" on page 128 ).
You can launch the virtual switch's Interface form from the following locations: l
A table of Interfaces l
A map view by double-clicking the Switch icon
For additional information about the
hypervisor
1 providing this virtual switch, see: l
Using the Wheel Dialog l
Using the Loom Dialog
1
The virtual machine manager in charge of delegating various aspects from a pool of resources to become virtual devices. The delegations might be static or dynamic, depending on the manufacture's implementation.
The type of virtual machines being generated depends on the manufacturer's implementation.
HPE Network Node Manager i Software (10.20)
Page 155 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
Basic Attributes
Attribute Description
Name
Status
The most accurate interface name available to the initial discovery process. First choice is the IF MIB ifName value. Second choice is the ifAlias value. Third choice is a combination of the ifType[ifIndex] value (for example, ethernetCsmacd[17]).
Overall status for the current interface. NNMi follows the ISO standard for status classification. See the
"Interface Form: Status Tab" on page 140
for more information.
Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Interface status is derived from SNMP polling results for
and
, as well as from any conclusions. Status reflects the most serious outstanding conclusion.
See the
"Interface Form: Conclusions Tab" on page 141
for information about how the current status was determined. See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views.
Management
Mode
The calculated Management Mode for the interface according to the Management Mode
Hierarchy. This value reflects the current management mode of this interface's parent object (the Hosted On Node). See
"How NNMi Assigns the Management Mode to an
.
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: You can also right-click any object in a table or map view to access the items available within the Actions menu.
HPE Network Node Manager i Software (10.20)
Page 156 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Direct
Management
Mode
Indicates whether or not NNMi is currently monitoring the interface. Possible values are:
Inherited – Used to indicate that the interface should inherit the Management Mode from this interface's parent object (the Hosted On Node).
Not Managed – Used to indicate that NNMi does not discover or monitor the interface.
For example, the interface might not be accessible because it is in a private network.
Out of Service – Used to indicate an interface is unavailable because it is out of service or participating in a
. NNMi does not discover or monitor this
Interface.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.
Note: 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
Physical
Address
Layer 2
Connection
The node in which the interface resides. This is the current value in the NNMi database for the Name attribute of the host device. 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.
The interface address at the physical layer, also known as the MAC address. This is the globally unique serial number assigned to each interface at the factory.
Used to indicate whether the selected interface is part of a Layer 2 Connection. If the interface is part of a connection, use this attribute to access information about its Layer 2
Connection and the neighboring device.
Click here for instructions.
1. Navigate to the Layer 2 Connection attribute. Click the select Open.
Lookup icon, and
2. In the Layer 2 Connection form, locate the Interfaces tab.
3. Double-click the row representing the other interface participating in this connection.
4. In the Interface form, locate the Hosted On Node attribute.
5. The Node form contains all known information about the neighboring node.
Interface State Attributes
Attribute Description
Administrative The current Administrative State provided by:
HPE Network Node Manager i Software (10.20)
Page 157 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface State Attributes, continued
Attribute Description
State
Operational
State l
The managing
l l
The managing
(NNMi Advanced)
Set by the device's administrator
This value contributes towards the status calculation for this interface. See the
for more information.
Possible values are:
Up – The interface is ready to pass packets of data.
Down – The interface is not available to pass packets of data.
Testing – The interface is in test mode.
Other – The Administrative State reported is not a recognized value.
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.
The current Operational State provided by: l
The managing
l
The managing
(NNMi Advanced)
This value contributes towards the status calculation for this interface. See the
for more information.
Possible values are:
Up – The interface is operationally up, ready to receive and send network traffic.
Down – The interface is operationally down.
Dormant – Indicates interface is in a "pending” state, waiting for some external event.
Lower Layer Down – Indicates the interface is down due to the state of lower-level interfaces.
HPE Network Node Manager i Software (10.20)
Page 158 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface State Attributes, continued
Attribute Description
State Last
Modified
Notes
Minor Fault – The interface is still functional, but a minor concern was detected.
Check the device, itself, for more details.
Not Present – Indicates that the interface is missing.
Other – The Operational State reported is not a recognized value.
Testing – The interface is in test mode.
Unknown – The Operational State value could not be detected.
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.
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
The date and time when the Administrative State, Operational State, or both were last modified.
Provided for network operators to use for any additional notes required to further explain the interface. Information might include to what service or customer the interface is connected.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your interface table views based on this value. Therefore, you might want to include keywords for this attribute value.
Interface Form: Uplinks Tab (NNMi Advanced)
The Interface Form provides details about the selected interface.
HPE Network Node Manager i Software (10.20)
Page 159 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Tip: The Uplinks tab appears only for those interfaces that represent virtual switches. Use this tab to view the list of physical interfaces associated with that virtual switch. These interfaces are identified using the Virtual Bridge Port capability.
For information about each tab:
Uplinks Table
Attribute Description
Interfaces Table view of all of the interfaces representing the uplink associated with the virtual switch.
Double-click the row representing an interface. The
displays all details about the selected interface.
Interface Form: Virtual Ports Tab (NNMi Advanced)
The
provides details about the selected network interface.
Tip: The Virtual Ports tab appears only for those interfaces that represent virtual switches. Use this tab to view the list of virtual interfaces on the virtual switch that connect to
virtual machine
1 nodes. Virtual
Ports are identified using the Virtual Bridge Port capability.
For information about each tab:
Virtual Ports Table
Attribute Description
Ports Table view of all of the virtual interfaces that connect to a virtual switch.
Use this table to access information about each virtual interface associated with the selected virtual switch.
Double-click the row in the Virtual Ports table. The
displays all details about the selected virtual interface that is acting as a virtual port.
IP Address Form
The IP Address form provides information for the IP address selected. This form is useful for troubleshooting purposes because you can access additional information about the
,
, and
associated with this address.
If your role permits, you can use this form to modify the
for an address (for example, to indicate it will be temporarily out of service) or add
to communicate information about this address to your team.
1
A device that utilizes components from multiple physical devices. Depending on the manufacture's implementation, the virtual machine may be static or dynamic.
HPE Network Node Manager i Software (10.20)
Page 160 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
Basic Attributes
Attribute Description
Address
Prefix
Length
An IP address provided by your NNMi administrator as a discovery seed or an IP address gathered by Spiral Discovery.
The number of significant bits in the subnet prefix associated with this IP address.
For IPv4 addresses, this value is derived from the subnet mask.
Mapped
Address
Status
If static Network Address Translation (NAT) is part of your network management domain, your NNMi administrator can configure NNMi to display the NAT internal IP address (such as private IPv4 address) assigned to the selected external IP address.
Overall status for the current IP address. NNMi follows the ISO standard for status classification. See
"IP Address Form: Status Tab" on page 166 .
Management
Mode
The calculated Management Mode for the address according to the Management Mode
Hierarchy. This value reflects the current management mode of this IP address's parent object (either an Interface or the Hosted On Node). See
Management Mode to an Object" on page 591
.
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: 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 IP address. Possible values are:
Inherited – Used to indicate that the address should inherit the Management Mode from the address's parent object (either the Parent Component interface or the Managed By node).
Not Managed – Used to indicate that you do not plan to manage the address. For example, the address might not be accessible because it is in a private network. NNMi does not discover or monitor these addresses.
Out of Service – Used to indicate the address is unavailable because it is out of service or participating in a
. NNMi does not discover or monitor this address.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.
HPE Network Node Manager i Software (10.20)
Page 161 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
State
Note: 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.
Indicates whether NNMi is communicating with the IP address. Possible values are:
Responding – Indicates that the IP address is being polled and is responding to an
ICMP ping.
Not Responding – Indicates that the IP address is being polled, but is not responding to an ICMP ping.
The following values indicate NNMi could not gather the required data:
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.
Note: NNMi's State Poller determines the State. The current state contributes towards the status calculation for the address. See the
for more information.
State Last
Modified
In Interface
The date and time when the State value was last modified.
Hosted On
Node
In Subnet
MIB-II ipAddrTable value indicating the interface that owns this IP address. Click the
Lookup icon and select Open to display more information about the interface.
node in which the address resides. This is the current value in NNMi’s database for the
Name attribute of the host device. 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.
Subnet on which the IP address resides. NNMi derives this subnet based on the IP address
HPE Network Node Manager i Software (10.20)
Page 162 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Notes and the subnet prefix information. Click the display more information about the IP subnet.
Lookup icon and select Open to
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
Provided for network operators to use for any additional notes required to further explain the
IP address. Information might include whether the address is a backup address. You might also use this attribute to track which geographical group might use the address.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your IP address table views based on this value. Therefore, you might want to include keywords for this attribute value.
IP Address Form: Incidents Tab
Tip: See
for more details about the incident attributes that appear in the incident view's column headings.
The
provides details about the selected IP address.
For information about each tab:
Incidents Table
Description
Table view of the incidents associated with the selected address. 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 address.
Double-click the row representing an incident. The
displays all details about the selected incident.
IP Address Form: Capabilities Tab
The
provides details about the selected IP address.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 163 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
The IP Address Form: Capabilities tab displays a table view of any capabilities added to the IP Address object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about an IP address than is initially stored in the NNMi database.
For example, NNMi uses the capability feature to identify an IPv4
Anycast Rendezvous Point IP Address
1 or IPv6 Anycast address so it is not polled. NNMi assigns the following capability to the address: com.hp.nnm.capability.address.anycast.
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Capabilities Table
Attribute Description
Capability Table of all of the capabilities associated with the selected IP Address. Use this table to access information about each Capability.
Double-click the row representing a Capability. The
"IP Address Capability Form" on the next page
displays all details about the selected Capability.
For more information, see
"IP Address Capabilities Provided by NNMi" below .
IP Address Capabilities Provided by NNMi
The
"IP Address Form: Capabilities Tab" on the previous page
displays a table of any capabilities added to a particular IP Address object. Capabilities enable NNMi and application programmers to provide more information about an IP address than what is initially stored in the NNMi database.
External applications can also add capabilities.
KEY: com.hp.<product>.capability.<content>.<vendor/org>.<MIB/feature>
Any Capability provided by NNMi begins with the prefix com.hp.nnm.capability.
<product> = Either NNMi or the NNM iSPI providing this capability.
<content> = chassis, card, ipaddr (address), iface (interface), lag (
Link Aggregation
2
Aggregation
3 or
Split Link
interface), node, rrp (Router Redundancy), or metric (Node Sensor or Physical Sensor).
<vendor/org> = Standards organization or vendor defining the MIB or feature associated with the capability.
<MIB/feature> = What this capability measures.
1
Rendezvous Point addresses are loopback addresses used for routers in multi-cast network configurations.
2
Protocols 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).
3
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 164 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Note: The following table shows a few examples of the Capabilities provided by NNMi.
IP Address Capability Attribute Values
Unique Key Capability Description
com.hp.nnm.capability.address.loopback LOOPBACK Used to identify a
loopback address
1
.
com.hp.nnm.capability.address.anycast
ANYCAST Used to identify an address that is either of the following: l
IPv4
Anycast Rendezvous Point
IP Address
2 that are loopback addresses used for routers in multi-cast network configurations. These duplicate
IP addresses are excluded from monitoring.
l
(NNMi Advanced) IPv6 Anycast address.
com.hp.nnm.capability.address.nat
NAT
(network address translation)
Used to map one address space into another (network masquerading to protect private networks).
IP Address Capability Form
This form describes a capability added to the IP address object by NNMi or an external application.
Capabilities enable NNMi and application programmers to provide more information about an IP address than what is initially stored in the NNMi database.
For example, NNMi uses the capability feature to identify an IPv4
Anycast Rendezvous Point IP Address
3 or IPv6 Anycast address. To exclude these addresses from polling, NNMi assigns following capability to the address: com.hp.nnm.capability.ipaddr.anycast
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
1
The address associated with the loopback interface. The loopback interface is a virtual interface on a device that provides a route for internal communication. Many vendors provide a specially configured loopback for management purposes. Exact details of how loopbacks are configured varies by vendor and model. See each device's documentation for details. NNMi identifies these loopback addresses by using ifType Number 24, softwareloopback from the IANA ifType-MIB.
2
3
Rendezvous Point addresses are loopback addresses used for routers in multi-cast network configurations.
Rendezvous Point addresses are loopback addresses used for routers in multi-cast network configurations.
HPE Network Node Manager i Software (10.20)
Page 165 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
IP Address Capability Attributes
Attribute Description
Capability Label used to identify the Capability that was added to the IP address object.
"IP Address Form: Capabilities Tab" on page 163
shows a list of all available Capabilities for that IP address.
For more information, see
"IP Address Capabilities Provided by NNMi" on page 164
.
Unique
Key
Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.
For more information, see
"IP Address Capabilities Provided by NNMi" on page 164
.
IP Address Form: Status Tab
The
provides details about the selected IP address .
For information about each tab:
Status of this IP Address
Attribute Description
Status Overall status for the current IP address. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
IP address status is derived from ICMP ping results, as well as any conclusions. For information about how the current status was determined, see the
Conclusions Tab" on the next page
. Status reflects the most serious outstanding conclusion.
See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views.
Status
Last
Modified
Date and time indicating when the status was last set.
HPE Network Node Manager i Software (10.20)
Page 166 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status History Table
Attribute
Description
Status
History
List of up to the last 30 changes in status for the selected IP Address. This view is useful for obtaining a summary of the IP address status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
IP Address Form: Conclusions Tab
The
provides details about the selected IP address .
All relevant conclusions are shown in the table on this tab. The most severe Status in the current group of conclusions becomes the overall IP Address status. Some IP Address conclusions propagate to other object types:
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses of the IP address that contributed to the current overall Status of the selected IP address. Status is set by the Causal Engine.
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 for the current node's IP address that led up to the address' most current Status.
The Status value is correlated based on the most critical 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 an
IP Address object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
AddressNotResponding The address is not responding to
ICMP ping.
Normal Status Conclusions
Status Incident?
Critical Y
HPE Network Node Manager i Software (10.20)
Page 167 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
AddressResponding The address responds to ICMP ping.
Status Incident?
Normal N
IP Address Form: Registration Tab
The
provides details about the selected IP address .
For information about each tab:
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.
Note: 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: l
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.
l
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.
SNMP Agent Form
The SNMP Agent form provides details about the SNMP Agent assigned to the currently selected node. This form is useful when you want to view more details about the SNMP Agent, including the agent's status. You can also use the form to determine all of the attributes in the NNMi database associated with the SNMP
Agent.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 168 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes
Attribute Description
Name Name used to identify the SNMP agent. This name is the hostname of the node (as stored in the NNMi database). NNMi chooses the hostname of the parent node according to the criteria specified by your NNMi administrator.
NNMi follows a set of rules to dynamically generate the value stored in the NNMi database for each Node's Hostname.
Click here for details.
l
If the Node supports SNMP, NNMi requests the Hostname using the IP Address of the associated SNMP agent (the Management Address attribute value on the Node form).
When the NNMi administrator chooses Enable SNMP Address Rediscovery in the Communication Configuration: l
If the SNMP Agent does not respond, NNMi checks for another Management
Address to request the Hostname, and the Hostname could change.
l
If the SNMP Agent associated with the node changes, the Management Address and Hostname could change.
When the NNMi administrator disables Enable SNMP Address Rediscovery in the Communication Configuration, when the current management address (SNMP agent) becomes unreachable, NNMi does not check for other potential management addresses.
l
If the Node does not support SNMP, no Management Address is available. NNMi requests a Hostname starting with the lowest IP Address associated with the node (a
Discovery Seed value or an IP address value gathered from a neighboring device).
NNMi uses the first Hostname provided. The Hostname might change during a future discovery cycle.
Note: NNMi administrators can use NNMi property file settings to change the way
NNMi determines Hostname values: l l nms-topology.properties file settings:
If DNS is the source of the Node's Hostname, there are three choices. By default
NNMi uses the exact Hostname from your network configuration. It is possible to change NNMi behavior to convert Hostnames to all uppercase or all lowercase.
See the "Modifying NNMi Normalization Properties" section of the HPE Network
Node Manager i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
nms-disco.properties file settings:
The Hostname is either requested from the Node's lowest loopback interface IP address that resolves to a Hostname or requested from the Node's designated
Management Address (SNMP agent address). With either choice, when no IP address resolves to a Hostname, the IP address itself becomes the Hostname.
See the "Maintaining NNMi" chapter of the HPE Network Node Manager i
Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
HPE Network Node Manager i Software (10.20)
Page 169 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
*
Mode NNMi administrators only.
Click here for more information.
Enables you to specify how NNMi determines the values of the editable Attributes within this instance of the SNMP Agent form.
Note: When the node is first discovered, the SNMP Agent's Mode = Auto by default.
NNMi discovers and monitors Nodes using the Communication Configuration settings. See Configuring Communication Protocol for more information.
SNMP Agent Settings Mode Options
Option Description
Auto
NNMi uses the current appropriate Communication Configuration settings to determine the values of the Attributes within this instance of the SNMP Agent form. See Configuring Communication Protocol for more information.
Locked
The NNMi Administrator controls the values of the editable Attributes within this instance of the SNMP Agent form for discovery and monitoring.
Any future updates to those configuration settings must be established within this instance of the SNMP Agent form.
Tip: You can also use nnmcomunication.ovpl
to set the Mode and view this SNMP
Agent's configuration settings.
Management
Address
IP address NNMi uses to communicate with this SNMP agent.
Note: As an NNMi administrator, you can over-ride this setting and specify the management address on a per-node basis using the
. The
IP address you enter must be a valid IP address for the associated Node. Also see the
attribute description.
Tip: If you are an NNMi administrator, you can also use nnmcomunication.ovpl
to change the Management Address value and to view the SNMP Agent settings.
The NNMi administrator can specify an address or NNMi can dynamically select one.
Click here for details.
Note: (NNMi Advanced) The NNMi administrator specifies whether NNMi prefers
IPv4 addresses, IPv6 addresses, or dual-stack (both) when selecting the
Management Address. See Configure Default SNMP, Management Address, and
ICMP Settings .
HPE Network Node Manager i Software (10.20)
Page 170 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
1. NNMi ignores the following addresses when determining which Management
Address is most appropriate: l
Any address of an administratively-down interface.
l
Any address that is virtual (for example,
VRRP
1
).
l
Any IPv4
Anycast Rendezvous Point IP Address
2 or IPv6 Anycast address.
l
Any address in the reserved loopback network range. IPv4 uses 127/24
( 127.*.*.*) and IPv6 uses ::1.
l
Any
IPv6 link-local address
3
.
2. If the NNMi Administrator chooses Enable SNMP Address Rediscovery
in
Communication Configuration, NNMi prefers the last-known Management Address
(if any).
3. If the Management Address does not respond and the NNMi Administrator specifies
Enable SNMP Address Rediscovery in Communication Configuration, NNMi uses the Communication Configuration settings for Management Address Selection. The
NNMi Administrator chooses the order in which NNMi checks the following: l
Seed IP / Management IP - If the NNMi Administrator configures a Seed, NNMi uses the Seed address (either a specified IP address or the DNS address associated with a specified hostname) only during initial Discovery. NNMi then requests the current Management Address (the address from which the node's
SNMP Agent responds) and uses that IP address for all communication after initial discovery.
l
Lowest Loopback - If a node supports multiple
loopback address
4
, NNMi queries each loopback addresses, starting with the lowest number. NNMi uses the loopback address with the lowest number from which the SNMP agent responds (for example, 10.16.42.197 is a lower number than 10.16.197.42).
1
Virtual Router Redundancy Protocol
2
Rendezvous Point addresses are loopback addresses used for routers in multi-cast network configurations.
3
A non-routable IPv6 unicast address only used for communication with other nodes on the same link (LAN or
VLAN). Link local addresses cannot be used for communication that must be forwarded through a router. IPv6 auto-configuration automatically assigns a unique link local address in the fe80::/10 address space to each
IPv6-enabled interface on a system.
4
The address associated with the loopback interface. The loopback interface is a virtual interface on a device that provides a route for internal communication. Many vendors provide a specially configured loopback for management purposes. Exact details of how loopbacks are configured varies by vendor and model. See each device's documentation for details. NNMi identifies these loopback addresses by using ifType Number 24, softwareloopback from the IANA ifType-MIB.
HPE Network Node Manager i Software (10.20)
Page 171 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
l
Highest Loopback - If a node supports multiple
loopback address
1
, NNMi queries each loopback addresses, starting with the highest number. NNMi uses the loopback address with the highest number from which the SNMP agent responds.
l
Interface Matching - The NNMi Administrator chooses which interface MIB variable NNMi queries to detect changes. NNMi can use the following MIB-II attribute values: ifIndex, ifName, ifDescr, ifAlias, or a combination of these
( ifName or ifDescr, ifName or ifDescr or ifAlias). NNMi searches current database entries for information about the interface in this order: index, alias, name, and description. If multiple IP addresses are associated with the interface,
NNMi starts by querying the lowest IP address and selects the first responding address in ascending order.
4. If no response, NNMi queries any remaining IP addresses in the node's IP address inventory, starting with the lowest number. NNMi uses the address with the lowest number from which the SNMP agent responds.
5. If no response, NNMi checks for any Mapped Address configured for one of the currently known addresses (see the Mapped Address column in the Custom
IP Addresses view).
Note: The address represents a static Network Address Translation (NAT) pair's external IP address from the internal/external IP address pair. NNMi
Administrators configure these pairs using the Overlapping IP Address Mapping form. NNMi uses this list of addresses starting with IPv4 from low to high, then
IPv6 from low to high.
6. If no response, NNMi might be configured to repeat the sequence using SNMPv1,
SNMPv2c, or SNMPv3 in the order specified by the NNMi administrator
(Communication Configurations SNMP Minimum Security Level settings).
7. When all else fails, NNMi retains the last known Management Address (if any) and automatically changes the State of that SNMP Agent object to Critical.
This process is repeated during each Spiral Discovery cycle, and the Management
Address can change. For example, NNMi's inventory of addresses for the node expands, or the current Management Address does not respond to SNMP queries due to network problems or node reconfiguration. The NNMi administrator can prevent changes to the management address using the Communication Configurations Enable SNMP Address
Rediscovery
(disabled) or Preferred Management Address setting.
1
The address associated with the loopback interface. The loopback interface is a virtual interface on a device that provides a route for internal communication. Many vendors provide a specially configured loopback for management purposes. Exact details of how loopbacks are configured varies by vendor and model. See each device's documentation for details. NNMi identifies these loopback addresses by using ifType Number 24, softwareloopback from the IANA ifType-MIB.
HPE Network Node Manager i Software (10.20)
Page 172 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Protocol
Version
Read
Community
String
SNMP Agent
Enabled
Version of the SNMP protocol in use. NNMi supports versions SNMPv1, SNMPv2c, and
SNMPv3.
The read community string value that was discovered for the selected SNMP agent.
Note the following: l
The read community string is an SNMPv1 or SNMPv2c password.
l
The actual read community string is only visible if you are assigned to the NNMi administrator role.
l l
If you are an NNMi administrator, you can change this value for the selected
SNMP Agent and its associated node.
The NNMi administrator can also choose to make this value viewable (read only) to
Level 2 Operators. If you are an NNMi administrator, see the "Maintaining NNMi" chapter of the HPE Network Node Manager i Software Deployment Reference for more information.
Indicates whether this SNMP agent is set up for SNMP communication in your network environment.
Note: When an agent is Disabled, any data previously reported by that agent is preserved in the NNMi database. Data reported by an Enabled agent is updated as new data is received.
UDP Port
Get-Bulk
Enabled
SNMP Proxy
Address
User Datagram Protocol port configuration for this SNMP agent.
Default 161. Port NNMi is instructed to use when contacting this SNMP agent to collect
SNMP data. Both the Discovery Process and the State Poller Service use this setting.
Applies only to SNMPv2 or higher. If you have devices in your network environment that have trouble responding to GetBulk commands, you can instruct NNMi to use Get or
GetNext instead of GetBulk.
If enabled, NNMi uses the SNMPv2c
GetBulk command to gather information from devices in your network environment.
If disabled, NNMi uses the SNMP Get or GetNext command to gather information from devices in your network environment (requesting responses for one SNMP OID at a time).
Prerequisite: The NNMi administrator must specify one or more SNMP Proxy Servers in the NNMi Communication Configuration settings.
The IP address of the server that is acting as the SNMP Proxy Server for this
SNMP agent. Your NNMi administrator might have set up one or more SNMP Proxy
Servers to enable communication with nodes that otherwise might be unreachable. For example, when a node to be managed is behind a firewall. The SNMP Proxy Server enables NNMi to manage these nodes in the same way as nodes that provide
SNMP access directly.
HPE Network Node Manager i Software (10.20)
Page 173 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
SNMP Proxy
Port
Prerequisite: The NNMi administrator must specify one or more SNMP Proxy Servers in the NNMi Communication Configuration settings.
The port number on the server that is acting as the SNMP Proxy Server for this
SNMP Agent. See SNMP Proxy Address (previous attribute) for more information.
SNMP
Timeout
(Seconds:Milliseconds) Time that NNMi waits for a response to an SNMP query before reissuing the request.
SNMP Retries Maximum number of retries that NNMi issues for an SNMP query before determining the query result to be "unresponsive". Zero means no retries.
SNMP Agent State Attributes
Attribute Description
Agent SNMP
State
Management
Address
ICMP State
Indicates whether the SNMP agent is available and how NNMi is using SNMP to interact with this SNMP agent. Possible values are:
Normal – Indicates that the agent responds to requests requiring authentication and login.
The following values indicate NNMi could not gather the required data:
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.
Not Responding – Indicates that the SNMP agent does not respond to requests requiring authentication and login.
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. The current state contributes towards the status calculation for the agent. See
"SNMP Agent Form: Status Tab" on page 176
for more information.
Indicates whether NMi is communicating with the management address. Possible values are:
Responding – Indicates that the management address is being polled and is responding to an ICMP ping.
HPE Network Node Manager i Software (10.20)
Page 174 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
SNMP Agent State Attributes, continued
Attribute Description
Not Responding – Indicates that the management address is being polled, but is not responding to an ICMP ping.
Not Polled – Indicates that this attribute is intentionally not polled, based on current
Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of
Service.
The following values indicate NNMi encountered trouble while trying to gather the required data:
No Polling Policy – No polling policy exists in Monitoring Configuration settings for this monitored attribute.
Unavailable – Unable to determine the State. For example, the ICMP poll returned a value outside the range of possible values or returned a null value.
Unset – Currently not used by NNMi.
Note: NNMi's current Monitoring configuration settings must provide ICMP Fault
Monitoring: Enable Management Address Polling ( default or node setting).
Management
Address
ICMP
Response
Time
State is determined by the State Poller Service. The current state contributes towards the status calculation for the SNMP Agent. See the
"SNMP Agent Form: Status Tab" on the next page
for more information.
Indicates the State of the ICMP response time between the management server and the selected node. Possible values are:
Nominal – Indicates the ICMP response time was between 0 and the configured High
Value.
Not Polled – Indicates that this attribute is intentionally not polled, based on current
Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of
Service.
If thresholds are set, the following value is also possible:
High – Indicates a higher than configured ICMP response time between the management server and the selected node.
The following values indicate NNMi encountered trouble while trying to gather the required data:
No Polling Policy – No polling policy exists in Monitoring Configuration settings for this monitored attribute.
Unavailable – Unable to determine the State. For example, the ICMP poll returned a value outside the range of possible values or returned a null value.
HPE Network Node Manager i Software (10.20)
Page 175 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
SNMP Agent State Attributes, continued
Attribute Description
Note: NNMi's current Monitoring configuration settings must provide ICMP Fault
Monitoring: Enable Management Address Polling ( default or node setting).
Management
Address
ICMP
Response
Time Baseline
Indicates the ICMP response time between the management server and the selected node is abnormal based on the computed baseline. Possible values are
Not Polled – Indicates that this attribute is intentionally not polled, based on current
Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of
Service.
Additional possible values include:
Requires HPE Network Node Manager iSPI Performance for Metrics Software (NNM iSPI Performance for Metrics) -click here for more information .
Normal Range – Indicates State Poller collected values within the normal range when compared to the baseline data collected for the management address response time.
If baseline thresholds are set, the following value is also possible:
Abnormal Range – Indicates State Poller has collected values outside the normal range when compared to the baseline data collected for the management address response time.
Note: NNMi's current Monitoring configuration settings must provide ICMP Fault
Monitoring: Enable Management Address Polling ( default or node setting).
State Last
Modified
Hosted On
Node
The date and time of the most recent update of any of the values in the SNMP Agent State attributes (in this table).
Node on which the SNMP Agent resides. This is the current value in NNMi’s database for the Name attribute of the host device. 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.
SNMP Agent Form: Status Tab
The
provides details about the SNMP Agent of the selected node or interface.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 176 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status
Attribute Description
Status Overall status for the current SNMP agent. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
For information about how the current status was determined, see
Conclusions Tab" below . Status reflects the most serious outstanding conclusion.
Date and time indicating when the Status was last set.
Status
Last
Modified
Status History Table
Attribute
Description
Status
History
List of the last 30 changes in the status for the SNMP agent. This view is useful for obtaining a summary of the SNMP agent status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
SNMP Agent Form: Conclusions Tab
The
provides details about the SNMP Agent of the selected node or interface.
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
The dynamically generated list of summary statuses for the SNMP agent that contributed to the current overall Status of the selected SNMP agent. Status is set by the Causal
HPE Network Node Manager i Software (10.20)
Page 177 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusions Engine.
Each Conclusion listed is still outstanding and applies to the current overall Status.
This view is useful for obtaining a quick summary of how the Status of SNMP Agent in the node contributes to the current Status of the SNMP Agent.
The Status value is correlated based on the most critical 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 an SNMP
Agent object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
SNMPAgentNotResponding The SNMP agent is not responding to SNMP queries on the selected node.
Status Incident?
Critical Y
Minor Status Conclusions
Conclusion Description
SNMPAgentPingNotResponding The address associated with this SNMP Agent is not responding to ping.
Status Incident?
Minor N
Warning Status Conclusions
Conclusion Description Status Incident?
ManagementAddress
ICMPResponseTimeAbnormal
Indicates there is an abnormal
Internet Control Message
Protocol (ICMP) response time from the NNMi management server to the selected node.
ICMP messages are typically used for diagnostic or routing purposes for determining whether a host or router could
Warning Y
HPE Network Node Manager i Software (10.20)
Page 178 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
ManagementAddress
ICMPResponseTimeHigh
Description
not be reached.
The incident is generated when NNMi detects a higher or lower value than the baseline ICMP response time between the NNMi management server and the selected node.
Status Incident?
Indicates a high Internet
Control Message Protocol
(ICMP) response time from the management server to the selected node.
ICMP messages are typically used for diagnostic or routing purposes for determining whether a host or router could not be reached.
The incident is generated when NNMi detects a higher than configured ICMP response time between the
NNMi management server and the selected node.
Warning Y
Normal Status Conclusions
Conclusion Description
ManagementAddress
ICMPResponseTimeNominal
Indicates that the Internet
Control Message Protocol
(ICMP) response time from the management server to the selected node is within the threshold range set by the administrator.
ICMP messages are typically used for diagnostic or routing purposes for determining whether a host or router could not be reached.
Status Incident?
Normal N
HPE Network Node Manager i Software (10.20)
Page 179 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
ManagementAddress
ICMPResponseTimeNormal
Description
Indicates l Internet Control
Message Protocol (ICMP) response time from the NNMi management server to the selected node is within the baseline set by the administrator.
ICMP messages are typically used for diagnostic or routing purposes for determining whether a host or router could not be reached.
SNMPAgentPingResponding The address associated with this SNMP Agent is responding to ping.
SNMPAgentResponding The SNMP Agent is responding to SNMP requests.
Status Incident?
Normal N
Normal N
Normal N
SNMP Agent Form: Incidents Tab
The
provides details about the SNMP Agent of the selected node or interface.
For information about each tab:
Incidents Table
Attribute Description
Associated
Incidents
Table view of the incidents associated with the selected SNMP agent. 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 SNMP agent.
Double-click the row representing an incident. The
displays all details about the selected incident.
SNMP Agent Form: Registration Tab
The
provides details about the SNMP Agent of the selected node or interface.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 180 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
Note: 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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
Web Agent Form (NNMi Advanced)
The Web Agent form provides details about the
Web Agent
1 assigned to the currently selected node. This form is useful when you want to view more details about the Web Agent, including the agent's status. You can also use the form to determine all of the attributes in the NNMi database associated with the Web Agent.
For information about each tab:
Basic Attributes
Attribute Description
Name The type of the Web Agent. For example, VMware vSphere indicates the agent is runs on a
VMware ESXi hypervisor.
Hostname The FQDN hostname of the server.
For example, in a VMware environment, the VMware ESXi server's hostname.
Mode NNMi administrators only.
Click here for more information.
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 181 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Enables you to specify how NNMi determines the values of the editable Attributes within this instance of the Web Agent form.
Note: When the node is first discovered, the Web Agent's Mode = Auto by default. NNMi discovers and monitors Nodes using the Communication Configuration settings. See
Configuring Communication Protocol for more information.
Web Agent Settings Mode Options
Option Description
Auto
NNMi uses the current appropriate Communication Configuration settings to determine the values of the Attributes within this instance of the Web Agent form.
See Configuring Communication Protocol for more information.
Locked
The NNMi Administrator controls the values of the editable Attributes within this instance of the Web Agent form for discovery and monitoring.
Any future updates to those configuration settings must be established within this instance of the Web Agent form.
Tip: You can also use nnmcomunication.ovpl
to set the Mode and view this Web Agent's configuration settings.
Agent
Enabled
Indicates whether the agent is enabled. The Web Agent is enabled when this check box is selected.
Note: When an agent is Disabled, any data previously reported by that agent is preserved in the NNMi database. Data reported by an Enabled agent is updated as new data is received.
Scheme
Port
Timeout
NNMi administrators only.
Click here for more information.
To disable the Web Agent, clear the check box.
Indicates the mode of communication between NNMi and the Web Agent. Default scheme is
HTTPS.
Port configuration for this Web Agent.
Default 80.
(Seconds:Milliseconds) Time that NNMi waits for a response from the device to a Web Agent query before reissuing the request.
Last
Modified
HPE Network Node Manager i Software (10.20)
Page 182 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Last
Modified
By
Web Agent State Attributes
Attribute Description
Web
Agent
State
Indicates whether the Web Agent is available and how NNMi is interacting with this Web agent.
Possible values are:
Normal – Indicates that the agent responds to requests requiring authentication and login.
The following values indicate NNMi could not gather the required data:
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.
Not Responding – Indicates that the Web Agent does not respond to requests requiring authentication and login.
Unavailable - The agent responded with a value outside the range of possible values or returned a null value.
State
Last
Modified
Unset – Currently not used by NNMi.
State is determined by the State Poller Service. The current state contributes towards the status calculation for the agent. See
"Web Agent Form: Status Tab (NNMi Advanced)" on page
for more information.
The date and time of the most recent update of any of the values in the Web Agent State attributes (in this table).
Hosted
On Node
Device on which the Web Agent resides.
HPE Network Node Manager i Software (10.20)
Page 183 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Web Agent Form: Device Credentials Tab (NNMi
Advanced)
The
"Web Agent Form (NNMi Advanced)" on page 181
provides details about the
Web Agent
1 of the selected node or interface.
For information about each tab:
Device Credentials Attributes
Attribute Description
User Name
Password
The user name with which NNMi connects to the Web Agent.
Password of the above user.
Web Agent Form: Managed Nodes Tab (NNMi
Advanced)
The Managed Node tab lists all the nodes currently managed by the
Web Agent
2
, including the hypervisor that hosts the Web Agent and the virtual machines residing on that hypervisor.
For information about each tab:
Managed Nodes Table
Attribute Description
Status
Device Category
Name
Status of the node.
Category of the device.
Name of the node.
Hostname FQDN of the node.
Management Address IP address of the node.
System Location Location of the node.
Device Profile
Agent Enabled
Type of device.
Indicates whether a Web Agent is enabled on this node.
Status Last Modified Last time of update.
Notes
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 184 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Web Agent Form: Incidents Tab (NNMi Advanced)
The Web Agent Form: Incidents Tab shows all the open incidents originating from the hypervisor that hosts the
Web Agent
1
.
For information about each tab:
Incidents Table
Attribute Description
Associated
Incidents
Table view of the incidents associated with the selected Web agent. 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 Web Agent.
Double-click the row representing an incident. The
displays all details about the selected incident.
Web Agent Form: Status Tab (NNMi Advanced)
The
"Web Agent Form (NNMi Advanced)" on page 181
provides details about the
Web Agent
2
.
For information about each tab:
Status
Attribute Description
Status Overall status for the current Web Agent. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
For information about how the current status was determined, see
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
2
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 185 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status, continued
Attribute Description
Status
Last
Modified
Conclusions Tab (NNMi Advanced)" on the next page . Status reflects the most serious
outstanding conclusion.
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 Web Agent. This view is useful for obtaining a summary of the Web Agent status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
Web Agent Form: Conclusions Tab (NNMi
Advanced)
The
"Web Agent Form (NNMi Advanced)" on page 181
provides details about the
Web Agent
1 of the selected node or interface.
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses for the Web agent that contributed to the current overall Status of the selected Web agent. Status is set by the Causal Engine.
Each Conclusion listed is still outstanding and applies to the current overall Status.
This view is useful for obtaining a quick summary of how the Status of Web Agent in the node contributes to the current Status of the Web Agent.
The Status value is correlated based on the most critical 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 an Web
Agent object.
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 186 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description Status Incident?
WebAgentNotResponding The Web agent is not responding to web queries requiring authentication and login on the selected node.
Critical Y
Normal Status Conclusions
Conclusion Description
WebAgentResponding The Web Agent is responding to web service requests that require authentication and login.
Status
Normal
Incident?
N
Web Agent Form: Registration Tab (NNMi Advanced)
The
"Web Agent Form (NNMi Advanced)" on page 181
provides details about the
Web Agent
1 of the selected node or interface.
For information about each tab:
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.
Note: 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: l
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
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 187 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Registration Attributes, continued
Attribute Description
Completed.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
Web Agent Form: Trusted Certificates Tab (NNMi
Advanced)
Note: This tab is for administrators only. The tab does not show any information if you do not log on as an
NNMi administrator.
The Web Agent Form: Trusted Certificates tab shows all the trusted certificates that are uploaded to the
NNMi management server to facilitate the HTTPS communication between the
Web Agent
1 and NNMi.
For information about each tab:
Trusted Certificate Attributes
Attribute Description
Subject DN The Subject Distinguished Name (Subject DN) of the certificate.
Valid From The Valid From and Valid To values together define the validity period of the certificate.
Valid To
Stored Agent Certificate Form (NNMi Advanced)
Note: This form is for administrators only. You cannot open this form if you do not log on as an NNMi administrator.
The Stored Agent Certificate form shows the following details of the selected trusted certificate that is associated with the Web Agent:
1
The Web Agent represents a management service running on a device and contains the settings NNMi uses to communicate with the device.
HPE Network Node Manager i Software (10.20)
Page 188 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l l
Subject DN
Valid From l
Valid To l
CA l l
Issuer DN
UUID l
Serial Number l
Finger Print
Basic Attributes: Stored Agent Certificate
Attribute Description
Subject DN
Valid From
Valid To
The Subject Distinguished Name (Subject DN) of the certificate.
The Valid From and Valid To values together define the validity period of the certificate.
CA
Issuer DN
Indicates whether the certificate is issued by a certificate authority.
Indicates the name of the issuer of the certificate
UUID Indicates the UUID of the certificate.
Serial Number Indicates the serial number of the certificate.
Finger Print Shows the finger print associated with the certificate.
IP Subnet Form
The IP Subnet form provides details about the selected subnet. Each IP Subnet represents an IP Subnet within a particular Tenant (that IPv4 Subnet definition independently applies to each Tenant).
If your role permits, you can add notes to communicate information about this subnet to your team.
For information about each tab:
Basic Attributes
Attribute Description
Name
Prefix
Prefix
Length
Tenant
Subnet in your network. This value is determined by the discovery process (calculated from IP
Addresses and the subnet prefix information).
The value of the prefix for the current subnet (also known as the subnet address).
The number of significant bits in the subnet prefix. This value is used to determine the size of the subnet.
Tenants enable NNMi administrators to partition a network across multiple customers. The
NNMi administrator controls the Tenant assignment for each Node.
HPE Network Node Manager i Software (10.20)
Page 189 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Notes
A Tenant is the top-level organization to which a Node belongs.
Devices that belong to the Default Tenant can have Layer 2 Connections to any device in any
Tenant. Devices within any Tenant other than Default Tenant can have Layer 2 Connections
only to devices within the same Tenant or the Default Tenant.
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
Provided for network operators to use for any additional notes required to further explain the subnet. Information might include its use; for example, point to point for dialup. You might also use this attribute to track which geographical group might use the subnet.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your subnet table views based on this value. Therefore, you might want to include keywords for this attribute value.
IP Subnet Form: IP Addresses Tab
The
"IP Subnet Form" on the previous page
provides details about the selected subnet.
For information about each tab:
IP Addresses Table
Attribute Description
IP
Addresses
Table view of the IP addresses associated with the selected subnet. You can use this table to determine the state, address, and interface, and parent node for each address associated with the selected subnet.
Double-click the row representing an IP address. The
displays all details about the selected IP address.
IP Subnet Form: Registration Tab
The
"IP Subnet Form" on the previous page
provides details about the subnet selected.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 190 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
Note: 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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
VLAN Form
The VLAN form provides details about the selected virtual local area network, and lists all ports known to participate in this VLAN.
Note the following: l
A trunk port can participate in multiple VLANs.
l
Only the objects to which you have access are visible from the form.
For information about each tab:
(NNMi Advanced - Global Network Management feature) There might be slight differences between the VLAN information shown on Regional Managers and Global Managers, because the VLAN calculations use
data.
The following attributes always appear on the VLAN form, whether you access that form from the VLAN view or from a VLAN Port form's tab.
Basic Attributes
Attribute Description
Global VLAN connections are determined by a common VLAN Id. The name assigned to that
HPE Network Node Manager i Software (10.20)
Page 191 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
VLAN
Name
VLAN can be designated by each participating Node\Interface's configuration settings for that
VLAN Id. Therefore, NNMi chooses a VLAN name for this value (from potentially many names for the same VLAN Id):
Global VLAN Name = NNMi uses the lowest sort-order name from all available names designated by member Nodes.
Tip: If you see an attribute named Local VLAN Name = the VLAN name assigned by the configuration settings on the currently selected Node\Interface.
VLAN Id The identification value for the current VLAN. This value is taken directly from the MIB file provided by the Vendor.
The following attributes display only when displaying information about a row in the VLAN view.
VLAN Statistics Attributes
Attribute Description
Member
Node
[Interface] hostname[Interface Name]
NNMi selects a representative Member Node and Member Interface for the current VLAN.
These members help to distinguish VLANs that use the same identification number.
NNMi selects the Member Node using the following criteria: l l
The node is a member of the VLAN.
The node has the lexicographically ordered first node hostname.
l
The User Group to Security Group mapping enables the user to view the node.
NNMi selects the Member Interface using the following criteria: l
The interface must be on the Member Node.
l l
The interface is a member of the VLAN.
The interface has the lexicographically ordered first interface name.
l
The User Group to Security Group mapping enables the user to view the node to which the interface belongs.
Member
Node Count
Specifies the number of nodes that belong to the current VLAN.
Related Topics:
"VLANs View (Inventory)" on page 44
HPE Network Node Manager i Software (10.20)
Page 192 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
VLAN Form: Ports Tab
Note: A trunk port can participate in multiple VLANs.
The
provides details about the selected VLAN.
For information about each tab:
Ports Associated with this VLAN
Attribute Description
Ports Table view of the ports associated with the selected VLAN. Use this table to access information about each port associated with the selected VLAN across all member devices.
Double-click the row representing a Port. The
displays all details about the selected Port.
Related Topics:
"VLANs View (Inventory)" on page 44
Chassis Form
The Chassis form provides details about the Chassis you selected on the Node form or Inventory:
For information about each tab:
Basic Attributes
Attribute Description
Name The name of the chassis. Sometimes it’s the descriptive string used by the network administrator to name the chassis. For example, C2950T, H3C S7503E, and Unit #2
S9505E.
If the Name value is null, NNMi uses the Component Identifier value (see
).
Type The type of Physical Component for this object: Chassis.
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).
Status
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
Overall status for the current chassis. NNMi follows the ISO standard for status
HPE Network Node Manager i Software (10.20)
Page 193 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
classification. See the
"Chassis Form: Status Tab" on page 206
for more information.
Possible values are:
Normal
Warning
Minor
Major
Critical
Unknown
No Status
Chassis status is derived from polling results for
and the most serious outstanding conclusion. See the
"Chassis Form: Conclusions Tab" on page 208
for information about how the current status was determined. See
for more information about possible status values.
Note: The icons are displayed only in table views.
Management
Mode
The calculated Management Mode for the chassis according to the Management Mode
Hierarchy. This value reflects the current management mode of this chassis's parent object
(either the Parent Component chassis or the Managed By node). See
"How NNMi Assigns the Management Mode to an Object" on page 591
.
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: 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 chassis. Possible values are:
Inherited – Used to indicate that the chassis should inherit the Management Mode from the chassis's parent object (either the Parent Component chassis or the Managed By node).
Not Managed – Used to indicate that NNMi does not discover or monitor the chassis.
Out of Service – Used to indicate the chassis is unavailable because it is out of service
HPE Network Node Manager i Software (10.20)
Page 194 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
or participating in a
. NNMi does not discover or monitor this
Chassis.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.
Note: 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.
Parent
Component
If this chassis is plugged into another chassis, the Name of that chassis is listed here.
Redundancy
Group
Indicates whether this chassis participates in a group of chassis that provide redundancy protection against chassis failure.
Physical Component State Attributes
Attribute Description
Administrative
State
Either the current chassis Administrative State value. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Administrative State contributes towards the status calculation for this chassis. See the
"Chassis Form: Status Tab" on page 206
for more information.
Note: If the chassis's SNMP agent supports only the
, no state or status information is available. NNMi sets this state to No Polling Policy and the chassis status to No Status. If you look on the parent
, you will see the com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Up – The SNMP agent responded with a chassis administrative status value of Up.
Down – The SNMP agent responded with a chassis administrative status value of
Down.
Other – The SNMP agent responded with a value for chassis administrative status that is not recognized.
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.
HPE Network Node Manager i Software (10.20)
Page 195 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
Operational
State
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.
The current chassis Operational State value. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Operational State contributes towards the status calculation for this chassis. See the
"Chassis Form: Status Tab" on page 206
for more information.
Note: If the chassis's SNMP agent supports only the
, no state or status information is available. NNMi sets this state to No Polling Policy and the chassis status to No Status. If you look on the parent
, you will see the com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Up – The SNMP agent responded that the chassis is operationally up, ready to receive and send network traffic.
Disabled – The chassis's Administrative State is set to Down.
Down – The SNMP agent responded that the chassis is operationally down.
Dormant – Indicates the chassis is in a "pending” state, waiting for some external event.
Minor Fault – Indicates that the chassis or one of its hardware components is experiencing a partial failure.
Not Present – Indicates that the chassis module is not installed or is missing.
Other – The SNMP agent responded with a value for chassis operational status that is not recognized.
Testing – The SNMP agent responded that the chassis is in test mode.
Transient – Indicates the chassis is in a transient state. For example, rebooting.
Unknown – The SNMP agent responded with a chassis operational status value of
HPE Network Node Manager i Software (10.20)
Page 196 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
unknown.
The following values indicate NNMi could not gather the required data:
Agent Error – Indicates an SNMP error was returned in response to an SNMP query to this agent.
No Polling Policy - No polling policy exists in Monitoring Configuration settings for this monitored attribute.
Not Polled - Indicates that this attribute is intentionally not polled, based on current
Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of
Service
Unavailable - The SNMP agent responded with a value for chassis operational status of Not-Specified, so NNMi is unable to determine the State. Other possibilities: the
SNMP agent returned a value outside the range of possible values or returned a null value.
Unset – Currently not used by NNMi.
Standby State Either the current MIB-II Standby State value or a value the NNMi State Poller interprets and normalizes to handle differences between vendors. The current Standby State contributes towards the status calculation for this chassis. See the
for more information.
Note: If the chassis's SNMP agent supports only the
, no state or status information is available. NNMi sets this state to No Polling Policy and the chassis status to No Status. If you look on the parent
, you will see the com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Active - Indicates the chassis is the active chassis in the Chassis Redundancy
Group.
Cold-Standby - Indicates the chassis is not in use, but is available to take over the role of the active chassis after it is initialized.
Hot-Standby - Indicates the chassis is not in use, but can immediately take over the role of the active chassis.
Standby - Indicates the chassis is a candidate to become the next active chassis.
Error - Indicates the chassis cannot take over the role of active or standby chassis in the Chassis Redundancy Group.
Other – The SNMP agent on the chassis responded with a value for Standby State of
HPE Network Node Manager i Software (10.20)
Page 197 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
Other or one that is not recognized.
Transient – Indicates the chassis is in a transient state. For example, rebooting.
Unknown - Indicates the chassis is unable to report Standby State.
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.
Previous
Standby State
The Standby State that was determined before the current Standby State. See
for more information about Standby State and the possible values.
State Last
Modified
The date and time when any combination of the Stand By State, Administrative State, and
Operational State were last modified.
Notes Attributes
Attribute Description
Notes Provided for network operators to use for any additional information about this chassis that you want to communicate to your team.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your Chassis table views based on this value. Therefore, you might want to include keywords for this attribute value.
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
HPE Network Node Manager i Software (10.20)
Page 198 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Chassis Form: General Tab
The
provides details about the selected chassis.
For information about each tab:
General Attributes
Attribute Description
Model
Name
Chassis model name or number designator, determined by the vendor.
Model Type The hardware manufacture's designator for the Chassis, determined by the vendor. For example: l cevChassisCat2950t24 l l hpSwitchJ8692A hpSwitch1600
Chassis serial number, determined by the vendor.
Serial
Number
Firmware
Version
The firmware version or revision for the Chassis, determined by the vendor. For example,12.1(22)EA11.
Hardware
Version
Software
Version
The hardware version or revision for the Chassis, determined by the vendor. For example,
VER.B.
The software version or revision for the Chassis, determined by the vendor. For example,
12.1(22)EA11.
Component
Identifier
The unique value assigned to each Physical Component: Chassis. The value chosen is always consistent with the Name value assigned to the Chassis's hosted port.
If ENTITY-MIB is the only MIB supported for a particular Chassis, this attribute has the same value as the Physical Index attribute.
Physical
Index
NNMi gathers this attribute value if the ENTITY-MIB is supported by the chassis's vendor.
Description The description assigned to the Chassis by the operating system of the device in which the
Chassis is mounted. Examples: l
Cisco Catalyst c2950 switch with 24 10/100 BaseTX ports and 2 10/100/1000 BaseT ports l
ProCurve J8692A Switch 3500yl-24G l
HPE J4120A ProCurve Switch 1600M
Chassis Form: Ports Tab
The
provides details about the selected chassis.
HPE Network Node Manager i Software (10.20)
Page 199 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
Ports Associated with this Chassis
Attribute Description
Ports Table of all of the ports associated with the selected chassis. Use this table to access information about each port associated with the selected chassis.
Double-click the row representing a Port. The
displays all details about the selected Port.
Chassis Form: Child Components Tab
The
provides details about the selected chassis.
For information about each tab:
Child Components Attached to this Chassis
Attribute Description
Child
Components
Table of all of the Physical Components of type Card or Chassis that are plugged into the selected chassis. Use this table to access information about each child card or child chassis associated with the selected parent chassis.
Double-click the row representing a child Physical Component. The
or
displays all details about the selected card or chassis.
Chassis Form: Hosted Nodes Tab
(NNMi Advanced) The Chassis Form: Hosted Nodes tab appears if the Chassis is hosting nodes other than the node that is managing this Chassis (the Node identified in this Chassis's
attribute). For example, a virtual device.
For information about each tab:
Hosted Nodes Table
Attribute Description
Status See the Status information in
.
Device Category
Name
Hostname
Management
Address
System Location
The NNMi administrator specifies this attribute value. See Configure Device
Category Icons .
See the Name information in
See the Hostname information in
.
See the Management Address information in
.
See the System Location information in
"Node Form: General Tab" on page 73
.
HPE Network Node Manager i Software (10.20)
Page 200 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Hosted Nodes Table, continued
Attribute Description
Device Profile
SNMP Agent
Enabled
Status Last
Modified
Notes
See the Device Profile information in
See the SNMP Agent Enabled information in
.
See the Status Last Modified information in
"Node Form: Status Tab" on page 93
.
See the Notes information in
Chassis Form: Capabilities Tab
The
provides details about the selected chassis.
The Chassis Form: Capabilities tab displays a table of any capabilities added to the chassis object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about a chassis than is initially stored in the NNMi database.
For information about each tab:
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Capabilities of this Chassis
Attribute Description
Capability Table of all of the capabilities associated with the selected Chassis. Use this table to access information about each Capability.
Unique
Key
Double-click the row representing a Capability. The Physical Component Capability Form displays all details about the selected Capability.
For more information, see
"Chassis Capabilities Provided by NNMi" below .
Chassis Capabilities Provided by NNMi
The
"Chassis Form: Capabilities Tab" above
displays a table of any capabilities added to a particular chassis object. Capabilities enable NNMi and application programmers to provide more information about a chassis than what is initially stored in the NNMi database.
External applications can also add capabilities.
KEY: com.hp.<product>.capability.<content>.<vendor/org>.<MIB/feature>
Any Capability provided by NNMi begins with the prefix com.hp.nnm.capability.
<product> = Either NNMi or the NNM iSPI providing this capability.
HPE Network Node Manager i Software (10.20)
Page 201 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
<content> = chassis, card, ipaddr (address), iface (interface), lag (
Link Aggregation
1
Aggregation
2 or
Split Link
interface), node, rrp (Router Redundancy), or metric (Node Sensor or Physical Sensor).
<vendor/org> = Standards organization or vendor defining the MIB or feature associated with the capability.
<MIB/feature> = What this capability measures.
Note: The following table shows an example of the Capabilities provided by NNMi.
Chassis Capability Attribute Values
Unique Key Capability
com.hp.nnm.capability.chassis.fru Field
Replaceable
Unit
Description
Indicates the device is a replaceable chassis
(Field Replaceable Unit).
Physical Component Capability Form (Chassis)
This form describes a capability added to the Physical Component object by NNMi or an external application.
Capabilities enable NNMi and application programmers to provide more information about a Physical
Component than what is initially stored in the NNMi database.
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Physical Component Capability Attributes
Attribute Description
Capability Label used to identify the Capability that was added to the Physical Component object.
For more information see the following: l
"Chassis Form: Capabilities Tab" on the previous page
shows a list of all available
Capabilities for that chassis.
Unique
Key
Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.
For more information: l
"Chassis Capabilities Provided by NNMi" on the previous page
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 202 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Chassis Form: Custom Attributes Tab
The Chassis Form: Custom Attributes tab displays a table view of any Custom Attributes that have been added to the selected chassis. Custom Attributes provide additional information about an object instance.
Note: If your role permits, you can edit a Custom Attribute. Only users assigned to the NNMi
Administrator role can add a Custom Attribute.
For information about each tab:
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Custom Attributes Table
Attribute Description
Name
Value
Name that identifies this Custom Attribute. This name appears in the table view on the Custom
Attributes tab in Chassis forms. Limit 50 of any combination of keyboard entries including spaces.
The actual value for the Custom Attribute for the selected chassis. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Physical Component Custom Attribute Form (Chassis)" below
.
Physical Component Custom Attribute Form (Chassis)
Physical Component Custom Attributes provide additional information about a Chassis object instance.
NNMi Administrators or applications that have been integrated with NNMi can create these Custom
Attributes.
The required settings for these attributes are described in the table below.
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Basics Attributes
Attribute Description
Name Name that identifies this Custom Attribute. The name appears in the table view on the Custom
Attributes tab in the Chassis form. Limit 50 of any combination of keyboard entries including spaces.
HPE Network Node Manager i Software (10.20)
Page 203 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Value Value assigned to this Custom Attribute for the selected Chassis object. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Chassis Form: Custom Attributes Tab" on the previous page .
Chassis Form: Physical Sensors Tab
The
provides details about the selected chassis.
For information about each tab:
The Chassis Form: Physical Sensors tab displays a table of any Physical Sensors associated with the chassis object for fault monitoring: l
Fan l
Power Supply l
Temperature l
Voltage
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics
Software is installed and configured within your environment, the table can also include Physical Sensors associated with the chassis object for performance monitoring and thresholds ( click here for more information ): l
Backplane Utilization
Threshold based on the percentage of backplane usage compared to the total amount of available backplane resources.
Tip: See
"Physical Sensor Form" on page 244
for more details about the node sensor attributes that appear in this view's column headings. Node Sensors are displayed in three views:
"Non-Normal Physical Sensors View" on page 394 , and
.
Physical Sensors Associated with this Chassis
Attribute Description
Physical
Sensors
Table view of the fault and performance metrics associated with the current chassis. You can use this table to determine the Status, Name, and Type for each Physical Sensor metric associated with the selected chassis.
Double-click the row representing a Physical Sensor. The
"Physical Sensor Monitored Attribute
Form" on page 247 displays all details about the selected Physical Sensor.
Note: The NNMi administrator can set Physical Sensor thresholds. For more information, see
"Chassis Form: Physical Sensors Tab" above
and
.
HPE Network Node Manager i Software (10.20)
Page 204 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Chassis Form: Node Sensors Tab
The
provides details about the selected chassis.
For information about each tab:
The Chassis Form: Node Sensors tab displays a table of any Node Sensors associated with the chassis object for fault monitoring. Each Node Sensor identifies the health aspect that is being monitored.
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics
Software is installed and configured within your environment, the table can include Node Sensors associated with the chassis object for performance monitoring and thresholds ( click here for more information ): l
Buffer Failure Rate l
Buffer Miss Rate l
Buffer Utilization l l
CPU 1Min Utilization
CPU 5Min Utilization l
CPU 5Sec Utilization l
Disk Space Utilization l
Memory Utilization
Tip: See
"Node Sensor Form" on page 232
for more details about the node sensor attributes that appear in this view's column headings. Node Sensors are displayed in three views:
"Node Sensors View" on page 47
,
"Non-Normal Node Sensors View" on page 393 , and
"Unmanaged Node Sensors View" on page
.
Node Sensors Associated with this Chassis
Attribute Description
Node
Sensors
Table view of the fault and performance metrics associated with the current chassis. You can use this table to determine the Status, Name, and Type for each Node Sensor metric associated with the selected chassis.
Double-click the row representing a Node Sensor. The
displays all details about the selected Node Sensor.
Note: The NNMi administrator can set Node Sensor thresholds. For more information, see
"Node Form: Node Sensors Tab" on page 84
,
"Chassis Form: Node Sensors Tab" above ,
and
"Card Form: Node Sensors Tab" on page 223 .
Chassis Form: Incidents Tab
The
provides details about the selected chassis.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 205 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Incidents Associated with this Chassis
Attribute Description
Incidents Table of the Incidents associated with the selected chassis.
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 chassis.
Double-click the row representing an incident. The
displays all details about the selected incident.
Note: See
for more details about the incident attributes that appear in the incident table's column headings.
Chassis Form: Status Tab
The
provides details about the selected chassis.
For information about each tab:
Overall Status Attributes
Attribute Description
Status Overall status for the current chassis. NNMi follows the ISO standard for status classification.
Possible values are:
No Status: The chassis and all of its cards are not polled.
Normal: The Operational State of the Chassis Up. The Operational State of all cards in the chassis is Up.
Unknown: The SNMP Agent associated with the Chassis does not respond to SNMP queries.
Warning: The Operational State of the Chassis not Down. The Operational State of one card in the chassis is Down.
Minor: The Operational State of the Chassis not Down. The Operational State of some (but not all) cards in the chassis is Down.
Major: The Operational State of the Chassis not Down. The Operational State of all cards in the chassis is Down.
Critical: The Operational State of the Chassis Down.
See
"Watch Status Colors" on page 406
for more information about possible status values.
Physical Component status is derived from SNMP polling results for
Operational State , and the most serious outstanding conclusion. For information about how the
current status was determined, see the following: l
"Card Form: Conclusions Tab" on page 226
HPE Network Node Manager i Software (10.20)
Page 206 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status Attributes, continued
Attribute Description
l
"Chassis Form: Conclusions Tab" on the next page
Note: The icons are displayed only in table views.
Status
Last
Modified
Date and time indicating when the Status was last set.
Physical Component Status History Table
Attribute Description
Status
History
Table of up to the last 30 changes in the status for the Chassis. This table is useful for obtaining a summary of the Chassis Status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The
"Physical Component Status History
displays all details about the selected Status.
Physical Component Status History Form (Chassis)
Status is derived from SNMP polling results for
Operational State , and the most serious
outstanding conclusion.
See the object's conclusions for information about how the current status was determined: l
"Chassis Form: Conclusions Tab" on the next page
Status Attributes
Attribute Description
Status Overall status for the current chassis. See
"Watch Status Colors" on page 406
for more information about possible status values.
NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
HPE Network Node Manager i Software (10.20)
Page 207 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status Attributes, continued
Attribute Description
Critical
Physical Component status is derived from SNMP polling results for
Operational State , and the most serious outstanding conclusion.
Note: The icons are displayed only in table views.
For more information see the following: l
"Chassis Form: Status Tab" on page 206
Status Last
Modified
Date and time indicating when the status was last set.
Chassis Form: Conclusions Tab
The
provides details about the selected chassis.
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The table of dynamically generated summary statuses for the chassis that contributed to the current overall Status of the selected chassis. Status is set by the
Causal Engine
1
.
Each Conclusion listed is outstanding and contributes to the current overall Status.
This table is useful for obtaining a quick summary of the problem description for the current chassis that led up to the chassis's most current Status.
Chassis Status is derived from the most serious outstanding Conclusion and SNMP polling results for
and
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 Chassis object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
1
The NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a
Causal Engine management event has an Origin of NNMi in your incident views.
HPE Network Node Manager i Software (10.20)
Page 208 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
ChassisDown The Operational State of the selected chassis is
Down.
Disabled Status Conclusions
Conclusion Description
ChassisDisabled SNMP agent reports that the Administrative
State for the selected chassis is Down.
Status Incident?
Critical Y
Status Incident?
Minor Y
Major Status Conclusions
If any of the following Major chassis conclusions occur, NNMi propagates a major
ChassisMajorInNode Status Conclusion to the parent
unless the NNMi administrator intentionally disables the propagation using java properties settings.
Conclusion
AllCardsDownInChassis
Description
All cards in a chassis are Down.
CardMajorInChassis
ChassisWithBadBackplane
One or more cards in a chassis have a status of major.
One or more backplanes have one or more monitored attributes that are outside the currently configured threshold range.
ChassisWithBadFan One or more fans are out of range or malfunctioning.
ChassisWithBadPowerSupply One or more power supplies are out of range or malfunctioning.
ChassisWithBadTemperature One or more temperature sensors are out of range or malfunctioning.
ChassisWithBadVoltage One or more voltage sensors are out of range or malfunctioning.
Status Incident?
Major Y
Major Y
Major N
Major N
Major N
Major N
Major N
Minor Status Conclusions
Conclusion Description
CardsDownInChassis More than one card in a chassis is Down, but not all cards are Down.
Status Incident?
Minor Y
HPE Network Node Manager i Software (10.20)
Page 209 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Warning Status Conclusions
Conclusion Description
CardDownInChassis One card in a chassis is Down, but not all cards are Down.
Status Incident?
Normal N
Unknown Status Conclusions
Conclusion Description
ChassisUnmanageable The SNMP agent of the managing
Node is not responding.
Status
Unknown
Incident?
N
Normal Status Conclusions
Conclusion
ChassisUp
Description
The Operational State for the current chassis is Up.
CardsUpInChassis The SNMP agent has determined that all
Cards are Up.
Status Incident?
Normal N
Normal Y
Physical Component Status Conclusions Form (Chassis)
The current Conclusion contributes towards the current overall Status of the selected Physical Component.
Basics Attributes
Attribute Description
Status Status is derived from the most serious outstanding Conclusion and SNMP polling results for
and
.
Time
Stamp
The time of the last change in Status.
Conclusion For more information about each conclusion, see the following: l
"Chassis Form: Conclusions Tab" on page 208
Chassis Form: Registration Tab
The
provides details about the selected chassis.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 210 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
Note: 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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
Card Form
The Card form provides details about the Card you selected on the Node form or Inventory: Cards view. The following table describes the fields included on Basics section of the Card form.
For information about each tab:
Basic Attributes
Attribute Description
Name The name of the card. Sometimes it’s the descriptive string used by the network administrator to name the card. For example, SupIII1000SX, Ether10/100TX, RSM-Mod, and ATM-OC3-Phy.
If the Name value is null, NNMi uses the Component Identifier value (see
).
Type The type of Physical Component for this object: Card.
Managed By Node in which the card resides. This is the current value in NNMi’s database for the Name attribute of the host device. The value could be a DNS name, a MIB-II sysName, or an address (depending on how your NNMi administrator configured the discovery process).
HPE Network Node Manager i Software (10.20)
Page 211 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Status
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
Overall status for the current card. NNMi follows the ISO standard for status classification.
See the
"Card Form: Status Tab" on page 224
for more information. Possible values are:
Normal
Warning
Minor
Major
Critical
Disabled
Unknown
No Status
Card status is derived from SNMP polling results for
State , and the most serious outstanding conclusion. See the
"Card Form: Conclusions Tab" on page 226
for information about how the current status was determined. See
for more information about possible status values.
Note: The icons are displayed only in table views.
Management
Mode
The calculated Management Mode for the card according to the Management Mode
Hierarchy. This value reflects the current management mode of this card's parent object
(either the Parent Component card or chassis, or the Managed By node). See
NNMi Assigns the Management Mode to an Object" on page 591 .
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: 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 card. Possible values are:
Inherited – Used to indicate that the card should inherit the Management Mode from this
HPE Network Node Manager i Software (10.20)
Page 212 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
card's parent object (either the Parent Component card or chassis, or the Managed By node).
Not Managed – Used to indicate that NNMi does not discover or monitor the card.
Out of Service – Used to indicate the card is unavailable because it is out of service or participating in a
Scheduled Node Outage . NNMi does not discover or monitor this
card.
NNMi administrators and Level 2 Operators can use the drop-down selection list to change the current setting.
Note: 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.
Parent
Component
If this card is plugged into a chassis or another card, the Name of that chassis or card is listed here.
Redundancy
Group
Indicates whether this card participates in a group of cards that provide redundancy protection against card failure.
Physical Component State Attributes
Attribute Description
Administrative
State
Either the current card Administrative State value. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Administrative State contributes towards the status calculation for this card. See the
"Card Form: Status Tab" on page 224
for more information.
Note: If the card's SNMP agent supports only the
Internet Engineering Task Force
(IETF) ENTITY-MIB , no state or status information is available. NNMi sets this state
to No Polling Policy and the card status to No Status. If you look on the parent
"Node Form" on page 65 , you will see the
com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Up – The SNMP agent responded with a card administrative status value of Up.
Down – The SNMP agent responded with a card administrative status value of Down.
Other – The SNMP agent responded with a value for card administrative status that is not recognized.
HPE Network Node Manager i Software (10.20)
Page 213 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
Operational
State
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.
The current card Operational State value. The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendors. The current Operational State contributes towards the status calculation for this card. See the
"Card Form: Status Tab" on page 224
for more information.
Note: If the card's SNMP agent supports only the
Internet Engineering Task Force
(IETF) ENTITY-MIB , no state or status information is available. NNMi sets this state
to No Polling Policy and the card status to No Status. If you look on the parent
"Node Form" on page 65 , you will see the
com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Up – The SNMP agent responded that the card is operationally up, ready to receive and send network traffic.
Disabled – The card's Administrative State is set to Down.
Down – The SNMP agent responded that the card is operationally down.
Dormant – Indicates the card is in a "pending” state, waiting for some external event.
Minor Fault – Indicates that the card or one of its hardware components is experiencing a partial failure.
Not Present – Indicates that the card module is not installed or is missing.
Other – The SNMP agent responded with a value for card operational status that is not recognized.
HPE Network Node Manager i Software (10.20)
Page 214 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
Testing – The SNMP agent responded that the card is in test mode.
Transient – Indicates the card is in a transient state. For example, rebooting.
Unknown – The SNMP agent responded with a card operational status value of
unknown.
The following values indicate NNMi could not gather the required data:
Agent Error – Indicates an SNMP error was returned in response to an SNMP query to this agent.
No Polling Policy - No polling policy exists in Monitoring Configuration settings for this monitored attribute.
Not Polled - Indicates that this attribute is intentionally not polled, based on current
Monitoring Configuration settings, current Communication Configuration settings, current polling policies, or because the parent Node is set to Not Managed or Out of
Service
Unavailable - The SNMP agent responded with a value for card operational status of
Not-Specified, so NNMi is unable to determine the State. Other possibilities: the
SNMP agent returned a value outside the range of possible values or returned a null value.
Unset – Currently not used by NNMi.
Standby State Either the current MIB-II Standby State value or a value the NNMi State Poller interprets and normalizes to handle differences between vendors. The current Standby State contributes towards the status calculation for this card. See the
"Card Form: Status Tab" on page 224
for more information.
Note: If the card's SNMP agent supports only the
Internet Engineering Task Force
(IETF) ENTITY-MIB , no state or status information is available. NNMi sets this state
to No Polling Policy and the card status to No Status. If you look on the parent
"Node Form" on page 65 , you will see the
com.hp.nnm.capability.card.ietf.entity capability in the list.
Possible values are:
Active - Indicates the card is the active card in the Card Redundancy Group.
Cold-Standby - Indicates the card is not in use, but is available to take over the role of the active card after it is initialized.
Hot-Standby - Indicates the card is not in use, but can immediately take over the role of the active card.
Standby - Indicates the card is a candidate to become the next active card.
HPE Network Node Manager i Software (10.20)
Page 215 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component State Attributes, continued
Attribute Description
Error - Indicates the card cannot take over the role of active or standby card in the
Card Redundancy Group.
Other – The SNMP agent on the card responded with a value for Standby State of
Other or one that is not recognized.
Transient – Indicates the card is in a transient state. For example, rebooting.
Unknown - Indicates the card is unable to report Standby State.
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.
Previous
Standby State
The Standby State that was determined before the current Standby State. See
for more information about Standby State and the possible values.
State Last
Modified
The date and time when any combination of the Stand By State, Administrative State, and
Operational State were last modified.
Notes Attributes
Attribute Description
Notes (NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
Provided for network operators to use for any additional information about this card that you want to communicate to your team.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Note: You can sort your Card table views based on this value. Therefore, you might want to include keywords for this attribute value.
HPE Network Node Manager i Software (10.20)
Page 216 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Card Form: General Tab
The
provides details about the selected card.
For information about each tab:
General Attributes
Attribute Description
Model
Name
Card model name or number designator, determined by the vendor.
Model Type The hardware manufacturer's designator for the card, determined by the vendor. For example: l cevCat6kWsSup720Base l l wssup720base(1002) cat6k-ws-sup720-base
Card serial number, determined by the vendor.
Serial
Number
Firmware
Version
The firmware version or revision for the card, determined by the vendor. For example, 5.4(2).
Hardware
Version
Software
Version
The hardware version or revision for the card, determined by the vendor. For example, 3.1.
The software version or revision for the card, determined by the vendor. For example, 12.2
(33)SXI
Component
Identifier
The unique value assigned to each Physical Component (card or chassis). The value chosen is always consistent with the Name value assigned to the card's hosted port. For example, the physical index of card hosting port Fa5/1 is 5 and the physical index of card hosting port
J8 is J.
If ENTITY-MIB is the only MIB supported for a particular card, this attribute has the same value as the Physical Index attribute.
Physical
Index
NNMi gathers this attribute value if the ENTITY-MIB is supported by the card's vendor.
Description The description assigned to the card by the operating system of the device in which the card is mounted. Examples: l
WS-X5530 1000BaseSXSupervisor Rev. 1.8
l
WS-X5225R 10/100BaseTX Ethernet Rev. 1.1
l
HP J4111A 8-port 10/100Base-TX module
HPE Network Node Manager i Software (10.20)
Page 217 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Card Form: Ports Tab
The
provides details about the selected card.
For information about each tab:
Ports Associated with this Card
Attribute Description
Ports Table of all of the ports associated with the selected card. Use this table to access information about each port associated with the selected card.
Double-click the row representing a Port. The
displays all details about the selected Port.
Card Form: Child Components Tab
The
provides details about the selected card.
For information about each tab:
Child Components Attached to this Card
Attribute Description
Child
Components
Table of all of the Physical Component: Cards that are plugged into the selected card. Use this table to access information about each child card associated with the selected parent card.
Double-click the row representing a child Physical Component. The
displays all details about the selected card.
Card Form: Hosted Nodes Tab
(NNMi Advanced) The Card Form: Hosted Nodes tab appears if the Card is hosting nodes other than the node that is managing this Card (the Node identified in this Card's
attribute). For example, a virtual device.
For information about each tab:
Hosted Nodes Table
Attribute Description
Status
Device Category
Name
See the Status information in
.
The NNMi administrator specifies this attribute value. See Configure Device
Category Icons .
See the Name information in
HPE Network Node Manager i Software (10.20)
Page 218 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Hosted Nodes Table, continued
Attribute Description
Hostname
Management
Address
System Location
Device Profile
SNMP Agent
Enabled
Status Last
Modified
Notes
See the Hostname information in
.
See the Management Address information in
.
See the System Location information in
"Node Form: General Tab" on page 73
.
See the Device Profile information in
See the SNMP Agent Enabled information in
.
See the Status Last Modified information in
"Node Form: Status Tab" on page 93
.
See the Notes information in
Card Form: Capabilities Tab
The
provides details about the selected card.
The Card Form: Capabilities tab displays a table of any capabilities added to the card object by NNMi or an external application. Capabilities enable NNMi and application programmers to provide more information about a card than is initially stored in the NNMi database.
For information about each tab:
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Capabilities of this Card
Attribute Description
Capability Table of all of the capabilities associated with the selected Card. Use this table to access information about each Capability.
Unique
Key
Double-click the row representing a Capability. The Physical Component Capability Form displays all details about the selected Capability.
For more information, see
"Card Capabilities Provided by NNMi" below
.
Card Capabilities Provided by NNMi
The
"Card Form: Capabilities Tab" above
displays a table of any capabilities added to a particular card object.
Capabilities enable NNMi and application programmers to provide more information about a card than what is initially stored in the NNMi database.
HPE Network Node Manager i Software (10.20)
Page 219 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
External applications can also add capabilities.
KEY: com.hp.<product>.capability.<content>.<vendor/org>.<MIB/feature>
Any Capability provided by NNMi begins with the prefix com.hp.nnm.capability.
<product> = Either NNMi or the NNM iSPI providing this capability.
<content> = chassis, card, ipaddr (address), iface (interface), lag (
Link Aggregation
1
Aggregation
2 or
Split Link
interface), node, rrp (Router Redundancy), or metric (Node Sensor or Physical Sensor).
<vendor/org> = Standards organization or vendor defining the MIB or feature associated with the capability.
<MIB/feature> = What this capability measures.
Note: The following table shows an example of the Capabilities provided by NNMi.
Card Capability Attribute Values
Unique Key Capability
com.hp.nnm.capability.card.fru Field
Replaceable
Unit
Description
Indicates the device is a replaceable card (Field
Replaceable Unit).
Physical Component Capability Form (Card)
This form describes a capability added to the Physical Component object by NNMi or an external application.
Capabilities enable NNMi and application programmers to provide more information about a Physical
Component than what is initially stored in the NNMi database.
Note: Because the values are generated by NNMi or an external application, Capability values cannot be modified.
(NNMi Advanced - Global Network Management feature) Any Capability values added by an NNM iSPI are available on the Global Manager only if that iSPI is also running on the Global Manager.
Physical Component Capability Attributes
Attribute Description
Capability Label used to identify the Capability that was added to the Physical Component object.
For more information see the following: l
"Card Form: Capabilities Tab" on the previous page
shows a list of all available Capabilities for that cards.
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 220 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Component Capability Attributes, continued
Attribute Description
Unique
Key
Used as a unique identifier for the Capability. Any capability provided by NNMi begins with the prefix com.hp.nnm.capability.
For more information: l
"Card Capabilities Provided by NNMi" on page 219
Card Form: Custom Attributes Tab
The Card Form: Custom Attributes tab displays a table view of any Custom Attributes that have been added to the selected card. Custom Attributes provide additional information about an object instance.
Note: If your role permits, you can edit a Custom Attribute. Only users assigned to the NNMi
Administrator role can add a Custom Attribute.
For information about each tab:
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
Custom Attributes Table
Attribute Description
Name
Value
Name that identifies this Custom Attribute. This name appears in the table view on the Custom
Attributes tab in Card forms. Limit 50 of any combination of keyboard entries including spaces.
The actual value for the Custom Attribute for the selected card. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Physical Component Custom Attribute Form (Card)" below .
Physical Component Custom Attribute Form (Card)
Physical Component Custom Attributes provide additional information about a Card object instance. NNMi
Administrators or applications that have been integrated with NNMi can create these Custom Attributes.
The required settings for these attributes are described in the table below.
(NNMi Advanced - Global Network Management feature) Custom Attribute values can be replicated from a
Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global
Manager configure which Regional Custom Attributes they want ( Global Manager: Configure Custom
Attribute Replication ). NNMi administrators can also configure Custom Attribute values that are unique to the
Global Manager's environment ( Customize Object Attributes ).
HPE Network Node Manager i Software (10.20)
Page 221 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes
Attribute Description
Name
Value
Name that identifies this Custom Attribute. The name appears in the table view on the Custom
Attributes tab in the Card form. Limit 50 of any combination of keyboard entries including spaces.
Value assigned to this Custom Attribute for the selected Card object. Limit 2,000 of any combination of keyboard entries including spaces.
For more information, see
"Card Form: Custom Attributes Tab" on the previous page
.
Card Form: Physical Sensors Tab
The
provides details about the selected card.
For information about each tab:
The Card Form: Physical Sensors tab displays a table of any Physical Sensors associated with the card for fault monitoring: l
Fan l
Power Supply l l
Temperature
Voltage
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics
Software is installed and configured within your environment, the table can also include Physical Sensors associated with the chassis object for performance monitoring and thresholds ( click here for more information ): l
Backplane Utilization
Threshold based on the percentage of backplane usage compared to the total amount of available backplane resources.
Tip: See
"Physical Sensor Form" on page 244
for more details about the node sensor attributes that appear in this view's column headings. Node Sensors are displayed in three views:
"Non-Normal Physical Sensors View" on page 394 , and
.
Physical Sensors Associated with this Chassis
Attribute Description
Physical
Sensors
Table view of the fault and performance metrics associated with the current card. You can use this table to determine the Status, Name, and Type for each Physical Sensor metric associated with the selected card.
Double-click the row representing a Physical Sensor. The
"Physical Sensor Monitored Attribute
Form" on page 247 displays all details about the selected Node Sensor.
HPE Network Node Manager i Software (10.20)
Page 222 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Sensors Associated with this Chassis, continued
Attribute Description
Note: The NNMi administrator can set Physical Sensor thresholds. For more information, see
"Chassis Form: Physical Sensors Tab" on page 204
and
Sensors Tab" on the previous page .
Card Form: Node Sensors Tab
The
provides details about the selected card.
For information about each tab:
The Card Form: Node Sensors tab displays a table of any Node Sensors associated with the card object for fault monitoring. Each Node Sensor identifies the health aspect that is being monitored.
(NNM iSPI Performance for Metrics) If the HPE Network Node Manager iSPI Performance for Metrics
Software is installed and configured within your environment, the table can include Node Sensors associated with the card object for performance monitoring and thresholds ( click here for more information ): l
Buffer Failure Rate l
Buffer Miss Rate l l
Buffer Utilization
CPU 5Sec Utilization l
CPU 1Min Utilization l
CPU 5Min Utilization l l
Disk Space Utilization
Memory Utilization
Tip: See
"Node Sensor Form" on page 232
for more details about the node sensor attributes that appear in this view's column headings. Node Sensors are displayed in three views:
"Node Sensors View" on page 47
,
"Non-Normal Node Sensors View" on page 393 , and
"Unmanaged Node Sensors View" on page
.
Node Sensors Associated with this Chassis
Attribute Description
Node
Sensors
Table view of fault and performance metrics associated with the current card. You can use this table to determine the Status, Name, and Type for each Node Sensor metric associated with the selected card.
Double-click the row representing a Node Sensor. The
displays all details about the selected Node Sensor.
Note: The NNMi administrator can set Node Sensor thresholds. For more information, see
HPE Network Node Manager i Software (10.20)
Page 223 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Node Sensors Associated with this Chassis, continued
Attribute Description
"Node Form: Node Sensors Tab" on page 84
,
"Chassis Form: Node Sensors Tab" on page
, and
"Card Form: Node Sensors Tab" on the previous page
.
Card Form: Incidents Tab
The
provides details about the selected card.
For information about each tab:
Incidents Associated with this Card
Attribute Description
Incidents Table of the Incidents associated with the selected card.
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 card.
Double-click the row representing an incident. The
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Card Form: Status Tab
The
provides details about the selected card.
For information about each tab:
Overall Status Attributes
Attribute Description
Status Overall status for the current card. NNMi follows the ISO standard for status classification.
Possible values are:
No Status
Normal
Disabled
Unknown
Warning
HPE Network Node Manager i Software (10.20)
Page 224 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status Attributes, continued
Attribute Description
Minor
Major
Critical
See
"Watch Status Colors" on page 406
for more information about possible status values.
Physical Component status is derived from SNMP polling results for
Operational State , and the most serious outstanding conclusion. For information about how the
current status was determined, see the following: l
"Card Form: Conclusions Tab" on the next page
l
"Chassis Form: Conclusions Tab" on page 208
Note: The icons are displayed only in table views.
Status
Last
Modified
Date and time indicating when the Status was last set.
Physical Component Status History Table
Attribute Description
Status
History
Table of up to the last 30 changes in the status for the Card. This table is useful for obtaining a summary of the Card Status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The
"Physical Component Status History
displays all details about the selected Status.
Physical Component Status History Form (Card)
Status is derived from SNMP polling results for
Operational State , and the most serious
outstanding conclusion.
See the object's conclusions for information about how the current status was determined: l
"Card Form: Conclusions Tab" on the next page
Status Attributes
Attribute Description
Status Overall status for the current chassis. See
"Watch Status Colors" on page 406
for more information about possible status values.
NNMi follows the ISO standard for status classification. Possible values are:
No Status
HPE Network Node Manager i Software (10.20)
Page 225 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status Attributes, continued
Attribute Description
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Physical Component status is derived from SNMP polling results for
Operational State , and the most serious outstanding conclusion.
Note: The icons are displayed only in table views.
For more information see the following: l
"Card Form: Status Tab" on page 224
Status Last
Modified
Date and time indicating when the status was last set.
Card Form: Conclusions Tab
The
provides details about the selected card.
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The table of dynamically generated summary statuses for the card that contributed to the current overall Status of the selected card. Status is set by the
Causal Engine
1
.
Each Conclusion listed is outstanding and contributes to the current overall Status.
This table is useful for obtaining a quick summary of the problem description for the current card that led up to the card's most current Status.
Card Status is derived from the most serious outstanding Conclusion and SNMP polling
1
The NNMi Causal Engine analyzes the health of your network and provides the ongoing health status reading for each device. The Causal Engine also extensively evaluates problems and determines the root cause for you, whenever possible, sending incidents to notify you of problems. Any incident generated from a
Causal Engine management event has an Origin of NNMi in your incident views.
HPE Network Node Manager i Software (10.20)
Page 226 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
results for
and
.
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 Card object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
CardDown The Operational State of the selected card is
Down.
Status
Critical
Incident?
Y
Disabled Status Conclusions
Conclusion Description
CardDisabled SNMP agent reports that the Administrative
State for the selected card is Down.
Status Incident?
Disabled Y
Major Status Conclusions
Conclusion
CardWithBadBackplane
CardWithBadFan
Description
One or more backplanes have one or more monitored attributes that are outside the currently configured threshold range.
One or more fans are out of range or malfunctioning.
CardWithBadPowerSupply One or more power supplies are out of range or malfunctioning.
CardWithBadTemperature One or more temperature sensors are out of range or malfunctioning.
CardWithBadVoltage One or more voltage sensors are out of range or malfunctioning.
Status Incident?
Major N
Major N
Major N
Major N
Major N
Minor Status Conclusions
HPE Network Node Manager i Software (10.20)
Page 227 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
CardUndeterminedState NNMi cannot determine the Card's
State for one of the following reasons: l
The SNMP agent responded with a value for the card's Operational
Status of Unavailable.
l
The SNMP agent returned a value outside the range of possible values or returned a null value.
DaughterCardsDown The Operational State of at least one of the associated child cards is
Down.
Status Incident?
Minor Y
Minor N
Unknown Status Conclusions
Conclusion Description
CardUnmanageable The SNMP agent of the managing
Node is not responding.
Status
Unknown
Incident?
N
Normal Status Conclusions
Conclusion
CardUp
Description
The Operational State for the current card is Up.
DaughterCardsUp The Operational State of all associated child cards are Up.
Status Incident?
Normal N
Normal N
Physical Component Status Conclusions Form (Card)
The current Conclusion contributes towards the current overall Status of the selected Physical Component.
Basics Attributes
Attribute Description
Status
Time
Stamp
Status is derived from the most serious outstanding Conclusion and SNMP polling results for
and
.
The time of the last change in Status.
HPE Network Node Manager i Software (10.20)
Page 228 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Conclusion For more information about each conclusion, see the following: l
"Card Form: Conclusions Tab" on page 226
Card Form: RegistrationTab
The
provides details about the selected card.
For information about each tab:
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.
Note: 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: l
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.
l
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.
Port Form
The Port form provides details about the port you selected on the Node form or VLAN form. The following table describes the fields included on the Port form.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 229 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes
Attribute Description
Name
Hosted on
Node
The port name consists of <Card-number / Port-number>.
The current value from the Name attribute on the Node form of the node on which the port resides. This is the current value in NNMi’s database for the Name attribute of the host device. The value could be a DNS name, a MIB-II sysName, or an address (depending on how your NNMi administrator configured the discovery process).
Card
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
The current value from the Name attribute on the Card form of the card to which this port is assigned.
Type
Speed
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
The port-type designator determined by the vendor.
Potential maximum physical speed of the port.
Configured
Duplex
Setting
Set by the administrator of the node. Possible values are:
Basic Attributes
Value Description
AUTO
HALF
Indicates that Auto-negotiation is set for the configured duplex setting. Autonegotiation is an Ethernet procedure in which two connected devices choose the fastest transmission mode they both support.
Indicates the port supports half-duplex operations. This means the port can send information in both directions between two devices, but in only one direction at a time.
FULL Indicates the port supports full-duplex operations. This means the port can send data in both directions simultaneously.
DISAGREE Indicates the port could not agree on the duplex settings with a port on the other end of a connection.
UNKNOWN Indicates the manufacturer of this device does not support this setting.
Associated
Interface
The current value from the Name attribute on the Interface form of the interface using this port. This is the current value in NNMi’s database obtained using the Interface MIB: ifName, ifAlias, or ifType+ifIndex
Click the Lookup icon and select Show Analysis or Open to display more information about the interface.
HPE Network Node Manager i Software (10.20)
Page 230 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
ifAlias Optional Interface MIB variable for ifAlias assigned to the interface. This value is set by the device administrator. An ifAlias could be useful if the interface vendor did not provide an ifName value.
Port Index The unique value assigned to this port within the card.
Related Topics:
Port Form: VLANs Tab
The
provides details about the selected port.
For information about each tab:
(NNMi Advanced - Global Network Management feature) There might be slight differences between the VLAN information shown on Regional Managers and Global Managers, because the VLAN calculations use
data.
VLANs Attributes
Attribute Description
VLANs Table view of the VLANs to which the selected port belongs. You can use this table to determine the VLAN ID number and name for each VLAN associated with the selected port.
Double-click the row representing a VLAN. The
displays all details about the selected VLAN.
Related Topics:
Port Form: RegistrationTab
The
provides details about the selected port.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 231 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
Note: 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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
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).
For information about each tab:
Tip: Node Sensors are displayed in three views:
"Node Sensors View" on page 47 ,
, and
"Unmanaged Node Sensors View" on page 585 .
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
HPE Network Node Manager i Software (10.20)
Page 232 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Unknown
Warning
Minor
Major
Critical
For information about how the current status was determined, see the
.
Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views.
Name
Type
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, HPE 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.
Note: If the associated MIB file does not provide a name value, NNMi uses the value provided by the Type attribute.
Identifies the health aspect that is being monitored.
(NNM iSPI Performance for Metrics) The following examples require an HPE Network
Node Manager iSPI Performance for Metrics Software license: l
Buffer l
Buffer Failure Rate l
Buffer Miss Rate l
Buffer Utilization l
CPU utilization
HPE Network Node Manager i Software (10.20)
Page 233 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
l
CPU 1Min Utilization l
CPU 5Min Utilization l
CPU 5Sec Utilization l
Disk Space Utilization l
Memory Utilization
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
.
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
Tip: 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
. 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.
Note: 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
for more
HPE Network Node Manager i Software (10.20)
Page 234 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
information.
Note: The NNMi administrator can set Physical Sensor thresholds. For more information, see
"Node Form: Node Sensors Tab" on page 84 ,
and
"Card Form: Node Sensors Tab" on page 223 .
Node Sensor Form: Monitored Attributes Tab
The
"Node Sensor Form" on page 232
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:
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" below
displays all details about the selected Monitored Attribute.
Node Sensor Monitored Attribute Form
The Node Sensor Monitored Attribute form displays information about the attribute selected on the
Sensor Form: Monitored Attributes Tab" above
.
NNMi obtains fault metric information from the associated MIB.
(NNM iSPI Performance for Metrics) If the HPE 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: l
Buffer Failure Rate l l
Buffer Miss Rate
Buffer Utilization l
CPU 5Sec Utilization l
CPU 1Min Utilization l l
CPU 5Min Utilization
Disk Space Utilization l
Memory Utilization
HPE Network Node Manager i Software (10.20)
Page 235 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes
Attribute Description
Label
Unique
Key
State
Name used to identify the attribute being monitored.
See
"Node Sensor Form" on page 232
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: l
CPU Revised 1 Minute l
CPU Revised 5 Minute l
CPU Revised 5 Second
Used as a unique identifier for the Monitored Attribute. Any Monitored Attribute provided by
NNMi begins with the prefix com.hp.nms.
Normalized value used to indicate the State of the attribute of the selected Monitored Attribute.
Possible values are listed below.
Note: 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.
HPE Network Node Manager i Software (10.20)
Page 236 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
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.
Node Sensor Form: Physical Components Tab
The
"Node Sensor Form" on page 232
provides details about the monitored attribute (for example, Memory
Utilization) related to the current Node Sensor.
For information about each tab:
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
displays all details about the selected Chassis. The
displays all details about the selected Card.
Node Sensor Form: Incidents Tab
The
"Node Sensor Form" on page 232
provides details about the selected node sensor.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 237 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Node Sensor Form: Status Tab
The
"Node Sensor Form" on page 232
provides details about the selected Node Sensor.
For information about each tab:
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
Note: 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" on page 240
. Status reflects the most serious outstanding conclusion. See
for more information about possible status values.
HPE Network Node Manager i Software (10.20)
Page 238 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute
Description
Note: 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" below
displays all details about the selected Status.
Node Sensor Status History Form
The Node Sensor Status History form displays information about the selected Status History entry on the
"Node Sensor Form: Status Tab " on the previous page
.
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
Note: Your NNMi administrator might have disabled polling of Node Sensors using the
HPE Network Node Manager i Software (10.20)
Page 239 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute Description
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
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The Status icons are displayed only in table views.
Time
Stamp
Date and time indicating when the Status History entry was established.
Node Sensor Form: Conclusions Tab
The
"Node Sensor Form" on page 232
provides details about the selected health metric for the current Node
Sensor.
For information about each tab:
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
displays all details about the selected Status Conclusion.
The following table describes the possible Conclusions that might appear for a Node
Sensor object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
HPE Network Node Manager i Software (10.20)
Page 240 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
BufferOutOfRangeOrMalfunctioning
CpuOutOfRangeOrMalfunctioning
Description
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.
Any of the following utilization averages is above the threshold range configured for the device: l l l
CPU 5 second utilization
CPU 1 minute utilization
CPU 5 minute utilization
DiskOutOfRangeOrMalfunctioning The disk monitored attributes are outside of the threshold range configured for the device.
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.
Status Incident?
Critical Y
Critical Y
Critical Y
Critical Y
Warning Status Conclusions
Conclusion
BufferAbnormal
Description
The buffer utilization is abnormal based on
Status Incident?
Warning Y
HPE Network Node Manager i Software (10.20)
Page 241 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
CpuAbnormal
Description
the computed baseline.
The CPU utilization is abnormal based on the computed baseline for one of the following: l
CPU 5 second utilization l
CPU 1 minute utilization l
CPU 5 minute utilization
DiskAbnormal The disk space utilization is abnormal based on the computed baseline.
MemoryAbnormal The memory utilization is abnormal based on the computed baseline.
Status Incident?
Warning Y
Warning Y
Warning Y
Normal Status Conclusions
Conclusion
BufferInRangeAndFunctioning
BufferNormal
CpuInRangeAndFunctioning
CpuNormal
Description
The buffer pool is operating within the threshold range configured for the device.
Status
Normal
Incident?
N
The buffer utilization is normal based on the computed baseline.
Normal N
All of the following utilization averages are within the threshold range configured for the device: l
CPU 5 second utilization l
CPU 1 minute utilization l
CPU 5 minute utilization
The CPU utilization is normal based on the computed baseline for the following: l l
CPU 5 second utilization
CPU 1 minute utilization l
CPU 5 minute utilization
Normal N
Normal N
HPE Network Node Manager i Software (10.20)
Page 242 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
DiskInRangeAndFunctioning
Description
The disk monitored attributes are within the threshold range configured for the device.
DiskNormal The disk space utilization is normal based on the computed baseline.
MemoryInRangeAndFunctioning The specified memory pool is operating within the threshold range configured for the device.
MemoryNormal The memory utilization is normal based on the computed baseline.
Status Incident?
Normal N
Normal N
Normal N
Normal N
Node Sensor Status Conclusion Form
The current Conclusion contributes towards the overall Status of the selected Node Sensor (see
Sensor Form: Status Tab " on page 238
).
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" on page 240
.
Node Sensor Form: Registration Tab
The
"Node Sensor Form" on page 232
provides details about the selected Node Sensor.
For information about each tab:
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.
Note: This value does not change when a node is rediscovered. This is because the Node object is modified, but not created.
HPE Network Node Manager i Software (10.20)
Page 243 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Registration Attributes, continued
Attribute Description
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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
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).
For information about each tab:
Tip: The NNMi administrator can set Physical Sensor thresholds. Physical Sensors are displayed in three views:
"Physical Sensors View" on page 47 ,
"Non-Normal Physical Sensors View" on page 394
, and
"Unmanaged Physical Sensors View" on page 585
.
Basic Attributes
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
HPE Network Node Manager i Software (10.20)
Page 244 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Major
Critical
For information about how the current status was determined, see the
.
Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: 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, HPE 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.
Note: 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: l
Fan l l
Power Supply
Temperature l
Voltage
(NNM iSPI Performance for Metrics) Health monitoring of the following requires an HPE
Network Node Manager iSPI Performance for Metrics Software license: l
Backplane
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
NNMi Assigns the Management Mode to an Object" on page 591 .
(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.
Note: If the NNMi Security configuration permits, you can change this setting using
Actions → Management Mode.
HPE Network Node Manager i Software (10.20)
Page 245 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Tip: 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
. 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.
Note: 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).
Hosted On
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
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
or
for more information.
Note: The NNMi administrator can set Physical Sensor thresholds. For more information, see
"Chassis Form: Physical Sensors Tab" on page 204
and
Physical Sensors Tab" on page 222 .
Physical Sensor Form: Monitored Attributes Tab
The
"Physical Sensor Form" on page 244
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
HPE Network Node Manager i Software (10.20)
Page 246 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details administrator.
For information about each tab:
Attributes Table
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" below
displays all details about the selected Monitored Attribute.
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" on the previous page .
Physical Sensors for fault monitoring include the following: l
Fan l
Power Supply l
Temperature l
Voltage
(NNM iSPI Performance for Metrics) If the HPE 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: l
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.
Basics Attributes
Attribute Description
Label
Unique
Key
State
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.
Used as a unique identifier for the Monitored Attribute. Any Monitored Attribute provided by
NNMi begins with the prefix com.hp.nms.
Normalized value used to indicate the State of the attribute of the selected node. Possible values are listed below.
Note: The NNMi State Poller interprets and normalizes the State value returned for the monitored attribute to handle the differences between vendor-specific nodes.
HPE Network Node Manager i Software (10.20)
Page 247 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
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.
Note: 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
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.
HPE Network Node Manager i Software (10.20)
Page 248 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Last
Modified
The most recent date and time when the State of this Monitored Attribute changed.
Physical Sensor Form: Incidents Tab
The
"Physical Sensor Form" on page 244
provides details about the selected physical sensor.
For information about each tab:
Incidents Associated with this Physical Sensor
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
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Physical Sensor Form: Status Tab
The
"Physical Sensor Form" on page 244
provides details about the selected Physical Sensor.
For information about each tab:
Overall Status
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
HPE Network Node Manager i Software (10.20)
Page 249 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute
Description
Major
Critical
Note: 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
Conclusions Tab" on the next page
. Status reflects the most serious outstanding conclusion.
See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: 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 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" below
displays all details about the selected Status.
Physical Sensor Status History Form
The Physical Sensor Status History form displays information about the selected Status History entry on the
"Physical Sensor Form: Status Tab " on the previous page .
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
HPE Network Node Manager i Software (10.20)
Page 250 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute
Description
Disabled
Unknown
Warning
Minor
Major
Critical
Note: 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
Conclusions Tab" below . Status reflects the most serious outstanding conclusion. See
for more information about possible status values.
Note: The Status icons are displayed only in table views.
Time
Stamp
Date and time indicating when the Status History entry was established.
Physical Sensor Form: Conclusions Tab
The
"Physical Sensor Form" on page 244
provides details about the selected health metric for the current
Physical Sensor.
For information about each tab:
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 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
HPE Network Node Manager i Software (10.20)
Page 251 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
displays all details about the selected Status Conclusion.
The following table describes the possible Conclusions that might appear for a Physical
Sensor object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion
BackplaneOutOfRangeOrMalfunctioning
Description Status Incident?
The backplane monitored attributes are outside of the threshold range configured for the device.
Critical Y
FanOutOfRangeOrMalfunctioning The fan monitored attributes are outside of the threshold range configured for the device.
Critical Y
PowerSupplyOutOfRangeOrMalfunctioning A power supply’s monitored attributes are outside of the threshold range configured for the device.
Critical Y
TemperatureOutOfRangeOrMalfunctioning The specified temperature sensor on the Source Node is outside of the threshold range configured for the device.
Critical Y
VoltageOutOfRangeOrMalfunctioning The specified voltage on one of the Source Node's power supplies is outside of the threshold
Critical Y
HPE Network Node Manager i Software (10.20)
Page 252 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
configured for the device.
Status Incident?
Warning Status Conclusions
Conclusion Description
BackplaneAbnormal The backplane utilization is abnormal based on the computed baseline.
Status
Warning
Incident?
Y
Normal Status Conclusions
Conclusion
BackplaneInRangeAndFunctioning
Description Status Incident?
The backplane monitored attributes are within the threshold range configured for the device.
Normal N
BackplaneNormal The backplane utilization is normal based on the computed baseline.
Normal N
Normal N FanInRangeAndFunctioning The specified fan monitored attributes are within the threshold range configured for the device.
PowerSupplyInRangeAndFunctioning A power supply’s monitored attributes are within the threshold range configured for the device.
Normal N
TemperatureInRangeAndFunctioning The specified temperature sensor on the Source Node is within the threshold range configured for the device.
VoltageInRangeAndFunctioning
Normal N
The specified voltage on one of the Source Node's power supplies is within the threshold range configured for the device.
Normal N
HPE Network Node Manager i Software (10.20)
Page 253 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Physical Sensor Status Conclusions Form
The current Conclusion contributes towards the overall Status of the selected Physical Sensor (see
Sensor Form: Status Tab " on page 249
).
Outstanding Status Conclusion Values
Attribute Description
Time Stamp The time of the last change in Status.
Conclusion For more information see the
"Physical Sensor Form: Conclusions Tab" on page 251
.
Physical Sensor Form: Registration Tab
The
"Physical Sensor Form" on page 244
provides details about the selected Physical Sensor.
For information about each tab:
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.
Note: 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: l
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.
l
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.
HPE Network Node Manager i Software (10.20)
Page 254 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Layer 2 Connection Form
The Layer 2 Connection form provides details about a managed connection. These details include the interfaces that make up the connection, the protocol used to create this connection, and the current status of the connection. For example, if all interfaces are down within a connection, the connection status is listed as
Critical. The NNMi administrator can configure NNMi to automatically delete Layer 2 Connections when all member Interfaces are down for a specified number of days.
For information about each tab:
Note: Forwarding Database (FDB) information can cause NNMi to establish wrong Layer 2 Connections in the following cases: l
When the FDB is configured as cache and contains obsolete data.
l
In network environments with hardware from a variety of vendors, when each vendor generates different and sometimes conflicting FDB data.
Optional: NNMi administrators can configure Spiral Discovery to ignore the FDB data from one Node
Group when calculating Layer 2 Connections (the FDB data is still included in other calculations).
(NNMi Advanced - Global Network Management feature) NNMi must read the Forwarding Database
(FDB) tables from Ethernet switches within the network before accurate communication paths between these network devices can be calculated. Because the FDB data is involved, NNMi can produce different results on a Regional Manager as opposed to the Global Manager.
Basic Attributes
Attribute Description
Name
Status
Name that NNMi assigned to the Layer 2 Connection. This name contains the list of member interface names separated by a comma. Each interface name appears in the format: Node_
Name[Interface_Name].
Overall status for the current connection. NNMi follows the ISO standard for status classification. See the
"Layer 2 Connection Form: Status Tab" on page 258
for more information. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
HPE Network Node Manager i Software (10.20)
Page 255 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
For information about how the current status was determined, see the
Form: Conclusions Tab" on page 260 . Status reflects the most serious outstanding conclusion.
See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views.
Topology
Source
Indicates the data source used to create this connection.
Note: (NNMi Advanced) Layer 2 Connections using
Link Aggregation
1
Aggregation
2 protocols can connect sets of Interfaces. See or
Split Link
Link Aggregation Tab (NNMi Advanced)" on page 265 . These Aggregator Layer 2
Connections display as thick lines on NNMi maps.
If you see the icon (in previous NNMi releases the icon), NNMi gathered information from Layer 2 of the Open System Interconnection (OSI) networking model to detect this connection. Layer 2 is the Data Link layer that encodes and decodes data packets into bits. The
Data Link layer has two sub-layers: The Media Access Control (MAC) sub-layer controls how a computer gains access to data and permission to transmit the data. The Logical Link Control
(LLC) sub-layer controls frame synchronization, flow control, and error checking. The following are some examples of possible Topology Source values:
CDP - Cisco Discovery Protocol. On the NNMi map, the following icon is in the middle of the
Layer 2 Connection line:
EDP - Extreme Discovery Protocol
EnDP - Enterasys Discovery Protocol (also known as CDP - Cabletron Discovery Protocol)
FDB - Forwarding Database (also known as AFT - Address Forwarding Table on a switch). On the NNMi map, the following icon is in the middle of the Layer 2 Connection line:
(in prior NNMi releases, the icon)
FDBH - NNMi’s Forwarding Database High Priority indicates a special case was encountered and NNMi gave priority of FDB over Discovery Protocol information.
FDP - Foundry Discovery Protocol
IEEELAG - Institute of Electrical and Electronics Engineers Link Aggregation
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 256 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Notes
ISL - Inter Switch Link Protocol
LLDP - Link Layer Discovery Protocol
NDP - IPv6 Neighbor Discovery Protocol
SONMP - SynOptics Network Management Protocol
VMWARE - VMware VSphere® web-service
ROUTES - Indicates that an unnumbered Interface is involved in this connection. The NNMi administrator has enabled the Unnumbered Interface Connectivity feature. For more information:
SUBNETCONNECTION - Subnet Connection Rule. NNMi applied a special configurable rule for subnets (only those IPv4 subnets with a prefix length between 28 and 31) to detect this connection. NNMi gathers information from Layer 3 of the Open System Interconnection
(OSI) networking model to detect this connection. Layer 3 is the Network layer that provides switching, routing, and logical paths (virtual circuits) for transmitting data between nodes. The NNMi administrator configures the Subnet Connection Rules, see "Help for
Administrators" for more information. On the NNMi map, the following icon is in the middle of the SUBNETCONNECTION line:
(in prior NNMi releases, the icon)
USER - This connection was configured by your NNMi administrator (using the Connection
Editor). See "Help for Administrators" for more information.
(NNMi Advanced - Global Network Management feature) The text you enter here is not sent from a Regional Manager (NNMi management server) to the Global Manager. NNMi administrators for the Global Manager can add notes that are stored in the NNMi database on the Global Manager.
Provided for network operators to use for any additional notes required to further explain the
Layer 2 Connection. Information might include when a cable was last replaced.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Layer 2 Connection Form: Interfaces Tab
The
"Layer 2 Connection Form" on page 255
provides details about a managed connection. These details include the interfaces that make up the connection, the protocol used to create this connection, and the current status of the connection. For example, if all interfaces are down within a connection, the connection status is listed as Critical.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 257 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interfaces Table
Attribute Description
Interfaces Table view of both of the interfaces that are part of the current connection. You can use this table to determine the status, administrative state, operational state, name, type, interface speed, and Layer 2 Connection for each interface associated with the selected Layer 2
Connection.
Double-click the row representing an interface. The
displays all details about the selected interface.
Layer 2 Connection Form: Incidents Tab
The
"Layer 2 Connection Form" on page 255
provides details about a managed connection.
For information about each tab:
Incidents Table
Attribute Description
Associated
Incidents
Table view of the incidents associated with the selected Layer 2 Connection. NNMi displays only those incidents that have a Family attribute value of Connection.
Tip: To check all Incidents related to the Interface on each end of the connection, navigate to the
"Layer 2 Connection Form: Interfaces Tab" on the previous page
and open an Interface form. To check all incidents related to the Node, use the Hosted On
Node attribute on the Interface form to open the Node form.
Examples of the incidents that might appear as Associated Incidents for Layer 2 Connections include the following: l
l
Modified Connection Down
Associated 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 connection.
Double-click the row representing an incident. The
displays all details about the selected incident. Navigate to the
"Incident Form: Correlated Children Tab" on page 446
and
"Incident Form: Correlated Parents Tab" on page 446
to check for any correlated incidents that are associated with the interfaces and nodes on each end of the connection.
Layer 2 Connection Form: Status Tab
The
"Layer 2 Connection Form" on page 255
provides details about a managed connection.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 258 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status Attributes
Attribute
Description
Status Overall status for the current connection. NNMi follows the ISO standard for status classification. Possible values are:
Note: The icons are displayed only in table views.
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Status
Last
Modified
Critical
For information about how the current status was determined, see
Conclusions Tab" on the next page
. Status reflects the most serious outstanding conclusion.
See
"Watch Status Colors" on page 406
for more information about possible status values.
(NNMi Advanced)
Link Aggregation
1 or
Split Link Aggregation
2
: If the Layer 2 Connection is an Aggregator, the Status is calculated using the combined Status of all Aggregation Member
Layer 2 Connections. For more information, see
"Layer 2 Connection Form: Link Aggregation
Tab (NNMi Advanced)" on page 265
and Status Color for Aggregator Objects .
Date and time indicating when the status was last set.
Status History Table
Attribute
Description
Status
History
List of up to the last 30 changes in status for the selected connection. This view is useful for obtaining a summary of the connection status so that you can better determine any patterns in
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 259 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status History Table, continued
Attribute
Description
connection behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
Layer 2 Connection Form: Conclusions Tab
The
"Layer 2 Connection Form" on page 255
provides details about a managed connection.
All relevant conclusions are shown in the table on this tab. The most severe Status in the current group of conclusions becomes the overall L2 Connection status. Some L2 Connection conclusions propagate to other object types:
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusion s
The dynamically generated list of summary statuses of the connection that contributed to the current overall Status of the selected connection. Status is set by Causal Engine.
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 for the current connection that led up to the connection's most current Status.
The Status value is correlated based on the most critical Conclusion.
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 Connection object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
HPE Network Node Manager i Software (10.20)
Page 260 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
AggregatorLinkDown
Description
AllConnectionThreshold
ValuesHigh
Each interface in the connection contains one of the following Conclusions:
Status
(NNMi Advanced)
Link
Aggregation
1
Aggregation
2 or
Split Link
: The Operational
State of all participating
Aggregation Member Layer 2
Connections is Down. For more information, see
.
Critical
Critical
ConnectionDown l
InterfaceInputUtilizationHigh l
InterfaceOutputUtilizationHigh l l
InterfaceInputDiscardRateHigh
InterfaceOutputDiscardRateHigh l
InterfaceInputErrorRateHigh l
InterfaceOutputErrorRateHigh l l
InterfaceOutputQueueDropsRateHigh
InterfaceInputQueueDropsRateHigh l
InterfaceFCSWLANErrorRateHigh l
InterfaceFCSLANErrorRateHigh
Both (or all) ends of a connection have an Operational
State of Down.
Critical
Minor Status Conclusions
Incident?
Y
N
Y
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 261 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
AggregatorLinkDegraded
ConnectionWithAtLeastOneDownEP
Description Status
(NNMi
Advanced)
Link
Aggregatio n
1 or
Split
Link
Aggregatio n
2
: Some
(but not all) of the participating
Aggregation
Member
Layer 2
Connections have an
Operational
State of
Down. For more information, see
Minor
At least one interface, but not all interfaces, in the connection have an
Minor
Incident?
Y
N
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 262 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion
SomeConnectionThresholdValuesHigh
Description Status
Operational
State of
Down.
One interface in the connection contains one of the following conclusions:
Minor
Incident?
N l
InterfaceInputUtilizationHigh l l
InterfaceOutputUtilizationHigh
InterfaceInputDiscardRateHigh l
InterfaceOutputDiscardRateHigh l
InterfaceInputErrorRateHigh l l
InterfaceOutputErrorRateHigh
InterfaceOutputQueueDropsRateHigh l
InterfaceInputQueueDropsRateHigh l
InterfaceFCSWLANErrorRateHigh l
InterfaceFCSLANErrorRateHigh
N SomeOrAllConnectionThresholdValuesLow One
Interface in the connection contains one of the following conclusions:
Minor
SomeOrAllConnectionThresholdValuesNo ne l l
InterfaceInputUtilizationLow
InterfaceOutputUtilizationLow
N One interface in the connection contains one of the
Minor
HPE Network Node Manager i Software (10.20)
Page 263 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description Status
following conclusions:
Incident?
l
InterfaceInputUtilizationNone l
InterfaceOutputUtilizationNone l l
InterfaceInputDiscardRateNone
InterfaceOutputDiscardRateNone l
InterfaceInputErrorRateNone l
InterfaceOutputErrorRateNone
Warning Status Conclusions
Conclusion Description Status Incident?
ConnectionPartiallyUnresponsive At least one interface in a connection has an Operational
State of Up and at least one interface's associated SNMP
Agent is not responding to
SNMP queries.
Warning N
Unknown Status Conclusions
Conclusion Description
ConnectionUnknown All SNMP Agents associated with all interfaces in the connection are not responding to SNMP queries.
Status
Unknown
Incident?
N
Disabled Status Conclusions
Conclusion
ConnectionDisabled
Description Status Incident?
All interfaces in the connection have an
Administrative State of
Disabled.
Disabled N
ConnectionWithAtLeastOneDisabledEP At least one interface, but not all interfaces, in the connection have an
Administrative State of
Down.
Disabled N
HPE Network Node Manager i Software (10.20)
Page 264 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Normal Status Conclusions
Conclusion
AggregatorLinkUp
ConnectionEnabled
Description
All interfaces in a connection have an
Administrative State of
Up.
Status Incident?
(NNMi Advanced)
Link
Aggregation
1 or
Split
Link Aggregation
2
: All of the participating
Aggregation Member
Layer 2 Connections have an Operational State of Up. For more information, see
Normal N
Normal N
ConnectionUp The Operational State of each interface in the connection is Up.
ConnectionWithinThresholdBoundaries All thresholds on interfaces in the connection are functioning within the threshold boundaries set on the device.
Normal N
Normal N
Layer 2 Connection Form: Link Aggregation Tab
( NNMi Advanced)
The
"Layer 2 Connection Form" on page 255
provides details about the selected Layer 2 Connection.
For information about each tab:
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 265 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
The Layer 2 Connection Form: Link Aggregation Tab appears if the selected connection uses a Link
Aggregation protocol.
On a Layer 2 map, a thick line with a superimposed ellipse represents a
Link Aggregation
1
Aggregation
2 or
Split Link
(group of multiple Layer 2 Connections that are functioning as one). The icon representing an
Interface at either end of the thick line is an Aggregator Interface (a logical interface comprised of many physical interfaces that are functioning as one).
Two endpoints: Three endpoints: More than three endpoints:
The selected object's role in the Link Aggregation determines the contents of the tab:
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 266 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
Aggregation Member, click here for details .
Attribute
Link
Aggregation
Protocol
Description
The
Link Aggregation
1 or
Split Link Aggregation
2
Protocol currently in use. These protocols allow network administrators to configure a set of interfaces on a switch as one
Aggregator Interface, creating an Aggregator Layer 2 Connection to another device using multiple interfaces in parallel to increase bandwidth, increase the speed at which data travels, and increase redundancy:
Text Represents This Protocol
Cisco Port Aggregation Protocol
Nortel Multi-Link Trunking
Split MLT
Cisco Systems Port Aggregation Protocol
(pagp)
Nortel Multi-Link Trunk technology (mlt)
Split Multi-Link Trunk: configuration technology
(splitMlt)
Split Multi-Link Trunk: inter-switch trunk (istMlt) Inter-Switch Trunk MLT
802.3ad Link Aggregation Control
Protocol
Static/Manual Configured Link
Aggregation
IEEE 802.3ad Link Aggregation Control protocol
(LACP)
Static/Manual Configured Link Aggregation
Unknown Protocol Link Aggregation unknown
Note: It is possible for a Layer 2 Connection to connect sets of Aggregator/Member
Interfaces that are configured using different Link Aggregation protocols. In that case, this attribute value contains multiple protocols separated with a slash (/).
Aggregator Name of the Aggregator that contains the selected participating Aggregation Member: l
Aggregator Interface - represents multiple member interfaces l
Aggregator Layer 2 Connection - thick line on the Layer 2 map represents multiple member Layer 2 Connections
See Layer 2 Neighbor View Map Objects for more information.
Click the Lookup icon, and choose Open to open the form for the Aggregator.
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 267 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l
Aggregator (representing multiple members), click here for details .
Attribute
Link
Aggregation
Protocol
Description
The
Link Aggregation
1 or
Split Link Aggregation
2
Protocol currently in use. These protocols allow network administrators to configure a set of interfaces on a switch as one
Aggregator Interface, creating an Aggregator Layer 2 Connection to another device using multiple interfaces in parallel to increase bandwidth, increase the speed at which data travels, and increase redundancy:
Text Represents This Protocol
Cisco Port Aggregation Protocol
Nortel Multi-Link Trunking
Split MLT
Cisco Systems Port Aggregation Protocol
(pagp)
Nortel Multi-Link Trunk technology (mlt)
Split Multi-Link Trunk: configuration technology
(splitMlt)
Split Multi-Link Trunk: inter-switch trunk (istMlt) Inter-Switch Trunk MLT
802.3ad Link Aggregation Control
Protocol
Static/Manual Configured Link
Aggregation
IEEE 802.3ad Link Aggregation Control protocol
(LACP)
Static/Manual Configured Link Aggregation
Unknown Protocol Link Aggregation unknown
Note: It is possible for a Layer 2 Connection to connect sets of Aggregator/Member
Interfaces that are configured using different Link Aggregation protocols. In that case, this attribute value contains multiple protocols separated with a slash (/).
Available
Bandwidth
Maximum
Bandwidth
Sum of the interface Input Speed attribute values of the Member Interfaces that have a
MIB-II ifOperStatus that is not Down. If the sum of the interface Output Speed attribute values is different, NNMi displays separate Available Input Bandwidth and Available
Output Bandwidth attributes.
Sum of the interface Input Speed attribute values of the Member Interfaces, regardless of
MIB-II ifOperStatus. If the sum of the interface Output Speed attribute values is different, NNMi displays separate Maximum Input Bandwidth and Maximum Output
Bandwidth attributes.
1
Protocols 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).
2
Link Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link
Aggregation, SLAG, MLAG, or MC-LAG.
HPE Network Node Manager i Software (10.20)
Page 268 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Attribute Description
Available
Bandwidth
Percentage
Percentage value computed using Available Bandwidth divided by the Maximum
Bandwidth.
Members Table view of the Aggregation Members.
For more information, double-click the row representing an Aggregation Member: l
The
displays all details about the selected Interface.
l
The
"Layer 2 Connection Form" on page 255
displays all details about the selected
Layer 2 Connection.
Layer 2 Connection Form: Registration Tab
The
"Layer 2 Connection Form" on page 255
provides details about a managed connection.
For information about each tab:
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.
Note: 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: l
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.
l
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
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
HPE Network Node Manager i Software (10.20)
Page 269 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Chassis Redundancy Group Form
Chassis Redundancy Groups are configured to provide redundancy protection against Chassis failure.
The Chassis Redundancy Group form provides details about the Chassis Redundancy Group you selected.
The following table describes the fields included on the Chassis Redundancy Group form.
For information about each tab:
Basic Attributes
Attribute Description
Name
Status
Name assigned to the Chassis Redundancy Group. NNMi uses the Node Name followed by a slash and then the name that is specific to the Device Vendor:
Overall status for the current Chassis Redundancy Group. NNMi follows the ISO standard for status classification.
Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Note: The icons are displayed only in table views.
Status Last
Modified
The date and time when the Status value was last modified.
Chassis Redundancy Group Form: Redundant
Components Tab
Chassis Redundancy Groups are configured to provide redundancy protection against Chassis failures.
The
"Chassis Redundancy Group Form" above
provides details about the selected Chassis Redundancy
Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 270 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Redundant Group Member Chassis
Attribute Description
Redundant
Chassis
Table of all of the chassis that are members of this Chassis Redundancy Group. Use this table to access information about each chassis associated with the selected Chassis
Redundancy Group.
Double-click the row representing a Chassis. The
displays all details about the selected Chassis.
Note: Only parent Chassis can be members of this group, child Chassis are not permitted to participate in Chassis Redundancy Groups.
Chassis Redundancy Group Form: Incidents Tab
Chassis Redundancy Groups are configured to provide redundancy protection against Chassis failures.
The
"Chassis Redundancy Group Form" on the previous page
provides details about the selected Chassis
Redundancy Group.
For information about each tab:
Incidents Associated with Chassis in this Redundancy Group
Attribute Description
Incidents Table of the Incidents associated with the selected Chassis Redundancy Group.
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 Chassis
Redundancy Group.
Double-click the row representing an Incident. The
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Chassis Redundancy Group Form: Status Tab
Chassis Redundancy Groups are configured to provide redundancy protection against chassis failures.
The
"Chassis Redundancy Group Form" on the previous page
provides details about the selected Chassis
Redundancy Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 271 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Chassis Redundancy Group Status History Table
Attribute Description
Status
History
List of up to the last 30 changes in the status for the Chassis Redundancy Group. This table is useful for obtaining a summary of the Chassis Redundancy Group Status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The
"Chassis Redundancy Group Status
displays all details about the selected Status.
Chassis Redundancy Group Status History Form
Chassis Redundancy Group Status is derived from SNMP polling results for each Chassis in the Chassis
Redundancy Group, as well as any conclusions. For information about how the current Status was determined, see the
"Chassis Redundancy Group Form: Conclusions Tab" below . Status reflects the most
serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Status Attributes
Attribute Description
Status Overall status for the current Chassis Redundancy Group. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal (one Active card and one Standby card)
Disabled
Unknown
Warning
Minor
Major
Critical
Note: The icons are displayed only in table views.
Status Last
Modified
Date and time indicating when the Status was last set.
Chassis Redundancy Group Form: Conclusions Tab
Chassis Redundancy Groups are configured to provide redundancy protection against Chassis failures.
The
"Chassis Redundancy Group Form" on page 270
provides details about the selected Chassis
Redundancy Group.
HPE Network Node Manager i Software (10.20)
Page 272 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses for the Chassis Redundancy Group that contributed to the current overall Status of the selected Chassis Redundancy Group.
Status is set by the Causal Engine.
Each Conclusion listed is outstanding and contributes to the current overall Status.
This table is useful for obtaining a quick summary of the problem description for the current
Chassis Redundancy Group that led up to the Chassis Redundancy Group's most current
Status.
The Status value is correlated based on the most critical 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 Chassis
Redundancy Group object.
Note: Inter switch links (ISL) are Layer 2 connections that connect chassis. The interfaces in these connections are on the same node, but they are associated with ports on different chassis in a Chassis Redundancy Group.
Note: A Y in the Incident? column indicates that the conclusion results in an incident.
Major Status Conclusions
Conclusion Description
StackWithNoSlave No Chassis in the Chassis Redundancy
Group has a SLAVE State.
Status
Major
Incident?
Y
Minor Status Conclusions
Conclusion Description
StackDegraded NNMi has detected the following conditions in the Chassis Redundancy
Group: l
One Chassis with a MASTER State l l
One Chassis with a SLAVE State
Other Chassis in the group are not in
SLAVE State
ISLAggregatorLinkDown (NNMi Advanced) At least one of the
Status Incident?
Minor Y
Minor N
HPE Network Node Manager i Software (10.20)
Page 273 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
Inter Switch Links between Chassis in the Chassis Redundancy Group is down. See
Down (NNMi Advanced)" on page 496
for more information.
Status Incident?
Warning Status Conclusions
Conclusion Description
ISLAggregatorLinkDegraded (NNMi Advanced) At least one of the Inter Switch Links between
Chassis in the Chassis
Redundancy Group is degraded.
See
Degraded (NNMi Advanced)" on page 495
for more information.
Status Incident?
Warning N
Card Redundancy Group Form
Card Redundancy Groups are configured to provide one-to-one redundancy protection against processor card failure.
The Card Redundancy Group form provides details about the Card Redundancy Group you selected. The following table describes the fields included on the Card Redundancy Group form.
For information about each tab:
Basic Attributes
Attribute Description
Name Name assigned to the Card Redundancy Group. NNMi uses the Node Name followed by a slash and then the name that is specific to the Device Vendor:
Card Redundancy Group Naming Conventions
Device
Vendor Naming Convention
Cisco <nodename>/Supervisor Engine Group
Note: Only cards classified as Management Modules are
HPE Network Node Manager i Software (10.20)
Page 274 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Card Redundancy Group Naming Conventions, continued
considered for Card Redundancy Groups.
HPE ProCurve <nodename>/Management Module Group
Note: Only cards classified as Management Modules are considered for Card Redundancy Groups.
Status Overall status for the current Card Redundancy Group. NNMi follows the ISO standard for status classification.
Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Note: The icons are displayed only in table views.
Status Last
Modified
The date and time when the Status value was last modified.
Card Redundancy Group Form: Redundant
Components Tab
Card Redundancy Groups are configured to provide redundancy protection against processor card failures.
The
"Card Redundancy Group Form" on the previous page
provides details about the selected Card
Redundancy Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 275 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Redundant Group Member Cards
Attribute Description
Redundant
Cards
Table of all of the Physical Component: Cards that are members of this Card Redundancy
Group. Use this table to access information about each card associated with the selected
Card Redundancy Group.
Double-click the row representing a Card. The
displays all details about the selected Card.
Note: Only parent cards can be members of this group, child cards are not permitted to participate in Card Redundancy Groups.
Card Redundancy Group Form: Incidents Tab
Card Redundancy Groups are configured to provide redundancy protection against processor card failures.
The
"Card Redundancy Group Form" on page 274
provides details about the selected Card Redundancy
Group.
For information about each tab:
Incidents Associated with Cards in this Redundancy Group
Attribute Description
Incidents Table of the Incidents associated with the selected Card Redundancy Group.
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 Card
Redundancy Group.
Double-click the row representing an Incident. The
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Card Redundancy Group Form: Status Tab
Card Redundancy Groups are configured to provide redundancy protection against processor card failures.
The
"Card Redundancy Group Form" on page 274
provides details about the selected Card Redundancy
Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 276 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Card Redundancy Group Status History Table
Attribute Description
Status
History
List of up to the last 30 changes in the status for the Card Redundancy Group. This table is useful for obtaining a summary of the Card Redundancy Group Status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The
displays all details about the selected Status.
Card Redundancy Group Status History Form
Card Redundancy Group Status is derived from SNMP polling results for both cards in the Card Redundancy
Group, as well as any conclusions. For information about how the current Status was determined, see the
"Card Redundancy Group Form: Conclusions Tab" below . Status reflects the most serious outstanding
conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Status Attributes
Attribute Description
Status Overall status for the current Card Redundancy Group. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal (one Active card and one Standby card)
Disabled
Unknown
Warning
Minor
Major
Critical
Note: The icons are displayed only in table views.
Status Last
Modified
Date and time indicating when the Status was last set.
Card Redundancy Group Form: Conclusions Tab
Card Redundancy Groups are configured to provide redundancy protection against processor card failures.
The
"Card Redundancy Group Form" on page 274
provides details about the selected Card Redundancy
Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 277 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses for the Card Redundancy Group that contributed to the current overall Status of the selected Card Redundancy Group. Status is set by the Causal Engine.
Each Conclusion listed is outstanding and contributes to the current overall Status.
This table is useful for obtaining a quick summary of the problem description for the current
Card Redundancy Group that led up to the Card Redundancy Group's most current Status.
The Status value is correlated based on the most critical 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 Card
Redundancy Group object.
Note: A Y in the Incident? column indicates that the conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
CrgMultiplePrimary NNMi has identified multiple Primary Cards
(for example, Card Active) in the Card
Redundancy Group. This typically indicates the communication between the cards in the group is malfunctioning.
CrgNoPrimary
Status
Critical
Incident?
Y
NNMi is unable to identify a Primary Card
(for example, Card Active) in the Card
Redundancy Group. This typically indicates one of the following: l
One card, or both the Primary and
Secondary Cards, are down.
l
NNMi has identified only Secondary cards
(for example Standby cards) in the group.
l
Communication between cards in the group is malfunctioning.
Critical Y
Warning Status Conclusions
Conclusion Description
CrgNoSecondary A Card Redundancy Group does not have a secondary member. Neither card has a cardStandbyStatus equal to Standby. A
Status Incident?
Warning Y
HPE Network Node Manager i Software (10.20)
Page 278 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
properly functioning Card Redundancy Group should have one operational Primary Card and one operational Secondary Card.
Status Incident?
Unknown Status Conclusions
Conclusion Description
CrgUnmanagable The SNMP Agent on the node hosting the
Card Redundancy Group is not responding to SNMP queries.
Status Incident?
Unknown N
Normal Status Conclusions
Conclusion Description Status Incident?
CrgFailback The initial Primary Card is now active. This conclusion can occur only when a failover has occurred and then the Card Redundancy Group has returned to its previous state.
Normal N
CrgNormal The Card Redundancy Group is operating normally.
It has one card operating as the Primary Card and the other acting as the Secondary Card.
Normal N
CrgFailover The Primary Card (for example, Card Active) has moved from one card to the other in a Card
Redundancy Group. The Card Redundancy Group is routing packets properly.
Normal Y
Router Redundancy Group Form (
NNMi
Advanced
)
The Router Redundancy Group Form provides details about the Router Redundancy Group selected. This form is useful for troubleshooting purposes. You can access information about the name, status, and Router
Redundancy Members (routers) associated with this Router Redundancy Group.
Note: All members of a Router Redundancy Group must be assigned to the same Tenant (visible in the
Node form's
and in the Tenants column of the
Inventory > Nodes view ). The NNMi
administrator configures the Tenants.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 279 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes
Attribute Description
Name
Tenant
Status
The name assigned to this Router Redundancy Group. This name is the virtual IP address protected by this group and used by the router that is actively routing information packets (for example, HSRP Active or VRRP Master).
Tenants enable NNMi administrators to partition a network across multiple customers. The
NNMi administrator controls the Tenant assignment for each Node. All Nodes in the Router
Redundancy Group must be assigned to the same Tenant.
A Tenant is the top-level organization to which a n=Node belongs.
Router Redundancy Group Status reflects the most serious Severity value of the incidents associated with the Router Redundancy Group. Possible values are:
Normal
Warning
Minor
Major
Critical
See
"Watch Status Colors" on page 406
for more information about Severity values.
Note: The icons are displayed only in table views.
Status
Last
Modified
Date and time indicating when the Status was last set.
Protocol The protocol in use for the selected Router Redundancy Group. For example: Virtual Router
Redundancy Protocol (
VRRP
1
) or Hot Standby Router Protocol (
HSRP
2
) .
Group
Number
The group number that was configured for the current Router Redundancy Group.
Number of
Members
Specifies the number of members that belong to the current Router Redundancy Group.
Related Topics
"Router Redundancy Group View" on page 402
1
Virtual Router Redundancy Protocol
2
Hot Standby Router Protocol
HPE Network Node Manager i Software (10.20)
Page 280 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Router Redundancy Group Form: Router
Redundancy Members Tab ( NNMi Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about the selected
Router Redundancy Group.
Note: All members of a Router Redundancy Group must be assigned to the same Tenant (visible in the
Node form's
and in the Tenants column of the
Inventory > Nodes view ). The NNMi
administrator configures the Tenants.
For information about each tab:
Router Redundancy Members in this Router Redundancy Group
Attribute Description
Router
Redundancy
Members
Table of all of the routers that are members of the selected Router Redundancy Group. The table lists each router's interface that is associated with this Router Redundancy Group.
Use this table to access information about each router.
Double-click the row representing a Router Redundancy Member. The
Member Form (NNMi Advanced)" below
displays all details about the selected Router
Redundancy Member.
Router Redundancy Member Form ( NNMi Advanced )
The Router Redundancy Member form provides details about a router in the Router Redundancy Group.
This form is useful for troubleshooting purposes. You can access information about the router name and status, as well as conclusions information to assist you in understanding the router's current state. You can also see the name of each tracked object associated with the router. A tracked object represents the interface responsible for delivering the outbound information packet that was originally sent to the current Router
Redundancy Member.
For information about each tab:
Basics Attributes
Attribute Description
Name Name of the selected router and its associated interface that is a member of the current
Router Redundancy Group.
Note: NNMi determines this Name value.
The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.
This name appears in the following format:
HPE Network Node Manager i Software (10.20)
Page 281 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Primary IP
<fully qualified hostname assigned to the router>[Interface Name:group_number]
For example: HSRPRouter1.abc.example.com[Se1/1:1]
See
for more information about node names. See
for more information about interface names.
The IP Address used to exchange messages between routers in the Router Redundancy
Group.
Is Owner
Priority
Boolean attribute used to Indicate whether the selected router owns a Virtual IP Address (if any) for the Router Redundancy Group. See
"Virtual IP Addresses Form (NNMi Advanced)" on page 287
for more information.
If the selected router uses a Router Redundancy Protocol that does not support virtual addresses, the value is set to false.
The configured protocol-specific number that indicates the current rank of the Router
Redundancy Member.
Redundancy
Interface
The interface that is being used by the router to participate in the Router Redundancy Group.
To find out more information about this Interface:
Hosted on
Node
Click the Lookup icon and choose one of the following options: l
Show Analysis to view the Analysis Pane information for the selected interface. (See
"Use the Analysis Pane " on page 482
for more information about the Analysis Pane.) l
Open to open the Interface form.
Name attribute value from the
of the selected router (the Router
Redundancy Group member).
To find out more information about the Node:
Click the l
Lookup icon and choose one of the following options: l
Show Analysis to view the Analysis Pane information for the selected interface. (See
"Use the Analysis Pane " on page 482
for more information about the Analysis Pane.)
Open to open the Node form.
Redundancy
Group
Name of the Router Redundancy Group to which the Router Redundancy Member belongs.
To find out more information about the Router Redundancy Group:
Current
Click the Lookup icon and choose one of the following options: l
Show Analysis to view the Analysis Pane information for the selected interface. (See
"Use the Analysis Pane " on page 482
for more information about the Analysis Pane.) l
Open to open the Router Redundancy Group form.
State of the Router Redundancy Member. State values are protocol-specific. For example:
HPE Network Node Manager i Software (10.20)
Page 282 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
State l
Hot Standby Router Protocol (HSRP) States:
click here .
Active - Indicates the router is forwarding packets that are sent to the router redundancy group.
Standby - Indicates the router is a candidate to become the next active router.
Initial - Indicates
HSRP
1
is not running. This state occurs when an interface first comes up.
Learn - Indicates the router has not yet determined the virtual IP address. This state occurs when the router is waiting to hear from the active router.
Listen - Indicates the router knows the virtual IP address, but it is neither the active nor standby router. In this state, the router is waiting for a message from the active and standby routers.
Speak - Indicates the router knows the virtual IP address. In this state, the router sends periodic messages and is ready to become an active or standby router.
l
Virtual Router Redundancy Protocol (VRRP) States:
click here .
Master - Indicates the router is forwarding packets that are sent to the router redundancy group.
Backup - Indicates the router is a candidate to become the next master router.
Initialize - Indicates the router is not running VRRP protocol. This state occurs when an interface first comes up.
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.
Other – The SNMP agent responded with a value for the MIB variable used to determine the Router Redundancy Member State that is not recognized.
1
Hot Standby Router Protocol
HPE Network Node Manager i Software (10.20)
Page 283 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Previous
State
State Last
Modified
The previous State of the Router Redundancy Member. State values are protocol-specific.
For examples, see
.
Date and time the Router Redundancy State was last modified.
Router Redundancy Member Form: Tracked Objects Tab ( NNMi
Advanced )
A tracked object is the outbound interface responsible for delivering the outbound information packet that was originally sent to a selected inbound interface on a router that is part of the Router Redundancy Group. A
Router Redundancy Member can have one or more associated tracked objects
The
"Router Redundancy Member Form (NNMi Advanced)" on page 281
provides details about the selected
Router Redundancy Member. Each Router Redundancy Member is a router in the Router Redundancy Group.
For information about each tab:
See
"Tracked Objects Form (NNMi Advanced)" on the next page
for more information about tracked objects.
Tracked Objects Table
Attribute Description
Name Name of the selected router and its associated interface that is a member of the current Router
Redundancy Group.
Note: NNMi determines this Name value.
The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.
This name appears in the following format:
<fully qualified hostname assigned to the router>[Interface Name]
For example:
HSRPRouter1.abc.example.com[Se1/1]
Note: NNMi determines this Name value. See
for more information about node names. See
for more information about interface names.
Track
Priority
Number NNMi uses to rank the tracked object whenever a
change occurs. NNMi uses this number indirectly in the calculation to determine the next Primary member of the
Router Redundancy Group.
When a tracked object goes down, the priority of the tracked object (Track Priority) is subtracted from its Router Redundancy Member Priority value to produce a smaller member
Priority number. If this new Priority number is smaller than one of the other member Priority
HPE Network Node Manager i Software (10.20)
Page 284 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Tracked Objects Table, continued
Attribute Description
numbers, the member with the highest Priority value becomes the new Primary router in the
Router Redundancy Group.
For example, if an interface that has a Track Priority of 20 goes down on a Router Redundancy
Member that has a member Priority of 250: l
The Track Priority (20) is subtracted from its member Priority (250-20=230).
l
The new member Priority (230) is then compared to the Priority value of the other members in the Router Redundancy Group.
l
If one of the members in the Router Redundancy Group has a higher member Priority, for example, 240, that member becomes the Primary router in the group (for example,
HSRP Active or VRRP Master).
State
Last
Modified
The date and time when the State value was last modified.
Tracked Objects Form ( NNMi Advanced)
Your network administrator might have set up groups of redundant routers to help ensure that information packets reach their intended destination. A tracked object is the outbound interface responsible for delivering the outbound information packet that was originally sent to a selected inbound interface on a router that is part of the Router Redundancy Group. A Router Redundancy Member can have one or more associated tracked objects.
Basics Attributes
Attribute Description
Name Name used to identify the selected Tracked Object. The name includes the fully-qualified
DNS name assigned to the Router and the name assigned to its associated Tracked Object .
Note: NNMi determines this Name value.
The name includes the fully-qualified DNS hostname assigned to the router and the Name attribute value that NNMi assigned to the interface.
This name appears in the following format:
<fully qualified hostname assigned to the router>[Interface Name]
For example: HSRPRouter1.abc.example.com[Se1/1]
See
for more information about node names. See
for more information about interface names.
To find out more information about this interface:
Click the l
Lookup icon and choose one of the following options:
Show Analysis to view the Analysis Pane information for the selected Tracked Object.
HPE Network Node Manager i Software (10.20)
Page 285 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Track
Priority l
(See
"Use the Analysis Pane " on page 482
for more information about the Analysis Pane.
Open to open the Interface form.
Number used to rank the tracked object. This number is used indirectly in the calculation that determines the next Active or Master member of the Router Redundancy Group whenever a
State change occurs.
When a tracked object goes down, the priority of the tracked object (Track Priority) is subtracted from its Router Redundancy Member Priority value to produce a smaller member
Priority number. If this new Priority number is smaller than one of the other member Priority numbers, the member with the highest Priority value becomes the new Master or Active router in the current Router Redundancy Group.
For example, if an interface that has a Track Priority of 20 goes down on a Router Redundancy
Member that has a member Priority of 250: l
The Track Priority (20) is subtracted from its member Priority (250-20=230).
l
The new member Priority (230) is then compared to the Priority value of the other members in the Router Redundancy Group.
l
If one of the members in the Router Redundancy Group has a higher member Priority, for example, 240, that member becomes the Active or Master router in the group.
State
Last
Modified
Date and time the Tracked Object State was last modified.
Router Redundancy Group Form: Virtual IP
Addresses Tab ( NNMi Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about the selected
Router Redundancy Group.
For information about each tab:
Virtual IP Addresses Table
Attribute Description
Virtual IP
Addresses
Table view of the virtual IP addresses associated with the selected Router Redundancy
Group. The virtual IP address is the IP address protected by this group and used by any router that is actively routing information packets (for example, VRRP Master). For each virtual IP address displayed, you can see the IP address value.
Double-click the row representing a Virtual IP Address. The
(NNMi Advanced)" on the next page
displays all details about the selected Virtual IP Address.
HPE Network Node Manager i Software (10.20)
Page 286 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Virtual IP Addresses Form (
NNMi Advanced
)
A virtual IP address is an address protected by the Router Redundancy Group and used by the router that is actively routing information packed (for example, VRRP Master).
Basic Attributes
Virtual IP Addresses
Attribute Description
Value IP address value for the virtual IP address.
Router Redundancy Group Form: Incidents Tab
( NNMi Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about the selected
Router Redundancy Group.
For information about each tab:
Incidents Associated with this Router Redundancy Group
Attribute Description
Incidents Table of the Incidents associated with the selected Router Redundancy Group.
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 Router
Redundancy Group.
Double-click the row representing an Incident. The
displays all details about the selected incident.
Tip: See
for more details about the incident attributes that appear in the incident table's column headings.
Router Redundancy Group Form: Status Tab (
NNMi
Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about the selected
Router Redundancy Group.
For information about each tab:
HPE Network Node Manager i Software (10.20)
Page 287 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Router Redundancy Group Status History Table
Attribute
Description
Status
History
List of up to the last 30 changes in the status for the Router Redundancy Group. This table is useful for obtaining a summary of the Router Redundancy status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The
"Router Redundancy Group Status
History Form (NNMi Advanced)" below
displays all details about the selected Status.
Router Redundancy Group Status History Form ( NNMi
Advanced
)
Router Redundancy Group Status is derived from SNMP polling results, as well as any conclusions. For information about how the current Status was determined, see the
"Router Redundancy Group Form:
Conclusions Tab (NNMi Advanced)" on the next page
. Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Status Attributes
Attribute Description
Status Overall status for the current Router Redundancy Group. NNMi follows the ISO standard for status classification. Possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
Critical
Note: The icons are displayed only in table views.
Status Last
Modified
Date and time indicating when the Status was last set.
HPE Network Node Manager i Software (10.20)
Page 288 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Router Redundancy Group Form: Conclusions Tab
( NNMi Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about the selected
Router Redundancy Group.
All relevant conclusions are shown in the table on this tab. The most severe Status in the current group of conclusions becomes the overall Router Redundancy Group status:
For information about each tab:
Outstanding Status Conclusion Values
Attribute Description
Outstanding
Status
Conclusions
The dynamically generated list of summary statuses for the Router Redundancy Group that contributed to the current overall Status of the selected Router Redundancy Group. Status is set by the Causal Engine.
Each Conclusion listed is outstanding and contributes to the current overall Status.
This table is useful for obtaining a quick summary of the problem description for the current
Router Redundancy Group that led up to the Router Redundancy Group's most current
Status.
The Status value is correlated based on the most critical 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 Router
Redundancy object.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
Critical Status Conclusions
Conclusion Description
RrgNoPrimary No primary device is identified in a Router
Redundancy Group (for example, zero routers reporting HSRP Active or VRRP Master). This incident typically indicates one of the following: l l
Too many routers are down.
Protocol-specific communication between routers in the group is malfunctioning.
Major Status Conclusions
Status Incident?
Critical Y
HPE Network Node Manager i Software (10.20)
Page 289 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description Status Incident?
RrgMultiplePrimary Indicates that more than one router in a
Router Redundancy Group is designated as
Primary (for example, two routers reporting
HSRP Active or VRRP Master). This incident typically indicates the protocol-specific communication between routers in the group is malfunctioning.
Major Y
Minor Status Conclusions
Conclusion Description
RrgMultipleSecondary Indicates that more than one secondary device is identified in a Router
Redundancy Group (for example, HSRP
Standby).
Status Incident?
Minor Y
Note: This incident applies only to
Router Redundancy Groups that allow only one secondary member.
Typically, the protocol-specific communication between routers in the group is malfunctioning.
RrgNoSecondary
Typically, the protocol-specific communication between routers in the group is malfunctioning.
Indicates that zero routers in a Router
Redundancy Group are designated as
Secondary (for example, no router reporting HSRP Standby or VRRP
Backup).
This incident typically indicates the following: l l
Protocol-specific communication between routers in the group is malfunctioning.
The group is routing packets properly because a single Primary device has been identified.
Warning Status Conclusions
Minor Y
HPE Network Node Manager i Software (10.20)
Page 290 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
RrgGroupContainsUnmanagedMember At least one, but not all
SNMP Agents, associated with the member interfaces are not responding to
SNMP queries or are not polled.
RrgDegraded
Status
Warning
Incident?
N
This incident occurs only in Router
Redundancy Groups with more than two members. This incident typically indicates the following: l
The Router
Redundancy Group has a Primary and
Secondary device.
l l
The remaining devices in the group are not in an expected protocolspecific state (for example, zero routers reporting
HSRP Listen state).
Typically, the protocol-specific communication between routers is malfunctioning.
However, the group is routing packets properly.
Warning Y
Unknown Status Conclusions
Conclusion Description
RrgGroupAllMembersUnmanaged The SNMP Agent associated with all Router
Status Incident?
Unknown N
HPE Network Node Manager i Software (10.20)
Page 291 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Conclusion Description
Redundancy Group member's interfaces are not responding to SNMP queries or are not polled.
Status Incident?
Normal Status Conclusions
Conclusion Description
RrgOnePrimary At least one member of the Router Redundancy
Group is acting as a Primary router.
Status Incident?
Normal N
Router Redundancy Group Form: Registration Tab
(
NNMi Advanced)
The
"Router Redundancy Group Form (NNMi Advanced)" on page 279
provides details about a managed connection.
For information about each tab:
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.
Note: 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: l
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.
l
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.
HPE Network Node Manager i Software (10.20)
Page 292 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Object Identifiers Attributes
Attribute Description
ID
UUID
The Unique Object Identifier, which is unique within the NNMi database.
The Universally Unique Object Identifier, which is unique across all databases.
Node Group Form
Note: Island Node Groups are a special kind of Node Group that NNMi manages internally. Therefore,
NNMi administrators should not modify Island Node Group configurations. NNMi overrides any user changes the next time NNMi updates the Island Node Group discovery information. See "Help for
Administrators" for more information about Island Node Groups.
Membership in each node group is determined by a number of factors specified on the Node Group form. The
NNMi administrator can create and modify Node Group definitions. The NNMi administrator can also configure
Node Groups as filters for views
. NNMi monitors the status of each Node Group over time. NNMi also provides a map of each Node Group (Actions → Node Group Map).
Each Node Group definition includes one or more of the following: l
Device Filters (by any combination of category, vendor, family, profile) l
Additional Filters (based on current object attribute values in the NNMi database) l l
Additional Nodes (specific nodes identified by case-sensitive Hostname)
Child Node Groups nest into this Node Group.
For information about each tab:
Tip:
Special Actions are available within the Node Group view and Interface Group view.
If you are an NNMI administrator, you can create Node Groups and use Node Groups in several ways:
Node Group Basic Settings
Attribute Description
Name The name of this group (text string specified by the NNMi administrator). This name is a maximum of 255 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & *
( ) _+ -) are permitted.
Calculate
Status
NNMi Administrators only.
If disabled , NNMi does not calculate the Status for this Node Group. NNMi sets the Node
Group Status value to No Status.
Status
If enabled , NNMi calculates the Node Group Status according to the Status Configuration settings. See "Configure Node Group Status" for more information.
Overall status for the specified node group. NNMi follows the ISO standard for status
HPE Network Node Manager i Software (10.20)
Page 293 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Node Group Basic Settings, continued
Attribute Description
classification. See the
"Node Group Form: Status Tab" on page 300
for more information.
Add to
View
Filter List
NNMi Administrators only.
If disabled , this node group does not appear in any node group filter lists for node, interface,
IP address, and incident views.
Notes
If enabled , this node group is available as a filter for all node, interface, IP address, and incident views.
Optional. If your role permits, enter any information that might be useful to you and your team.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
NNM iSPI Performance
Attribute Description
Add to
Filter List
NNMi Administrators only.
Using this feature is entirely optional. The NNM iSPI Performance software, such as NNM iSPI
Performance for Metrics or NNM iSPI Performance for Traffic, can monitor your network without any exported filter.
Enable only for groups that are needed as filters in NNM iSPI Performance reports. It might take up to an hour before the results are visible in the NNM iSPI Performance reports. Choose wisely because establishing a filter requires significant NNM iSPI Performance software processing time.
If disabled , this group is not available as a filter in NNM iSPI Performance reports.
If enabled , this group appears in the Optional Filters selection panel of the NNM iSPI
Performance reports.
Requires HPE Network Node Manager iSPI Performance for Metrics Software (NNM iSPI
Performance for Metrics) -click here for more information .
Requires HPE Network Node Manager iSPI Performance for Traffic Software (NNM iSPI
Performance for Traffic) -click here for more information .
Node Group Form: Device Filters Tab ( NNMi
Administrators only)
Optional: Determine Node Group members by vendor, family, model, or other device characteristics such as
SNMP object identifiers.
NNMi combines the results of all Node Group configuration settings in the following manner:
HPE Network Node Manager i Software (10.20)
Page 294 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details l l l
NNMi first evaluates Device Filters. If any exist, nodes must match at least one specification to belong to this Node Group.
NNMi then evaluates any Additional Filters. Nodes must also pass all Additional Filters specifications to belong to this Node Group.
Any Additional Nodes specified are always included in the Node Group, regardless of any filters.
l
Any Child Node Group results are treated the same as Additional Nodes.
Note: The
provides details about the selected node group.
For information about each tab:
Device-Characteristic Filters Table
Attribute Description
Device
Filter
Table view of the device category, vendor, product family, or product model filters associated with the selected node group.
Double-click the row representing the node that has the
"Node Device Filter Form (NNMi
you want to see.
Node Device Filter Form ( NNMi Administrators only )
Optional: Node Group definitions can specify membership using combinations of Device Profile attributes for device category, vendor, family, and profile. If you provide more than one Node Device Filter specification for a particular Node Group, the Node Group includes devices that pass any one of the Device Filters.
NNMi combines the results of all Node Group configuration settings in the following manner: l
NNMi first evaluates Device Filters. If any exist, nodes must match at least one specification to belong to this Node Group.
l
NNMi then evaluates any Additional Filters. Nodes must also pass all Additional Filters specifications to belong to this Node Group.
l
Any Additional Nodes specified are always included in the Node Group, regardless of any filters.
l
Any Child Node Group results are treated the same as Additional Nodes.
Each Node Device Filter specifies one or more criteria that devices must meet to qualify for inclusion in the
Node Group (see table below). If more than one criteria, devices must meet all of the criteria to pass that Node
Device Filter and join the Node Group.
Device Attribute Filters Table
Attribute Description
Device
Category
Optional: A particular category of devices. The drop-down list displays all available choices.
Optional: A particular vendor. The drop-down list displays all available choices.
Device
Vendor
Device
Family
Optional: A particular family of devices. The drop-down list displays all available choices.
HPE Network Node Manager i Software (10.20)
Page 295 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Device Attribute Filters Table , continued
Attribute Description
Device
Category
Optional: A particular category of devices. The drop-down list displays all available choices.
Device
Profile
Optional: The text string for Device Model from the Device Profile.
Tip: According to industry standards (RFC 1213, MIB-II), each combination of vendor, category, and model is assigned a unique SNMP system object ID number (sysObjectID).
NNMi provides a Device Profile for each of these. The Device Profile allows you to customize NNMi behavior for specific device models. If you want to know the actual
SNMP system object ID number, use Quick Find (see below).
l l
If your role permits, click the down menu:
Lookup icon and select one of the options from the dropl
Show Analysis to view Analysis Pane information for the currently selected Device
Profile. (See
"Use the Analysis Pane " on page 482
for more information about the Analysis
Pane.) l
Quick Find to view and select from the list of all existing Device Profiles.
Open to display the details of the currently selected Device Profile.
New to create a new Device Profile definition.
Node Group Form: Additional Filters Tab ( NNMi
Administrators only)
Note: The Additional Filters Editor requires that your user name be assigned a role of Administrator. If you are an NNMi Administrator, see Specify Node Group Additional Filters for more information about how to use the Additional Filters editor.
The Additional Filters tab enables the NNMi administrator to use expressions to refine the requirements for membership in a Node Group.
NNMi combines the results of all Node Group configuration settings in the following manner: l
NNMi first evaluates Device Filters. If any exist, nodes must match at least one specification to belong to this Node Group.
l
NNMi then evaluates any Additional Filters. Nodes must also pass all Additional Filters specifications to belong to this Node Group.
l l
Any Additional Nodes specified are always included in the Node Group, regardless of any filters.
Any Child Node Group results are treated the same as Additional Nodes.
Note: The
provides details about the selected Node Group.
HPE Network Node Manager i Software (10.20)
Page 296 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
For information about each tab:
If an NNMi administrator created any Additional Filters for the selected Node Group, NNMi displays the
Additional Filters expression.
Node Group Form: Additional Nodes Tab ( NNMi
Administrators only)
Optional: Determine Node Group members by specifying each device hostname (or address when hostname is not available).
Nodes that are specifically listed are always included in this node group.
The
provides details about the selected node group.
For information about each tab:
Specific-Device Filters Table
Attribute Description
Node
Hostname
Table view of the case-sensitive Hostnames for the additional nodes added as members of the selected Node Group.
Double-click the row representing the node that has the
you want to see.
Additional Node Form (
NNMi Administrators only
)
Optional: Node Group definitions can specify members by case-sensitive Hostname (on the
Form: Additional Nodes Tab (NNMi Administrators only)" above
.
Nodes that are specified as Additional Nodes are always included in the Node Group.
Tip: To add more than a few additional nodes to the Node Group, create a Custom Attribute for the nodes. Use the Additional Filters tab with the Custom Attribute value to group the nodes together. See
"Custom Node Attribute Samples" on page 88
and Add Custom Attributes to Multiple Objects for more information.
Specific Node Group Member
Attribute Description
Node
Hostname
The current value of the fully-qualified, case-sensitive Hostname attribute as it appears on the
Node form.
NNMi follows a set of rules to dynamically generate the value stored in the NNMi database for each Node's Hostname.
Click here for details.
l
If the Node supports SNMP, NNMi requests the Hostname using the IP Address of the associated SNMP agent (the Management Address attribute value on the Node form).
When the NNMi administrator chooses Enable SNMP Address Rediscovery in the
HPE Network Node Manager i Software (10.20)
Page 297 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Specific Node Group Member, continued
Attribute Description
Communication Configuration: l
If the SNMP Agent does not respond, NNMi checks for another Management Address to request the Hostname, and the Hostname could change.
l
If the SNMP Agent associated with the node changes, the Management Address and
Hostname could change.
l
When the NNMi administrator disables Enable SNMP Address Rediscovery in the
Communication Configuration, when the current management address (SNMP agent) becomes unreachable, NNMi does not check for other potential management addresses.
If the Node does not support SNMP, no Management Address is available. NNMi requests a Hostname starting with the lowest IP Address associated with the node (a Discovery
Seed value or an IP address value gathered from a neighboring device). NNMi uses the first
Hostname provided. The Hostname might change during a future discovery cycle.
Note: NNMi administrators can use NNMi property file settings to change the way NNMi determines Hostname values: l nms-topology.properties file settings:
If DNS is the source of the Node's Hostname, there are three choices. By default
NNMi uses the exact Hostname from your network configuration. It is possible to change NNMi behavior to convert Hostnames to all uppercase or all lowercase. See the "Modifying NNMi Normalization Properties" section of the HPE Network Node
Manager i Software Deployment Reference, which is available at: http://softwaresupport.hpe.com.
l nms-disco.properties file settings:
The Hostname is either requested from the Node's lowest loopback interface IP address that resolves to a Hostname or requested from the Node's designated
Management Address (SNMP agent address). With either choice, when no IP address resolves to a Hostname, the IP address itself becomes the Hostname. See the
"Maintaining NNMi" chapter of the HPE Network Node Manager i Software
Deployment Reference, which is available at: http://softwaresupport.hpe.com.
See
"Access Node Details" on page 409
and Access More Details (Forms and Analysis Pane) for a description of the ways to verify node details.
Node Group Form: Child Node Groups Tab ( NNMi
Administrators only)
The
provides details about the selected Node Group.
A set of Node Groups can be hierarchically configured, for example, based on geographical location. The
Parent Node Group might be named North America to represent all of the nodes on that continent. Additional
Node Groups might exist for each country in which your business offices reside (for example Canada,
HPE Network Node Manager i Software (10.20)
Page 298 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Mexico and United States). Each of these individual Node Groups are configured as a Child Node Group of the North AmericaNode Group.
For information about each of the columns displayed in the Child Node Groups table, see
Hierarchy (Child Node Group) Form (NNMi Administrators only)" below .
By default, each Child Node Group is represented by a hexagon symbol that appears with the other Node objects of the Parent Node Group in the Node Group Map. Child Node Group objects can be moved and have their locations saved with other Node objects in the map. Unlike other Node objects, double-clicking a Child
Node Group object displays a map of the nodes in the Child Node Group rather than the object's form.
Alternatively, an NNMi administrator can configure the map to display all nodes in a Child Node Group as though its contents are directly in the Parent Node Group by setting the Expand Child in Parent Node
Group Map attribute. An NNMi administrator must set this option for each Child Node Group that should be expanded. See
"Node Group Hierarchy (Child Node Group) Form (NNMi Administrators only)" below
for more information.
For information about each tab:
Related Topics
"Navigating within a Node Group Map" on page 370
"Position Nodes on a Node Group Map" on page 372
Node Group Hierarchy (Child Node Group) Form (
NNMi
Administrators only )
Child Node Groups associate groups of nodes in a hierarchical order. For example, the Parent Node Group might be named United States to represent all of the nodes in the United States. Additional Node Groups might exist for each state in which your business offices reside (for example Colorado and California). Each of these individual state Node Groups can be a Child Node Group of the United States Node Group.
The following table describes each of the Basics attributes in the Node Group Hierarchy form.
Basics Attributes
Attribute Description
Child Node
Group
Indicates the name of a Node Group that is below the current Node Group in the hierarchical order. For example, Colorado could be a Child Node Group to a Node
Group named United States.
Note: This attribute appears as the Name column in the Child Node Groups table view.
Expand Child in
Parent Node
Group Map
Used to indicate whether all of the nodes contained in a Child Node Group are displayed in the Node Group Map as though they were directly contained in the parent node group.
If enabled, each node in the group appears as a separate node on the Node Group Map.
HPE Network Node Manager i Software (10.20)
Page 299 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basics Attributes, continued
Attribute Description
Child Node
Group
Indicates the name of a Node Group that is below the current Node Group in the hierarchical order. For example, Colorado could be a Child Node Group to a Node
Group named United States.
Note: This attribute appears as the Name column in the Child Node Groups table view.
If disabled, a single object represents a Child Node Group on the Node Group Map.
Note the following: l
If the current Node Group has one or more Child Node Groups, each Child Node
Group is also displayed. Child Node Groups are indicated using a hexagon as shown below: l
If any Child Node Group is a parent to other Child Node Groups, those Child Node
Groups are also displayed on the map as follows: l
If the Child Node Group has the Expand Child in Parent Node Group Map attribute disabled, the Child Node Group appears as a hexagon.
l
If any Child Node Group has the Expand Child in Parent Node Group Map attribute enabled, NNMi displays each of the nodes in that Child Node Group.
Note: This attribute appears in the Expand column in the Child Node Groups table view.
Related Topics
"Position Nodes on a Node Group Map" on page 372
Node Group Form: Status Tab
NNMi calculates the Node Group status based on the status of the nodes within the group. NNMi follows the
ISO standard for status classification. Your NNMi administrator chooses a strategy for calculating Node
Group Status. Possible strategies are: l
Propagating the Most Severe Status l
Configuring percentage thresholds
By default, NNMi uses the strategy for Propagating the Most Severe Status. NNMi sets the Node Group status equal to the most severe Status of any node in the Node Group.
When propagating Node Group status, NNMi uses the following severity order (from lowest to highest):
No Status
HPE Network Node Manager i Software (10.20)
Page 300 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Normal
Unknown
Warning
Minor
Major
Critical
NNMi can also use the alternative Percentage threshold strategy. NNMi sets the Node Group status according to rules defined by your NNMi Administrator. When more than one Status percentage exceeds the threshold, NNMi propagates the most severe status. For example using the settings below, if the percentage of nodes with Warning Status exceeds 30 percent and the number of nodes with Minor Status exceeds
20 percent, NNMi assigns the Node Group a Status of Minor.
The following list shows an example of using the alternative Percentage strategy:
No Status — The Node Group has just been added and NNMi has not yet calculated the status.
Normal — All nodes in the Node Group have a status of Normal or the threshold specified for this Target
Status has not been reached.
Unknown — All nodes within the Node Group have a status of Unknown.
Warning — At least 30 percent of the nodes within the Node Group have a status of Warning.
Minor — At least 20 percent of the nodes in the Node Group have a Status of Minor.
Major — At least 10 percent of the nodes within the Node Group have a status of Major.
Critical — At least 5 percent of the nodes in the group have a status of Critical.
Note: These example percentages might not match your NNMi Administrator's choices. See "Help for
Administrators" for more information.
The
provides details about the selected Node Group.
For information about each tab:
Status Attributes
Attribute Description
Status NNMi calculates the Node Group status based on the status of the nodes within the group.
Your NNMi administrator chooses a strategy for calculating Node Group Status. Possible strategies are: l
Propagating the Most Severe Status (NNMi default setting) l
Configuring percentage thresholds
Possible status values are as follows. See
"Watch Status Colors" on page 406
for more information about the meaning of possible status values. The status icons are displayed in table views. All other locations use status colors (instead of icons):
HPE Network Node Manager i Software (10.20)
Page 301 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Status Attributes , continued
Attribute Description
No Status
Normal
Unknown
Warning
Status
Last
Modified
Date and time indicating when the status was last set.
Minor
Major
Critical
Status History Table
Attribute Description
Status
History
List of up to the last 30 changes in status for the selected node. This view is useful for obtaining a summary of the node group status so that you can better determine any patterns in behavior and activity.
Double-click the row representing a Status History. The Status History form displays all details about the selected Status.
Interface Group Form
Each interface group can include one or more interface-type specifications (based on industry-standard IANA ifType-MIB variables). The NNMi administrator can create and modify interface group definitions. The NNMi administrator can also configure interface groups as filters in table views.
The NNMi administrator can create and modify Interface Group definitions. The NNMi administrator can also configure
Interface Groups as filters for views .
When determining membership in this Interface Group, NNMi combines the results of all Interface Group configuration settings in the following manner: l
NNMi first evaluates ifType Filters. If any exist, interfaces must match at least one specification to belong to this Interface Group.
l l
NNMi then evaluates any Additional Filters. Interfaces must also pass all Additional Filters specifications to belong to this Interface Group.
If a Node Group is specified for this Interface Group, any interface in this group must be contained in a node that is a member of the Node Group specified in the Basics section.
For information about each tab:
Tip:
Special Actions are available within the Node Group and Interface Group views.
If you are an NNMI administrator, you can create Interface Groups and use Interface Groups in several ways:
HPE Network Node Manager i Software (10.20)
Page 302 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Group Basics
Attribute Description
Name
Add to
View
Filter List
If disabled , this interface group does not appear in any interface group filter lists for interface and IP address views.
If enabled , this interface group is a filter for all interface and IP address views.
Node
Group
The name of this group (text string specified by the NNMi administrator). This name is a maximum of 255 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & *
( ) _+ -) are permitted.
Notes
Optional. If configured, the specified Node Group serves as a filter for this Interface Group.
If you specify a Node Group, any interface in this group must be contained in a node that matches the specified Node Group. For example, an Interface Group configured for Ethernetonly interfaces could be further refined by associating a Node Group configured for Printersonly. You could then gather data about all printers that contain Ethernet interfaces.
Optional. If your role permits, enter any information that might be useful to you and your team.
Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
NNM iSPI Performance
Attribute Description
Add to
Filter List
NNMi Administrators only.
Using this feature is entirely optional. The NNM iSPI Performance software, such as NNM iSPI
Performance for Metrics or NNM iSPI Performance for Traffic, can monitor your network without any exported filter.
Enable only for groups that are needed as filters in NNM iSPI Performance reports. It might take up to an hour before the results are visible in the NNM iSPI Performance reports. Choose wisely because establishing a filter requires significant NNM iSPI Performance software processing time.
If disabled , this group is not available as a filter in NNM iSPI Performance reports.
If enabled , this group appears in the Optional Filters selection panel of the NNM iSPI
Performance reports.
Requires HPE Network Node Manager iSPI Performance for Metrics Software (NNM iSPI
Performance for Metrics) -click here for more information .
Requires HPE Network Node Manager iSPI Performance for Traffic Software (NNM iSPI
Performance for Traffic) -click here for more information .
Interface Group Form: ifType Filters Tab
Interface Group members are filtered by industry-standard IANA ifType-MIB variables.
HPE Network Node Manager i Software (10.20)
Page 303 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
When determining membership in this Interface Group, NNMi combines the results of all Interface Group configuration settings in the following manner: l
NNMi first evaluates ifType Filters. If any exist, interfaces must match at least one specification to belong to this Interface Group.
l
NNMi then evaluates any Additional Filters. Interfaces must also pass all Additional Filters specifications to belong to this Interface Group.
l
If a Node Group is specified for this Interface Group, any interface in this group must be contained in a node that is a member of the Node Group specified in the Basics section.
The
"Interface Group Form" on page 302
provides details about the selected interface group.
For information about each tab: ifType Filters Table
Attribute Description
ifType
Filters
Table view of all ifType filters associated with the selected interface group.
If the Security configuration permits, double-click the row representing the ifType filter to view more details on the
ifType Filter Form
If the NNMi Security configuration permits access to this form, displays the specification of the selected interface-type filter. This filter is based on an industry-standard IANA ifType-MIB variable.
ifType Specification
Attribute Description
ifType
Click the Lookup icon and select Open to display the
"ifType (Interface Type) Form" below
and view more information about the specified IANA ifType-MIB variable.
If your role permits, you can easily choose from a list of all known industry-standard
IANAifType-MIB variables (as of the time NNMi was released). You can also add a new value.
(For more information, see: http://www.iana.org/assignments/ianaiftype-mib)
ifType (Interface Type) Form
Displays information about the
IANA ifType-MIB file's ifType variable value assigned to the selected type of interface (make and model).
For more information, see: http://www.iana.org/assignments/ianaiftype-mib
To access the ifType form, do one of the following: l
Open any
"Interface Form: General Tab" on page 118 .
l
Open any
"Interface Group Form: ifType Filters Tab" on the previous page
.
HPE Network Node Manager i Software (10.20)
Page 304 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Interface Type Definition
Attribute Description
ifType IANA ifType-MIB file's text string assigned to this kind of interface.
Number IANA ifType-MIB file's unique number assigned to this kind of interface.
Description A description of this type of interface.
Maximum of 2048 characters. Alpha-numeric, spaces, and special characters
(~ ! @ # $ % ^ & * ( ) _+ -) are permitted.
Optional. NNMi Administrators can navigate to the Configuration → MIBs → ifTypes view and modify the description text to provide useful information to your team.
Interface Group Form: Additional Filters Tab
Note: To create Additional Filters, your user name must be assigned to the role of NNMi Administrator.
Additional Filters enable the NNMi administrator to create expressions that further refine which interfaces to include in an Interface Group. If an NNMi administrator created any Additional Filters for the selected
Interface Group, NNMi displays the Additional Filters expression. See Specify Interface Group Additional
Filters for information about how to use the Additional Filters Editor or how to decipher an existing Additional
Filters expression.
When determining membership in this Interface Group, NNMi combines the results of all Interface Group configuration settings in the following manner: l l
NNMi first evaluates ifType Filters. If any exist, interfaces must match at least one specification to belong to this Interface Group.
NNMi then evaluates any Additional Filters. Interfaces must also pass all Additional Filters specifications to belong to this Interface Group.
l
If a Node Group is specified for this Interface Group, any interface in this group must be contained in a node that is a member of the Node Group specified in the Basics section.
Note: The
"Interface Group Form" on page 302
provides details about the selected Interface Group.
For information about each tab:
MPLS WAN Cloud (RAMS) Form (
NNMi
Advanced
)
(NNMi Advanced, plus HPE Route Analytics Management System (RAMS) for MPLS WAN) The MPLS
WAN Cloud (RAMS) form provides information for the selected MPLS WAN Cloud. The following table describes the fields included on the MPLS WAN Cloud (RAMS) form:
HPE Network Node Manager i Software (10.20)
Page 305 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes
Attributes
MPLS WAN Cloud
Name
AS Number
CEs
Description
The name assigned to the discovered MPLS WAN Cloud.
The
Autonomous System
1
Number assigned to the MPLS WAN Cloud.
The number of Customer Edge (CE) routers associated with the
MPLS WAN Cloud.
Related Topics:
"MPLS WAN Cloud (RAMS) Form: MPLS WAN Connections Tab (NNMi Advanced)" below
"MPLS WAN Cloud Map (NNMi Advanced)" on page 389
MPLS WAN Cloud (RAMS) Form: MPLS WAN
Connections Tab (
NNMi Advanced)
(NNMi Advanced, plus HPE Route Analytics Management System (RAMS) for MPLS WAN) The
provides details about the selected MPLS VPN Cloud.
Note: The Last Discovered Time is displayed in the MPLS WAN Interface summary. It is the date and time when the selected MPLS WAN Cloud was last discovered.
Basic Attributes
Attributes
CE Status
Description
Overall status for the Customer Edge (
CE
2
) router. The possible values are:
No Status
Normal
Disabled
Unknown
Warning
Minor
Major
1
An Autonomous System (AS) is a collection of connected Internet Protocol (IP) routing prefixes that present a common, clearly defined Border Gateway Protocol (BPG) routing policy to the Internet by having an officially registered Autonomous System Number (ASN).
2
Customer Edge router. The router in your network that sends data to an Internet Service Provider's router
(the Provider Edge) on the path to the data's final desination.
HPE Network Node Manager i Software (10.20)
Page 306 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attributes Description
CE Name
CE Interface
CE Address
PE Address
Protocol
Critical
The name assigned to the CE router.
Interface of the CE router participating in the MPLS WAN Cloud.
The IP address of the CE router.
The IP address of the Provider Edge (
PE
1
) router.
The routing protocol used between the CE and the PE router.
Related Topics:
"MPLS WAN Cloud Map (NNMi Advanced)" on page 389
Custom Node Collections 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.
The following table describes the attributes included on the Custom Node Collection form.
The Custom Node Collections form also provides details about the
associated with this Custom Poller Node.
For information about each tab:
Basic Attributes
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).
Active
State
Click the Lookup icon and select Show Analysis or Open to display more information about the node.
The Active State for the associated Custom Collect Policy. Possible values are described below:
Active - Indicates the Custom Poller Policy is in use.
1
Provider Edge router. The Internet Service Provider's router that receives your data on the path to your data's final desination. The Customer Edge (CE) router in your network connects to this PE.
HPE Network Node Manager i Software (10.20)
Page 307 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Note: 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.
Status
Policy
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
Suspended, or the NNMi administrator disabled Custom Poller in the Global
Control settings of Configuration workspace, Custom Poller Configuration form.
NNMi suspends polling and retains the most recent State value from before the Policy was suspended.
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
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.
Discovery
State
If the NNMi Security configuration permits, click the
Analysis or
Policy.
Lookup icon and select Show
Open to display more information about the current Custom Poller Node's
Indicates the progress toward collecting data associated with this
(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.
HPE Network Node Manager i Software (10.20)
Page 308 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
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.
Related Topics
About Custom Poller
Custom Node Collections Form: Incidents Tab
The
"Custom Node Collections Form" on page 307
provides details about the selected Custom Node
Collection.
For information about each tab:
Incidents Table
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
displays all details about the selected incident.
Custom Node Collections Form: Status Tab
The
"Custom Node Collections Form" on page 307
provides details about the selected Custom Node
Collection.
For information about each tab:
Overall Status
Attribute Description
Status The most severe value returned from the Polled Instances for this Custom Node
Collection.
Possible values are:
Normal
Warning
HPE Network Node Manager i Software (10.20)
Page 309 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute Description
Status Last
Modified
Minor
Major
Critical
Date and time indicating when the status was last set.
Status History Table
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.
Custom Node Collections Form: Conclusions Tab
The
"Custom Node Collections Form" on page 307
provides details about the selected Custom Node
Collection.
For information about each tab:
Outstanding Status Conclusion Values
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.
Note: A Y in the Incident? column indicates that the Conclusion results in an incident.
HPE Network Node Manager i Software (10.20)
Page 310 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Status Conclusion Values, continued
Attribute Description
Critical Status Conclusions
Conclusion Description Status Incident?
CustomPollCritical A Custom Polled Instance associated with the Custom Poller Collection is in a
Critical State.
Critical Y
Major Status Conclusions
Conclusion Description
CustomPollMajor A Custom Polled Instance associated with the Custom Poller Collection is in a Major
State.
Status Incident?
Major Y
Minor Status Conclusions
Conclusion Description
CustomPollMinor A Custom Polled Instance associated with the Custom Poller Collection is in a Minor
State.
Status Incident?
Minor Y
Warning Status Conclusions
Conclusion Description Status Incident?
CustomPollWarning A Custom Polled Instance associated with the Custom Poller Collection is in a
Warning State.
Warning Y
Normal Status Conclusions
Conclusion Description
CustomPollNormal A Custom Polled Instance associated with the Custom Poller Collection is in a
Normal State.
Status Incident?
Normal N
Custom Node Collections Form: Polled Instances
Tab
The
"Custom Node Collections Form" on page 307
provides details about the selected Custom Node
Collection.
HPE Network Node Manager i Software (10.20)
Page 311 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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: l
Updates whenever a change in State occurs (defined using Threshold or Comparison Maps settings).
l
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:
Polled Instances Table
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" below
displays all details about the selected Polled Instance.
Custom Polled Instance Form
The
Custom Polled Instance
1 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:
Note the following about Custom Polled Instances: l l
The first time a MIB Expression is validated with discovery information, the results appear in the
Monitoring workspace's
.
Each Custom Polled Instance: l
Updates whenever a change in State occurs (defined using Threshold or Comparison Maps settings).
l
Includes the most recent polled value that caused the State to change.
l
These results are then used to determine the Status of the associated Custom Node Collection.
1
A 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.
HPE Network Node Manager i Software (10.20)
Page 312 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
Basic Attributes
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).
MIB
Instance
Click the Lookup icon and select Show Analysis or Open to display more information about the topology node.
This attribute contains the multiple filtered instances for the MIB Expression. Each instance value identifies a row in the MIB table.
Note: 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.
Note: 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.
See
"Custom Node Collections Form" on page 307
for more information.
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.
HPE Network Node Manager i Software (10.20)
Page 313 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
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.
Status
Click the Lookup icon and select Show Analysis or Open to display more information about the Custom Poller Collection.
See
"Custom Polled Collection Form" on page 317
for more information.
Overall status for the current Custom Polled Instance. NNMi follows the ISO standard for status classification. See the
"Custom Polled Instance Form: Status Tab" on the next page
for more information. Possible values are:
Normal
Warning
Minor
Major
Critical
Status reflects the most serious outstanding conclusion. See
"Watch Status Colors" on page 406
for more information about possible status values.
Note: The icons are displayed only in table views
State
The State of the Custom Polled Instance as determined by any Thresholds ( High 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
Note: The most severe Threshold
or
value or Comparison Map
State Mapping value returned from the Polled Instances for a
becomes the Custom Node Collection Status.
Last State The value from the MIB Expression that most recently caused the State to change.
HPE Network Node Manager i Software (10.20)
Page 314 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Basic Attributes, continued
Attribute Description
Change
Value
Note: 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.
Custom Polled Instance Form: Incidents Tab
Tip: The
"Custom Polled Instance Form" on page 312
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>.
Note: 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:
Incidents Table
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
displays all details about the selected incident.
Custom Polled Instance Form: Status Tab
The
"Custom Polled Instance Form" on page 312
provides details about the selected Custom Polled
Instance.
For information about each tab:
Overall Status
Attribute Description
Status The most severe value returned from the Custom Polled Instance.
Possible values are:
HPE Network Node Manager i Software (10.20)
Page 315 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Overall Status, continued
Attribute Description
Status Last Modified
Normal
Warning
Minor
Major
Critical
Date and time indicating when the status was last set.
Status History Table
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.
Custom Polled Instance Form: Conclusions Tab
The
"Custom Polled Instance Form" on page 312
provides details about the selected Custom Polled
Instance.
For information about each tab:
Outstanding Conclusions Table
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.
HPE Network Node Manager i Software (10.20)
Page 316 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Outstanding Conclusions Table, continued
Attribute Description
Note: 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
Conclusion Description
CustomPolledInstanceCritical A Custom Polled Instance is in a
Critical State.
Status Incident?
Critical Y
Major Status Conclusions
Conclusion Description
CustomPolledInstanceMajor A Custom Polled Instance is in a
Major State.
Minor Status Conclusions
Conclusion Description
CustomPolledInstanceMinor A Custom Polled Instance is in a
Minor State.
Status
Major
Status
Minor
Incident?
Y
Incident?
Y
Warning Status Conclusions
Conclusion Description
CustomPolledInstanceWarning A Custom Polled Instance is in a Warning State.
Status Incident?
Warning Y
Normal Status Conclusions
Conclusion Description
CustomPolledInstanceNormal A Custom Polled Instance is in a
Normal State.
Status Incident?
Normal N
Custom Polled Collection Form
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.
HPE Network Node Manager i Software (10.20)
Page 317 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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:
Note: 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.
Basics for this Custom Poller Collection
Attribute Description
Name
Affect
Node
Status
Generate
Incident
The name for the Custom Poller Collection configuration.
The Custom Poller Collection name appears in any incidents generated as a result of the collection.
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.
Used to indicate whether NNMi generates an incident: l when a threshold is crossed l when a polled MIB value causes the Custom Polled Collection's State to be other than
Normal
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.
Variable Attributes
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.
HPE Network Node Manager i Software (10.20)
Page 318 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
High Threshold Attributes for a Custom Polled Instance
Monitored Attribute Description
Threshold Setting
Type
High State
High Value
One of the following: l
Count threshold based on the number of occurrences specified before the threshold is reached.
l
Time threshold based on the duration of time specified before the threshold is reached.
Possible values are: l
Normal l l
Warning
Minor l
Major l
Critical
The value that above which becomes a threshold situation. Use one of the following: l
Designate a percentage between 0.00 and 100.00.
For special situations, the following values can be used: l
0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero.
l
99.99999999999999 for the highest value less than one hundred.
l
Designate any appropriate integer value (for example, a Management Address
ICMP Response Time of 0 or greater milliseconds ).
The High Value must be greater than or equal to the designated Low Value.
Note: If you use the highest possible value, the threshold is disabled because it cannot be crossed.
High Value Rearm The High Value Rearm designates the lower boundary of the High Threshold
range of values.
Threshold Setting Type = Count:
High Trigger Count The number of consecutive polling intervals the returned value must be greater than the specified High Value to meet the High Threshold criteria.
Threshold Setting Type = Time (setting both of these to zero disables the High Threshold):
High Duration The minimum time within which the value must remain in the High range before the threshold state changes to High and (optionally) an incident is generated.
High Duration Window The window of time within which the High Duration criteria must be met.
HPE Network Node Manager i Software (10.20)
Page 319 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
Low Threshold Attributes for a Custom Polled Instance
Monitored Attribute Description
Low State
Low Value
Possible values are: l
Normal l
Warning l l
Minor
Major l
Critical
The value that below which becomes a threshold situation. Use one of the following: l
Designate a percentage between 0.00 and 100.00.
For special situations, the following values can be used: l
0.000000000000001 (or 1E-15 in Scientific Notation) for the smallest value greater than zero.
l
99.99999999999999 for the highest value less than one hundred.
l
Designate any appropriate integer value (for example, a Management Address
ICMP Response Time of 0 or greater milliseconds ).
The Low Value must be less than or equal to the designated High Value.
Note: If you use the minimum possible value, the Low threshold is disabled because it cannot be crossed.
Low Value Rearm The Low Value Rearm designates the upper boundary of the Low Threshold range
of values.
Threshold Setting Type = Count:
Low Trigger Count The number of consecutive polling interval the returned value must be less than the specified Low Value to meet the Low Threshold criteria.
Threshold Setting Type = Time (setting both of these to zero disables the Low Threshold):
Low Duration The minimum time within which the value must remain in the Low range before the threshold state changes to Low and (optionally) an incident is generated.
Low Duration Window The window of time within which the Low Duration criteria must be met.
Comparison Map Form
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.
HPE Network Node Manager i Software (10.20)
Page 320 of 601
Online Help: Help for Operators
Chapter 5: Accessing Device Details
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.
State Mapping Attributes
Attribute Description
Ordering The order in which the State mapping (Comparison Maps) operations should be performed.
Note: 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
HPE Network Node Manager i Software (10.20)
Page 321 of 601
Pobierz
Publiczny link zaktualizowany
Publiczny link do Twojego czatu został zaktualizowany. You may view and manage your chat links after registration here.
Publiczny link do dokumentu
Reklama
