Programmable Internetworking & Communication Operating System Docs ... Click Spaces -> Space Directory to see docs for all releases ...
Page tree
Skip to end of metadata
Go to start of metadata

 Preparation before Upgrading

Table 1 Checklist before Upgrading

No.

Checking Items

Checking Standard

Results

1

Checking the Running PICOS Version

 

The currently running system software version is lower than the software version to be installed


2

Building Upgrade Environment

Build a different upgrade environment to get the upgrade software according to the need


3

Getting the Required Upgrade Software

Obtain the required supporting upgrade software


4

Backing up Important Data in Flash

All the important data in Flash is backed up


5

Checking Available Flash Space

Flash space is enough to save upgrading package and other files


Checking the Running PICOS Version

Use the version command to check the version of the running system software.

admin@Xorplus$version
Copyright (C) 2009-2019 Pica8, Inc.
===================================
Hardware Model                : as7312_54x
Linux System Version/Revision    : 2.11.16/0a9a4fb
Linux System Released Date      : 11/16/2018
L2/L3 Version/Revision          : 2.11.16/0a9a4fb
L2/L3 Released Date            : 11/16/2018
OVS/OF Version/Revision       : 2.11.16/0a9a4fb
OVS/OF Released Date          : 11/16/2018

Building Upgrade Environment

Please make sure that you have set up an HTTP, TFTP or FTP protocol upgrading environment to get the upgrade software, the basic requirements are as follows:

  • PC can log in to the device through serial or SSH.
  • The communication between the server and the device works well.
  • The upgrading file used by the device has already been stored on the server.

Getting the Required Upgrade Software

Please contact Pica8 technical support engineers at the following website for the latest version of upgrade software.

http://www.pica8.com/support/customer

Backing up Important Data in Flash

Before upgrading, save the important data in Flash to the local PC through FTP or TFTP, and then upload it to the switch after the upgrade is completed.

Where is the PicOS configuration?
OVSDB file

L2/L3 Configuration Files

Checking Available Flash Space

Use the df command to check the available flash space.

admin@Xorplus$df  
Filesystem     1K-blocks   Used Available Use% Mounted on
udev               10240      0     10240   0% /dev
overlay           307068   2944    304124   1% /
tmpfs             204712    132    204580   1% /run
tmpfs               5120      0      5120   0% /run/lock
tmpfs             409420      0    409420   0% /run/shm
tmpfs              51200    180     51020   1% /tmp
/dev/ubi0_0       876492 466972    404684  54% /mnt/open

Upgrading Notes

•  User data (such as the configuration file) will be lost if upgrade from 2.11.x to 3.1.0 (or the later versions).

•  A license check has been added. Without a license, only the first four ports on the system can be used.

  • If PICOS has no license installed (or if the license has expired) before the upgrade, only 4 ports will be activated with the upgrade.
  • If PICOS has a license installed before the upgrade, the license will be copied and active after the upgrade.

       Please check this section for the license installation procedure.

    The device is not supported to downgrade.

    You can log in to a device through its console port or using SSH. After successful login, you can run commands on the command line interface (CLI) to upgrade the device.

   When using FTP/TFTP to download the image, user should verify that the "binary" mode is being used. If the "binary" transfer mode is not being used, the image can be modified during download, and the upgrade will fail during the md5 check.

   The image is platform dependent, that is, the image_name should be consistent with the platform, otherwise the script will abort.

    When upgrading, the installer checks whether there is a user-data partition. If there exists a User-Data partition, the installer only rewrites the running system boot partition (PicOS/ PicOS2) and installs the new installation package to this partition. However, if there is no User-Data partition, the installer removes all the partitions to rebuild a brand new NOS.

   Upgrade operation via upgrade or upgrade2 commands is not allowed on non-default system, you can upgrade PICOS only on default system. When there are more than one PICOS, the default system is the one automatically booted into after reboot.

   The image file of PICOS 3.1.0 and the later versions is a .bin file that can be used for both installation and upgrade, for example onie-installer-picos-s4148-3.1.0.bin.

   Cannot return to 2.11.x if fail to upgrade to 3.1.0 (or the later versions) because of unexpected event such as power outage.

   As port naming conventions of Pica8 switches have been redefined since PICOS 3.2.0, the upgrade script modifies the name of the corresponding port in configuration file when upgrading from PICOS 2.11 to 3.2 or the later version. For details about port naming conventions and port names of Pica8 switches in PICOS 3.2, see Port Index Description.


Upgrading Procedure

NOTE

Usage of upgrade command:

admin@Xorplus$sudo upgrade                            

USAGE

Upgrade system with local new image

SYNOPSIS

upgrade [image_name] [factory-default] [backup-file=(*.lst)]

DESCRIPTION

image_name - Image with bin format file(*.bin)

factory-default - Recovery configuration to factory default

PICOS upgrade is done via the command "upgrade" in bash (launching a shell script named "upgrade.sh"). This script will upgrade the image and back up configuration files automatically.

The format of the upgrade package is *.tar.gz in versions before PICOS 3.1.0, and *.bin in PICOS 3.1.0 and the later version.

The option no-md5-check is removed from PICOS 3.1.0. If there is an MD5 file in the /cftmp directory, the upgrade script will check package integrity with MD5. Else if there is no MD5 file in the /cftmp directory, then skip the MD5 check step.

The option factory-default is used to reset the configuration to factory default when performing upgrade. This option retains the license files from the previous version.


The upgrading procedure in this document gives an example of upgrading on N3048EP-ON from PicOS 2.11.16 to 3.1.0.

Step1

Copy the upgrade package (in the form of .bin) and the MD5 file to /cftmp directory by either FTP, TFTP, HTTP or SCP according to the actual upgrade environment. The following example uses the SCP method.

admin@XorPlus$sudo scp pica8@10.10.50.22:/tftp/build/daily/n3048/picos-3.7.1-DELL_N3048EP-ON-2382c03.bin  /cftmp

NOTE:

If management VRF is enabled, and the FTP/TFTP/HTTP/SCP server is connected via the Eth0/1 port, you need to add the string sudo ip vrf exec mgmt-vrf before the SCP command when executing the scp operation. The format is as follows:

admin@Xorplus:~$ sudo ip vrf exec mgmt-vrf scp pica8@10.10.50.22:/tftp/build/3.7.1/n3048/picos-3.7.1-DELL_N3048EP-ON-2382c03.bin /cftmp

admin@Xorplus:~$sudo ip vrf exec mgmt-vrf scp pica8@10.10.50.22:/tftp/build/3.7.1/n3048/picos-3.7.1-DELL_N3048EP-ON-2382c03.bin.md5 /cftmp

If sudo ip vrf exec mgmt-vrf is not added, find the next hop routing information from the default VRF. For the usage of VRF, refer to the VRF configuration guide.

Step2       Execute the sync operation.

admin@XorPlus$sync

Step3       Change directory to /cftmp.

admin@XorPlus$cd /cftmp

Step4       Run the upgrade command.

admin@XorPlus$sudo upgrade picos-3.7.1-DELL_N3048EP-ON-2382c03.bin

After finishing upgrade will reboot automatically, the system will come up running the new network operating system.

Verifying Version after Upgrading 

admin@Xorplus$version
Copyright (C) 2009-2020 Pica8, Inc.
===================================
Hardware Model                : N3048EP-ON
Linux System Version/Revision : 3.7.1/4b5f523
Linux System Released Date    : 8/27/2020
L2/L3 Version/Revision        : 3.7.1/4b5f523
L2/L3 Released Date           : 8/27/2020
OVS/OF Version/Revision       : 3.7.1/4b5f523
OVS/OF Released Date          : 8/27/2020
  • No labels