Analysis: For out-of-band networking, there is no root device, but an out-of-band management switch is used to form an independent management network for all devices, servers, and iMaster NCE. In out-of-band networking, devices and servers to be brought online are no different from those in in-band networking. ▫ Out-of-band management switches: iMaster NCE does not accept out-of-band management switches for forwarding devices on out-of-band management networks, and you need to manually underlay the out-of-band management switches . Spine and leaf devices communicate with the DHCP server through out-of-band management switches, and DHCP Relay is not required in Layer 2 networking scenarios and configuration is required on out-of-band management switches in Layer 3 networking scenarios DHCP Relay 。 ▫ Management network port: that is, the interface corresponding to the management cable of the switch in the figure. Except for out-of-band management switches, all METH ports are used as management network ports. The out-of-band management network is divided into out-of-band Meth port management network and VPN isolated out-of-band management network, the difference between the two is that the configuration of the management network port is different, and the management network port in the out-of-band Meth port management network binds the device management IP, and The management port of the out-of-band management network in the VPN isolation management network is bound to the management VPN. ▫ Powered device: indicates the device at the previous level of the device to be brought online. In out-of-band networking, no online device exists when a Spine device goes online with ZTP, and when a server leaf device goes online with ZTP, the online device is Spine Equipment. •For in-band networking: iMaster NCE: ▫used to perform ZTP deployment tasks and manage them to be launched
Equipment. ▫ Root device: The root device is a device that has been managed by iMaster NCE to connect to the device to be brought online, and as the DHCP Relay of the device to be brought online, it applies for a temporary IP address from the DHCP server for the device to be brought online . In the in-band networking scenario, a root device exists, and the root device needs to be manually managed by the user. ▫Spine and Leaf: CE switches that perform ZTP on-line operations. Currently, Spine and Server Leaf are mainly supported to go live via ZTP. If you want to use ZTP to go online to Border Leaf, you need to use the device as a Server Leaf first, and then use iMaster NCE to set the device Border Leaf configures external gateways, etc. ▫ Pending Device: A CE switch device that is performing the ZTP onboarding task . ▫ Powered device: indicates the device at the previous level of the device to be brought online. In the in-band networking scenario, when a Spine device goes online with ZTP, the online device is the root device, and when a server leaf device goes online with ZTP, the online device is Spine devices. ▫DHCP Server: Used to assign temporary management IP addresses, default gateways, DNS server addresses, and SFTP to devices that perform ZTP Server address and other information. The DHCP server can use a third-party server (third-party server scenario) or the built-in DHCP function of iMaster NCE (built-in scenario). There is no dashed frame in the built-in scene. ▫SFTP server: used to save the Python scripts, version files, and license files that need to be loaded by the device during the ZTP process. The SFTP server can use a third-party server (third-party server scenario) or the built-in SFTP function of iMaster NCE (built-in scenario), which has a built-in part without a dotted box in the scene.
