In a CPUSE upgrade scenario, you perform the upgrade procedure on the same Security Management Server.
Notes:
Important - Before you upgrade a Security Management Server:
Step |
Description |
---|---|
1 |
|
2 |
See the Upgrade Options and Prerequisites. |
3 |
In R80 and above, examine the SmartConsole sessions:
|
4 |
You must close all GUI clients (SmartConsole applications) connected to the source Security Management Server. |
Workflow:
Step 1 of 6: Upgrade the Security Management Server with CPUSE
See Installing Software Packages on Gaia and follow the applicable action plan for the local installation.
Step 2 of 6: Install the R80.20 SmartConsole
Step 3 of 6: Upgrade the dedicated Log Servers and dedicated SmartEvent Servers
If your Security Management Server manages dedicated Log Servers or SmartEvent Servers, you must upgrade these dedicated servers to the same version as the Security Management Server:
Step 4 of 6: Install the management database
Step |
Description |
---|---|
1 |
Connect with SmartConsole to the R80.20 Security Management Server. |
2 |
In the top left corner, click Menu > Install database. |
3 |
Select all objects. |
4 |
Click Install. |
5 |
Click OK. |
Step 5 of 6: Install the Event Policy
This step applies only if the SmartEvent Correlation Unit Software Blade is enabled on the R80.20 Security Management Server.
Step |
Description |
---|---|
1 |
Connect with the SmartConsole to the R80.20 Security Management Server. |
2 |
In the SmartConsole, from the left navigation panel, click Logs & Monitor. |
3 |
At the top, click + to open a new tab. |
4 |
In the bottom left corner, in the External Apps section, click SmartEvent Settings & Policy. The Legacy SmartEvent client opens. |
5 |
In the top left corner, click Menu > Actions > Install Event Policy. |
6 |
Confirm. |
7 |
Wait for these messages to appear:
|
8 |
Click Close. |
9 |
Close the Legacy SmartEvent client. |
Step 6 of 6: Test the functionality
Step |
Description |
---|---|
1 |
Connect with the SmartConsole to the R80.20 Security Management Server. |
2 |
Make sure the management database and configuration were upgraded correctly. |