SRX

Expand all | Collapse all

SRX550 - upgrade from 15.1X49-D170.4 to 18.2R3-S2.9 - Validation failed

Jump to Best Answer
  • 1.  SRX550 - upgrade from 15.1X49-D170.4 to 18.2R3-S2.9 - Validation failed

    Posted 04-30-2020 01:26

    Hi.

     

    I am trying upgrade software on SRX550m from 15.1X49-D170.4 to 18.2R3-S2.9 and I get Validation failed message. I am aware that I can use no-validate option. Howerver - is it safe to use that option? What this error exactly mean (mgd: error: Allocating memory for action maps 'no-ssh-rsa' failed)? I am able to log into device via ssh, so I think it is configure correctly.

     

    root@srx550m> request system software add /var/tmp/junos-srxsme-18.2R3-S2.9.tgz no-copy unlink validate
    
    Formatting alternate root (/dev/ad0s2a)...
    /dev/ad0s2a: 599.0MB (1226700 sectors) block size 16384, fragment size 2048
    using 4 cylinder groups of 149.75MB, 9584 blks, 19200 inodes.
    super-block backups (for fsck -b #) at:
    32, 306720, 613408, 920096
    Checking compatibility with configuration
    Initializing...
    Verified manifest signed by PackageProductionEc_2019 method ECDSA256+SHA256
    Using junos-18.2R3-S2.9 from /altroot/cf/packages/install-tmp/junos-18.2R3-S2.9
    Copying package ...
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/var/jailetc/php_mod.ini: No such file or directory
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/var/jailetc/mime.types: No such file or directory
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/usr/lib/libpsu.so.3: Too many links
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/usr/lib/libyaml.so.3: Too many links
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/usr/lib/libext_db.so.3: Too many links
    veriexec: cannot update veriexec for /cf/var/validate/c/junos/usr/telemetry/na-mqttd/na-mqtt.conf: No such file or directory
    Verified manifest signed by PackageProductionEc_2019 method ECDSA256+SHA256
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    mgd: error: Allocating memory for action maps 'no-ssh-rsa' failed
    Abort trap (core dumped)
    Validation failed
    Validating against /config/rescue.conf.gz
    mgd: commit complete
    Validation succeeded
    ERROR: Configuration validation failed with /altroot/cf/packages/install-tmp/junos-18.2R3-S2.9
    
    
    
    root@srx550m> show system software
    Information for junos:
    Comment:
    JUNOS Software Release [15.1X49-D170.4]

     



  • 2.  RE: SRX550 - upgrade from 15.1X49-D170.4 to 18.2R3-S2.9 - Validation failed
    Best Answer

    Posted 04-30-2020 09:46

    Hello LukaszRz,

     

    I think validation will always fail because there has been a change in internal file system starting 17 release. 

     

    An upgrade with "no-validate" is more likely to be successful.

     

    If you are not comfortable with "no-validate" , I would suggest you to get JTAC involved when you are upgrading.   

     

    Also, as per the upgrade guidelines you are encouraged to upgrades "NOT more than 3 releases" at a time.

     

    Refer :-  https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/18.2/jd0e27340.html#cbbu-rn-junos-es-upgrade-downgrade

     

    "You can upgrade or downgrade to the EEOL release that occurs directly before or after the currently installed EEOL release, or to two EEOL releases before or after. For example, Junos OS Releases 15.1X49, 17.3, 17.4, 18.1 and 18.2 are EEOL releases. You can upgrade from one Junos OS Release to the next release or one release after the next release. For example you can upgrade from Junos OS Release 15.1X49 to Release 17.3 or 17.4, Junos OS Release 17.4 to Release 18.1 or 18.2, and from Junos OS Release 18.1 to Release 18.2 or 18.3 and so on."

     

    Hope this is helpful.

    Thanks!