Junos OS

Expand all | Collapse all

mx480 upgrade fail

Jump to Best Answer
  • 1.  mx480 upgrade fail

    Posted 07-31-2018 05:19

    I try upgarde dual RE mx480. 

    Routing Engine 0 REV 08   740-031116   9009128476        RE-S-1800x4

    Routing Engine 1 REV 08   740-031116   9009128489        RE-S-1800x4


    The first re0 upgraded fine: 

    admin@mx480-koddos> show version
    Hostname: mx480-koddos
    Model: mx480
    Junos: 15.1R7.8
    JUNOS OS Kernel 64-bit [20180310.ba55661_builder_stable_10]
    JUNOS OS libs [20180310.ba55661_builder_stable_10]
    JUNOS OS runtime [20180310.ba55661_builder_stable_10]
    JUNOS OS time zone information [20180310.ba55661_builder_stable_10]
    JUNOS OS libs compat32 [20180310.ba55661_builder_stable_10]
    JUNOS OS 32-bit compatibility [20180310.ba55661_builder_stable_10]
    JUNOS py base [20180427.182457_builder_junos_151_r7]
    JUNOS OS crypto [20180310.ba55661_builder_stable_10]
    JUNOS network stack and utilities [20180427.182457_builder_junos_151_r7]
    JUNOS libs compat32 [20180427.182457_builder_junos_151_r7]
    JUNOS runtime [20180427.182457_builder_junos_151_r7]
    JUNOS platform support [20180427.182457_builder_junos_151_r7]
    JUNOS modules [20180427.182457_builder_junos_151_r7]
    JUNOS libs [20180427.182457_builder_junos_151_r7]
    JUNOS mtx Data Plane Crypto Support [20180427.182457_builder_junos_151_r7]
    JUNOS daemons [20180427.182457_builder_junos_151_r7]
    JUNOS Voice Services Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services SSL [20180427.182457_builder_junos_151_r7]
    JUNOS Services Stateful Firewall [20180427.182457_builder_junos_151_r7]
    JUNOS Services RPM [20180427.182457_builder_junos_151_r7]
    JUNOS Services PTSP Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services NAT [20180427.182457_builder_junos_151_r7]
    JUNOS Services Mobile Subscriber Service Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services MobileNext Software package [20180427.182457_builder_junos_151_r7]
    JUNOS Services LL-PDF Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services Jflow Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services IPSec [20180427.182457_builder_junos_151_r7]
    JUNOS IDP Services [20180427.182457_builder_junos_151_r7]
    JUNOS Services HTTP Content Management package [20180427.182457_builder_junos_151_r7]
    JUNOS Services Crypto [20180427.182457_builder_junos_151_r7]
    JUNOS Services Captive Portal and Content Delivery Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Services COS [20180427.182457_builder_junos_151_r7]
    JUNOS Border Gateway Function package [20180427.182457_builder_junos_151_r7]
    JUNOS AppId Services [20180427.182457_builder_junos_151_r7]
    JUNOS Services Application Level Gateways [20180427.182457_builder_junos_151_r7]
    JUNOS Services AACL Container package [20180427.182457_builder_junos_151_r7]
    JUNOS Packet Forwarding Engine Support (MX/EX92XX Common) [20180427.182457_builder_junos_151_r7]
    JUNOS Packet Forwarding Engine Support (M/T Common) [20180427.182457_builder_junos_151_r7]
    JUNOS Online Documentation [20180427.182457_builder_junos_151_r7]
    JUNOS FIPS mode utilities [20180427.182457_builder_junos_151_r7]

    But, the next re1 fail after upgrade:

    ugen0.1: <Intel> at usbus0
    uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
    uhub0: 1 port with 1 removable, self powered
    ugen0.2: <vendor 0x8087> at usbus0
    uhub1: <vendor 0x8087 product 0x0020, class 9/0, rev 2.00/0.00, addr 2> on usbus0
    ada0 at ata0 bus 0 scbus0 target 0 lun 0
    uhub1: 8 ports with 8 removable, self powered
    ada0: <UGB94BPH32H0S1-KCI 2030> ATA8-ACS SATA 2.x device
    ada0: Serial Number 11000055735
    ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 512bytes)
    ada0: 30533MB (62533296 512 byte sectors)
    ada0: Previously was known as ad0
    ada1 at ata0 bus 0 scbus0 target 1 lun 0
    ada1: <UGB30SFA4000T1 20101028> ATA-7 device
    ada1: Serial Number SFA4000T1 00001529
    ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 512bytes)
    ada1: 3831MB (7847280 512 byte sectors)
    ada1: Previously was known as ad1
    SMP: AP CPU #2 Launched!
    SMP: AP CPU #1 Launched!
    SMP: AP CPU #3 Launched!
    Timecounter "TSC" frequency 1729040608 Hz quality 1000
    WARNING: WITNESS option enabled, expect reduced performance.
    Trying to mount root from cd9660:/dev/md0 []...
    Installation of disk:/freebsd/inWARNstall.tar
    ING: was not properly dismounted
    ERROR: Could not find installation package
    *** The installer exited with status 3 ***
    *** The installation is unsuccessful!!! ***
    A shell has been started. Type exit<cr> to reboot:
    # ls -al /

     What should I do?

  • 2.  RE: mx480 upgrade fail

    Posted 07-31-2018 07:20

    I'm not sure if the MX480 upgrade to the junos is the same as an MX240?


    I am just completing an MX240 upgrade from 16 to 17 on a dual routing-engine device.  After a few problems it is now upgraded. 


    To ensure "master switch" completed successfully I also implimented GRES.


    I loaded the software to /var/tmp and just completed:


    request system software add re1 /var/tmp/(Junos file) no-validate

    request system software add /var/tmp/(junos file) no-validate


    Make sure you are on re0 (You probably will be), then run:

    request system reboot other-routing-engine     ----   You won't lose connectivity with this command (or you can just reboot the device but that defeats the purpose of redundancy)......


    Then you either need to switch master (you will need to if you want redundancy, but this then gives another problem of BGP reconvergence which can take a few minutes). Use this command:

    request chassis routing-engine master switch    ---- Cause BGP convergence


    or, logon to re1 and then complete the same command as above by rebooting the other re.


  • 3.  RE: mx480 upgrade fail
    Best Answer

    Posted 07-31-2018 07:50