17-Network Management and Monitoring Command Reference

HomeSupportResource CenterReference GuidesCommand ReferencesH3C MSR810[830][2600][3600] Routers Command Reference(V7)-R6728-6W10017-Network Management and Monitoring Command Reference
23-Cloud connection commands
Title Size Download
23-Cloud connection commands 106.75 KB

Cloud connection commands

The following compatibility matrixes show the support of hardware platforms for cloud connections to Cloudnet (oasis.h3c.com):

 

Hardware

Cloud connection compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE

Yes

MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA

No

MSR810-LME

Yes

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

Yes

MSR 2630

Yes

MSR3600-28, MSR3600-51

No

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, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-IE-ES

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

Yes

MSR 3620-DP

Yes

MSR 3610, MSR 3620, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

Hardware

Cloud connection compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

Yes

MSR830-4LM-WiNet

Yes

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

Yes

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

Yes

MSR2600-6-WiNet, MSR2600-10-X1-WiNet

Yes

MSR2630-WiNet

Yes

MSR3600-28-WiNet

Yes

MSR3610-X1-WiNet

Yes

MSR3610-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

Yes

MSR3620-10-WiNet

No

Hardware

Cloud connection compatibility

MSR2630-XS

Yes

MSR3600-28-XS

Yes

MSR3610-XS

Yes

MSR3620-XS

Yes

MSR3610-I-XS

Yes

MSR3610-IE-XS

Yes

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

Yes

Hardware

Cloud connection compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

The following compatibility matrixes show the support of hardware platforms for cloud connections to Cloudnet (oasiscloud.h3c.com):

 

Hardware

Cloud connection compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE

Yes

MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

Yes

MSR1004S-5G

Yes

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-X1

Yes

MSR 2630

Yes

MSR3600-28, MSR3600-51

No

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, MSR3610-IE-EAD, MSR-EAD-AK770, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-IE-ES

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

Yes

MSR 3620-DP

Yes

MSR 3610, MSR 3620, MSR 3640, MSR 3660

No

MSR3610-G, MSR3620-G

No

MSR3640-X1-HI

Yes

Hardware

Cloud connection compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet , MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

Hardware

Cloud connection compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

Yes

Hardware

Cloud connection compatibility

MSR810-LM-GL

Yes

MSR810-W-LM-GL

Yes

MSR830-6EI-GL

Yes

MSR830-10EI-GL

Yes

MSR830-6HI-GL

Yes

MSR830-10HI-GL

Yes

MSR1004S-5G-GL

Yes

MSR2600-6-X1-GL

Yes

MSR3600-28-SI-GL

No

The following compatibility matrixes show the support of hardware platforms for cloud connections to the ADWAN controller:

 

Hardware

Cloud connection compatibility

MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE

Yes

MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LM-CNDE-SJK, MSR810-CNDE-SJK

No

MSR810-LMS, MSR810-LUS

No

MSR810-LMS-EA, MSR810-LME

No

MSR1004S-5G

No

MSR2600-6-X1, MSR2600-10-X1, MSR2600-15-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, MSR3610-I-IG, MSR3610-IE-IG

Yes

MSR3610-IE-ES, MSR3610-IE-EAD, MSR-EAD-AK770

No

MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC, MSR3620-X1, MSR3640-X1

Yes

MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660

Yes

MSR3610-G, MSR3620-G

Yes

MSR3640-X1-HI

Yes

Hardware

Cloud connection compatibility

MSR810-W-WiNet, MSR810-LM-WiNet

No

MSR830-4LM-WiNet

No

MSR830-5BEI-WiNet, MSR830-6EI-WiNet, MSR830-10BEI-WiNet

No

MSR830-6BHI-WiNet, MSR830-10BHI-WiNet

No

MSR2600-6-WiNet , MSR2600-10-X1-WiNet

No

MSR2630-WiNet

No

MSR3600-28-WiNet

No

MSR3610-X1-WiNet

No

MSR3610-WiNet, MSR3620-10-WiNet, MSR3620-DP-WiNet, MSR3620-WiNet, MSR3660-WiNet

No

Hardware

Cloud connection compatibility

MSR2630-XS

No

MSR3600-28-XS

No

MSR3610-XS

No

MSR3620-XS

No

MSR3610-I-XS

No

MSR3610-IE-XS

No

MSR3620-X1-XS

Yes

MSR3640-XS

Yes

MSR3660-XS

Yes

Hardware

Cloud connection compatibility

MSR810-LM-GL

No

MSR810-W-LM-GL

No

MSR830-6EI-GL

No

MSR830-10EI-GL

No

MSR830-6HI-GL

No

MSR830-10HI-GL

No

MSR1004S-5G-GL

No

MSR2600-6-X1-GL

No

MSR3600-28-SI-GL

No

cloud-management backup-server domain

Use cloud-management backup-server domain to specify a backup cloud server by its domain name.

Use undo cloud-management backup-server domain to remove one or all backup cloud servers.

Syntax

cloud-management backup-server domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ipv4-address ]

undo cloud-management backup-server domain [ domain-name [ port port-number ] ]

Default

No backup cloud server is specified.

Views

System view

Predefined user roles

network-admin

Parameters

domain-name: Specifies a backup cloud server by its domain name, a case-insensitive string of 1 to 253 characters. If you do not specify this parameter in the undo cloud-management backup-server domain command, all backup cloud servers will be deleted.

port port-number: Specifies the TCP port number used by the device to initiate authentication to the cloud server. The value range for the port-number argument is 1 to 65535. If you do not specify this option, the port number specified by the cloud-management server port command is used.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the backup cloud server is on the public network.

source-ip ipv4-address: Specifies the source IPv4 address for the device that connects to the backup cloud server. It must be the same as the IPv4 address configured on the device. If you do not specify this option, the device uses the primary IPv4 address of the egress interface to connect to the backup cloud server.

Usage guidelines

Before configuring this command, make sure a DNS server is configured to translate domain names.

You can specify a maximum of eight backup servers by repeating the cloud-management backup-server domain command. Each server domain name supports a maximum of three port numbers. If you execute this command multiple times to configure a backup cloud server with the same domain name and port number, the most recent configuration takes effect.

You can specify one primary server by using the cloud-management server domain command and a maximum of eight backup servers by repeating the cloud-management backup-server domain command.

When establishing a cloud connection, the device connects to one of the primary and backup servers according to the order in which they are stored. The server domain names are stored in alphabet order and port numbers are stored in descending order. When the connected server fails, the device switches to another server and does not switch back to the original server even if the original server recovers.

To view the connected server, execute the display cloud-management state command.

If multiple servers exist in the intranet and the NAT device has only one public IP address, you can execute this command to specify different port numbers for one server domain name.

For a device to establish a cloud connection to the cloud server, perform either of the following tasks:

·     Specify the domain name of the cloud server on the device through CLI.

·     Configure VLAN interface 1 of the device as a DHCP client and the cloud server as the DHCP server. The device obtains the IP address of the DHCP server and parses the option 253 field in the DHCP packets to obtain the domain name of the cloud server. For more information about the option 253 field, see DHCP configuration in Layer3 IP Services Configuration Guide.

The domain name obtained through DHCP has a higher priority than the domain name configured manually.

If a device obtains the domain name of the cloud server through DHCP after establishing a cloud connection to the cloud server with the manually configured domain name, the device performs the following tasks:

·     If the automatically obtained and manually configured domain names are identical, the device retains the cloud connection.

·     If the automatically obtained and manually configured domain names are different, the device tears down the cloud connection and then establishes a cloud connection to the cloud server with the automatically obtained domain name.

Examples

# Specify the server with domain name 123.com as a backup cloud server.

<Sysname> system-view

[Sysname] cloud-management backup-server domain 123.com

Related commands

display cloud-management state

cloud-management keepalive

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

Usage guidelines

After establishing the cloud connection, the local device sends keepalive packets to the cloud server at the interval specified by the cloud-management keepalive interval command. If the device does not receive a response from the cloud server after the number of keepalive packets sent reached the limit specified by the cloud-management keepalive count count command, 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

Related commands

cloud-management keepalive count

cloud-management keepalive count

Use cloud-management keepalive count to specify the maximum number of consecutive keepalive packets that the local device can send to the cloud server.

Use undo cloud-management keepalive count to restore the default.

Syntax

cloud-management keepalive count count

undo cloud-management keepalive count

Default

A device can send three consecutive keepalive packets to the cloud server.

Views

System view

Predefined user roles

network-admin

Parameters

count: Specifies the maximum number of consecutive keepalive packets that the local device can send to the cloud server. The value range for this argument is 2 to 100.

Usage guidelines

After establishing the cloud connection, the local device sends keepalive packets to the cloud server at the interval specified by the cloud-management keepalive interval command. If the device does not receive a response from the cloud server after the number of keepalive packets sent reached the limit specified by the cloud-management keepalive count count command, the device sends a registration request to re-establish the cloud connection.

Examples

# Set the maximum number of consecutive keepalive packets that the local device can send to the cloud server to five.

<Sysname> system-view

[Sysname] cloud-management keepalive count 5

Related commands

cloud-management keepalive

cloud-management ping

Use cloud-management ping to set the interval at which the local device sends ping packets to the cloud 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 cloud 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 cloud server, in the range of 10 to 600 seconds.

Usage guidelines

After the connection to the cloud 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 cloud server does not respond to ping packets.

Examples

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

<Sysname> system-view

[Sysname] cloud-management ping 120

cloud-management server domain

Use cloud-management server domain to specify the primary cloud server by its domain name.

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

Syntax

cloud-management server domain domain-name [ port port-number ] [ vpn-instance vpn-instance-name ] [ source-ip ipv4-address ]

undo cloud-management server domain

Default

No primary cloud server is specified.

Views

System view

Predefined user roles

network-admin

Parameters

domain-name: Specifies the primary cloud server by its domain name, a case-insensitive string of 1 to 253 characters.

port port-number: Specifies the TCP port number used by the device to initiate authentication to the cloud server. The value range for the port-number argument is 1 to 65535. If you do not specify this option, the port number specified by the cloud-management server port command is used.

vpn-instance vpn-instance-name: Specifies an MPLS L3VPN instance by its name, a case-sensitive string of 1 to 31 characters. If you do not specify this option, the primary cloud server is on the public network.

source-ip ipv4-address: Specifies the source IPv4 address for the device that connects to the primary cloud server. It must be the same as the IPv4 address configured on the device. If you do not specify this option, the device uses the primary IPv4 address of the egress interface to connect to the primary cloud server.

Usage guidelines

Before configuring this command, make sure a DNS server is configured to translate domain names.

You can specify one primary server by using the cloud-management server domain command. If you execute the command multiple times, the most recent configuration takes effect.

If multiple servers exist in the intranet and the NAT device has only one public IP address, you can execute this command to specify different port numbers for one server domain name.

For a device to establish a cloud connection to the cloud server, perform either of the following tasks:

·     Specify the domain name of the cloud server on the device through CLI.

·     Configure VLAN interface 1 of the device as a DHCP client and the cloud server as the DHCP server. The device obtains the IP address of the DHCP server and parses the option 253 field in the DHCP packets to obtain the domain name of the cloud server. For more information about the option 253 field, see DHCP configuration in Layer3 IP Services Configuration Guide.

The domain name obtained through DHCP has a higher priority than the domain name configured manually.

If a device obtains the domain name of the cloud server through DHCP after establishing a cloud connection to the cloud server with the manually configured domain name, the device performs the following tasks:

·     If the automatically obtained and manually configured domain names are identical, the device retains the cloud connection.

·     If the automatically obtained and manually configured domain names are different, the device tears down the cloud connection and then establishes a cloud connection to the cloud server with the automatically obtained domain name.

Examples

# Specify the server with domain name lvzhouv3.h3c.com as the primary cloud server.

<Sysname> system-view

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

Related commands

display cloud-management state

cloud-management server password

Use cloud-management server password to set the password for establishing cloud connections to the ADWAN server.

Use cloud-management server password to restore the default.

Syntax

cloud-management server password { cipher | simple } string

undo cloud-management server password

Default

No password is set for establishing cloud connections to the ADWAN server.

Views

System view

Predefined user roles

network-admin

Parameters

cipher: Specifies the password in encrypted form.

simple: Specifies the password in plaintext form. For security purposes, the password specified in plaintext form will be stored in encrypted form.

string: Specifies the password. The plaintext form is a case-sensitive string of 1 to 63 characters. The encrypted form is a case-sensitive string of 1 to 117 characters.

Usage guidelines

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

Examples

# Set the password for establishing cloud connections to the ADWAN server to 12345678 in plaintext format.

<Sysname> system-view

[Sysname] cloud-management server password simple 12345678

cloud-management server port

Use cloud-management server port to specify the TCP port number used by the device to initiate authentication to the cloud server.

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 19443 is used by the device to initiate authentication to the cloud server.

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.

If you do not specify a TCP port number for authentication when specifying a cloud server by its domain name, the device uses the port number specified by this command.

Examples

# Specify the TCP port number used by the device to initiate authentication to the cloud server as 80.

<Sysname> system-view

[Sysname] cloud-management server port 80

Related commands

display cloud-management state

cloud-management unbinding-code

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

Syntax

cloud-management unbinding-code code

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

2.     Execute this command on the device to send the verification code to the cloud server.

3.     Register the device on the cloud server.

Examples

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

[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                        : 139.217.27.153

Cloud server domain name                    : oasis.h3c.com

Cloud connection mode                       : Https

Cloud server authentication port            : 19443

Cloud server connection 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 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 cloud server.

Cloud server domain name

Domain name of the cloud server.

Cloud server authentication port

TCP port number used by the device to initiate authentication to the cloud server.

Cloud server connection 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.