Page 2
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.
Page 3
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.
Page 4
Convention Description Multi-level menus are separated by angle brackets. For example, File > Create > > Folder. Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software.
Page 5
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.
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 ·········································································································...
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.
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.
Task Command display cloud-management state Display cloud connection state information. 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.
Page 11
2, and configure a routing protocol to make sure the devices can reach each other. (Details not shown.) Log in to the H3C Oasis server to add the serial number of the AC to the server. (Details not shown.) Configure the domain name of the H3C Oasis server as oasis.h3c.com.