If the FW starts with a specified profile, the deployment personnel must manually configure the FW to connect to the cloud management platform.
The deployment personnel can switch the operating mode of the FW to cloud management mode on the web UI. For details, see Configuring Cloud Management Using the Web UI.
The deployment personnel can switch the operating mode of the FW to cloud management mode through the CLI. For details, see Configuring Cloud Management Using the CLI.
The deployment personnel can place the profile in the USB disk in advance. After the FW starts, it switches its operating mode to cloud management mode, and then the profile in the USB disk is loaded. For details, see Upgrade Through USB.
The USB upgrade mode applies to batch deployment scenarios. Deployment personnel need to configure the profile once only in that this profile can be repeatedly used on multiple devices. Compared with the CLI and web UI modes, the USB mode helps reduce the configuration workload and boost the deployment efficiency.
After the FW operating in cloud management mode is connected to the Internet, it immediately initiates a connection request towards the cloud management platform. After the connection succeeds and the authentication is passed, the FW is incorporated into the management of the cloud management platform. Figure 1 shows the process.
The connection request carries the device certificate of the FW for the cloud management platform to authenticate the FW.
The established NETCONF channel transmits the subsequent query request and service configuration.
The cloud management platform can properly deliver the service configuration to the FW, indicating that the FW has been incorporated into the management of the cloud management platform. The FW incorporated into the cloud management platform proactively reports NETCONF Notification alarms to the cloud management platform. For alarm details, see API Development Guide.