- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- Aruba & ProVision-based
- >
- Re: A daily switch lockup, same time every day
-
- Forums
-
Blogs
- Hybrid Cloud
- Edge
- Data & AI
- Working in Tech
- AI Insights
- Alliances
- Around the Storage Block
- Behind the scenes at Labs
- Careers in Tech
- HPE Storage Tech Insiders
- Inspiring Progress
- IoT at the Edge
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- HPE Blog, Austria, Germany & Switzerland
- Blog HPE, France
- HPE Blog, Italy
- HPE Blog, Japan
- HPE Blog, Russia
- HPE Blog, UK & Ireland
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
05-20-2015 01:37 PM
05-20-2015 01:37 PM
Re: A daily switch lockup, same time every day
Well, I am hoping this is the fix:
I had IP IGMP on a few VLANS and on the default VLAN, it had no IP Address. I believe my firewall got in the IGMP querier conversation and broadcast from my management VLAN to my default VLAN.
It seems that IGMP multicast can really screw up STP.
At any rate, removing all IP IGMP from my edge switchse has resolved the problem. After a few days, I'll announce victory.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
06-24-2015 07:07 AM
06-24-2015 07:07 AM
SolutionWell, to bring closure to this and hopefully help someone, even at the risk of personal embarrasment.
The main problem was HP800's with Intel NICS and old drivers, with IPv6 enabled. These NICs caused a staggering IPv6 neighbor discovery storm when going from sleep to wake.
Fixes include:
- getting rid of IPv6 -- we don't need it and it should have never been enabled
- updating the drivers
- configuring the ProCurve's with MLD protection
The "same time every day" should have been the clue I needed. And I should have wiresharked long ago, as the problem was immediately apparent from a capture (more than a million packets in a 1 second capture).
- « Previous
-
- 1
- 2
- Next »
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP