Basic Network

except for the open cloud connect scenario, the other three scenarios all require basic network configuration click \[basic network] to enter the basic network configuration interface to configure the basic network that carries the service network, including the routing protocols between leaf and spine, and between spine and up link devices besides information such as ip addresses that must be specified by the user, the controller will dynamically generate basic configurations based on the network topology that do not require the user's attention in band management in band management large/mid scale campus large/mid scale campus aggregation aggregation in large/mid scale campus scenarios, the spine and leaf devices are layer 3 devices in band management can use the loopback0 address while the aggregation device is a layer 2 device for which you need to configure the management vlan and ip controller can assign an in band management address to each aggregation device based on the address segments that are entered by the user server network server network leaf devices in large/mid scale campus server areas also need to be configured with in band management networks (if out of band management is selected, there is no need to configure the management address range) configure the peerlink interface vlan and peerlink ip traditional l2 network traditional l2 network in the traditional l2 network scenario, the in band management method for leaf devices is as follows create a vlan interface as the in band management interface to connect to the controller on the current page, administrator can specify a vlan id as the in band management vlan, configure the address segment of the management ip and the gateway address for in band management (this gateway address will be configured on the spine device), and select the member interfaces of the vlan and the mode (trunk/access) when joining the vlan the controller will allocate a management ip address from the specified address segment for each leaf switch and present the allocation results in the table below egress route egress route configuring spine device up link interface information configure the ip address of the spine device uplink interface and static routing information on the spine device if the spine and the core device do not use static route but use dynamic route, user can click \[advance] button to configure it note in traditional l2 network scenarios, spine only supports connecting to external networks by configuring static routes fast convergence enable minimize the convergence time during network topology changes in order to protect the high availability of mission critical services bgp enable enable the bgp function of spine device and configure the as number and ip address information of the up link device, so that spine can establish bgp neighbor relationship with the up link device route aggregation enable when the spine devices enable the bgp function, the routing information of the terminal will be synchronized with the up link device in form of aggregated routes ha when enabled, the two spine devices will provide a cross device lag interface to the up link device through the mc lag function device management device management configure device management related information timezone configure the system time zone ntp configure ntp server snmp configure snmp community syslog configure syslog server ip address tacacs+ configure tacacs server ip address device acl configure acl rules restricting ssh, snmp, telnet connections to device