ip pim rp-announce-filter
Only routers configured as mapping agents subscribe to candidate RP announcement messages. Therefore, the ip pim rp-announce-filter global configuration command is effective only when configured on a mapping agent router. This command has no effect when configured on any other router.
R5(config)#do sh run | i rp-
ip pim send-rp-discovery Loopback0 scope 16
ip pim rp-announce-filter rp-list RPS group-list DENSE
R5(config)#
The following example configures the router to accept RP announcements
from RPs in access list 1 for group ranges described in access list 2; note the ACEs in access-list 2.
ip pim rp-announce-filter rp-list 1 group-list 2
access-list 1 permit 10.0.0.1
access-list 1 permit 10.0.0.2
access-list 2 permit 224.0.0.0 192.168.255.255
access-list 1 permit 10.0.0.1
access-list 1 permit 10.0.0.2
access-list 2 permit 224.0.0.0 192.168.255.255
If rp-list is missing, filtering is then based on group-list and vice versa.
mtrace
This command is great to give you an overview of your topology with regards to any S and G you're tracking. Note that 155.1.67.7 which was a test vlan on SW1 showing up!
R6#mstat 150.1.6.6 150.1.10.10 224.0.1.40
Type escape sequence to abort.
Mtrace from 150.1.6.6 to 150.1.10.10 via group 224.0.1.40
From source (R6) to destination (?)
Waiting to accumulate statistics....* .* .
Results after 13 seconds:
Source Response Dest Packet Statistics For Only For Traffic
150.1.6.6 150.1.6.6 All Multicast Traffic From 150.1.6.6
| __/ rtt 48 ms Lost/Sent = Pct Rate To 224.0.1.40
v / hop -1 s --------------------- --------------------
150.1.6.6
155.1.67.6 ?
| ^ ttl 0
v | hop 719 ms -4/0 = --% 0 pps 0/0 = --% 0 pps
155.1.67.7
155.1.37.7 ?
| ^ ttl 1
v | hop -14 s 0/0 = --% 0 pps 0/0 = --% 0 pps
155.1.37.3
155.1.0.3 ?
| ^ ttl 2
v | hop 12 s 0/0 = --% 0 pps 0/0 = --% 0 pps
155.1.0.5
155.1.58.5 ?
| ^ ttl 3
v | hop 2441 ms -3/0 = --% 0 pps 0/0 = --% 0 pps
155.1.58.8
155.1.108.8 ?
| ^ ttl 4
v | hop -1 s -3/0 = --% 0 pps 0/0 = --% 0 pps
155.1.108.10 ?
| \__ ttl 5
v \ hop 1211 ms 0 0 pps 0 0 pps
150.1.10.10 150.1.6.6
Receiver Query Source
R6#
mtrace
This command is great to give you an overview of your topology with regards to any S and G you're tracking. Note that 155.1.67.7 which was a test vlan on SW1 showing up!
R6#mstat 150.1.6.6 150.1.10.10 224.0.1.40
Type escape sequence to abort.
Mtrace from 150.1.6.6 to 150.1.10.10 via group 224.0.1.40
From source (R6) to destination (?)
Waiting to accumulate statistics....* .* .
Results after 13 seconds:
Source Response Dest Packet Statistics For Only For Traffic
150.1.6.6 150.1.6.6 All Multicast Traffic From 150.1.6.6
| __/ rtt 48 ms Lost/Sent = Pct Rate To 224.0.1.40
v / hop -1 s --------------------- --------------------
150.1.6.6
155.1.67.6 ?
| ^ ttl 0
v | hop 719 ms -4/0 = --% 0 pps 0/0 = --% 0 pps
155.1.67.7
155.1.37.7 ?
| ^ ttl 1
v | hop -14 s 0/0 = --% 0 pps 0/0 = --% 0 pps
155.1.37.3
155.1.0.3 ?
| ^ ttl 2
v | hop 12 s 0/0 = --% 0 pps 0/0 = --% 0 pps
155.1.0.5
155.1.58.5 ?
| ^ ttl 3
v | hop 2441 ms -3/0 = --% 0 pps 0/0 = --% 0 pps
155.1.58.8
155.1.108.8 ?
| ^ ttl 4
v | hop -1 s -3/0 = --% 0 pps 0/0 = --% 0 pps
155.1.108.10 ?
| \__ ttl 5
v \ hop 1211 ms 0 0 pps 0 0 pps
150.1.10.10 150.1.6.6
Receiver Query Source
R6#
mrinfo
This command shows multicast neighbor router information, router capabilities and code version, multicast interface information, TTL thresholds, metrics, protocol, and status. It is useful when you need to verify multicast neighbors, confirm that bi−directional neighbor adjacency exists, and verify that tunnels are up in both directions.
R1#mrinfo
155.1.146.1 [version 12.4] [flags: PMA]:
155.1.146.1 -> 155.1.146.4 [1/0/pim/querier]
155.1.146.1 -> 155.1.146.6 [1/0/pim/querier]
155.1.0.1 -> 155.1.0.5 [1/0/pim]
150.1.1.1 -> 150.1.9.9 [1/0/tunnel/pim]
150.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]
150.1.1.1 -> 150.1.3.3 [1/0/tunnel/pim]
R1#
R1#sh ip pim ne
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
155.1.146.4 GigabitEthernet0/0 1w1d/00:01:24 v2 1 / S P
155.1.146.6 GigabitEthernet0/0 1w1d/00:01:38 v2 1 / S P
155.1.0.5 Serial0/0/0.1 1w1d/00:01:34 v2 1 / S P
150.1.9.9 Tunnel0 1d23h/00:01:24 v2 1 / S P
150.1.3.3 Tunnel1 1d23h/00:01:22 v2 1 / S P
R1#
This command shows multicast neighbor router information, router capabilities and code version, multicast interface information, TTL thresholds, metrics, protocol, and status. It is useful when you need to verify multicast neighbors, confirm that bi−directional neighbor adjacency exists, and verify that tunnels are up in both directions.
R1#mrinfo
155.1.146.1 [version 12.4] [flags: PMA]:
155.1.146.1 -> 155.1.146.4 [1/0/pim/querier]
155.1.146.1 -> 155.1.146.6 [1/0/pim/querier]
155.1.0.1 -> 155.1.0.5 [1/0/pim]
150.1.1.1 -> 150.1.9.9 [1/0/tunnel/pim]
150.1.1.1 -> 0.0.0.0 [1/0/pim/querier/leaf]
150.1.1.1 -> 150.1.3.3 [1/0/tunnel/pim]
R1#
R1#sh ip pim ne
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
155.1.146.4 GigabitEthernet0/0 1w1d/00:01:24 v2 1 / S P
155.1.146.6 GigabitEthernet0/0 1w1d/00:01:38 v2 1 / S P
155.1.0.5 Serial0/0/0.1 1w1d/00:01:34 v2 1 / S P
150.1.9.9 Tunnel0 1d23h/00:01:24 v2 1 / S P
150.1.3.3 Tunnel1 1d23h/00:01:22 v2 1 / S P
R1#
No comments:
Post a Comment