ZTP+ Phases of Operation

Connect

The Connect phase is the first phase of ZTP+ during which the switch connects to the Extreme Management Center or ExtremeCloud IQ - Site Engine server on the network. The Extreme Management Center or ExtremeCloud IQ - Site Engine server is discovered by resolving the DNS name extremecontrol.<domain-name>.

If the attempt is successful, the Extreme Management Center or ExtremeCloud IQ - Site Engine server responds with an Accept message. When connectivity is established, the switch communicates with the Extreme Management Center or ExtremeCloud IQ - Site Engine server securely and transmits information, such as its serial number, model number. The switch then progresses to the next phase of ZTP+.

Upgrade

After a successful connect to the Extreme Management Center or ExtremeCloud IQ - Site Engine server, the next phase of ZTP+ is the Upgrade phase. This phase verifies that the switch is running the image file version that is currently selected as the reference version on the Extreme Management Center or ExtremeCloud IQ - Site Engine server.

Image file validation is initiated by the switch. After a successful connect, the switch sends an image file upgrade request to the Extreme Management Center or ExtremeCloud IQ - Site Engine server with details on the current image file version. If the image file versions on the switch and the Extreme Management Center or ExtremeCloud IQ - Site Engine server match, no upgrade is initiated, and the switch moves to the next phase of ZTP+. If the Extreme Management Center or ExtremeCloud IQ - Site Engine server detects a different image file version, ZTP+ initiates the .tgz image file download from a specified URL location.

After a successful image upgrade, the switch reboots and reconnects to the Extreme Management Center or ExtremeCloud IQ - Site Engine server. If there are errors in the image upgrade process, an event is added to the server log. The switch then retries the image upgrade.

Configuration

The next phase after the image upgrade is ZTP+ Configuration phase. During this phase, the switch queries the Extreme Management Center or ExtremeCloud IQ - Site Engine server for configuration updates, and initiates auto-provisioning by transmitting information, such as the image version, model name, and serial number. The switch then attempts to apply the configuration that is pushed from the Extreme Management Center or ExtremeCloud IQ - Site Engine server.

If the switch can still communicate with the Extreme Management Center or ExtremeCloud IQ - Site Engine server after the configuration is applied, the new configuration is automatically saved on the switch. The switch can be managed through the Extreme Management Center or ExtremeCloud IQ - Site Engine using Simple Network Management Protocol (SNMP). However, if the configuration that is pushed from the Extreme Management Center or ExtremeCloud IQ - Site Engine server breaks switch connectivity to the Extreme Management Center or ExtremeCloud IQ - Site Engine server, the switch reboots without saving the configuration. After the switch reboots, the ZTP+ onboarding restarts.

Any configurations pushed from the Extreme Management Center or ExtremeCloud IQ - Site Engine server to devices using the initial ZTP+ configuration push are not displayed in the show log file detail command output. The logs associated with the Cloud connector are logged internally to state_machine.txt and ztp_plus.txt files located in /intflash/cc/cc_logs/.

Extreme Management Center or ExtremeCloud IQ - Site Engine uses ZTP+ to configure the following items:

• Link Layer Discovery Protocol (LLDP) neighbor discovery

  

  Note

  Based on the LLDP discovery, port templates can be used on the Extreme Management Center or ExtremeCloud IQ - Site Engine server. Enabling or disabling LLDP is not supported.

• Login

• Network Time Protocol (NTP)

• Ports configuration

• SNMP

• VLANs

  

  Note

  ZTP+ cannot manage VLAN port membership. With ZTP+, new VLANs are created with no ports. Ports cannot be removed from the onboarding VLAN. Ports cannot be added to another VLAN. VLAN port membership is managed through Auto-sense functionality or through manual configuration after initial onboarding is complete.