Which two statements about EVN are true? (Choose two.)
A. It supports IPv6 traffic.
B. It can support up to 16 VNs.
C. It uses redistribution to share routes between VNs.
D. It supports SSM only.
E. A configuration can be based on an existing VRF configuration
Answers B and D can be excluded, because EVN supports 32 VNs and there is no information about supporting only Source Specific Multicast (SSM) on Cisco websites.
We have A, C and E left. We all agree that E is true, so we have to choose between A and C.
ENV CAN support IPv6, but there is a strong restriction – in vnet global only, which makes it basically unusable for IPV6 environments. That would alone exclude it as an answer.
But let’s focus on C. Of course the documentation says that ENV uses route replication for shared services, but that is true only for the RIB on the router, on which the route replication takes place. The replicated route must be visible to other routers in the network, that’s why it MUST BE redistributed into IGP. So C is definitely true.
That gives us the correct answer: CE
Q.E.D.
CE Final answer
Restrictions for EVN as shown below:
An EVN trunk is allowed on any interface that supports 802.1q encapsulation, such as Fast Ethernet, Gigabit Ethernet, and port channels.
There are additional platform and line-card restrictions for an EVN trunk. Check Cisco Feature Navigator, http://www.cisco.com/go/cfn for supported platforms and line cards.
A single IP infrastructure can be virtualized to provide up to 32 virtual networks end-to-end.
If an EVN trunk is configured on an interface, you cannot configure VRF-Lite on the same interface.
OSPFv3 is not supported; OSPFv2 is supported.
The following are not supported by EVN:
IS-IS
RIP
Route replication is not supported with BGP
Certain SNMP set operations
The following are not supported on an EVN trunk:
Access control lists (ACLs)
BGP interface commands are not inherited
IPv6, except on vnet global
Network address translation (NAT)
NetFlow
Web Cache Communication Protocol (WCCP)
EVN uses route replication to share routes between VNs, then uses redistribution to propagate the routes in the VNs, so it is AE. IPv6 is supported in VNET global, so it is not unsupported.
“After routes are replicated from a different virtual network, those routes are propagated across each virtual network through existing redistribution into the Interior Gateway Protocol (IGP).”
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/evn/configuration/xe-3s/evn-xe-3s-book/evn-shared-svcs.html#GUID-B7C41C36-B688-47DE-9FA6-ADBB7C8D8F87
CE.
About C. For me C answer, we need read as, can Evn share routes via redistribution – answer yes.
In C no keyword _only_. So it right for me.
A – is not true, because only general rt cAn support for ipv6. It, s like unsupported.
https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/evn/configuration/xe-16-12/evn-xe-16-12-book/evn-overview.html?dtid=osscdc000283#GUID-AB46ACF8-0E49-433E-A459-C16E67D6D28D
The following are not supported on an EVN trunk:
Access control lists (ACLs)
BGP interface commands are not inherited
IPv6, except on vnet global
Network address translation (NAT)
NetFlow
Web Cache Communication Protocol (WCCP)
i think EVN do not support IPV6
Depending on whether VRF-Lite or EVN is implemented, route exchanges among VRFs are accomplished in one of the following ways:
==If VRF-Lite is implemented, route leaking is achieved via BGP by using the route import/export feature.
==If EVN is implemented, route replication is supported directly by the Routing Information Base (RIB); there is no dependency on BGP. After routes are replicated from a different virtual network, those routes are propagated across each virtual network through existing redistribution into the Interior Gateway Protocol (IGP).
ANSWER IS CE
Multi-VRF is available to support IPv6 VRFs. Networks that have dual stack VNs on access links, Multi-VRF for IPv6 VNs, and EVN for IPv4 VNs can be deployed concurrently.
AC
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/layer-3-vpns-l3vpn/whitepaper_c11-638769.html
Replicated routes are not redistributed automatically. Route redistribution into Interior Gateway Protocol (IGP) or Exterior Gateway Protocol (EGP) is required after route replication to propagate routes across each EVN so that remote users can access shared services. Figure 5 demonstrates a scenario where Yellow VN routes are replicated and then redistributed.
Provides a pure IP alternative to MPLS in enterprise networks for up to 32 VNs
Supports non-IP and IPv6 traffic through the EVN global table
AE
The answer is AE. The white paper says redistribution is not required.
AE
CE should be right:
https://www.cisco.com/c/en/us/products/collateral/ios-nx-os-software/layer-3-vpns-l3vpn/whitepaper_c11-638769.html