H3C WX1804H User manual

H3C Access Controllers

Oasis Connection Configuration Guide

New H3C Technologies Co., Ltd.

http://www.h3c.com

Document version: 6W104-20210413

Product version: R5426P02

No part of this manual may be reproduced or transmitted in any form or by any means without prior written

consent of New H3C Technologies Co., Ltd.

Trademarks

Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this

document are the property of their respective owners.

Notice

The information in this document is subject to change without notice. All contents in this document, including

statements, information, and recommendations, are believed to be accurate, but they are presented without

warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions

contained herein.

Preface

The access controllers documentation set describes the software features for the access controllers

and guide you through the software configuration procedures. These guides also provide

configuration examples to help you apply software features to different network scenarios.

The Oasis Connection Configuration Guide describes Oasis connection configurations.

This preface includes the following topics about the documentation:

•

Audience.

•

Conventions.

•

Documentation feedback.

Audience

This documentation is intended for:

•

Network planners.

•

Field technical support and servicing engineers.

•

Network administrators working with the H3C access controllers.

Conventions

The following information describes the conventions used in the documentation.

Command conventions

Convention

Description

Boldface

Bold

text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.

{ x | y | ... }

Braces enclose a set of required syntax choices separated by vertical bars, from which

you select one.

[ x | y | ... ]

Square brackets enclose a set of optional syntax choices separated by vertical bars,

from which you select one or none.

{ x | y | ... } *

Asterisk marked braces enclose a set of required syntax choices separated by vertical

bars, from which you select a minimum of one.

[ x | y | ... ] *

Asterisk marked square brackets enclose optional syntaxchoices separated by vertical

bars, from which you select one choice, multiple choices, or none.

&<1-n> The argument or keyword and argument combination before the ampersand (&) sign

can be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention

Description

Boldface Window names, button names, field names, and menu items are in Boldface. For

example, the

New User

window opens; click

Convention

Description

> Multi-level menus are separated by angle brackets. For example, File > Create >

Folder.

Symbols

Convention

Description

WARNING!

An alert that calls attention to important information that if not understood or followed

can result in personal injury.

CAUTION:

An alert that calls attention to important information that if not understood or followed

can result in data loss, data corruption, or damage to hardware or software.

IMPORTANT:

An alert that calls attention to essential information.

NOTE:

An alert that contains additional or supplementary information.

TIP:

An alert that provides helpful information.

Network topology icons

Convention

Description

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that

supports Layer 2 forwarding and other Layer 2 features.

Represents an access controller, a unified wired-WLAN module, or the access

controller engine on a unified wired-WLAN switch.

Represents an access point.

Represents a wireless terminator unit.

Represents a wireless terminator.

Represents a mesh access point.

Represents omnidirectional signals.

Represents directional signals.

Represents a security product, such as a firewall, UTM, multiservice security

gateway, or load balancing device.

Represents a security module, such as a firewall, load balancing, NetStream, SSL

VPN, IPS, or ACG module.

Examples provided in this document

Examples in this document might use devices that differ from your device in hardware model,

configuration, or software version. It is normal that the port numbers, sample output, screenshots,

and other information in the examples differ from what you have on your device.

Documentation feedback

You can e-mail your comments about product documentation to info@h3c.com.

We appreciate your comments.

Contents

Configuring cloud connections·······································································1

About cloud connections····································································································································1

Multiple subconnections·····························································································································1

Cloud connection establishment················································································································1

Restrictions: Hardware compatibility with cloud connections·············································································2

Configuring the H3C Oasis server ·····················································································································3

Configuring the local device·······························································································································3

Unbinding the device from the Oasis server······································································································4

Display and maintenance commands for cloud connections·············································································4

Cloud connection configuration examples ·········································································································4

Example: Configuring a cloud connection··································································································4

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 EWP-WX5510E Yes

Cloud connection

Registration request

Registration response

Device

Handshake request

Handshake response

H3C Oasis server

Authentication request

Authentication success packet

WX5540E EWP-WX5540E

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

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.

This manual suits for next models

Table of contents

Popular IP Access Controllers manuals by other brands

ZKTeco

ZKTeco SpeedFace-V5L user manual

Jantar

Jantar REX A-1-9 quick start guide

2N Access Unit Configuration manual

Kedacom

Kedacom KSCA120 Series quick start guide

G4S

G4S S870-EX Installation and user instructions

PRASTEL

PRASTEL M2000PE manual

Allegion

Allegion interflex IF-281 Cylinder manual

TECOM

TECOM TS1067E manual

Fermax

Fermax Memokey 100C Installer manual

Fermax

Fermax CITYLINE MEMOKEY User& installer's manual

Software House

Software House iSTAR Pro 2U RM Quick start installation guide

AKCP

AKCP SP+ manual

Bpt

Bpt HNA/102 installation instructions

Civintec

Civintec CV9601T-T-1F installation manual

BioMax

BioMax N-X90W user manual

ZKTeco

ZKTeco OP-200 quick start guide

FingerTec

FingerTec s-Kadex user guide

C Prox Ltd

C Prox Ltd DPN-2 user manual