Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 24 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
24
Dung lượng
224,21 KB
Nội dung
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Before you begin, make sure you have Unicast routing connectivity
between CE1, CE2, CE8, PE1, PE2, and PE3. Otherwise, you will get
RPF checks failures and Multicast won’t work. One of the
workarounds is to use ip mroute static statements. RPF is checked
against them before using Unicast IP routing table.
Multicast Groups and IGMP
Task 6.1:
Configure on all routers:
PE3-RACK1(config)#ip multicast-routing
PE3-RACK1#show ip multicast
Multicast Routing: enabled
Multicast Multipath: disabled
Multicast Route limit: No limit
Multicast Triggered RPF check: enabled
Multicast Fallback group mode: Dense
Task 6.2:.
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip igmp join-group
CE8-RACK1(config-if)#ip igmp join-group
CE8-RACK1(config-if)#ip igmp join-group
CE8-RACK1(config-if)#ip igmp join-group
CE8-RACK1(config-if)#ip igmp join-group
1
224.8.8.8
225.8.8.8
235.235.235.235
229.0.0.1
229.0.0.2
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
CE8-RACK1#show ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 FastEthernet1/0
224.8.8.8
FastEthernet1/0
225.8.8.8
FastEthernet1/0
229.0.0.1
FastEthernet1/0
229.0.0.2
FastEthernet1/0
|
Lab6 Solutions: Multicast I
Uptime
00:00:25
00:00:25
00:00:25
00:00:25
00:00:25
Expires
stopped
stopped
stopped
stopped
stopped
Last Reporter
192.168.100.8
192.168.100.8
192.168.100.8
192.168.100.8
192.168.100.8
The IGMP join-group command makes a router advertise Multicast
groups to itself. Now, CE8 wants to receive Multicast traffic on the
specified Multicast group addresses.
Task 6.3:
CE2-RACK1(config)#int ethernet0/0
CE2-RACK1(config-if)#ip igmp join-group 224.2.2.2
CE2-RACK1(config-if)#ip igmp join-group 225.2.2.2
CE2-RACK1(config-if)#ip igmp join-group 235.235.235.235
CE2-RACK1#show ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 Ethernet0/0
224.2.2.2
Ethernet0/0
225.2.2.2
Ethernet0/0
Uptime
00:00:17
00:00:28
00:00:23
Expires
never
never
never
Last Reporter
10.23.1.1
10.23.1.1
10.23.1.1
Task 6.4:
CE1-RACK1(config)#int ethernet0/0
CE1-RACK1(config-if)#ip igmp join-group 224.1.1.1
CE1-RACK1(config-if)#ip igmp join-group 225.1.1.1
CE1-RACK1(config-if)#ip igmp join-group 235.235.235.235
2
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
CE1-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
225.1.1.1
Ethernet0/0
224.1.1.1
Ethernet0/0
235.235.235.235 Ethernet0/0
|
Lab6 Solutions: Multicast I
Uptime
00:01:30
00:01:35
00:01:24
Expires
stopped
stopped
stopped
Last Reporter
10.13.1.1
10.13.1.1
10.13.1.1
Task 6.5:
So far you don’t have ip pim enabled anywhere. To get this task
done, you need to turn on Multicast routing protocol on these two
interfaces: PE3 E0/0.23 and CE2 E0/0. IGMPv2 election process on
one Ethernet segment happens by default when there’s more than
one interface with Multicast routing protocol enabled. This process
will elect the IGMP querying router for the segment. IGMP router
with the lowest IP address will be elected.
Before enabling IP PIM on these two interfaces, here’s an output of
the show ip igmp int e0/0 command on CE2:
CE2-RACK1#sh ip igmp int e0/0
Ethernet0/0 is up, line protocol is up
Internet address is 10.23.1.1/24
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query count is 2
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 3 joins, 0 leaves
Multicast routing is disabled on interface
Multicast TTL threshold is 0
Multicast groups joined (number of users):
224.2.2.2(1) 225.2.2.2(1) 235.235.235.235(1)
Notice that IGMPv2 is enabled on the Ethernet0/0 interface but
Multicast routing is not. These conditions won’t allow IGMPv2
election process to start on this Ethernet segment. Also, notice that
CE2 and PE3 right now only act as IGMP hosts, but not as IGMP
routers. If you look at IGMP groups on PE3, you won’t see CE2’s
groups:
3
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE3-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
Uptime
Expires
Last Reporter
Configure one of the IP PIM modes on both routers. Start with PE3:
PE3-RACK1(config)#int ethernet0/0.23
PE3-RACK1(config-if)#ip pim sparse-dense-mode
As soon as you enable Multicast routing protocol on PE3
Ethernet0/0.23, PE3 will send out IGMPv2 report query on the
segment and then accept IGMP joins from CE2 Ethernet0/0
interface and add the groups to its IGMP group table:
PE3-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 Ethernet0/0.23
224.2.2.2
Ethernet0/0.23
225.2.2.2
Ethernet0/0.23
224.0.1.40
Ethernet0/0.23
Uptime
00:00:12
00:00:11
00:00:12
00:00:14
Expires
00:02:47
00:02:48
00:02:47
00:02:45
Last Reporter
10.23.1.1
10.23.1.1
10.23.1.1
10.23.1.3
Notice the new 224.0.1.40 group that PE3 has joined on
Ethernet0/0.23 interface. It enables these routers to receive PIM
Sparse Mode Auto-RP discovery messages sent to the 224.0.1.40
group address. Auto-RP will be configured later on.
Now, let’s enable IP PIM on CE2:
CE2-RACK1(config)#int ethernet0/0
CE2-RACK1(config-if)#ip pim sparse-dense-mode
Go back to PE3:
PE3-RACK1#sh ip igmp interface ethernet0/0.23
Ethernet0/0.23 is up, line protocol is up
Internet address is 10.23.1.3/24
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query count is 2
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 4 joins, 0 leaves
Multicast routing is enabled on interface
4
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Multicast TTL threshold is 0
Multicast designated router (DR) is 10.23.1.3 (this system)
IGMP querying router is 10.23.1.1
Multicast groups joined (number of users):
224.0.1.40(1)
Pay attention to the two highlighted lines in the output.
The first highlighted line shows PIM Designated Router on this
segment, which is PE3. Multicast routers automatically elect a PIM
designated router for the LAN (subnet). This is the router with the
highest IP address. The designated router is responsible for
sending IGMP host-query messages to all hosts on the LAN. In
zsparse mode, the designated router also sends PIM register and
PIM join messages toward the RP router.
The second highlighted line shows IGMP elected querying router on
this segment, which is CE2. This is the router with the lowest IP
address. IGMPv2 Election process took place. Let’s double check
CE2:
CE2-RACK1#sh ip igmp int e0/0
Ethernet0/0 is up, line protocol is up
Internet address is 10.23.1.1/24
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query count is 2
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 5 joins, 1 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 10.23.1.3
IGMP querying router is 10.23.1.1 (this system)
Multicast groups joined (number of users):
224.2.2.2(1) 225.2.2.2(1) 235.235.235.235(1)
224.0.1.40(1)
5
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Task 6.6:
Enable this requirement by configuring IGMP static-group. This
command acts almost like IGMP join-group, but the interface
doesn’t actually join the group. If you were to ping the Multicast
address that was configured in the IGMP join-group command,
you would get an ICMP response from the interface. If you were to
ping the Multicast address that was configured in IGMP staticgroup command, you would not get an ICMP response from the
interface. You would only get ICMP responses from the receivers on
the segment, if any.
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip igmp static-group 235.5.5.5
CE8-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 FastEthernet0/1
224.8.8.8
FastEthernet0/1
225.8.8.8
FastEthernet0/1
229.0.0.1
FastEthernet0/1
229.0.0.2
FastEthernet0/1
Uptime
01:03:19
01:03:19
01:03:19
01:03:19
01:03:19
Expires
stopped
stopped
stopped
stopped
stopped
Last Reporter
192.168.100.8
192.168.100.8
192.168.100.8
192.168.100.8
192.168.100.8
Notice, that 235.5.5.5 has not yet appeared in the IGMP group list.
The reason is lack of Multicast routing protocol on FastEthernet0/1
interface. Let’s enable IP PIM on this interface.
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip pim sparse-dense-mode
CE8-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 FastEthernet0/1
235.5.5.5
FastEthernet0/1
224.8.8.8
FastEthernet0/1
225.8.8.8
FastEthernet0/1
229.0.0.1
FastEthernet0/1
229.0.0.2
FastEthernet0/1
224.0.1.40
FastEthernet0/1
Uptime
01:05:03
00:00:13
01:05:03
01:05:03
01:05:03
01:05:03
00:00:13
Expires
00:02:48
stopped
00:02:47
00:02:47
00:02:48
00:02:48
00:02:46
Last Reporter
192.168.100.1
0.0.0.0
192.168.100.1
192.168.100.1
192.168.100.1
192.168.100.1
192.168.100.1
235.5.5.5 now appears in the table. It has no reporters because
CE8 is not acting as an IGMP host, it only creates IGMP group for
Multicast routing.
Task 6.7:
6
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
You are asked to send out IGMPv2 Report Query every 30 seconds.
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip igmp query-interval 30
CE8-RACK1#sh ip igmp int FastEthernet0/1
FastEthernet0/1 is up, line protocol is up
Internet address is 192.168.100.8/24
IGMP is enabled on interface
Current IGMP host version is 2
Current IGMP router version is 2
IGMP query interval is 30 seconds
IGMP querier timeout is 60 seconds
IGMP max query response time is 10 seconds
Last member query count is 2
Last member query response interval is 1000 ms
Inbound IGMP access group is not set
IGMP activity: 9 joins, 2 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 0.0.0.0
IGMP querying router is 192.168.100.8 (this system)
Multicast groups joined (number of users):
224.8.8.8(1) 225.8.8.8(1) 235.235.235.235(1)
229.0.0.1(1) 229.0.0.2(1) 224.0.1.40(1)
Task 6.8:
To make CE8 compatible with this topology, you need to force
Fa0/1 into the IGMP version 1 mode.
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip igmp version 1
CE8-RACK1#sh ip igmp int FastEthernet0/1
FastEthernet0/1 is up, line protocol is up
Internet address is 192.168.100.8/24
IGMP is enabled on interface
Current IGMP host version is 1
Current IGMP router version is 1
IGMP query interval is 30 seconds
Inbound IGMP access group is not set
IGMP activity: 9 joins, 2 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast designated router (DR) is 0.0.0.0
IGMP querying router is 0.0.0.0 (this system)
Multicast groups joined (number of users):
224.8.8.8(1) 225.8.8.8(1) 235.235.235.235(1)
229.0.0.1(1) 229.0.0.2(1) 224.0.1.40(1)
7
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Task 6.9:
3750(config)#ip igmp snooping vlan 23 immediate-leave
Task 6.10:
This is a trick question. Such change cannot be made on a 3750. It
has to be done on PE3. If you issue sh ip igmp snooping vlan 23
on 3750, it will say "IGMP_ONLY."
PE3(config)#int Ethernet0/0.23
PE3(config-if)#ip cgmp
Now, if you issue sh ip igmp snooping vlan 23 on the 3750, it
will say "IGMP_CGMP".
Task 6.11:
CE8-RACK1(config)#int FastEthernet0/1
CE8-RACK1(config-if)#ip sdr listen
CE8-RACK1#sh ip sdr
SDR Cache - 0 entries
Task 6.12:
You have to configure ip pim sparse-dense-mode on all
interfaces. If there is no RP (Rendezvous Point) available for a
group, the interface will operate in dense mode for that group. If
there’s an RP available (Auto-RP, BSR, or static) for a group, the
interface will operate in Sparse mode for that group. Some
interfaces already have IP PIM sparse-dense-mode enabled. Let’s
enable it on the rest of the routers and interfaces.
CE8-RACK1(config)#int fastethernet0/0
CE8-RACK1(config-if)#ip pim sparse-dense-mode
PE1-RACK1(config)#int fastethernet0/0
PE1-RACK1(config-if)#ip pim sparse-dense-mode
PE1-RACK1(config)#int fastethernet0/1
PE1-RACK1(config-if)#ip pim sparse-dense-mode
PE2-RACK1(config)#int ethernet0/0.82
PE2-RACK1(config-if)#ip pim sparse-dense-mode
PE2-RACK1(config)#int ethernet0/0.123
8
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE2-RACK1(config-if)#ip pim sparse-dense-mode
PE2-RACK1(config)#int ethernet0/0.21
PE2-RACK1(config-if)#ip pim sparse-dense-mode
PE3-RACK1(config)#int ethernet0/0.23
PE3-RACK1(config-if)#ip pim sparse-dense-mode
PE3-RACK1(config)#int ethernet0/0.123
PE3-RACK1(config-if)#ip pim sparse-dense-mode
PE3-RACK1(config)#int ethernet0/0.13
PE3-RACK1(config-if)#ip pim sparse-dense-mode
PE3-RACK1(config)#int ethernet0/0.31
PE3-RACK1(config-if)#ip pim sparse-dense-mode
Let’s check PIM status on one of the routers.
PE2-RACK1#sh ip pim neighbor
PIM Neighbor Table
Neighbor
Interface
Address
Priority/Mode
172.16.123.3
Ethernet0/0.123
10.82.1.1
Ethernet0/0.82
172.16.12.1
Ethernet0/0.21
Uptime/Expires
Ver
00:01:43/00:01:30 v2
00:04:21/00:01:19 v2
00:02:50/00:01:22 v2
DR
1 / DR P
1 / P
1 / P
The above output shows IP addresses of the PIM neighbors.
PE2-RACK1#sh ip pim interface
Address
Interface
172.16.123.2
10.82.1.2
172.16.12.2
Ethernet0/0.123
Ethernet0/0.82
Ethernet0/0.21
Ver/
Mode
v2/SD
v2/SD
v2/SD
Nbr
Count
1
1
1
Query
Intvl
30
30
30
DR
Prior
1
1
1
DR
172.16.123.3
10.82.1.2
172.16.12.2
The above output shows IP addresses of the local interfaces on the
router running PIM. You can also see that PIM already went
through the PIM Designated Router election process. The router
with the highest IP address on the segment has won. Also notice
that PIM Version 2 is being used and that interfaces are in Sparse
Dense (SD) mode.
Let’s look at the Multicast routing table on PE2.
PE2-RACK1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,
9
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.40), 00:08:36/00:02:16, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0.123, Forward/Sparse-Dense, 00:06:48/00:00:00
Ethernet0/0.82, Forward/Sparse-Dense, 00:08:20/00:00:00
Ethernet0/0.21, Forward/Sparse-Dense, 00:08:36/00:00:00
Notice that multicast routing table is empty (except for the
224.0.1.40 Auto-RP discovery group). None of the configured IGMP
groups are in the table. This is because all of our interfaces and
groups are currently operating in Dense Mode, and not Sparse
Mode. The reason why we are operating in Dense Mode is because
there’s no Auto-RP and no static RPs configured. Dense Mode uses
the Flood technique. In the beginning, the topology doesn’t have
routing for Multicast groups. As soon as the first Multicast packet
is sent from a source to the group, it will be flooded to all routers in
the PIM Dense topology, and the Multicast routing table will show
the (S,G) entries for each source. We are going to try this in a little
while.
If you look at the Multicast routing table on the routers that have
IGMP groups configured, it will show you the (*,G) entries for each
Multicast group. The flag is DCL, Dense, Connected, Local.
CE8-RACK1#sh ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 235.235.235.235), 01:12:19/00:02:53, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:26/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:19/00:00:00
(*, 235.5.5.5), 01:12:20/stopped, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:26/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:20/00:00:00
10
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
(*, 239.255.255.255), 00:25:25/00:02:53, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:26/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 00:25:25/00:00:00
(*, 224.2.127.254), 00:25:26/00:02:52, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:27/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 00:25:26/00:00:00
(*, 224.8.8.8), 01:12:21/00:02:52, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:27/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:21/00:00:00
(*, 225.8.8.8), 01:12:21/00:02:52, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:27/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:21/00:00:00
(*, 229.0.0.1), 01:12:20/00:02:52, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:27/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:20/00:00:00
(*, 229.0.0.2), 01:12:21/00:02:51, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:28/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:21/00:00:00
(*, 224.0.1.40), 01:12:22/00:02:51, RP 0.0.0.0, flags: DCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet0/0, Forward/Sparse-Dense, 00:16:28/00:00:00
FastEthernet0/1, Forward/Sparse-Dense, 01:12:22/00:00:00
Notice that our static group 235.5.5.5 is Connected, but not Local.
Connected groups are groups discovered by IGMP and will also
show up in the show ip igmp groups. Local groups are groups
that have router’s interface as one of the receivers. The joingroup command creates this condition, but the static-group does
not.
Task 6.13:
CE8-RACK1(config)#int fastethernet0/0
CE8-RACK1(config-if)#ip pim query-interval 20
PE2-RACK1(config)#int ethernet0/0.82
PE2-RACK1(config-if)#ip pim query-interval 20
11
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE2-RACK1#sh ip pim interface
Address
Interface
172.16.123.2
10.82.1.2
172.16.12.2
Ethernet0/0.123
Ethernet0/0.82
Ethernet0/0.21
Ver/
Mode
v2/SD
v2/SD
v2/SD
Nbr
Count
1
1
1
Query
Intvl
30
20
30
DR
Prior
1
1
1
DR
172.16.123.3
10.82.1.2
172.16.12.2
6.14:
CE2-RACK1#ping 224.8.8.8
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.8.8.8, timeout is 2 seconds:
Reply to request 0 from 10.82.1.1, 60 ms
CE1-RACK1#ping 224.8.8.8
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.8.8.8, timeout is 2 seconds:
Reply to request 0 from 10.82.1.1, 52 ms
The ping was successful. Now let’s look at the Multicast routing
table on CE2. CE2 participates in PIM, so we should see PIM Dense
tree for the 224.8.8.8 group.
CE2-RACK1#sh ip mroute 224.8.8.8
Group 224.8.8.8 not found
The reason why you don’t see any (S,G) Dense entries in the
Multicast routing table on CE2 is because CE2 acts only as a source
when sending traffic to the 224.8.8.8 group. CE2 doesn’t need to
have Multicast routing table entries for this group. When you ping
224.8.8.8, IOS® simply makes an ICMP packet for each interface
running IP PIM routing protocol and sends it out. Now let’s look at
the Multicast routing table on directly connected PE3 router.
PE3-RACK1#sh ip mroute 224.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
12
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
(*, 224.8.8.8), 00:00:17/stopped, RP 0.0.0.0, flags: D
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0.23, Forward/Sparse-Dense, 00:00:17/00:00:00
Ethernet0/0.31, Forward/Sparse-Dense, 00:00:17/00:00:00
Ethernet0/0.123, Forward/Sparse-Dense, 00:00:17/00:00:00
(10.23.1.1, 224.8.8.8), 00:00:17/00:02:53, flags: T
Incoming interface: Ethernet0/0.23, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0.123, Forward/Sparse-Dense, 00:00:17/00:00:00
Ethernet0/0.31, Prune/Sparse-Dense, 00:00:17/00:02:45
The first (*,G) entry was created when all PIM routers were
flooding the first ping packet on all the routers operating in Dense
mode. Notice that PE3 considered all of its interfaces (including the
one where the packet came from–Eth0/0.23) as outgoing for the
initial flooding.
After all routers have received the flooded packet, the tree leaves
have either decided to join or prune. The router that has receivers
for this group, CE8, has joined the tree. The routers that had no
receivers for this group pruned it. The result is an SPT (shortest
path tree) that looks like this:
CE2
|
PE3
|
PE2
|
CE8
All other leaves are pruned. Perform the similar test from CE1 for
other Multicast groups, you should get similar results.
IP PIM Sparse Mode with Static RP
Task 6.15:
PE1, PE2, and PE3 have Loopback0 interfaces with the following
addresses: 10.1.1.1, 10.1.1.2 and 10.1.1.3. We can use these
interfaces for the PIM RPs. Make sure these addresses are
reachable in all routers’ Unicast routing tables. If you are
configuring this lab after the MPLS lab, your CEs will not
have connectivity to Loopback0’s on PEs.
13
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
Let’s configure PE2 as static RP for the 224.8.8.8 group. This
command has to be configured on every router running PIM. This is
one of the disadvantages of using static RP. You should also always
configure a group list specifying what Multicast groups the static RP
is used for.
CE2-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups
CE2-RACK1(config-std-nacl)#permit 224.8.8.8
CE2-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
CE8-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups
CE8-RACK1(config-std-nacl)#permit 224.8.8.8
CE8-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
PE1-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups
PE1-RACK1(config-std-nacl)#permit 224.8.8.8
PE1-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
PE2-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups
PE2-RACK1(config-std-nacl)#permit 224.8.8.8
PE2-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
PE3-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups
PE3-RACK1(config-std-nacl)#permit 224.8.8.8
PE3-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
The above configuration tells every router in the PIM domain that
group 224.8.8.8 has an RP on 10.1.1.2. Therefore, it can run in
sparse mode. Immediately, every router that has receivers for the
224.8.8.8 group (in our case, it’s only CE8) will try to create a
shared Multicast tree with RP PE2 at its root. The shared tree would
be pretty simple in our case:
PE2 (10.1.1.2, RP for 224.8.8.8 group)
|
CE8 (router with 224.8.8.8 receivers)
You should know the difference between the show ip pim rp
mapping and the show ip pim rp commands. The first command
shows you an identical output on all PIM routers in the domain. It is
the direct result of our static RP configuration or it could also be the
result of Auto-RP (or BSR). It doesn’t matter if the 224.8.8.8
receivers exist on any of the routers. If you run the show ip pim
rp mapping command on any PIM router you will get the same
output:
14
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE3-RACK1#show ip pim rp mapping
PIM Group-to-RP Mappings
Acl: RP-10.1.1.2-Groups, Static
RP: 10.1.1.2 (?)
This mapping indicates that if PE3 ever hears about the Multicast
group listed in RP-10.1.1.2-Groups ACL (i.e. directly connected
receivers join the group), it will try to build a shared Multicast tree
with RP 10.1.1.2 at its root.
Show ip pim rp is the result of the shared tree creation. You will
only see the output for this command on the routers that are part
of the shared tree: CE8 and PE2.
CE8-RACK1#show ip pim rp
Group: 224.8.8.8, RP: 10.1.1.2, uptime 00:18:13, expires never
PE2-RACK1#sh ip pim rp
Group: 224.8.8.8, RP: 10.1.1.2, next RP-reachable in 00:00:11
Notice the difference in the outputs. The first output is from the
leaf router CE8. It indicates that the RP has been up for 18 minutes
and 13 seconds. The second output is from the RP PE2. It indicates
that it will send the next RP-reachability message for 224.8.8.8 on
Ethernet 1/0 interface in 11 seconds. It does it every 90 seconds.
PE2-RACK1#debug ip pim
04:29:23: PIM(0): Send RP-reachability for 224.8.8.8 on Ethernet0/0.82
Let’s look at how CE8 tries to create the shared tree. We’ll remove
the static RP information from CE8, enable debug, and then reenter the static RP command. The process looks like this:
1. There’s a receiver for Multicast group 224.8.8.8 on CE8.
2. Leaf router CE8 knows the IP address of the RP for the
224.8.8.8 group (from the static RP statement). It sends
(*,G) join for this group towards the RP PE2.
3. This (*,G) Join travels hop-by-hop to the RP (PE2) building a
branch of the Shared tree that extends from the RP (PE2) to
the last-hop router (CE8). In our case this shared tree is
very small consisting of two routers, PE2 and CE8.
15
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
4. At this point, group 224.8.8.8’s traffic can flow down the
Shared Tree to the receiver.
CE8-RACK1(config)#no ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
CE8-RACK1#debug ip pim
CE8-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups
04:40:50: PIM(0): Check RP 10.1.1.2 into the (*, 224.8.8.8) entry
04:40:50: PIM(0): Building triggered (*,G) Join / (S,G,RP-bit) Prune
message for 224.8.8.8
04:40:50: PIM(0): Insert (*,224.8.8.8) join in nbr 10.82.1.2's queue
04:40:50: PIM(0): Building Join/Prune packet for nbr 10.82.1.2
04:40:50: PIM(0): Adding v2 (10.1.1.2/32, 224.8.8.8), WC-bit, RPT-bit,
S-bit Join
04:40:50: PIM(0): Send v2 join/prune to 10.82.1.2 (FastEthernet0/0)
Let’s look at the debug on PE2 when this happens:
PE2-RACK1#debug ip pim
04:43:21: PIM(0): Received v2 Join/Prune on Ethernet0/0.82 from
10.82.1.1, to us
04:43:21: PIM(0): Join-list: (*, 224.8.8.8), RPT-bit set, WC-bit set, Sbit set
04:43:21: PIM(0): Check RP 10.1.1.2 into the (*, 224.8.8.8) entry
04:43:21: PIM(0): Add Ethernet0/0.82/10.82.1.1 to (*, 224.8.8.8), Forward
state, by PIM *G Join
The result is the added (*,G) entry to the Multicast routing table on
PE2 and CE8.
16
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
CE8-RACK1#show ip mroute 224.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.8.8.8), 00:02:52/00:02:57, RP 10.1.1.2, flags: SJCL
Incoming interface: FastEthernet0/0, RPF nbr 10.82.1.2
Outgoing interface list:
FastEthernet0/1, Forward/Sparse-Dense, 00:02:52/00:02:57
PE2-RACK1#sh ip mroute 224.8.8.8
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel,
Y - Joined MDT-data group, y - Sending to MDT-data group
V - RD & Vector, v - Vector
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.8.8.8), 00:02:52/00:03:04, RP 10.1.1.2, flags: S
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Ethernet0/0.82, Forward/Sparse-Dense, 00:02:52/00:03:04
Pay attention to the Incoming and Outgoing interface lists. They
should make sense to you now.
No other router in the topology knows anything about group
224.8.8.8. Notice, no traffic has been sent yet. Remember that IP
Dense Mode requires the first packet to be sent from the source in
order to start building the Multicast tree. Let’s look at show ip pim
rp and show ip mroute on some other router that doesn’t belong
to the shared tree, for example PE1.
PE1-RACK1#sh ip pim rp
Å NO OUTPUT
PE1-RACK1#sh ip mroute 224.8.8.8
Group 224.8.8.8 not found
Let’s do a ping test right from RP PE2.
17
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE2-RACK1#ping 224.8.8.8
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.8.8.8, timeout is 2 seconds:
Reply to request 0 from 10.82.1.1, 8 ms
Reply to request 0 from 10.82.1.1, 48 ms
Reply to request 0 from 10.82.1.1, 20 ms
By the way, you have received three replies, because three ICMP
messages have been sent out. One from each PIM-enabled
interface on PE2:
1. Ethernet0/0.123 connected to PE3
2. Ethernet0/0.82 connected to CE8
3. Ethernet0/0.21 connected to PE1
The ICMP echo sent via the Ethernet0/0.82 directly to CE8 took the
Sparse shared tree that has already been created. We can assume
that the very first reply (8 ms) was for that packet.
Task 6.16:.
Let’s configure PE1 as a static RP for the 224.1.1.1 group. This
command has to be configured on every router running PIM. You
should always configure a group list specifying what Multicast
groups the static RP is for.
CE2-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups
CE2-RACK1(config-std-nacl)#permit 224.1.1.1
CE2-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups
CE8-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups
CE8-RACK1(config-std-nacl)#permit 224.1.1.1
CE8-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups
PE1-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups
PE1-RACK1(config-std-nacl)#permit 224.1.1.1
PE1-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups
PE2-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups
PE2-RACK1(config-std-nacl)#permit 224.1.1.1
PE2-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups
PE3-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups
18
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
PE3-RACK1(config-std-nacl)#permit 224.1.1.1
PE3-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups
Verify.
CE1-RACK1#show ip pim rp
CE1 has no RP mappings, because it doesn’t participate in PIM. It’s
simply an IGMP host. PE3 is the IGMP router on that segment.
PE3-RACK1#sh ip igmp groups 224.1.1.1
IGMP Connected Group Membership
Group Address
Interface
Reporter
224.1.1.1
Ethernet0/0.13
Uptime
Expires
Last
00:18:23
00:02:41
10.13.1.1
PE3-RACK1#show ip pim rp
Group: 224.1.1.1, RP: 10.1.1.1, uptime 00:11:08, expires never
Up the tree, let’s check PE1.
PE1-RACK1#show ip pim rp
Group: 224.1.1.1, RP: 10.1.1.1, next RP-reachable in 00:00:46
Let’s check PE2. It should not know about the RP for this group as
it’s not part of the shared tree.
PE2-RACK1#sh ip pim rp
Group: 224.8.8.8, RP: 10.1.1.2, next RP-reachable in 00:00:44
Everything is OK. It’s a different group, there’s no 224.1.1.1.
Task 6.17:
Let’s configure PE3 as a static RP for the 224.2.2.2 group. This
command has to be configured on every router running PIM. You
should always configure a group list specifying what Multicast
groups the static RP is for.
By default, Auto-RP will always override static RP information. You
have to specify the override keyword to override this behavior and
prefer the static RP.
CE2-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups
19
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
CE2-RACK1(config-std-nacl)#permit 224.2.2.2
CE2-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override
CE8-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups
CE8-RACK1(config-std-nacl)#permit 224.2.2.2
CE8-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override
PE1-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups
PE1-RACK1(config-std-nacl)#permit 224.2.2.2
PE1-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override
PE2-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups
PE2-RACK1(config-std-nacl)#permit 224.2.2.2
PE2-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override
PE3-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups
PE3-RACK1(config-std-nacl)#permit 224.2.2.2
PE3-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override
Verify on PE3:
PE3-RACK1#show ip pim rp mapping
PIM Group-to-RP Mappings
Acl: RP-10.1.1.2-Groups, Static
RP: 10.1.1.2 (?)
Acl: RP-10.1.1.1-Groups, Static
RP: 10.1.1.1 (?)
Acl: RP-10.1.1.3-Groups, Static-Override
RP: 10.1.1.3 (?)
As you can see each router knows about all three static RP
mappings. The last RP 10.1.1.3 is static for the group specified in
RP-10.1.1.3-Groups access-list.
PE3-RACK1#show ip pim rp
Group: 224.2.2.2, RP: 10.1.1.3, next RP-reachable in 00:00:23
Group: 224.1.1.1, RP: 10.1.1.1, uptime 00:19:30, expires never
Not every router knows about each elected RP. For example, PE3
only knows that it is an RP for the 224.2.2.2 group and that it’s
part of the shared tree for group 224.1.1.1 with the 10.1.1.1 RP.
Task 6.18:
Ping should work from everywhere. Remember that number of
ICMP echo replies directly correlates to the number of PIM
20
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
interfaces on the source router. In the example below, PE3 has four
IP PIM-enabled interfaces. When you ping the group, the router
creates four ICMP echo packets and sends them out. All four will
reach the receiver.
PE3-RACK1#ping 224.2.2.2
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.2.2.2, timeout is 2 seconds:
Reply
Reply
Reply
Reply
to
to
to
to
request
request
request
request
0
0
0
0
from
from
from
from
10.23.1.1,
10.23.1.1,
10.23.1.1,
10.23.1.1,
8 ms
28 ms
28 ms
28 ms
PE3-RACK1#ping 224.8.8.8
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.8.8.8, timeout is 2 seconds:
Reply
Reply
Reply
Reply
to
to
to
to
request
request
request
request
0
0
0
0
from
from
from
from
10.82.1.1,
10.82.1.1,
10.82.1.1,
10.82.1.1,
40
64
64
64
ms
ms
ms
ms
Task 6.19:
The ip pim dm-fallback command was introduced in 12.3(4)T
version of the IOS® code. The PIM Dense Mode Fallback Prevention
in a Network Following RP Information Loss feature enables you to
prevent Protocol Independent Multicast (PIM) dense mode (DM)
fallback when all rendezvous points (RPs) fail. Preventing the use of
PIM-DM is very important to Multicast networks whose reliability is
critical. The feature provides a mechanism to keep Multicast groups
in sparse mode. Preventing the use of PIM-DM is very important to
Multicast networks whose reliability is critical. The feature provides
a mechanism to keep Multicast groups in sparse mode.
21
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
There are three ways to prevent dense mode fallback. First one is
to simply change the ip sparse-dense-mode config to ip pim
sparse-mode on all PIM interfaces. This would prevent IP PIM
dense mode to ever go in effect when RP information is lost. In
fact, if there’s no static RP available and Auto-RP is not configured
or is misconfigured, Multicast traffic will fail. We can’t use this
method, because we have configured Dense groups, and need to
leave them this way.
The second way is to configure the new command ip pim dmfallback in global configuration mode. When the feature is
configured, sparse mode groups operate with an RP address of
0.0.0.0. This task requires that you don’t use this method.
The third way is to configure a sink RP. This method was used
before the ip pim dm-fallback command became available.
To successfully implement Auto-RP and prevent any groups other
than 224.0.1.39 and 224.0.1.40 from operating in dense mode,
you should configure a "sink RP" (also known as RP of last resort).
A sink RP is a statically configured RP that may or may not actually
exist in the network. Configuring a sink RP does not interfere with
Auto-RP operation because, by default, Auto-RP messages
supersede static RP configurations. We recommend configuring a
sink RP for all possible Multicast groups in your network because it
is possible for an unknown or unexpected source to become active.
If no RP is configured to limit source registration, the group may
revert to dense mode operation and be flooded with data.
If you have already configured some static RPs and would like to
keep them that way, you would have to exclude them when
configuring a sink RP.
Let’s configure RP1 as a sink RP for all IGMP groups. Typically, in
the all-Auto-RP environment you would configure this command on
every router:
ip pim rp-address 10.1.1.1
22
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
When you don’t specify a group-list in the above command, the
default 224.0.0.0/4 group range is applied. That translates to
“10.1.1.1 is a static RP for all Multicast groups”. But since we
already have some static RPs configured, we have to exclude those
groups. Don’t exclude the 224.1.1.1 group because PE1 was
already configured to be its static RP.
Always exclude 224.0.1.39 and 224.0.1.40 Auto-RP groups,
because they should always operate in PIM Dense Mode.
Apply the following configuration on all routers (CE8, CE2, PE1,
PE2, PE3).
CE8-RACK1(config)#ip access-list standard RP-Sink-Groups
CE8-RACK1(config-std-nacl)#deny 224.0.1.39
CE8-RACK1(config-std-nacl)#deny 224.0.1.40
CE8-RACK1(config-std-nacl)#deny 224.8.8.8
CE8-RACK1(config-std-nacl)#deny 224.2.2.2
CE8-RACK1(config-std-nacl)#permit 224.0.0.0 15.255.255.255
CE8-RACK1(config)#ip pim rp-address 10.1.1.1 RP-Sink-Groups
FYI, ip pim rp-address 10.1.1.1 RP-Sink-Groups overrides
previously entered ip pim rp-address 10.1.1.1 RP-10.1.1.1Groups command. You can’t have more than one group list
configured for a single static RP.
Let’s look at the show ip pim rp on PE3:
PE1-RACK1#sh ip pim rp
Group: 235.235.235.235, RP: 10.1.1.1, next RP-reachable in 00:00:43
Group: 235.5.5.5, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 239.255.255.255, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 224.2.127.254, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 225.8.8.8, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 229.0.0.1, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 229.0.0.2, RP: 10.1.1.1, next RP-reachable in 00:01:20
Group: 225.2.2.2, RP: 10.1.1.1, next RP-reachable in 00:00:01
Group: 225.1.1.1, RP: 10.1.1.1, next RP-reachable in 00:01:26
Group: 224.1.1.1, RP: 10.1.1.1, next RP-reachable in 00:00:42
By now you should see why some groups show up in the list and
why others don’t. For example, 224.2.2.2 is not in the list because
PE3 is its RP, and PE1 is not part of that shared tree.
23
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
ieMentor CCIE™ Service Provider Workbook v1.0
|
Lab6 Solutions: Multicast I
You will notice two new groups: 239.255.255.255 and
224.2.127.254. If you check all the routers, you will find the IGMP
groups 239.255.255.255 and 224.2.127.254:
CE8-RACK1#sh ip igmp groups
IGMP Connected Group Membership
Group Address
Interface
235.235.235.235 FastEthernet0/1
235.5.5.5
FastEthernet0/1
239.255.255.255 FastEthernet0/1
224.2.127.254
FastEthernet0/1
224.8.8.8
FastEthernet0/1
225.8.8.8
FastEthernet0/1
229.0.0.1
FastEthernet0/1
229.0.0.2
FastEthernet0/1
224.0.1.40
FastEthernet0/0
Uptime
Expires
Last Reporter
01:39:04 00:01:16 192.168.100.8
01:39:04 stopped
0.0.0.0
00:05:57 00:01:16 192.168.100.8
00:05:57 00:01:16 192.168.100.8
01:39:05 00:01:16 192.168.100.8
01:39:04 00:01:16 192.168.100.8
01:39:04 00:01:16 192.168.100.8
01:39:04 00:01:16 192.168.100.8
01:39:05 00:02:09 10.82.1.1
These two new groups are the result of configuring ip sdr listen.
24
This product is individually licensed.
Copyright® 2005 ieMentor http://www.iementor.com.
[...]... RP-10.1.1.2-Groups CE8-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups CE8-RACK1(config-std-nacl)#permit 224.8.8.8 CE8-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups PE1-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups PE1-RACK1(config-std-nacl)#permit 224.8.8.8 PE1-RACK1(config)#ip pim rp-address 10.1.1.2 RP-10.1.1.2-Groups PE2-RACK1(config)#ip access-list standard RP-10.1.1.2-Groups... CE2-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups CE2-RACK1(config-std-nacl)#permit 224.1.1.1 CE2-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups CE8-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups CE8-RACK1(config-std-nacl)#permit 224.1.1.1 CE8-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups PE1-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups PE1-RACK1(config-std-nacl)#permit... CE2-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override CE8-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups CE8-RACK1(config-std-nacl)#permit 224.2.2.2 CE8-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override PE1-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups PE1-RACK1(config-std-nacl)#permit 224.2.2.2 PE1-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups... PE1-RACK1(config-std-nacl)#permit 224.1.1.1 PE1-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups PE2-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups PE2-RACK1(config-std-nacl)#permit 224.1.1.1 PE2-RACK1(config)#ip pim rp-address 10.1.1.1 RP-10.1.1.1-Groups PE3-RACK1(config)#ip access-list standard RP-10.1.1.1-Groups 18 This product is individually licensed Copyright® 2005 ieMentor http://www.iementor.com... override PE2-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups PE2-RACK1(config-std-nacl)#permit 224.2.2.2 PE2-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override PE3-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups PE3-RACK1(config-std-nacl)#permit 224.2.2.2 PE3-RACK1(config)#ip pim rp-address 10.1.1.3 RP-10.1.1.3-Groups override Verify on PE3: PE3-RACK1#show ip pim rp... CE8-RACK1(config)#ip access-list standard RP-Sink-Groups CE8-RACK1(config-std-nacl)#deny 224.0.1.39 CE8-RACK1(config-std-nacl)#deny 224.0.1.40 CE8-RACK1(config-std-nacl)#deny 224.8.8.8 CE8-RACK1(config-std-nacl)#deny 224.2.2.2 CE8-RACK1(config-std-nacl)#permit 224.0.0.0 15.255.255.255 CE8-RACK1(config)#ip pim rp-address 10.1.1.1 RP-Sink-Groups FYI, ip pim rp-address 10.1.1.1 RP-Sink-Groups overrides previously... ieMentor CCIE™ Service Provider Workbook v1.0 | Lab6 Solutions: Multicast I CE8-RACK1#show ip mroute 224.8.8.8 IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U -. .. Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, Y - Joined MDT-data group, y - Sending to MDT-data group V - RD & Vector, v - Vector Outgoing interface flags: H - Hardware switched, A - Assert winner Timers:... override static RP information You have to specify the override keyword to override this behavior and prefer the static RP CE2-RACK1(config)#ip access-list standard RP-10.1.1.3-Groups 19 This product is individually licensed Copyright® 2005 ieMentor http://www.iementor.com ieMentor CCIE™ Service Provider Workbook v1.0 | Lab6 Solutions: Multicast I CE2-RACK1(config-std-nacl)#permit 224.2.2.2 CE2-RACK1(config)#ip... provides a mechanism to keep Multicast groups in sparse mode Preventing the use of PIM-DM is very important to Multicast networks whose reliability is critical The feature provides a mechanism to keep Multicast groups in sparse mode 21 This product is individually licensed Copyright® 2005 ieMentor http://www.iementor.com ieMentor CCIE™ Service Provider Workbook v1.0 | Lab6 Solutions: Multicast I There ... response interval is 1000 ms Inbound IGMP access group is not set IGMP activity: joins, leaves Multicast routing is enabled on interface This product is individually licensed Copyright® 2005 ieMentor... PE2-RACK1(config)#int ethernet0/0.82 PE2-RACK1(config-if)#ip pim query-interval 20 11 This product is individually licensed Copyright® 2005 ieMentor http://www.iementor.com ieMentor CCIE™ Service Provider... CE1-RACK1(config)#int ethernet0/0 CE1-RACK1(config-if)#ip igmp join-group 224.1.1.1 CE1-RACK1(config-if)#ip igmp join-group 225.1.1.1 CE1-RACK1(config-if)#ip igmp join-group 235.235.235.235 This product is