Difference between revisions of "Zero-Touch Provisioning (ZTP) Not Working"
Jump to navigation
Jump to search
(Created page with "You need to set an NTP server in your DHCP scope. A Juniper box checks the signatures of the packages it is installing, and if the system clock is too far off, the certificat...") |
|||
(2 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
+ | If you are monitoring your Juniper ZTP server, and you see the file get downloaded, but you get a message like this: | ||
+ | |||
+ | <PRE style="color:white;background-color:black;font-weight:bold;font-size:1.2em;"> | ||
+ | Auto Image Upgrade: Installation of /var/tmp/junos-arm-32-22.3R1-S2.1.tgz image fetched from server 192.168.1.1 through vme failed:[ERROR: Failed to add junos-arm-32-22.3R1-S2.1.tgz] | ||
+ | </PRE> | ||
+ | |||
You need to set an NTP server in your DHCP scope. A Juniper box checks the signatures of the packages it is installing, and if the system clock is too far off, the certificates will not be valid. | You need to set an NTP server in your DHCP scope. A Juniper box checks the signatures of the packages it is installing, and if the system clock is too far off, the certificates will not be valid. |
Latest revision as of 16:38, 19 September 2024
If you are monitoring your Juniper ZTP server, and you see the file get downloaded, but you get a message like this:
Auto Image Upgrade: Installation of /var/tmp/junos-arm-32-22.3R1-S2.1.tgz image fetched from server 192.168.1.1 through vme failed:[ERROR: Failed to add junos-arm-32-22.3R1-S2.1.tgz]
You need to set an NTP server in your DHCP scope. A Juniper box checks the signatures of the packages it is installing, and if the system clock is too far off, the certificates will not be valid.