Use > Access Device Details > Interface Form > Interface Form > Interface Form - Capabilities Tab > Interface Capabilities Provided by NNMi

Interface Capabilities Provided by NNMi

The Interface Form: Capabilities Tab 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.

<product> = Either NNMi or the NNM iSPI providing this capability.

<content> = chassis, card, ipaddr (address), iface (interface), lag (Link AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG. 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.

The following tables show a few examples of the Capabilities provided by NNMi.

Interface Capability Attribute Values
Unique Key Capability Description
com.hp.nnm.capability.iface.private Private

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: 

  • The interface index (ifIndex) value is always set to 0 (zero).
  • The interface type (ifType) is set to Other.

  • The interface Name (ifName), if none is available, is set to Pseudo Interface.

    For Pseudo Interface, NNMi attempts to obtain additional information using a variety of discovery protocols (see the list of Topology Source protocols in Layer 2 Connection Form).

  • 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: 

  • The interface index (ifIndex) value is set according the Nortel private MIB.
  • NNMi tries to collect the MAC address and interface name using Nortel's private MIBs.
com.hp.nnm.capability.iface.ietf.NON-DEFAULT-CONTEXT-RFC1213 RFC 1213 Interface from Non-default Context

Indicates the following:

  • NNMi discovered the interface from the RFC1213 MIB.
  • The interface has a context other than default.

Note  

  • NNMi collects context values using the vacmContextTable in the SNMP-VIEW-BASED-ACM-MIB defined in RFC2575.
  • NNMi does not monitor interfaces under a non-default context.
com.hp.nnm.capability.iface.PE PE Interface Indicates that the interface is serving as a Provider Edge (PEProvider 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.). NNMi's Subnet Connection Rules use this information.
com.hp.nnm.capability.br.bridge Virtual Bridge Indicates that the interface represents a virtual bridge (also known as a virtual switch).
com.hp.nnm.capability.br.port Virtual Bridge Port Indicates that the interface represents any interface associated with a virtual bridge.
  VM Virtual Machine Interface  

Requires Network Node Manager iSPI Performance for Metrics Software (NNM iSPI Performance for Metrics). To populate performance data in the dashboard views or enhance NNM iSPI Performance for Metrics reports by sharing NNMi configuration settings, install the optional Network Performance Server (NPS).
com.hp.nnm.capability.iface.ietf.DS1 DS1 Interface Metrics Interface that supports the DS1 (T1) MIB for gathering performance data. This data is used by NNM iSPI Performance for Metrics.
com.hp.nnm.capability.iface.ietf.DS3 DS3 Interface Metrics Interface that supports the DS3 (T3) MIB for gathering performance data. This data is used by NNM iSPI Performance for Metrics.
com.hp.nnm.capability.iface.ietf.ETHERLIKE EtherLike Interface 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.
com.hp.nnm.capability.iface.ietf.IEEE80211 IEEE 802.11 Interface 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 Metrics.
com.hp.nnm.capability.iface.ietf.SONET SONET 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.
com.hp.nnm.capability.iface.ietf.SONET-PATH SDH Interface 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:

  • Interface index (ifIndex) and description (ifDescr) are set according to the RFC 2465 IPv6 MIB.
  • Interface type (ifType) is set to Other (no specific type is available).
  • Interface Name (ifName), Alias (ifAlias), and Speed (ifSpeed) are blank (not available).
  • 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>]).

(NNMi Advanced) The capabilities in the following table identify how the interface is participating in a Link AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG..

(NNMi Advanced) Link Aggregation Interface Capabilities: Roles
Unique Key Capability Description
com.hp.nnm.capability.lag.aggregator Aggregator 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.
com.hp.nnm.capability.lag.member 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 AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG. protocol is available.

(NNMi Advanced) Link Aggregation Interface Capabilities: Protocols
Unique Key Capability Description
com.hp.nnm.capability.lag.protocol.lacp 802.3ad Link Aggregation Control Protocol Indicates an interface using the IEEE 802.3ad Link Aggregation Control protocol (LACP).
com.hp.nnm.capability.lag.protocol.static Static/Manual Configured Link Aggregation Indicates the device has been configured with Static/Manual Configured Link Aggregation (static).
com.hp.nnm.capability.lag.protocol.pagp Cisco Port Aggregation Protocol Cisco Systems Port Aggregation Protocol (pagp)
com.hp.nnm.capability.lag.protocol.mlt Nortel Multi-Link Trunking Nortel Multi-Link Trunk technology (mlt)
com.hp.nnm.capability.lag.protocol.istmlt Inter-Switch Trunk MLT Split Multi-Link Trunk: inter-switch trunk (istMlt)
com.hp.nnm.capability.lag.protocol.smlt Split MLT Split Multi-Link Trunk: configuration technology (splitMlt)
com.hp.nnm.capability.lag.protocol.unknown Unknown Protocol Link Aggregation Indicates the hosting interface is a member of Link Aggregation with unknown protocol.

Send Help Center feedback