Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pim vxlan issues #15130

Merged
merged 3 commits into from
Jan 12, 2024
Merged

Pim vxlan issues #15130

merged 3 commits into from
Jan 12, 2024

Conversation

donaldsharp
Copy link
Member

One fix to pim vxlan behavior and several debug changes to make debugging easier on the eyes.

The pim vxlan behavior change is to be more persistent about sending the Null Register on startup. Effectively one thing that was noticed during internal testing is that the null register is sometimes not received on the RP. Just sending one at startup time ( when all the other routers/switches are starting up too ) leave you with a situation where the next Null register is 60 seconds out. PIM VXlan wants to build the SPT tree as fast as possible. So let's facilitate this.

When doing pim vxlan multicast bum handling, setup
the register to send up to 10 null registers on
immediate startup.  If the null register packet
gets dropped this delays the formation of the
S,G tree from the RP towards the FHR.

Signed-off-by: Donald Sharp <[email protected]>
The Join or Prune messages require you to turn on `trace`
but this is part of Join/Prune processing of the packet
let's use PIM_DEBUG_PIM_J_P instead of TRACE here.

Signed-off-by: Donald Sharp <[email protected]>
When turning on debug pim trace, there are lots of messages
surrounding the timing of rpf lookup.  99% of the time
no-one cares about these anymore.  Let's make them
not seen unless we turn up debugs

Signed-off-by: Donald Sharp <[email protected]>
@routingrocks
Copy link
Contributor

LGTM

@ton31337 ton31337 merged commit ef85d4f into FRRouting:master Jan 12, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants