Hi Aaradhana  You will have to run command for neighbor R3 , not for R6 on  R4 . Because r4 is advertising routes to R3 of R6 . So , you have to run following command on R4 to modify next-hop -- R4(config)#router bgp 12345 R4(config-router)#neighbor 123.3.3.3  next-hop self After that clear the BGP process with the following command --- R4# clear ip bgp * soft Hope it will be helpful.... (more)

Hi Aaradhana  You will have to run command for neighbor R3 , not for R6 on  R4 . Because r4 is advertising routes to R3 of R6 . So , you have to run following command on R4 to modify next-hop -- R4(config)#router bgp 12345 R4(config-router)#neighbor 123.3.3.3  next-hop self After that clear the BGP process with the following command --- R4# clear ip bgp * soft Hope it will be helpful.... (more)

Hi Aaradhana  You will have to run command for neighbor R3 , not for R6 on  R4 . Because r4 is advertising routes to R3 of R6 . So , you have to run following command on R4 to modify next-hop -- R4(config)#router bgp 12345 R4(config-router)#neighbor 123.3.3.3  next-hop self After that clear the BGP process with the following command --- R4# clear ip bgp * soft Hope it will be helpful.... (more)

Hi Monty, It is not allowing me to enter tag with a non integer value. That is why I tried with 1111.  I have applied a route-map on R2 to set tag 2222 and I can see that the same tag is applied when I check routes for 2.x.x.x network on R4. Only problem is that route-map applied on R4 is not denying the routes out from R4. Will PBR work if applied on the interface?... (more)

Thanks for the clear explanation ! I will try this and let you know.

Thanks for the clear explanation ! I will try this and let you know.

Thanks for the clear explanation ! I will try this and let you know.

  Hi As you mentioned here that packets are taking path from both R3 and R4 because of same metric . The reason here is that the whenever a cisco router forward traffic it will match the destination ip address in routing table and in which longest prefix match , it will send packet by that path . In this task , R1 and R2 receive R5 loopback on /24 from both R3 and R4 , so whenever they will gen... (more)

  Hi As you mentioned here that packets are taking path from both R3 and R4 because of same metric . The reason here is that the whenever a cisco router forward traffic it will match the destination ip address in routing table and in which longest prefix match , it will send packet by that path . In this task , R1 and R2 receive R5 loopback on /24 from both R3 and R4 , so whenever they will gen... (more)

  Hi As you mentioned here that packets are taking path from both R3 and R4 because of same metric . The reason here is that the whenever a cisco router forward traffic it will match the destination ip address in routing table and in which longest prefix match , it will send packet by that path . In this task , R1 and R2 receive R5 loopback on /24 from both R3 and R4 , so whenever they will gen... (more)

  Hi As you mentioned here that packets are taking path from both R3 and R4 because of same metric . The reason here is that the whenever a cisco router forward traffic it will match the destination ip address in routing table and in which longest prefix match , it will send packet by that path . In this task , R1 and R2 receive R5 loopback on /24 from both R3 and R4 , so whenever they will gen... (more)

  Hi As you mentioned here that packets are taking path from both R3 and R4 because of same metric . The reason here is that the whenever a cisco router forward traffic it will match the destination ip address in routing table and in which longest prefix match , it will send packet by that path . In this task , R1 and R2 receive R5 loopback on /24 from both R3 and R4 , so whenever they will gen... (more)

Thanks for the answer Monty.After implementation of Task 2, R1 can reach R5 via 123.45.67.2 (R3), since setting higher delay value on all the interfaces of R4 makes its metric higher than R3.Hence in routing table, we can see only R3 as the next-hop addressAfter removing delay D        123.45.67.12/30 [90/30720] via 123.45.67.6, 00:00:30, FastEthernet0/1After increasing delayD        123... (more)

Hello Aaradhana joshi ,  No , you don't have to remove all the interface setting configured in Task 2 , while performing Task 3 (A) . Because from R3 , you are sending individual routes and from R4 sending summary routes , so interface characteristics doesn't effect this task . And in task 3 , we are not  manipulating the path .   But as given in guidelines for the task is recomm... (more)

Hello Aaradhana joshi ,  No , you don't have to remove all the interface setting configured in Task 2 , while performing Task 3 (A) . Because from R3 , you are sending individual routes and from R4 sending summary routes , so interface characteristics doesn't effect this task . And in task 3 , we are not  manipulating the path .   But as given in guidelines for the task is recomm... (more)