Contents

Cloud connection commands· 1

cloud-management keepalive· 1

cloud-management ping· 2

cloud-management server domain· 2

cloud-management server port 3

display cloud-management state· 4

 

Cloud connection commands

The term "AC" in this document refers to MSR routers that can function as ACs. For more information, see "Compatibility of hardware and AC functionality."

The following compatibility matrix shows the support of hardware platforms for cloud connections:

 

Hardware	Cloud connection compatibility
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA	Yes
MSR810-LMS, MSR810-LUS	No
MSR2600-6-X1, 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
MSR3610-I-DP, MSR3610-IE-DP	No
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	No

 

cloud-management keepalive

Use cloud-management keepalive to set the keepalive interval for the local device to send keepalive packets to the H3C Oasis server.

Use undo cloud-management keepalive to restore the default.

Syntax

cloud-management keepalive interval

undo cloud-management keepalive

Default

The keepalive interval is 180 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the keepalive interval in the range of 10 to 600 seconds.

Usage guidelines

If the 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.

Examples

# Set the keepalive interval to 360 seconds.

<Sysname> system-view

[Sysname] cloud-management keepalive 360

cloud-management ping

Use cloud-management ping to set the interval at which the local device sends ping packets to the H3C Oasis server.

Use undo cloud-management ping to restore the default.

Syntax

cloud-management ping interval

undo cloud-management ping

Default

The local device sends ping packets to the H3C Oasis server at intervals of 60 seconds.

Views

System view

Predefined user roles

network-admin

Parameters

interval: Specifies the interval at which the local device sends ping packets to the H3C Oasis server, in the range of 10 to 600 seconds.

Usage guidelines

After the connection to the H3C Oasis server is established, the local device sends ping packets to the server periodically to prevent NAT entry aging. Reduce the interval value if the network condition is poor or the NAT entry aging time is short.

The H3C Oasis server does not respond to ping packets.

Examples

# Configure the local device to send ping packets to the H3C Oasis server at intervals of 120 seconds.

<Sysname> system-view

[Sysname] cloud-management ping 120

cloud-management server domain

Use cloud-management server domain to configure the domain name of the H3C Oasis server.

Use undo cloud-management server domain to restore the default.

Syntax

cloud-management server domain domain-name

undo cloud-management server domain

Default

The domain name of the H3C Oasis server is not configured.

Views

System view

Predefined user roles

network-admin

Parameters

domain-name: Specifies the domain name of the H3C Oasis server, a case-sensitive string of 1 to 253 characters.

Usage guidelines

Before you configure the domain name of the H3C Oasis server, make sure a DNS server is configured to translate the domain name.

If you execute the command multiple times, the most recent configuration takes effect.

Examples

# Configure the domain name of the H3C Oasis server as lvzhouv3.h3c.com.

<Sysname> system-view

[Sysname] cloud-management server domain lvzhouv3.h3c.com

cloud-management server port

Use cloud-management server port to specify the TCP port number used to establish cloud connections.

Use undo cloud-management server port to restore the default.

Syntax

cloud-management server port port-number

undo cloud-management server port

Default

TCP port number 443 is used to establish cloud connections.

Views

System view

Predefined user roles

network-admin

Parameters

port-number: Specifies a TCP port number in the range of 1 to 65535.

Usage guidelines

After you change the port number, the device terminates the cloud connections that have been established (if any) and uses the new port number to establish cloud connections.

Examples

# Specify the TCP port number used to establish cloud connections as 80.

<Sysname> system-view

[Sysname] cloud-management server port 80

display cloud-management state

Use display cloud-management state to display cloud connection state information.

Syntax

display cloud-management state

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display cloud connection state information.

<Sysname> 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

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

Table 1 Command output

Field	Description
Cloud connection state	Cloud connection state: Unconnected, Request, and Established.
Device state	Local device state: ·     Idle—In idle state. ·     Connecting—Connecting to the H3C Oasis server. ·     Request_CAS_url—Sent a central authentication service (CAS) URL request. ·     Request_CAS_url_success—Requesting CAS URL succeeded. ·     Request_CAS_TGT—Sent a ticket granting ticket (TGT) request. ·     Request_CAS_TGT_success—Requesting TGT succeeded. ·     Request_CAS_ST—Sent a service ticket (ST) request. ·     Request_CAS_ST_success—Requesting ST succeeded. ·     Request_cloud_auth—Sent an authentication request. ·     Request_cloud_auth_success—Authentication succeeded. ·     Register—Sent a registration request. ·     Register_success—Registration succeeded. ·     Request—Sent a handshake request. ·     Request_success—Handshake succeeded.
Cloud server address	IP address of the H3C Oasis server.
Cloud server domain name	Domain name of the H3C Oasis server.
Local port	TCP port number used to establish cloud connections.
Connected at	Time when the cloud connection was established.
Duration	Duration since the establishment of the cloud connection.
Process state	Cloud connection processing state: ·     DNS not parsed. ·     DNS parsed. ·     Message not sent. ·     Message sent. ·     Message not received. ·     Message received.
Failure reason	Cloud connection failure reason: ·     DNS parse failed. ·     Socket connection failed. ·     SSL creation failed. ·     Sending CAS url request failed. ·     Sending CAS TGT failed. ·     Sending CAS ST failed. ·     Sending cloud auth failed. ·     Sending register failed. ·     Processing CAS url response failed. ·     Processing CAS TGT response failed. ·     Processing CAS ST response failed. ·     Processing cloud auth response failed. ·     Processing register response failed. ·     Sending handshake request failed. ·     Processing handshake failed. ·     Sending websocket request failed. ·     Processing websocket packet failed.
Last down reason	Reason for the most recent cloud connection interruption: ·     Device or process rebooted. ·     Socket connection error. ·     Configuration changed. ·     Received websocket close packet from cloud. ·     Keepalive expired. ·     Packet processing failed. ·     Main connection went down. ·     Cloud reset connection. ·     Memory reached threshold.
Last down at	Time when the cloud connection went down most recently.
Last report failure reason	Reason for the most recent cloud connection packet sending failure: ·     Tunnel is being deleted. ·     Tunnel socket is invalid. ·     Failed to convert string to json. ·     Failed to convert json to string. ·     Failed to create message node. ·     Tunnel is not ready. ·     Failed to create packet buffer. ·     SSL sending failure. If the reason is SSL sending failure, one of the following detailed reason will be displayed: ·     ssl error none. ·     ssl error ssl. ·     ssl error read. ·     ssl error write. ·     ssl error x509 lookup. ·     ssl error syscall. ·     ssl error zero return. ·     ssl error connect. ·     ssl error accept.
Last report failure at	Time when the most recent cloud connection packet sending failure occurred.
Dropped packets after reaching buffer limit	Number of packets that are dropped because the CMTNL buffer limit is reached.
Total dropped packets	Total number of dropped packets.
Last report incomplete reason	Reason for the most recent unfinished packet sending: ·     Interrupted system call. ·     Socket buffer is full.
Last report incomplete at	Time when the most recent unfinished packet sending occurred.
Buffer full count	Number of times that the buffer becomes full.