HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Slow FTP FCS/Inbound errors
Operating System - HP-UX
1832856
Members
3125
Online
110047
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
Forums
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
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
01-09-2003 08:05 AM
01-09-2003 08:05 AM
Slow FTP FCS/Inbound errors
I'm trying solve a slow FTP tranfer rate problem on my 11.0 rp5450.
- all transfers tested are on local IP segment.
- I 'hardcoded' 100mb full duplex in the NIC and on the hub
- I'm still getting FCS errors and inbound errors while 'getting' files.
lanadmin reports the following:
icgsva1:/pkg/qpk> lanadmin -g mibstats 0
LAN INTERFACE STATUS DISPLAY
Thu, Jan 9,2003 10:57:12
PPA Number = 0
Description = lan0 Hewlett-Packard 10/100 TX Full-Duplex Man
ual TT = 1500
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e06a63c
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 119276203
Inbound Octets = 2437396
Inbound Unicast Packets = 2193
Inbound Non-Unicast Packets = 1813
Inbound Discards = 3
Inbound Errors = 238
Inbound Unknown Protocols = 1478
Outbound Octets = 113501
Outbound Unicast Packets = 1707
Outbound Non-Unicast Packets = 21
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367
Ethernet-like Statistics Group
Index = 1
Alignment Errors = 1
FCS Errors = 238
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0
Advice?
- all transfers tested are on local IP segment.
- I 'hardcoded' 100mb full duplex in the NIC and on the hub
- I'm still getting FCS errors and inbound errors while 'getting' files.
lanadmin reports the following:
icgsva1:/pkg/qpk> lanadmin -g mibstats 0
LAN INTERFACE STATUS DISPLAY
Thu, Jan 9,2003 10:57:12
PPA Number = 0
Description = lan0 Hewlett-Packard 10/100 TX Full-Duplex Man
ual TT = 1500
Type (value) = ethernet-csmacd(6)
MTU Size = 1500
Speed = 100000000
Station Address = 0x306e06a63c
Administration Status (value) = up(1)
Operation Status (value) = up(1)
Last Change = 119276203
Inbound Octets = 2437396
Inbound Unicast Packets = 2193
Inbound Non-Unicast Packets = 1813
Inbound Discards = 3
Inbound Errors = 238
Inbound Unknown Protocols = 1478
Outbound Octets = 113501
Outbound Unicast Packets = 1707
Outbound Non-Unicast Packets = 21
Outbound Discards = 0
Outbound Errors = 0
Outbound Queue Length = 0
Specific = 655367
Ethernet-like Statistics Group
Index = 1
Alignment Errors = 1
FCS Errors = 238
Single Collision Frames = 0
Multiple Collision Frames = 0
Deferred Transmissions = 0
Late Collisions = 0
Excessive Collisions = 0
Internal MAC Transmit Errors = 0
Carrier Sense Errors = 0
Frames Too Long = 0
Internal MAC Receive Errors = 0
Advice?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2003 09:09 AM
01-09-2003 09:09 AM
Re: Slow FTP FCS/Inbound errors
You have a duplex mismatch. If you set the NIC to 100 Full you have to set the corresponding switch port to 100 Full too. Autonegotiate will not work if one side has been manually set. (Actually it works with the speed but it always sets the duplex to Half which is what the RFC tells it to do don't ask me why.)
Ron
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2003 10:00 AM
01-09-2003 10:00 AM
Re: Slow FTP FCS/Inbound errors
Problem solved..... it was as simple as a bad cat 5 cable.
My 11 hour file transfer went to 6.2 minutes.
This newbie to UX became somewhat proficient in lanadmin, though!
Thanks!
My 11 hour file transfer went to 6.2 minutes.
This newbie to UX became somewhat proficient in lanadmin, though!
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2003 11:06 AM
01-10-2003 11:06 AM
Re: Slow FTP FCS/Inbound errors
glad to see you found the trouble. one minor nit though - if it does full duplex, it ain't a hub, its a switch. a hub is a half-duplex only device where all the attached nodes share the same bandwidth. any one node connected to the hub can see traffic destined for any other node.
a switch is a device that does traffic isolation. traffic between A and B will not (generally) be viewable by C, and will not share bandwidht with traffic between C and D. switches can operatin in half duplex like a hub, or in full-duplex.
a switch is a device that does traffic isolation. traffic between A and B will not (generally) be viewable by C, and will not share bandwidht with traffic between C and D. switches can operatin in half duplex like a hub, or in full-duplex.
there is no rest for the wicked yet the virtuous have no pillows
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP