Objectives
The simulator ticks each one as soon as the network meets it.
From SRC ping 239.1.1.1 and read why PC4 misses the stream, then check show ip msdp peer 2.2.2.2 on R3.
R3 opens the session from 10.0.23.2, but R2 expects 3.3.3.3: add connect-source loopback0 to R3’s ip msdp peer 2.2.2.2.
On R3, show ip msdp summary: peer 2.2.2.2 is Up.
Ping 239.1.1.1 from SRC again: PC4 replies.
Before you start
An MSDP peer accepts a TCP connection only from the address it has configured for that peer. Without connect-source, a router sources the session from its outgoing interface, so a peer configured on a loopback address refuses it. Both ends must agree on both addresses, and each needs a unicast route to the other.
Concept
MSDP: sources in another PIM domain
Each PIM sparse-mode domain has its own RP, and an RP only learns the sources that register with it. MSDP (Multicast Source Discovery Protocol) peers RPs over TCP port 639, so a source in one domain is announced to the RPs of the others in a Source-Active (SA) message.
