Absent Member.. Absent Member..
Absent Member..

NNMi 9.10: TO Upgrade or Not to Upgrade

What sort of improvements have occurred in 9.10 that would motivate someone to upgrade from a system that seems to be pretty stable at 9.0?  Have you encountered any glaring issues that an administrator needs to be concerned about?


Thank you

Tags (1)
21 Replies
Micro Focus Expert
Micro Focus Expert


Yes backing up is recommended prior to any upgrade. There is a section in all of the 9.10 Installation and Configuration manuals specifically talking about steps to take to protect your data.


Absent Member.
Absent Member.

One additional reason to upgrade to 9.10 is significant increase in capabilities to manage enterprise IP Telephony and unified communications deployments. There have been numerous additional new monitoring and reporting capabilities such as real time voice quality monitoring, reporting for the same, various new  ultilization/usage alerts, reports on the same, newer reports using call details(CDRs) etc. Please refer to the release notes for the 9.10 version of the NNM iSPI for IP Telephony and other product documentation to know more. Also feel free to contact us in case you need more information. We would be glad to provide the same.

Absent Member.
Absent Member.

Overview of the NNMi 9.10

    • Web browser bookmarks for accessing the NNMi console in the format http://<fully_qualified_domain_name>:<port>/nnm/welcome.jsp no longer work. All NNMi console users should update their bookmarks to the supported URL format of http://<fully_qualified_domain_name>:<port>/nnm/.
    • During the upgrade, NNMi users are assigned to one of five special predefined NNMi user groups, depending on their previous role. These user groups define access to NNMi itself. Upon completion of the upgrade, all NNMi users are linked to the Default Security Group, which provides access to all nodes in the NNMi topology.
    • The minimal refresh rate for the Network Overview map has been increased from 3 seconds to 4 minutes, so that it does not refresh as often after restarting ovjboss.
    • In NNMi 9.0x, the NNMi Application Failover feature supported a UDP solution where cluster hosts were automatically discovered on the network. Beginning with NNMi 9.10, HP eliminated the UDP solution and only supports the TCP solution. For more information on configuring Application Failover and especially if you are upgrading a system that currently uses UDP for Application Failover,
    • Upgrading high availability (HA) clusters from NNMi 9.0x to NNMi 9.10 while keeping the clusters under HA configuration is supported. For more information.
    • Beginning with NNMi 9.10, the NNMi Integration Enablement license is obsolete and is not needed for run-time use of the NNMi Web Services. The NNMi Developer license is still required for Web Services SDK development.
  • Changes to Supported Environments
    • Adds support of SUSE Linux.
    • Adds support of Oracle Solaris Zones.
    • Adds support of ESX 4.0 and ESXi 4.1.
    • Adds support of Microsoft Hyper-V R2.
    • Adds support of Red Hat Cluster Suite.
    • HP Serviceguard on Linux is no longer supported.
    • Microsoft Windows 2003 is no longer supported.
    • Internet Explorer 7 is no longer supported.
  • Documentation Changes
    • The Deployment Reference has been split into two volumes. The Upgrade Reference contains the content that was previously in the Upgrading from NNM 6.x/7.xsection of the Deployment Reference.
    • An introductory overview of NNMi is available from Help → Getting Started with NNMi in the NNMi console.
    • Access to this release notes document is available from Help → What's New? in the NNMi console.
  • Security and Multi-Tenancy
    • Object level security provides for fine-grained control of operator access to topology objects and incidents.
    • User Group objects group users and define access to the product. The special NNMi user groups "admin", "level2", "level1", "guest", and "client" define access to the entire product (when no object has been selected).
    • Updated LDAP directory service support to use a Distinguished Name to directly map a directory service group to an NNMi User Group.
      • Security Groups control access rights to objects based on the corresponding node's Security Group assignment and the Security Group to User Group mapping. This same control is used for SNMP queries using the MIB Browser and MIB Grapher.
      • Security Groups affect the visibility of incidents. The Unresolved Incidents security group controls access to incidents without a resolved source node.
      • An incident CIA indicates the tenant associated with an incident.
        • The Security Wizard simplifies the process of configuring User Groups, User Group mappings, Security Groups, and Security Group mappings.
        • Tenants divide the topology into separate spaces for managed service providers. Tenants indicate which organization a node belongs to.
        • A tenant can be specified when seeding a node for discovery (with the nnmloadseeds.ovpl command or in the NNMi console).
        • Configuration can be done per tenant using node groups.
          • Node groups can be defined based on the node's Tenant or Security Group.
          • The nnmsecurity.ovpl command is multi-functional:
          • Manages User Accounts, User Groups, Security Groups, and Tenants.
          • Reports on the security configuration (also available from Tools → Security Reports).
          • The nnmprincipalconfig.ovpl command has been deprecated; use nnmsecurity.ovpl instead.
            • Operators can change their password by using File → Change Password.
            • Single Sign-On is now configured in the nms-ui.properties file. Changes can be made to take effect without restarting ovjboss. See the nnmssso.ovpl reference page, or the UNIX® manpage, for more information.
            • (NNM iSPI Performance for Metrics) Performance reports are filtered based on NNMi security configuration (User Groups and Security Groups). Topology filtering of reports based on tenants is also available.
            • The NNMi administrator can restrict access at the interface level for reporting purposes.
              • (NNMi Advanced) In a Global Network Management (GNM) deployment, tenants and tenant node assignments are replicated from the regional manager to the global manager.
  • State Poller
    • Enhanced ICMP (ping) monitoring of management addresses in networks supports networks using Name Address Translation (NAT) in which the management address may not be an IP address hosted on the node. Note the following about this feature:
    • A new Agent ICMP State that indicates whether a node’s management address responds to ICMP is displayed for each node and SNMP Agent.
    • The configuration setting controlling this monitoring is still enabled using the Enable ICMP Management Address Polling check box.
    • The ICMP state of the IP address hosted on the node is only monitored if Enable ICMP Fault Pollingis selected.
      • Time-based thresholds provide for thresholds that occur for a specified duration within a sliding period. Thresholds can be configured to be generated when a threshold has been exceeded for X minutes of Y hours.
      • Thresholds on Management Address ICMP Response Time can be configured.
      • For detecting renumbering of interfaces on a device, the Interface Reindexing Type attribute on Device Profile objects has an additional value: ifName or ifDescr or ifAlias.
      • You now can now be alerted if a threshold is above 0 by setting the high threshold value to 0. This functionality is useful when thresholding against errors and discards and it is expected that there should not be any on a properly running network. This capability is also available with Custom Poller.
  • Performance Management (NNM iSPI Performance for Metrics required)
    • Configurable baseline thresholds, including configuration of number of deviations from normal.
    • Collect and report on many new performance metrics:
    • Interface Metrics
      • Additional interface metrics from the IF MIB
      • Etherlike MIB
      • Wireless LAN MIBs (IEEE802dot11 MIB, CISCO-DOT11-ASSOCIATION MIB)
      • WAN Metrics (DS1/DS3, SONET)
        • Monitoring configuration control over monitoring of DSx and SONET WAN metrics
        • Node Component Metrics
          • Disk space utilization (HOST-RESOURCES MIB)
          • Backplane utilization
            • CISCO-STACK-MIB (Cisco)
            • RAPID-CITY MIB (Nortel)
            • XYLAN-HEALTH-MIB Alcatel)
            • Node availability (SNMP) and node reachability (ICMP)
            • Bad polls.  Bad polls fall into the following categories:
              • Unresponsive target
              • Target error (such as SNMP "no such object" error)
              • Invalid data (such as number of packets > number of octets)
    • Many new performance thresholds available:
    • Count-based, Time-based, and Baseline Thresholds:
      • Disk Space Utilization
      • Backplane Utilization
      • Management Address ICMP Response Time
      • Buffer Utilization
      • CPU Utilization
      • Memory Utilization
      • Interface Input Utilization
      • Interface Output Utilization
      • Count-based and Time-based Thresholds:
        • FCS Error Rates (LAN, WLAN)
        • Queue Drop Rates
        • Buffer Failure Rate
        • Buffer Miss Rate
        • Buffer Utilization
  • User Interface
    • By default, forms open in the NNMi console with breadcrumbs to navigate between previous views and forms.
    • An actions context menu is available when you right-click on one or more table entries or map objects.
    • The Analysis Pane provides additional information on the selected object:
    • Clickable links provide for direct navigation to referenced items.
    • Expandable lists are clickable and show the total number, such as indicating the number of IP Addresses and Interfaces on a Node.
    • The Summary Panel shows an overview of the object.
      • Nodes show in the Summary Panel the total number of Incidents received, along with the first and last time and the frequency with which they were received.
      • The Details tab provides more detailed information about the object.
      • Various Analysis Pane tabs are available depending on the type of object:
        • Topology objects
          • Objects have tabs showing related topology objects (such as the Node and Interface for an IP Address).
          • The Status History tab shows the percentage of time the entity had each status.
          • The Gauges tab shows real-time SNMP gauges to display State Poller and Custom Poller SNMP data.
          • These gauges are displayed for Nodes, Interfaces, Custom Node Collections, Custom Node Instances, and for Node Components of type CPU, MEMORY, BUFFERS, or BACKPLANE.
          • An icon appears at the bottom of each gauge that can be clicked to launch a real-time SNMP line graph for the metric.
          • Double clicking on a gauge opens a window for selecting and copying the tooltip information.
            • The State Poller and Custom Poller tabs show the results of the last collected values.
            • Nodes have a MIB Values tab that displays sysUpTime and ifNumber. Cisco nodes also displays the chassis serial number.
            • Nodes have a Security tab that shows the Security Group and User Groups with access to the Node.
            • Nodes have a Layer 2 Map tab shows the 1-hop neighbors of the selected Node.
            • Layer 2 Connection, Interface, Port, and IP Address have a Connection tab that shows mismatches of speed, duplex, and other settings between two ports.
            • Incidents have tabs that shows Custom Attributes, Parent Incidents, Child Incidents, and Similar Incidents. The Custom Attributes tab shows Textual Conventions values for SNMP varbinds. Tabs show details for the Source Node and Source Object.
            • Node Groups display a pie chart of the status for contained Nodes.
            • User Accounts, User Groups, Security Groups, User Account Mappings, and Security Group Mappings display tabs indicating unused User Accounts, User Groups, or Security Groups.
    • A new Initial Discovery Progress map view is the default view immediately after product installation. After more than 100 connectors have been discovered, the Open Key Incidents table view becomes the initial starting view. To change this behavior, change the Initial View parameter on the User Interface Configuration form from Installation Default to the initial view of your choice.
    • Incident tables can have color-coded rows. This feature can be enabled using the User Interface Configuration form in the Configuration workspace.
    • URLs (http://, https://, ssh://, telnet://, and mailto:) in Notes, Incident fields, Analysis Pane, and descriptions are clickable.
    • Operators no longer see the Node Group configuration tab in a Node Form. They only see the Status tab. Only Administrators can see the "Device Filters", "Additional Filters", "Additional Nodes", and "Child Node Groups" tabs.
    • Views and Forms in the Configuration workspace are grouped with a tree control.
    • CSV Export:
    • Export an entire table (or selected rows) to a comma-separated values file with right-click Export to CSV.
    • Export to a .csv file from Real-time Line Graphs.
      • Node access menu items:
      • Menu item to launch a web browser to the selected Node, IP Address, or Incident Source Node.
      • New Secure Shell... (from client)menu item requires the configuration of client browsers to respond to the ssh:// protocol. For information on configuring your browser
        • SNMP Communication and MIBs
          • Configuration of the SNMP Management Address Selection algorithm in the Communication Configuration form: "Seed IP", "Lowest Loopback IP", "Highest Loopback IP", and Interface matching. By default, the management address is set to the seeded address.
          • Now handles changing the SNMPv3 engine ID on the device.
          • The nnmsnmpset.ovpl command now accepts multiple varbinds as arguments.
          • The nnmcommload.ovpl command now includes options for setting SNMP enabled, SNMP address discovery enabled, and get bulk enabled.
          • SNMP MIB loading:
          • Improved MIB loading performance.
          • Stricter enforcement of MIB conventions. Invalid MIBs do not load.
          • Support for Textual Conventions: table of Textual Conventions; visible in MIB Browser, command line tools, and Analysis Pane.
          • When loading incidents as traps from a MIB, nnmincidentcfg.ovpl no longer has a -loadMib option. First, use nnmloadmib.ovpl to load the necessary MIBs before calling nnmincidentcfg.ovpl -loadTraps.
            • Discovery
              • Discovery takes MAC Addresses into account for the following benefits:
              • Improves support for DHCP or other nodes that change IP addresses.
              • Improves node identity for nodes configured with duplicate IP addresses.
              • Improves support for devices that do not report hosted IP addresses.
                • The disco.SkipXdpProcessing configuration file can contain the management addresses of the devices for which NNMi should ignore the Discovery Protocol SNMP tables. This configuration file is especially important for customers who have Enterasys devices in their management domain.
                • The disco.NoVLANIndexing configuration file is now fully supported.
  • Events and Causal Engine
    • Better dampening defaults for many Management Events.
    • Faster root cause incident generation for Node Down, Interface Down, and Connection Down.
    • Jython version 2.5.1 now supported for event actions.
    • The trapFilter.conf file can be used to block traps based on IP address ranges or trap OIDs. The blocking happens before the trap is written to the trap binary store and before it is analyzed for rate, which means that traps blocked by this filter do not affect trap rate calculations and do not appear when using the nnmtrapdump.ovpl command.
  • Integrations
    • HP SiteScope
    • HP SiteScope trap integration for SiteScope monitor alerts
      • Includes canceling of traps when the alert condition is cleared in SiteScope
      • HP SiteScope System Metrics integration (NNM iSPI Performance for Metricsrequired)
        • Configured through the HP SiteScope System Metrics link in the Integration Module Configuration workspace
        • Reports on HP SiteScope system resource metrics:
          • Memory Utilization
          • CPU Utilization
          • Disk Space
          • Windows Processes
          • UNIX Processes
    • HP Network Automation
    • The configuration of the HP NNMi–HP NA integration is now done completely through the HP NA integration module configuration. There is no more need for installing an NA Connector on the NNMi management server.
    • Single sign-on support when cross-launching from NNMi to NA
    • Topology synchronization improvements:
      • More reliable node/device identification between the two products.
      • Nodes discovered by NNMi are added to NA based on Node Group membership.
      • Dynamic real-time synchronization.
      • Periodic full synchronization to recover from failures, outages, failovers, and so on.
      • Load balanced with Spiral Discovery to avoid competing for resources. Paced to avoid excessive load on NNMi.
      • Bi-directional synchronization (NNMi adds nodes to NA, NA hints nodes to NNMi). Previously NA seeded nodes to NNMi; now with hinting, nodes from NA are only discovered by NNMi if they pass the NNMi auto-discovery rules.
      • Node deletion synchronization (NNMi delete -> NA unmanaged, NA delete -> NNMi delete). Previously, nodes deleted in NNMi were also deleted in NA; now they are simply unmanaged in NA.
  • General
    • The nnmnodegroup.ovpl command lists Node Group names or Nodes in a Node Group.
    • The nnmhealth.ovpl command has options for filtering by category and severity level.
    • NNMi Application Failover improvements:
    • Increased network throughput for database file transfers.
    • Detect if certificates have not been properly merged to nnm.keystore to support application failover.
    • The $NnmDataDir/log/nnm/nnmcluster-status.log file shows the current status of the cluster without the need to invoke nnmcluster -display.
    • By default, a full database backup is transferred every 6 hours.
    • The new com.hp.ov.nms.cluster.autofailover system property is available in the nms-cluster.properties file for disabling automatic failover so that users always initiate a manual failover.
      • iSPI NET
        • (NNM iSPI NET only) The nnmooflow.ovpl command supports integrating HP Operations Orchestration flow definitions into NNMi for running diagnostics based on incidents.
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..



a backup or snapshot of your VM is always a very good idea. Also a site by site migration is an option if you have the resources. I would never use nnmconfig*.ovpl commands for an upgrade or a migration from Win 2003 to 2008 with same or different versions of NNMi and SPIs. Use the procedures in teh Deployment Guide.


NNMi and the PerfSPI have their own backup commands (e.g. %NnmInstallDir%\NNMPerformanceSPI\bin\backup.ovpl). Until now all customers agreed to not migrate the PerfSPI data, so I have currently no experience about that. NNMi works as described by the Deployment Guide and it is very easy when it is on the same system already running Windows 2008 as you wrote. But take the time for backup and the tips I posted in this thread.


HTH and kind regards



Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..


I'd recomend the upgrade to 9.10 patch 1 jsut for the reduction in the number of pop up windows, analysis pane, and the addtion of SONET, WiFi, DSx,Frame-Relay, and ATM Metrics in the perf spi.

Have a nice day 🙂

Andy Kemp
I've lasted longer in the technology industry than most certifications.
Absent Member.
Absent Member.

HI All,


This is siva and iam new to the HP nnm tool.I want your help in this regard. You can mail me the steps to vsiva25@gmail.com id please.please.........


     My question is how we can turn ON auto refresh in HP NNM Version 9.10 with patch 2.I want the steps.If you can say the solution it will be very help full for me as iam facing a lot of problems with autorefresh off and every time iam clicking on other options and getting back.Request you to help me in this issue.



Thanks in advance.




Trusted Contributor.
Trusted Contributor.

how to configure color coded rows of incident tables in NNMi

Absent Member.. Absent Member..
Absent Member..

Configuration > User Interface > User Interface Configuration > Enable Table Row Shading

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Absent Member.. Absent Member..
Absent Member..

You can change Maps auto-refresh settings under Configuration > User Interface > Node Group Map Settings

HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Trusted Contributor.
Trusted Contributor.

Thank You Walinton. That helped me... 🙂

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.