MSDP scenario

Hi guys

I have an issue with this scenario. It cannot establish multicast community between sw1 and sw2 because R2 has null in outgoing interface list. SW2 joined the group 232.1.1.1 Any ideas?

R2#sh ip mroute

(*, 232.1.1.1), 01:25:13/stopped, RP 150.1.24.2, flags: SP
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list: Null

(10.1.37.7, 232.1.1.1), 00:19:27/00:01:32, flags: PA
  Incoming interface: Serial0/0.1, RPF nbr 150.1.12.1
  Outgoing interface list: Null

R4#sh ip mr
(*, 232.1.1.1), 6d00h/00:03:26, RP 150.1.24.4, flags: SJCL
  Incoming interface: Null, RPF nbr 0.0.0.0, Mroute
  Outgoing interface list:
    Loopback0, Forward/Sparse, 6d00h/00:02:52
    Serial0/0.1, Forward/Sparse, 00:06:00/00:03:26

(10.1.37.7, 232.1.1.1), 00:00:46/00:02:14, flags: LM
  Incoming interface: FastEthernet0/0, RPF nbr 150.1.24.2
  Outgoing interface list:
    Loopback0, Forward/Sparse, 00:00:47/00:02:51
    Serial0/0.1, Forward/Sparse, 00:00:47/00:03:25

R4#sh ip msdp sa-cache
MSDP Source-Active Cache - 1 entries
(10.1.37.7, 232.1.1.1), RP 150.1.24.2, BGP/AS 0, 00:24:00/00:05:45, Peer 150.1.24.2

Comments

  • OK. I figured it out. I missed sparse-mode interface configuration between R2 and R4 so that's why R4 did not send pim join through E0/0 and R2 had null in OIL.

    Best

  • OK. I figured it out. I missed sparse-mode interface configuration between R2 and R4 so that's why R4 did not send pim join through E0/0 and R2 had null in OIL.

    Best

     

    i've fallen in the same error 2 months later! [Y]

    i think this is due to the fact that when i read about msdp i thought this was the only necessary protocol between domains.

    i had OUI list null in R3, but first ping from sw1 to sw2 always worked fine, only yhe first ping packet came back, this is still unclear for me [:^)]

    anyway, going ahead, step by step [8-|]

Sign In or Register to comment.