Question 340
A core network change board wants to avoid: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. Which ongoing safeguard fits best?
Explanation
Correct Answer
Document the selected inter-AS option and verify service labels at each boundary. This helps prevent recurrence of the issue: An inter-AS L3VPN reaches the first provider but customer prefixes vanish at the AS boundary because VPNv4 routes and label context are not exchanged under the chosen inter-AS model. Acceptance evidence should be: A remote customer VRF imports the approved prefix and delivers labeled packets across both provider ASes.
Incorrect Answers
Contract-test route-target separation before onboarding a new tenant EVI. That is a sensible control for ANOTHER scenario: A provider imports all EVPN routes from every retail tenant into one MAC-VRF, and identical MAC addresses cause cross-customer service confusion. It is less targeted to this issue than: Document the selected inter-AS option and verify service labels at each boundary.
Track provider tree membership and packet replication under subscriber growth. That is a sensible control for ANOTHER scenario: A provider deploys mVPN for an IPTV customer but replicates each source stream individually to every access PE even when a shared provider multicast tree is available. It is less targeted to this issue than: Document the selected inter-AS option and verify service labels at each boundary.
Include both IGMP and MLD listener tests on dual-stack access nodes. That is a sensible control for ANOTHER scenario: An IPv6 multicast receiver joins an MLDv2 group, but the adjacent router polls only IGMP state and reports no listeners. It is less targeted to this issue than: Document the selected inter-AS option and verify service labels at each boundary.