- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- How to deal with dhcpv6-snooping and replaced devi...
-
- Forums
-
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Middle East
- HPE Blog, Russia
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
-
Blogs
- Advancing Life & Work
- Advantage EX
- Alliances
- Around the Storage Block
- HPE Blog, Latin America
- HPE Blog, Middle East
- HPE Blog, Saudi Arabia
- HPE Blog, South Africa
- HPE Blog, UK & Ireland
- HPE Ezmeral: Uncut
- OEM Solutions
- Servers & Systems: The Right Compute
- Tech Insights
- The Cloud Experience Everywhere
-
Information
- Community
- Welcome
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Tips and Tricks
- Resources
- Announcements
- Email us
- Feedback
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Aruba Airheads Community
- Enterprise.nxt
- HPE Dev Community
- Cloud28+ Community
- Marketplace
-
Forums
-
Blogs
-
Information
-
English
- 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
- Email to a Friend
- Report Inappropriate Content
09-25-2019 02:41 AM
09-25-2019 02:41 AM
How to deal with dhcpv6-snooping and replaced devices/stale bindings
Hello,
I'm currently playing around with dhcp[v6]-snooping usinga limit of 1 device to somewhat limit our users in plugging in additional switches without notifying the IT department. I'm using various devices, mostly WB (2920) and WC-Series (2930F). For the most part this works as expected. Now from time to time we need to replace broken computers. Obviously the new device has a different MAC and the switch blocks the request. For legacy IP we can use clear dhcp-snooping binding port 99 to get rid of the old binding and allow the new device to fetch an IP. For IPv6 there doesn't seem to be a similar possibility to clear bindings, as such the old binding/MAC stays and we're unable to get the new device working. As far as I can tell only a reboot clears the table which isn't quite a usable solution.
Is there another way to clear v6 bindings?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
12-01-2020 05:14 AM
12-01-2020 05:14 AM
Re: How to deal with dhcpv6-snooping and replaced devices/stale bindings
For those searching along: Sadly there doesn't seem to be an equivialent so far. To avoid reboots the following workaround should help:
- Disable DHCPv6-Snooping limit for the port in question
- Deactivate/Reactivate the port to force the client to rerun DHCP
(Only works if the endpoint is directly connected)- Re-Enable the port limit
Log should now warn about too many Clients but keep the lease active until the previous one times out.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2021 Hewlett Packard Enterprise Development LP