| Age | Commit message (Collapse) | Author |
|---|
|
* added option "check-control-plane-failure" for BFD in BGP neighbors
* added configuration check for checking if BFD peer is already configured before applying bfd option to BGP neighbor
* added configuration check for checking if BFD peers are already configured for all members in peer-group before applying bfd option to BGP peer-group
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
set protocols bgp <X> neighbor <Y> bfd
set protocols bgp <X> peer-group <Y> bfd
|
|
This reverts commit 890c9e8984c6b4eeef7ee277c88777416e1fb340.
|
|
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
}
}
}
|
|
Reproduce with:
set protocols ospf passive-interface default
set protocols ospf passive-interface-exclude eth1
set protocols ospf passive-interface-exclude eth2.5
commit
delete protocols ospf passive-interface default
delete protocols ospf passive-interface-exclude eth1
delete protocols ospf passive-interface-exclude eth2.5
commit
Results in
[ protocols ospf passive-interface default ]
sh: line 8: [: eth1: unary operator expected
|
|
|
|
|
|
|
|
|
|
41df1579f6ca3e5a1618ee85bbb337011148f1ef
|
|
- interface for route table
|
|
|
|
|
|
|
|
|
|
|
|
|
|
and allow named community lists there.
|
|
comm-list" statements.
|
|
|
|
|
|
|
|
support it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conflicts:
debian/control
|
|
|
|
|
|
|
