Lab Objective:
The focus of this lab is to understand IP Multicast Dense Mode forwarding in Cisco IOS routers. Additional technologies include Internet Group Management Protocol (IGMP).
Lab Topology:
The lab network topology is illustrated below:
|
IMPORTANT NOTE If you are using the www.howtonetwork.net racks, please bring up the LAN interfaces connected to the routers by issuing the no shutdown command on the connected switches. If you are using a home lab with no interface fastethernet 0/0 Alternately, you can simply connect the interfaces to a hub or switch if you have one available in your own lab. |
Task 1
Configure the hostnames, IP addressing on all routers as illustrated in the network topology.
Task 2
Enable EIGRP on all routers as illustrated in the topology. Verify your EIGRP configuration.
Task 3
Enable Internet Group Management Protocol on the LAN interfaces of R1 and R4. Ensure that the configuration allows the host to request traffic from a specific host in the network. Next, enable Dense Mode forwarding on the interfaces. Verify your solution using the appropriate commands.
Task 4
Enable Dense Mode forwarding on all router WAN interfaces. Verify your configuration using the appropriate commands.
Task 5
Configure R1 so that its LAN interface is joined to Multicast group 227.1.1.1. Configure R4 so that its LAN interface is joined to Multicast group 227.4.4.4. Verify that R1 can ping R4s Multicast group and that R4 can ping R1s Multicast group.
Lab Validation
Task 1
Please refer to previous tasks for basic VLAN and IP addressing configuration. These will not be included in this section for brevity and to avoid being redundant.
Task 2
Please refer to previous labs for basic EIGRP configuration. Following this, verify your EIGRP configuration using the show ip eigrp neighbors andshow ip route commands. Following this configuration, your route tables should show the following route information:
| R1#show ip route eigrp 10.0.0.0/30 is subnetted, 3 subnets D 10.0.0.8 [90/2681856] via 10.0.0.2, 00:00:12, Serial0/0 D 10.0.0.12 [90/21536000] via 10.0.0.2, 00:00:12, Serial0/0 150.4.0.0/24 is subnetted, 1 subnets D 150.4.4.0 [90/21538560] via 10.0.0.2, 00:00:12, Serial0/0 |
| R2#show ip route eigrp 10.0.0.0/30 is subnetted, 3 subnets D 10.0.0.12 [90/21024000] via 10.0.0.10, 00:00:22, Serial0/1 150.1.0.0/24 is subnetted, 1 subnets D 150.1.1.0 [90/2172416] via 10.0.0.1, 00:00:17, Serial0/0 150.4.0.0/24 is subnetted, 1 subnets D 150.4.4.0 [90/21026560] via 10.0.0.10, 00:00:22, Serial0/1 |
| R3#show ip route eigrp 10.0.0.0/30 is subnetted, 3 subnets D 10.0.0.0 [90/21024000] via 10.0.0.9, 00:00:25, Serial1/1 150.1.0.0/24 is subnetted, 1 subnets D 150.1.1.0 [90/21026560] via 10.0.0.9, 00:00:20, Serial1/1 150.4.0.0/24 is subnetted, 1 subnets D 150.4.4.0 [90/20514560] via 10.0.0.14, 00:00:31, Serial1/2 |
| R4#show ip route eigrp 10.0.0.0/30 is subnetted, 3 subnets D 10.0.0.8 [90/21024000] via 10.0.0.13, 00:00:34, Serial0/0 D 10.0.0.0 [90/21536000] via 10.0.0.13, 00:00:28, Serial0/0 150.1.0.0/24 is subnetted, 1 subnets D 150.1.1.0 [90/21538560] via 10.0.0.13, 00:00:23, Serial0/0 |
Task 3
The core requirement of this task is straightforward. However, in order to complete this task as required you need to understand, from the wording, what version of IGMP is required. Specifically, the task is requiring that IGMPv3 be enabled. IGMP version 3, the most recent modification of the IGMP specification, is defined in RFC 3376. This version now allows the host to request traffic from a specific host in the network. Hosts can also specify a list of sources that they should not receive Multicast traffic from. These changes provide support for the use of Source Specific Multicast within the 232.0.0.0 /8 Multicast group address range. Given this understanding, this task is completed as follows:
| R1(config)#ip multicast-routing R1(config)#interface fastethernet 0/0 R1(config-if)#ip igmp version 3 R1(config-if)#ip pim dense-mode R1(config-if)#exit |
| R4(config)#ip multicast-routing R4(config)#interface fastethernet 0/0 R4(config-if)#ip igmp version 3 R4(config-if)#ip pim dense-mode R4(config-if)#exit |
Next, verify your configuration using the show ip igmp interface command:
| R1#show ip igmp interface fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Internet address is 150.1.1.1/24 IGMP is enabled on interface Current IGMP host version is 3 Current IGMP router version is 3 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: 1 joins, 0 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 150.1.1.1 (this system) IGMP querying router is 150.1.1.1 (this system) Multicast groups joined by this system (number of users): 224.0.1.40(1) |
| R4#show ip igmp interface fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Internet address is 150.4.4.4/24 IGMP is enabled on interface Current IGMP host version is 3 Current IGMP router version is 3 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: 1 joins, 0 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 150.4.4.4 (this system) IGMP querying router is 150.1.1.1 Multicast groups joined by this system (number of users): 224.0.1.40(1) |
Notice in the last line of the output that the interface is automatically joined to group 224.0.1.40. This group is for Cisco RP Discovery messages. The interface is automatically joined to this group because Dense mode assumes that all hosts wants to receive Multicast traffic, unless they explicitly state that they do not. This group is enabled by default; however, it is not applicable in this section because there is no RP when PIM dense mode is enabled. It simply indicates that the interface is listening for packets that may be sent to this group address.
Task 4
The requirements of this task are straightforward. This task is completed as follows:
| R1(config)#interface serial 0/0 R1(config-if)#ip pim dense-mode R1(config-if)#exit |
| R2(config)#ip multicast-routing R2(config)#interface serial 0/0 R2(config-if)#ip pim dense-mode R2(config-if)#exit R2(config)#interface serial 0/1 R2(config-if)#ip pim dense-mode R2(config-if)#exit |
| R3(config)#ip multicast-routing R3(config)#interface serial 1/1 R3(config-if)#ip pim dense-mode R3(config-if)#exit R3(config)#interface serial 1/2 R3(config-if)#ip pim dense-mode R3(config-if)#exit |
| R4(config)#interface serial 0/0 R4(config-if)#ip pim dense-mode R4(config-if)#exit |
Next, verify PIM Dense Mode parameters using the show ip pim interface command:
| R4#show ip pim interface serial 0/0 detail Serial0/0 is up, line protocol is up Internet address is 10.0.0.14/30 Multicast switching: fast Multicast packets in/out: 254/0 Multicast TTL threshold: 0 PIM: enabled PIM version: 2, mode: dense PIM DR: 0.0.0.0 PIM neighbor count: 1 PIM Hello/Query interval: 30 seconds PIM Hello packets in/out: 4/5 PIM State-Refresh processing: enabled PIM State-Refresh origination: disabled PIM NBMA mode: disabled PIM ATM multipoint signalling: disabled PIM domain border: disabled Multicast Tagswitching: disabled |
Task 5
To configure a router interface to join a Multicast group, a technique commonly used to test the Multicast configuration, use the ip igmp join-group <group> interface command:
| R1(config)#interface fastethernet 0/0 R1(config-if)#ip igmp join-group 227.1.1.1 R1(config-if)#exit |
| R4(config)#interface fastethernet 0/0 R4(config-if)#ip igmp join-group 227.4.4.4 R4(config-if)#exit |
Next, verify your configuration using the show ip igmp interface command:
| R1#show ip igmp interface fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Internet address is 150.1.1.1/24 IGMP is enabled on interface Current IGMP host version is 3 Current IGMP router version is 3 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 enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 150.4.4.4 IGMP querying router is 150.1.1.1 (this system) Multicast groups joined by this system (number of users): 224.0.1.40(1) 227.1.1.1(1) |
| R4#show ip igmp interface fastethernet 0/0 FastEthernet0/0 is up, line protocol is up Internet address is 150.4.4.4/24 IGMP is enabled on interface Current IGMP host version is 3 Current IGMP router version is 3 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: 2 joins, 0 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 150.4.4.4 (this system) IGMP querying router is 150.1.1.1 Multicast groups joined by this system (number of users): 224.0.1.40(1) 227.4.4.4(1) |
Finally, complete the task by pinging the Multicast groups from routers R1 and R4:
| R1#ping 227.4.4.4
Type escape sequence to abort. Reply to request 0 from 10.0.0.14, 40 ms |
| R4#ping 227.1.1.1
Type escape sequence to abort. Reply to request 0 from 10.0.0.1, 40 ms |
Final Router Configurations
R1
|
R1#term len 0 Current configuration : 986 bytes R1# |
R2
|
R2#term len 0 Current configuration : 906 bytes R2# |
R3
|
R3#term len 0 Current configuration : 1247 bytes R3# |
R4
|
R4#term len 0 Current configuration : 955 bytes R4# |
