Description

Device Image Deployment has "no-validate" option enabled by default. Therefore, when upgrading Junos images from Junos Space platform, the following RPC is received:

<rpc message-id="1"> <request-package-add> <no-copy/> <no-validate/>

Note: Validation is used to ensure that the candidate software is compatible with the current configuration, while "no-validate" option should turn off validation of the current configuration against the new Junos and may prevent devices to successfully reboot with new Junos images. Selection should be made based on user requirements during Device Image Deployment.

Symptoms

Devices may not reboot successfully with new Junos image installed.

Solution

By default, Image Deployment from Junos Space has "Check compatibility with current configuration" option under Conventional Deployment Options "unchecked". This causes Junos Space to send a "no-validate" option during Image install on a device. In other words, selecting the default option means "no validation" of current configuration with a candidate Junos Image. This may cause the Junos device to not reboot if there is a configuration that is unsupported by the new Junos Image.

Use the steps below to enable the validation check during Image Upgrade.

On Network Management Platform:
  1. Navigate to Images and Scripts -> Images
  2. Select the Image -> Right click the Image and Chose "Deploy Device Image" 
  3. Select the Device which you want to upgrade to

Under Conventional Deployment Options, check the box "Check compatibility with current configuration". This should send a validate option during Image deployment.
alt

Note: This is disabled by default.

Once the above option is checked, the following RPC is will be sent during Image upgrade:

<request-package-add> <no-copy/> <validate/> <package-name>