Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
- Multicast traffic for the shared mcast-groups is affected by the NVE Service-Policy even for replicated flows that exist non-NVE OIFs.
- Border Spine with an Up/Up NVE Interface - Under the interface configuration, a member VNI utilizes the same mcast-group as VTEPs connected to the Spine. - An ingress QOS policy is configured on the NVE interface with actions such as "set qos-group". - The ingress interface of the multicast BUM traffic also has a service-policy attached that performs a similar function such as 'set qos-group' interface Ethernet1/2 mtu 9216 service-policy type qos input Example-1 service-policy type queuing output Example-2 <<< Queuing policy is applied to ingress L3 from VTEP ip address 10.1.2.1/30 ip ospf network point-to-point no ip ospf passive-interface ip router ospf UNDERLAY area 0.0.0.1 ip pim sparse-mode no shutdown evpn multisite fabric-tracking interface nve1 service-policy type qos input VXLAN <<< QOS policy is also applied to NVE1 Type qos policy-maps ==================== policy-map type qos Example-1 class QoS_Customer_Topology_DSCP set qos-group 3 class QoS_Internet_Topology_DSCP set qos-group 2 policy-map type qos VXLAN class class-default <<<< Locally routed multicast will egress Group 4 instead of Groups 2 or 3. set cos 3 set qos-group 4
The following suggestions have been identified and will be added to the "VXLAN QOS" document for Nexus 9000 under "Guidelines and Limitations for VXLAN QOS". - If QOS policies are needed for intra-site BUM traffic for VNI with multicast underlay, and that multicast underlay group is also owned by a VNI defined on the BGW Spine, then the QOS policy must be applied to the NVE interface. QOS Policies applied to fabric interfaces will not modify these flows since the NVE interface acts as an incoming interface. - If QOS policies are needed for intra-site BUM traffic for VNI with multicast underlay, that multicast group is NOT owned by a VNI defined on the BGW Spine, and the VNI is not stretched on the BGW, then the QOS policy must be applied to a fabric interface. QOS Policies applied to the NVE interface will not modify these flows since the NVE is not considered an incoming interface. - If the NVE interface of the BGW Spine owns a multicast group used for BUM traffic within the local fabric, QOS policies cannot be applied to both the fabric interfaces and NVE interface to differentiate treatment of intra-site and inter-site flows for that multicast group."
This is expected behavior. The VXLAN QOS document will be updated to reflect that.