11-Network Management and Monitoring Command Reference

HomeSupportReference GuidesCommand ReferencesH3C S6520X-HI[EI][SI] & S6520-SI & S5560X-HI & S5000-EI & MS4600 Switch Series Command References-R63xx-6W10111-Network Management and Monitoring Command Reference
19-Cloud connection commands
Title Size Download
19-Cloud connection commands 58.16 KB

Cloud connection commands

cloud-management keepalive

Use cloud-management keepalive to set the keepalive interval for the local device to send keepalive packets to the H3C cloud 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 180 to 600 seconds.

Usage guidelines

If the device does not receive a response from the H3C cloud 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 server domain

Use cloud-management server domain to configure the domain name of the H3C cloud 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 cloud server is not configured.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

Before you configure the domain name of the H3C cloud server, make sure a DNS server has been 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 cloud server as abc.com.

<Sysname> system-view

[Sysname] cloud-management server domain abc.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 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

cloud-management unbinding-code

Use cloud-management unbinding-code to send the verification code for device unbinding to the Oasis server.

Syntax

cloud-management unbinding-code code

Views

System view

Predefined user roles

network-admin

Parameters

code: Specifies the verification code obtained from the Oasis server. The verification code is a case-sensitive string of 16 characters.

Usage guidelines

Only Release 6320 and later versions support this feature.

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 this command on the device to send the verification code to the Oasis server.

3.     Register the device on the Oasis server.

Examples

# Send the verification code for device unbinding to the Oasis server.

<Sysname> system-view

[Sysname] cloud-management unbinding-code A6B9C3C2D5A8Z1S7

Related commands

cloud-management server domain

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     : 10.1.1.1

Cloud server domain name : abc.com

Cloud server port        : 443

Connected at             : Wed Jan  27 14:18:40 2016

Duration                 : 00d 00h 02m 01s

Process state            : Message received

Failure reason           : N/A

Table1-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 cloud 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 cloud server.

Cloud server domain name

Domain name of the H3C cloud server.

Cloud server 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 request failed.

·     Sending registration request failed.

·     Processing CAS URL response failed.

·     Processing CAS TGT response failed.

·     Processing CAS ST response failed.

·     Processing cloud auth response failed.

·     Processing registration response failed.

·     Sending handshake request failed.

·     Processing handshake failed.

·     Sending websocket request failed.

·     Processing websocket packet failed.

 

reset cloud-management tunnel

Use reset cloud-management tunnel to re-establish the cloud connection to the H3C cloud server.

Syntax

reset cloud-management tunnel

Views

User view

Predefined user roles

network-admin

Examples

# Re-establish the cloud connection to the H3C cloud server.

<Sysname> reset cloud-management tunnel

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网