Device Configuration Backup
GigaVUE‑FM retrieves and stores the device configuration in binary and text formats. GigaVUE‑FM restores the device configurations in binary format and allows you to view the configurations in text format. The advantage of the binary format is that it backs up all state parameters, including system parameters.
Version Compatibility
|
■
|
For GigaVUE devices 5.1 version onwards, GigaVUE‑FM will take a binary backup of those devices. For devices prior to version 5.1, GigaVUE‑FM will continue to take text-based backups. |
|
■
|
For backups taken in text format in GigaVUE‑FM v5.4.01 or above, GigaVUE‑FM will allow those configurations to be restored. |
|
■
|
Before GigaVUE‑FM v5.500, the configuration backup was text based, which was intended to backup only traffic related configs. |
Points to Remember
|
■
|
Describe your backup: Provide a meaningful name and comments while taking the backup, to help track the configuration while restoring. |
|
■
|
View your backup: You can view and download the text format of binary contents for readability. Some details in the binary content might not appear in text format. |
|
■
|
View the restore report: After performing a restore operation, a restore report displays the results of the restore operation such as the success or failure as well as all the logs from the leader device. |
Restore Configuration (RMA'ed device)
The following are the steps to be performed for Standalone and Cluster Nodes:
Standalone Devices (RMA):
|
1.
|
Make a backup on Device A, which will contain Device A details (Serial Number, chassis ID, GUID, etc.) |
|
2.
|
Device A has now failed. |
|
3.
|
Order and get a new device, Device B (identical hardware inventory, except all the hardware serial numbers are different). |
|
4.
|
Power up Device B and assign it a hostname and IP address. |
|
5.
|
The hostname should be the same as the previous device. |
|
6.
|
The IP address should be the same. (Different IP addresses are supported, but not recommended.) |
|
7.
|
On GigaVUE‑FM, restore the backup of Device A onto this device: |
|
a.
|
If the IP address is the same, then it will get discovered as Device A. |
|
b.
|
If the IP address is not the same, restore the Device A data onto the Device B (IP address, etc.) |
|
c.
|
Now the backup taken on device A is pushed to device B. |
|
d.
|
When the backup is complete, GigaVUE‑FM invokes a new “Migration” API from the node. |
|
e.
|
When the process is complete, Device B is restored to Device A’s configuration. |
A node of the cluster (RMA):
|
1.
|
The binary backup of the cluster is available in GigaVUE‑FM. |
|
4.
|
Configure the node B with the IP address, hostname, cluster ID, cluster VIP etc. |
|
5.
|
Node B joins into the cluster. |
|
6.
|
Cluster leader will push the config to the new node, which will not apply to its hardware since its serial number does not match. |
|
7.
|
GigaVUE‑FM will now discover node B back in the inventory. |
|
8.
|
Instruct GigaVUE‑FM to migrate the configuration of node B, from the old serial number to the new one. |
|
9.
|
This will be sent to the Leader of the cluster (and new API that will be provided same as 7 above). |
|
10.
|
Cluster leader will do the migration and push the configuration to the new node |
Note:
| ■ | GigaVUE‑FM handles the UUID stored in GigaVUE‑FM. |
| ■ | GigaVUE‑FM has a dependency on the device API to migrate configuration of RMA box to a new serial number. |
