New or Replacement SGM Procedure Using Snapshot

Use this procedure to make sure that the current environment, including latest hotfixes, is installed on a new or replacement SGM. You can use this if an SGM is sent for service as an RMA.

This procedure has these basic steps:

1. Create image snapshot for the existing configuration and export it.
2. Import the snapshot to the new or replacement SGM.
3. Add the new or replacement SGM to the security group.
4. Make sure the new or replacement SGM works correctly.

To create and export a snapshot of the existing configuration:

1. Switch to an SGM on the standby Chassis:

   # blade <standby_Chassis_id>_<sgm_id>

2. Set the global mode to off:

   # set global-mode off

   This makes sure that the new snapshot image is created only on this SGM

3. Create a new image snapshot:

   # add snapshot <snapshot_name> desc <snapshot_desc>

4. Monitor the creation process progress:

   > show snapshots

5. Insert a removable disk to the USB port of the SGM and mount it to: /mnt/usb

   To learn how to mount a USB drive, see Mounting and Unmounting a USB Disk.

6. When creation process is done, export the snapshot to a tar file under /mnt/usb:

   # set snapshot export <snapshot_name_without_.tar> path /mnt/usb

7. Monitor the export process progress:

   > show snapshots

8. Un-mount /usb/mnt:

   # umount /mnt/usb

9. Remove the USB drive from the SGM.

Example

> set global-mode off

> add snapshot rma_62 desc rma

Taking snapshot. You can continue working normally.

You can use the command ‘show snapshots’ to monitor creation progress, 

> show sna

snapshot - show snapshot data

snapshots — list of local snapshots

> show snapshots

Restore points:

---------------

armdilo62_2

Restore point now under creation:

riua_62 (19%)

Creation of an additional restore point will need 2.624G

Amount of space available for restore points is il.41G

test-chO2—03> show snapshots

Restore points:

----------------

rma_62

armdi 1062_2

Creation of an additional restore point will need 2.624G

Amount of space available for restore points is 41.53G

test-chO2—03> set snapshot export rma_62 path /mnt/usb/

Exporting snapshot. You can continue working normally.

You can use the command ‘show snapshots’ to monitor exporting progress.

# blade 2_3

Moving to blade 2_3

This system is for authorized use only.

Last login: Wed Jun 20 08:43:28 2012 from test—chO2—03

CLINFRO771 This gclish instance cannot run “set” operations. To allow running “

set” operations, run “set config—lock omm Override”

> shell

# cd /mnt/usb

# ls

rzna_62 . tar

> exit

Connection to 192.0.2.17 closed.

# umount /uint/usb

To import the snapshot to the new or replacement SGM:

1. Choose the Standby Chassis and insert the new or replacement SGM in a slot that is not part of the security group.

   If all the slots are taken, reconfigure the security group and remove one of the SGM from it:

   # asg security_group

2. Insert the removable disk to the USB port of the RMA and mount it to: /mnt/usb

   To learn how to mount a USB drive, see Mounting and Unmounting a USB Disk.

3. Connect to the SGM using a console connection.
4. Import the snapshot file:

   > set snapshot import <filename_without_.tar> path /mnt/usb/

5. Monitor the import progress:

   > show snapshots

6. Unmount /mnt/usb and remove the removable disk:

   # umount /mnt/usb

7. Revert the RMA to the snapshot image:

   # set snapshot revert <snapshotname>

8. The revert takes a while and includes reboot. When the reboot starts, continue to the next step.

To add the new or replacement SGM to the security group

Update the security group to include the new or replacement SGM:

# asg security_group

To make sure the SGM works correctly:

1. Make sure that that the new or replacement SGM is up and enforces the latest policy:

   > asg monitor

2. Make sure that all the SGMs have the same operating system version:

   # asg_version