- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- trunk problem
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
тАО07-24-2010 11:36 PM
тАО07-24-2010 11:36 PM
i have 8206zl with two 24-Port Mini-GBIC Module nd on port a1 a3 a5 nd b1 b3 b5 i have Gigabit 1000Base-T mini-GBIC nd configure a1 nd b1 as trunk static nd the same with a3 nd b3 nd a5 nd b5 when i connect 2610 via port 25 nd 26 to any of them no problem but when i connect another device utm sonicwall every thing down but when i connet it via single port it work good although i config sonicwall x0 nd x1 to be trunk don't know why this happen .
when i open syslog i found b3 clocked with stp wheni connect sonicwall to port a3 nd b3 nd the work as atrunk i'm using rstp on my network
another thing Server-to-Switch Trunking in Procurve switch how this work or how i configer it or just config atrunk nd on other side teaming on server side
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-25-2010 03:36 AM
тАО07-25-2010 03:36 AM
SolutionBe aware thet that the HP trunk is a HP proprietary protocol and will not work well with non HP/Procurve switches.
To set up trunks with 3rd party devices i would use LACP instead.
Regarding server to switch trunking, it depends on the server teaming software.
But in most cases, leaving the ports as LACP passive mode (default configuration) usually works. The server acs as the active side and set up the trunk.
Other teaming software might require you to set up static LACP trunk.
Check the documantation of you server software.
Tore
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-27-2010 10:38 AM
тАО07-27-2010 10:38 AM
Re: trunk problem
really thnx u for ur help :) it's working now
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-30-2010 08:04 AM
тАО07-30-2010 08:04 AM
Re: trunk problem
i do what u told me nd us lacp ieee 802.3.ad the same problem everything goes down nd i attached a picture of error message that happen when i connect the utm to my core don't know what's the problem plz chick it nd advise what should i do
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2010 02:19 AM
тАО08-03-2010 02:19 AM
Re: trunk problem
And sorry for the late response.
What kind of configuration options do you have on the sonic wall side for link aggregation?
Could you extract a show tech all from the switch and attach here? Or just the config?
The errors indicate layer 1 issues, and could indicate issues with the trunk.
Is it only on 1 of the ports you get errors? Or just 1.
What does the command "show trunk" give you?
Tore