summaryrefslogtreecommitdiffstats
path: root/yang (follow)
Commit message (Collapse)AuthorAgeFilesLines
* pimd: change ranges to 1..max, type align with IETF YANG.Christian Hopps2021-08-192-28/+28
| | | | | | | | | | | | | While defaults are good picks for "reasonable" guesses, min and max range values really aren't. Operators and experimenters often like to configure "unreasonable" values to stress test, tests boundary conditions and explore innovations. With that in mind, change all ranges to 1..max (of type). While we're here add optional ignored values in the "no" CLI forms. Signed-off-by: Christian Hopps <chopps@labn.net>
* yang: mark a couple of prefix-list/access-list leafs as mandatoryIgor Ryzhov2021-08-101-1/+5
| | | | | | | | | | | | | The code assumes that these leafs always exist when their complementary leafs exist. For example, when processing `ipv4-exact-match`, the code always expects to have access to `ipv4-prefix`. If those leafs are not provided, code crashes. It doesn't happen when using the CLI because it always does the right thing, but it can happen when using other frontends. Also fix incorrect description for prefix-list sequence leaf. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* pimd: Allow join prune intervals to be as small as 5 secondsDonald Sharp2021-07-261-1/+1
| | | | | | | | | | Allow the join-prune interval to be as small as 5 seconds instead of limiting the value to 60. This can and will come at a price of being able to converge less mroutes. Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* Merge pull request #8983 from mobash-rasool/pim-upstreaming-activityDonald Sharp2021-07-221-2/+2
|\ | | | | pimd: Minor fixes for BSM Show CLI and Hold Timer CLI
| * pimd: make pim interface hold interval range 1-630github login name2021-07-071-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | Making the interface holdtime range to 3.5 times the hello-time As per 7761, Section 4.11: The Holdtime in a Hello message should be set to (3.5 * Hello_Period), giving a default value of 105 seconds. Therefore providing the user also to configure max upto 3.5 times the hello timer interval. Signed-off-by: Mobashshera Rasool <mrasool@vmware.com>
* | bgpd: Add route-map `match alias` commandDonatas Abraitis2021-07-211-1/+14
|/ | | | | | | Will be handy to filter BGP prefixes by using BGP community alias instead of numerical community values. Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
* yang: add MSDP timer configurationRafael Zalamena2021-07-011-0/+49
| | | | | | Allow users to configure global MSDP timers. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* yang: simplify MSDP peer handlingRafael Zalamena2021-06-251-0/+1
| | | | | | | | Make the source address mandatory since it doesn't work without it. The CLI already mandated it before so it makes sense to change this here as well. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* Merge pull request #6695 from adharkar/frr-master-gateway_ipPatrick Ruddy2021-06-231-0/+32
|\ | | | | EVPN route type-5 gateway IP overlay Index
| * bgpd: Add "set evpn gateway-ip" clause for route-mapAmeya Dharkar2021-06-081-0/+32
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Add following set clause for route-maps "set evpn gateway-ip <ipv4|ipv6 >A.B.C.D|X:X::X:X" - When this route-map is applied as outboubd policy in BGP, it will set the gateway-ip in BGP attribute For EVPN type-5 routes. Example configuration: route-map RMAP-EVPN_GWIP permit 5 set evpn gateway-ip ipv4 50.0.2.12 set evpn gateway-ip ipv6 50:0:2::12 router bgp 101 bgp router-id 10.100.0.1 neighbor 10.0.1.2 remote-as 102 ! address-family l2vpn evpn neighbor 10.0.1.2 activate neighbor 10.0.1.2 route-map RMAP-EVPN_GWIP out advertise-all-vni exit-address-family Signed-off-by: Ameya Dharkar <adharkar@vmware.com>
* | yang: rework PIM MSDP mesh groupRafael Zalamena2021-06-091-12/+22
|/ | | | | | | Allow PIM MSDP configuration to support multiple MSDP mesh groups per PIM instance. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* bfdd: forbid setting interface for multihop sessionsIgor Ryzhov2021-06-011-6/+1
| | | | Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* bgpd: fix default for extended-nexthop-capabilityChristian Hopps2021-05-233-2/+10
| | | | | | | | | The default for extended-nexthop-capability is true for unnumbered (interface) neighbors, false for other types. Break the inner grouping out of the outer neighbor-parameters grouping so that we can refine the default in that uses case. Signed-off-by: Christian Hopps <chopps@gmail.com>
* yang: fix BGP multicast prefix typeRafael Zalamena2021-05-211-10/+10
| | | | | | | Fix many of the commands in the `address-family ipv4 multicast` to use the proper type to avoid wrong YANG model validation failures. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* yang: move multicast prefix type definitionRafael Zalamena2021-05-212-36/+40
| | | | | | | Move the multicast prefix type to a common YANG model so other models can use it. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* bgpd, yang: fix replace-as yang leafIgor Ryzhov2021-05-141-1/+1
| | | | | | | The leaf is called "no-replace-as" in the model but is used reversed in all the code. Let's rename it to comply with the actual behavior. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* lib: adapt to version 2 of libyangChristian Hopps2021-05-1315-103/+107
| | | | | | | | | Compile with v2.0.0 tag of `libyang2` branch of: https://github.com/CESNET/libyang staticd init load time of 10k routes now 6s vs ly1 time of 150s Signed-off-by: Christian Hopps <chopps@labn.net>
* pathd. TED support . Validation of candidate path - [part 2/4]Javier Garcia2021-05-101-42/+67
| | | | | | | | | | | | | | - Explicit segment list nai will be resolved to corresponded sid. - Dynamic segment list (from pce) will be validated. - If segment list could not be resolved or validated won't be used. - Now this new config is supported segment-list sl-1 index 10 nai prefix 10.1.2.1/32 iface 1 index 30 nai adjacency 10.2.5.2 10.2.5.5 index 40 nai prefix 10.10.10.5/32 algorithm 0 Signed-off-by: Javier Garcia <javier.garcia@voltanet.io>
* isisd: link protection optional fallback in ti-lfaFredi Raspall2021-05-031-0/+7
| | | | | | | | | | | | | | | | The current implementation of TI-LFA computes link-protecting repair paths (even when node protection is enabled) to have repair paths to all destinations when no node-protecting repair has been found. This may be desired or not. E.g. the link-protecting paths may use the protected node and be, therefore, useless if the node fails. Also, computing link-protecting repairs incurs extra calculations. With this patch, when node protection is enabled, link protecting repair paths are only computed if "link-fallback" is specified in the configuration, on a per interface and IS-IS level. Signed-off-by: Fredi Raspall <fredi@voltanet.io>
* isisd, yang: remove vrf leaf from isis interface nodeIgor Ryzhov2021-04-291-7/+0
| | | | | | | This is very confusing and incorrect. We can and should use vrf leaf of the interface itself instead. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* isisd: fix ldp-sync configurationIgor Ryzhov2021-04-291-4/+4
| | | | | | | | | | | YANG model and CLI commands allow user to configure LDP-sync per area. But the actual implementation is incorrect - all commands are changing the config for the whole VRF instead of a single area. This commit fixes this issue by actually implementing per area configuration. Fixes #8578. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* yang: add PIM BFD profile supportRafael Zalamena2021-04-231-0/+6
| | | | | | Allow users to configure BFD profile for the peers in a interface. Signed-off-by: Rafael Zalamena <rzalamena@opensourcerouting.org>
* Merge pull request #8389 from idryzhov/route-map-optimization-nbRenato Westphal2021-04-131-0/+5
|\ | | | | lib: convert route-map optimization to NB
| * lib: convert route-map optimization to NBIgor Ryzhov2021-04-061-0/+5
| | | | | | | | Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | Merge pull request #8348 from chiragshah6/mdevIgor Ryzhov2021-04-051-0/+4
|\ \ | | | | | | yang, bgpd: add northbound transactional callbacks for neighbor route-map for af l2vpn-evpn
| * | yang: add policy support for l2vpn-evpn nbr treeChirag Shah2021-03-261-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add bgp routing policy support for unnumbered and peer-group. For numbered peer the policy support is already present. +--rw bgp! +--rw neighbors | +--rw unnumbered-neighbor* [interface] | +--rw afi-safis | +--rw afi-safi* [afi-safi-name] +--rw l2vpn-evpn | | | +--rw filter-config | | | +--rw rmap-import? frr-route-map:route-map-ref | | | +--rw rmap-export? frr-route-map:route-map-ref | | | +--rw plist-import? frr-bgp-types:plist-ref | | | +--rw plist-export? frr-bgp-types:plist-ref | | | +--rw access-list-import? frr-bgp-types:access-list-ref | | | +--rw access-list-export? frr-bgp-types:access-list-ref | | | +--rw as-path-filter-list-import? frr-bgp-types:as-path-filter-ref | | | +--rw as-path-filter-list-export? frr-bgp-types:as-path-filter-ref | | | +--rw unsuppress-map-import? frr-route-map:route-map-ref | | | +--rw unsuppress-map-export? frr-route-map:route-map-ref ... +--rw peer-groups +--rw peer-group* [peer-group-name] | +--rw afi-safis | +--rw afi-safi* [afi-safi-name] +--rw l2vpn-evpn | | | +--rw filter-config | | | +--rw rmap-import? frr-route-map:route-map-ref | | | +--rw rmap-export? frr-route-map:route-map-ref | | | +--rw plist-import? frr-bgp-types:plist-ref | | | +--rw plist-export? frr-bgp-types:plist-ref | | | +--rw access-list-import? frr-bgp-types:access-list-ref | | | +--rw access-list-export? frr-bgp-types:access-list-ref | | | +--rw as-path-filter-list-import? frr-bgp-types:as-path-filter-ref | | | +--rw as-path-filter-list-export? frr-bgp-types:as-path-filter-ref | | | +--rw unsuppress-map-import? frr-route-map:route-map-ref | | | +--rw unsuppress-map-export? frr-route-map:route-map-ref ... Signed-off-by: Chirag Shah <chirag@nvidia.com>
* | | bgpd: increase the maximum number of neighborsPhilippe Guibert2021-04-021-1/+1
| |/ |/| | | | | | | | | | | increase the maximum number of neighbors in a bgp group. Set the maximum value to 50000 instead of 5000. Signed-off-by: Philippe Guibert <philippe.guibert@6wind.com>
* | lib,zebra,bgpd,ospfd,ospf6d: Route-map yang defnsSarita Patra2021-03-308-336/+1702
|/ | | | | | | | | | | | This commit includes the following: 1) Modifications to the frr-route-map.yang to enable addition of bgpd, ospfd, ospf6d and zebra specific route map match/set clauses. 2) Yang definitions for bgpd match/set clauses. 3) Yang definitions for ospfd and ospf6d match/set clauses. 4) Yang definitions for zebra match/set clauses. Signed-off-by: NaveenThanikachalam <nthanikachal@vmware.com> Signed-off-by: Sarita Patra <saritap@vmware.com>
* Merge pull request #8332 from donaldsharp/yang_cleanDavid Lamparter2021-03-251-0/+6
|\ | | | | yang: Allow `make clean` to actually clean up dependant files
| * yang: Allow `make clean` to actually clean up dependant filesDonald Sharp2021-03-251-0/+6
| | | | | | | | Signed-off-by: Donald Sharp <sharpd@nvidia.com>
* | Merge pull request #8333 from mobash-rasool/pim-fixes-2Donald Sharp2021-03-251-0/+3
|\ \ | | | | | | pimd: Fix hold time related issues
| * | pimd: Validation that hello should be less than hold time config.Mobashshera Rasool2021-03-251-0/+3
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also included display of hold time in CLI 'show ip pim int <intf>' cmd and json commands. Issue: PIM neighbor not coming up if hold time is less than hello timer since hello is sent every 4 sec and hold is 1 sec, because of this nbr is flapping Fix: Do not allow configuration of hold timer less than hello timer Also reset the value of hold timer to 3.5 times to hello whenever only hello is modified so that the relationship holds good. Signed-off-by: Mobashshera Rasool <mrasool@vmware.com>
* | Merge pull request #8250 from idryzhov/fix-nb-running-get-entryRenato Westphal2021-03-241-1/+1
|\ \ | |/ |/| Fix aborts when using nb_running_get_entry during validation stage
| * zebra: make ribs config falseIgor Ryzhov2021-03-161-1/+1
| | | | | | | | | | | | | | | | | | | | Zebra routing tables are not controlled by the user and can not be created/deleted manually. Current NB create/destroy callbacks are incorrectly implemented because instead of creating/deleting the RIB they are only checking for it's existence. YANG model should reflect the real situation. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | Merge pull request #8008 from chiragshah6/yang_nb5Santosh P K2021-03-171-4/+0
|\ \ | | | | | | [lib, yang] : multiple fixes in prefix-list northbound conversion
| * | yang: remove when statement from prefix-listChirag Shah2021-03-021-4/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove when statements from prefix-list yang OM, and do the same check in frr validation phase. This helps a bit in perfomance of prefix-lists scale config. Ticket:CM-32035 Reviewed By:CCR-11096 Testing Done: Signed-off-by: Chirag Shah <chirag@nvidia.com>
* | | bfdd: separate echo rx/tx timersIgor Ryzhov2021-03-161-1/+8
| |/ |/| | | | | | | | | | | | | | | | | Currently there is a single interval for both RX and TX echo functions. This commit introduces separate RX and TX timers for echo packets. The main advantage is to be able to set the receive interval to zero when we don't want to receive echo packets from the remote system. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | bfdd: make sessions administratively up by defaultIgor Ryzhov2021-03-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current behavior is inconsistent. When the session is created by another daemon, it is up by default. When we later configure peer in bfdd, the session is still up, but the NB layer thinks that it is down. More than that, even when the session is created in bfdd using peer command, it is created in DOWN state, not ADM_DOWN. And it actually starts sending and receiving packets. The sessions is marked with SHUTDOWN flag only when we try to reconfigure some parameter. This behavior is also very unexpected. Fixes #7780. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>
* | isisd, yang, doc: combine config cmd for SRGB+SRLBEmanuele Di Pascale2021-03-101-30/+39
|/ | | | | | | | | | | when changing both ranges at the same time the order of the commands matters, as we need to make sure that the intermediate state is valid. This represents a problem when pushing configuration via frr-reload. To fix this, the global-block command was extended to optionally allow setting the local-block range as well. The local-block command is deprecated with a 1-year notice. Signed-off-by: Emanuele Di Pascale <emanuele@voltanet.io>
* isisd: Fix Attach-bit processinglynne2021-01-201-0/+15
| | | | | | | | | | | | | | | | | | | | | | | The purpose of the Attach-bit is to accomplish inter-area routing. In other venders, the Attached-bit is automatically set when a router is configured as a L1|L2 router and has two adjacencies. When a L1 router receives a LSP with the Attached-bit set it is supposed to create a default route pointing toward the neighbor to provide a default path out of the L1 area. ISIS implementation has been fixed to support the above definition: Setting the Attach-bit is now the default behavior and we allow the user to turn it off. We will only set the Default Attach-bit when creating a L1 LSP, if we are a L1|L2 router and have a L2 adjacency up. When a L1 router receives a LSP with the Attach-bit set, we will create a default route pointing to the L1|L2 router as the nexthop. The default route will be removed if the LSP is received with the Attach-bit cleared. Signed-off-by: Lynne Morrison <lynne@voltanet.io>
* Merge pull request #7781 from chiragshah6/evpn_devRuss White2021-01-191-1/+51
|\ | | | | [yang,bgpd] convert neighbor prefix-list and route-map to transactional clis
| * yang: nbr plist nb conversion for more afi-safisChirag Shah2021-01-101-1/+51
| | | | | | | | Signed-off-by: Chirag Shah <chirag@nvidia.com>
* | Merge pull request #7863 from chiragshah6/mdevRuss White2021-01-191-4/+2
|\ \ | | | | | | [yang,staticd]: remove when condition from static nexthop om
| * | yang: remove when condition from static nexthop omChirag Shah2021-01-131-4/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Remove when conditions from the yang OM as it degrades the performance in libyang. Instead do the same when conditional check in frr northbound validate phase. Reject the config if condiion do not meet. Ticket:CM-32530 Testing Done: Co-developed-by: VishalDhingra <vdhingra@vmware.com> Signed-off-by: Chirag Shah <chirag@nvidia.com>
* | | Merge pull request #7844 from vishaldhingra/staticMark Stapp2021-01-151-8/+7
|\ \ \ | |/ / |/| | staticd: correct table-id handling for static routes.
| * | staticd: make table-id as the key for path-listvdhingra2021-01-101-8/+7
| |/ | | | | | | | | | | | | | | modified the yang model for path-list. table-id should be a key, as one route can have multiple table-ids. Signed-off-by: vishaldhingra <vdhingra@vmware.com>
* / yang, isisd: add RLFA nodes, skeleton callbacks and CLI commandsRenato Westphal2021-01-091-0/+47
|/ | | | Signed-off-by: Renato Westphal <renato@opensourcerouting.org>
* Merge pull request #7807 from logbob0401/vrrpd_yang_bug_fixRuss White2021-01-051-2/+2
|\ | | | | Fix augment path problem in frr-vrrpd.yang to comply with rfc 7950
| * vrrpd.yang bug fix: modify augment path to comply with rfc 7950Bo Zhang2021-01-031-2/+2
| | | | | | | | Signed-off-by: Bo Zhang <logbob0401@gmail.com>
* | Merge pull request #7507 from ↵Russ White2021-01-051-0/+7
|\ \ | |/ |/| | | | | ton31337/fix/bgpd_do_not_send_update_if_path_really_did_not_change bgpd: Do not send BGP UPDATE if the route actually not changed
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-19 03:13:52 +0100