Hello,
I am having issues with LABing and verifying state-refresh configuration in PIM Dense mode which should be fairly simple thing. Interface configuaration from both side of PIM Dense neighbors stetest this command " ip pim state-refresh origination-interval 20" . My expectations is that neigbor would now send every 20 seconds state-refresh Prune messages so there is no single multicast forwarding because that 3 minute Prune timer is never exiped (instead is refreshed every 20 sec). I put those interface state-refresh commands on both side on a link, router are still behaving by prunning when they got another multicast packet. I tested this in my EVE-NG LAB with IOS I have as well with IOS XE CRS 1000V platform on ESXi - result is identical. I verified this with debug command “debug ip pim group” and with wireshark on EVE-NG. What am I missing here with this state refresh in dense mode?
I got simplest topology sender–>R9-- pimD—R10----stub_network_no_receivers
Here are logs from CSR 1000V (router R10)
Sep 29 14:13:56.746: PIM(0): Insert (155.8.9.8,239.9.9.9) prune in nbr 155.9.10.9’s queue
*Sep 29 14:13:56.747: PIM(0): Building Join/Prune packet for nbr 155.9.10.9
*Sep 29 14:13:56.747: PIM(0): Adding v2 (155.8.9.8/32, 239.9.9.9) Prune
*Sep 29 14:13:56.747: PIM(0): Send v2 join/prune to 155.9.10.9 (GigabitEthernet1.910)!!!
*Sep 29 14:16:56.814: PIM(0): Insert (155.8.9.8,239.9.9.9) prune in nbr 155.9.10.9’s queue
*Sep 29 14:16:56.814: PIM(0): Building Join/Prune packet for nbr 155.9.10.9
*Sep 29 14:16:56.814: PIM(0): Adding v2 (155.8.9.8/32, 239.9.9.9) Prune
*Sep 29 14:16:56.815: PIM(0): Send v2 join/prune to 155.9.10.9 (GigabitEthernet1.910)!!!
*Sep 29 14:19:56.871: PIM(0): Insert (155.8.9.8,239.9.9.9) prune in nbr 155.9.10.9’s queue
*Sep 29 14:19:56.872: PIM(0): Building Join/Prune packet for nbr 155.9.10.9
*Sep 29 14:19:56.872: PIM(0): Adding v2 (155.8.9.8/32, 239.9.9.9) Prune
*Sep 29 14:19:56.872: PIM(0): Send v2 join/prune to 155.9.10.9 (GigabitEthernet1.910)!