A cloud connection is a management tunnel established between a local device and the cloud server. It enables you to manage the local device from the cloud server without accessing the network where the device resides.

Multiple subconnections

After a local device establishes a connection with the cloud server, service modules on the local device can establish multiple subconnections with the microservices on the cloud server. These subconnections are independent from each other and provide separate communication channels for different services. This mechanism avoids interference among different services.

Cloud connection establishment

As shown in Figure 1, the cloud connection between the device and the cloud server is established as follows:

1. The device sends an authentication request to the cloud server.

2. The cloud server sends an authentication success packet to the device.

The device passes the authentication only if the serial number of the device has been added to the cloud server. If the authentication fails, the cloud server sends an authentication failure packet to the device.

3. The device sends a registration request to the cloud server.

4. The cloud server sends a registration response to the device.

The registration response contains the uniform resource locator (URL) used to establish a cloud connection.

5. The device uses the URL to send a handshake request (changing the protocol from HTTP to WebSocket) to the cloud server.

6. The cloud server sends a handshake response to the device to finish establishing the cloud connection.

7. After the cloud connection is established, the device automatically obtains the subconnection URLs and establishes subconnections with the cloud server based on the service needs.

Figure 1 Establishing a cloud connection

Restrictions: Hardware compatibility with cloud connection (cloud server at oasis.h3c.com)

Hardware	Cloud connection compatibility
MSR610	Yes
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK	No
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LME	Yes
MSR810-LMS-EA	No
MSR1004S-5G, MSR1004S-5G-CN	No
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	No
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-IE-ES	No
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR 3620-DP	Yes
MSR 3610, MSR 3620, MSR 3640, MSR 3660	No
MSR3610-G, MSR3620-G	No
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	Cloud connection compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	Yes
MSR830-4LM-WiNet	Yes
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	Yes
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	Yes
MSR2600-6-WiNet	Yes
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	Yes
MSR3600-28-WiNet	Yes
MSR3610-X1-WiNet	Yes
MSR3610-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	Yes
MSR3620-10-WiNet	No

Hardware	Cloud connection compatibility
MSR860-6EI-XS	No
MSR860-6HI-XS	No
MSR2630-XS	Yes
MSR3600-28-XS	Yes
MSR3610-XS	Yes
MSR3620-XS	Yes
MSR3610-I-XS	Yes
MSR3610-IE-XS	Yes
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	Cloud connection compatibility
MSR810-LM-GL	No
MSR810-W-LM-GL	No
MSR830-6EI-GL	No
MSR830-10EI-GL	No
MSR830-6HI-GL	No
MSR830-10HI-GL	No
MSR1004S-5G-GL	No
MSR2600-6-X1-GL	No
MSR3600-28-SI-GL	No

Restrictions: Hardware compatibility with cloud connection (cloud server at oasiscloud.h3c.com）

Hardware	Cloud connection compatibility
MSR610	Yes
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK	No
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LMS-EA, MSR810-LME	Yes
MSR1004S-5G, MSR1004S-5G-CN	Yes
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	No
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-IE-ES	No
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR 3620-DP	Yes
MSR 3610, MSR 3620, MSR 3640, MSR 3660	No
MSR3610-G, MSR3620-G	No
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	Cloud connection compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	No
MSR830-4LM-WiNet	No
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	No
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	No
MSR2600-6-WiNet	No
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	No
MSR3600-28-WiNet	No
MSR3610-X1-WiNet	No
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	No

Hardware	Cloud connection compatibility
MSR860-6EI-XS	Yes
MSR860-6HI-XS	Yes
MSR2630-XS	No
MSR3600-28-XS	No
MSR3610-XS	No
MSR3620-XS	No
MSR3610-I-XS	No
MSR3610-IE-XS	No
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	Cloud connection compatibility
MSR810-LM-GL	Yes
MSR810-W-LM-GL	Yes
MSR830-6EI-GL	Yes
MSR830-10EI-GL	Yes
MSR830-6HI-GL	Yes
MSR830-10HI-GL	Yes
MSR1004S-5G-GL	Yes
MSR2600-6-X1-GL	Yes
MSR3600-28-SI-GL	No

Restrictions: Hardware compatibility with cloud connection (ADWAN controllers)

Hardware	Cloud connection compatibility
MSR610	Yes
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-EI, MSR810-LM-EA, MSR810-LM-EI	Yes
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK	No
MSR810-LMS, MSR810-LUS	No
MSR810-SI, MSR810-LM-SI	No
MSR810-LMS-EA, MSR810-LME	No
MSR1004S-5G, MSR1004S-5G-CN	No
MSR1104S-W, MSR1104S-W-CAT6, MSR1104S-5G-CN, MSR1104S-W-5G-CN	Yes
MSR2600-6-X1, MSR2600-15-X1, MSR2600-15-X1-T	Yes
MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	No
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3600-28-G-DP, MSR3600-51-G-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP, MSR3610-I-IG, MSR3610-IE-IG	Yes
MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770	No
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	Yes
MSR3640-G	Yes
MSR3640-X1-HI	Yes

Hardware	Cloud connection compatibility
MSR810-W-WiNet, MSR810-LM-WiNet	No
MSR830-4LM-WiNet	No
MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet	No
MSR830-6BHI-WiNet, MSR830-10BHI-WiNet	No
MSR2600-6-WiNet	No
MSR2600-10-X1-WiNet	Yes
MSR2630-WiNet	No
MSR3600-28-WiNet	No
MSR3610-X1-WiNet	No
MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet	No

Hardware	Cloud connection compatibility
MSR860-6EI-XS	No
MSR860-6HI-XS	No
MSR2630-XS	No
MSR3600-28-XS	No
MSR3610-XS	No
MSR3620-XS	No
MSR3610-I-XS	No
MSR3610-IE-XS	No
MSR3620-X1-XS	Yes
MSR3640-XS	Yes
MSR3660-XS	Yes

Hardware	Cloud connection compatibility
MSR810-LM-GL	No
MSR810-W-LM-GL	No
MSR830-6EI-GL	No
MSR830-10EI-GL	No
MSR830-6HI-GL	No
MSR830-10HI-GL	No
MSR1004S-5G-GL	No
MSR2600-6-X1-GL	No
MSR3600-28-SI-GL	No

Configuring the cloud server

For a successful cloud connection establishment, add the serial number of the device to be managed to the cloud server. For more information about the cloud server settings, see the installation guide for the cloud server.

Configuring the local device

About this task

You can specify a cloud server by its domain name and log in to the server through the domain name on a remote PC to manage the local device.

For a device to establish a cloud connection to the cloud server, perform either of the following tasks:

· Specify the domain name of the cloud server on the device through CLI.

· Configure VLAN interface 1 of the device as a DHCP client and the cloud server as the DHCP server. The device obtains the IP address of the DHCP server and parses the option 253 field in the DHCP packets to obtain the domain name of the cloud server. When the domain name obtained through the option 253 field is an IPv4 or IPv6 address, the device uses the IPv4 or IPv6 address to connect to the cloud server. When the domain name obtained through the option 253 field is not an IPv4 or IPv6 address, the device parses the domain name into an IPv4 address. If the device fails to parse the domain name into an IPv4 address, it will not parse the domain name into an IPv6 address. For more information about the option 253 field, see DHCP configuration in Layer 3—IP Services Configuration Guide.

To establish cloud connections to the cloud server, a password is required. A device can use either of the following methods to obtain the password for establishing cloud connections to the cloud server:

· Execute the cloud-management server password command on the device to specify the password for establishing cloud connections to the cloud server.

· Configure VLAN interface 1 of the device as a DHCP client and the cloud server as the DHCP server. The device obtains the IP address of the DHCP server and parses the option 252 field in the DHCP packets to obtain the password for connection to the cloud server. For more information about the option 252 field, see DHCP configuration in Layer 3—IP Services Configuration Guide.

After establishing the cloud connection, the local device sends keepalive packets to the cloud server at the interval specified by the cloud-management keepalive interval command. If the device does not receive a response from the cloud server after the number of keepalive packets sent reached the limit specified by the cloud-management keepalive count count command, the device sends a registration request to re-establish the cloud connection.

To prevent NAT entry aging, the local device sends ping packets to the cloud server periodically.

If the cloud server verifies the token of a device before establishing a cloud connection to the device, you must configure the token on the device. To avoid authentication failure, make sure the token configured on the device is consistent with that specified for the device on the cloud server.

Restrictions and guidelines

You can specify one primary server by using the cloud-management server domain command and a maximum of eight IPv4 and IPv6 backup servers by repeating the cloud-management backup-server domain command. Each server domain name supports a maximum of three port numbers.

When establishing a cloud connection, the device can connect to only one cloud server at one time according to the sequence in which the servers are stored. The server domain names are stored in alphabet order and port numbers are in descending order. To view the connected server, execute the display cloud-management state command.

If multiple servers exist in the intranet and the NAT device has only one public IP address, you can execute this command to specify different port numbers for one server domain name.

When establishing a cloud connection, the first specified server has the highest priority. When the connected server fails, the device switches to another server and does not switch back to the original server even if the original server recovers.

The domain name obtained through DHCP has a higher priority than the domain name configured manually.

If a device obtains the domain name of the cloud server through DHCP after establishing a cloud connection to the cloud server with the manually configured domain name, the device performs the following tasks:

· If the automatically obtained and manually configured domain names are identical, the device retains the cloud connection.

· If the automatically obtained and manually configured domain names are different, the device tears down the cloud connection and then establishes a cloud connection to the cloud server with the automatically obtained domain name.

The password obtained through DHCP has a higher priority than the password configured manually.

If a device obtains the password for connection to the cloud server through DHCP after establishing a cloud connection to the cloud server with the manually configured password, the device performs the following tasks:

· If the automatically obtained and manually configured passwords are identical, the device retains the cloud connection.

· If the automatically obtained and manually configured passwords are different, the device tears down the cloud connection and then establishes a cloud connection to the cloud server with the automatically obtained password.

Reduce the ping interval value if the network condition is poor or the NAT entry aging time is short. When you use the cloud server for cloud connections, you must set the password for establishing cloud connections to the cloud server.

Prerequisites

Before configuring this feature, make sure a DNS server is configured to translate domain names.

To obtain the domain name of the cloud server automatically, first configure the option 253 field as the domain name of the cloud server.

To obtain the password for connection to the cloud server automatically, first configure the option 252 field as the password of the cloud server.

Procedure

1. Enter system view.

system-view

2. Specify the primary cloud server by its domain name.

cloud-management server [ ipv6 ] domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ip-address ]

By default, no primary cloud server is specified.

3. (Optional.) Specify a backup cloud server by its domain name.

cloud-management backup-server [ ipv6 ] domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ip-address ]

By default, no backup cloud server is specified.

4. (Optional.) Set the keepalive interval.

cloud-management keepalive interval

By default, the keepalive interval is 180 seconds.

5. (Optional.) Specify the maximum number of consecutive keepalive packets that the local device can send to the cloud server.

cloud-management keepalive count count

By default, the local device can send three consecutive keepalive packets to the cloud server.

6. (Optional.) Set the ping interval.

cloud-management ping interval

By default, the ping interval is 60 seconds.

7. (Optional.) Specify the TCP port number used by the device to initiate the authentication to the cloud server.

cloud-management server port port-number

By default, TCP port number 19443 is used by the device to initiate the authentication to a cloud server.

8. (Optional.) Set the password for establishing cloud connections to the cloud server.

cloud-management server password { cipher | simple } string

By default, no password is set for establishing cloud connections to the cloud server.

9. (Optional.) Set the token for establishing cloud connections to the cloud server.

cloud-management token { cipher | simple } string

By default, no token is set for establishing cloud connections to the cloud server.

Unbinding the device from the cloud server

About this task

A device can be registered on the cloud server by only one user.

To register a device that has been registered by another user, you need to take the following steps:

1. Obtain a verification code for device unbinding from the cloud server.

2. Execute the command on the device for sending the verification code to the cloud server.

3. Register the device on the cloud server.

Procedure

1. Enter system view.

system-view

2. Send the verification code for device unbinding to the cloud server.

cloud-management unbinding-code code

Display and maintenance commands for cloud connections

Execute display commands in any view.

Task	Command
Display cloud connection state information.	display cloud-management state

‌

Cloud connection configuration examples

Example: Configuring a cloud connection

Network configuration

As shown in Figure 2, configure the device to establish a cloud connection with the cloud server.

Figure 2 Network diagram

‌

Procedure

1. Configure IP addresses for interfaces as shown in Figure 2, and configure a routing protocol to make sure the devices can reach each other. (Details not shown.)

2. Log in to the cloud server to add the serial number of the device to the server. (Details not shown.)

3. Configure the domain name of the cloud server as oasiscloud.h3c.com.

<Device> system-view

[Device] cloud-management server domain oasiscloud.h3c.com

NOTE:

· The DNS service is provided by the ISP DNS server.

· The domain name and IP address used here are for illustration only.

‌

Verifying the configuration

# Verify that the device and the cloud server have established a cloud connection.

[Device] display cloud-management state

Cloud connection state : Established

Device state : Request_success

Cloud server address : 52.163.242.100

Cloud server domain name : oasiscloud.h3c.com

Cloud connection mode : Https

Cloud server authentication port : 19443

Cloud server connection port : 443

Connected at : Wed Jan 27 14:18:40 2018

Duration : 00d 00h 02m 01s

Process state : Message received

Failure reason : N/A

Last down reason : socket connection error (Details:N/A)

Last down at : Wed Jan 27 13:18:40 2018

Last report failure reason : N/A

Last report failure at : N/A

Dropped packets after reaching buffer limit : 0

Total dropped packets : 1

Last report incomplete reason : N/A

Last report incomplete at : N/A

Buffer full count : 0

Cloud connection configuration examples

Example: Configuring a cloud connection

Network configuration

As shown in Figure 3, configure the AC to establish a cloud connection with the cloud server.

Figure 3 Network diagram

‌

Procedure

1. Configure IP addresses for interfaces as shown in Figure 3, and configure a routing protocol to make sure the devices can reach each other. (Details not shown.)

2. Log in to the cloud server to add the serial number of the AC to the server. (Details not shown.)

3. Configure the domain name of the cloud server as oasiscloud.h3c.com.

<AC> system-view

[AC] cloud-management server domain oasiscloud.h3c.com

NOTE:

· The DNS service is provided by the ISP DNS server.

· The domain name and IP address used here are for illustration only.

‌

Verifying the configuration

# Verify that the AC and the cloud server have established a cloud connection.

[AC] display cloud-management state

Cloud connection state : Established

Device state : Request_success

Cloud server address : 52.163.242.100

Cloud server domain name : oasiscloud.h3c.com

Cloud connection mode : Https

Cloud server authentication port : 19443

Cloud server connection port : 443

Connected at : Wed Jan 27 14:18:40 2018

Duration : 00d 00h 02m 01s

Process state : Message received

Failure reason : N/A

Last down reason : socket connection error (Details:N/A)

Last down at : Wed Jan 27 13:18:40 2018

Last report failure reason : N/A

Last report failure at : N/A

Dropped packets after reaching buffer limit : 0

Total dropped packets : 1

Last report incomplete reason : N/A

Last report incomplete at : N/A

Buffer full count : 0

Cloud connection configuration examples

Example: Configuring a cloud connection

Network configuration

As shown in Figure 4, configure the AP to establish a cloud connection with the cloud server.

Figure 4 Network diagram

‌

Procedure

1. Configure IP addresses for interfaces as shown in Figure 4, and configure a routing protocol to ensure that the devices can reach each other. (Details not shown.)

2. Log in to the cloud server to add the serial number of the AP to the server. (Details not shown.)

3. Configure the domain name of the cloud server as oasiscloud.h3c.com.

<AP> system-view

[AP] cloud-management server domain oasiscloud.h3c.com

NOTE:

· The DNS service is provided by the ISP DNS server.

· The domain name and IP address used here are for illustration only.

‌

Verifying the configuration

# Verify that the AP and the cloud server have established a cloud connection.

[AP] display cloud-management state

Cloud connection state : Established

Device state : Request_success

Cloud server address : 52.163.242.100

Cloud server domain name : oasiscloud.h3c.com

Cloud connection mode : Https

Cloud server authentication port : 19443

Cloud server connection port : 443

Connected at : Wed Jan 27 14:18:40 2018

Duration : 00d 00h 02m 01s

Process state : Message received

Failure reason : N/A

Last down reason : socket connection error (Details:N/A)

Last down at : Wed Jan 27 13:18:40 2018

Last report failure reason : N/A

Last report failure at : N/A

Dropped packets after reaching buffer limit : 0

Total dropped packets : 1

Last report incomplete reason : N/A

Last report incomplete at : N/A

Buffer full count : 0

15-Network Management and Monitoring Configuration Guide

Configuring cloud connections

About cloud connections

Restrictions: Hardware compatibility with cloud connection (cloud server at oasiscloud.h3c.com）

Configuring the cloud server

About this task

Restrictions and guidelines

Prerequisites

Procedure

About this task

Procedure

Display and maintenance commands for cloud connections

Network configuration

Procedure

Verifying the configuration

Example: Configuring a cloud connection

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us