Hypervisor offers an IP address to vSRX via DHCP when it is configured as a dhcp-client on the fxp0.0 interface, to get out-of-band access from Juniper Device Manager (JDM) to vSRX. However, vSRX installs a default route towards JDM, so it seems that the Hypervisor is offering the gateway (router attribute) on the DHCP offer.

This article explains what should be done to resolve the problem.

vSRX is installing a default route towards the JDM when Hypervisor offers an IP address via DHCP (configured as a dhcp-client on the fxp0.0 interface) to vSRX, to get out-of-band access from JDM to vSRX.

admin@vsrx> show dhcp client binding detail

Client Interface/Id: fxp0.0
Hardware Address:             f4:cc:55:2b:49:4e
State:                        BOUND(LOCAL_CLIENT_STATE_BOUND)
Lease Expires:                2018-07-27 21:30:02 UTC
Lease Expires in:             2489 seconds
Lease Start:                  2018-07-27 20:30:02 UTC
Server Identifier:            192.168.1.1
Client IP Address:            192.168.1.100
Update Server                 No

DHCP options:
Name: dhcp-lease-time, Value: 1 hour
Name: server-identifier, Value: 192.168.1.1
Name: router, Value: [ 192.168.1.1 ] <--- Router value offered by JDM
Name: name-server, Value: [ 192.168.1.1 ]
Name: subnet-mask, Value: 255.255.255.0

Given that fxp0.0 is the outbound management interface to access vSRX locally from JDM, it should not be installing a default route pointing to the JDM.

To resolve the issue, upgrade to image 15.1X53-D471.

The default-route issue has been fixed in PR1281578 .