MSDP Query

Answered Question
Dec 19th, 2009
User Badges:

In MSDP is it required that the peering be done with another RP only ??? or supposing i have R1 in AS 100 (Being the Rp of that AS) has a MBGP peering with R2 in AS 200 (which is not the Rp on the AS). R3 which is behind R2 in AS 200 is the RP.for the AS


Thanks.


Ryel

Correct Answer by Marwan ALshawi about 7 years 7 months ago

solved


is this what you were looking for

R5#ping 230.0.0.1 source lo0

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 230.0.0.1, timeout is 2 seconds:
Packet sent with a source address of 55.55.55.55

Reply to request 0 from 31.0.0.1, 328 ms
Reply to request 0 from 16.0.0.2, 536 ms


i did the follwoing changes to ur config


R3:


address-family ipv4 multicast
network 33.33.33.33 mask 255.255.255.255


becuase in R1:


*Dec 20 23:36:07.899: MSDP(0): 31.0.0.2: Peer RPF check failed for 33.33.33.33,
used IBGP route's peer 0.0.0.0


Then


*Dec 20 23:40:35.035: MSDP(0): 31.0.0.2: Peer RPF check passed for 33.33.33.33,
used EMBGP peer


again in R3:


access-list 10 permit 224.0.0.0 7.255.255.255
access-list 10 permit 230.0.0.0 0.255.255.255


ip pim send-rp-discovery Loopback0 scope 255 group-list 10


also i added default route from R# to R5 to make sure the subnet reachable from remote ssites

by the way looks like you configured R1 and R6 with the group 230.0.0.1 becuase the replay above from both of them


good luck

please if helpful Rate

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Reza Sharifi Sat, 12/19/2009 - 21:38
User Badges:
  • Super Bronze, 10000 points or more
  • Cisco Designated VIP,

    2017 LAN

Hello Ryel,

RP.for the AS>


Yes, you can connect to R2 in AS 200, but you have to use your local interface as the source.


Example:


ip msdp peer 192.168.1.4 connect-source ethernet 0/0 remote-as 200


Please refer to this command reference guide for more info and example:


http://www.cisco.com/en/US/docs/ios/ipmulti/command/reference/imc_03.html#wp1056138


HTH

Reza

ryel.dsouza Sun, 12/20/2009 - 02:43
User Badges:

My setup is like this R5 & R3 (Rp) in AS100 & R1 & R6(RP) in AS200. R3 & R1 are having a mbgp peering. Problem is multaiacst traffic generated from R5 for 230.0.0.1 is not reaching R6 lo0 in AS 200. Have added the run config kindly have a look and please help.


Thanks


Ryel

Attachment: 
Marwan ALshawi Sun, 12/20/2009 - 02:55
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

can you put your diagram please


is this lab test ?

ryel.dsouza Sun, 12/20/2009 - 03:05
User Badges:

yes it is a lab test


Setup Is


R5 s1/1 ---> R3 s1/1 ----> R3 s1/2 -----> R1 s1/2 ----->  R1 s1/3 ------> R6 s1/3


Kindly Help.



Ryel

Marwan ALshawi Sun, 12/20/2009 - 03:16
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

you are using


ip msdp peer 31.0.0.1 connect-source Serial1/0


where is s1/0 in the diagram you sent me ?


i can see you trying to use another link bewteen R1 and R3 andyou tying to get RPF check thorugh multicast BGP

logicaly this is valid

the question is

can you make sure your MSDP peer is up

show ip msdp peer


and when you do ping do  debug ip msdp peer route and see the if the SA messages are exchanged about the source or not between the two MSDP peers

by the way you d not need MBGP between R1- R6 or R5 R3 as they have only one link between them OSPF enough to get the normal route

and make sure there is unicast routing as well default route will be enoguh between the two ASs


by the way if you using second link between R1 and R3 using MBGP make sure you recieve the route through MBGP


do

show ip bgp ipv4 multicast


good luck

ryel.dsouza Sun, 12/20/2009 - 03:46
User Badges:

It Seems my MSDP peering are up but some how multicast traffic traffic is not reaching R6 & yes there is a second link connecting from R3 s1/0 to R1 s1/0 for rpf check.



R1 (sh ip msdp sum)


Peer Address     AS    State    Uptime/  Reset     SA    Peer Name
                                Downtime Count              Count
31.0.0.2         100   Up       05:15:52 0                  0     ?
16.0.0.2         200   Up       01:38:30 0                  0     ?
R1(config)#


R3 (sh ip msdp sum)


MSDP Peer Status Summary
Peer Address     AS    State    Uptime/  Reset SA    Peer Name
                                Downtime Count          Count
31.0.0.1         100   Up       05:17:02 0             0          ?


R6 (sh ip msdp sum)


MSDP Peer Status Summary
Peer Address     AS    State    Uptime/  Reset SA    Peer Name
                                Downtime Count          Count
16.0.0.1         200   Up       01:41:22 0               0     ?
R6#




R6 (sh ip bgp ipv4 multicast)



BGP table version is 4, local router ID is 66.66.66.66
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
              r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete

   Network          Next Hop            Metric LocPrf Weight Path
*>i55.55.55.0/24    16.0.0.1                 0    100      0 100 i                  <------------------------- Advertised in R5 bgp address family
R6#

Correct Answer
Marwan ALshawi Sun, 12/20/2009 - 04:37
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

solved


is this what you were looking for

R5#ping 230.0.0.1 source lo0

Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 230.0.0.1, timeout is 2 seconds:
Packet sent with a source address of 55.55.55.55

Reply to request 0 from 31.0.0.1, 328 ms
Reply to request 0 from 16.0.0.2, 536 ms


i did the follwoing changes to ur config


R3:


address-family ipv4 multicast
network 33.33.33.33 mask 255.255.255.255


becuase in R1:


*Dec 20 23:36:07.899: MSDP(0): 31.0.0.2: Peer RPF check failed for 33.33.33.33,
used IBGP route's peer 0.0.0.0


Then


*Dec 20 23:40:35.035: MSDP(0): 31.0.0.2: Peer RPF check passed for 33.33.33.33,
used EMBGP peer


again in R3:


access-list 10 permit 224.0.0.0 7.255.255.255
access-list 10 permit 230.0.0.0 0.255.255.255


ip pim send-rp-discovery Loopback0 scope 255 group-list 10


also i added default route from R# to R5 to make sure the subnet reachable from remote ssites

by the way looks like you configured R1 and R6 with the group 230.0.0.1 becuase the replay above from both of them


good luck

please if helpful Rate

ryel.dsouza Sun, 12/20/2009 - 07:08
User Badges:

how come the rpf was failing at R1 did not even notice it was going on.

Marwan ALshawi Sun, 12/20/2009 - 15:29
User Badges:
  • Purple, 4500 points or more
  • Community Spotlight Award,

    Best Publication, December 2015

i think in your case the router using thier loopbacks as the sroutrce of MSDP (R3)  not sure but i have to see the debug again but this was the issue

and also u need a reachability between the two domains

the best way is to injuct default routes to R5 and R6 thorugh ospf or bgp


try to use the originator-id command and put the required interface ip address and see if the RPF pass or not


good luck with your study and i am glad its working now

Actions

This Discussion