Description

There are conditions where SRX becomes very unresponsive for both console and SSH. It appears to be "High CPU" but no counter shows it high. The device may not even be connected to the network and no traffic is going through but still the device is showing very sluggish response. 

This article will attempt to explain one of those situations and how to resolve the issue.

Symptoms

Check to see if the following configuration is present

system {
    accounting {
        events [ login change-log interactive-commands ];
        destination {
            tacplus {
                server {
                    172.30.3.15 {
                        port 49;
                        source-address 172.30.1.25;
                    }
                }
            }
        }
    }
}

If it is there then make sure there is connectivity between the SRX and TacPlus server.

To verify please look for the following log message in the "messages log";
efwa32-manage-01a mgd[2220]: UI_TACPLUS_ERROR: TACACS+ failure: connect: timed out
If the above conditions match, then the issue is most likely a known issue.

 

Solution

Workaround:
===========

There are two possible solutions/workarounds:

  1. Deactivate the "system accounting" stanza.
  2. Restore the connectivity between the SRX and TacPlus server.
 

Modification History

2024-09-02: minor non tech changes

Can be moved to ​ ‘[Archive]’ . Not much relevant now .