summaryrefslogtreecommitdiffstats
path: root/yang
diff options
context:
space:
mode:
authorRafael Zalamena <rzalamena@opensourcerouting.org>2021-04-20 19:54:01 +0200
committerRafael Zalamena <rzalamena@gmail.com>2021-06-09 17:32:24 +0200
commit0213a658006216ddcd796b77c040797b1f5a01a4 (patch)
tree2c43686201e94f5f377f4853e14a0770d6ba667e /yang
parentMerge pull request #8815 from idryzhov/fix-ospf-aggr (diff)
downloadfrr-0213a658006216ddcd796b77c040797b1f5a01a4.tar.xz
frr-0213a658006216ddcd796b77c040797b1f5a01a4.zip
yang: rework PIM MSDP mesh group
Allow PIM MSDP configuration to support multiple MSDP mesh groups per PIM instance. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
Diffstat (limited to 'yang')
-rw-r--r--yang/frr-pim.yang34
1 files changed, 22 insertions, 12 deletions
diff --git a/yang/frr-pim.yang b/yang/frr-pim.yang
index 70adb37b2..4c4819ac2 100644
--- a/yang/frr-pim.yang
+++ b/yang/frr-pim.yang
@@ -174,26 +174,36 @@ module frr-pim {
"Enable ssmpingd operation.";
}
- container msdp-mesh-group {
- presence
- "Configure MSDP mesh-group.";
+ list msdp-mesh-groups {
+ key "name";
+ description
+ "RFC 3618 Section 10.2. MSDP mesh-group semantics
- leaf mesh-group-name {
- type string;
+ Groups multiple MSDP peers to reduce SA flooding typically used
+ in intra-domain settings.";
+
+ leaf name {
+ type string {
+ length 1..64;
+ }
description
- "MSDP mesh group name.";
+ "The mesh group name.";
}
- leaf-list member-ip {
+ leaf source {
type inet:ip-address;
description
- "Peer ip address.";
+ "Source IP address for the TCP connections.";
}
- leaf source-ip {
- type inet:ip-address;
- description
- "Source ip address for the TCP connection.";
+ list members {
+ key "address";
+
+ leaf address {
+ type inet:ip-address;
+ description
+ "Peer member IP address.";
+ }
}
}