Solved: Re: BSR and selcting RP problem

burhan.agir · ‎10-08-2018

Hi,

I am using BSR for selecting auto RP and distribute on GNS3. I choose the O1 as RP and B1 as the backup RP. The BSR and RP information distribute between O1, A1, and B1 but other routers (B3, O3, A3, and A4) could not get this information. I could not find the reason!!!

I wrote "ip pim sparse-mode" command for all related interfaces.

I wrote "ip multicast-routing" command for all routers.

All static routing things are OK. All devices can ping the Loopback interfaces.

B1:

ip pim bsr-candidate Loopback0 1

ip pim rp-candidate Loopback0 priority 20

O1:

ip pim bsr-candidate Loopback0 1

ip pim rp-candidate Loopback0 priority 10

Note: I am using HSRP with second routers for redundancy. Example O1-O2.

paul driver · ‎10-09-2018

Hello

@Georg Pauwen did you apply a static mroute towards the physical pim peer of the edge rtr as the default static route on the edge rtr is pointing the the vip address of the Hrsp and this address is not pim peered as such the mc join requests from the edge rtr will get ignored

When an static mroute was applied @burhan.agir stated it began to work - so going forward the resolution I suggested was to try and use the hrsp pim redundancy feature instead if a static mroute

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

View solution in original post

paul driver · ‎10-08-2018

Hello

@burhan.agir wrote:

B1:

ip pim bsr-candidate Loopback0 1 <- equal

ip pim rp-candidate Loopback0 priority 20

O1:

ip pim bsr-candidate Loopback0 1<- equal

ip pim rp-candidate Loopback0 priority 10 <- preferred

01 is the RP specified via a priority value however it looks like you have the BSR being elected by the ip address of the loopback and not via a priority , The most preferred BSR in this case needs to be something other than 1

ip pim bsr-candidate Loopback0 100

Can you post the output from one of the rtrs that receiving not MC

sh ip pim rp mapping
sh ip pim bsr-router

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-08-2018

Hi Paul,

I think the place that you showed as equal is "hash mask length". Priority part is after that. Anyway, I gave a priority for bsr election.

O1:

O1#sh run | i cand
ip pim bsr-candidate Loopback0 1 10
ip pim rp-candidate Loopback0 priority 10

B1:

B1#sh run | i cand
ip pim bsr-candidate Loopback0 1 20
ip pim rp-candidate Loopback0 priority 20

O1:

O1#sh ip pim rp mapping
PIM Group-to-RP Mappings
This system is a candidate RP (v2)

Group(s) 224.0.0.0/4
RP 1.1.1.2 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 10, holdtime 150
Uptime: 00:12:04, expires: 00:02:00
RP 1.1.1.1 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 20, holdtime 150
Uptime: 00:11:02, expires: 00:02:01

O1#sh ip pim bsr-router
PIMv2 Bootstrap information
BSR address: 1.1.1.1 (?)
Uptime: 00:05:34, BSR Priority: 20, Hash mask length: 1
Expires: 00:01:37
This system is a candidate BSR
Candidate BSR address: 1.1.1.2, priority: 10, hash mask length: 1
Candidate RP: 1.1.1.2(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:27
Candidate RP priority : 10

B1:

B1#sh ip pim rp map
PIM Group-to-RP Mappings
This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)

Group(s) 224.0.0.0/4
RP 1.1.1.2 (?), v2
Info source: 1.1.1.2 (?), via bootstrap, priority 10, holdtime 150
Uptime: 00:12:49, expires: 00:01:43
RP 1.1.1.1 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 20, holdtime 150
Uptime: 00:14:02, expires: 00:01:44

B1#sh ip pim bsr
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 1.1.1.1 (?)
Uptime: 00:06:50, BSR Priority: 20, Hash mask length: 1
Next bootstrap message in 00:00:13
Candidate RP: 1.1.1.1(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:09
Candidate RP priority : 20
B1#

And you can see the other command outputs from other routers.

O3:

O3#sh ip pim rp mapping
PIM Group-to-RP Mappings

O3#sh ip pim rp
Group: 226.1.1.1, RP: 0.0.0.0
Group: 225.1.1.1, RP: 0.0.0.0
O3#sh ip pim bsr-router
PIMv2 Bootstrap information
O3#

A1: (There is no problem)

A1#sh ip pim rp mapping
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
RP 1.1.1.2 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 10, holdtime 150
Uptime: 00:11:33, expires: 00:02:21
RP 1.1.1.1 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 20, holdtime 150
Uptime: 00:11:41, expires: 00:02:18
A1#sh ip pim bsr
PIMv2 Bootstrap information
BSR address: 1.1.1.1 (?)
Uptime: 00:06:43, BSR Priority: 20, Hash mask length: 1
Expires: 00:01:59
A1#

A3:

A3#sh ip pim rp
Group: 225.1.1.1, RP: 0.0.0.0
A3#sh ip pim rp ma
PIM Group-to-RP Mappings

A3#sh ip pim bsr
PIMv2 Bootstrap information
A3#

Thanks,

paul driver · ‎10-08-2018

Hello

Do you have fulll reachability to all rtrs?
Is pim enabled on those rtrs interfaces, do you any acls that could be negating access

Are those intelligent switches if so do you have igmp and snooping enabled for any specific vlans

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-08-2018

Hello,

Yes. All routers can communicate with each other via static routing.

PIM is enabled for all physical and tunnel interfaces except WAN interfaces. There is no ACL.

Actually, these are dummy switches. I can just manage access/trunk and access VLAN.

Georg Pauwen · ‎10-08-2018

Hello,

it is unclear from your drawing how your HSRP is set up. Is that for LAN or WAN redundancy ?

Post the full configs of O1,O2, O3, as well as B1, B2, and B3.

burhan.agir · ‎10-08-2018

Hello,

All HSRP configuration is between first and second routers for LAN and WAN redundancy. For example O1-O2, B1-B2, A1-A2.

I added the whole configuration about devices except switches.

Thanks,

paul driver · ‎10-08-2018

Hello

You have the same tunnel addressing on both A1 -A2, B1-B2 routers?

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-08-2018

Hello,

Yes, it is. I want to use the first router as the active router. When the first router goes down, the second router takes the position as active. Is it block the learn RP IP address, you think?
Actually, the second router can learn or not the RP IP address is not important this step. I think the problem is that backside router could not learn the RP.

Thanks,

paul driver · ‎10-08-2018

hello

@burhan.agir wrote:
Hello,

Yes, it is. I want to use the first router as the active router. When the first router goes down, the second router takes the position as active. Is it block the learn RP IP address, you think?
Actually, the second router can learn or not the RP IP address is not important this step. I think the problem is that backside router could not learn the RP.

Thanks,

Well thats not the way to implement resiliency-

Do the "backside" routers has a pim neighbor towards the active wan rtr?
Can they reach the RP and BSR loopbacks?

Can you post the output of the following from one for the failing "backside" rtrs:
sh ip pim neighbor
sh ip rpf x.x.x.x (bsr)
sh ip rpf x.x.x.x (rp)

mrtrace (source loopback) (dest RP)
mrtrace (source loopback) (dest BSR)

traceroute (dest RP) source loopback x

traceroute (dest BSR) source loopback x
deb ip pim bsr

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-08-2018

Hello,

Backside routers have no pim neighbor with WAN router.

Yes, they can reach (ping) RP and BSR router.

I took outputs from A3 router. You can find in attachment. At the moment RP and BSR IP address on the system is below.

B1#
B1#sh ip pim rp ma
PIM Group-to-RP Mappings
This system is a candidate RP (v2)
This system is the Bootstrap Router (v2)

Group(s) 224.0.0.0/4
RP 1.1.1.2 (?), v2
Info source: 1.1.1.2 (?), via bootstrap, priority 10, holdtime 150
Uptime: 00:26:34, expires: 00:01:53
RP 1.1.1.1 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 20, holdtime 150
Uptime: 00:26:42, expires: 00:01:46
B1#

B1#
B1#sh ip pim bsr
PIMv2 Bootstrap information
This system is the Bootstrap Router (BSR)
BSR address: 1.1.1.1 (?)
Uptime: 00:26:46, BSR Priority: 20, Hash mask length: 1
Next bootstrap message in 00:00:21
Candidate RP: 1.1.1.1(Loopback0)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 00:00:14
Candidate RP priority : 20
B1#

Thanks,

paul driver · ‎10-09-2018

Hello

Can you perform the same tests again on A3 but sourcing from GigabitEthernet0/0 not loopback 0

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-09-2018

Hello,

When I did the test with Gi0/0 all outputs are ok. But RP and BSR IP address still not learned.

A3#
A3#mtrace 10.52.100.1 1.1.1.1
Type escape sequence to abort.
Mtrace from 10.52.100.1 to 1.1.1.1 via RPF
From source (?) to destination (?)
Querying full reverse path...
0 1.1.1.1
-1 2.2.2.1 ==> 2.2.2.1 PIM/Static [10.52.0.0/16]
-2 2.2.2.2 ==> 10.52.100.52 PIM_MT [10.52.100.0/24]
-3 10.52.100.1
A3#
*Oct 9 11:24:57.311: PIM-BSR(0): bootstrap (1.1.1.1) on non-RPF path GigabitEthernet0/0 or from non-RPF neighbor 10.52.100.51 discarded
A3#

A3#
A3#mtrace 10.52.100.1 1.1.1.2
Type escape sequence to abort.
Mtrace from 10.52.100.1 to 1.1.1.2 via RPF
From source (?) to destination (?)
Querying full reverse path...
0 1.1.1.2
-1 1.1.1.9 ==> 1.1.1.9 PIM/Static [10.52.0.0/16]
-2 1.1.1.10 ==> 10.52.100.52 PIM_MT [10.52.100.0/24]
-3 10.52.100.1
A3#

A3#
A3#traceroute 1.1.1.1 source gi 0/0
Type escape sequence to abort.
Tracing the route to 1.1.1.1
VRF info: (vrf in name/id, vrf out name/id)
1 10.52.100.52 64 msec 28 msec 28 msec
2 2.2.2.1 80 msec 108 msec 92 msec
A3#

A3#
A3#traceroute 1.1.1.2 source gi 0/0
Type escape sequence to abort.
Tracing the route to 1.1.1.2
VRF info: (vrf in name/id, vrf out name/id)
1 10.52.100.52 20 msec 28 msec 28 msec
2 1.1.1.9 88 msec 92 msec 88 msec
A3#

paul driver · ‎10-09-2018

Hello

A3#sh ip pim ne
PIM Neighbor Table
10.52.100.52      GigabitEthernet0/0       00:16:18/00:01:32 v2    1 / S P G
10.52.100.2       GigabitEthernet0/0       00:16:18/00:01:37 v2    1 / S P G
10.52.100.53      GigabitEthernet0/0       00:16:18/00:01:03 v2    1 / DR S P G

You dont have a pim relationship with the vip address just the physical address -

Can you try adding the following to A3 and test again
ip mroute 0.0.0.0 0.0.0.0 10.52.100.52

Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

burhan.agir · ‎10-09-2018

Hello,

It's done! But this IP address is physical. When the router 1 goes down I could not reach this IP address. Should I write another static route with a higher preference for router2 physical IP address?

A3#
A3#sh run | i route
ip mroute 0.0.0.0 0.0.0.0 10.52.100.52
ip route 0.0.0.0 0.0.0.0 10.52.100.51
A3#
A3#
A3#sh ip pim ne
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
P - Proxy Capable, S - State Refresh Capable, G - GenID Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
10.52.100.2 GigabitEthernet0/0 00:09:51/00:01:42 v2 1 / S P G
10.52.100.52 GigabitEthernet0/0 00:09:53/00:01:20 v2 1 / S P G
10.52.100.53 GigabitEthernet0/0 00:09:54/00:01:18 v2 1 / DR S P G
A3#
A3#sh ip pim rp ma
PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4
RP 1.1.1.2 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 10, holdtime 150
Uptime: 00:06:41, expires: 00:01:17
RP 1.1.1.1 (?), v2
Info source: 1.1.1.1 (?), via bootstrap, priority 20, holdtime 150
Uptime: 00:06:41, expires: 00:01:15
A3#
A3#
A3#sh ip pim bsr
PIMv2 Bootstrap information
BSR address: 1.1.1.1 (?)
Uptime: 00:06:45, BSR Priority: 20, Hash mask length: 1
Expires: 00:00:55
A3#
A3#