In This Section: |
To upgrade from a minor release, use an HFA Upgrade package. Download it from the R76SP.50 60000/40000 Security Platforms Home Page.
Use this procedure to upgrade to R76SP.50 from: R76SP.10, R76SP.20, R76SP.30 and R76SP.40.
Notes:
vsx stat -v
Upgrade Chassis B through an SGM on Chassis A, and then upgrade Chassis A through an SGM on Chassis B.
Change the system back to VSX VSLS mode when the upgrade procedure is complete.
-c
, enter the Chassis ID only, not the word chassis
.For example: # asg chassis_admin -c 1 down
-b
, enter the word Chassis and its ID of Chassis1 or Chassis2.For example: # g_reboot -a -b chassis1
Step |
Operation |
Command |
1 |
Make sure that all SGMs and SSMs are up to date and that the system is configured correctly. |
|
2 |
Copy the HFA Upgrade package to the SMO. |
|
3 |
Create a temporary directory on the SMO in:
|
If a temporary directory already exists, delete it first with this command:
|
4 |
Extract the HFA Upgrade package to the temporary directory. |
|
Best Practice - Connect over a console to the SMO and run the next steps through the console connection. |
||
5 |
Run the pre-installation script. |
|
Step |
Operation |
Command |
6 |
Set Chassis B to administratively DOWN state. |
|
7 |
Make sure that Chassis B is in administratively DOWN state. |
|
8 |
Upgrade Chassis B. Note - Make sure to run the script from Chassis A and not Chassis B. |
|
Confirm that the HFA Upgrade installation procedure completed successfully. A summary message shows when the upgrade is complete. |
||
9 |
If the installation was successful: a. You are prompted to upgrade the SSM firmware. You can do this now or later. b. Reboot the SGMs when prompted. Wait until all SGMs are UP. |
If you do not upgrade the firmware now at the prompt, upgrade it later with:
|
10 |
Make sure that all SGMs show the correct version. Note - SGMs on Chassis A show as failed, or show the previous version. This is normal, and you can continue to the next step. |
|
Step |
Operation |
Command |
11 |
Set Chassis B to administratively UP state. |
|
12 |
Run the diagnostics. |
|
13 |
Make sure that Chassis B is UP and enforces security. Important - You must correct all errors shown by the diagnostics before you continue to the next step. |
|
14 |
Set Chassis A to administratively DOWN state. |
|
15 |
Make sure that all SGMs are UP, and that traffic flows normally on Chassis B. Important - Make sure Chassis B works correctly before you upgrade Chassis A. |
|
Step |
Operation |
Command |
16 |
Copy the HFA Upgrade package to the SMO. |
|
17 |
Create a temporary directory on the SMO in:
|
If a temporary directory already exists, delete it first with this command:
|
18 |
Extract the HFA Upgrade package to the temporary directory. |
|
Best Practice - Connect over a console to the SMO and run the next steps through the console connection. |
||
19 |
Make sure that Chassis A is in administratively DOWN state. |
|
20 |
Upgrade Chassis A. Note - Make sure to run the script from Chassis B and not Chassis A. |
|
Confirm that the HFA Upgrade installation procedure completed successfully. A summary message shows when the upgrade is complete. |
||
21 |
If the installation was successful: a. You are prompted to upgrade the SSM firmware. You can do this now or later. b. Reboot the SGMs when prompted. Wait until all SGMs are UP. |
If you do not upgrade the firmware now at the prompt, upgrade it later with:
|
Step |
Operation |
Command |
22 |
Set Chassis A to administratively UP state. |
|
23 |
Run the diagnostics. |
|
24 |
Make sure that Chassis A is UP and enforces security. Important - You must correct all errors shown by the diagnostics before you continue to the next step. |
|
Step |
Operation |
Command |
25 |
Run the finalize step. Note - This is a mandatory step. |
|
26 |
Make sure all SGMs and SSMs are up to date, and that the system is configured correctly. |
|
27 |
Delete the upgrade files from all relevant SGMs. |
|
To upgrade the Chassis, you must use two SGM groups.
You should not upgrade all the SGMs at the same time.
With this procedure, upgrade half of the SGMs at one time.
The other half continues to handle traffic.
Upgrade Group B SGMs through an SGM of Group A, and then upgrade Group A SGMs through an SGM of Group B.
Step |
Operation |
Command |
---|---|---|
1 |
Make sure that all SGMs and SSMs are up to date, and that the system is configured correctly. |
|
2 |
Divide the SGMs into two groups (A and B). SGMs in Group A remain Active and continue to handle traffic while you upgrade SGMs in Group B. Then, fail over between SGMs from Group A to Group B, which handles traffic while you upgrade SGMs in Group A. |
|
3 |
Copy the HFA Upgrade package to the SMO:
Important - The SMO must be an SGM of Group A. |
|
4 |
Create a temporary directory on the SMO in:
|
If a temporary directory already exists, delete it first with this command:
|
5 |
Extract the HFA Upgrade package to the temporary directory. |
|
Best Practice - Connect over a console to the SMO and run the next steps through the console connection. Console connection is not mandatory, if you skip the SSM firmware upgrade step in the upgrade process. |
||
6 |
Run the pre-installation procedure. |
|
Step |
Operation |
Command |
---|---|---|
7 |
Set SGMs in Group B to administratively DOWN state. |
|
8 |
Make sure that all SGMs in Group B are DOWN. |
|
9 |
Upgrade SGMs in Group B. |
|
Confirm that the HFA Upgrade installation procedure completed successfully. A summary message shows when the upgrade is complete. If the installation was successful, you are prompted to run SSM firmware upgrade checks. Do not do that at this time. |
||
10 |
When prompted, reboot SGMs in Group B. After reboot, the SGMs on Group B stay in the administratively DOWN state. |
Step |
Operation |
Command |
---|---|---|
11 |
Run the diagnostics. |
|
12 |
Set SGMs in Group B to administratively UP state. |
|
13 |
Make sure that all SGMs in Group B are UP and enforce security. |
|
14 |
Set SGMs in Group A to administratively DOWN state. |
|
15 |
Make sure that the SGMs in Group B are UP and enforce security. Important - Make sure SGMs in Group B work correctly before you upgrade SGMs in Group A. |
|
Step |
Operation |
Command |
---|---|---|
16 |
Copy the HFA Upgrade package to the SMO:
Note - The SMO must be an SGM of Group B. |
|
17 |
Create a temporary directory on the SMO in:
|
If a temporary directory already exists, delete it first with this command:
|
18 |
Extract the HFA Upgrade package to the temporary directory. |
|
Best Practice - Connect over a console to the SMO and run the next steps through the console connection. A console connection is not mandatory, if you skip the SSM firmware upgrade step in the upgrade process. |
||
19 |
Make sure that all SGMs in Group A are DOWN. |
|
20 |
Upgrade SGMs in Group A. |
|
Confirm that the HFA Upgrade installation procedure completed successfully. A summary message shows when the upgrade is complete. If the installation was successful, you are prompted to run SSM firmware upgrade checks. Do not do this at this time. |
||
21 |
When prompted, reboot Group A SGMs. After reboot, the Group A SGMs stay in the Admin DOWN state. |
|
Note - You can run the SSM firmware upgrade now. Press Y at the prompt. This will cause some downtime.
Step |
Operation |
Command |
---|---|---|
22 |
Run the finalize step. Note - This is a mandatory step. |
|
23 |
Make sure all SGMs and SSMs are up to date, and that the system is configured correctly. |
|
24 |
Delete the upgrade files on all SGMs on both the Active and Standby Chassis. |
|