This article describes why the AIS script cannot be pushed to EX switches (VC) from Junos Space running Junos 11.4R1.6.

Unable to push the AIS script from Junos Space to virtual chassis using the CLI command below:

request system script add

The following error is received:

Error Package must match hardware or package is corrupted. Upgrade failed .

This error is also received when an attempt is made to add the AIS script directly on the VC.

The virtual chassis of the EX4200 or the EX4500 running Junos 11.4R1.6 or 11.4R2.14 is unable to push AIS scripts on all members from the primary. Also, the AIS script cannot be added to virtual chassis members using Junos Space. But, the AIS script can be added to the individual members.

When the AIS script is added on an individual basis from Junos Space or VC members, Junos Space is unable to check the AIS script on the VC.

On EX4500 VC two member

{master:0}
root@4500vc> show version
fpc0:
--------------------------------------------------------------------------
Hostname: 4500vc
Model: ex4500-40f
JUNOS Base OS boot [11.4R1.6]

fpc1:
--------------------------------------------------------------------------
Hostname: 4500vc
Model: ex4500-40f
JUNOS Base OS boot [11.4R1.6]

{master:0}
root@4500vc> request system software add /var/tmp/jais-3.7R3.0-signed.tgz >>>> CLI Command

Retrieving software images. This process can take several minutes. Please be patient..

Package must match hardware or package is corrupted. Upgrade failed. >>>> Error

Same Error message is received on Junos Space >>>>>>>>>>>>>>

Above mentioned issue is resolved in 12.1 and later codes

root@4500vc> show version
fpc0:
--------------------------------------------------------------------------
Hostname: 4500vc
Model: ex4500-40f
JUNOS Base OS boot [12.1R4.7]

fpc1:
--------------------------------------------------------------------------
Hostname: 4500vc
Model: ex4500-40f
JUNOS Base OS boot [12.1R4.7]

{master:0}
root@4500vc> request system scripts add /var/tmp/jais-3.7R3.0-signed.tgz

Retrieving software images. This process can take several minutes. Please be patient..

Checking pending install on fpc1

Checking pending install on fpc0
Pushing bundle to fpc1

Validating on fpc1
[: -a: unexpected operator

Validating on fpc0
[: -a: unexpected operator
Done with validate on all virtual chassis members >>>> Successful

This issue is resolved from Junos 12.1 onward.

2021-03-22: Updated article terminology

2025-07-15: Minor non-technical update