diff options
| author | Rajesh Varatharaj <rvaratharaj@nvidia.com> | 2023-06-01 16:11:46 -0700 |
|---|---|---|
| committer | Rajesh Varatharaj <rvaratharaj@nvidia.com> | 2023-06-01 16:13:51 -0700 |
| commit | 314a97c164cd37e760a28940e4176195a4a7c91f (patch) | |
| tree | a9fc16755e0824d03ed8f727cd57063a980fb93b /ldpd/ldp_debug.c | |
| parent | 575a0c5e3cdc50915a9c41ab9a2c5ff31ff7e04d (diff) | |
pimd: Change in PIM northbound error, when a path to RP is not found during config apply
Currently, in PIM Northbound, when a path to RP is not found during config apply, we are treating this as a NB_ERR_INCONSISTENCY.
However, there are two issues with this approach:
When OSPF or IGP convergence is completed, it is possible that the RPF check will succeed.
If we have multiple groups and RPs (e.g. 50 RPs), we will receive 50 logs with inconsistency errors.
example:
2023/05/27 22:57:45 PIM: [G822R-SBMNH] config-from-file# ip pim rp 192.168.100.1 239.100.0.0/28 2023/05/27 22:57:45
PIM: [VAKV3-NMY7B][EC 100663337] error processing configuration change: error [internal inconsistency] event [apply]
operation [create] xpath [/frr-routing:routing/control-plane-protocols/control-plane-protocol[type='frr-pim:pimd']
[name='pim'][vrf='default']/frr-pim:pim/address-family[address-family='frr-routing:ipv4']/frr-pim-rp:rp/static-rp/rp-list
[rp-address='192.168.100.1']/group-list[.='239.100.0.0/28']] message: No Path to RP address specified: 192.168.100.1
Issue: #13620
Signed-off-by: Rajesh Varatharaj <rvaratharaj@nvidia.com>
Diffstat (limited to 'ldpd/ldp_debug.c')
0 files changed, 0 insertions, 0 deletions