Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Upgrading JUNOS Software on a Virtual Chassis of EX2300 and EX3400

0

0

Article ID: KB34662 KB Last Updated: 18 Jun 2019Version: 1.0
Summary:

The EX2300 and EX3400 devices come with a 2GB of storage space.  There may be upgrade situations where there’s not enough free storage space required for a successful upgrade.
This article provides upgrade procedures for Virtual Chassis (VC) systems which address this issue.

Symptoms:

During a software upgrade of a member, if there is not enough storage space, the following error will be observed:

{master:0}
root@juniper> request system software add /var/tmp/junos-arm-32-18.1R3-S5.3.tgz unlink reboot force member 3
ERROR: insufficient space for /packages/db/junos-arm-32-18.1R3-S5.3/contents/junos-runtime.tgz
ERROR: insufficient space
ERROR: Failed to add junos-arm-32-18.1R3-S5.3.tgz
veriexec: /usr/libexec/debug.sh: Authentication error
veriexec: /usr/libexec/hooks.sh: Authentication error
veriexec: /usr/libexec/ui/validate_hooks.sh: Authentication error
/usr/libexec/ui/validate-config.sh: DebugOn: not found
/usr/libexec/ui/validate-config.sh: DebugOff: not found
Solution:
To upgrade a Virtual Chassis (VC) system, we recommend upgrading the linecards first and then upgrading the REs to complete the VC system upgrade.  Here are the methods to upgrade the linecards and REs in the following four members VC system example:
{master:0}
root@juniper> show virtual-chassis   
 
Preprovisioned Virtual Chassis
Virtual Chassis ID: d0e1.846e.3144
Virtual Chassis Mode: Enabled
                                                Mstr           Mixed Route Neighbor List
Member ID  Status   Serial No    Model          prio  Role      Mode  Mode ID  Interface
0 (FPC 0)  Prsnt    NW0215340024 ex3400-24p     129   Master*      N  VC   2  vcp-255/1/0
                                                                           1  vcp-255/1/1
1 (FPC 1)  Prsnt    NY0215350008 ex3400-48p     129   Backup       N  VC   0  vcp-255/1/0
                                                                           3  vcp-255/1/1
2 (FPC 2)  Prsnt    NV0216340065 ex3400-24t       0   Linecard     N  VC   3  vcp-255/1/0
                                                                           0  vcp-255/1/1
3 (FPC 3)  Prsnt    NV0216290113 ex3400-24t       0   Linecard     N  VC   1  vcp-255/1/0
                                                                           2  vcp-255/1/1

Upgrading one linecard at a time in a VC system.  In our example, the linecards are members/FPCs 2 and 3.
 

    1- Execute storage clean up.

    root@juniper> request system storage cleanup all-members

    2- Delete snapshot on all members.

    root@juniper> request system snapshot delete * all-members.

    3- Copy the new SW package file to the /tmp folder (tmpfs) of the linecard.  In our example, member/FPC 3 is the first linecard to be upgraded.

    root@juniper>
    root@juniper> file copy /var/tmp/junos-arm-32-18.2R2-S4.3.tgz fpc3:/tmp/.

     Note: Tmpfs is a temporary file system which stores files in virtual RAM memory.

    4- Login to the member 3.  Use the unlink and force options while performing a software update.

   {master:0}
   root@juniper> request session member 3
   Last login: Tue Jun 18 08:59:46 from master
 
    --- JUNOS 18.1R3-S5.3 Kernel 32-bit  JNPR-11.0-20190316.df99236_buil
    root@juniper:LC:3% cli
    {linecard:3}
    root@juniper>
    root@juniper> request system software add /tmp/junos-arm-32-18.2R2-S4.3.tgz unlink reboot force member 3‚Äč

       5- If step 4 fails, run the software update with the force option again (it will work the second time in some situations).

       6- Member/FPC 3 reboots and comes online with the new software version. 
 
 
       {master:0}
       root@juniper> show version | match "fpc|Junos:"                                                                
       fpc0:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc1:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc2:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc3:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
 
       {master:0}

   7- Repeat the above steps to upgrade all other linecards.  In our example, the other linecard in the VC chassis is member/FPC 2.  Once the linecards are upgraded, verify the software releases of the linecards with the                following command.            

       {master:0}
       root@juniper> show version | match "fpc|Junos:"
       fpc0:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc1:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc2:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc3:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
 
       {master:0}
       root@juniper>

Upgrading the REs in a VC system.  In our example, the REs are members/FPCs 0 and 1.
 

    1- Execute storage clean up.

    root@juniper> request system storage cleanup all-members

    2- Delete snapshot on all members.

    root@juniper> request system snapshot delete * all-members.

    3- Use the unlink and force options while performing a software update for backup RE (member 1).  For example:

       {master:0}
       root@juniper >
       request system software add /var/tmp/junos-arm-32-18.2R2-S4.3.tgz unlink reboot force member 1

     Note: The force option frees up storage space by removing the non-recovery snapshots.

    4- If step 3 fails, run the software update with the force option again (it will work the second time in some situations.)

    5- Backup RE (member/FPC 1) reboots and comes online with the new software version.

       {master:0}
       root@juniper> show version | match "fpc|Junos:"                                                                
       fpc0:
       --------------------------------------------------------------------------
       Junos: 18.1R3-S5.3
       fpc1:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc2:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc3:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
   

    6- Final step is to complete the upgrade of the Master RE (member/FPC 0) using the same steps for upgrading the backup RE (member/FPC 1).  Verify the release of software for each member with the following              command:

 
    root@juniper> show version | match "fpc|Junos:"
       fpc0:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc1:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc2:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
       fpc3:
       --------------------------------------------------------------------------
       Junos: 18.2R2-S4.3
 
       {master:1}
       root@juniper>


 

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search