Blog

Remote Infrastructure Management – Juniper SRX 210 – SSH connection disconnected leaving stale connections

Tags: Juniper router managementremote infrastructure managementrouter setupswitch management

Scenario:

As a part of our remote infrastructure management services, while trying to configure a Juniper Series (JunOS which is based on FreeBSD) you may get an error saying a similar message to below

root@srx210> configure             
Entering configuration mode
Users currently editing the configuration:
  root terminal p0 (pid 60524) on since 2016-08-13 01:31:42 EDT, idle 00:10:01
      [edit]
The configuration has been changed but not committed

[edit]
root@srx210# 

This is because you may have an SSH connection which could have disconnected while in the configuration mode. You can disconnect the other session other than yours, by doing these.

root@srx210# status 
Users currently editing the configuration:
  root terminal p0 (pid 60524) on since 2016-08-13 01:31:42 EDT, idle 00:12:45
      [edit]
  root terminal p1 (pid 60638) on since 2016-08-13 01:45:15 EDT
      [edit]

[edit]
root@srx210#

You can see that the current connection is infact the second one since there is no idle time while the other is having an idle time of 12:45 mins.

To disconnect execute the below command, and it may take around 30 secs to 1 min to finish. So be patient 🙂

root@srx210# run request system logout pid 60524    

[edit]
root@srx210# status                                 
Users currently editing the configuration:
  root terminal p1 (pid 60638) on since 2016-08-13 01:45:15 EDT
      [edit]

[edit]

However don’t forget to view the changes before you commit.

root@srx210# show | compare
[edit security address-book global]
     address mail.domains.com { ... }
+    address centosweb 192.168.1.54/32;

[edit]
root@srx210# 

If you don’t want to commmit, issue a rollback, as in below.

root@srx210# rollback 0 
load complete

[edit]
root@srx210# show | compare    

[edit]

More detailed explanation of the issue and the solutions are in Juniper KB also. Please refer How to disconnect JUNOS TTY sessions with a TTY ID of “qX” and Securing console using log-out-on-disconnect

Category : General, Troubleshooting