diff options
| author | vivek <vivek@cumulusnetworks.com> | 2017-12-01 17:36:37 -0800 | 
|---|---|---|
| committer | mitesh <mitesh@cumulusnetworks.com> | 2018-01-23 16:24:35 -0800 | 
| commit | 84915b0a15e32a51622f28b6bcafff58a4b02d6d (patch) | |
| tree | b832db0fc25d5f67e73f43138f1949c5a76b5a47 /lib/vrf.h | |
| parent | fb8384733f1865dbec3a8def0fb18ab4d78f0b47 (diff) | |
*: Handle VRF configuration when VRF gets inactivated and activated
A VRF is active only when the corresponding VRF device is present in the
kernel. However, when the kernel VRF device is removed, the VRF container in
FRR should go away only if there is no user configuration for it. Otherwise,
when the VRF device is created again so that the VRF becomes active, FRR
cannot take the correct actions. Example configuration for the VRF includes
static routes and EVPN L3 VNI.
Note that a VRF is currently considered to be "configured" as soon as the
operator has issued the "vrf <name>" command in FRR. Such a configured VRF
is not deleted upon VRF device removal, it is only made inactive. A VRF that
is "configured" can be deleted only upon operator action and only if the VRF
has been deactivated i.e., the VRF device removed from the kernel. This is
an existing restriction.
To implement this change, the VRF disable and delete actions have been modified.
Signed-off-by: Vivek Venkatraman <vivek@cumulusnetworks.com>
Reviewed-by:   Donald Sharp <sharpd@cumulusnetworks.com>
Reviewed-by:   Mitesh Kanjariya <mkanjariya@cumulusnetworks.com>
Reviewed-by:   Don Slice <dslice@cumulusnetworks.com>
Ticket: CM-18553, CM-18918, CM-10139
Reviewed By: CCR-7022
Testing Done:
1. vrf and pim-vrf automation tests
2. Multiple VRF delete and readd (ifdown, ifup-with-depends)
3. FRR stop, start, restart
4. Networking restart
5. Configuration delete and readd
Some of the above tests run in different sequences (manually).
Diffstat (limited to 'lib/vrf.h')
| -rw-r--r-- | lib/vrf.h | 17 | 
1 files changed, 16 insertions, 1 deletions
@@ -75,7 +75,8 @@ struct vrf {  	/* Zebra internal VRF status */  	u_char status; -#define VRF_ACTIVE     (1 << 0) +#define VRF_ACTIVE     (1 << 0) /* VRF is up in kernel */ +#define VRF_CONFIGURED (1 << 1) /* VRF is configured by user in frr */  	/* Interfaces belonging to this VRF */  	struct if_name_head ifaces_by_name; @@ -120,6 +121,20 @@ extern vrf_id_t vrf_name_to_id(const char *);  	} while (0)  /* + * Check whether the VRF is enabled. + */ +static inline int vrf_is_enabled(struct vrf *vrf) +{ +	return vrf && CHECK_FLAG(vrf->status, VRF_ACTIVE); +} + +/* check if the vrf is user configured */ +static inline int vrf_is_user_cfged(struct vrf *vrf) +{ +	return vrf && CHECK_FLAG(vrf->status, VRF_CONFIGURED); +} + +/*   * Utilities to obtain the user data   */  | 
