10-3 - Troubleshoot PE-to-CE Connectivity

Question 1

T/F: While you are testing PE-to-CE connectivity, you can use the link-local IPv6 address of the configured IPv6 address on interfaces that connect both devices to test Layer 3 communication.

Answer 1

True

Question 2

IOS-XE Command:
show ipv6 cef vrf [vrf-name] [prefix/mask] detail

Answer 2

look for details for a specific IPv6 prefix

Question 3

IOS-XE Command:
show mpls forwarding-table [bgp-next-hop]

Answer 3

verify the label forwarding information base (LFIB) table entry for the remote BGP peer and validate label swapping where the outer label displays.

Question 4

IOS-XR Command:
show cef vrf [vrf-name] [prefix/mask]

Answer 4

look for details for a specific IPv6 prefix

Question 5

IOS-XR Command:
show mpls forwarding-table prefix [bgp-next-hop/32]

Answer 5

verify the LFIB table entry for the remote BGP peer and validate label swapping where outer label displays

Question 6

IOS-XE Command:
show ipv6 route vrf [vrf-name]

Answer 6

Show the RIB entries corresponding to a particular VRF

Question 7

What is true about issues with PE-to-CE connectivity?

A. Routing between a CE router and its PE router uses a routing protocol that is VRF-aware.
B. The CE redistributes IGP routes into MP-EBGP address-family IPv6.
C. Static routes are not supported because they are not VRF-aware.
D. At the CE, routes are installed in the VRF and forwarded to the remote CEs.

Answer 7

A