[TRM] Implement VRF EVPN-Mcast Support in Terraform Provider #392
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for TRM VRF EVPN-Mcast configuration in the Terraform Provider.
Overview
This PR adds support for Tenant Routed Multicast (TRM) VRF EVPN-Multicast configuration in the
iosxe_vrfresource in the Terraform Provider.This extends the
iosxe_vrfresource with 8 new EVPN-Multicast-related attributes:New Attributes
ipv4_evpn_mcast_mdt_default_addressipv4_evpn_mcast_anycastipv4_evpn_mcast_data_addressipv4_evpn_mcast_data_mask_bitsipv6_evpn_mcast_mdt_default_addressipv6_evpn_mcast_anycastipv6_evpn_mcast_data_addressipv6_evpn_mcast_data_mask_bitsYANG Paths
address-family/ipv4/evpn-mcast/mdt-def-addraddress-family/ipv4/evpn-mcast/anycastaddress-family/ipv4/evpn-mcast/data/data-addraddress-family/ipv4/evpn-mcast/data/mask-bitsaddress-family/ipv6/evpn-mcast/mdt-def-addraddress-family/ipv6/evpn-mcast/anycastaddress-family/ipv6/evpn-mcast/data/data-addraddress-family/ipv6/evpn-mcast/data/mask-bitsIOS-XE Version Support
Changes
gen/definitions/vrf.yamlinternal/provider/model_iosxe_vrf.gointernal/provider/resource_iosxe_vrf.gointernal/provider/resource_iosxe_vrf_test.godocs/resources/vrf.mdNote on Acceptance Test Exclusion
The new EVPN-mcast attributes are tagged with
exclude_test: truein the resource definition. This is intentional and necessary because:Mutual Exclusivity: The
evpn-mcastconfiguration is mutually exclusive with traditionalmdt(Multicast Distribution Tree) configuration under the same VRF address-family. The existing acceptance tests already validate the traditional MDT attributes, and attempting to configure both simultaneously results in a device error:"inconsistent value: Device refused one or more commands".Fabric Prerequisites: EVPN-mcast requires a fully configured EVPN/VXLAN fabric environment including VNID configuration, EVPN instance, NVE interface, BGP EVPN peering, and multicast underlay.
The YANG path mappings have been validated against the IOS-XE 17.15.1 YANG models.
Current Caveats to Function and Support
IMPORTANT:
Provider support for the
vnid <vnid_number> evpn-instance vni <nve_l3vni_number> core-vlan <vlan_number>CLI command (vrf) does not yet exist. Support for this command is a prerequisite to the new attributes introduced in this PR.Related Issues
Closes: Issue 394 (Internal)