Sangfor AD Load Balancer Inspection Manual
Device Hardware Status Check
POWER Indicator Status Check
Inspection Requirements | When the device is operating normally, the POWER indicator light remains on. |
Inspection Method | Log in to the device remotely and check the POWER status information on the device control panel. |
Inspection Results | ![]() |
Rectification Suggestions | If the POWER indicator status is abnormal, verify whether there is a power supply anomaly or if the power module has failed. |
Device Fan Operation Status Check
Inspection Requirements | The device fans must be in normal operation, and no abnormal fan noise should occur during device operation. |
Inspection Method | Log in to the device remotely and check the device fan status information. |
Inspection Results | ![]() |
Rectification Suggestions | If there is an abnormal sound inside the device, it may be caused by abnormal operation of the fans [or hard drives]. Immediately disconnect the power supply to stop the device. If a standby machine is available, immediately switch the system to the standby machine. |
Device CPU Usage Check
Inspection Requirements | The device CPU usage rate must not exceed 80%. |
Inspection Method | Access the device status interface via the device console [Network-wide Monitoring/Home Page] to check if CPU utilization remains high for an extended period. |
Inspection Results | ![]() |
Rectification Suggestions | If CPU utilization remains high for an extended period, perform the following steps: 1. View the interface throughput column in [Network-wide Monitoring/Home Page/Traffic Analysis] to check if the current bandwidth is consistently saturated. 2. View the business traffic ranking column in [Network-wide Monitoring/Home Page/Traffic Analysis] to check if any users are generating unusually high traffic spikes. 3. Enable the device's internal network DoS attack prevention module ([Terminal Behavior Security/Internet Access Security/Safety Capabilities/Safety Configuration]) to check if the device has been subjected to a DoS attack. DoS attack prevention logs can be viewed in [System Management/System Diagnostics/System Logs]. |
Device Memory Usage Check
Inspection Requirements | The device memory usage rate must not exceed 80%. |
Inspection Method | Access the device status interface via the device console [Network-wide Monitoring/Home Page] to check if memory utilization remains high for an extended period. |
Inspection Results | ![]() |
Rectification Suggestions | If memory utilization remains high for an extended period, perform the following steps: 1. Check the interface throughput column in [Global Monitoring / Home Page / Traffic Analysis] to verify if the current bandwidth is consistently saturated. 2. Check the business traffic ranking column in [Global Monitoring / Home Page / Traffic Analysis] to identify if there are users with unusually high burst traffic. 3. Enable the device's internal network DoS attack prevention module ([Terminal Behavior Security / Terminal Internet Security / Security Capabilities / Security Configuration]). Check if the device has been subjected to DoS attacks. DoS attack prevention logs can be viewed in [System Management / System Diagnostics / System Logs]. |
Device Throughput Check
Inspection Requirements | The device's traffic throughput value must remain stable during operation, without significant traffic bursts. |
Inspection Method | Access the device status interface via the device console [Global Monitoring / Home Page] to inspect the traffic analysis situation. Traffic analysis allows for the examination of global internet traffic, including the interface throughput line chart (real-time traffic on all WAN ports), user traffic ranking, application traffic ranking, and business traffic ranking. Interface Throughput Line Chart: The device dynamically displays real-time data transmission and reception status for external interfaces using a line chart. It also shows the forwarding status of the interface over a specific time period. |
Inspection Results | ![]() |
Rectification Recommendations | If the device throughput exhibits significant bursts, check for abnormal network fluctuations or attacks. |
Rule Base Version Check
Inspection Requirements | The rule base upgrade service validity period must not be 'Expired', and the current rule base version must be up to date. |
Inspection Method | Access the device console [System Management / System Configuration / System Update / Rule Base Upgrade] interface to check the device's rule base upgrade details. |
Inspection Results | ![]() |
Rectification Recommendations | 1. If the upgrade service validity period is 'Expired', promptly purchase the corresponding authorization file. 2. When connected to the network, the device will automatically update to the latest rule base; when offline, select the option to import the latest version locally. Please update the rule base version promptly to fix vulnerabilities and defend against new intrusions and attacks. |
Dual-Node Hot Standby Status Check
Inspection Requirements | The device dual-node hot standby status must align with actual business requirements. |
Inspection Results | ![]() |
Inspection Method | Access the device console [System Management / Network Configuration / High Availability] interface to check the device's dual-node hot standby enabled status. |
Rectification Recommendations | If the dual-node hot standby service status is abnormal, check whether the configurations at both ends are correct and whether there are faults in the intermediate heartbeat link. |
High-Risk Log Content Check
Inspection Requirements | The device system logs must not contain a large number of error logs and alert logs. |
Inspection Method | Access the device console [System Management / System Diagnostics / System Logs] interface to view the running status logs of each device module. These logs can be used to determine if each module is functioning normally. |
Inspection Results | ![]() ![]() |
Images localized into English for illustration; labels may vary by product version.





