Upgrade Plan Overview

Main Features of the Version

New Features/ Optimization

Some known issues have been fixed.

Other Matters

None.

Upgrade Impact

None.

Impact on Business

VDI services will not be interrupted, and there is no need to shut down or restart the HCI/ VDC/ virtual machines.

Impact on Operations and Maintenance

During the upgrade process, maintenance personnel are prohibited from logging in to the IOM backend to perform maintenance operations.

Impact on Customer Networks

The platform upgrade process has no impact on network communications.

Other Impacts

None.

Customer Preparation

Upgrade Coordination

Coordinate with upgrade personnel in advance to ensure no impact on production operations during the upgrade process. Please refer to the table below for the impact time on IOM functions.

Operation	Time
Open the IOM platform web console page and upload the upgrade package.	5-10 minutes​
Start the IOM upgrade and wait until it is complete.	10 minutes​
Restart the IOM system after the upgrade is successful.	10-15 minutes​​

Notify Customers

During the upgrade process, maintenance personnel are prohibited from logging in to the IOM backend for operations and maintenance.

Upgrade Implementation Process

Stage	Content	Time
First stage	IOM Upgrade	25 minutes
Second stage	Pagent Upgrade	On average, one upgrade takes 5 to 30 seconds. In addition, to avoid upgrade storms, IOM will perform staggered upgrades on Pagent. The number of concurrent users is 10.

Upgrade Notes

If the IOM is a virtual machine, make sure to make a snapshot backup of the virtual machine before upgrading the system.

Post-Upgrade Verification

1. Check the login page to see the version.

2. Check whether the data on virtual machine status, node status, cluster status, etc., are retrieved normally. (After the upgrade is completed, it takes 1-2 hours for the page data to be restored.)

Emergency Rollback Plan

1. In case of upgrade failure, FAE and partner must retain the failure status and are prohibited from rolling back on their own.

2. Contact TAC or R&D for further action.

Upgrade Operation Guide

Preparation Before Upgrade

Upgrade Tool Preparation

Name	Function	Download
IOM Upgrade Package	The upgrade package of the IOM component needs to be uploaded for installation on the IOM web console.	Download link

Environmental Information Collection

Platform Name	IP​	Username/ Password
IOM

Coordinate Customer Resources

To ensure the smooth progress of the upgrade work, please follow the requirements below for resource coordination:

1. Determine the upgrade time and be fully prepared for business interruptions that might occur during the upgrade process to reduce the impact.

2. Effective contact information for the person in charge of the upgrade site.

3. The upgrade site requires a computer (with Internet access and a stable connection to the IOM backend and IOM console).

Category	Name	Contact Information	Responsibility
Sangfor Technology			IOM component upgrade.
Customer			Responsible for coordinating resources and upgrade timing. (upgrade time: )
Customer			Maintenance personnel are prohibited from logging in to the IOM component for operations and maintenance.
Customer			The system leader is responsible for service activation and verification of the application system.

Pre-Upgrade Checks

Item	Content
Version	IOM’s current version.
Upgrade package	The IOM upgrade package has been downloaded. And verify that the MD5 value is correct.
Upgrade tools	Chrome or other browsers.

Upgrade Steps

Upgrade Path

Version correspondence:

IOM Version	VDC Version	Supported Monitoring Scope
2.0​	VDC 5.9.1–VDC 5.9.1R1	Virtual machine (Win7, Win10, Win 11) HCI (X86) VDC (X86)
2.1.0	VDC 5.9.1–VDC 5.9.1R1	Virtual machine (Win7, Win10, Win 11) HCI (X86) VDC (X86)

Upgrade Steps

1. Log in to the IOM platform by entering the admin username and password.

2. On the IOM web console, click the Settings icon in the lower-left corner. Select System Settings > System Upgrade to enter the upgrade page, and click Upgrade Now.

3. Click Upload Upgrade Package to upload the upgrade package to the device.

4. After completing the upload, click Next to start the upgrade.

5. The device will restart once the upgrade is completed.

6. The IOM will automatically restart all services. Wait for 10-15 minutes, refresh the browser manually. After the browser restarts and displays the login page normally, verify whether the version has been upgraded.

Post-Upgrade Checks

Verify Platform Status

1. Check the login page to see whether the version number is 2.1.0.

2. Check whether the Pagent has been upgraded to the latest version 1.2.0.xxx. (The last number of the version does not matter.)

Verify Business Operation Status

1. Check whether the status of the virtual machines, servers, and clusters are retrieved normally.

2. Click the virtual machine details to check whether the real-time process is consistent with the process running on the virtual machine.

Troubleshooting

Wrong Secret Key Prompt After Upgrade

In version 2.0, the problem of IOM mapping to the public network due to the hard-coded internal network address in the front-end script was solved, with the assistance of R&D. However, the file would disappear after the upgrade. At this time, a layer of forwarding needs to be added:

/opt/iom-platform/laganalyser/dockerfiles/business

There is a .env file in the directory. Add a line:

IP_LIST=xxx .com

xxx.com is the domain name mapped to the public network.

Emergency Rollback Plan (Virtual Machine Restoration)

If the issue cannot be fixed, please restore the virtual machine using the snapshot.