Wired Intelligent Edge

 View Only
last person joined: 2 days ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

the maximum number of telnet session are active

This thread has been viewed 0 times
  • 1.  the maximum number of telnet session are active

    Posted Jun 05, 2015 03:15 AM

    I can not connect to our 8212zl switch by telnet.

    The switch said "the maximum number of telnet sessions are active".
    I did kill session-id by serial console.
    However still I can not connect telnet session.

     

    HP Switch 8212zl (J9091A)

    K.15.16.0008, ROM K.15.30


    #8212zl
    #telnet


  • 2.  RE: the maximum number of telnet session are active

    Posted Jun 05, 2015 03:27 AM

    Did you try SSH? It is preferable to telnet anyway because of security. On Procuve switches it is activated like this:

     

    crypto key generate ssh rsa bits 2048

    ip ssh

    no telnet-server

     



  • 3.  RE: the maximum number of telnet session are active

    Posted Jun 05, 2015 03:39 AM

    Yes, I tried SSH.  But I can not connect to the switch.

     

    "Sorry, the maximum number of sessions are active. Try again later."



  • 4.  RE: the maximum number of telnet session are active

    Posted Jun 05, 2015 06:41 AM

    This has happened to me also a couple of times, and the only solution I have found is to reboot the switch. If this cannot be done easily then I suggest you open a case with HP support.



  • 5.  RE: the maximum number of telnet session are active

    EMPLOYEE
    Posted Jun 05, 2015 10:57 AM

    Is it possible that something on your network is programmatically opening a telnet session to your switch? If you do a "show telnet" or a "show ip ssh" it will give you the IP of the host that is connected.



  • 6.  RE: the maximum number of telnet session are active

    Posted Jun 08, 2015 01:20 AM

    To close the open Telnet sessions, it is necessary to either access the switch over the serial console port, or else reboot.

    By default, ProCurve switches support a total of three open Telnet sessions and do not automatically terminate sessions that were not properly exited.

    When you access the switch through a serial console session, issue the command: “kill” at the prompt. This closes the open Telnet sessions. Next, configure an inactivity timer setting that will serve to automatically close inactive Telnet sessions in the future:

    ProCurve Switch(config)# console inactivity-timer <0-120 minutes>
    ProCurve Switch(config)# write mem

    This will ensure that any Telnet sessions that are inadvertently left open in the future will time out of the switch, and ensure that you are able to establish management access as needed.

     

    Thanks and regards

    Anurag Thottathil

     



  • 7.  RE: the maximum number of telnet session are active

    Posted Jun 09, 2015 09:45 PM

    I killed telnet session by serial console, and already configured console idle-timeout.

     

    This problem may arise from firmware K15.16.0008.

     

    show session-list

    Session Activity

    Source IP Selection: Outgoing Interface

    --------------------------------------------------------
    Session : ** 1
    Privilege: Manager
    From : Console
    To :

     

    --

    show config

    ...

    console idle-timeout 3600
    console idle-timeout serial-usb 3600
    ...

     

     



  • 8.  RE: the maximum number of telnet session are active

    Posted Jul 26, 2018 01:16 PM

    Hi,

    I have the same issue with an HP Aruba 2530G POE switch.  I get the same error even trying to connect to the console port so is my only recourse rebooting the switch?

    Thanks in advance.



  • 9.  RE: the maximum number of telnet session are active

    Posted Jul 27, 2018 06:08 PM

    Just in case someone else runs into this problem:  Rebooting the switch cleared it up.  This is a production switch so I had to come in early to do it but I can get in now.