Description
Migrating from SA 200 to SA 2000
Scope
KB ARTICLE TYPE: Design
RELATED PRODUCTS: Ezrf SA 1000, SA 200, SA 2000
RELATED SOFTWARE VERSIONS: 3.0 onwards
KEYWORDS: Ezrf, hardware upgrade, SA 2000 , SA 1000 , SA 200, Network Manager
Solution
1. Back up the SA200 data using the CLI command backup all:
SA200# backup all
2. Copy the backup file from the SA200 appliance to an external location using the
CLI command copy. For example:
SA200# copy /data/backup/nms/Backup-2.2-30-SA200-2009-12-07-06-37-
39.tar.gz ftp://anonymous@<ip address>/
3. Turn off SA200 and disconnect it.
4.Set up the SA2000, following the directions in the Meru Service Appliance User
Guide. Configure the same host name, network, time zone and other details as
those configured on the SA200 server.
5. Copy the backup file from the external location to the SA2000 using the CLI
command copy. For example:
SA2000# copy ftp://anonymous@<ip address>/Backup-2.2-30-SA200-2009-12-07-
06-37-39.tar.gz /data/backup/nms/
6. Restore the backup on the SA2000 using the CLI command restore. For example:
SA2000# restore Backup-2.2-30-SA200-2009-12-07-06-37-39.tar.gz
This command takes time. Do you want to continue [y|n]? y
SA2000#
Help:
1.NM ( Network Manager ) firmware versions can be different to an extent ( SA 1000 is 3.0.46 and the new SA 2000 3.2 )
2.Heat maps will be automatically migrated.
3.You cannot register one controller on two NMS servers, which means you have to unplug the old NM server after taking the backup and configure the new NM server with the same IP address / host name etc as on the SA 1000 and plug the SA 2000 on to the network.
4. You need to get new set of licenses for SA 2000 as the system ID changes for the new NM server and old licenses cannot be used.
5. Migrating tool is used only for NM 1 and NM 2 versions where NM is hosted on windows 2003 server.
