Description

QFX5120-32C | show system uptime Bug | 'show system uptime | display xml' command displays wrong seconds

Symptoms

QFX5120-32C | show system uptime Bug | 'show system uptime | display xml' command displays wrong seconds

 

On Junos and Junos Evolved platforms, post device reboot, when uptime is checked executing the below command, at the top of the hour, the display is shown in "minutes" instead of seconds for 24 hours. After 24 hours it self recovers and displays correct value.

It's a non impacting behaviour.

If the issue is hit below logs or uptime can be observed.

user@device> show system uptime | display xml | match "up-time junos:seconds" | refresh 60    
X:55:50                      <up-time junos:seconds="7140">1:59</up-time>
X:56:50  ---(refreshed at X:56:50 PDT)---
X:56:50                      <up-time junos:seconds="120">2 hrs</up-time> <<<<<this is the issue, it's displaying 120 instead of 7200 (7140+60) >> "120" minutes=120x60= 7,200 seconds, which is correct. 
X:57:50  ---(refreshed at X:57:50 PDT)---
X:57:50                      <up-time junos:seconds="7260">2:01</up-time>
X:53:50  ---(refreshed at Y:53:50 PDT)---
X:53:50                      <up-time junos:seconds="10620">2:57</up-time>
X:54:50  ---(refreshed at Y:54:50 PDT)---
X:54:50                      <up-time junos:seconds="10620">2:57</up-time>
X:55:51  ---(refreshed at Y:55:50 PDT)---
X:55:51                      <up-time junos:seconds="10740">2:59</up-time> <<<<<<< 10740 seconds
X:56:50  ---(refreshed at Y:56:50 PDT)---
X:56:51                      <up-time junos:seconds="180">3 hrs</up-time> <<<<<<<<<<<<<< this is the issue. 180 minutes=180x60= 10,800 seconds, which is correct.


On all Junos and Junos Evolved platforms, after the device reboot, show system uptime command is showing time in minutes instead of seconds for 24 hours.

This issue might be seen if the following conditions are met:
* On all Junos and Junos Evolved platforms
* Device reboot

This issue has been fixed through PR1681656.

 

Solution

This issue has been fixed through PR1681656.

Modification History

2024-03-08 : Article Created