BSR Filtering can be done by lowering the priority value ("zero") of the BSR -
candidate. The higher the BSR priority value the more preferred the BSR.
Secondly it can be done by using
ip pim bsr-border @ the interface level
Regards,
Mohammad A Paracha
________________________________
From: "[email protected]"
<[email protected]>
To: [email protected]
Sent: Sun, September 5, 2010 8:06:08 PM
Subject: CCIE_RS Digest, Vol 56, Issue 24
Send CCIE_RS mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://onlinestudylist.com/mailman/listinfo/ccie_rs
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CCIE_RS digest..."
Today's Topics:
1. (no subject) (Finger Fehler)
2. BSR Filtering (Morgan C)
3. Vol1-LAB13-TASK13.12 - Thoughts? (Jason Maynard)
----------------------------------------------------------------------
Message: 1
Date: Sun, 5 Sep 2010 15:59:25 -0400
From: Finger Fehler <[email protected]>
To: [email protected]
Cc: [email protected], [email protected]
Subject: [OSL | CCIE_RS] (no subject)
Message-ID:
<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
http://zoguvawu.tripod.com/difise.html S atis fyYour GirlsA llNi
ghtWit hNoBr eaks! WeOff erYouPi lulesFo rSup erLo vemaking !
Turn oyour girl on and satsify her for houars! With our cures your
male sertngth is unleimited! eExpress web-ordeirng of maole btosoing
remidees. surpriSe your gairl!
------------------------------
Message: 2
Date: Sun, 5 Sep 2010 23:11:04 +0200 (CEST)
From: Morgan C <[email protected]>
To: [email protected]
Subject: [OSL | CCIE_RS] BSR Filtering
Message-ID: <12544945.90142.1283721064327.javamail....@wwinf1d22>
Content-Type: text/plain; charset=UTF-8
Hello,
With Auto-RP we have a way to filter what the RP agent will announce with the
command 'ip pim rp-announce-filter' in order, for example, to prevent rogue RP
to announce itself for a group.
Is there a way to do the same thing on the BSR mapping agent ?
What would be the answer for the following task
'On a Multicast domain that uses BSR as group-to-rp mapping, be sure that the
router Rx that is wrongly annoucing itslef as candidate RP is not advertised to
others routers by the BSR router.'
The only way I found is setting on every router ip pim rp-accept for legal rp
but it doesn't prevent the rogue to be advertised and it's not very scalable.
Thanks much
------------------------------
Message: 3
Date: Sun, 5 Sep 2010 20:06:02 -0400
From: "Jason Maynard" <[email protected]>
To: <[email protected]>
Subject: [OSL | CCIE_RS] Vol1-LAB13-TASK13.12 - Thoughts?
Message-ID: <020f01cb4d57$4b457dd0$e1d079...@[email protected]>
Content-Type: text/plain; charset="us-ascii"
13.12 - No Null routes are permitted on CAT1 - in the workbook it states
that a distribute-list will not work as the route is generated and not a
learned route. I configured it with a distribute-list and it worked fine.
Unless I am missing something,
Configuration below - Can someone explain why or is the workbook incorrect
CAT1-
r outer bgp 10101
no synchronization
bgp log-neighbor-changes
network 150.100.81.0 mask 255.255.255.0
network 150.101.12.0 mask 255.255.255.0
network 150.101.13.0 mask 255.255.255.0
network 150.101.14.0 mask 255.255.255.0
network 200.0.0.11 mask 255.255.255.255
aggregate-address 200.11.0.0 255.255.248.0 summary-only
neighbor 150.101.12.2 remote-as 10101
neighbor 150.101.12.2 route-reflector-client
neighbor 150.101.13.3 remote-as 10101
neighbor 150.101.13.3 route-reflector-client
neighbor 150.101.14.4 remote-as 10101
neighbor 150.101.14.4 route-reflector-client
neighbor 150.101.14.4 unsuppress-map CAT4-TASK11
distribute-list prefix Null in
no auto-summary
ip prefix-list Null seq 5 deny 200.11.0.0/21
ip prefix-list Null seq 10 permit 0.0.0.0/0 le 32
Cat3550-1(config-router)#do sh ip bgp
BGP table version is 28, local router ID is 200.0.0.11
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
*> 150.100.81.0/24 0.0.0.0 0 32768 i
*> 150.101.12.0/24 0.0.0.0 0 32768 i
* i 150.101.12.2 0 100 0 i
*> 150.101.13.0/24 0.0.0.0 0 32768 i
* i 150.101.13.3 0 100 0 i
*> 150.101.14.0/24 0.0.0.0 0 32768 i
* i 150.101.14.4 0 100 0 i
*> 200.0.0.11/32 0.0.0.0 0 32768 i
*>i200.0.0.12/32 150.101.12.2 0 100 0 i
*>i200.0.0.14/32 150.101.14.4 0 100 0 i
r> 200.11.0.0/21 0.0.0.0 32768 i
s>i200.11.1.0 150.101.12.2 0 100 0 i
s>i200.11.2.0 150.101.12.2 0 100 0 i
s>i200.11.3.0 150.101.12.2 0 100 0 i
s>i200.11.4.0 150.101.12.2 0 100 0 i
Network Next Hop Metric LocPrf Weight Path
s>i200.11.5.0 150.101.12.2 0 100 0 i
s>i200.11.6.0 150.101.12.2 0 100 0 i
sh ip route
B 200.11.4.0/24 [200/0] via 150.101.12.2, 00:07:44
B 200.11.5.0/24 [200/0] via 150.101.12.2, 00:07:44
B 200.11.6.0/24 [200/0] via 150.101.12.2, 00:07:44
200.0.0.0/32 is subnetted, 3 subnets
C 200.0.0.11 is directly connected, Loopback0
B 200.0.0.12 [200/0] via 150.101.12.2, 00:07:44
B 200.0.0.14 [200/0] via 150.101.14.4, 00:07:44
B 200.11.1.0/24 [200/0] via 150.101.12.2, 00:07:44
B 200.11.2.0/24 [200/0] via 150.101.12.2, 00:07:44
B 200.11.3.0/24 [200/0] via 150.101.12.2, 00:07:44
150.100.0.0/24 is subnetted, 1 subnets
C 150.100.81.0 is directly connected, Vlan2200
150.101.0.0/24 is subnetted, 3 subnets
C 150.101.14.0 is directly connected, FastEthernet0/19
C 150.101.13.0 is directly connected, FastEthernet0/21
C 150.101.12.0 is directly connected, FastEthernet0/23
Other requirements are still being met on the other nodes (13.10,13.11)
CAT4
Sh ip route
B 200.11.4.0/24 [200/0] via 150.101.12.2, 00:00:16
B 200.11.5.0/24 [200/0] via 150.101.12.2, 00:00:16
B 200.11.6.0/24 [200/0] via 150.101.12.2, 00:00:16
200.0.0.0/32 is subnetted, 3 subnets
B 200.0.0.11 [200/0] via 150.101.14.1, 00:00:21
B 200.0.0.12 [200/0] via 150.101.12.2, 00:00:16
C 200.0.0.14 is directly connected, Loopback0
B 200.11.1.0/24 [200/0] via 150.101.12.2, 00:00:16
B 200.11.2.0/24 [200/0] via 150.101.12.2, 00:00:16
B 200.11.3.0/24 [200/0] via 150.101.12.2, 00:00:16
150.100.0.0/24 is subnetted, 1 subnets
B 150.100.81.0 [200/0] via 150.101.14.1, 00:00:22
150.101.0.0/24 is subnetted, 3 subnets
C 150.101.14.0 is directly connected, FastEthernet0/19
B 150.101.13.0 [200/0] via 150.101.14.1, 00:00:22
B 150.101.12.0 [200/0] via 150.101.14.1, 00:00:22
B 200.11.0.0/21 [200/0] via 150.101.14.1, 00:00:57
CAT3
sh ip route
Gateway of last resort is not set
200.0.0.0/32 is subnetted, 4 subnets
B 200.0.0.11 [200/0] via 150.101.13.1, 00:01:38
B 200.0.0.12 [200/0] via 150.101.12.2, 00:01:33
C 200.0.0.13 is directly connected, Loopback0
B 200.0.0.14 [200/0] via 150.101.14.4, 00:01:33
150.100.0.0/24 is subnetted, 1 subnets
B 150.100.81.0 [200/0] via 150.101.13.1, 00:01:38
150.101.0.0/24 is subnetted, 3 subnets
B 150.101.14.0 [200/0] via 150.101.13.1, 00:01:38
C 150.101.13.0 is directly connected, FastEthernet0/21
B 150.101.12.0 [200/0] via 150.101.13.1, 00:01:39
B 200.11.0.0/21 [200/0] via 150.101.13.1, 00:02:15
CAT 2
sh ip route
Gateway of last resort is not set
C 200.11.4.0/24 is directly connected, Loopback14
C 200.11.5.0/24 is directly connected, Loopback15
C 200.11.6.0/24 is directly connected, Loopback16
200.0.0.0/32 is subnetted, 3 subnets
B 200.0.0.11 [200/0] via 150.101.12.1, 00:02:11
C 200.0.0.12 is directly connected, Loopback0
B 200.0.0.14 [200/0] via 150.101.14.4, 00:02:06
C 200.11.1.0/24 is directly connected, Loopback11
C 200.11.2.0/24 is directly connected, Loopback12
C 200.11.3.0/24 is directly connected, Loopback13
150.100.0.0/24 is subnetted, 1 subnets
B 150.100.81.0 [200/0] via 150.101.12.1, 00:02:12
150.101.0.0/24 is subnetted, 3 subnets
B 150.101.14.0 [200/0] via 150.101.12.1, 00:02:12
B 150.101.13.0 [200/0] via 150.101.12.1, 00:02:12
C 150.101.12.0 is directly connected, FastEthernet0/23
B 200.11.0.0/21 [200/0] via 150.101.12.1, 00:02:47
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </archives/ccie_rs/attachments/20100905/aa2241ac/attachment.html>
End of CCIE_RS Digest, Vol 56, Issue 24
***************************************
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
