- Community Home
- >
- Networking
- >
- Legacy
- >
- Switches, Hubs, Modems
- >
- Re: dhcp-snooping and arp-protection trusted ports...
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
тАО06-17-2009 08:46 AM
тАО06-17-2009 08:46 AM
dhcp-snooping and arp-protection trusted ports versus LACP
I configure our switches so that a set of uplink ports are enabled for LACP, and also trusted for dhcp-snooping. The idea being to have a standard configuration, where we have the option to connect multiple ports to make a trunk.
Of course the problem is, when one makes the uplink into a LACP trunk, the original ports "disappear" as trusted port, and are replaced by a "Dyn1" port which is untrusted.
Is there any way around this other than to go back and set the Dyn1 port as trusted retrospectively. Is it possible to automatically trust any and all LACP (dynamic-created) trunks? Maybe a stupid configuration in some respects, but our regular edge ports use mac-based/radius port-access control, so lacp is not possible or an issue for them.
I guess the only obvious option I can think of is to define static LACP trunks on the specific ports...
- Tags:
- DHCP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-17-2009 09:07 AM
тАО06-17-2009 09:07 AM
Re: dhcp-snooping and arp-protection trusted ports versus LACP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-06-2013 12:15 AM - edited тАО06-06-2013 12:16 AM
тАО06-06-2013 12:15 AM - edited тАО06-06-2013 12:16 AM
Re: dhcp-snooping and arp-protection trusted ports versus LACP
I am bringing things back from the dead today .....
Dynamic LACP sounds great in theory then all the limitations kick in
must use GVRP for VLAN trunks
can't use DHCP Snooping
can't use ARP Protection
can't use anything that relys on knowing the TRKX number as the DYNX is Dyanmic .. hence the name
many more ...
Pros
Makes the configs soooo simple for trunks
interface X
name "My Interface"
lacp active
exit