summaryrefslogtreecommitdiff
path: root/pimd/pim_errors.c
diff options
context:
space:
mode:
authorSarita Patra <saritap@vmware.com>2022-07-28 10:40:52 -0700
committerSarita Patra <saritap@vmware.com>2022-07-28 13:03:46 -0700
commitf789683690ceb7e063e99b1b9b92370e24a21f18 (patch)
treea447caf657b437061163eed4c30e7d5a29db9549 /pimd/pim_errors.c
parentb5e08672eae95e880496702d375e6bbd7c3501aa (diff)
pimd: Update mroute IIF based on Nexthop received from Zebra
Topology: R1(LHR) ---- R2 ----R4(FHR) ---- R3 ---- R2 = RP Steps to reproduce: 1. R1(LHR) sends IGMP join, R4(FHR) sends multicast traffic. Verify traffic is flowing from FHR to LHR. 2. Restart R1(LHR). 3. Below sequence of events are happening after FRR restart in R1(LHR). 4. R1(LHR) Register RP address to Zebra. 5. R1(LHR) Receive update from Zebra that R2(RP) is reachable via R3. 6. R1(LHR) Receive IGMP join for group 225.1.1.1, will create pim upstream and (*,G) mroute with IIF towards R3. 7. R1(LHR) Receive update from Zebra that RP is reachable via R2(RP). 8. R1(LHR) Update the PIM upstream IIF, but not updating the (*,G) IIF even there is RPF change. 9. R1(LHR) receives IGMP join for group 225.1.1.2, will create (*,G) with IIF towards R2(RP), both upstream and (,G) created with IIF towards R2(RP). Root Cause: Mroute IIF is not getting updated when better route update received. It is still pointing to the older nexthop. Fix: Update the mroute IIF when there is change in nexthop. Fixing Issue #11675 Signed-off-by: Sarita Patra <saritap@vmware.com>
Diffstat (limited to 'pimd/pim_errors.c')
0 files changed, 0 insertions, 0 deletions