- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: High collision or drop rate
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
Discussions
Discussions
Forums
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
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
тАО08-10-2008 11:49 PM
тАО08-10-2008 11:49 PM
High collision or drop rate
We have three ProCurve Switches in our organisation. 5406zl, 3500yl and 2900-48G we originally just had the 5406 and 3500 but just installed the 2900-48G in our server rack.
Between the server rack 2900-48G and 5406zl we have a 4Gb trunk (Trk2) which consists of two 1GB SX-LC fiber and two 1GB CAT6, we then have between to 5406zl and 3500yl a 3Gb trunk (Trk1) which consists of two 1GB SX-LC fiber and one CAT6.
Since introducing trunk 2 we keep getting High collision or drop rate warnings on all three switches.
Configurations are as follows;
5406zl (MAIN 3RD FLOOR SWITCH)
Running configuration:
; J8697A Configuration Editor; Created on release #K.13.23
hostname "ProCurve Switch 5406zl"
web-management management-url ""
module 1 type J8702A
module 2 type J8702A
module 3 type J8702A
module 4 type J8702A
module 5 type J8705A
trunk E20,E23-E24 Trk1 Trunk
trunk A1-A2,E21-E22 Trk2 Trunk
ip default-gateway 192.168.35.41
snmp-server community "public" Unrestricted
snmp-server host 192.168.35.61 "public"
vlan 1
name "DEFAULT_VLAN"
untagged A3-A24,B1-B24,C1-C24,D1-D17,E1-E19
ip address 192.168.35.32 255.255.255.0
tagged Trk1-Trk2
no untagged D18-D24
exit
vlan 2
name "Wireless"
untagged D18-D24
tagged Trk1-Trk2
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
no ip ssh
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
3500YL (GROUND FLOOR SWITCH)
Running configuration:
; J8693A Configuration Editor; Created on release #K.13.23
hostname "ProCurve Switch 3500yl-48G"
web-management management-url ""
module 1 type J86yyA
module 2 type J86xxA
trunk 46-48 Trk1 Trunk
ip default-gateway 192.168.35.41
snmp-server community "public" Unrestricted
snmp-server host 192.168.35.61 "public"
vlan 1
name "DEFAULT_VLAN"
untagged 1-42
ip address 192.168.35.33 255.255.255.0
tagged Trk1
no untagged 43-45
exit
vlan 2
name "Wireless"
untagged 43-45
tagged Trk1
no ip address
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
no ip ssh
spanning-tree Trk1 priority 4
2900-48G (SERVER RACK SWITCH)
Running configuration:
; J9050A Configuration Editor; Created on release #T.13.23
hostname "ProCurve Switch 2900-48G"
snmp-server contact "Mark Hodge"
web-management management-url ""
module 1 type J86yyA
module 2 type J86xxA
module 3 type J90XXA
trunk 45-48 Trk2 Trunk
ip default-gateway 192.168.35.41
snmp-server community "public" Unrestricted
snmp-server host 192.168.35.61 "public"
vlan 1
name "DEFAULT_VLAN"
untagged 1-44,A1-A4
ip address 192.168.35.31 255.255.255.0
tagged Trk2
exit
fault-finder bad-driver sensitivity high
fault-finder bad-transceiver sensitivity high
fault-finder bad-cable sensitivity high
fault-finder too-long-cable sensitivity high
fault-finder over-bandwidth sensitivity high
fault-finder broadcast-storm sensitivity high
fault-finder loss-of-link sensitivity high
fault-finder duplex-mismatch-HDx sensitivity high
fault-finder duplex-mismatch-FDx sensitivity high
no ip ssh
spanning-tree Trk2 priority 4
I hope someone can advise on a solution as this only seems to have occurred since we introduced the 2900-48G and added the Trunk2.
Thanks,
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 02:13 AM
тАО08-11-2008 02:13 AM
Re: High collision or drop rate
- I can see Trunk2 on the 5400 has 4 Ports, where in the 2900 has only 3 Ports ??? if you need only 3 ports, then remove the Unnecessary port from Trunk2 on the 5400.
- Since the 5400 is your main Switch, i advice you to make it Root for Spanning-Tree, just run this command on the 5400:
Sw(config)#span priority 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 02:17 AM
тАО08-11-2008 02:17 AM
Re: High collision or drop rate
trunk 45-48 Trk2 Trunk
Regards,
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 02:41 AM
тАО08-11-2008 02:41 AM
Re: High collision or drop rate
Make sure you enable Spanning-Tree on all the switches, and make the 5400 is the Root one,
Then check if you still getting the same warnings.
Good Luck !!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 02:49 AM
тАО08-11-2008 02:49 AM
Re: High collision or drop rate
http://cdn.procurve.com/training/Manuals/3500-5400-6200-8200-MCG-Jan08-12-PortTrunk.pdf
Trunking can't be done by using more than one media type in a port trunk group.
And you are using different media in each trunk.
Good Luck !!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 02:53 AM
тАО08-11-2008 02:53 AM
Re: High collision or drop rate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 03:34 AM
тАО08-11-2008 03:34 AM
Re: High collision or drop rate
You are using Fiber and Copper for Trunk1 and for Trunk2, and Trunks accept same Media.
For test, do the following:
For Trunk1: use ONLY 2 ports, 1GB SX-LC fiber
For Trunk2: use ONLY 2 ports, 1GB SX-LC fibre
Then connect Trunk1 and Trunk2 and see your network behavior.
Good Luck !!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 03:53 AM
тАО08-11-2008 03:53 AM
Re: High collision or drop rate
Regards,
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 04:22 AM
тАО08-11-2008 04:22 AM
Re: High collision or drop rate
So for does that rule carry over to Trunks without LACP enabled?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-11-2008 07:17 AM
тАО08-11-2008 07:17 AM
Re: High collision or drop rate
for successfull working trunk group (trunk or lacp)ports must be same-speed and same media type
cenk