- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Collisions on Procurve Switches
Switches, Hubs, and Modems
1753883
Members
7706
Online
108809
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
тАО11-11-2003 01:18 PM
тАО11-11-2003 01:18 PM
Collisions on Procurve Switches
We are experiencing excess collisions, late collisions and deferred Tx packets when connecting IP radio's and Cisco routers to up 5372XL and HP 2626 or 2560 Procuves.
The two brands of IP radio's operate a fixed speeds of 100FD and 10HD. If the Procurve switches ports forced to match these speeds the ports do not even enable(no link up).
If the Procurve ports are set to Auto, then the 100FD connection is detected as 100HD and there are collisions. The 10HD port is detected as 10HD but also has collisions and many Deferred Tx errors.
Likewise with a Cisco 1751 router, the router is set to 100HD and the switch is set to 100HD but there is still alot of collisions and late collision on the procurve port and CRC errors at the cisco end.
I understand the problems with devices that do not auto negotiate when connected to a Procurve Port that is set to auto, but i dont understand why if you force the Procurve port to a set speed why it does not fix the problem.
Any help would be appreciated.
The two brands of IP radio's operate a fixed speeds of 100FD and 10HD. If the Procurve switches ports forced to match these speeds the ports do not even enable(no link up).
If the Procurve ports are set to Auto, then the 100FD connection is detected as 100HD and there are collisions. The 10HD port is detected as 10HD but also has collisions and many Deferred Tx errors.
Likewise with a Cisco 1751 router, the router is set to 100HD and the switch is set to 100HD but there is still alot of collisions and late collision on the procurve port and CRC errors at the cisco end.
I understand the problems with devices that do not auto negotiate when connected to a Procurve Port that is set to auto, but i dont understand why if you force the Procurve port to a set speed why it does not fix the problem.
Any help would be appreciated.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2003 02:04 AM
тАО11-12-2003 02:04 AM
Re: Collisions on Procurve Switches
I'm not sure about the IP Radios but you say:
"Likewise with a Cisco 1751 router, the router is set to 100HD and the switch is set to 100HD but there is still alot of collisions and late collision on the procurve port and CRC errors at the cisco end."
CRC errors on the Cisco side are usually caused by the switch being in Half duplex while the Cisco is in Full duplex. You need to set the switch to Full Duplex or recheck the Cisco cause it seems to be in full duplex mode. Perhaps it has more than one Ethernet interface and you have been looking at the wrong one?
Are you sure you have CAT 5 cables? Are you sure they are good?
Ron
"Likewise with a Cisco 1751 router, the router is set to 100HD and the switch is set to 100HD but there is still alot of collisions and late collision on the procurve port and CRC errors at the cisco end."
CRC errors on the Cisco side are usually caused by the switch being in Half duplex while the Cisco is in Full duplex. You need to set the switch to Full Duplex or recheck the Cisco cause it seems to be in full duplex mode. Perhaps it has more than one Ethernet interface and you have been looking at the wrong one?
Are you sure you have CAT 5 cables? Are you sure they are good?
Ron
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-12-2003 11:24 PM
тАО11-12-2003 11:24 PM
Re: Collisions on Procurve Switches
I'm assuming you've already tested the patch cables and they are OK - in particular, no split pairs.
I too don't understand why locking both the switch and router at FDX doesn't fix the CRC errors.
However, if the links on the far side of the device attached to the switch are full-duplex, and the link between the switch and that device is half-duplex, collisions are inevitable. There's two-way traffic trying to cross a one-way link.
I too don't understand why locking both the switch and router at FDX doesn't fix the CRC errors.
However, if the links on the far side of the device attached to the switch are full-duplex, and the link between the switch and that device is half-duplex, collisions are inevitable. There's two-way traffic trying to cross a one-way link.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-14-2003 02:28 AM
тАО11-14-2003 02:28 AM
Re: Collisions on Procurve Switches
Hello Anthony,
On explanation for the link not coming is when you fix the ports on the Procurve gear is that on the models you mention, there is a feature called Auto-MDI/X. It enables you to connect f.e. switch to switch using straight cable. However, when you change the port setting on a Procurve with auto-MDI/X, the feature is disabled. You would need a true cross-over cable to establish a link.
My 2 cents; always use a cross-over cable for mdi-x to mdi-x or mdi to mdi links.
The Procurve falling back to HDx when the port is in Auto and a 100FDx device is connected to that Auto port is per the auto-negotiation standard. Only use the combination Auto<>Auto for best performance when you wish to rely on automation.
Do you fabricate your UTP cables yourself?
Goodluck!
On explanation for the link not coming is when you fix the ports on the Procurve gear is that on the models you mention, there is a feature called Auto-MDI/X. It enables you to connect f.e. switch to switch using straight cable. However, when you change the port setting on a Procurve with auto-MDI/X, the feature is disabled. You would need a true cross-over cable to establish a link.
My 2 cents; always use a cross-over cable for mdi-x to mdi-x or mdi to mdi links.
The Procurve falling back to HDx when the port is in Auto and a 100FDx device is connected to that Auto port is per the auto-negotiation standard. Only use the combination Auto<>Auto for best performance when you wish to rely on automation.
Do you fabricate your UTP cables yourself?
Goodluck!
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