diff options
| author | Donald Sharp <sharpd@cumulusnetworks.com> | 2020-02-19 10:52:14 -0500 |
|---|---|---|
| committer | Donald Sharp <sharpd@cumulusnetworks.com> | 2020-02-19 10:52:14 -0500 |
| commit | 3dbe2b6061ba07711584a87b714e76da92c4f8fa (patch) | |
| tree | 5976c7c28a57c378d50f7aab4e1f19a9e27d420c /bgpd/bgp_errors.h | |
| parent | 1a21da6b01ff50ac99eb6d54e6e1b2877ce5d5f8 (diff) | |
bgpd: Add a better breadcrumb for when bgp is missconfiged
Currently During bgp open collision resolution if both
the router-id's are the same, we correctly follow
the RFC and close the connection. The problem is of course
that there is no notification of the error in configuration
to the end user other than a subtle open debug message.
Explicitly call out the miss-configuration as an error message
as that this miss-config took several hours of debugging to notice.
Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>
Diffstat (limited to 'bgpd/bgp_errors.h')
| -rw-r--r-- | bgpd/bgp_errors.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/bgpd/bgp_errors.h b/bgpd/bgp_errors.h index 35c5cc3998..49c58ae6b0 100644 --- a/bgpd/bgp_errors.h +++ b/bgpd/bgp_errors.h @@ -98,6 +98,7 @@ enum bgp_log_refs { EC_BGP_CAPABILITY_UNKNOWN, EC_BGP_INVALID_NEXTHOP_LENGTH, EC_BGP_DOPPELGANGER_CONFIG, + EC_BGP_ROUTER_ID_SAME, }; extern void bgp_error_init(void); |