You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Download the data required for all the configuration tasks before processing the first task.
Solution 1 will not be sufficient if there is a configuration task that requires connectivity, therefore we can add to connectivity check an option to restart DHCP if connectivity check is failing and user will add it to his ZTP JSON.
Steps to reproduce the issue:
Single switch connected to a server using an inband port.
Run inband ZTP session, use the following ZTP JSON:
Description
When reboot takes place during ZTP process, interface connected to provision server is not getting IP address from DHCP server on init.
Issue is in the flow of continue processing addition configuration tasks after reboot that took place as part of handling former configuration task.
ZTP engine starts DHCP on the inband interfaces but the interface that is connected to provision server is still down (link to snippet).
Discussed solutions with @rajendra-dendukuri:
Steps to reproduce the issue:
return_success.sh:
Describe the results you received:
Interface connected to provision server not getting ip from DHCP server.
Describe the results you expected:
Interface connected to provision server gets ip from DHCP server.
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
The text was updated successfully, but these errors were encountered: