No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CLI-based Configuration Guide - Network Management and Monitoring

AR100, AR120, AR150, AR160, AR200, AR1200, AR2200, AR3200, and AR3600 V200R009

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Understanding AR and Controller Interconnection Configuration

Understanding AR and Controller Interconnection Configuration

Figure 15-1 shows the connections between the devices and controller.

Figure 15-1  Connections between devices and controller
  1. The devices obtain controller information, including the controller's IP address and domain name and port number matching the controller's IP address and domain name.
    • Factory settings: The controller information is contained in the configuration file before delivery.
    • USB-based deployment: The controller information is obtained during USB-based deployment.
    • DHCP: After a device connects to the network, the device functions as a DHCP client to send a request packet to the DHCP server. The DHCP server (which can be an egress gateway or an independent DHCP server) sends a DHCP packet to the device. The Option 148 field in the packet sent by the DHCP server contains the controller's information.
    • Command line: The controller information is configured on the device using commands.
  2. The controller registers devices.
    1. After obtaining the controller's information, the device registers with the controller.
    2. A NETCONF channel is set up: The device functions as a client to set up a TCP connection with the controller. Based on the TCP connection, the device functions as an SSH server to set up an SSH tunnel with the controller. During tunnel setup, the device and controller use bidirectional CA certificate for authentication. Based on the SSH tunnel, the device as the NETCONF server and the controller as the NETCONF client exchange control packets.
    3. The controller queries and verifies the ESN of the device. After the verification is successful, the controller notifies the device of successful registration.
  3. The controller uniformly manages devices.

    After a transmission channel is set up using NETCONF, the controller can manage the devices, for example, issuing configurations to implement batch service configuration.

Updated: 2019-05-17

Document ID: EDOC1000174072

Views: 108774

Downloads: 346

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next