diff options
| author | Christian Poessinger <christian@poessinger.com> | 2019-06-16 15:13:21 +0200 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2019-06-16 15:50:14 +0200 |
| commit | 890c9e8984c6b4eeef7ee277c88777416e1fb340 (patch) | |
| tree | ad741de36e727dcccb48aac30c5d9745ffa860ba /templates/protocols | |
| parent | 8dc9ac88c2ab71a71ab6f532339cd4ab2b321a29 (diff) | |
| download | vyatta-cfg-quagga-890c9e8984c6b4eeef7ee277c88777416e1fb340.tar.gz vyatta-cfg-quagga-890c9e8984c6b4eeef7ee277c88777416e1fb340.zip | |
T849: move BGP peer-group node to ipv4 address family
To have a consitent IPv4/IPv6 CLI a lot of BGP neighbor nodes have been
migrated. The IPv4 peer-group has been forgotten, leaving a non consistent CLI.
Previously:
-----------
neighbor 2001:DB8:FFFF::1 {
address-family {
ipv6-unicast {
peer-group iBGP
}
}
peer-group iBGP
}
Now:
----
neighbor 2001:DB8:FFFF::1 {
address-family {
ipv6-unicast {
peer-group iBGP
}
}
address-family {
ipv4-unicast {
peer-group iBGP
}
}
}
Diffstat (limited to 'templates/protocols')
| -rw-r--r-- | templates/protocols/bgp/node.tag/neighbor/node.tag/address-family/ipv4-unicast/peer-group/node.def (renamed from templates/protocols/bgp/node.tag/neighbor/node.tag/peer-group/node.def) | 0 |
1 files changed, 0 insertions, 0 deletions
diff --git a/templates/protocols/bgp/node.tag/neighbor/node.tag/peer-group/node.def b/templates/protocols/bgp/node.tag/neighbor/node.tag/address-family/ipv4-unicast/peer-group/node.def index 5da142d6..5da142d6 100644 --- a/templates/protocols/bgp/node.tag/neighbor/node.tag/peer-group/node.def +++ b/templates/protocols/bgp/node.tag/neighbor/node.tag/address-family/ipv4-unicast/peer-group/node.def |