Reset Search
 

 

Article

How to stop Kern.IPv4Mc.Error Unable to Del IPmc sender entry not found log message from appearing

« Go Back

Information

 
TitleHow to stop Kern.IPv4Mc.Error Unable to Del IPmc sender entry not found log message from appearing
Objective
These logs show up when the multicast hardware table is unnecessarily populated with a number of entries (As shown in the below output), possibly created by SSDP (Simple Service Discovery Protocol, 239.255.255.250) running on clients by default.

 
08/24/2016 15:52:50.89 <Erro:Kern.IPv4Mc.Error> Slot-3: IPmc sender entry s,G,v=0,ef020e2f,169 IPMC 33 was not added to all switching resources rc -4
<Erro:Kern.IPv4Mc.Error> Slot-3: IPmc sender entry s,G,v=0,ef020c81,138 IPMC 33 was not added to all switching resources rc -4
<Erro:Kern.IPv4Mc.Error> Slot-3: Unable to Del IPmc sender entry s,G,v=10.221.140.131,239.255.255.250,140 IPMC 33 flags 8000 unit 1, Entry not found
<Erro:Kern.IPv4Mc.Error> Slot-3: Unable to Del IPmc sender entry s,G,v=10.221.140.91,239.255.255.250,140 IPMC 33 flags 8000 unit 1, Entry not found
<Erro:Kern.IPv4Mc.Error> Slot-3: Unable to Del IPmc sender entry s,G,v=10.221.140.24,239.255.255.250,140 IPMC 33 flags 8000 unit 1, Entry not found
Environment
  • Black Diamond switches
  • All EXOS Platform
Procedure
Since all the error messages are related to SSDP (239.255.255.250) multicast entries, the following command (if SSDP is not in use) will help optimize the mulitcast hardware table by grouping SSDP multicast entries and reprogramming them in the hardware table.
 
Switch# configure forwarding ipmc lookup-key group-vlan | Note: If using PIM or MVR, use mixed-mode instead of group-vlan
Switch# clear igmp snooping

The above command also is useful in stopping the reported multicast continuous log messages appaering on BD switches.
 
Additional notes

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255