Converting an NFM-P system to IPv6
Introduction
|
CAUTION Service Disruption |
An NFM-P system conversion requires a thorough understanding of NFM-P system administration and platform requirements, and is supported only under the conditions described in this guide, the NSP Planning Guide, and the NSP Release Notice.
Such an operation must be planned, documented, and tested in advance on a trial system that is representative of the target live network. Contact NSP professional services to assess the requirements of your NFM-P deployment, and for information about the upgrade service, which you are strongly recommended to engage for any type of deployment.
|
|
CAUTION Service Disruption |
An NFM-P system conversion to IPv6 involves a network management outage.
You must perform a conversion only during a maintenance period of sufficient duration.
This section describes the conversion of inter-component communication from IPv4 to IPv6 in a standalone or redundant NFM-P system.
The NFM-P samconfig utility is used for component configuration and deployment. See NFM-P samconfig utility for information about using the samconfig utility.
Note: The Bash shell is the supported command shell for RHEL CLI operations.
IPv6 conversion requirements
The following must be true before you attempt a system conversion to IPv6.
-
Each required IPv6 interface is plumbed and operational; see the RHEL documentation for information about enabling and configuring an IPv6 interface.
-
The NFM-P system is at the release described in this guide; you cannot combine an upgrade and a conversion to IPv6 in one operation.
-
If the system to be converted is a newly upgraded system, the system is fully initialized and functional; an upgraded main server performs crucial upgrade-specific tasks during startup.
IPv6 conversion restrictions
An NFM-P system conversion from IPv4 to IPv6 is not supported during a system upgrade or conversion to redundancy.