Description

In some corner cases, VMHOST based PTX went into Amnesiac mode after upgrade due to legacy JSU packages in the previous Junos OS were not deleted properly. The customer can use USB media installation to recover the issue.

Symptoms

labroot@jtac-ptx10008-r2005-re0> request system software add /var/tmp/jselective-update-amd64-J16.2-x86-64-20.4R3-S2-J16.2.tgz

Verified jselective-update-amd64-J16.2-x86-64-20.4R3-S2-J16.2 signed by PackageProductionECP256_2022 method ECDSA256+SHA256

Restarting rpd ...

 

 

labroot@jtac-ptx10008-r2005-re0> request system software add /var/tmp/jselective-update-amd64-J16.3-x86-64-20.4R3-S2-J16.3.tgz

Verified jselective-update-amd64-J16.3-x86-64-20.4R3-S2-J16.3 signed by PackageProductionECP256_2022 method ECDSA256+SHA256

Restarting rpd ...

 

labroot@jtac-ptx10008-r2005-re0> request vmhost software add /var/tmp/junos-vmhost-install-ptx-x86-64-22.4R3-S2.11.tgz no-validate reboot

 

 

Trying 10.219.9.200...

Connected to jtac-acs6000-48-r2077.ultralab.juniper.net.

Escape character is '^]'.

 

Type the hot key to suspend the connection: <CTRL>Z

 

 

FreeBSD/amd64 (Amnesiac) (ttyu0)

 

login: Jul 24 08:22:18 pgmd[33682]: PGMD_RPD_SESSION_CONNECT_FAILED: rpd_session_connect() failed: No such file or directory (2). will retry

Jul 24 08:22:19 gkmd[33670]: IKED-PKID socket creation failed

root

Jul 24 08:22:22 login[32679]: login_getclass: unknown class 'junos-login-defaults'

Password:Jul 24 08:22:22 login[32679]: login_getclass: unknown class 'junos-login-defaults'

Jul 24 08:22:23 pgmd[33682]: PGMD_RPD_SESSION_CONNECT_FAILED: rpd_session_connect() failed: No such file or directory (2). will retry

Jul 24 08:22:24 gkmd[33670]: IKED-PKID socket creation failed

 

Last login: Wed Jul 24 02:12:57 on ttyu0

 

 

 

root> show version

Model: ptx10008

Junos: 22.4R3-S2.11

JUNOS Selective Update J16.3 (for: /usr/sbin/rpd /usr/libexec64/rpd) [20.4R3-S2-J16.3]

JUNOS Selective Update J16.2 (for: /usr/sbin/rpd /usr/libexec64/rpd) [20.4R3-S2-J16.2]

JUNOS OS Kernel 64-bit [20240313.333b213_builder_stable_12_224]

JUNOS OS libs [20240313.333b213_builder_stable_12_224]

JUNOS OS runtime [20240313.333b213_builder_stable_12_224]

JUNOS OS time zone information [20240313.333b213_builder_stable_12_224]

JUNOS network stack and utilities [20240510.190651_builder_junos_224_r3_s2]

Solution

JTAC had done the following tests, and confirmed that legacy JSU won't be removed properly after upgrade.

1)  Standard 20.4R3-S2.6 -> 21.4R3-S7.8                  <<<< OK
2)  Standard 20.4R3-S2.6 -> 22.4R3-S2.11                 <<<< OK
3)  20.4R3-S2.6 (with JSU 16.2 and 16.3) -> 21.4R3-S7.8  <<<< failed
4)  20.4R3-S2.6 (with JSU 16.2 and 16.3) -> 22.4R3-S2.11 <<<< failed
5) Remove JSU manually, 20.4R3-S2.6 -> 21.4R3-S7.8       <<<< OK
6) Remove JSU manually, 20.4R3-S2.6 -> 22.4R3-S2.11      <<<< OK

JTAC highly suggested the customer to remove old JSU package and then upgrade the Junos OS.

 

Modification History

2024-07-29 : Article Created