Header Only - DO NOT REMOVE - Extreme Networks

lost Network message:ICMPv6 Mulitcast Listener Report

  • 20 March 2015
  • 8 replies
  • 410 views

I have my network switches extreme, during the day I have lost network, making a sniffer with wireshark I see many messages ICMPv6 (see attached), that can cause this?

regards


8 replies

Userlevel 4
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD
Userlevel 3
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD


Hi Jason,

Please share document guide for set policy
I cannot find set policy command in EXOS. Is it hardware or software limitation?
Can i apply it on Summit Series X250, X440, X450, BD8000

EXOS_Concepts_Guide_15_4
EXOS_Command_Reference_15_7

Appreciate your help.
Userlevel 7
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD


In EXOS, you can create an ACL to accomplish the same thing. In this case, an example policy file is below:

entry deny_ipv6{ if { ethernet-type 0x86dd; } then { deny; count ipv6_drop; } } [/code]Then, apply this ingress on the affected ports. The process for creating the policy file and applying it is shown the the GTAC Knowledge article below:

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-create-and-apply-an-ACL-in-EXOS

-Brandon

Edit: Fixed an incorrect match condition.
Userlevel 3
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD


Hi Brandon,

In my case ICMPv6 Length are 110 and 90.

Appreciate your help.
Userlevel 3
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD


Hi Brandon,

For ICMPv6 Length are 110 and 90.

Can i use as follow?

ethernet-type 0x86dd;
ethernet-type 0x90dd;
ethernet-type 0x110dd;

Thanks.
Userlevel 7
You can set a basic policy to block this traffic if you are not using IPv6.

set policy profile 100 name BlockIPV6

set policy rule 100 ether 0x86dd mask 16 drop

set policy port *.*.* 100

*.*.* is all ports

BTW, you will get a error that you cannot set this on a LAG ports
It is FAD


Ethertype 0x86dd means IPv6. The length is only for low value of the ethertype (below 1500 decimal).
I had this problem once with a specific series of DELL workstations. They did this when going into power save mode. The model in question was DELL Optiplex 780 iirc. If you have those machines in your network try updating them to the latest BIOS and NIC drivers.
Userlevel 7
I had this problem once with a specific series of DELL workstations. They did this when going into power save mode. The model in question was DELL Optiplex 780 iirc. If you have those machines in your network try updating them to the latest BIOS and NIC drivers.
Yes, this is a known issue with some Intel NICs that leads to flooding MLD traffic when the NIC is in power save mode. There should be a driver update available to remedy this issue. More information is on Intel's support forum, linked below.

https://communities.intel.com/thread/48051

-Brandon

Reply