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