You use the Migrate Configuration page primarily to map interfaces from the source to the target. Voyager provides information to help you choose which interfaces on the target are the best matches for the interfaces on the source. The table on the left lists all the physical interfaces on the source platform and also identifies all the attributes associated with each interface. For example, you can see whether routing protocols, VRRP, SNMP, and so on are configured for an interface. This table also lists the configured speeds for the source interfaces. <00491419> The table on the right lists the physical interfaces on the target platform and their available speeds.
In addition to the physical interfaces on the source platform, the table on the left lists all the logical interfaces that have IP addresses assigned. When you map a physical interface, IPSO migrates all the logical configuration for that interface to the physical interface on the target. You cannot map logical interfaces individually.
If there is a logical interface without an associated IP address on the source platform (for example, if there is a VLAN interface without an address), the logical interface does not appear in the table and is not migrated to the target.
Migrating Configuration Information
You must map each source interface or explicitly choose to not migrate it by making selections in the Interface on Target Platform column. If you click Next or Finish without making a selection for every source physical interface, Voyager displays a message telling you that you must choose an entry for every interface and does not display the next page.
Warning - If an interface on the target is configured before you perform the migration, that configuration information is deleted when the new configuration is applied even if you do not choose a mapping for it. For example, if a target interface has an IP address before the migration and you do not select it during the mapping process, the IP address is deleted when the new configuration is applied.
You cannot map multiple source interfaces to one interface on the target platform.
If you attempt to do so, Voyager displays a message telling you that this is invalid.
The actual steps you take to complete the migration vary depending on whether there are any link aggregation group (LAG) or link redundancy group (LRG) interfaces on the source platform.
If there are no LAG or LRG interfaces
1. For each interface, choose a mapping or explicitly choose to not migrate it.
2. Choose to migrate all features (accept the default setting) or prohibit selected features from being migrated.
Remember that choosing to not migrate a feature means only that the
configuration information for that feature is not migrated. The feature itself is still available on the target. See “Migrating Features” on page 37 for important information about this step.
3. Reboot or test boot the target platform.
If there are LAG or LRG interfaces on the source
If there are LAG or LRG interfaces on the source, the process is similar except that the LAG and LRG interfaces are presented on separate pages:
1. Map or explicitly choose to not migrate each non-LAG/non-LRG interface.
2. Map or explicitly choose to not migrate each LAG interface (if any).
3. Map or explicitly choose to not migrate each LRG interface (if any).
• If an LAG interface is part of an LRG interface, you can choose whether to migrate it as part of the LRG or whether to remove it from the LRG during the migration. (If you chose to not migrate this LAG interface in step 2, it is still listed in the table of LRG interfaces but you cannot migrate it as part of the LRG.) <00491477>
Migrating Configuration Information
4. Choose to migrate all features (accept the default setting) or prohibit selected features from being migrated.
See “Migrating Features” on page 37 for important information about this step.
5. Reboot or test boot the target platform.
Note - When the Finish button is available, you can click it to skip the process of selecting features to migrate. In this case, all the IPSO features on the source are migrated (the default setting). Clicking Finish always displays a page that allows you to complete the migration by rebooting or test booting the target platform.
Migrating Features
If you include Users as one of the features that will be migrated (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 that will be migrated 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:
• optional disks
• PPPoE
• ISDN
• IPv6 host address (if the source configuration is from an IPSO version previous to 6.1) <00491728>
If configuration information for a feature cannot be migrated, the feature is not included in the list.