- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- How to deal with dhcpv6-snooping and replaced devi...
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
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
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
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
- 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.