Aruba & ProVision-based
cancel
Showing results for 
Search instead for 
Did you mean: 

SSH session does not time out - console inactivity log message

 
SOLVED
Go to solution

SSH session does not time out - console inactivity log message

Can anyone tell me why I'm getting the following log messages?  I have three Procurve 3500yl switches on firmware K.16.02.0022m that have started spitting this out about every hour.  They did not exhibit this behavior before Friday for some reason.  I did make minor changes to their configurations, but did not touch the idle timeout or do any file transfers.  I don't see where there is a file transfer in progress either.  One of the switches was just rebooted before beginning to make the log entries.

I appreciate your attention, please let me know if I have not included some piece of info that will assist in resolving this.

I 03/05/18 10:46:57 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 09:46:57 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 08:46:57 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 08:21:38 04910 ntp: All the NTP server associations reset.
I 03/05/18 07:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
W 03/05/18 07:35:25 00850 dhcp-snoop: backplane: Server 0.0.0.0 packet received
            on untrusted port 11 dropped
I 03/05/18 06:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 05:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 04:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 03:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 03:34:27 04910 ntp: All the NTP server associations reset.
I 03/05/18 02:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 01:46:56 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.
I 03/05/18 00:46:55 00166 update: Console inactivity timer is reset as the file
            transfer is in progress.

I have the console idel timeout set

Running configuration:

; J8693A Configuration Editor; Created on release #K.16.02.0022m
; Ver #10:08.03.81.30.02.34.59.2c.6b.ff.f7.fc.7f.ff.3f.ef:26
hostname "hp3500-kb3-1"
module 1 type j86yya
module 2 type j86xxa
module 3 type j8694a
connection-rate-filter sensitivity low
console idle-timeout 3600
console idle-timeout serial-usb 3600

hp3500-kb3-1# show telnet

 Telnet Activity

 Source IP Selection: Outgoing Interface

 --------------------------------------------------------
 Session  :     1
 Privilege: Superuser
 From     : Console
 To       :
 --------------------------------------------------------
 Session  : **  2
 Privilege: Manager
 From     : <redacted>
 To       :

 

hp3500-kb3-1# show ip ssh

  SSH Enabled     : Yes                 Secure Copy Enabled : Yes
  TCP Port Number : 22                  Timeout (sec)       : 120
  Host Key Type   : RSA                 Host Key Size       : 2048

  Ciphers : aes256-ctr,aes256-cbc,rijndael-cbc@lysator.liu.se,aes192-ctr,
            aes192-cbc,aes128-ctr,aes128-cbc,3des-cbc
  MACs    : hmac-sha1-96,hmac-md5,hmac-sha1,hmac-md5-96

  Ses Type     | Source IP                                      Port
  --- -------- + ---------------------------------------------- -----
  1   console  |
  2   ssh      | <redacted>                                  20532
  3   inactive |
  4   inactive |
  5   inactive |
  6   inactive |

1 REPLY 1
Highlighted
Solution

Re: SSH session does not time out - console inactivity log message

Weirdly the issue went away.

Perhaps it was due to making sure that any serial console sessions were explicitly logged out and killing console sessions.  I would swear I tried that and still got the log message later.