Adding or Replacing an SGM on Scalable Chassis

You can perform an operating system upgrade on a new or replacement SGM.

There are two methods to update operating system versions:

  • Create a snapshot image from one of the SGMs on the Standby Chassis and revert the new SGM to this snapshot.

  • Install from a distribution media (a CD/DVD, or a USB device).

Using Snapshot Image to Add a New or a Replacement SGM

Use snapshot as a backup. Confirm that the latest hotfixes are installed on a new or replacement SGM (or if an SGM is sent for service as an RMA).

Best Practice - In a Dual Chassis configuration, create a snapshot on one of the SGMs on the Standby Chassis.

Step

Procedure

Instructions

Notes

1

Connect to the command line on the Standby Chassis, over an SSH or console connection.

 

 

2

Log in to the Expert mode.

gHostName> expert

 

3

Go to one of the SGMs on the Standby Chassis.

[Expert@HostName-ch0X-0X:0]# member <ID of Standby Chassis>_<SGM ID>

Example:

[Expert@HostName-ch0x-0x:0]# member 2_3

4

Disable the global mode.

gHostName> set global-mode off

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

5

Create a new snapshot image.

HostName> add snapshot <Snapshot_Name> desc "<Snapshot Description>"

Example:

[Global] HostName-ch01-01 > add snapshot <Snapshot_Working_SGM> desc "Snapshot of a working SGM #3 on the Standby Chassis"

6

Monitor the progress of the snapshot image creation.

HostName> show snapshots

Run this command repeatedly.

The process can take 15 - 20 minutes.

7

Insert a USB removable disk in the USB port of the SGM, and mount it to the /mnt/usb directory.

  1. Find the device name for the USB removable disk in one of these ways:

    • In the /var/log/messages file:

      [Expert@HostName-ch0X-0X:0]# tail /var/log/messages

      Example:

      :SCSI device sdb: 7827392 512-byte hdwr sectors (4008 MB)

      sdb: Write Protect is off

      sdb: assuming drive cache: write through

      SCSI device sdb: 7827392 512-byte hdwr sectors (4008 MB)

      sdb: Write Protect is off

      sdb: assuming drive cache: write through

      sdb: sdb1

      sd 9:0:0:0: Attached scsi removable disk sdb

      sd 9:0:0:0: Attached scsi generic sg1

    • With the "fdisk -l" command:

      [Expert@HostName-ch0X-0X:0]# fdisk -l

  2. Create the /mnt/usb directory:

    [Expert@HostName-ch0X-0X:0]# mkdir -p /mnt/usb

  3. Mount the USB removable disk (for example: /dev/sdb1) to your /mnt/usb directory:

    [Expert@HostName-ch0X-0X:0]# mount /dev/sdb1 /mnt/usb

8

When the image creation is complete, export the snapshot image file to a TAR file on the local SGM.

HostName> set snapshot export <Name of Snapshot Image File Without the .TAR Extension> path /home/admin

Later, you copy this file to the USB device.

9

Monitor the progress of the snapshot image creation.

HostName> show snapshots

Run this command repeatedly.

The process can take 15 - 20 minutes.

10

Copy the snapshot file to the USB removable disk.

[Expert@HostName-ch0X-0X:0]# cp -v /home/admin/<Name of Snapshot Image File Without the .TAR Extension>.tar /mnt/usb/

 

11

Check the snapshot image TAR file on the USB removable disk.

[Expert@HostName-ch0X-0X:0]# ls -l /mnt/usb/

 

12

Unmount the USB removable disk from the /usb/mnt directory.

[Expert@HostName-ch0X-0X:0]# umount /mnt/usb

 

13

Remove the USB removable disk from the SGM.

 

 

Step

Procedure

Instructions

Notes

14

Insert the replacement SGM into a slot that is not part of any Security Group.

 

If all the slots are used, reconfigure the Security Group to remove one of the SGMs from it:

HostName> delete smo security-group <SGM ID>

15

Connect to the command line on the replacement SGM.

 

 

16

Disable the global mode.

gHostName> set global-mode off

This makes sure that the new snapshot image applies only to this SGM.

17

Connect to the replacement SGM over a console connection.

 

 

18

Insert a USB removable disk in the USB port of the replacement SGM, and mount it to the /mnt/usb directory.

  1. Find the device name for the USB removable disk in one of these ways:

    • In the /var/log/messages file:

      [Expert@HostName-ch0X-0X:0]# tail /var/log/messages

      Example:

      :SCSI device sdb: 7827392 512-byte hdwr sectors (4008 MB)

      sdb: Write Protect is off

      sdb: assuming drive cache: write through

      SCSI device sdb: 7827392 512-byte hdwr sectors (4008 MB)

      sdb: Write Protect is off

      sdb: assuming drive cache: write through

      sdb: sdb1

      sd 9:0:0:0: Attached scsi removable disk sdb

      sd 9:0:0:0: Attached scsi generic sg1

    • With the "fdisk -l" command:

      [Expert@HostName-ch0X-0X:0]# fdisk -l

  2. Create the /mnt/usb directory:

    [Expert@HostName-ch0X-0X:0]# mkdir -p /mnt/usb

  3. Mount the USB removable disk (for example: /dev/sdb1) to your /mnt/usb directory:

    [Expert@HostName-ch0X-0X:0]# mount /dev/sdb1 /mnt/usb

19

Copy the snapshot file from the USB removable disk to the replacement SGM.

[Expert@HostName-ch0X-0X:0]# cp -v /mnt/usb/<Name of Snapshot Image>.tar /home/admin/

 

20

Import the snapshot image file.

HostName> set snapshot import <Name of Snapshot Image File Without the .TAR Extension> path /home/admin/

 

21

Monitor the progress of the snapshot image import.

HostName> show snapshots

Run this command repeatedly.

The process can take 15 - 20 minutes.

22

Unmount the USB removable disk from the /mnt/usb directory.

[Expert@HostName-ch0X-0X:0]# umount /mnt/usb

 

23

Remove the USB removable disk from the replacement SGM.

 

 

24

Revert the snapshot image.

HostName> set snapshot revert <Snapshot_Name>

Revert can take 15 - 20 minutes.

During the revert, the SGM can reboot several times.

Proceed to the next step after the revert is complete.

25

Connect to the command line on the chassis, over an SSH or console connection.

 

 

26

Log in to the Expert mode.

gHostName> expert

 

27

Update the Security Group to include the replacement SGM.

HostName> add smo security-group <SGM ID>

You can run this command:

HostName> add smo security_group {$NEW_SGM_ID}

28

Confirm that the replacement SGM is in the state "UP" and enforces the latest policy.

[Expert@HostName-ch0X-0X:0]# asg monitor

 

29

Confirm that all SGMs on the chassis have the same OS version.

[Expert@HostName-ch0X-0X:0]# asg_version

 

 
[Expert@HostName-ch0x-0x:0]# gclish
 
[Global] HostName-ch01-01 > set global-mode off
 
HostName-ch01-01 > add snapshot rma_62 desc rma
Taking snapshot. You can continue working normally.
You can use the command 'show snapshots' to monitor creation progress,
 
HostName-ch01-01 > 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
 
HostName-ch01-01 > 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
 
HostName-ch01-01 > 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.
 
HostName-ch01-01 > set global-mode on
 
[Global] HostName-ch01-01 > exit
 
[Expert@HostName-ch0x-0x:0]# member 2_3
Moving to blade 2_3
This system is for authorized use only.
Last login: Wed Jun 20 08:43:28 2012 from HostName-ch02-03
 
[Expert@HostName-ch0x-0x:0]# cd /mnt/usb
 
[Expert@HostName-ch0x-0x:0]# ls
rzna_62.tar
 
[Expert@HostName-ch0x-0x:0]# umount /uint/usb

Installing a New SGM Using a CD/DVD Device

Step

Instructions

1

Burn the required image onto a CD/DVD.

See the R82 Home Page: sk181127..

2

Install the new SGM into an unoccupied slot in the Standby Chassis.

3

If necessary, reconfigure the Security Group to include the new SGM.

4

Connect to the new SGM with a console connection.

5

Remove the SGM boot sector:

eraseboot

6

Connect the CD/DVD device to the SGM.

7

Reboot the SGM:

  1. Pull it out

  2. Insert it

8

The installation starts.

Follow the instructions in the console connection to the new SGM.