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

[BTI] Upgrading BTI7000 code using CLI commands

0

0

Article ID: KB35652 KB Last Updated: 08 Apr 2020Version: 1.0
Summary:

The BTI7000 Series platform can be upgraded by using the ProNX GUI software. However, when upgrading multiple devices in a maintenance window, using the Command Line Interface (CLI) method is faster and preferred.

This article details the upgrade procedure by using CLI commands.

 

Symptoms:

This document covers the following:

  1. Download the software image from the Juniper Support site.

  2. Unzip the image into a folder on the PSM server or any server running an FTP server.

  3. Load the code to each BTI7000 platform.

  4. Invoke the code.

  5. Commit the upgrade.

 

Solution:

Perform the following steps:

  1. Download the desired code version from the Support site.  

Do not unzip the file on your desktop. Instead, create a folder on the PSM server (which is also an FTP server), for example, create /home/ftpadmin/NeSoftware/NE12.2.2_C006, and copy the code file from your laptop into this folder. You can then unzip the code into this folder. The /home/ftpadmin/NeSoftware/NE12.2.2_C006 folder should now have the original zip file, plus three files that were unzipped. The original zip file is no longer needed, but it does no harm to leave it in the folder.

At the BTI7000 CLI prompt, load the code by specifying the path and name of this folder.

  1. SSH to the PSM Linux server, and change directory to /home/ftpadmin/NeSoftware. See the example below:

[root@psmd ~]# cd /home/ftpadmin/NeSoftware
[root@psm NeSoftware]#
[root@psm NeSoftware]# mkdir NE12.2.2_C006
[root@psm NeSoftware]#
  1. Use WinSCP or any SCP/FTP utility to copy the zipped code file from your desktop into the PSM server folder, /home/ftpadmin/NeSoftware/NE12.2.2_C006.

Change directory to the folder, and you should see the file that you just copied to it. See the example below:

[root@psm NeSoftware]# cd NE12.2.2_C006
[root@psm NE12.2.2_C006]# ls -l
total 160272
-rw-r--r-- 1 root root 164114813 Mar 18 15:44 NE12.2.2_C006.zip
  1. Use the unzip command to unzip the code and extract the three files.  

You can see that there are now four files in the folder.

The Present Working Directory (PWD) shows the full path of the current folder.

[root@psm NE12.2.2_C006]# pwd
/home/ftpadmin/NeSoftware/NE12.2.2_C006
[root@psm NE12.2.2_C006]#

[root@psm NE12.2.2_C006]# unzip NE12.2.2_C006.zip
Archive:  NE12.2.2_C006.zip
  inflating: BTI_OLS_MANIFEST        
  inflating: mibs.tgz                
  inflating: OLS_12_2_2              
[root@psm NE12.2.2_C006]#  
[root@psm NE12.2.2_C006]# ls -l
total 322140
-rw-r--r-- 1 root root     14655 Mar 18 16:49 BTI_OLS_MANIFEST
-rw-r--r-- 1 root root    257768 Mar 18 16:49 mibs.tgz
-rw-r--r-- 1 root root 164114813 Mar 18 16:50 NE12.2.2_C006.zip
-rw-r--r-- 1 root root 165478400 Mar 18 16:51 OLS_12_2_2
[root@jlab-psm NE12.2.2_C006]#
  1. Load the code to the BTI7000 platform from the BTI7000 CLI prompt. This can be done at any time before the upgrade.

The BTI7000 platform has an active and an inactive folder with the current code version and old code version, respectively. When a new code version is loaded during an upgrade, the previous old version is replaced in the inactive bank. After the upgrade is invoked and completed, the new version that was in the inactive bank is stored in the active bank, and the previously running version moves to the inactive bank, replacing the previous inactive version.

In this example, when you copy the 12.2.2 code to the node, it will automatically be stored in the secondary folder.

  • Telnet to the node on TCP 3084.

  • Go to Enable mode, and load the code:

default username: admin
default password: admin

Example:

BTI7000> en
BTI7000# sw-upgrade load ftp 10.85.211.66 path NeSoftware/NE12.2.2_C006 user ftpadmin
Password: ftpadmin
..............................................................
Active load: 10.3.5 C006        Inactive load: 12.2.2 C006
BTI7000#

  1. When it is time for the scheduled upgrade, invoke the image in the inactive bank. The keyword nocheckalarm will allow the upgrade even if there is an alarm, such as a missing SFP.  

Note: The name of the code image needs to be in quotation marks, due to the space.   

BTI7000# sw-upgrade invoke "12.2.2 C006" nocheckalarm                        
.....................
[20:44:22  Wed Mar 18 2020] SCP-1/5 Upgrade Started.
.........................................................................
[20:46:44  Wed Mar 18 2020] SCP-1/5 Reinitializing.
  1. When the SCP initializes, you will first lose the telnet session but be able to re-establish the session after a minute. However, if the management path relies on one of the line cards, such as the PVX, you will lose the telnet session a second time when the PVX or the other line card reloads.  

When the upgrade is complete, the last command is to commit.  

When all cards are upgraded and reloaded, there will be an upgrade alarm with severity = min. This indicates that the upgrade is complete, but it still needs to be committed. At this point, you can commit or cancel. You may also leave the node in this state for a period of time if you want to check on e-services and other connectivity, but you cannot make any changes. When satisfied that the upgrade is successful, issue the command to commit.   

BTI7000# show alarm all

Alarm    Equipment        Sev    Date   Time   SA/NSA       Description         
------- ---------------- ------ ----- -------- ------ --------------------------
Pack    SCP-1/5           Min   03-18 20:48:32  NSA   System upgrade in progress.
BTI7000#
BTI7000# sw-upgrade commit
.
Commit completed successfully
BTI7000#
BTI7000#

 

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