Device Connect to Controller

switch switch dynamically obtain the controller ip through the dhcp server dynamically obtain the controller ip through the dhcp server all asterfusion devices can act as dhcp clients under the factory default configuration, they will actively send dhcp request to obtain the management ip address and the controller ip address to ensure that devices can obtain the controller ip through dhcp requests, the dhcp server must be capable of responding to the option 138 field the following is a configuration example for the isc dhcp server subnet 192 168 1 0 netmask 255 255 255 0 { range 192 168 0 100 192 168 0 200; option routers 192 168 0 1; option subnet mask 255 255 255 0; option capwap ac v4 "192 168 0 91"; \[description] 192 168 0 91 is the ip address of the controller in this case, configure the dhcp server and dhcp relay (if any) as needed after the switch is powered on and the physical connections are completed, you can see the switch go online on the \[devices] page of the controller connect to controller by command line connect to controller by command line if the dhcp server does not exist in the network, or the dhcp server cannot be configured with the controller address, the user can use the command ucentral client server \<a b c d> to configure the ip address of the controller on the switch so that the device can connect to the controller if the device uses out of band management and the management port belongs to vrf mgmt, users need to specify the vrf parameter when designating the management address, for example ucentral client server \<a b c d> vrf mgmt the following is a sample configuration for switch connect to the controller using the out of band management port： sonic# config sonic(config)# ucentral client enable sonic(config)# ucentral client server 192 168 0 91 vrf mgmt sonic(config)# interface mgmt 0 sonic(config if mgmt) ip address 192 168 0 20/24 192 168 0 91 sonic(config if mgmt) vrf mgmt use in band management to connect to the controller take the ethernet49 port as an example： sonic# config sonic(config)# ucentral client enable sonic(config)# ucentral client server 192 168 0 91 sonic(config)# interface ethernet 49 sonic(config if 49)# ip address 192 168 0 20/24 sonic(config if 49)# exit sonic(config)# ip route 0 0 0 0/0 192 168 0 91 after the configuration is completed, you can see the switch go online on the \[devices] page of the controller ap ap in the factory default configuration, the ap will actively send a dhcp request to request the management ip address and the controller ip address dhcp server deployment on server dhcp server deployment on server if there is a dhcp server in the network and the configuration has been completed according to section 5 1 1 since the ap is not directly connected to the dhcp server, it is necessary to use the script function or directly enter the switch background to configure through the command line configure the vlan broadcast domain on the switch device directly connected to the ap to broadcast the dhcp request of the ap to the dhcp server after entering the venue, click \[operation] \[script] to enter the script editing view click the \[+] in the upper right corner to create a new script, and select the script type as sonic cli script content configure interface ethernet 48 no router interface exit vlan 4010 exit port group ethernet 46 48 switchport access vlan 4010 exit interface vlan 4010 ip address dhcp alloc after completing the configuration, click save enter the device view, select the switch connected to the ap, and click the \[actions] \[script] button in the upper right corner select the script edited in the previous step, click \[next] \[start] , and send the script to the switch dhcp server deployment on asternos switch dhcp server deployment on asternos switch if there is no dhcp server in the network, you need to configure the switch to act as a dhcp server, assign management ip addresses to the aps, and inform them of the controller's ip address after entering the venue, click \[operation] \[script] to enter the script editing view click the \[+] in the upper right corner to create a new script, and select the script type as sonic cli script content configure interface ethernet 48 no router interface exit vlan 4020 exit port group ethernet 46 48 switchport access vlan 4020 exit interface vlan 4020 ip address 192 168 0 1/24 dhcp select server exit dhcp pool ap address pool 192 168 0 100 192 168 0 200 lease time 3000 6000 network 192 168 0 0 255 255 255 0 routers 192 168 0 1 capwap ac 192 168 0 91 note 192 168 0 91 is the ip address of the controller after completing the configuration, click save enter the device view, select the switch connected to the ap, and click the \[actions] \[script] button in the upper right corner select the script edited in the previous step, click \[start] , and send the script to the switch users can also directly select custom scripts on the script running page shown in the picture, fill in script content or upload script files and run them directly on this page