- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- HP4000m and 2524 cannot telnet in half the time
Switches, Hubs, and Modems
1753652
Members
5527
Online
108798
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
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
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
11-30-2005 07:08 AM
11-30-2005 07:08 AM
HP4000m and 2524 cannot telnet in half the time
Hi,
I've seen some talk about users who cannot Telnet into their switches from time to time and this is something I've dealt with for over a year. Over Thanksgiving, I updated all 31 of our HP switches on campus and everything is running either 9_22 or 5_34 depending on the model.
I'm plugged into an 8000m via ethernet (not console cable) and the 4000m I am trying to Telnet to is 2 switches away connected by fiber to a 4000m, then out of that switch with more fiber to the final switch. half the time I can telnet, other times it just sits at the dos prompt and then times out.
we found a work around but it seems silly to have to do this every time.
workaround: ping the switch until it replies, then 100% of the time I can Telnet into the switch, type my user and pw in and voila the main menu.
I have also set ABC on IP_IPX on most of my switches because I suspect the Telnet logins timing out due to traffic on the network. ABC at 30% doesnt seem to be doing the trick in respect to Telnet, and I am running the latest C_09_22.swi firmware.
Does anyone know of any other features I should set in the config, or what the cause of the Telnet problem is? I really don't feel I should have to ping the switch in order to then run Telnet to get into it. In fact, pinging doesnt reply sometimes either, I'm not sure if this is network traffic, or switches being stubborn.
ps. I am not using any form of PCM or Toptools, we found that program to be a huge resource hog on the computer and it never really showed us anything useful as far as internal traffic patterns go, but I digress.
Thanks for your help, sorry to post something that was talked about already, but I couldnt find any recent threads to help me find a solution.
-Walter
I've seen some talk about users who cannot Telnet into their switches from time to time and this is something I've dealt with for over a year. Over Thanksgiving, I updated all 31 of our HP switches on campus and everything is running either 9_22 or 5_34 depending on the model.
I'm plugged into an 8000m via ethernet (not console cable) and the 4000m I am trying to Telnet to is 2 switches away connected by fiber to a 4000m, then out of that switch with more fiber to the final switch. half the time I can telnet, other times it just sits at the dos prompt and then times out.
we found a work around but it seems silly to have to do this every time.
workaround: ping the switch until it replies, then 100% of the time I can Telnet into the switch, type my user and pw in and voila the main menu.
I have also set ABC on IP_IPX on most of my switches because I suspect the Telnet logins timing out due to traffic on the network. ABC at 30% doesnt seem to be doing the trick in respect to Telnet, and I am running the latest C_09_22.swi firmware.
Does anyone know of any other features I should set in the config, or what the cause of the Telnet problem is? I really don't feel I should have to ping the switch in order to then run Telnet to get into it. In fact, pinging doesnt reply sometimes either, I'm not sure if this is network traffic, or switches being stubborn.
ps. I am not using any form of PCM or Toptools, we found that program to be a huge resource hog on the computer and it never really showed us anything useful as far as internal traffic patterns go, but I digress.
Thanks for your help, sorry to post something that was talked about already, but I couldnt find any recent threads to help me find a solution.
-Walter
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