the RPF check was failing i think this is mostly becuase 126.96.36.199 is seen by R1 as RP as well
but it is not seen through the multicast link ( only though the unicast link) >> RPF failed
however if you stop the RP messages from beign exchanged between the two domains and allow only MSDP as the inter domain multicasting ( which is the best practice as will ) the 188.8.131.52 will not be aproblem as lon as you are using the directly connected interfaces between R3 and R1 as the MSDP connection source
in other words if you dont advertise it (33.33.) in MBGP your topology will work
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...