16.7 Reactivating the IPv6 management feature
Capabilities requiring IPv6 communication, such as the discovery of only IPv6 devices and monitoring IPv6 address status, require an NNMi management server to have an IPv6 global unicast address configured and operational.
To reactive the IPv6 feature after it has been deactivated:
Edit the nms-jboss.properties file.
Locate the following line:
Windows: %NNM_PROPS%\nms-jboss.properties
Linux: $NNM_PROPS/nms-jboss.properties
NNMi provides a complete description of each property, showing them as comments in the nms-jboss.properties file.
Locate the text that begins with # Enable NNMi IPv6 Management.
To enable IPv6 communication in NNMi, un-comment the following property:
java.net.preferIPv4Stack=false
To un-comment a property, remove the #! characters from the beginning of the line.
Locate the text that begins with # Enable NNMi IPv6 Management.
To enable overall IPv6 management in NNMi, un-comment the following property:
com.hp.nnm.enableIPv6Mgmt=true
Save and close the nms-jboss.properties file.
Execute the following commands to restart NNMi:
ovstop ovstart
- Important
If you change a file while the system is operating in High Availability (HA) mode, you must make the change on both nodes in the cluster. For NNMi in an HA configuration, if the change requires you to stop and restart the NNMi management server, you must place the nodes in maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.
Check the NNMi processes by using the following command:
ovstatus -v ovjboss
Successful startup will look something like the following:
object manager name: ovjboss state: RUNNING PID: process-ID-number last message: Initialization complete. exit status: - additional info: SERVICE STATUS CommunicationModelService Service is started CommunicationParametersStatsService Service is started CustomPoller Service is started IslandSpotterService Service is started ManagedNodeLicenseManager Service is started MonitoringSettingsService Service is started NamedPoll Service is started msApa Service is started NmsCustomCorrelation Service is started NmsDisco Service is started NmsEvents Service is started NmsEventsConfiguration Service is started NmsExtensionNotificationService Service is started NnmTrapService Service is started PerformanceSpiAdapterTopologyChangeService Service is started PerformanceSpiConsumptionManager Service is started RbaManager Service is started RediscoverQueue Service is started SpmdjbossStart Service is started StagedIcmp Service is started StagedSnmp Service is started StatePoller Service is started TrapConfigurationService Service is started TrustManager Service is started
After you reactivate IPv6, NNMi views immediately include the IPv6 inventory for newly discovered nodes.
During the next discovery cycle, NNMi views will show the IPv6 inventory associated with previously discovered nodes.
Optionally, you can set the SNMP management address preference for dual-stacked managed nodes.
Dual-stacked managed nodes are nodes that can communicate using either IPv4 or IPv6. To do this, complete the following steps:
a. From the NNMi console, click Communication Configuration located in the Configuration workspace.
b. Locate the Management Address Selection section. Select IPv4, IPv6, or Any in the IP Version Preference field.
c. Save your changes.
d. Execute the following commands to restart NNMi:
ovstop ovstart
- Important
If you change a file while the system is operating in High Availability (HA) mode, you must make the change on both nodes in the cluster. For NNMi in an HA configuration, if the change requires you to stop and restart the NNMi management server, you must put the nodes in maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.
To speed things up, select nodes that you know are dual-stacked nodes, and then use the Actions > Configuration Poll command located on the NNMi console. You can also use the nnmnoderediscover.ovpl script to add nodes to the NNMi discovery queue. For details, see the nnmnoderediscover.ovpl Reference Page.
After you enable IPv6 communication on the NNMi management server, NNMi begins using ICMPv6 to monitor nodes for IPv6 address faults.