diff options
| author | Chirag Shah <chirag@cumulusnetworks.com> | 2017-02-22 16:28:36 +0100 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2017-03-16 23:53:28 +0100 |
| commit | 1bc9827622572b24c7c47656565dc1a2601d6dc5 (patch) | |
| tree | eda923517f772ca214aa507de5fc313bff1a24dd /doc/fig-vnc-commercial-route-reflector.dia | |
| parent | Merge pull request #270 from donaldsharp/cares (diff) | |
| download | frr-1bc9827622572b24c7c47656565dc1a2601d6dc5.tar.xz frr-1bc9827622572b24c7c47656565dc1a2601d6dc5.zip | |
pimd: Nexthop tracking support
Add pim Nexthop tracking feature 1st part where, specific RP or Source address (unicast address)
register with Zebra. Once nexthop update received from Zebra for a given address, scan RP or upstream
entries impacted by the change in nexthop.
Reviewed By: CCR-5761, Donald Sharp <sharpd@cumulusnetworks.com>
Testing Done: Tested with multiple RPs and multiple *,G entries at LHR.
Add new Nexthop or remove one of the link towards RP and verify RP and upstream nexthop update.
similar test done at RP with multiple S,G entries to reach source.
Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
Diffstat (limited to '')
0 files changed, 0 insertions, 0 deletions