Upgrading the CTP2000 Series Devices to Dual Image of CTPOS 9.3R2
Starting from CTPOS Release 9.3R2, you can install and upgrade dual image of CTPOS 9.3R2 on CTP2000 Series devices. This topic describes the install and upgrade procedures.
CTPOS Release 9.3R2 supports only CTP2000 Series (Gen3 and Gen4) devices.
Prerequisites for Dual Image Upgrade
Upgrading to Dual Image on CTP2000 Series
Before you upgrade to dual image, ensure that you meet the following broad level requirements.
-
You can perform dual upgrade by using a console connection (and not SSH) to the device or through a non-interactive upgrade process on a SSH session.
-
For USB clean installation or dual upgrade process, insert an USB into the device.
-
This dual image upgrade feature is supported from CTPOS 9.1R3 release. However, if you want to upgrade any earlier CTPOS versions to CTPOS 9.3R2, then you must first upgrade the earlier versions to CTPOS 9.1R3 on CTP2000 Series devices and then to CTPOS 9.3R2.
CTPOS releases from release 9.1R3-x onwards can be directly upgraded to 9.3R2 using the dual image upgrade.
-
The partitions geometry details on both category of platforms are:
Following partitions will be created on CTP2000 Series device when running the factory installation USB or upgrading from a single-image CTPOS (e.g., 7.3Rx). Otherwise, the existing partitions will be used. The first two partitions are common to both images. The first partition (BIOS Type) will have 1M size and will have no label name. This partition is required for supporting dual boot feature (legacy Bios + UEFI boot).
Table 1: b. UEFI Supported Platforms–CTP2000 Gen3 Series Label
Size
Type
CTP_BOOT 100M Ext3 CTP_ROOT_1 1400M Ext3 CTP_HOME_1 50M Ext3 CTP_VAR_1 50M Ext3 CTP_LOCAL_1 300M Ext3 CTP_ROOT_2 1400M Ext3 CTP_HOME_2 50M Ext3 CTP_VAR_2 50M Ext3 CTP_LOCAL_2 300M Ext3 Total Size 3.8 GB Table 2: b. UEFI Supported Platforms–CTP2000 Gen4 Series Label
Size
Type
CTP_EFI 100M Ext3 CTP_ROOT_1 4000M Ext3 CTP_HOME_1 200M Ext3 CTP_VAR_1 200M Ext3 CTP_LOCAL_1 1000M Ext3 CTP_ROOT_2 4000M Ext3 CTP_HOME_2 200M Ext3 CTP_VAR_2 200M Ext3 CTP_LOCAL_2 1000M Ext3 Total Size 11 GB -
Following files will be available in CTPOS 9.3R2 Release to install the dual image:
File Name
Purpose
acorn_310_dual_image_upgrade_ctp2k-03_260805.tgz Dual Image Upgrade script for
CTP2000 Gen3 Series device running a 9.1x release
acorn_310_dual_image_upgrade_ctp2k-04_260805.tgz Dual Image Upgrade script for
CTP2000 Gen4 Series device running a 9.1x release
acorn_619_dual_image_upgrade_ctp2k-03_260805.tgz Dual Image Upgrade script for CTP2000 Gen3 Series device running a 9.3R2 release acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz Dual Image Upgrade script for CTP2000 Gen4 Series device running a 9.3R2 release CTPOS_9.3R2_partitions_ctp2k-03_260805.tgz CTPOS Image file for CTP2000 Gen3 Series device. CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz CTPOS Image file for CTP2000 Gen4 Series device. ctpos_usb_clean_install_9.3R2_ctp2k-04_260805.img.gz
NOTE: This file is provided as a compressed file (.gz) which was compressed using gzip. Instructions on how to uncompress it are included in the "Installing Clean Dual Image on CTP2000 Gen4 Series Device from USB" section below.
Bootable USB image for performing factory install (repartitions CTP SSD)
This file performs partitioning, formatting, and filesystem setup on the CTP 2000 Gen4 flash device with dual image partitions.
ctpos_usb_install_9.3R2_ctp2k-04_260805.img.gz Bootable USB image for performing Dual Image Upgrade.
This file loads a CTPOS image onto one of the dual partitions of the CTP 2000 Gen4 flash.
flash_ctp_9.3R2_2k-03_260812.img.gz CTPOS Flash Image file for CTP2000 Gen3. ctp_complete_9.3R2_260805.tgz
Release Bundle (contains all upgrade files)
Installing Clean Dual Image on CTP2000 Gen4 Series Device from USB
The USB flash image ctpos_usb_clean_install_9.3R2_ctp2k-04_260805.img.gz is needed to install a clean CTPOS 9.3R2 in the CTP2000 Gen4 Series device. Download this image from the Juniper Networks download page at https://support.juniper.net/support/downloads/ for CTPOS 9.3R2 Release.When USB install for dual upgrade is executed:
|
On a single image system, it will |
|
|
On a dual image system, it will |
Prepare the system to accept image upgrade partition file (create RAM disk). |
To install dual image from USB:
Burning Compact Flash on CTP2000 Gen3 Series Device
To burn compact flash on CTP2000 Gen3 Series device:
-
Unmount all the sd<x> present on CTP2000 Gen3 device; sd<x> filesystem is displayed in the command "df -h".
-
Do the flashing of CTP2000 Gen3 device with the command ssh user@remote_host "zcat /path/flash_ctp_9.3R2_2k-03_260812.img.gz" | sudo dd of=/dev/sd<x> bs=1M on the node fetching flash file (img.gz) from a remote server.
-
Reboot the node.
[root@ctp_91:~ 12]# df -h Filesystem Size Used Avail Use% Mounted on none 3.9G 0 3.9G 0% /dev tmpfs 3.9G 532K 3.9G 1% /run tmpfs 3.9G 3.9M 3.9G 1% /var/volatile /dev/sda1 91M 29M 58M 34% /boot /dev/sda5 1.3G 1.1G 230M 82% /flash_root /dev/sda6 43M 95K 40M 1% /flash_home /dev/sda7 43M 3.7M 37M 10% /flash_var /dev/sda8 278M 7.3M 256M 3% /flash_local /dev/ram2 89M 121K 87M 1% /home [root@ctp_91:~ 13]# umount /dev/sda* [root@ctp_91:~ 14]# df -h Filesystem Size Used Avail Use% Mounted on none 3.9G 0 3.9G 0% /dev tmpfs 3.9G 532K 3.9G 1% /run tmpfs 3.9G 3.9M 3.9G 1% /var/volatile /dev/ram2 89M 121K 87M 1% /home [root@ctp_91:~ 15]# [root@ctp_91:~ 15]# ssh root@10.216.118.69 "zcat /tmp/flash_ctp_9.3R2_2k-03_260812.img.gz" | sudo dd of=/dev/sda bs=1M root@10.216.118.69's password: 0+104089 records in 0+104089 records out 4110188544 bytes (4.1 GB, 3.8 GiB) copied, 175.762 s, 23.4 MB/s [root@ctp_91:~ 16]# [root@ctp_91:~ 16]# reboot
Boot logs will be displayed at this point on the device. However, we are not showing it here.
-
Node will be bring up with first boot parameters. Follow step 7 onwards from Installing Clean Dual Image on CTP2000 Gen4 Series Device from USB.
Upgrading CTPOS to Dual Image
Before you upgrade to CTPOS 9.3R2 dual image on your CTP2000 device, ensure that the device has a dual partition.
You can upgrade to CTPOS 9.3R2 on a CTP2000 Series device through three different interface methods:
USB (only for CTP2000 Gen4 Series device)
CLI (interactive or non-interactive mode)
CTPView
The node upgrades the image on the appropriate partition based on the following conditions.
-
If the node is running with a dual partition but having a single image, then the image will be upgraded to the alternate partition along with personality transfer.
-
If the node is running with dual partitions, the image upgrade will occur along with the personality transfer based on the following conditions:
Different release versions installed in both partitions > The partition having the lower release version/name will be upgraded.
Same release versions installed in both partitions > The partition having the older “Root-FS/Kernel compile” timestamp will be upgraded.
Same release versions and same “Root-FS/Kernel compile” timestamp in both partitions > The partition having the older “Image upgrade” timestamp will be upgraded.
9.3R2-comp-YYMMDD-HHMMSS-load-YYMMDD-HHMMSS format, where:9.3R2: Release name
- comp-YYMMDD-HHMMSS: Root-FS / Kernel compile timestamp
- load-YYMMDD-HHMMSS: Image upgrade timestamp
- Upgrading CTPOS to Dual Image via USB
- Upgrading Dual Image through CLI (interactive mode)
- Upgrading Dual Image through CLI (non-interactive mode)
- Upgrading Dual Image on CTP2000 Series from CTPView
Upgrading CTPOS to Dual Image via USB
Upgrading the ctpos_usb_install_9.3R2_ctp2k-04_260805.img.gz image through USB follows the same procedure as described in Installing Clean Dual Image on CTP2000 Gen4 Series Device from USB step 1 through step 6.
This method is more useful when there is no network connection.
From Step 7 onwards, the system continues with the personality transfer of the currently running image and CTP2000 Gen4 Series device will be up with 9.3R2.
================================================================================================
============ CTPOS USB installation - Version 0.54==============================================
--- Checking for programs... Done.
--- Detecting system type: CTP2000_PPF84
--- Detecting disks/partitions on system... Done.
--- Detecting available image files... Only one image file exists: 9.3R2
-----------------------------------------------
Please Select a destination disk from the list:
1) USB Disk /dev/nvme0n1 (93.2G)
-----------------------------------------------
Selection: 1
-----------------------------------------------
Here are your installation selections:
Image file: 9.3R2
Destination disk: /dev/nvme0n1
-----------------------------------------------
Continue with installation? y[n]: y
CTP system software upgrade utility - Version 1.5.0
Found kernel version 6.1.90-yocto-standard, setting KVER to 619
Checking for active menu sessions
Found USB storage device... Mounting
System version is 619
Here is a list of all the found compatible CTP code archive files:
/tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz
Removing old installation residue...
/tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz is the newest archive file...
===== Uncompressing and Extracting Archive =====
Archive file: /tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz
acorn_install/
acorn_install/install
acorn_install/uefi_partition_files.tgz
acorn_install/sgdisk
acorn_instalEXT4-fs (nvme0n1p3): mounting ext3 file system using the ext4 subsystem
l/libstdc++.so.6EXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Quota mode: none.
acorn_install/mbr_record.dataEXT4-fs (nvme0n1p4): mounting ext3 file system using the ext4 subsystem
acorn_installEXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Quota mode: none.
/gui_instr
acorn_install/secure_boot_signed_files.tgz
Running install non-interactively
!!!! This script is being called from a network connection,
!!!! which will be terminated during upgrade script execution.
!!!! Please allow several minutes for system to update and reboot.
!!!! This command will succeed when the CTP is upgraded and ready:
!!!! % nc -vz <CTP IP> 22
Backing up system identity files . . .
[ OK ]
EXT4-fs (nvme0n1p3): unmounting filesystem.
EXT4-fs (nvme0n1p4): unmounting filesystem.
mounting tmpfs at /mnt/ramdisk[ OK ]
***** Image archive not found at /mnt/ramdisk ***
***** Please copEXT4-fs (nvme0n1p3): mounting ext3 file system using the ext4 subsystem
y CTPOS Image arEXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p4): mounting ext3 file system using the ext4 subsystem
***** and then re-execute dualEXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Quota mode: none.
image upgrade ***
!EXT4-fs (nvme0n1p5): mounting ext3 file system using the ext4 subsystem
!! NOTE: ThereEXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Quota mode: none.
is 13570 MB available space in EXT4-fs (nvme0n1p6): mounting ext3 file system using the ext4 subsystem
/mnt/ramdisk(RAMEXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. Quota mode: none.
)
!!! If your flash image .tgz is larger than this, *do not* continue
!!! with this image upgrade. Please contact JTAC for assistance.
Unmounting all partitions of /dev/nvme0n1
Unmounting all partitions of /dev/nvme0n1
Mounting Image1 to / ...[ OK ]
Exiting...
===== Archive Cleanup =====
Unmounting USB storage device
Done...
GPT PMBR size mismatch (6291455 != 62517247) will be corrected by write.
The backup GPT table is not on the end of the device.
Command Output:
Disk /dev/ram0: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram1: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram2: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram3: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram4: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram5: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram6: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram7: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram8: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram9: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram10: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram11: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram12: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram13: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram14: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/ram15: 100 MiB, 104857600 bytes, 204800 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/nvme0n1: 93.16 GiB, 100030242816 bytes, 195371568 sectors
Disk model: SFPC100GM1AG2TO-C-6B-5AD-JUN
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7658124C-0596-4466-AEBD-50DF873AE3A0
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 4095 2048 1M BIOS boot
/dev/nvme0n1p2 4096 413695 409600 200M EFI System
/dev/nvme0n1p3 413696 12701695 12288000 5.9G Linux filesystem
/dev/nvme0n1p4 12701696 13111295 409600 200M Linux filesystem
/dev/nvme0n1p5 13111296 13520895 409600 200M Linux filesystem
/dev/nvme0n1p6 13520896 15568895 2048000 1000M Linux filesystem
/dev/nvme0n1p7 15568896 27856895 12288000 5.9G Linux filesystem
/dev/nvme0n1p8 27856896 28266495 409600 200M Linux filesystem
/dev/nvme0n1p9 28266496 28676095 409600 200M Linux filesystem
/dev/nvme0n1p10 28676096 30724095 2048000 1000M Linux filesystem
/dev/nvme0n1p11 30724096 178180095 147456000 70.3G Linux filesystem
Disk /dev/sda: 29.81 GiB, 32008830976 bytes, 62517248 sectors
Disk model: USB Flash Drive
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 03D08B8F-6A06-4087-8982-BAACD6757C4F
Device Start End Sectors Size Type
/dev/sda1 2048 4095 2048 1M BIOS boot
/dev/sda2 4096 208895 204800 100M EFI System
/dev/sda3 208896 6291422 6082527 2.9G Linux filesystemCopied /root/CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz to /mnt/ramdisk
CTP system software upgrade utility - Version 1.5.0
Found kernel version 6.1.90-yocto-standard, setting KVER to 619
Checking for active menu sessions
Found USB storage device... Mounting
System version is 619
Here is a list of all the found compatible CTP code archive files:
/tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz
Removing old installation residue...
/tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz is the newest archive file...
===== Uncompressing and Extracting Archive =====
Archive file: /tmp/acorn_619_dual_image_upgrade_ctp2k-04_260805.tgz
acorn_install/
acorn_install/install
acorn_install/uefi_partition_files.tgz
acorn_install/sgdisk
acorn_install/libstdc++.so.6
acorn_install/mbr_record.data
acorn_install/gui_instr
acorn_install/secure_boot_signed_files.tgz
Running install non-interactively
!!!! This script is being called from a network connection,
!!!! which will be terminated during upgrade script execution.
!!!! Please allow several minutes for system to update and reboot.
!!!! This command will succeed when the CTP is upgraded and ready:
!!!! % nc -vz <CTP IP> 22
[ OK ]
CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz Image archive file foEXT4-fs (nvme0n1p3): unmounting filesystem.
und at /mnt/ramdEXT4-fs (nvme0n1p4): unmounting filesystem.
isk
EXT4-fs (nvme0n1p5): unmounting filesystem.
Terminating allEXT4-fs (nvme0n1p6): unmounting filesystem.
ssh sessions...
Unmounting all partitions of /dev/nvme0n1
Unmounting Image1...[ OK ]
Unmounting all paEXT4-fs (nvme0n1p3): mounting ext3 file system using the ext4 subsystem
rtitions of /dev/nvme0n1
MountEXT4-fs (nvme0n1p3): mounted filesystem with ordered data mode. Quota mode: none.
ing Image1 to /mnt/ ...EXT4-fs (nvme0n1p4): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p4): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p5): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p5): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p6): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. Quota mode: none.
[ OK ]
==============================================================
System Type : CTP2000
CPU Type : ppf84
Flash Type : NVMe Disk
Currently Running CTPOS : 9.3R2
System State : Running
Total RAM Size : 15879 MB
Free RAM Size : 12906 MB
No. of partitions on /dev/nvme0n1 : 10
CTPOS installed on : Image1 only
Running Image : Image1 (9.3R2-comp-260805-220115-load-260806-071437')
Non-Running Image : Image2 (Empty)
NOTE:
9.3R2-comp-YYMMDD-HHMMSS-load-YYMMDD-HHMMSS decoded as :
9.3R2 : Release Name
comp-YYMMDD-HHMMSS : Root-FS/Kernel compile timestamp
load-YYMMDD-HHMMSS : Image upgrade timestamp
Dual Image on Flash has two logical images :
Image1 - consists Five partitions (1,5,6,7,8)
Image2 - consists Five partitions (1,9,10,11,12)
First partition(bootable) is common to both Image1 and Image2
==============================================================
CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz Image archive file found at /mnt/ramdisk
Verifying CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz archive ...
CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz md5sum - Matched
!!! There is 12906 MB free space available on /mnt/ramdisk(RAM)
*** Upgrade in progress. Please be patient.... ***
***Upgrading Image2 partition wiEXT4-fs (nvme0n1p3): unmounting filesystem.
th CTPOS_9.3R2_pEXT4-fs (nvme0n1p4): unmounting filesystem.
artitions_ctp2k-EXT4-fs (nvme0n1p5): unmounting filesystem.
04_260805.tgz **EXT4-fs (nvme0n1p6): unmounting filesystem.
*
Unmounting all partitions of /dev/nvme0n1
Mounting Image2 EXT4-fs (nvme0n1p7): mounting ext3 file system using the ext4 subsystem
to /mnt/ ...EXT4-fs (nvme0n1p7): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p8): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p8): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p9): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p9): mounted filesystem with ordered data mode. Quota mode: none.
EXT4-fs (nvme0n1p10): mounting ext3 file system using the ext4 subsystem
EXT4-fs (nvme0n1p10): mounted filesystem with ordered data mode. Quota mode: none.
[ OK ]
Extracting CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz to Image2 ...
flash_root.tgz to /mnt/flash_root [ OK ]
flash_home.tgz to /mnt/flash_home [ OK ]
flash_var.tgz to /mnt/flash_var [ OK ]
flash_local.tgz to /mnt/flash_local [ OK ]
[ OK ]
Transferring system identity files . . .
rsync: change_dir "/mnt/restore/var" failed: No such file or directory (2)
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /b/dc-builder/yocto-x86/JUNOS_222_R1_BRANCH/JUNOS_222_R1_BRANCH-x86-64-ovp-WRL8-nfx-3-71/build-nfx-3/x86-64-ovp/bitbake_build/tmp/work/corei7-64-wrs-linux/rsync/3.1.1-r0/rsync-3.1.1/main.c(1165) [sender=3.1.1]
[ FAIL ]
Could not transfer var files
Unmounting Image2...EXT4-fs (nvme0n1p7): unmounting filesystem.
EXT4-fs (nvme0n1p8): unmounting filesystem.
EXT4-fs (nvme0n1p9): unmounting filesystem.
EXT4-fs (nvme0n1p10): unmounting filesystem.
[ OK ]
Updating grub conf files... [ OK ]
Unmounting all partitions of /dev/nvme0n1
*** ***
Upgrading Image2 partition with CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz complete
The system needs to be rebooted
*** ***
*** ***
!!!!!!!Rebooting System...
*** ***
sd 0:0:0:0: [sda] Synchronizing SCSI cache
ACPI: PM: Preparing to enter system sleep state S5
reboot: Restarting system
reboot: machine restartBoot logs will be displayed at this point on the device. However, we are not showing it here.
In the user login prompt, enter the user credentials, and check the version on the device with the command "cmd -v"
ctp_202 login: ctp_cmd
Password:
[ctp_cmd@ctp_202:~ 1]> cmd -v
CTPOS CLI version: 9.3R2 260805
Compile Time: Wed Aug 05 2026 07:35:40 AM
Flash: Dual Image
[ctp_cmd@ctp_202:~ 2]>Upgrading Dual Image through CLI (interactive mode)
The package acorn_310_dual_image_upgrade_ctp2k-04_260805.tgz and CTPOS CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz are required to upgrade CTP2000 Gen4 Series from CTPOS 9.1Rx to CTPOS 9.3R2.
Similarly, the acorn_310_dual_image_upgrade_ctp2k-03_260805.tgz package and CTPOS CTPOS_9.3R2_partitions_ctp2k-03_260805.tgz are required to upgrade CTP2000 Gen3 Series from CTPOS 9.1Rx to CTPOS 9.3R2.
Download the CTP partition file CTPOS_9.3R2_partitions_ctp2k-04_260805.tgz that is available in the Juniper Networks download page at https://support.juniper.net/support/downloads/ for CTPOS 9.3R2 Release.
The following steps illustrate how to manually upgrade a CTPOS 9.3R2 dual image from an existing single image or a dual image using CLI commands.
Upgrading Dual Image through CLI (non-interactive mode)
Once you run upgrade y, the device is upgraded with personality transfer feature, and the script automatically selects the older image to overwrite with the new CTPOS image.
[root@ctp_227:/tmp 5]# upgrade y
CTP system software upgrade utility - Version 1.5.0
Found kernel version 3.14.39ltsi-WR7.0.0.27_standard, setting KVER to 310
Checking for active menu sessions
Found USB storage device... Mounting
System version is 310
Here is a list of all the found compatible CTP code archive files:
/tmp/acorn_310_dual_image_upgrade_ctp2k-04_260805.tgz
Removing old installation residue...
/tmp/acorn_310_dual_image_upgrade_ctp2k-04_260805.tgz is the newest archive file...
===== Uncompressing and Extracting Archive =====
Archive file: /tmp/acorn_310_dual_image_upgrade_ctp2k-04_260805.tgz
acorn_install/
acorn_install/sgdisk
acorn_install/uefi_partition_files.tgz
acorn_install/gui_instr
acorn_install/install
acorn_install/libstdc++.so.6
acorn_install/mbr_record.data
acorn_install/secure_boot_signed_files.tgz
Running install non-interactively
mounting tmpfs at /mnt/ramdisk[ OK ]
CTPOS_partitions file copied from /tmp to /mnt/ramdisk
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!! You are executing in Non-Interactive Mode
!!!! SYSTEM will *REBOOT* automatically once the
!!!! execution completes successfully
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Boot logs will be displayed at this point on the device. However, we are not showing it here.
In the user login prompt, enter the user credentials and check the version on the device with the command "cmd -v"
***** Normal boot up of this flash. *****
ctp_setmod:
ctp_setmod: Checking number of ethernet devices indicates system changes needed!
Starting system message bus: dbus[1097]: Unknown username "avahi" in message bus configuration file
dbus.
iptables: Applying firewall rules: [ OK ]
ip6tables: Applying firewall rules: [ OK ]
Bringing up loopback interface: [ OK ]
Setting 802.1Q VLAN parameters: Set name-type for VLAN subsystem. Should be visible in /proc/net/vlan/config
[ OK ]
Bringing up interface eth0: [ OK ]
Bringing up interface eth0.0: [ OK ]
Bringing up interface eth0.2026: [ OK ]
Bringing up interface eth0.4094: [ OK ]
Bringing up interface eth1.1000: [ OK ]
Bringing up interface eth1.1010: [ OK ]
Starting OpenBSD Secure Shell server: sshd[ OK ]/usr/sbin/sshd already running.
Starting rpcbind daemon...done.
starting statd: done
Starting Advanced Configuration and Power Interface daemon: acpid.
Starting atd: OK
Starting domain name service: namedacpid: starting up with netlink and the input layer
acpid: 0 rules loaded
acpid: waiting for events: event logging is off
.
Starting irqbalance: [ OK ]
starting rsyslogd ... [ OK ]
Starting kea-dhcp4-server: done.
No kdump kernel image found.
Starting ntpd: [ OK ].
Starting fan control daemon: fancontrol... done.
Starting sticky [ OK ]
Starting crond: OK
In boot
Installing IPMI driver... [ OK ]
IPMI device is present [ OK ]
ctp: Installing HDLC kernel driver [ OK ]
ctp: Installing CTP kernel driver [ OK ]
ctp: Installing HDLC FR kernel driver [ OK ]
ctp: Installing HDLC PPP kernel driver [ OK ]
ctp: Installing HDLC RAW kernel driver [ OK ]
ctp: Installing HDLC CISCO kernel driver [ OK ]
ctp: Installing layer-2 bridge kernel module [ OK ]
ctp: Check CTP kernel driver [ OK ]
ctp: Checking for required memory [ OK ]
ctp: Checking for required bios [ OK ]
ctp: Starting CTP daemon: [ OK ]
ctp: Checking fpga for all cards . . . . . . . . . . [ OK ]
Starting snmpd [ OK ]
...................Login banner ........
ctp_227 login: ctp_cmd
Password:
Last login: Mon Jul 27 18:37:29 UTC 2026 from 10.54.240.211 on ssh
[ctp_cmd@ctp_227:~ 1]> cmd -v
CTPOS CLI version: 9.3R2 260805
Compile Time: Wed Aug 05 2026 07:35:40 AM
Flash: Dual Image
[ctp_cmd@ctp_227:~ 2]>