Many Juniper switches are pre-configured with different options to facilitate their introduction to ZTP environments.

This article explains which statements should be optimized, mainly on new switches, if ZTP is not implemented on the network to stop unwanted messages and processing.

When a new device is added to a  Zero Touch Provisioning (ZTP) network, it will request an available IP address, upgrade the Junos firmware, and modify its configuration file. However, if ZTP is not in used, the following messages will constantly be reported:

From log messages:

Mar 22 00:51:27 MUM104-CSW-PRI-FL01 jdhcpd: DH_SVC_SENDMSG_FAILURE: sendmsg() from 0.0.0.0 to port 67 at 255.255.255.255 via interface 5 and routing instance default failed: Network is down
Mar 22 00:51:31 MUM104-CSW-PRI-FL01 jdhcpd: DH_SVC_SENDMSG_FAILURE: sendmsg() from 0.0.0.0 to port 67 at 255.255.255.255 via interface 5 and routing instance default failed: Network is down

As real-time events:

Auto Image Upgrade: DHCP Client Bound interfaces:
Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0
Auto Image Upgrade: To stop, on CLI apply
"delete chassis auto-image-upgrade"  and commit

Auto Image Upgrade: No DHCP Client in bound state, reset all DHCP clients
Auto Image Upgrade: DHCP Client State Reset: irb.0 vme.0

1. Management interfaces such as EM, ME, VME, and the default IRB.0 are pre-configured on switches to obtain an IP address via DHCP automatically as part of the ZTP process, and track DH_SVC_SENDMSG_FAILURE logs on failing attempts due to the following configurations:

root@switch>show configuration system | match dhcp | display set

set system processes dhcp-service traceoptions file dhcp_logfile
set system processes dhcp-service traceoptions file size 10m
set system processes dhcp-service traceoptions level all
set system processes dhcp-service traceoptions flag all

root@switch>show configuration interfaces| match dhcp | display set

set interfaces em1 unit 0 family inet dhcp vendor-id Juniper-qfx5100-96s-8q
set interfaces irb unit 0 family inet dhcp vendor-id Juniper-qfx5100-96s-8q
set interfaces vme unit 0 family inet dhcp vendor-id Juniper-qfx5100-96s-8q

Improve this by deleting DHCP configurations on unwanted ports. For example:                           

root@switch# delete interface vme unit 0 family inet dhcp
root@switch# delete interface irb unit 0 family inet dhcp
root@switch# delete interface em1 unit 0 family inet dhcp
root@switch# ​commit  

2. Due to ZTP settings, new brand switches will check and install the specified Junos OS on the ZTP servers, reporting the below logs on each failing attempt:

Auto Image Upgrade: DHCP Client Bound interfaces:
Auto Image Upgrade: DHCP Client Unbound interfaces: irb.0 vme.0
Auto Image Upgrade: To stop, on CLI apply

Fix this by removing the predefined auto-image-upgrade statement if ZTP is not in used:

delete chassis auto-image-upgrade

3. Phone-home client  (PHC) features may also be enabled on new switches due to ZTP requirements. Although no logs may be seen, it is recommended to remove this configuration on non-ZTP environments to avoid unnecessary processing:

delete system phone-home
deactivate apply-groups phcd_user_script
deactivate groups phcd_user_script

2020-06-17: Article improved upon by adding AUTO IMAGE UPGRADE logs and adding instructions on what should be done if ZTP is not used.