- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Ethernet culprit? Telnet/FTP slow response/timout ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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-14-2005 06:38 PM
11-14-2005 06:38 PM
Ethernet culprit? Telnet/FTP slow response/timout many time.
One of our lab server rp5470 ethernet is behaving strangly.
When I try to telnet / ftp across the network getting very slow respond and some time timeout.
Any pointer on this issue. How can I isolate problem.
Regards,
Rajesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2005 06:43 PM
11-14-2005 06:43 PM
Re: Ethernet culprit? Telnet/FTP slow response/timout many time.
What are the network card type it is having?
What is the speed setting in the card and switch side?
Sometime auto-negotiation on either end could cause similar problems. Try to fix it one by one like this.
1. Change card speed to 100FD or 10FD as supported by card.
2. Set switch port also to same as of the lan card.( Auto Negotiation shall not be there in both switch port as well as NIC of the server)
3. Monitor network utilization of the server, if this is allready heavily used. Use Glance Plus for the same.
Update here accordingly.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2005 07:12 PM
11-14-2005 07:12 PM
Re: Ethernet culprit? Telnet/FTP slow response/timout many time.
some questions:
what says "netstat -s", lanadmin -> lan -> display.
Can you ping your default gateway from the UX Machine?
What are the duplex/speed setting under lanadmin and on the switch?
hth
Patrick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2005 08:27 PM
11-14-2005 08:27 PM
Re: Ethernet culprit? Telnet/FTP slow response/timout many time.
try this:
telnet hostname
then:
telnet ipaddress
If there is a significant differential in speed, you've boxed the problem into DNS. /etc/resolv.conf things like that.
Also:
lanscan
lanadmin -x 0
Change zero to the interface you are really connecting to.
You should see full duplex 100 BaseT at minimum. Report any anomalies.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2005 09:28 PM
11-14-2005 09:28 PM
Re: Ethernet culprit? Telnet/FTP slow response/timout many time.
i) Taking time to resolve hostname -> ip-address
ii) Routing settings. Check as,
traceroute
how much it is taking
iii) network cable problem
iv) Too many process running by occupying more system resource(s) like cpu and memory
v) file system usage on server
hth.