Junos OS

IMPORTANT MODERATION NOTICE

This community is currently under full moderation, meaning  all posts will be reviewed before appearing in the community. Please expect a brief delay—there is no need to post multiple times. If your post is rejected, you'll receive an email outlining the reason(s). We've implemented full moderation to control spam. Thank you for your patience and participation.



  • 1.  Junos upgrade failed - Could not open database schema

    Posted 09-03-2021 11:59

    I am trying to upgrade MX104 form 13.3 to 20.4 and got the following error ' Could not open database schema'  after executing 'request system software add /var/tmp/jinstall-ppc-20.4R2.7-signed.tgz' on the backup RE -


    Using jbase-ppc-13.3R4.6 [297/1887]
    Verified manifest signed by PackageProductionEc_2014
    Using /var/tmp/jinstall-ppc-20.4R2.7-signed.tgz
    Verified jinstall-ppc-20.4R2.7.tgz signed by PackageProductionECP256_2021
    Using jinstall-ppc-20.4R2.7.tgz
    Using jbundle-ppc-20.4R2.7.tgz
    Checking jbundle-ppc requirements on /
    Using jbase-ppc-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jbase-ppc-20.4R2.7 signed by PackageProductionECP256_2021
    Using /var/v/c/tmp/jbundle-ppc/jboot-ppc-20.4R2.7.tgz
    Using jcrypto-dp-support-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jcrypto-dp-support-20.4R2.7 signed by PackageProductionECP256_2021
    Using jcrypto-ppc-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jcrypto-ppc-20.4R2.7 signed by PackageProductionECP256_2021
    Using jdocs-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jdocs-20.4R2.7 signed by PackageProductionECP256_2021
    Using jkernel-ppc-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jkernel-ppc-20.4R2.7 signed by PackageProductionECP256_2021
    Using jmacsec-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jmacsec-20.4R2.7 signed by PackageProductionECP256_2021
    Using jpfe-ppc-20.4R2.7.tgz
    Verified SHA1 checksum of jpfe-ACX-20.4R2.7.tgz
    Verified SHA1 checksum of jpfe-MX104-20.4R2.7.tgz
    Verified SHA1 checksum of jpfe-MX80-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jpfe-MX104-20.4R2.7 signed by PackageProductionECP256_2021
    Using jroute-ppc-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jroute-ppc-20.4R2.7 signed by PackageProductionECP256_2021
    Using jsd-powerpc-20.4R2.7-jet-1.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jsd-powerpc-20.4R2.7-jet-1 signed by PackageProductionECP256_2021
    Using jsdn-powerpc-20.4R2.7.tgz
    Verified manifest signed by PackageProductionECP256_2021
    Verified jsdn-powerpc-20.4R2.7 signed by PackageProductionECP256_2021
    Using jservices-crypto-ppc-20.4R2.7.tgz
    Using jservices-ppc-20.4R2.7.tgz
    Hardware Database regeneration succeeded
    Validating against /config/juniper.conf.gz
    UI_DBASE_OPEN_FAILED: Database open failed for file '/var/run/db/schema.db': No such file or directory
    mgd: error: could not open database schema: /var/run/db/schema.db
    mgd: error: could not open database schema
    Opening configuration database: Could not open database schema

    mgd: commit complete
    Validation succeeded

    cr4-re1> show system storage
    Filesystem Size Used Avail Capacity Mounted on
    /dev/da0s1a 904M 182M 649M 22% /
    devfs 1.0K 1.0K 0B 100% /dev
    /dev/md0 59M 59M 0B 100% /packages/mnt/jbase
    /dev/md1 208M 208M 0B 100% /packages/mnt/jkernel-ppc-13.3R4.6
    /dev/md2 154M 154M 0B 100% /packages/mnt/jpfe-MX104-13.3R4.6
    /dev/md3 6.6M 6.6M 0B 100% /packages/mnt/jdocs-13.3R4.6
    /dev/md4 74M 74M 0B 100% /packages/mnt/jroute-ppc-13.3R4.6
    /dev/md5 12M 12M 0B 100% /packages/mnt/jcrypto-ppc-13.3R4.6
    /dev/md6 1008M 8.0K 927M 0% /tmp
    /dev/md7 1008M 680K 926M 0% /mfs
    /dev/da0s1e 100M 32K 92M 0% /config
    procfs 4.0K 4.0K 0B 100% /proc
    /dev/da0s1f 5.4G 1.4G 3.5G 29% /var



    ------------------------------
    Leo Chan
    ------------------------------


  • 2.  RE: Junos upgrade failed - Could not open database schema

    Posted 09-05-2021 12:34
    You should reference the release notes and look for an upgrade path or open a case with JTAC on what your upgrade path should be. I'm pretty sure that you can't make a big leap in JUNOS from 13.3 all the way to 20.4. There probably will have to be a phased approach to a middle version so that you can then go directly to 20.4.

    ------------------------------
    Derek Summitt
    ------------------------------



  • 3.  RE: Junos upgrade failed - Could not open database schema

    Posted 09-07-2021 15:46
    I am all set. They are lab devices and I was looking for a quickest way. I ended up have to zeroize the routing engines to get rid of this error.

    ------------------------------
    Leo Chan
    ------------------------------



  • 4.  RE: Junos upgrade failed - Could not open database schema

     
    Posted 09-05-2021 12:37
    The max jump that Junos has ever supported was 4 major versions.

    The MX104 in particular is a separate beast for the upgrade process.  There are some major changes that get introduced by Junos 17.  So the upgrade path recommended to me and what I used going from 13 was a follows

    13 > 15
    15 > 17

    I have not gone beyond 17 yet but check the release notes for 20 and it should confirm that the 17 > 20 would be supported.  I think this would since a jump of 3 major versions has been generally supported for a long time.

    ------------------------------
    Steve Puluka BSEET - Juniper Ambassador
    IP Architect - DQE Communications Pittsburgh, PA (Metro Ethernet & ISP)
    http://puluka.com/home
    ------------------------------