Login
- Table of Contents
-
- 17-Network Management and Monitoring Configuration Guide
- 00-Preface
- 01-System maintenance and debugging configuration
- 02-NQA configuration
- 03-iNQA configuration
- 04-NTP configuration
- 05-PoE configuration
- 06-SNMP configuration
- 07-RMON configuration
- 08-Event MIB configuration
- 09-NETCONF configuration
- 10-SmartMC configuration
- 11-CWMP configuration
- 12-EAA configuration
- 13-Process monitoring and maintenance configuration
- 14-Sampler configuration
- 15-Mirroring configuration
- 16-NetStream configuration
- 17-IPv6 NetStream configuration
- 18-sFlow configuration
- 19-Performance management configuration
- 20-Flow log configuration
- 21-Information center configuration
- 22-Packet capture configuration
- 23-Cloud connection configuration
- 24-GOLD configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 23-Cloud connection configuration | 115.71 KB |
Cloud connection establishment
Restrictions: Hardware compatibility with cloud connection to Cloudnet (oasis.h3c.com)
Restrictions: Hardware compatibility with cloud connection to Cloudnet (oasiscloud.h3c.com)
Restrictions: Hardware compatibility with cloud connection to ADWAN controller
Unbinding the device from the cloud server
Display and maintenance commands for cloud connections
Cloud connection configuration examples
Example: Configuring a cloud connection
Configuring cloud connections
About cloud connections
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 to Cloudnet (oasis.h3c.com)
|
Hardware |
Cloud connection compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE |
Yes |
|
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR810-LMS-EA |
No |
|
MSR810-LME |
Yes |
|
MSR1004S-5G |
No |
|
MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-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 |
|
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-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, 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 |
|
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 to Cloudnet (oasiscloud.h3c.com)
|
Hardware |
Cloud connection compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE |
Yes |
|
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR810-LMS-EA, MSR810-LME |
Yes |
|
MSR1004S-5G |
Yes |
|
MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-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 |
|
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-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 , MSR2600-10-X1-WiNet |
No |
|
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 |
|
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 to ADWAN controller
|
Hardware |
Cloud connection compatibility |
|
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE |
Yes |
|
MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK |
No |
|
MSR810-LMS, MSR810-LUS |
No |
|
MSR810-LMS-EA, MSR810-LME |
No |
|
MSR1004S-5G |
No |
|
MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-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 |
|
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-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, MSR2600-10-X1-WiNet |
No |
|
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 |
|
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.
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. For more information about the option 253 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.
Restrictions and guidelines
You can specify one primary server by using the cloud-management server domain command and a maximum of eight 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 connects to one of the primary and backup servers according to the order in which they are stored. The server domain names are stored in alphabet order and port numbers are stored in descending order. 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. 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.
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.
Reduce the ping interval value if the network condition is poor or the NAT entry aging time is short. When you use the ADWAN server for cloud connections, you must set the password for establishing cloud connections to the ADWAN 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.
Procedure
1. Enter system view.
system-view
2. Specify the primary cloud server by its domain name.
cloud-management server domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ipv4-address ]
By default, no primary cloud server is specified.
3. (Optional.) Specify a backup cloud server by its domain name.
cloud-management backup-server domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ipv4-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 authentication to the cloud server.
cloud-management server port port-number
By default, TCP port number 19443 is used by the device to initiate authentication to the cloud server.
8. (Optional.) Set the password for establishing cloud connections to the ADWAN server.
cloud-management server password { cipher | simple } string
By default, no password is set for establishing cloud connections to the ADWAN 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.
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 oasis.h3c.com.
<Device> system-view
[Device] cloud-management server domain oasis.h3c.com
|
|
NOTE: The DNS service is provided by the ISP DNS server. |
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 : 139.217.27.153
Cloud server domain name : oasis.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
