This article explains the possible reason of delay/latency in command execution on the CLI of the Junos device allthough the CPU appears normal.
Delay of a few seconds while executing the command via ssh access or console access. The delay could be constant or random depending on the cause of the delay.
If the delay is random in command execution, then it could be related to high CPU or a memory problem. Check for the CPU/memory utilization on the device using the following commands:
show chassis routing-engineshow system process extensive
If the authentication is set to tacacs/tacplus and tacacs/tacplus server is configured but not reachable.
set system tacplus server xx.xx.xx.xx
If the system accounting is enabled with tacplus server.
system accounting destination tacplus server xx.xx.xx.xx
Confirm if the source address for the tacplus server is correct
set system tacplus-server xx.xx.xx.xx source-address xx.xx.xx.xx
Check for any tacacs error in the logs
Aug 9 21:27:56.100 Device mgd[27846]: UI_TACPLUS_ERROR: TACACS+ failure: TACACS+ server returned status as 'error' in the accounting reply Aug 9 21:28:10.902 Device mgd[27859]: UI_TACPLUS_ERROR: TACACS+ failure: TACACS+ server returned status as 'error' in the accounting reply Aug 9 21:28:21.373 Device mgd[27863]: UI_TACPLUS_ERROR: TACACS+ failure: TACACS+ server returned status as 'error' in the accounting reply
If the cause is high CPU/memory utilization, then troubleshoot the underlying cause to resolve the issue.
If the cause is tacplus, then make sure the tacplus servers are reachable.
For more details on tacplus configuration, refer to the technical documentation on TACACS+ Authentication