So we had this problem and it was related to not having unit 0 on all the non AE interfaces. It seems that on different versions the system will hceck to make sure you have certain things set in your config and sometimes they dont.
We got by this one of two ways, either set unit 0 on all the interfaces or re did the no-validate command when we did the upgrades. Both worked for us.
Of course we still did not make more than that 2 version jump just to be safe.
ge-1/0/5 {
traps;
unit 0 {
family ethernet-switching;
}
}
ge-1/0/6 {
traps;
unit 0 {
family ethernet-switching;
}
}
ge-1/0/7 {
traps;
unit 0 {
family ethernet-switching;
}
}
ge-1/0/8 {
traps;
unit 0 {
family ethernet-switching;
}
}
------------------------------
Steven Skula
------------------------------
Original Message:
Sent: 09-16-2019 14:00
From: Unknown User
Subject: Upgrade firmware to Ex2300
Current firmware:
Hostname: JUNO-B1
Model: ex2300-24t
Junos: 15.1X53-D57.3
--- JUNOS 15.1X53-D57.3 Kernel 32-bit JNPR-11.0-20170825.354680_build
Want to upgrade to 18.4.R2
>request system software validate /tmp/image2.tgz fails with error:
validation fails on:
Validating against /config/juniper.conf.gz
This is the output error:
.....
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
Chassis control process: <xnm:error xmlns="http://xml.juniper.net/xnm/1.1/xnm" xmlns:xnm="http://xml.juniper.net/xnm/1.1/xnm">
Chassis control process: <source-daemon>chassisd</source-daemon>
Chassis control process: <edit-path>[edit interfaces]</edit-path>
Chassis control process: <statement>xe-0/1/1</statement>
Chassis control process: <message>INTERFACES_TYPE_UNIDIR: Error in parsing interface name</message>
Chassis control process: </xnm:error>
mgd: error: configuration check-out failed
Validation failed