Understanding AR and Controller Interconnection Configuration
Figure 15-1 shows the connections between the devices and controller.
- 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.
- The controller registers devices.
- After obtaining the controller's information, the device registers with the controller.
- 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.
- The controller queries and verifies the ESN of the device. After the verification is successful, the controller notifies the device of successful registration.
- 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.