Multicast Overview. IP Multicasting: Explaining Multicast. Lesson Cisco Systems, Inc. All rights reserved. Cisco Public. BSCI Module 7 Lesson 1

IP Multicast Distribute information to large audiences over an IP network BSCI Module 7 3 Multicast Adoption Past, Present, and Future Research Community MBONE Early Adopters NASA, DOD, Cisco, Microsoft, Sprint Financials NASDAQ, NYSE, LIFE, Morgan, GS, Prudential Multicast (1986-2005) Corporate Communication HP, IBM, Intel, Ford, BMW, Dupont E Learning 150 Universities in US, Hawaii, Oregon, USC, UCLA, Berkley MXU & Content Providers Fastweb, B2, Yahoo, BBC, CNN Multicast Deployment Surveillance Law Enforcement and Federal IPv6 Multicast NTT, Sony, Panasonic, Multicast VPN C&W, MCI, AT&T, TI, FT, DT, NTT 1986 z z z 1992 1996 1997 1998 2000 2001 2002 2003 2004 2005 Time BSCI Module 7 4 2

Why Multicast? Used when sending same data to multiple receivers Better bandwidth utilization Less host/router processing Used when addresses of receivers unknown Used when simultaneous delivery for a group of receivers is required (simulcast) BSCI Module 7 5 Unicast vs. Multicast BSCI Module 7 6 3

Multicast Advantages Enhanced efficiency: Controls network traffic and reduces server and CPU loads Optimized performance: Eliminates traffic redundancy Distributed applications: Makes multipoint applications possible BSCI Module 7 7 Other Multicast Advantages For the equivalent amount of multicast traffic, the sender needs much less processing power and bandwidth. Multicast packets do not impose as high a rate of bandwidth utilization as unicast packets, so there is a greater possibility that they will arrive almost simultaneously at the receivers. BSCI Module 7 8 4

Multicast Disadvantages Multicast is UDP-based. Best-effort delivery Heavy drops in Voice traffic Moderate to Heavy drops in Video No congestion avoidance Duplicate packets may be generated Out-of-sequence delivery may occur Efficiency issues in filtering and in security BSCI Module 7 9 Types of Multicast Applications One-to-many A single host sending to two or more (n) receivers Many-to-many Any number of hosts sending to the same multicast group; hosts are also members of the group (sender = receiver) Many-to-one Any number of receivers sending data back to a source (via unicast or multicast) BSCI Module 7 10 5

IP Multicast Applications Live TV and Radio Broadcast to the Desktop Multicast File Transfer Data and File Replication Distance Learning Corporate Broadcasts Training Whiteboard/Collaboration Real-Time Data Delivery Financial Videoconferencing Video-on-Demand BSCI Module 7 11 Self Check 1. List some advantages of multicast transmission over unicast transmission. 2. How does the best effort delivery nature of UDP impact multicast transmissions? 3. What are the 3 basic types of multicast applications? 4. Give examples of one-to-many. 5. What model is used when a host can be a sender as well as a receiver simultaneously? BSCI Module 7 12 6

Multicast Addressing BSCI Module 7 13 IP Multicast Address Structure IP group addresses: Class D address (high-order three bits are set) Range from 224.0.0.0 through 239.255.255.255 BSCI Module 7 14 7

Multicast Addressing IPv4 Header Version IHL Type of Service Total Length Identification Flags Fragment Offset Source Address can never be Class D Multicast Group Address Time to Live Protocol Header Checksum Source Source Address 1.0.0.0-223.255.255.255 (Class A, B, C) Destination Destination Address 224.0.0.0-239.255.255.255 (Class D) Multicast Group Address Range Options Padding BSCI Module 7 15 IP Multicast Address Groups Local scope addresses 224.0.0.0 to 224.0.0.255 Global scope addresses 224.0.1.0 to 238.255.255.255 Administratively scoped addresses 239.0.0.0 to 239.255.255.255 BSCI Module 7 16 8

Local Scope Addresses Well-known addresses assigned by IANA Reserved use: 224.0.0.0 through 224.0.0.255 224.0.0.1 (all multicast systems on subnet) 224.0.0.2 (all routers on subnet) 224.0.0.4 (all DVMRP routers) 224.0.0.13 (all PIMv2 routers) 224.0.0.5, 224.0.0.6, 224.0.0.9, and 224.0.0.10 used by unicast routing protocols BSCI Module 7 17 Global Scope Addresses Transient addresses, assigned and reclaimed dynamically (within applications): Global range: 224.0.1.0-238.255.255.255 224.2.X.X usually used in MBONE applications Part of a global scope recently used for new protocols and temporary usage BSCI Module 7 18 9

Administratively Scoped Addresses Transient addresses, assigned and reclaimed dynamically (within applications): Limited (local) scope: 239.0.0.0/8 for private IP multicast addresses (RFC-2365) Site-local scope: 239.255.0.0/16 Organization-local scope: 239.192.0.0 to 239.251.255.255 BSCI Module 7 19 Layer 2 Multicast Addressing IEEE 802.3 MAC Address Format BSCI Module 7 20 10

IANA Ethernet MAC Address Range Available range of MAC addresses for IP multicast 01-00-5e-00-00-00 through 01-00-5e-7f-ff-ff BSCI Module 7 21 IANA Ethernet MAC Address Range Available range of MAC addresses for IP multicast 00000001:00000000:01011110:00000000:00000000:00000000 through 00000001:00000000:01011110:01111111:11111111:11111111 Within this range, these MAC addresses have the first 25 bits in common. The remaining 23 bits are available for mapping to the lower 23 bits of the IP multicast group address. BSCI Module 7 22 11

Ethernet MAC Address Mapping BSCI Module 7 23 Multicast Addressing IP Multicast MAC Address Mapping (FDDI & Ethernet) Be Aware of the 32:1 Address Overlap 32 - IP Multicast Addresses 224.1.1.1 224.129.1.1 225.1.1.1 225.129.1.1. 238.1.1.1 238.129.1.1 239.1.1.1 239.129.1.1 1 - Multicast MAC Address (FDDI and Ethernet) 0x0100.5E01.0101 BSCI Module 7 24 12

Madcap in MS Server BSCI Module 7 25 How are Multicast Addresses Assigned? Static Global Group Address Assignment Temporary method to meet immediate needs Group range: 233.0.0.0 233.255.255.255 Your AS number is inserted in middle two octets Remaining low-order octet used for group assignment Defined in RFC 2770 GLOP Addressing in 233/8 Manual address allocation by the admin is still the most common practice. BSCI Module 7 26 13

Learning About Multicast Sessions Potential receivers have to learn about multicast streams or sessions available before a multicast application is launched. Possibilities: Another multicast application sending to a well-known group whose members are all potential receivers Directory services Web page, e-mail Session Announcement Protocol (SAP) BSCI Module 7 27 sdr Session Directory BSCI Module 7 28 14

A Cisco IP/TV Example Cisco IP/TV application Clients (viewers) use program listing Contact the server directly Listen to SAP announcements BSCI Module 7 29 Self Check 1. What is the address range for multicast addresses? 2. What are Local Scope Addresses? 3. What is Mbone? 4. What is the 32-to-1 overlap? 5. What is MADCAP? BSCI Module 7 30 15

Internet Group Management Protocol (IGMP) How hosts tell routers about group membership Routers solicit group membership from directly connected hosts RFC 1112 specifies IGMPv1 Supported on Windows 95 RFC 2236 specifies IGMPv2 Supported on latest service pack for Windows and most UNIX systems RFC 3376 specifies IGMPv3 Supported in Window XP and various UNIX systems BSCI Module 7 33 IGMPv2 RFC 2236 Group-specific query Router sends query membership message to a single group rather than all hosts at 224.0.0.1 (reduces traffic). Leave group message Host sends leave message if it leaves the group and is the last member (reduces leave latency in comparison to v1). Query-interval response time The Query router sets the maximum Query-Response time (controls burstiness and fine-tunes leave latencies). Querier election process IGMPv2 routers can elect the Query Router without relying on the multicast routing protocol. BSCI Module 7 34 17

IGMPv2 Joining a Group 224.1.1.1 Join Group BSCI Module 7 35 IGMPv2 Leaving a Group IGMPv2 has explicit Leave Group messages, which reduces overall leave latency. BSCI Module 7 36 18

IGMPv2 Leaving a Group (Cont.) Hosts H2 and H3 are members of group 224.1.1.1. 1. H2 sends a leave message. BSCI Module 7 37 IGMPv2 Leaving a Group (Cont.) 2. Router sends group-specific query. BSCI Module 7 38 19

IGMPv2 Leaving a Group (Cont.) 3. A remaining member host sends report, so group remains active. BSCI Module 7 39 IGMPv2 Leaving a Group (Cont.) BSCI Module 7 40 20

IGMPv2 Leaving a Group (Cont.) BSCI Module 7 41 IGMPv3 Joining a Group Joining member sends IGMPv3 report to 224.0.0.22 immediately upon joining. BSCI Module 7 42 21

IGMPv3 Joining Specific Source(s) IGMPv3 Report contains desired sources in the Include list. Only Included sources are joined. BSCI Module 7 43 IGMPv3 Maintaining State Router sends periodic queries: All IGMPv3 members respond. Reports contain multiple group state records. BSCI Module 7 44 22

Self Check 1. What is the primary purpose of IGMP? 2. When 2 IGMP routers are located on the same Ethernet segment, which router will be the designated querier? 3. What does the ICMPv2 Query router doe when it receives a Leave Message? BSCI Module 7 45 IGMP Layer 2 Issues BSCI Module 7 46 23

Determining IGMP Version Running Determining which IGMP version is running on an interface. rtr-a>show ip igmp interface e0 Ethernet0 is up, line protocol is up Internet address is 1.1.1.1, subnet mask is 255.255.255.0 IGMP is enabled on interface Current IGMP version is 2 CGMP is disabled on interface IGMP query interval is 60 seconds IGMP querier timeout is 120 seconds IGMP max query response time is 10 seconds Inbound IGMP access group is not set Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 1.1.1.1 (this system) IGMP querying router is 1.1.1.1 (this system) Multicast groups joined: 224.0.1.40 224.2.127.254 BSCI Module 7 47 Layer 2 Multicast Frame Switching Problem: Layer 2 flooding of multicast frames Typical Layer 2 switches treat multicast traffic as unknown or broadcast and must flood the frame to every port (in VLAN). Static entries may sometimes be set to specify which ports receive which groups of multicast traffic. Dynamic configuration of these entries may reduce administration. BSCI Module 7 48 24

Layer 2 Multicast Switching Solutions Cisco Group Management Protocol (CGMP): Simple, proprietary; routers and switches IGMP snooping: Complex, standardized, proprietary implementations; switches only BSCI Module 7 49 Layer 2 Multicast Frame Switching CGMP Solution 1: CGMP Runs on switches and routers. CGMP packets sent by routers to switches at the CGMP multicast MAC address of 0100.0cdd.dddd. CGMP packet contains: Type field: join or leave MAC address of the IGMP client Multicast MAC address of the group Switch uses CGMP packet information to add or remove an entry for a particular multicast MAC address. BSCI Module 7 50 25

IGMP Snooping Solution 2: IGMP snooping Switches become IGMP-aware. IGMP packets are intercepted by the CPU or by special hardware ASICs. Switch examines contents of IGMP messages to learn which ports want what traffic. Effect on switch without Layer 3-aware Hardware/ASICs Must process all Layer 2 multicast packets Administration load increased with multicast traffic load Effect on switch with Layer 3-aware Hardware/ASICs Maintain high-throughput performance but cost of switch increases BSCI Module 7 51 IGMPv3 and IGMP Snooping Impact of IGMPv3 on IGMP Snooping IGMPv3 Reports are sent to a separate group (224.0.0.22) reduces load on switch CPU No Report Suppression in IGMPv3 IGMP Snooping should not cause a serious performance problem once IGMPv3 is implemented. BSCI Module 7 52 26

Self Check 1. What command is used to determine the version of IGMP active on an interface? 2. How does a typical layer 2 switch treat multicast traffic? 3. What is CGMP? 4. What type of switch is recommending for use with IGMP snooping? BSCI Module 7 53 Resources Wikipedia IP Multicast article http://en.wikipedia.org/wiki/ip_multicast Webopedia Mbone article http://www.webopedia.com/term/m/mbone.html BSCI Module 7 54 27

Resources Wikipedia IGMP article http://en.wikipedia.org/wiki/igmp Multicast in a Campus Network: CGMP and IGMP Snooping http://www.cisco.com/warp/public/473/22.html IP Multicast Glossary of Terms http://www.cisco.com/en/us/tech/tk828/tech_brief0900aecd801 bca26.html BSCI Module 7 55 IP Multicasting: Multicast Routing Protocols and Verification BSCI Module 7 Lesson 3 & 4 BSCI Module 7 Lesson 1 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 56 28

Multicast Distribution Trees BSCI Module 7 57 Multicast Protocol Basics Types of multicast distribution trees: Source distribution trees; also called shortest path trees (SPTs) Shared distribution trees; rooted at a meeting point in the network A core router serves as a rendezvous point (RP) BSCI Module 7 58 29

Multicast Distribution Trees Shortest Path or Source Distribution Tree Source 1 Notation: (S, G) S = Source G = Group Source 2 A B D F C E Receiver 1 Receiver 2 BSCI Module 7 59 Multicast Distribution Trees Shortest Path or Source Distribution Tree Source 1 Notation: (S, G) S = Source G = Group Source 2 A B D F C E Receiver 1 Receiver 2 BSCI Module 7 60 30

Multicast Distribution Trees Shared Distribution Tree Notation: (*, G) * = All Sources G = Group A B D (RP) F C E (RP) PIM Rendezvous Point Shared Tree Receiver 1 Receiver 2 BSCI Module 7 61 Multicast Distribution Trees Shared Distribution Tree Source 1 Notation: (*, G) * = All Sources G = Group Source 2 A B D (RP) F C E (RP) PIM Rendezvous Point Shared Tree Source Tree Receiver 1 Receiver 2 BSCI Module 7 62 31

Multicast Distribution Trees Characteristics of Distribution Trees Source or Shortest Path trees Uses more memory but optimal paths from source to all receivers; minimizes delay Shared trees Uses less memory but sub-optimal paths from source to all receivers; may introduce extra delay BSCI Module 7 63 Multicast Routing BSCI Module 7 64 32

Protocols for IP Multicast Routing PIM is used between routers so that they can track which multicast packets to forward to each other and to their directly connected LANs. BSCI Module 7 65 Multicast Tree Creation PIM Join/Prune Control Messages Used to create/remove Distribution Trees Shortest Path trees PIM control messages are sent toward the Source Shared trees PIM control messages are sent toward RP BSCI Module 7 66 33

Multicast Forwarding Multicast routing operation is the opposite of unicast routing. Unicast routing is concerned with where the packet is going. Multicast routing is concerned with where the packet comes from. Multicast routing uses Reverse Path Forwarding (RPF) to prevent forwarding loops. BSCI Module 7 67 Reverse Path Forwarding (RPF) The RPF Calculation The multicast source address is checked against the unicast routing table. This determines the interface and upstream router in the direction of the source to which PIM Joins are sent. This interface becomes the Incoming or RPF interface. A router forwards a multicast datagram only if received on the RPF interface. BSCI Module 7 68 34

Reverse Path Forwarding (RPF) RPF Calculation 10.1.1.1 Based on Source Address. Best path to source found in Unicast Route Table. Join Determines where to send Joins. Joins continue towards Source to build multicast tree. Multicast data flows down tree. E0 Join E2 E1 Unicast Route Table Network Interface 10.1.0.0/24 E0 BSCI Module 7 69 Reverse Path Forwarding (RPF) RPF Calculation (cont.) Repeat for other receivers 10.1.1.1 Join Join E0 E1 E2 BSCI Module 7 70 35

Reverse Path Forwarding (RPF) RPF Calculation What if we have equal-cost paths? We can t use both. Tie-Breaker Use highest Next-Hop IP address. 10.1.1.1 1.1.1.1 Unicast Route Table Network Intfc Nxt-Hop 10.1.0.0/24 E0 1.1.1.1 10.1.0.0/24 E1 1.1.2.1 E0 Join E1 E2 1.1.2.1 BSCI Module 7 71 Multicast Distribution Tree Creation Shared Tree Example BSCI Module 7 72 36

PIM Dense Mode Operation BSCI Module 7 73 PIM-DM Flood and Prune Initial Flooding BSCI Module 7 74 37

PIM-DM Flood and Prune (Cont.) BSCI Module 7 75 PIM-DM Flood and Prune (Cont.) Results After Pruning BSCI Module 7 76 38

PIM Sparse Mode Operation BSCI Module 7 77 PIM Sparse Mode PIM-SM works with any of the underlying unicast routing protocols. PIM-SM supports both source and shared trees. PIM-SM is based on an explicit pull model. PIM-SM uses an RP. Senders and receivers meet each other. Senders are registered with RP by their first-hop router. Receivers are joined to the shared tree (rooted at the RP) by their local DR. BSCI Module 7 78 39

PIM-SM Shared Tree Join RP (*, G) Join Shared Tree (*, G) State created only along the Shared Tree. Receiver BSCI Module 7 79 PIM-SM Sender Registration Source RP Traffic Flow Shared Tree Source Tree (S, G) Register (S, G) Join (unicast) Receiver (S, G) State created only along the Source Tree. BSCI Module 7 80 40

PIM-SM Sender Registration Source RP Traffic Flow Shared Tree Source Tree (S, G) Register (S, G) Register-Stop (unicast) (unicast) Receiver (S, G) traffic begins arriving at the RP through the Source tree. RP sends a Register-Stop back to the first-hop router to stop the Register process. BSCI Module 7 81 PIM-SM Sender Registration Source RP Traffic Flow Shared Tree Source Tree Receiver Source traffic flows natively along SPT to RP. From RP, traffic flows down the Shared Tree to Receivers. BSCI Module 7 82 41

PIM-SM SPT Switchover Source RP Traffic Flow Shared Tree Source Tree (S, G) Join Receiver Last-hop router joins the Source Tree. Additional (S, G) State is created along new part of the Source Tree. BSCI Module 7 83 PIM-SM SPT Switchover Source RP Traffic Flow Shared Tree Source Tree (S, G)RP-bit Prune Receiver Traffic begins flowing down the new branch of the Source Tree. Additional (S, G) State is created along along the Shared Tree to prune off (S, G) traffic. BSCI Module 7 84 42

PIM-SM SPT Switchover Source RP Traffic Flow Shared Tree Source Tree Receiver (S, G) Traffic flow is now pruned off of the Shared Tree and is flowing to the Receiver through the Source Tree. BSCI Module 7 85 PIM-SM SPT Switchover Source RP Traffic Flow Shared Tree Source Tree (S, G) Prune Receiver (S, G) traffic flow is no longer needed by the RP so it Prunes the flow of (S, G) traffic. BSCI Module 7 86 43

PIM-SM SPT Switchover Source RP Traffic Flow Shared Tree Source Tree Receiver (S, G) Traffic flow is now only flowing to the Receiver through a single branch of the Source Tree. BSCI Module 7 87 The default behavior of PIM-SM is that routers with directly connected members will join the Shortest Path Tree as soon as they detect a new multicast source. PIM-SM Frequently Forgotten Fact BSCI Module 7 Lesson 1 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 88 44

Multiple RPs with Auto RP PIM Sparse-Dense-Mode BSCI Module 7 89 IP Multicasting: Multicast Configuration and Verification BSCI Module 7 Lesson 4 BSCI Module 7 Lesson 1 2006 Cisco Systems, Inc. All rights reserved. Cisco Public 90 45

Multicast Configuration BSCI Module 7 91 Enabling IP Multicast Routing router(config)# ip multicast-routing Enables multicast routing. Enabling IP multicast routing allows the Cisco IOS software to forward multicast packets. BSCI Module 7 92 46

Enabling PIM on an Interface router(config-if)# ip pim { sparse-mode sparse-dense-mode } Enables PIM SM on an interface; the sparse-dense-mode option enables mixed sparse-dense groups. Enabling PIM on an interface also enables IGMP operation on that interface. Recommended method is to use sparse-dense-mode option. BSCI Module 7 93 Announcing the RP and the Group Range It Serves router(config)# ip pim send-rp-announce {interface type} scope {ttl} group-list {acl} Configures a router to be the RP for the local group as defined in the access list. The following example advertises the IP address of Ethernet 0 as the RP for the administratively scoped groups: router(config)# ip pim send-rp-announce ethernet0 scope 16 group-list 1 access-list 1 permit 239.0.0.0 0.255.255.255 BSCI Module 7 94 47

Verifying Multicast Configuration BSCI Module 7 95 Inspecting Multicast Routing Table router# show ip mroute [group-address] [summary] [count] [active kbps] Displays the contents of the IP multicast routing table summary: Displays a one-line, abbreviated summary of each entry in the IP multicast routing table. count: Displays statistics about the group and source, including number of packets, packets per second, average packet size, and bits per second. active: Displays the rate at which active sources are sending to multicast groups. Active sources are those sending at a rate specified in the kbps argument or higher. The kbps argument defaults to 4 kbps. BSCI Module 7 96 48

show ip mroute NA-1#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 - Advertised via MSDP, U - URD, I - Received Source Specific Host Report Outgoing interface flags: H - Hardware switched Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 224.1.1.1), 00:07:54/00:02:59, RP 10.127.0.7, flags: S Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Serial1/3, Forward/Sparse, 00:07:54/00:02:32 (172.16.8.1, 224.1.1.1), 00:01:29/00:02:08, flags: TA Incoming interface: Serial1/4, RPF nbr 10.139.16.130 Outgoing interface list: Serial1/3, Forward/Sparse, 00:00:57/00:02:02 BSCI Module 7 97 show ip pim interface NA-2#show ip pim interface Address Interface Ver/ Nbr Query DR DR Mode Count Intvl Prior 10.139.16.133 Serial0/0 v2/s 1 30 1 0.0.0.0 10.127.0.170 Serial1/2 v2/s 1 30 1 0.0.0.0 10.127.0.242 Serial1/3 v2/s 1 30 1 0.0.0.0 BSCI Module 7 98 49

show ip pim neighbor NA-2#show ip pim neighbor PIM Neighbor Table Neighbor Interface Uptime/Expires Ver DR Address Priority 10.139.16.134 Serial0/0 00:01:46/00:01:28 v2 None 10.127.0.169 Serial1/2 00:01:05/00:01:40 v2 1 (BD) 10.127.0.241 Serial1/3 00:01:56/00:01:18 v2 1 (BD) BSCI Module 7 99 show ip pim rp P4-2#show ip pim rp Group: 224.1.2.3, RP: 10.127.0.7, uptime 00:00:20, expires never P4-2#show ip pim rp mapping PIM Group-to-RP Mappings Group(s) 224.0.1.39/32 RP 10.127.0.7 (NA-1), v1 Info source: local, via Auto-RP Uptime: 00:00:21, expires: never Group(s) 224.0.1.40/32 RP 10.127.0.7 (NA-1), v1 Info source: local, via Auto-RP Uptime: 00:00:21, expires: never Group(s): 224.0.0.0/4, Static RP: 10.127.0.7 (NA-1) BSCI Module 7 100 50

show ip rpf (towards the RP) NA-2#show ip rpf 10.127.0.7 RPF information for NA-1 (10.127.0.7) RPF interface: Serial1/3 RPF neighbor:? (10.127.0.241) RPF route/mask: 10.127.0.7/32 RPF type: unicast (ospf 1) RPF recursion count: 0 Doing distance-preferred lookups across tables (towards the source) NA-2#show ip rpf 10.139.17.126 RPF information for? (10.139.17.126) RPF interface: Serial0/0 RPF neighbor:? (10.139.16.134) RPF route/mask: 10.139.17.0/25 RPF type: unicast (ospf 1) RPF recursion count: 0 Doing distance-preferred lookups across tables BSCI Module 7 101 show ip igmp interface rtr-a>show ip igmp interface e0 Ethernet0 is up, line protocol is up Internet address is 1.1.1.1, subnet mask is 255.255.255.0 IGMP is enabled on interface Current IGMP version is 2 CGMP is disabled on interface IGMP query interval is 60 seconds IGMP querier timeout is 120 seconds IGMP max query response time is 10 seconds Inbound IGMP access group is not set Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 1.1.1.1 (this system) IGMP querying router is 1.1.1.1 (this system) Multicast groups joined: 224.0.1.40 224.2.127.254 BSCI Module 7 102 51

Verifying IGMP Snooping on a Switch switch> show multicast group [igmp] [mac_addr] [vlan_id] Displays information about multicast groups. If igmp keyword is used, only IGMP-learned information is shown. switch> show multicast router [igmp] [mod_num/port_num] [vlan_id] Displays information on dynamically learned and manually configured multicast router ports. If igmp keyword is used, only IGMP-learned information is shown. BSCI Module 7 103 Verifying IGMP Snooping Example BSCI Module 7 104 52

Verifying IGMP Snooping Example (Cont.) Switch> show multicast router igmp Port Vlan ---------- ---------------- 4/1 10 Total Number of Entries = 1 '*' - Configured '+' - RGMP-capable Switch> show multicast group igmp VLAN Dest MAC/Route Des [CoS] Destination Ports or VCs / [Protocol Type] ---- --------------------------------------------------------------------- 10 01-00-5e-00-01-28 4/1 10 01-00-5e-01-02-03 4/1-2 Total Number of Entries = 2 BSCI Module 7 105 Verifying IGMP Snooping Example (Cont.) Switch> show igmp statistics 10 IGMP enabled IGMP statistics for vlan 10: IGMP statistics for vlan 10: Transmit: General Queries: 0 Group Specific Queries: 0 Reports: 0 Leaves: 0 Receive: General Queries: 1 Group Specific Queries: 0 Reports: 2 Leaves: 0 Total Valid pkts: 4 Total Invalid pkts: 0 Other pkts: 1 MAC-Based General Queries: 0 Failures to add GDA to EARL: 0 Topology Notifications: 0 BSCI Module 7 106 53

Q and A BSCI Module 7 107 BSCI Module 7 108 54