14-Oasis Connection Configuration Guide

HomeSupportResource CenterConfigure & DeployConfiguration GuidesH3C Access Controllers Configuration Guides(R5426P02)-6W10414-Oasis Connection Configuration Guide
01-Cloud connection configuration
Title Size Download
01-Cloud connection configuration 81.43 KB

Configuring cloud connections

About cloud connections

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.

Multiple subconnections

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.

Cloud connection establishment

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.

 

Figure 1 Establishing a cloud connection

 

Restrictions: Hardware compatibility with cloud connections

Hardware series

Model

Product code

Cloud connection compatibility

WX1800H series

WX1804H

EWP-WX1804H-PWR-CN

Yes

WX2500H series

WX2508H-PWR-LTE

WX2510H

WX2510H-F

WX2540H

WX2540H-F

WX2560H

EWP-WX2508H-PWR-LTE

EWP-WX2510H-PWR

EWP-WX2510H-F-PWR

EWP-WX2540H

EWP-WX2540H-F

EWP-WX2560H

Yes

WX3000H series

WX3010H

WX3010H-X

WX3010H-L

WX3024H

WX3024H-L

WX3024H-F

EWP-WX3010H

EWP-WX3010H-X-PWR

EWP-WX3010H-L-PWR

EWP-WX3024H

EWP-WX3024H-L-PWR

EWP-WX3024H-F

Yes

WX3500H series

WX3508H

WX3510H

WX3520H

WX3520H-F

WX3540H

EWP-WX3508H

EWP-WX3510H

EWP-WX3520H

EWP-WX3520H-F

EWP-WX3540H

Yes

WX5500E series

WX5510E

WX5540E

EWP-WX5510E

EWP-WX5540E

Yes

WX5500H series

WX5540H

WX5560H

WX5580H

EWP-WX5540H

EWP-WX5560H

EWP-WX5580H

Yes

Access controller modules

LSUM1WCME0

EWPXM1WCME0

LSQM1WCMX20

LSUM1WCMX20RT

LSQM1WCMX40

LSUM1WCMX40RT

EWPXM2WCMD0F

EWPXM1MAC0F

LSUM1WCME0

EWPXM1WCME0

LSQM1WCMX20

LSUM1WCMX20RT

LSQM1WCMX40

LSUM1WCMX40RT

EWPXM2WCMD0F

EWPXM1MAC0F

Yes

Hardware series

Model

Product code

Cloud connection compatibility

WX1800H series

WX1804H

WX1810H

WX1820H

WX1840H

EWP-WX1804H-PWR

EWP-WX1810H-PWR

EWP-WX1820H

EWP-WX1840H-GL

No

WX3800H series

WX3820H

WX3840H

EWP-WX3820H-GL

EWP-WX3840H-GL

No

WX5800H series

WX5860H

EWP-WX5860H-GL

No

Configuring the H3C Oasis server

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.

Configuring the local device

About this task

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.

Procedure

1.     Enter system view.

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, the TCP port number used to establish cloud connections is 19443.

Unbinding the device from the Oasis server

About this task

A device can be registered on the Oasis 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 Oasis server.

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

3.     Register the device on the Oasis server.

Procedure

1.     Enter system view.

system-view

2.     Send the verification code for device unbinding to the Oasis 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 AC to establish a cloud connection with the H3C Oasis 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 H3C Oasis server to add the serial number of the AC to the server. (Details not shown.)

3.     Configure the domain name of the H3C Oasis server as oasis.h3c.com.

<AC> system-view

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

 

 

NOTE:

The DNS service is provided by the ISP DNS server.

 

Verifying the configuration

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

[AC] 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 port                           : 19443

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