5.3 Multicast Test. Sourcing the test ping from Serial0/0

Hi, 

Can anyone tell me why the question and solution specifically used fa0/1.52's IP address and didn't just allow R5 to source it from both PIM enabled interfaces?

If both interfaces source a ping then it fails from 174.1.145.5 i.e. Serial 0/0.  The mroute states on the respective devices show that for 174.1.145.5,226.0.0.4 there's no entry in the OIL facing back to R5' Serial interface:

 

R5 has:

(174.1.145.5, 226.0.0.4), 00:02:18/00:01:11, flags: PFT

  Incoming interface: Serial0/0, RPF nbr 0.0.0.0, Registering

  Outgoing interface list: Null

But there is for 192.10.1.5

(192.10.1.5, 226.0.0.4), 00:02:18/00:01:41, flags: FT

  Incoming interface: FastEthernet0/1.52, RPF nbr 0.0.0.0

  Outgoing interface list:

    Serial0/0, Forward/Sparse-Dense, 00:02:20/00:03:05

 

R1, the RP, has:

 

(174.1.145.5, 226.0.0.4), 00:00:25/00:02:58, flags: PJT

  Incoming interface: Serial0/0, RPF nbr 174.1.145.5

  Outgoing interface list: Null

 

(192.10.1.5, 226.0.0.4), 00:00:23/00:03:09, flags: T

  Incoming interface: Serial0/0, RPF nbr 174.1.145.5

  Outgoing interface list:

    Serial0/0, 174.1.145.4, Forward/Sparse-Dense, 00:00:23/00:03:08

 

Whereas R4 has only the entry for 174.1.145.5:

 

(174.1.145.5, 226.0.0.4), 00:03:15/00:02:44, flags: LFT

  Incoming interface: Serial0/0, RPF nbr 0.0.0.0

  Outgoing interface list:

    FastEthernet0/0, Forward/Sparse-Dense, 00:03:15/00:02:33

 

 

 

Even when the ping is sources as per the SG there's still no mroute entry for 192.10.1.5,226.0.0.4?

This had me trying to get it to work from Serial0/0 but couldn't.

Hopefully this is something I've missed and should know.

Thanks.

Sign In or Register to comment.