From: Keith Bizzell (mkbcoolman@gmail.com)
Date: Tue Mar 06 2007 - 23:59:01 ART
This section calls for filtering the admin range between R3/SW2, which are
pim neighors on R3s Fa0/0. This should call for a simple access-list,
right? Here's my output on SW2 prior to filtering:
Rack1SW2#show ip pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,
S - State Refresh Capable
Neighbor Interface Uptime/Expires Ver DR
Address Prio/Mode
162.1.38.3 Vlan38 04:16:53/00:01:30 v2 1 / S
Rack1SW2#show ip pim rp map
PIM Group-to-RP Mappings
Group(s) 226.0.0.0/7
RP 150.1.5.5 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:05:47, expires: 00:00:10
Group(s) 228.0.0.0/6
RP 150.1.5.5 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:02:49, expires: 00:00:05
Group(s) 232.0.0.0/6
RP 150.1.5.5 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:05:47, expires: 00:00:09
Group(s) 236.0.0.0/7
RP 150.1.5.5 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:05:47, expires: 00:00:09
Group(s) 238.0.0.0/8
RP 150.1.5.5 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:05:47, expires: 00:00:09
Group(s) 239.0.0.0/8
RP 150.1.3.3 (?), v2v1
Info source: 150.1.1.1 (?), elected via Auto-RP
Uptime: 00:05:47, expires: 00:00:06
I performed the following configuration on R3:
int fa0/0
ip multicast boundry 75
ip access-list 75 deny 239.0.0.0 0.255.255.255
ip access-list 75 permit 224.0.0.0 15.255.255.255
When I apply the boundry, SW2 has no RP mappings. I've tried every
combination I can think of on the access list, but no luck. Any ideas?
Keith
This archive was generated by hypermail 2.1.4 : Sun Apr 01 2007 - 06:35:50 ART