5.3 : why pim on tunnel ?

why do we have to activate pim on tunnel interfaces of R2 and R5 ?

they are already pim neighbors via VLAN 258 : why is this not enough ?

thanks

Comments

  • If the tunnel is to be used for multicast traffic, ip pim will need to be enabled on the tunnel interface at each end, too.

    Darrell
  • Thanks Darrell, but you may want to read the lab tasks.

    R2 and R5 are already pim neighbors through their ethernet links.

    Multicast traffic can already use this ethernet link.

    But this ethernet link is in ospf area 1.
    Whereas tunnel interfaces are in ospf area 0.

    So I guess, RPF want mcast traffic to come from area 0.
    Could we have typed instead : ip mroute 0.0.0.0 0.0.0.0 e0/0 on R5 ?
  • Hello,

    the source IP when checked on R2 it is routed vial the tunnel interface

    Rack1R2#sh ip route 204.12.1.4
    Routing entry for 204.12.1.0/24
    Known via "ospf 100", distance 110, metric 11212, type extern 1
    Last update from 151.1.1.2 on Tunnel0, 01:10:26 ago
    Routing Descriptor Blocks:
    * 151.1.1.2, from 150.1.4.4, 01:10:26 ago, via Tunnel0
    Route metric is 11212, traffic share count is 1


    so you need to enable the PIM on the tunnel interfaces , also static mroute may work

    thanks
  • colleagues, why we have duplicates ?

    Rack1R4(config-if)#do p 239.39.39.39 re 10 so 204.12.1.4

    Packet sent with a source address of 204.12.1.4
     Quote:

    Reply to request 0 from 141.1.123.3, 56 ms
    Reply to request 0 from 141.1.123.3, 96 ms
    Reply to request 1 from 141.1.123.3, 56 ms
    Reply to request 1 from 141.1.123.3, 96 ms
    Reply to request 2 from 141.1.123.3, 56 ms
    Reply to request 2 from 141.1.123.3, 96 ms
    Reply to request 3 from 141.1.123.3, 56 ms
    Reply to request 3 from 141.1.123.3, 96 ms


    Rack1R4(config-if)#do p 225.25.25.25 re 10 so 204.12.1.4

    Packet sent with a source address of 204.12.1.4
     Quote:

    Reply to request 0 from 141.1.123.3, 60 ms
    Reply to request 0 from 141.1.123.3, 108 ms
    Reply to request 0 from 141.1.123.3, 80 ms
    Reply to request 1 from 141.1.123.3, 60 ms
    Reply to request 1 from 141.1.123.3, 100 ms
    Reply to request 1 from 141.1.123.3, 72 ms
    Reply to request 2 from 141.1.123.3, 56 ms
    Reply to request 2 from 141.1.123.3, 100 ms
    Reply to request 3 from 141.1.123.3, 56 ms
    Reply to request 3 from 141.1.123.3, 100 ms


    from R1 it seems ok - one reply to one request.
Sign In or Register to comment.