Compatibility: Check whether the target version is compatible with the current hardware (such as servers and NICs) and business systems (such as VM operating system and databases).
Service impact: Assess the amount of time required for the upgrade. It is recommended to perform the upgrade during off-peak hours, such as early mornings on weekends. Confirm whether core service migration is required.
Rollback preparation: Back up the system configuration and service data, and provide a rollback plan. Make sure that SCP can be rolled back to the original version when the upgrade fails.
Upgrade guidelines:
Follow the "test before production" principle to verify the upgrade procedure and its compatibility in a test environment before you perform the upgrade in the production environment.
[8]
SP guidelines:
SP selection: Install only compatible SPs released by Sangfor. Do not install third-party SPs. Prioritize SPs that fix high-risk vulnerabilities.
SP verification: After SP installation, check whether the SP takes effect (for example, use the CLI) and make sure that no service compatibility issues exist.