Pass the Cisco CCNP Service Provider 350-501 Questions and answers with Dumpstech

The configuration shown is for the head-end router of a Cisco MPLS TE tunnel with segment routing. This setup involves commands related to segment routing and MPLS traffic engineering tunnels, such as “mpls traffic-eng tunnels”, “segment-routing mpls”, and “segment-routing prefix-sid-map advertise-local”. These commands configure the head-end router to effectively create and manage TE tunnels using segment routing. References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) - Cisco SPCOR Training & Certification.

https://community.cisco.com/t5/mpls/cisco-xr-rpl-destination-vs-destination-prefix/td-p/4587693

 The REST API command shown in the exhibit is a POST request to a specific URL, indicating that it is used to submit data to be processed to a specified resource. In this case, the resource is an XML file named “Descriptions.xml”. POST requests are used when submitting data to be processed by the resource identified by the URI. The nature of the process conducted on the submitted data depends on that particular URI. References: Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) - REST API section.

Remember that SSM is an extension of IP multicast where datagram traffic is forwarded only from explicitly joined multicast sources to receivers. It creates source-specific multicast distribution trees without shared trees.

The issue described indicates that the preferred BGP path for traffic destined to 192.168.1.1/32 is not being used. By applying a route-map with a higher Local Preference (LP) on R1 for the prefix 192.168.1.1/32, the BGP path attributes can be manipulated to prefer the path through R2. Local Preference is a BGP attribute that determines the preferred exit path out of an AS. A higher Local Preference value is preferred over a lower one. Therefore, configuring the route-map High-LP with a higher Local Preference on R1’s BGP peering with R2 will influence the BGP path selection process, ensuring that traffic for 192.168.1.1/32 prefers the path R3-R2-R1 as expected.

The configuration in Option C correctly sets up the interfaces for VLAN tag translation. On interface GigabitEthernet2, the command rewrite ingress tag translate 1-to-1 dot1q 21 changes the incoming VLAN tag from 12 to 21. Conversely, on interface GigabitEthernet3, the command rewrite egress tag translate 1-to-1 dot1q 12 changes the outgoing VLAN tag from 21 to 12. This setup ensures that traffic flowing from R1 to R2 and vice versa has the correct VLAN tags as required.

 Router R1 is configured as a stub area with the “no-summary” option, which means it will not receive summary LSAs (Type 3) from the Area Border Router (ABR). It will only have Type 1 (Router LSAs) and Type 2 (Network LSAs) in its OSPF database for the area it belongs to. Router R2 is configured as an NSSA (Not So Stubby Area), which allows it to import AS external routes as Type-7 LSAs. These Type-7 LSAs can then be converted to Type-5 LSAs by the ABR when propagated into other areas. Therefore, R2 has Types 1, 2, and 7 LSAs in its OSPF database.

Path Computation Element (Calculates paths through the network, keeps TE topology database information, sends path status updates)

Path computation Client (sends path calculation request, sends path creation request)

Path Computation Element (PCE)

Represents a software module (which can be a component or application) that enables the router to compute paths applying a set of constraints between any pair of nodes within the router’s TE topology database. PCEs are discovered through IGP.

Path Computation Client (PCC)

Represents a software module running on a router that is capable of sending and receiving path computation requests and responses to and from PCEs. The PCC is typically an LSR (Label Switching Router).

https://www.cisco.com/c/en/us/td/docs/routers/crs/softwa re/crs_r5-3/mpls/configuration/guide/b-mpls-cg53x-crs/b-mpls-cg53x-crs_chapter_0110.html#con_1279822

The issue is occurring in OSPF stub area 100 where the Ethernet link is down between routers RX and RY due to a cut fiber, leading to dropped traffic from CE site A to the hub site. Changing the OSPF area 100 type to stub on RZ can resolve these issues. In a stub area, OSPF routers use a default route to forward traffic to destinations outside the area, reducing the size of their routing tables. This would allow traffic from CE site A to be routed through RZ when the direct link between RX and RY is down.

R1

router ospf 10

redistribute static

int et0/0

ip ospf hello-interval 5

ip ospf dead-interval 10

ip ospf cost 15

ip ospf 10 area 0

copy run start

R2

router ospf 10

redistribute static

int et0/0

ip ospf hello-interval 5

ip ospf dead-interval 10

ip ospf cost 15

ip ospf 10 area 0

copy run start