- Table of Contents
- 14-WLAN Configuration Guide (Fat AP)
- 01-Compatibility of hardware and AP functionality
- 02-Radio management configuration
- 03-Band navigation configuration
- 04-WLAN access configuration
- 05-WLAN security configuration
- 06-WLAN authentication configuration
- 07-WLAN QoS configuration
- 08-Cloud connection configuration
- 09-WLAN multicast optimization configuration
- 10-WLAN load balancing configuration
- Related Documents
|08-Cloud connection configuration||65.79 KB|
A cloud connection is a management tunnel established between a local device and the H3C Oasis server. It enables you to manage the local device from the H3C Oasis server without accessing the network where the device resides.
The term "AP" in this document refers to MSR routers that offer WLAN services as fat APs. For more information, see "Compatibility of hardware and AP functionality."
After a local device establishes a connection with the H3C Oasis server, service modules on the local device can establish multiple subconnections with the microservices on the H3C Oasis server. These subconnections are independent from each other and provide separate communication channels for different services. This mechanism avoids interference among different services.
As shown in Figure 1, the cloud connection between the device and the H3C Oasis server is established as follows:
1. The device sends an authentication request to the H3C Oasis server.
2. The H3C Oasis 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 H3C Oasis server. If the authentication fails, the H3C Oasis server sends an authentication failure packet to the device.
3. The device sends a registration request to the H3C Oasis server.
4. The H3C Oasis 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 H3C Oasis server.
6. The H3C Oasis 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 H3C Oasis server based on the service needs.
For a successful cloud connection establishment, add the serial number of the device to be managed to the H3C Oasis server. For more information about the H3C Oasis server settings, see the installation guide for the H3C Oasis server.
About configuring the local device
You can specify a domain name for the H3C Oasis server and log in to the server through the domain name on a remote PC to manage the local device.
If the local device does not receive a response from the H3C Oasis server within three keepalive intervals, 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 H3C Oasis server periodically.
Restrictions and guidelines
Reduce the ping interval value if the network condition is poor or the NAT entry aging time is short.
1. Enter system view.
2. Configure the domain name of the H3C Oasis server.
cloud-management server domain domain-name
By default, the domain name of the H3C Oasis server is not configured.
3. (Optional.) Set the keepalive interval.
cloud-management keepalive interval
By default, the keepalive interval is 180 seconds.
4. (Optional.) Set the ping interval.
cloud-management ping interval
By default, the ping interval is 60 seconds.
5. (Optional.) Specify the TCP port number used to establish cloud connections.
cloud-management server port port-number
By default, TCP port number 443 is used to establish cloud connections.
Execute display commands in any view.
Display cloud connection state information.
display cloud-management state
As shown in Figure 2, configure the AP to establish a cloud connection with the H3C Oasis server.
1. Configure IP addresses for interfaces as shown in Figure 2, and configure a routing protocol to ensure that the devices can reach each other. (Details not shown.)
2. Log in to the H3C Oasis server to add the serial number of the AP to the server. (Details not shown.)
3. Configure the domain name of the H3C Oasis server as oasis.h3c.com.
[AP] cloud-management server domain oasis.h3c.com
The DNS service is provided by the ISP DNS server.
Verifying the configuration
# Verify that the AP and the H3C Oasis server have established a cloud connection.
[AP] display cloud-management state
Cloud connection state : Established
Device state : Request_success
Cloud server address : 126.96.36.199
Cloud server domain name : oasis.h3c.com
Local 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