diff options
| author | Sarita Patra <saritap@vmware.com> | 2023-04-09 22:30:44 -0700 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2023-04-13 11:37:39 +0000 |
| commit | 5339bb3ddd7d0ff4fb9ee5f6ca5f194df914aec2 (patch) | |
| tree | d35e4ae4cc9d508f38dafe95cd93ba729a1d1fc9 /lib/command.c | |
| parent | 6398f442457ae4285e9c0ee1d7764825c571f37e (diff) | |
pimd: Process no-forward BSM packet
Topology Used:
=============
Cisco---FRR4----FRR2
Initially PIM nbr is down between FRR4----FRR2 from FRR2 side
Cisco is sending BSR packet to FRR4.
Problem Statement:
=================
No shutdown the PIM neighbor on FRR2 towards FRR4.
FRR2, receives BSR packet immediately as the new neighbor
comes up. This BSR packet is having no-forward bit set.
FRR2 is not able to process the BSR packet, and drop the
BSR packet.
Root Cause:
==========
When PIMD comes up, we start BSM timer for 60 seconds.
Here, the value accept_nofwd_bsm is setting to false.
FRR2, when receives no-forward BSR packet, it is getting
accept_nofwd_bsm value as false.
So, it drops, the no-forward BSM packet.
Fix:
===
Set accept_nofwd_bsm as false after first BSM packet received.
Signed-off-by: Sarita Patra <saritap@vmware.com>
(cherry picked from commit 8b462d557905200d98c7a8965b3d223637c3c5dd)
Diffstat (limited to 'lib/command.c')
0 files changed, 0 insertions, 0 deletions