How To Use the Voyager Configuration Migration Tool - Check Point

How To Use the Voyager
Configuration Migration
Tool
10 April 2012

© 2012 Check Point Software Technologies Ltd.
All rights reserved. This product and related documentation are protected by copyright and distributed under
licensing restricting their use, copying, distribution, and decompilation. No part of this product or related
documentation may be reproduced in any form or by any means without prior written authorization of Check
Point. While every precaution has been taken in the preparation of this book, Check Point assumes no
responsibility for errors or omissions. This publication and features described herein are subject to change
without notice.
RESTRICTED RIGHTS LEGEND:
Use, duplication, or disclosure by the government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 and FAR
52.227-19.
TRADEMARKS:
Refer to the Copyright page (http://www.checkpoint.com/copyright.html) for a list of our trademarks.
Refer to the Third Party copyright notices (http://www.checkpoint.com/3rd_party_copyright.html) for a list of
relevant copyrights and third-party licenses.

Important Information
Latest Software
We recommend that you install the most recent software release to stay up-to-date with the latest functional
improvements, stability fixes, security enhancements and protection against new and evolving attacks.
Latest Documentation
The latest version of this document is at:
http://supportcontent.checkpoint.com/documentation_download?ID=15381
For additional technical information, visit the Check Point Support Center
(http://supportcenter.checkpoint.com).
Revision History
Date
Description
4/10/2012 First release of this document
Feedback
Check Point is engaged in a continuous effort to improve its documentation.
Please help us by sending your comments
(mailto:cp_techpub_feedback@checkpoint.com?subject=Feedback on How To Use the Voyager
Configuration Migration Tool ).

Contents
Important Information ............................................................................................. 3
How To Use the Voyager Configuration Migration Tool ....................................... 5
Objective ................................................................................................................. 5
Supported Versions ............................................................................................. 5
Supported Operating Systems ............................................................................. 5
Supported Appliances ......................................................................................... 5
Before You Start ..................................................................................................... 5
Related Documents and Assumed Knowledge .................................................... 5
Using the Voyager Configuration Migration Tool ................................................. 5
Migrating a System Configuration ........................................................................ 5
Migrating the Configuration Information ............................................................... 7
Verifying the Procedure........................................................................................ 10
Index ...................................................................................................................... 11

How To Use the Voyager Configuration Migration Tool
How To Use the Voyager
Configuration Migration Tool
Objective
This document outlines the steps used to migrate the IPSO configuration from one IP appliance to another
with the Configuration Migration tool in Voyager. With this tool, the IP appliance and IPSO version to which
you migrate is irrelevant. For example: migration from IPSO 3.8 to IPSO 6.2 is supported.
Supported Versions
Check Point versions that are supported on IPSO 6.x (NGX R65 for IPSO 6, R70.x, R71.x R75.x)
Supported Operating Systems
IPSO 6.1 and higher
Supported Appliances
Any IP Appliance
Before You Start
Related Documents and Assumed Knowledge
Network Voyager for IPSO 6.2 Reference Guide
(http://downloads.checkpoint.com/dc/download.htm?ID=10293)
Using the Voyager Configuration
Migration Tool
Migrating a System Configuration
Configuration migration allows you to map interface configuration across the platforms. For example, you
can map interface A on the source to interface B on the target so that interface B is configured identically to
A.
How To Use the Voyager Configuration Migration Tool | 5

For Example: Migration from an IP350 with IPSO 3.9 to an IP1280 with IPSO 6.2:
Using the Voyager Configuration Migration Tool
IP350 (Source) Interface settings:
IP1290 (Destination) Interface settings:
To Acquire Configuration Information:
You can acquire configuration information from a Check Point platform with any version of IPSO between
3.7 and 4.2 (inclusive). To acquire configuration information, you copy an IPSO configuration file or backup
file from the source to the target.
You can move these files directly from the source to the target (with Voyager or another method) or move
them to a workstation. To move the file to the target with Voyager, use these options on the Acquire
Configuration window:
Remote Device: Use this option to transfer a file directly from the source to the target.
You must have network access to the source.
If you specify a file (configuration file or backup file), you must specify the complete path.
If you do not specify a file, IPSO automatically copies the current configuration database file from the
source.
Upload: Use this option if you have moved the IPSO configuration file or backup file from the source to
your workstation (the computer with Network Voyager).
How To Use the Voyager Configuration Migration Tool | 6

Using the Voyager Configuration Migration Tool
Local File: Use this option if you have moved the IPSO configuration file or backup file from the source
to the target with FTP or a similar method. If you use this option, you must save the configuration file or
backup file in one of several specified directories. To see which directories you can use, expand the
directory tree in the Select File to Acquire box.
Example of a remote configuration set:
Navigate to System > Tools > Configuration Migration > Acquire Configuration:
See Managing Configuration Sets and Creating Backup Files sections in the Network Voyager for IPSO
6.2 Reference Guide (http://downloads.checkpoint.com/dc/download.htm?ID=10293) for instructions to
create the Configuration Sets and the Backups.
Regardless of which method you choose, click Apply once you have selected the appropriate file. If IPSO
recognizes that the file is a valid configuration file or backup file (and transfers it to the target, if necessary),
you see a message that indicates that the process is successful and tells you to access the Migrate
Configuration window.
Migrating the Configuration Information
Navigate to System > Tools > Configuration Migration > Migrate Configuration:
How To Use the Voyager Configuration Migration Tool | 7

Using the Voyager Configuration Migration Tool
Voyager displays the IPSO version of the source configuration at the top of the page to help you verify that
you acquired appropriate configuration information. IPSO needs to know the model number of the source
platform. If IPSO is able to determine the number because of the method used to acquire the configuration
or backup file, the number is displayed near the top of the page. Otherwise there is a menu from which you
must select the model of the source platform.
Use the Migrate Configuration page to determine how to map the interfaces from the Source platform to the
Target platform. When you map a physical interface, IPSO migrates all the logical configuration for that
interface to the physical interface on the target. That includes VLAN information (see above).
Migrating Features
If you include Users as one of the features to migrate (the default setting), the admin password of the source
platform becomes the admin password of the target platform after you reboot it. If you want to prevent this,
remove Users from the list of features to migrate before you finish the migration. In this case, the original
admin password of the target platform is retained after you reboot the target. Configuration information for
certain features cannot be migrated because it is not stored in IPSO configuration files. Examples include:
IP Clustering
HA Voyager
Packages
optional disks
PPPoE
ISDN
IPv6 host address (if the source configuration is from an IPSO version previous to 6.1)
How To Use the Voyager Configuration Migration Tool | 8

Using the Voyager Configuration Migration Tool
If configuration information for a feature cannot be migrated, the feature is not included in the list.
Once the proper features are added (or removed) click the Finish button.
How To Use the Voyager Configuration Migration Tool | 9

If desired you can now use the provided link to view the configuration migration process details.
Verifying the Procedure
Verifying the Procedure
To verify that the migration is successful, simply check the interface configuration on the Target platform to
ensure all of the Source interface configurations (and features) appear correctly.
How To Use the Voyager Configuration Migration Tool | 10

Index
B
Before You Start • 5
H
How To Use the Voyager Configuration
Migration Tool • 5
I
Important Information • 3
M
Migrating a System Configuration • 5
Migrating the Configuration Information • 7
O
Objective • 5
R
Related Documents and Assumed Knowledge •
5
S
Supported Appliances • 5
Supported Operating Systems • 5
Supported Versions • 5
U
Using the Voyager Configuration Migration Tool
• 5
V
Verifying the Procedure • 10