Applies To:

Show Versions Show Versions

Manual Chapter: Preparing for Upgrade and Migration
Manual Chapter
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

There are significant differences between BIG-IP® version 4.x and BIG-IP® Local Traffic ManagerTM version 9.x. Following is a list of the new features introduced in Local Traffic Manager version 9.x.
For more detailed information about all of the local traffic management features, see the Local Traffic Manager release note specific to the version to which you are upgrading, as well as the Configuration Guide for BIG-IP® Local Traffic Management and the BIG-IP® Network and System Management Guide. All documentation is available on the F5 Technical Support Web site, https://support.f5.com.
Upgrading from BIG-IP® version 4.x system to BIG-IP® Local Traffic Manager version 9.x is more involved than a standard upgrade because, in addition to new features, the Local Traffic Manager software also introduces significant changes to the system. These system changes include the new Traffic Management Operating System® (TMOS®) and the updated Configuration utility.
Because you can configure the BIG-IP system in a wide variety of ways, it is not possible to anticipate every issue that may arise during upgrade and migration. However, this document helps you identify some areas where potential problems may occur, and provides you with options to consider when addressing them.
Note: For this document, the term upgrading refers to upgrading the BIG-IP software only. The term migrating refers to importing the existing BIG-IP version 4.x configuration settings to Local Traffic Manager, after you upgrade.
After you upgrade to Local Traffic Manager version 9.x, you can rebuild your configuration settings manually, which is ideal for systems with minimal configuration.
Another option is to migrate your previous configuration settings to the new system. You can do this either by using the one-time conversion utility (OTCU), which converts your BIG-IP configuration files to a format compatible with Local Traffic Manager, or by hiring a consultant from F5 Networks system to perform the migration for you.
Important: The OTCU was developed specifically for BIG-IP versions 4.2 to 4.5.12. If you are running BIG-IP version 4.5.13 or later, be aware that the OTCU may fail, or might not fully migrate all of the settings in the UCS archive to Local Traffic Manager. If you successfully migrate the settings for BIG-IP version 4.5.13 or later, you must re-create manually, any configuration settings for features introduced after version 4.5.12.
Employ an F5 Networks consultant
Ideal for large organizations with complex deployments of BIG-IP systems.
Might be time-intensive for smaller deployments or organizations.
Manually rebuild the configuration
Simplifies software installation and provides an opportunity to understand how Local Traffic Manager operates.
Recreating configuration settings can be time consuming for large deployments.
Use the OTCU to convert configuration settings
Automatically converts the configuration settings you specified in BIG-IP version 4.x to Local Traffic Manager version 9.x.
Depending on the complexity of the configuration, or the version of the BIG-IP system, the OTCU might not fully optimize all settings during the conversion process.
Before you start the process of upgrading and migrating your configuration, we recommend that you review the following documentation for the specific version of Local Traffic Manager to which you are upgrading.
BIG-IP® Local Traffic Manager release notes
The release notes for Local Traffic Manager provide hardware requirements, feature details, and information about how to download the software.
Installation, Licensing, and Upgrades for BIG-IP® Systems
This guide describes how to install the BIG-IP software, license the system, and use the Setup utility to perform basic configuration tasks.
Local Traffic Manager solutions
The solutions on the F5 Technical Support web site provide further information regarding Local Traffic Manager and hardware platforms.
Note: Starting in version 10.0.0, the Installation, Licensing, and Upgrades for BIG-IP® Systems guide is titled, BIG-IP® Systems: Getting Started Guide.
Resource requirements
Local Traffic Manager version 9.x has considerably more functionality than BIG-IP version 4.x. This additional functionality, coupled with the new full-proxy architecture, requires more hardware resources. Before upgrading to Local Traffic Manager, review the minimum system requirements specified in the Local Traffic Manager release notes.
Migration on 520/540 platforms
When you upgrade a 520/540 platform to Local Traffic Manager, one interface becomes the management interface by default. As a result, the interface that handles traffic is likely to change from your previous configuration.
Redundant system
If you are upgrading a redundant system configuration, you install Local Traffic Manager only on the inactive system. After you provide the minimum configuration details, you can synchronize the configuration to the peer system, using the ConfigSync operation. (For the minimum configuration details, you must provide the appropriate VLANs, self IP addresses, interfaces, and configuration information.)
Keyboard and video ports
After you upgrade to Local Traffic Manager version 9.x, you may need to change the serial console to the settings 19200, 8, n, and 1 in order for your keyboard and video ports to function reliably.
Table of Contents   |   << Previous Chapter   |   Next Chapter >>

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)