1.3.5. Notes on upgrading from Version 1 to Version 2¶
Please note the following about the version upgrade function. It may not be possible to upgrade the version at the timing you desire, so we would appreciate it if you could plan multiple work schedules in advance.
-It takes about 80 minutes to upgrade one device.
-When upgrading the version of Managed WAF, a total of about 10 minutes of communication interruption will occur.
-Version upgrade processing will be performed sequentially for each region.
Example 1) When 3 devices are being upgraded in JP1 (1 device is running, 2 devices are waiting), if you execute the upgrade function in JP1, a maximum of 240 minutes will be waited before the upgrade starts.
Example 2) Even when 3 devices are being upgraded in JP1 (1 device is running and 2 devices are waiting), if there are no devices being upgraded in JP2, There is no waiting time to start version upgrade of JP2.
-The display of the estimated waiting time is provided in the version upgrade function.
-If the version upgrade function is executed, the status cannot be canceled even if the status is waiting for the version upgrade.
-Communication interruption does not occur while waiting for version upgrade.
・ If you want to move from Version 1 to another plan of Version 2, you need to change the plan after moving to Version 2 with the same plan.
Example: If you want to change from Managed WAF (2CPU-4GB) Version1 to Managed WAF (4CPU-6GB) Version2.
STEP1: Upgraded from Managed WAF (2CPU-4GB) Version1 to Managed WAF (2CPU-4GB) Version2. (Communication interruption occurred)
STEP2: Plan change from Managed WAF (2CPU-4GB) Version 2 to Managed WAF (4CPU-6GB) Version 2. (Communication interruption occurred)
-Logs and Incident Reports before the version upgrade will not be carried over to Version 2. In addition, after the version upgrade, you will not be able to check past logs on the Version 1 portal.
-The device KPI before the version upgrade will not be carried over to Version 2.
・As you can see in here, some Signature IDs have been changed. If the Signature ID registered in the White List / Block List is applicable, the ID setting will be deleted after the version upgrade. If you are concerned about the communication impact due to the deletion of the Signature ID setting, change to Monitor mode before upgrading, check the communication impact after upgrading, and then cancel Monitor mode. See here for Monitor mode settings.