Hello Michele,
No compliance doc or cert exists for the V2H.
IPv6 introduces some new protocols but still has to run on ethernet. Any layer 2 ethernet switch will be able to handle IPv6 forwarding.
ARP goes away in v6 but plenty of multicast is present. IPv6 multicast packets get the same treatment IPv4 multicast receives; forward out all ports except the ingress port.
If I'm on target, you're not describing packet replication observed in a wireshark trace. I gather you've determined it's not a loop - but the multicast aspect of the problem and the crushing impact on the network is that of a loop.
Most of us are familiar with the confusion and chaos L2 loops bring to the party.
We hear similar symptoms described from time to time in support. It seems to happen to all switch types. The behavior is destructive to network switches and the L2 network. There appears to be more than one flavor of the problem described below (link: nic blasts ipv6 mld queries). The good news - if this is your problem there's a solution: driver updates.
The following link (from a quick search 'ipv6 sleeping nic') is not an official bug report, it's a journal/blog entry from a battered network admin.
There are others like it:
http://packetpushers.net/good-nics-bad-things-blast-ipv6-multicast-listener-discovery-queries/
Often this starts as an annoying slowdown eventually getting very painful.
The behavior is ddos-ish since many end stations will exhibit the condition at once. OS upgrade rollout establishes the means - then everyone in the physics dept goes home at the same time. Many end stations will power down at around the same time. Silliness ensues.
My official recommendation: Order 75 or 80 X460-G2's.
🙂
Let us know how things are going Michele. If this driver problem isn't a fit, bump the thread again. There's sure to be someone in the community with experience that will be able to help.
Regards,
Mike
