- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- HP 5300 Went down
Switches, Hubs, and Modems
1753512
Members
5230
Online
108795
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2007 03:53 AM
тАО05-14-2007 03:53 AM
HP 5300 Went down
Hi to everyone,
I had this problem today on a customer site:
I was trying to connect to the core hp5300 switch.
I get this message back: "sorry, the maximum number of active telnet session.....plese try again later".
I was also unable to connect to the 5300 via console cable.
After 2 hours that i was trying to connect to the switch, the device reboot itself.
You can find the "sh logg" output after the problem. anyone has experienced the same problem?
I had this problem today on a customer site:
I was trying to connect to the core hp5300 switch.
I get this message back: "sorry, the maximum number of active telnet session.....plese try again later".
I was also unable to connect to the 5300 via console cable.
After 2 hours that i was trying to connect to the switch, the device reboot itself.
You can find the "sh logg" output after the problem. anyone has experienced the same problem?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2007 08:26 AM
тАО05-14-2007 08:26 AM
Re: HP 5300 Went down
Hy there,
I saw something funny in you're log,i am the type who like to put the dot' on my I, you're date on HP 5300 is 05/29/90 06:49:01, you could have a problem hardware?
I saw something funny in you're log,i am the type who like to put the dot' on my I, you're date on HP 5300 is 05/29/90 06:49:01, you could have a problem hardware?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-14-2007 04:02 PM
тАО05-14-2007 04:02 PM
Re: HP 5300 Went down
Hi
You have to visit this switch physically and connect by console cable then you can run:
Switch#show telnet
then you will get all the telnet sessions ended improperly and you can use the command:
Switch#kill
Also i have 2 advices for you:
1- Instruct whoever telnet to the switch to terminate his session properly by using exit command or ctrl+z
2- Issue the following command to any ProCurve switch you see in your life :)
Switch(config)#console inactivity-timer 15
And this will end any session after 15 minutes (you can change), and of course you need to restart the switch after that.
COMMENT:
--------
Why ProCurve not like any other vendor keep this command enabled by default for any value, because nobody pay attention to that.
Good Luck !!!
You have to visit this switch physically and connect by console cable then you can run:
Switch#show telnet
then you will get all the telnet sessions ended improperly and you can use the command:
Switch#kill
Also i have 2 advices for you:
1- Instruct whoever telnet to the switch to terminate his session properly by using exit command or ctrl+z
2- Issue the following command to any ProCurve switch you see in your life :)
Switch(config)#console inactivity-timer 15
And this will end any session after 15 minutes (you can change), and of course you need to restart the switch after that.
COMMENT:
--------
Why ProCurve not like any other vendor keep this command enabled by default for any value, because nobody pay attention to that.
Good Luck !!!
Science for Everyone
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP