[j-nsp] Multicast/Broadcast Packets going to EX CPU

Sebastian Wiesinger juniper-nsp at ml.karotte.org
Thu Mar 6 04:48:53 EST 2014


* Keegan Holley <no.spam at comcast.net> [2014-03-05 18:33]:
> I agree.  It’s more likely that you had an increase in packets that
> the switch would process normally than the switch getting bored and
> suddenly deciding to read packets off the wire.  If there is an IP
> interface on the network that the broadcast/multicast packets
> traverse, the switch must read them just like every other IP enabled
> host.  This will even happen for tagged frames if there is a VLAN
> interface that matches the tag.

Yes there was a flood of BOOTP/DHCP packets in one VLAN that caused
the problems. The thing is: This should not be a problem in my mind
because the switch has no reason to look at these packets (the switch
has no l3-interface in the VLAN). So I can't imagine I'm the only one
facing this issue.

Regards

Sebastian

-- 
GPG Key: 0x93A0B9CE (F4F6 B1A3 866B 26E9 450A  9D82 58A2 D94A 93A0 B9CE)
'Are you Death?' ... IT'S THE SCYTHE, ISN'T IT? PEOPLE ALWAYS NOTICE THE SCYTHE.
            -- Terry Pratchett, The Fifth Elephant


More information about the juniper-nsp mailing list