...
NOTE：
|
...
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 an upgrade environment according to the need. | |
3 | Getting the Required Upgrade Software | Obtain the required supported upgrade software. | |
4 | Backing up Important Data | All the important data was backed up. | |
| 5 | Converting Configuration to 4.x before Upgrade (when Upgrade from Version 3.x to 4.x) | 4.x configuration is generated from 3.x configuration file. |
Checking the Running PICOS Version
Use the version command to check the version of the running system software.
...
https://www.pica8.com/support/
Backing up Important Data
Before upgrading, save the important data, e.g. the configuration file, to the local PC through FTP or TFTP, and then upload it to the switch after the upgrade is completed if needed.
Anchor convert config convert config
Converting Configuration to 4.x before Upgrade (when Upgrade from Version 3.x to 4.x)
| convert config | |
| convert config |
| Info | ||
|---|---|---|
| ||
When upgrade PICOS from version 3.x to 4.x:
|
You can not cannot do a standard upgrade from 3.x to 4.x. This is because 3.x configuration and 4.x configuration are not compatible, and PICOS 4.x will not be able to boot with 3.x configuration after the upgrade.
In order to upgrade from 3.x to 4.x, follow the procedure below to prepare the 4.x configuration file before upgrade:
- Create directory /pica/config-4.x/.
- Contact Pica8 support to convert the 3.x configuration to 4.x configuration in configuration file pica_startup.boot.
- Copy the 4.x configuration file (converted from 3.x configuration file in step 2) into the directory /pica/config-4.x just created. After upgrading from 3.x to 4.x and after rebooting, PICOS 4.x will look for the 4.x configuration in /pica/config-4.x.
...
admin@Xorplus:~$ sudo upgrade2 USAGE Upgrade system with local new image SYNOPSIS upgrade2 [image_name] [factory-default] [use-prev-config] [backup-file=(*.lst)] DESCRIPTION image_name - Image with bin format file(*.bin) factory-default - Recovery configuration to factory default use-prev-config - Use previous config, and syslog trace backup-file=(*.lst) - Specify a user defined backup list |
For PICOS go2cli version, users can run the upgrade2 command under CLI operational mode or configuration mode:
| Code Block |
|---|
admin@Xorplus> upgrade2 image-file xx.bin Possible completions: <[Enter]> Execute this command backup-file Specify a user defined backup list(*.lst) factory-default Recovery configuration to factory default use-prev-config Use previous configuration, and syslog trace admin@Xorplus# run upgrade2 image-file xx.bin Possible completions: <[Enter]> Execute this command backup-file Specify a user defined backup list(*.lst) factory-default Recovery configuration to factory default use-prev-config Use previous configuration, and syslog trace |
...
| Info | ||
|---|---|---|
| ||
admin@Xorplus:~$ sudo ip vrf exec mgmt-vrf scp pica8@10.10.50.22:/tftp/build/4.0.1/as7312_54x/onie-installer-picos-as7312_54x-4.0.1-cc8d268.bin /cftmp admin@Xorplus:~$sudo ip vrf exec mgmt-vrf scp pica8@10.10.50.22:/tftp/build/4.0.1/as7312_54x/onie-installer-picos-as7312_54x-4.0.1-cc8d268.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.
Φ Download a file: file scp get remote-file <remote-file-path> [local-file local-file-path] ip-address <ip-address>:<port> [vrf <mgmt-vrf | vrf-name>] Φ Upload a file: file scp put local-file <local-file-path> [remote-file <remote-file-path>] ip-address <ip-address>:<port> [vrf <mgmt-vrf | vrf-name>] |
...
After finishing upgrade, the switch will reboot automatically, the system will come up running the new network operating system.
NOTE：
|
...