Allow sessions to use BFD profile configurations instead of having to
clone the configuration per peer.
If using a profile and setting a peer configuration, the peer
configuration will take precedence over the profile.
Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
}
}
+ typedef profile-name {
+ type string {
+ length "1..64";
+ }
+ description "Profile name format";
+ }
+
+ typedef profile-ref {
+ type leafref {
+ path "/frr-bfdd:bfdd/frr-bfdd:bfd/frr-bfdd:profile/frr-bfdd:name";
+ require-instance false;
+ }
+ description "Reference to a BFD profile";
+ }
+
/*
* Shared BFD items.
*/
container bfd {
presence "Present if the BFD protocol is enabled";
+ list profile {
+ key "name";
+ description "BFD pre configuration profiles";
+
+ leaf name {
+ type profile-name;
+ description "Profile name";
+ }
+
+ uses session-common;
+ uses session-echo;
+ }
+
container sessions {
list single-hop {
key "dest-addr interface vrf";
description "Local IP address";
}
+ leaf profile {
+ type profile-ref;
+ description "Override defaults with profile.";
+ }
+
uses session-common;
uses session-echo;
description "Virtual Routing Domain name";
}
+ leaf profile {
+ type profile-ref;
+ description "Override defaults with profile.";
+ }
+
uses session-common;
container stats {