Regarding the MTU value of MP-BGP EVPN control plane packets in Cisco ACI, which statement about communication between spine nodes in different sites is true?
Regarding the MTU value of MP-BGP EVPN control plane packets in Cisco ACI, which statement about communication between spine nodes in different sites is true?
Spine nodes in a Cisco ACI environment generate 9000-byte packets by default to exchange endpoint routing information over the MP-BGP EVPN control plane. Therefore, the Inter-Site Network (ISN) must support at least 9000-bytes packets to ensure successful communication between spine nodes in different sites.
Correct answer is A https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739609.html Excerpt: MTU of MP-BGP control-plane communication between spine nodes in different sites: By default, the spine nodes generate 9000-byte packets for exchanging endpoint routing information. If that default value is not modified, the ISN must support an MTU size of at least 9000 bytes
I agree, the question is about exchanging endpoint routing information (i.e. control plane traffic) *between* spines in different sites, not local endpoint to spine traffic for which the 9100 byte MTU applies to.
It is D from the link you give => "Maximum MTU of the frames generated by the endpoints connected to the fabric: If the endpoints are configured to support jumbo frames (9000 bytes), then the ISN should be configured with at least a 9100-byte MTU value. If the endpoints are instead configured with the default 1500-byte value, then the ISN MTU size can be reduced to 1600 bytes"
@Jey10; what you have written is about Data Plane MTU. The question is about Control plane MTU. So the answer is A as therufus said
MTU of MP-BGP control-plane communication between spine nodes in different sites: By default, the spine nodes generate 9000-byte packets for exchanging endpoint routing information. If that default value is not modified, the ISN must support an MTU size of at least 9000 bytes, otherwise the exchange of control-plane information across sites would not succeed (despite being able to establish MP-BGP adjacencies). https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739609.html
Correct answer is A. The question is specific for control plane traffic as per the CISCO documentation the MTU on both spines and IPN devices must support 9000 bytes at least. The 9100 MTU applies to data plane traffic (VXLAN and 8021q header included).
Maximum transmission unit (MTU) of Multiprotocol Border Gateway Protocol (MP-BGP) Ethernet Virtual Private Network (EVPN) control plane communication between spine nodes in different sites - By default, the spine nodes generate 9000-byte packets to exchange endpoint routing information. If that default value is not modified, the Inter Site Network (ISN) must support an MTU size of at least 9100 bytes. In order to tune the default value, modify the corresponding system settings in each APIC domain.
This question has two answers on the internet. But if you want to support endpoint traffic of a MTU of 9000, it is required to increase the MTU to at least 9100 on the ISN. So what is this question about? Something that is minimal required for the MP-BGP protocol to work? Or an recommended setup looking further than only the communication between Spines. I would like to pick MTU 9100 for the ISN, but not sure if it is a trick question. LINK 1 = MTU 9100 https://www.cisco.com/c/en/us/support/docs/cloud-systems-management/application-policy-infrastructure-controller-apic/214270-configure-aci-multi-site-deployment.html LINK 2 = MTU 9000 https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739609.html
A is the right answer as per the link https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-739609.html
No mentioning of supporting jumbo frames within the fabric -> A.
Answer is D. While it's true the question is about the control plane and a mtu of 9000 is suitable. For the data plane you need to configure 9100 for mtu. In a real world environment you need to account for the data plane and go with the highest value. It could be A, but it's a technically either way.
Difficult question but I am swaying towards A rather than B due to the fact it mentions control plane within the question...
From ACI Multi-site white paper: The MTU of MP-BGP control-plane communication between spine nodes in different sites: By default, the spine nodes generate 9000-byte packets for exchanging endpoint routing information. If that default value is not modified, the ISN must support an MTU size of at least 9000 bytes; otherwise, the MP-BGP exchange of control-plane information across sites would not succeed.
Here the ask is about control plane so answer is A. If it was for data plane then answer would be D.
IPN requirements for a Remote Leaf solution are as follows: MTU: The solution must support an end-to-end MTU that is at least 100 bytes higher than that of the endpoint source traffic. Assuming that 1500 bytes has been configured for data plane MTU, Remote Leaf can be deployed using a minimum MTU of 1600 bytes. An IPN MTU this low, however, necessitates that ACI administrators lower the ACI fabricwide control plane MTU, which is 9000 bytes by default. https://www.ciscopress.com/articles/article.asp?p=3150964&seqNum=3
The minimum MTU value to configure in the ISN depends on two factors: ● The maximum MTU of the frames generated by the endpoints connected to the fabric: If the endpoints are configured to support jumbo frames (9000 bytes), then the ISN should be configured with at least a 9050-byte MTU value. If the endpoints are instead configured with the default 1500-byte value, then the ISN MTU size can be reduced to 1550 bytes.
D is correct!
Maximum MTU of the frames generated by the endpoints connected to the fabric: If the endpoints are configured to support jumbo frames (9000 bytes), then the ISN should be configured with at least a 9100-byte MTU value. If the endpoints are instead configured with the default 1500-byte value, then the ISN MTU size can be reduced to 1600 bytes. ● MTU of MP-BGP control-plane communication between spine nodes in different sites: By default, the spine nodes generate 9000-byte packets for exchanging endpoint routing information. If that default value is not modified, the ISN must support an MTU size of at least 9000 bytes, otherwise the exchange of control-plane information across sites would not succeed (despite being able to establish MP-BGP adjacencies). The default value can be tuned by modifying the corresponding system settings in each APIC domain
the ISN mtu value needed depends on whether you need jumbo frame support for endpoint or not. In this question it does not say anything about endpoint jumbo frame support, in this case 9000 is enough for ISN control plane packets
A is correct. We are asked exactly about the control plane traffic between sites, not about the size of frames of the EPs connected to the fabric. Link provided by therufus is clearly describing that.
I changed my mind to D. However there is some documentation that is confusing, some CISCO documents state it should be 9000 whereas others states it should be 9100.