Authored By: Anthony Sequeira CCIE# 15626 (R&S), CCDP, CCSP Terry Vinson CCNP Technical Editor: Carl Yost Jr CCIE# 30486 (R&S), Jason Gooley CCNP Technical Consultant: Scott Morris CCIEx4 #4713 (R&S) (ISP-Dial) (Security) (SP), CCDE #2009::13 Editor: Tiffany Pagan
IPv4/6 Multicast Operation and Troubleshooting
Before We Begin This product is part of the IPexpert suite of materials that provide CCIE candidates and network engineers with a comprehensive training program. For information about the full solution, contact an IPexpert Training Advisor today. Telephone: +1.810.326.1444 Email:
[email protected] Congratulations! You now possess one of the ULTIMATE CCIETM Lab preparation and network operation resources available today! Senior engineers, technical instructors, and authors boasting decades of internetworking experience produced this resource. In order to enjoy technical support from IPexpert and your CCIE community, be sure to visit the following Internet resources: http://blog.ipexpert.com http://onlinestudylist.com IPexpert is proud to lead the industry with multiple support options at your disposal free of charge. Our online communities have attracted a membership of over 20,000 of your peers from around the world! At blog.ipexpert.com, you can keep up to date with everything IPexpert does and read the latest in technical articles from word-‐renowned IPexpert instructors. At OnlineStudyList.com, you may subscribe to multiple “SPAM-‐free,” moderated CCIE-‐focused email lists.
Feedback Do you have a suggestion or other feedback regarding this book or other IPexpert products? At IPexpert, we look to you – our valued clients – for the real world, frontline evaluation that we believe is necessary so that we may always improve. Please send an email with your thoughts to
[email protected] or call 1.866.225.8064 (international callers dial +1.810.326.1444). In addition, for those using this book as CCIETM preparation, when you pass the CCIETM Lab exam, we want to hear about it! Email your CCIETM number to
[email protected] and let us know how IPexpert helped you succeed. We would like to send you a gift of thanks and congratulations.
Copyright © by IPexpert, Inc. All Rights Reserved.
i
IPv4/6 Multicast Operation and Troubleshooting
Additional CCIETM Preparation Material IPexpert, Inc. is committed to developing the most effective Cisco CCIETM R&S, Security, Voice and Wireless Lab certification preparation tools available. Our team of certified networking professionals develops the most up-‐to-‐date and comprehensive materials for networking certification, including self-‐ paced workbooks, online Cisco hardware rental, classroom training, online (distance learning) instructor-‐ led training, audio products, and video training materials. Unlike other certification-‐training providers, we employ the most experienced and accomplished teams of experts to create, maintain, and constantly update our products. At IPexpert, we are focus on making your CCIETM Lab preparation more effective.
Issues with this Book This book is carefully edited to ensure the accuracy of all content. Should you find any error whatsoever, please email a page reference and detailed comment to
[email protected]. Your email will be responded to promptly.
Copyright © by IPexpert, Inc. All Rights Reserved.
II
IPv4/6 Multicast Operation and Troubleshooting
IPEXPERT END-‐USER LICENSE AGREEMENT END USER LICENSE FOR ONE (1) PERSON ONLY IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, DO NOT OPEN OR USE THE TRAINING MATERIALS.
This is a legally binding agreement between you and IPEXPERT, the “Licensor,” from whom you have licensed the IPEXPERT training materials (the “Training Materials”). By using the Training Materials, you agree to be bound by the terms of this License, except to the extent these terms have been modified by a written agreement (the “Governing Agreement”) signed by you (or the party that has licensed the Training Materials for your use) and an executive officer of Licensor. If you do not agree to the License terms, the Licensor is unwilling to license the Training Materials to you. In this event, you may not use the Training Materials, and you should promptly contact the Licensor for return instructions. The Training Materials shall be used by only ONE (1) INDIVIDUAL who shall be the sole individual authorized to use the Training Materials throughout the term of this License.
Copyright and Proprietary Rights The Training Materials are the property of IPEXPERT, Inc. ("IPEXPERT") and are protected by United States and International copyright laws. All copyright, trademark, and other proprietary rights in the Training Materials and in the Training Materials, text, graphics, design elements, audio, and all other materials originated by IPEXPERT at its site, in its workbooks, scenarios and courses (the "IPEXPERT Information") are reserved to IPEXPERT. The Training Materials cannot be used by or transferred to any other person. You may not rent, lease, loan, barter, sell or time-‐share the Training Materials or accompanying documentation. You may not reverse engineer, decompile, or disassemble the Training Materials. You may not modify, or create derivative works based upon the Training Materials in whole or in part. You may not reproduce, store, upload, post, transmit, download or distribute in any form or by any means, electronic, mechanical, recording or otherwise any part of the Training Materials and IPEXPERT Information other than printing out or downloading portions of the text and images for your own personal, non-‐commercial use without the prior written permission of IPEXPERT. You shall observe copyright and other restrictions imposed by IPEXPERT. You may not use the Training Materials or IPEXPERT Information in any manner that infringes the rights of any person or entity.
Copyright © by IPexpert, Inc. All Rights Reserved.
III
IPv4/6 Multicast Operation and Troubleshooting
Exclusions of Warranties THE TRAINING MATERIALS AND DOCUMENTATION ARE PROVIDED “AS IS.” LICENSOR HEREBY DISCLAIMS ALL OTHER WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW THE LIMITATION OF INCIDENTAL DAMAGES OR LIMITATIONS ON HOW LONG AN IMPLIED WARRANTY LASTS, SO THE ABOVE LIMITATIONS OR EXCLUSIONS MAY NOT APPLY TO YOU. This agreement gives you specific legal rights, and you may have other rights that vary from state to state.
Choice of Law and Jurisdiction This Agreement shall be governed by and construed in accordance with the laws of the State of Michigan, without reference to any conflict of law principles. You agree that any litigation or other proceeding between you and Licensor in connection with the Training Materials shall be brought in the Michigan state or courts located in Port Huron, Michigan, and you consent to the jurisdiction of such courts to decide the matter. The parties agree that the United Nations Convention on Contracts for the International Sale of Goods shall not apply to this License. If any provision of this Agreement is held invalid, the remainder of this License shall continue in full force and effect.
Limitation of Claims and Liability ANY ACTION ON ANY CLAIM AGAINST IPEXPERT MUST BE BROUGHT BY THE USER WITHIN ONE (1) YEAR FOLLOWING THE DATE THE CLAIM FIRST ACCRUED, OR SHALL BE DEEMED WAIVED. IN NO EVENT WILL THE LICENSOR’S LIABILITY UNDER, ARISING OUT OF, OR RELATING TO THIS AGREEMENT EXCEED THE AMOUNT PAID TO LICENSOR FOR THE TRAINING MATERIALS. LICENSOR SHALL NOT BE LIABLE FOR ANY SPECIAL, INCIDENTAL, INDIRECT, OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, REGARDLESS OF WHETHER LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. WITHOUT LIMITING THE FOREGOING, LICENSOR WILL NOT BE LIABLE FOR LOST PROFITS, LOSS OF DATA, OR COSTS OF COVER.
Entire Agreement This is the entire agreement between the parties and may not be modified except in writing signed by both parties.
Copyright © by IPexpert, Inc. All Rights Reserved.
IV
IPv4/6 Multicast Operation and Troubleshooting
U.S. Government -‐ Restricted Rights The Training Materials and accompanying documentation are “commercial computer Training Materials” and “commercial computer Training Materials documentation,” respectively, pursuant to DFAR Section 227.7202 and FAR Section 12.212, as applicable. Any use, modification, reproduction release, performance, display, or disclosure of the Training Materials and accompanying documentation by the U.S. Government shall be governed solely by the terms of this Agreement and shall be prohibited except to the extent expressly permitted by the terms of this Agreement. IF YOU DO NOT AGREE WITH THE ABOVE TERMS AND CONDITIONS, DO NOT OPEN OR USE THE TRAINING MATERIALS AND CONTACT LICENSOR FOR INSTRUCTIONS ON RETURN OF THE TRAINING MATERIALS.
Copyright © by IPexpert, Inc. All Rights Reserved.
V
IPv4/6 Multicast Operation and Troubleshooting
Table of Contents Before We Begin ...................................................................................................................................... 1 Feedback .................................................................................................................................................. 1 Additional CCIETM Preparation Material .................................................................................................. 2 IPEXPERT END-‐USER LICENSE AGREEMENT ............................................................................................. 3 Copyright and Proprietary Rights ............................................................................................................ 3 Exclusions of Warranties ......................................................................................................................... 4 Choice of Law and Jurisdiction ................................................................................................................. 4 Limitation of Claims and Liability ............................................................................................................. 4 Entire Agreement .................................................................................................................................... 4 U.S. Government -‐ Restricted Rights ....................................................................................................... 5 Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting ......................................... 1-‐1 About the Authors ................................................................................................................................ 1-‐2 About the Technical Editors .................................................................................................................. 1-‐2 About the Technical Consultant ........................................................................................................... 1-‐2 About the Editor ................................................................................................................................... 1-‐3 Who Should Read this Book? ................................................................................................................ 1-‐3 How to Use this Book ........................................................................................................................... 1-‐3 An Introduction to IPv4/6 Multicast ..................................................................................................... 1-‐4 An Introduction to IPv4/6 Multicast Troubleshooting .......................................................................... 1-‐5 Chapter 2: Internet Group Management Protocol (IGMP) ....................................................................... 2-‐1 IGMP Technology Review ..................................................................................................................... 2-‐2 IGMP Version 1 ................................................................................................................................. 2-‐3 IGMP Version 2 ................................................................................................................................. 2-‐4 IGMP Version 3 ................................................................................................................................. 2-‐5 IGMP Leave Process .......................................................................................................................... 2-‐6 The Operation and Troubleshooting of IGMP ...................................................................................... 2-‐7 IGMP Version 1 ................................................................................................................................. 2-‐8
Copyright © by IPexpert, Inc. All Rights Reserved.
VI
IPv4/6 Multicast Operation and Troubleshooting
IGMP Version 2 ............................................................................................................................... 2-‐10 IGMP Version 3 ............................................................................................................................... 2-‐12 IGMP and Multicast Forwarding ..................................................................................................... 2-‐13 Common Issues with IGMP ................................................................................................................. 2-‐14 Host Fails to Send IGMP joins ......................................................................................................... 2-‐14 Switch Fails To Forward IGMP Packets ........................................................................................... 2-‐14 IGMP Packet Filtering ..................................................................................................................... 2-‐15 IGMP Sample Troubleshooting Scenarios ............................................................................................... 2-‐16 Host Fails To Send IGMP Joins ........................................................................................................ 2-‐16 Switch Fails To Forward IGMP Packets ........................................................................................... 2-‐18 IGMP Packet Filtering ..................................................................................................................... 2-‐20 IGMP Show Command Tools .................................................................................................................. 2-‐21 IGMP Debug Command Tools ................................................................................................................. 2-‐24 Chapter Challenge: IGMP Sample Trouble Tickets ................................................................................. 2-‐26 Trouble Ticket #1 ............................................................................................................................ 2-‐26 Trouble Ticket #2 ............................................................................................................................ 2-‐26 Trouble Ticket #3 ............................................................................................................................ 2-‐26 Chapter Challenge: IGMP Sample Trouble Tickets Solutions .................................................................. 2-‐27 Trouble Ticket #1 Solution .............................................................................................................. 2-‐27 Trouble Ticket #2 Solution .............................................................................................................. 2-‐29 Trouble Ticket #3 Solution .............................................................................................................. 2-‐31 Chapter 3: Protocol Independent Multicast -‐ Dense Mode (PIM-‐DM) ..................................................... 3-‐1 PIM-‐DM Technology Review ................................................................................................................. 3-‐2 PIMv1 ................................................................................................................................................ 3-‐2 PIMv2 ................................................................................................................................................ 3-‐2 PIM Dense Mode .............................................................................................................................. 3-‐4 The Operation and Troubleshooting of PIM-‐DM .................................................................................. 3-‐5 Reverse Path Forwarding ................................................................................................................... 22
Copyright © by IPexpert, Inc. All Rights Reserved.
VII
IPv4/6 Multicast Operation and Troubleshooting
Common Issues with PIM-‐DM ............................................................................................................ 3-‐25 RPF Failures ..................................................................................................................................... 3-‐25 Hub and Spoke Designs .................................................................................................................. 3-‐25 Multicast Threshold Problems ........................................................................................................ 3-‐26 PIM-‐DM Sample Troubleshooting Scenarios .......................................................................................... 3-‐27 Fault isolation in PIM-‐DM ............................................................................................................... 3-‐27 PIM-‐DM show Command Tools .............................................................................................................. 3-‐38 PIM-‐DM debug Command Tools ............................................................................................................. 3-‐41 Chapter Challenge: PIM-‐DM Sample Trouble Tickets ............................................................................. 3-‐43 Trouble Ticket #1 ............................................................................................................................ 3-‐43 Trouble Ticket #2 ............................................................................................................................ 3-‐43 Trouble Ticket #3 ............................................................................................................................ 3-‐43 Chapter Challenge: PIM-‐DM Sample Trouble Tickets Solutions ............................................................. 3-‐44 Trouble Ticket #1 Solution .............................................................................................................. 3-‐44 Trouble Ticket #2 Solution .............................................................................................................. 3-‐46 Trouble Ticket #3 Solution .............................................................................................................. 3-‐49 Chapter 4: Protocol Independent Multicast -‐ Sparse Mode (PIM-‐SM) ..................................................... 4-‐1 PIM-‐SM Technology Review ................................................................................................................. 4-‐2 The Operation and Troubleshooting of PIM-‐SM .................................................................................. 4-‐3 Merging the Trees ........................................................................................................................... 4-‐12 The Shortest Path Tree (SPT) .......................................................................................................... 4-‐17 Common Issues with PIM-‐SM ............................................................................................................. 4-‐21 RPF Failures ..................................................................................................................................... 4-‐21 Unicast Routing and Forwarding Problems .................................................................................... 4-‐21 Multicast Routing and Forwarding Problems ................................................................................. 4-‐22 PIM-‐SM Sample Troubleshooting Scenarios ........................................................................................... 4-‐23 PIM-‐SM show Command Tools ............................................................................................................... 4-‐32 PIM-‐SM debug Command Tools ............................................................................................................. 4-‐36
Copyright © by IPexpert, Inc. All Rights Reserved.
VIII
IPv4/6 Multicast Operation and Troubleshooting
Chapter Challenge: PIM-‐SM Sample Trouble Tickets ............................................................................. 4-‐38 Trouble Ticket #1 ............................................................................................................................ 4-‐38 Trouble Ticket #2 ............................................................................................................................ 4-‐38 Trouble Ticket #3 ............................................................................................................................ 4-‐38 Chapter Challenge: PIM-‐SM Sample Trouble Tickets Solutions .............................................................. 4-‐39 Trouble Ticket #1 Solution .............................................................................................................. 4-‐39 Trouble Ticket #2 Solution .............................................................................................................. 4-‐42 Trouble Ticket #3 Solution .............................................................................................................. 4-‐45 Chapter 5: Protocol Independent Multicast – Sparse-‐Dense Mode (PIM-‐S-‐DM) ..................................... 5-‐1 PIM-‐S-‐DM Technology Review .............................................................................................................. 5-‐2 The Operation and Troubleshooting of PIM-‐S-‐DM ............................................................................... 5-‐3 Introduction of the Topology ............................................................................................................ 5-‐3 The Problem with PIM-‐S-‐DM ............................................................................................................ 5-‐8 Common Issues with PIM-‐S-‐DM ......................................................................................................... 5-‐10 RPF Failures ..................................................................................................................................... 5-‐10 Unicast Routing and Forwarding Problems .................................................................................... 5-‐11 Multicast Routing and Forwarding Problems ................................................................................. 5-‐11 PIM-‐S-‐DM Sample Troubleshooting Scenarios ....................................................................................... 5-‐13 RPF Fault Isolation in PIM-‐S-‐DM (for Sparse Mode Traffic) ............................................................ 5-‐13 RPF Fault isolation in PIM-‐S-‐DM (for Dense Mode Traffic) ............................................................. 5-‐16 Unicast Routing and Forwarding Problems .................................................................................... 5-‐18 Multicast Routing and Forwarding problems ................................................................................. 5-‐22 PIM-‐S-‐DM show Command Tools ........................................................................................................... 5-‐28 PIM-‐S-‐DM debug Command Tools ......................................................................................................... 5-‐32 Chapter Challenge: PIM-‐S-‐DM Sample Trouble Tickets .......................................................................... 5-‐34 Trouble Ticket #1 ............................................................................................................................ 5-‐34 Trouble Ticket #2 ............................................................................................................................ 5-‐34 Chapter Challenge: PIM-‐S-‐DM Sample Trouble Tickets Solutions .......................................................... 5-‐35
Copyright © by IPexpert, Inc. All Rights Reserved.
IX
IPv4/6 Multicast Operation and Troubleshooting
Trouble Ticket #1 Solution .............................................................................................................. 5-‐35 Trouble Ticket #2 Solution .............................................................................................................. 5-‐40 Chapter 6: Bidirectional Protocol Independent Multicast (BIDIR-‐PIM) .................................................... 6-‐1 BIDIR-‐PIM Technology Review .............................................................................................................. 6-‐3 The Operation and Troubleshooting of BIDIR-‐PIM ............................................................................... 6-‐5 BIDIR-‐PIM RP .................................................................................................................................... 6-‐5 Host-‐to-‐RP Shared Tree .................................................................................................................... 6-‐7 Source-‐to-‐RP Shared Tree ................................................................................................................. 6-‐9 BIDIR-‐PIM Neighbors and Designated Forwarder Election ............................................................. 6-‐11 Common Issues with BIDIR-‐PIM ......................................................................................................... 6-‐13 RP and DR Failures .......................................................................................................................... 6-‐13 Multicast Routing and Forwarding Problems ................................................................................. 6-‐13 BIDIR-‐PIM Sample Troubleshooting Scenarios ....................................................................................... 6-‐15 RP Failure in BIDIR-‐PIM ................................................................................................................... 6-‐15 DF Failure in BIDIR-‐PIM ................................................................................................................... 6-‐17 Multicast Routing and Forwarding Failure in BIDIR-‐PIM ................................................................ 6-‐20 BIDIR-‐PIM show Command Tools ........................................................................................................... 6-‐24 BIDIR-‐PIM debug Command Tools .......................................................................................................... 6-‐28 Chapter Challenge: BIDIR-‐PIM Sample Trouble Tickets .......................................................................... 6-‐30 Trouble Ticket #1 ............................................................................................................................ 6-‐30 Trouble Ticket #2 ............................................................................................................................ 6-‐30 Chapter Challenge: PIM-‐DM Sample Trouble Tickets Solutions ............................................................. 6-‐31 Trouble Ticket #1 Solution .............................................................................................................. 6-‐31 Trouble Ticket #2 Solution .............................................................................................................. 6-‐33 Chapter 7: Static Rendezvous Points (RPs) ............................................................................................... 7-‐1 Static RP Technology Review ................................................................................................................ 7-‐2 The Operation and Troubleshooting of Static RP ................................................................................. 7-‐3 Introduction to Load Balancing between RPs ................................................................................... 7-‐3
Copyright © by IPexpert, Inc. All Rights Reserved.
X
IPv4/6 Multicast Operation and Troubleshooting
Common Issues with Static RP .............................................................................................................. 7-‐7 Static RP Sample Troubleshooting Scenarios ............................................................................................ 7-‐8 Incorrect RP Assignment ................................................................................................................... 7-‐8 ACL Issue ......................................................................................................................................... 7-‐10 Static Rendezvous Points show Command Tools ................................................................................... 7-‐13 Static Rendezvous Points debug Command Tools .................................................................................. 7-‐17 Chapter Challenge: Static RP Sample Trouble Tickets ............................................................................ 7-‐19 Trouble Ticket #1 ............................................................................................................................ 7-‐19 Chapter Challenge: Static RP Sample Trouble Tickets Solutions ............................................................ 7-‐20 Trouble Ticket #1 Solution .............................................................................................................. 7-‐20 Chapter 8: AutoRP .................................................................................................................................... 8-‐1 AutoRP Technology Review .................................................................................................................. 8-‐2 The Operation and Troubleshooting of Auto-‐RP .................................................................................. 8-‐4 C-‐RP Announcements ....................................................................................................................... 8-‐4 Mapping Agent Assignment and Placement ..................................................................................... 8-‐9 Multicast Routing Topology ............................................................................................................ 8-‐14 Auto-‐RP Listener ............................................................................................................................. 8-‐18 One Last Step .................................................................................................................................. 8-‐31 Common Issues with Auto-‐RP ............................................................................................................ 8-‐33 RPF Failures ..................................................................................................................................... 8-‐33 Multicast Routing and Forwarding Problems ................................................................................. 8-‐33 Auto-‐RP Sample Troubleshooting Scenarios .......................................................................................... 8-‐35 RPF failures ..................................................................................................................................... 8-‐37 Multicast Forwarding and Routing Failures .................................................................................... 8-‐40 AutoRP show Command Tools ................................................................................................................ 8-‐45 AutoRP debug Command Tools .............................................................................................................. 8-‐50 Chapter Challenge: Auto-‐RP Sample Trouble Tickets ............................................................................. 8-‐52 Trouble Ticket #1 ............................................................................................................................ 8-‐52
Copyright © by IPexpert, Inc. All Rights Reserved.
XI
IPv4/6 Multicast Operation and Troubleshooting
Trouble Ticket #2 ............................................................................................................................ 8-‐52 Trouble Ticket #3 ............................................................................................................................ 8-‐52 Chapter Challenge: Auto-‐RP Sample Trouble Tickets Solutions ............................................................. 8-‐53 Trouble Ticket #1 Solution .............................................................................................................. 8-‐53 Trouble Ticket #2 Solution .............................................................................................................. 8-‐55 Trouble Ticket #3 Solution .............................................................................................................. 8-‐59 Chapter 9: Bootstrap Router (BSR) Protocol ............................................................................................ 9-‐1 BSR Technology Review ........................................................................................................................ 9-‐2 The Operation and Troubleshooting of BSR ......................................................................................... 9-‐6 BSR Election/Announcements .......................................................................................................... 9-‐6 Candidate-‐Rendezvous Point Announcement .................................................................................. 9-‐9 Propagation of Group-‐to-‐RP Mappings .......................................................................................... 9-‐10 Load Balancing Between Candidate-‐RPs ........................................................................................ 9-‐12 The Final Step ................................................................................................................................. 9-‐14 Common Issues with BSR .................................................................................................................... 9-‐16 RPF Failures ..................................................................................................................................... 9-‐16 Unicast Routing and Forwarding Problems .................................................................................... 9-‐16 Multicast Routing and Forwarding Problems ................................................................................. 9-‐17 BSR Sample Troubleshooting Scenarios ................................................................................................. 9-‐18 BSR show Command Tools ..................................................................................................................... 9-‐31 BSR debug Command Tools .................................................................................................................... 9-‐35 Chapter Challenge: BSR Sample Trouble Tickets .................................................................................... 9-‐37 Trouble Ticket #1 ............................................................................................................................ 9-‐37 Trouble Ticket #2 ............................................................................................................................ 9-‐37 Trouble Ticket #3 ............................................................................................................................ 9-‐37 Chapter Challenge: BSR Sample Trouble Tickets Solutions .................................................................... 9-‐38 Trouble Ticket #1 Solution .............................................................................................................. 9-‐38 Trouble Ticket #2 Solution .............................................................................................................. 9-‐42
Copyright © by IPexpert, Inc. All Rights Reserved.
XII
IPv4/6 Multicast Operation and Troubleshooting
Trouble Ticket #3 Solution .............................................................................................................. 9-‐45 Chapter 10: Multicast Source Discovery Protocol (MSDP) ..................................................................... 10-‐1 MSDP Technology Review .................................................................................................................. 10-‐2 The Operation and Troubleshooting of MSDP .................................................................................... 10-‐4 Source Active Messages ................................................................................................................. 10-‐4 MSDP RPF Failure ............................................................................................................................ 10-‐5 SA Message Arrives on the RP in the Other Multicast Domain ...................................................... 10-‐5 SA Cache ......................................................................................................................................... 10-‐6 Common Issues with MSDP ................................................................................................................ 10-‐7 Incorrect Peering Configuration ..................................................................................................... 10-‐7 No PIM Enabled Path Between MSDP peers .................................................................................. 10-‐7 MSDP Passwords and Filters ........................................................................................................... 10-‐7 MSDP Sample Troubleshooting Scenarios .............................................................................................. 10-‐8 Incorrect Peering Configuration ..................................................................................................... 10-‐8 No PIM Enabled Path Between MSDP Peers ................................................................................ 10-‐12 MSDP Passwords and Filters ......................................................................................................... 10-‐16 MSDP Show Command Tools ................................................................................................................ 10-‐21 MSDP Debug Command Tools .............................................................................................................. 10-‐23 Chapter Challenge: MSDP Sample Trouble Tickets ............................................................................... 10-‐24 Trouble Ticket #1 .......................................................................................................................... 10-‐24 Trouble Ticket #2 .......................................................................................................................... 10-‐24 Chapter Challenge: MSDP Sample Trouble Tickets Solutions ............................................................... 10-‐25 Trouble Ticket #1 Solution ............................................................................................................ 10-‐25 Trouble Ticket #2 Solution ............................................................................................................ 10-‐27 Chapter 11: Anycast-‐RP .......................................................................................................................... 11-‐1 Anycast-‐RP Technology Review .......................................................................................................... 11-‐2 The Operation and Troubleshooting of Anycast-‐RP ........................................................................... 11-‐3 Common Issues with Anycast-‐RP ........................................................................................................ 11-‐7
Copyright © by IPexpert, Inc. All Rights Reserved.
XIII
IPv4/6 Multicast Operation and Troubleshooting
MSDP Peering Issues ....................................................................................................................... 11-‐7 Unicast Routing Problems ............................................................................................................... 11-‐8 Anycast-‐RP Sample Troubleshooting Scenarios ...................................................................................... 11-‐9 MSDP Peering Issues ....................................................................................................................... 11-‐9 Unicast Routing Problems ............................................................................................................. 11-‐11 Anycast-‐RP Show Command Tools ....................................................................................................... 11-‐15 Anycast-‐RP debug Command Tools ...................................................................................................... 11-‐17 Chapter Challenge: Anycast-‐RP Sample Trouble Tickets ...................................................................... 11-‐18 Trouble Ticket #1 .......................................................................................................................... 11-‐18 Chapter Challenge: Anycast-‐RP Sample Trouble Tickets Solutions ...................................................... 11-‐19 Trouble Ticket #1 Solution ............................................................................................................ 11-‐19 Chapter 12: Multiprotocol-‐BGP (MP-‐BGP) and Interdomain Multicast .................................................. 12-‐1 Multiprotocol-‐BGP Technology Review .............................................................................................. 12-‐3 The Operation and Troubleshooting of MP-‐BGP ................................................................................ 12-‐4 MP-‐BGP ........................................................................................................................................... 12-‐5 Common Issues with MP-‐BGP .......................................................................................................... 12-‐12 Peer Rejects All MSDP SA Messages ............................................................................................. 12-‐12 Failure to Advertise the MSDP Peer Network ............................................................................... 12-‐12 Using Incorrect Addresses to form MSDP Peers ........................................................................... 12-‐12 MP-‐BGP Sample Troubleshooting Scenarios ........................................................................................ 12-‐13 Peer Rejects all MSDP SA Messages ............................................................................................. 12-‐13 Failure to Advertise the MSDP Peer Network ............................................................................... 12-‐15 Incorrect Address Used to form MSDP Peers ............................................................................... 12-‐19 MP-‐BGP Show Command Tools ............................................................................................................ 12-‐22 MP-‐BGP Debug Command Tools .......................................................................................................... 12-‐25 Chapter Challenge: MP-‐BGP Sample Trouble Tickets ........................................................................... 12-‐27 Trouble Ticket #1 .......................................................................................................................... 12-‐27 Trouble Ticket #2 .......................................................................................................................... 12-‐27
Copyright © by IPexpert, Inc. All Rights Reserved.
XIV
IPv4/6 Multicast Operation and Troubleshooting
Chapter Challenge: MP-‐BGP Sample Trouble Tickets Solutions ........................................................... 12-‐28 Trouble Ticket #1 Solution ............................................................................................................ 12-‐28 Trouble Ticket #2 Solution ............................................................................................................ 12-‐30 Chapter 13: Multicast Security and Advanced Features ......................................................................... 13-‐1 The Operation and Troubleshooting of Multicast Security and Advanced Features .............................. 13-‐2 Multicast Filtering on a Cisco Catalyst Switch ................................................................................. 13-‐2 Multicast Route Limiting ................................................................................................................. 13-‐8 Multicasting Through a GRE Tunnel ............................................................................................... 13-‐9 Chapter Challenge: Multicast Security and Advanced Features Sample Trouble Tickets ..................... 13-‐15 Trouble Ticket #1 .......................................................................................................................... 13-‐15 Trouble Ticket #2 .......................................................................................................................... 13-‐15 Chapter Challenge: Multicast Security and Advanced Features Sample Trouble Tickets Solutions ..... 13-‐16 Trouble Ticket #1 Solution ............................................................................................................ 13-‐16 Trouble Ticket #2 Solution ............................................................................................................ 13-‐19 Chapter 14: IPv6 Multicast ..................................................................................................................... 14-‐1 IPv6 Multicast Technology Review ..................................................................................................... 14-‐2 IPv6 Multicast Addressing ............................................................................................................... 14-‐2 Protocol Independent Multicast Version 2 (PIMv2) for IPv6 .......................................................... 14-‐3 Multicast Listener Discovery (MLD) Protocol ................................................................................. 14-‐3 IPv6 PIM Bootstrap Router Protocol (BSR) ..................................................................................... 14-‐4 IPv6 Embedded RP .......................................................................................................................... 14-‐4 The Operation and Troubleshooting of IPv6 Multicast ....................................................................... 14-‐5 IPv6 Multicast Addressing ............................................................................................................... 14-‐5 Protocol Independent Multicast Version 2 (PIMv2) for IPv6 .......................................................... 14-‐6 Multicast Listener Discovery (MLD) Protocol ................................................................................. 14-‐8 IPv6 PIM Bootstrap Router Protocol (BSR) ..................................................................................... 14-‐9 IPv6 Embedded RP .......................................................................................................................... 14-‐9
Copyright © by IPexpert, Inc. All Rights Reserved.
XV
IPv4/6 Multicast Operation and Troubleshooting
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting introduces the team of authors, consultants, and editors that completed this book and describes the book’s purpose. This chapter also provides suggestions for the usage of this written work. This introductory chapter also covers a basic overview of multicast’s operations and troubleshooting concerns. Readers who are very familiar with basic multicast principles may safely skip this section.
Copyright © by IPexpert, Inc. All Rights Reserved.
1-1
IPv4/6 Multicast Operation and Troubleshooting
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting
About the Authors Anthony Sequeira, CCIE No. 15626 (R&S), formally began his career in the information technology industry in 1994 with IBM in Tampa, Florida. He quickly formed his own computer consultancy, Computer Solutions, and then discovered his true passion—teaching and writing about Microsoft and Cisco technologies. Anthony is currently pursuing his second CCIE in the area of Security, and is a full-‐ time instructor for the next generation of KnowledgeNet: www.StormWindLive.com. He recently achieved his VMware Certified Professional certification. When Anthony is not writing or lecturing about the latest innovations in networking technologies, you may find him flying a Cessna in the Florida skies. Terry Vinson, CCNP, Terry Vinson is a highly experienced training consultant, specializing in documentation development, validation, verification and communications. For the last 10 years, Terry has worked in the private sector as a Senior Technology Consultant and Trainer for several consulting firms in Washington DC, Northern and Central Virginia. In this capacity, he has provided services to Major Metropolitan Health Systems, the Mexican Embassy, and the Executive Office of the President of the United States of America (EOP).
About the Technical Editors Carl Yost Jr., CCIE No. 30486 (R&S), currently works as a Network Engineer/Director of I.T. for a health care company in Buffalo NY. He has worked in numerous roles in I.T. since 1998. Carl is currently preparing for the CCIE in Security while living with his wife and children in Western New York. When not surrounded by Cisco devices, Carl truly enjoys working with Redhat Linux. Jason Gooley, CCNP, Jason is a highly motivated network engineer with over 17 years of experience in the communications industry. Based in Chicago, Jason currently manages the network for the nation’s most famous next day carpet company. Jason is currently in the process of pursuing his CCIE certification for Routing and Switching while also expanding his knowledge in Unified Communications and Security.
About the Technical Consultant Scott Morris, CCIEx4, CCDE, JNCIEx2, CISSP, Scott has been one of the most well-‐known figures in the IT industry for over 25 years. He has fulfilled a number of important roles within both the public and private sectors. As a Certified Cisco Systems Instructor (CCSI) and Juniper Networks Certified Instructor (JNCI), Scott has provided world-‐renowned CCIE training since 2002. He has delivered courses to a wide variety of audiences including internal training at Cisco Systems.
Copyright © by IPexpert, Inc. All Rights Reserved.
1-2
IPv4/6 Multicast Operation and Troubleshooting
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting
About the Editor Tiffany Pagan began her career in editing in 1997. Throughout her career, she has worked with several private individuals and companies such as Moffitt Cancer Center and Tampa General Hospital. Tiffany is currently working on writing her own series of short stories as well as working as an editor and personal assistant. Tiffany resides in Tampa, Florida with her husband and three beautiful children.
Who Should Read this Book? This text has two primary audiences. The first audience is for those CCIE candidates that are searching for the most comprehensive and error-‐free materials available for the operation and troubleshooting of key technologies presented in the various tracks of the CCIE written and practical lab exams. These students should possess a home rack of equipment for CCIE-‐level command-‐line practice, they should possess an equipment emulator, or they should rent equipment from a company like www.proctorlabs.com. The authors and technical editors exhaustively tested all of the demonstrations found throughout the text and the important end of chapter Trouble Ticket challenges against all practice rack options described earlier. Where issues arise with popular equipment emulators, the text makes note. This book is the most remarkably thorough and technically accurate book written on the subject of multicast to date. The book’s second audience is those readers that must support multicast technologies in their actual network environments. This book serves as an amazing guide and reference for real-‐world problem solving within production networks that deploy these specific technologies. In fact, while many courses and texts purport to have certification success as a by-‐product of a thorough investigation of all protocols, this book actually succeeds in this approach.
How to Use this Book This book breaks specific multicast technologies down on a chapter-‐by-‐chapter basis for a complete and thorough review of this broad set of topics. Each chapter begins with a review of the selected multicast technology. Following this, the text provides an intense examination of the operation of the protocols, including key aspects of troubleshooting for the specific technology. After this, the chapter presents some of the most common issues that can result with a particular technology, and most importantly, details the simple troubleshooting tools and steps that succeed for remediation. Each chapter concludes with sample troubleshooting scenarios that provide a full walkthrough of a well-‐ designed approach for troubleshooting each major issue. The text provides reference guides for the most popular and powerful show and debug commands for a specific technology. Each chapter concludes with sample Trouble Tickets on the specific technology. Readers may download initial configurations, or install them in a simple Graphical User Interface (GUI) on
Copyright © by IPexpert, Inc. All Rights Reserved.
1-3
IPv4/6 Multicast Operation and Troubleshooting
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting
www.proctorlabs.com. These sample Trouble Tickets allow students to build confidence and expertise by actually troubleshooting issues in the multicast domain presented in the chapter. Students are encouraged to follow along on a rack of equipment for every section of every chapter. This really enhances and strengthens the learning process.
An Introduction to IPv4/6 Multicast IP multicast is a bandwidth-‐conserving technology delivering a single stream of information simultaneously to a large or small number of endpoints within the network. Video conferencing, corporate communications, distance learning, and software distribution, stock quotes, and news are common applications that take advantage of a multicast traffic delivery approach. IP multicast routing enables a source host to send packets to a group of receivers anywhere within the IP network by using a special form of IP address called the IP multicast group address. This special multicast group address forms the destination IP address of the packet. Multicast enabled routers and switches forward these incoming multicast packets out all interfaces that lead to members of the multicast group. Any host, regardless of whether it is a member of a group, can send to a group. However, only the members of a group receive the message. A quick question that arises when examining this multicast approach is – “how can hosts that are interested in receiving the multicast information actually join this multicast group?” Internet Group Management Protocol (IGMP) makes this possible in IPv4, while the Multicast Listener Discovery (MLD) protocol makes this possible in IPv6. Network administrators who assign multicast group addresses must make sure the addresses conform to the multicast address range assignments reserved by the Internet Assigned Numbers Authority (IANA). The IANA assigns the IPv4 Class D address space for multicast. The first four high-‐order bits of a Class D address are 1110. This causes the multicast group addresses to fall in the range 224.0.0.0 to 239.255.255.255. This book fully describes multicast addressing for IPv6 networks in Chapter 14: IPv6 Multicast. To provide predictable behavior for various address ranges and for address reuse within smaller domains, the overall multicast address range shown above is subdivided. • • • •
Reserved link-‐local addresses -‐ 224.0.0.0 to 224.0.0.255 Globally scoped addresses -‐ 224.0.1.0 to 238.255.255.255 – for use on the Internet Source specific multicast -‐ 232.0.0.0 to 232.255.255.255 – source specific delivery model GLOP addresses -‐ 233.0.0.0 to 233.255.255.255 – reserved for use on the Internet by companies that possess a publicly registered AS
Copyright © by IPexpert, Inc. All Rights Reserved.
1-4
IPv4/6 Multicast Operation and Troubleshooting
•
Chapter 1: Introduction to IPv4/6 Multicast Operation and Troubleshooting
Administrative limited scope -‐ 239.0.0.0 to 239.255.255.255 – reserved for internal corporate use
The Protocol Independent Multicast (PIM) protocol is responsible for routing multicast traffic through the network infrastructure. As the name of this protocol conveys, it is not dependent on a specific unicast routing protocol; it is IP routing protocol independent and can leverage the unicast routing protocol used to populate the unicast routing table, including simple static routes. PIM relies upon this unicast routing information to perform the multicast forwarding function. PIM uses the unicast routing table to perform the reverse path forwarding (RPF) check function instead of building up a completely independent multicast routing table. The RPF process is a key in the operation and subsequent troubleshooting of multicast As such, this book covers the RPF process in depth throughout its chapters. Unlike other routing protocols, PIM does not send and receive routing updates between routers. PIM can operate in dense mode or sparse mode. The mode determines how the router populates its multicast routing table and how the router forwards multicast packets it receives from its directly connected LANs.
An Introduction to IPv4/6 Multicast Troubleshooting This book takes a common sense approach for multicast troubleshooting. First, the text carefully dissects the operation of each technology for an intense understanding of the protocol’s operation. Without this intense level of knowledge, troubleshooting is difficult at best, or impossible at worst. The troubleshooting approach separates the control-‐plane from the data-‐plane and relies heavily on the use of the show ip mroute command for control-‐plane verification. As you will discover in this text, a common reason for most issues with multicast routing is incongruence between the Protocol Independent Multicast (PIM) topology and the logical/physical topology. In a perfect world, one deploys multicast in a single Interior Gateway Protocol (IGP) domain with PIM enabled on all links running the IGP. These links should be point-‐to-‐point or broadcast multi-‐access in structure. Should you have multicast running across a domain with multiple IGPs, or you do not have PIM enabled on all links, or you have Non Broadcast Multi-‐Access (NBMA) links, you are at a much greater risk for issues. As one might guess, exam authors (proctors) are very familiar with these issues and intentionally construct CCIE practical lab exam scenarios as such. The next chapter of this text, Chapter 2: Internet Group Management Protocol (IGMP) begins with a thorough analysis of the most logical starting point in the journey. The protocol responsible for hosts indicating their desire to join multicast groups.
Copyright © by IPexpert, Inc. All Rights Reserved.
1-5
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Chapter 2: Internet Group Management Protocol (IGMP) In this chapter of IPv4/6 Multicast Operation and Troubleshooting, the processes and functionality of the Internet Group Management Protocol (IGMP) are examined in great depth. Once the operational characteristics of this important protocol are detailed completely, the focus becomes that of troubleshooting. This includes the careful examination of symptoms, a fault isolation methodology, and the implementation of repairs for the Internet Group Management Protocol (IGMP). The chapter begins with a thorough review of IGMP, and then quickly launches in to an exhaustive analysis of the “art” of troubleshooting this multicast support protocol. This important chapter concludes with sample troubleshooting scenarios, reference materials for the most important show and debug commands, and exciting challenges that allow readers to practice implementing the troubleshooting skills they have obtained.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-1
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
IGMP Technology Review Internet Group Management Protocol (IGMP) dynamically registers individual hosts in a multicast group on a particular LAN. Enabling Protocol Independent Multicast (PIM) on an interface also enables IGMP. IGMP provides a means to automatically control and limit the flow of multicast traffic throughout your network with the use of special multicast queriers and hosts. A querier is a router that sends query messages to discover which network devices are members of a given multicast group. A host, on the other hand, is a receiver that sends report messages (in response to query messages) to inform the querier of a host membership. Hosts use IGMP messages to join and leave multicast groups. Hosts identify group memberships by sending IGMP messages to their local multicast router. These multicast routers listen to IGMP messages and periodically send out queries to discover which groups are active or inactive on a particular subnet. Figure 2-‐1 illustrates a sample IGMP topology.
Figure 2-‐1: A Sample IGMP Topology
This text covers the following three versions of IGMP: •
IGMP version 1 -‐ provides a basic query-‐response mechanism that allows the multicast router to determine which multicast groups are active; also enables hosts to join and leave a multicast group
Copyright © by IPexpert, Inc. All Rights Reserved.
2-2
IPv4/6 Multicast Operation and Troubleshooting
•
•
Chapter 2: Internet Group Management Protocol (IGMP)
IGMP version 2 – introduces the IGMP leave process, group specific queries, and an explicit maximum response time field; also adds the capability for routers to elect the IGMP querier without dependence on the multicast protocol to perform this task IGMP version 3 -‐ provides source filtering; supports the link local address 224.0.0.22, which is the destination IP address for IGMP version 3 membership reports
Note: By default, enabling PIM on an interface enables IGMP version 2 on that interface. IGMP version 2 was designed to be as backward compatible with IGMP version 1 as possible. IGMP Version 1 IGMP version 1 routers send IGMP queries to the "all-‐hosts" multicast address of 224.0.0.1 to solicit multicast groups with active multicast receivers. The multicast receivers also send IGMP reports to the router to notify it that they are interested in receiving a particular multicast stream. Hosts can send the report independently or in response to the IGMP queries sent by the router. If more than one multicast receiver exists for the same multicast group, only one of these hosts sends an IGMP report message; the other hosts suppress their report messages. In IGMP version 1, there is no election of an IGMP querier. If more than one router on the segment exists, all the routers send periodic IGMP queries. IGMP version 1 has no special mechanism by which the hosts can leave the group. If the hosts are no longer interested in receiving multicast packets for a particular group, they simply do not reply to the IGMP query packets sent from the router. The router continues sending query packets. If the router does not hear a response in three IGMP queries, the group times out and the router stops sending multicast packets on the segment for the group. If there are multiple routers on a LAN, a designated router (DR) must be elected to avoid duplicating multicast traffic for connected hosts. PIM routers follow an election process to select a DR. The PIM router with the highest IP address becomes the DR. The DR is responsible for the following tasks: • • •
Sending PIM register, PIM Join, and Prune messages toward the rendezvous point (RP) to inform it about host group memberships Sending IGMP host-‐query messages Sending host-‐query messages in order to keep the IGMP overhead on hosts and networks very low
Copyright © by IPexpert, Inc. All Rights Reserved.
2-3
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
IGMP Version 2 IGMP version 2 improves the query messaging capabilities of IGMP version 1. The query and membership report messages in IGMP version 2 are identical to the IGMP version 1 messages with two exceptions: • •
IGMP version 2 query messages are broken into two categories: general queries (identical to IGMP version 1 queries) and group-‐specific queries IGMP version 1 membership reports and IGMP version 2 membership reports have different IGMP type codes
IGMP version 2 also enhances IGMP by providing support for the following capabilities: • •
• •
Querier election process—IGMP version 2 routers can elect the IGMP querier without having to rely on the multicast routing protocol to perform the process Maximum Response Time field—a new field in query messages permits the IGMP querier to specify the maximum query-‐response time; this feature permits the tuning of the query-‐ response process to control response “burstiness” and to fine-‐tune leave latencies Group-‐Specific Query messages—permits the IGMP querier to perform the query operation on a specific group instead of all groups Leave-‐Group messages—provides hosts with a method of notifying routers on the network that they wish to leave the group
Unlike IGMP version 1, in which the DR and the IGMP querier are typically the same router, in IGMP version 2 the two functions are decoupled. The DR and the IGMP querier are selected based on different criteria and may be different routers on the same subnet. The DR is the router with the highest IP address on the subnet, whereas the IGMP querier is the router with the lowest IP address. Query messages are used to elect the IGMP querier as follows: Step 1 -‐ when an IGMP version 2 router starts, they each multicast a general query message to the all-‐ systems group address of 224.0.0.1 with their interface address in the source IP address field of the message. Step 2 -‐ when an IGMP version 2 router receives a general query message, the router compares the source IP address in the message with its own interface address. The router with the lowest IP address on the subnet is elected the IGMP querier. Step 3 -‐ all routers (excluding the querier) start the query timer, which is reset whenever a general query message is received from the IGMP querier. If the query timer expires, it is assumed that the IGMP querier has gone down, and the election process is performed again to elect a new IGMP querier.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-4
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
By default, the timer is two times the query interval. IGMP Version 3 IGMP version 3 adds support in the IOS for source filtering, which enables a multicast receiver host to signal to a router which groups it wants to receive multicast traffic from, and from which sources this traffic is expected. This membership information enables Cisco IOS software to forward traffic only from those sources from which receivers requested the traffic. IGMP version 3 supports applications that explicitly signal sources from which they want to receive traffic. With IGMP version 3, receivers signal membership to a multicast group in the following two modes: • •
INCLUDE mode— the receiver announces membership to a group and provides a list of IP addresses (the INCLUDE list) from which it wants to receive traffic EXCLUDE mode—the receiver announces membership to a group and provides a list of IP addresses (the EXCLUDE list) from which it does not want to receive traffic; to receive traffic from all sources, like in the case of the Internet Standard Multicast (ISM) service model, a host expresses EXCLUDE mode membership with an empty EXCLUDE list
IGMP version 3 is the industry-‐designated standard protocol for hosts to signal channel subscriptions in a Source Specific Multicast (SSM) network. For SSM to rely on IGMP version 3, IGMP version 3 must be available in the network stack portion of the operating systems running on the last hop routers, hosts and be used by the applications running on those hosts. In IGMP version 3, hosts send their membership reports to 224.0.0.22; all IGMP version 3 routers, therefore, must listen to this address. Hosts, however, do not listen or respond to 224.0.0.22; they only send their reports to that address. In addition, in IGMP version 3, there is no membership report suppression because IGMP version 3 hosts do not listen to the reports sent by other hosts. Therefore, when a general query is sent out, all hosts on the wire respond. When a host wants to join a multicast group, the host sends one or more unsolicited membership reports for the multicast group it wants to join. The IGMP join process is the same for IGMP version 1 and IGMP version 2 hosts. In IGMP version 3, the join process for hosts proceeds as follows: • •
When a hosts wants to join a group, it sends an IGMP version 3 membership report to 224.0.0.22 with an empty EXCLUDE list When a host wants to join a specific channel, it sends an IGMP version 3 membership report to 224.0.0.22 with the address of the specific source included in the INCLUDE list
Copyright © by IPexpert, Inc. All Rights Reserved.
2-5
IPv4/6 Multicast Operation and Troubleshooting
•
Chapter 2: Internet Group Management Protocol (IGMP)
When a host wants to join a group excluding particular sources, it sends an IGMP version 3 membership report to 224.0.0.22 excluding those sources in the EXCLUDE list
IGMP Leave Process The method that hosts use to leave a group varies depending on the version of IGMP in operation. IGMP Version 1 Leave Process There is no leave-‐group message in IGMP version 1 to notify the routers on the subnet that a host no longer wants to receive the multicast traffic from a specific group. The host simply stops processing traffic for the multicast group and ceases responding to IGMP queries with IGMP membership reports for the group. As a result, the only way IGMP version 1 routers know that there are no longer any active receivers for a particular multicast group on a subnet is when the routers stop receiving membership reports. To facilitate this process, IGMP version 1 routers associate a countdown timer with an IGMP group on a subnet. When a membership report is received for the group on the subnet, the timer is reset. For IGMP version 1 routers, this timeout interval is typically three times the query interval (3 minutes). This timeout interval means that the router may continue to forward multicast traffic onto the subnet for up to 3 minutes after all hosts have left the multicast group. IGMP Version 2 Leave Process IGMP version 2 incorporates a leave-‐group message that provides the means for a host to indicate that it wishes to stop receiving multicast traffic for a specific group. When an IGMP version 2 host leaves a multicast group, if it was the last host to respond to a query with a membership report for that group, it sends a leave-‐group message to the all-‐routers multicast group (224.0.0.2). IGMP Version 3 Leave Process IGMP version 3 enhances the leave process by introducing the capability for a host to stop receiving traffic from a particular group, source, or channel in IGMP by including or excluding sources, groups, or channels in IGMP version 3 membership reports.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-6
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
The Operation and Troubleshooting of IGMP Multicast technology has developed significantly since its introduction in the late 1990's. This is abundantly evident when considering the large number of multicast-‐enabled applications developed in the last few years. Some multicast applications used on a daily basis include webinars, video conferencing, internet radio, IPTV and network gaming. These applications share one critical element; they require real-‐time data flow between a group of receivers and a set of sources. In instances where multiple receivers have a need for the same data, multicast technology is a natural fit, because it enables the efficient transfer of data from a single source or a set of sources to a dynamically formed group of receivers. The concept of IP multicast was the perfect solution to this one-‐to-‐many model of data distribution. However, IP multicast brought with it, its own issues. This section focuses on the first of these issues: •
Maintenance of dynamic group membership information -‐ A router must maintain group member information so that it can efficiently forward the necessary multicast data to interested receivers.
IP multicast environments propagate membership information via Internet Group Management Protocol (IGMP). IGMP propagates membership information from the host toward the routers attached to discreet sources. This is odd behavior when compared to the typical unicast routing model. So odd, in fact, that many phrases exist to describe this process including "upside-‐down routing" or "bottoms-‐up routing.” It is important to understand this concept early on. Multicasting routes packets away from the source (toward the receivers) not toward a given destination. Understanding this one concept will make deploying and troubleshooting IP multicast much simpler. In summary, routers attached to multicast sources learn about group members via IGMP. This section will take an exhaustive look at the operation and troubleshooting of the three versions of IGMP protocol by using the topology in the Figure 2-‐2.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-7
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Figure 2-‐2: IGMP Lab Topology
IGMP Version 1 A critical analysis of the inner working of IGMP version 1 must begin with the protocol message types it supports: •
•
IGMPv1 Membership Query Messages -‐ Generated by the IGMP querier -‐ One multicast router per LAN must periodically transmit host "membership query messages". These messages identify which groups have members on a directly connected network. Query Messages use an address of 224.0.0.1. An adjacent router does not forward query messages to any other multicast enabled router. IGMPv1 Membership Report Messages -‐ Generated by the hosts -‐ When a host receives an IGMP query message it responds with a membership report. The membership report identifies the groups that a host has joined.
These two message types are part of a two-‐phase mechanism where, an IGMP version 1 host sends a report when it joins a multicast group. In order to configure a router to utilize IGMP version 1 protocol it is necessary to apply the ip igmp version 1 command at the interface level: interface FastEthernet0/0 ip address 172.16.100.2 255.255.255.0 ip igmp version 1
An IGMP version 1 router (known as a querier) queries periodically using query messages to dynamically identify active members of groups. Whenever a host receives a query message, it responds with membership report messages for all its associated multicast groups. The host sends an individual membership report for each multicast group it has joined to the querier. A host will wait a random
Copyright © by IPexpert, Inc. All Rights Reserved.
2-8
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
period between responses to queries (no more than 10 seconds) for each group it has joined. This delay affords the host time to receive a valid report sent by another device on the segment. If a host does not receive a report from another host on the same segment during the delay period, it will generate a membership report itself. If a host does receive a membership report from another host for one of its multicast group associations, it will suppress its own membership report for that group. This process prevents a "storm" of membership report messages. Observe this behavior in the output provided by the debug ip igmp command on R2: R2# IGMP(0): Received v1 Query on GigabitEthernet0/0 from 172.16.100.1 IGMP(0): Set report delay time to 0.2 seconds for 224.7.7.7 on GigabitEthernet0/0 IGMP(0): Send v1 Report for 224.7.7.7 on GigabitEthernet0/0
On R1 we can see the report for the group address 224.0.1.40 being canceled. R1# IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.5 for 224.0.1.40 IGMP(0): Received Group record for group 224.0.1.40, mode 2 from 172.16.100.5 for 0 sources IGMP(0): Cancel report for 224.0.1.40 on FastEthernet0/0
When the querier receives a membership report for a given group, it will start an EXCLUDE Group timer. The querier will remove group membership information not refreshed by a subsequent membership report sent in response to periodic general queries, within the configured EXCLUDE group timer. First, we see the EXCLUDE timer update in the output of the debug ip igmp command on R4 when the membership report arrives: R4# IGMP(0): Received v1 Report on FastEthernet0/0 from 172.16.100.2 for 224.7.7.7 IGMP(0): Received Group record for group 224.7.7.7, mode 2 from 172.16.100.2 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.7.7.7
This output clearly illustrates the process we have just described. The querier received the IGMP version 1 membership report from 172.16.100.2 for the group 224.7.7.7. The router in question has no knowledge of an active source, but it still resets the EXCLUDE group timer. At first blush, the IGMP version 1 protocol seems to accomplish all the goals we have discussed to date. However, this version IGMP does have one huge Achilles heel. Hosts have no special mechanism to allow them to leave a group. As stated earlier in the IGMP Technology Review, in IGMP version 1 a host that no longer needs to receive multicast packets for a particular group, simply stops replying to the IGMP query packets sent from the router.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-9
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
The router will continue sending queries and only stops sending queries on the network for the group after three consecutive query messages go unanswered. If a host on the segment wants to receive multicast packets after this timeout period, it simply sends a new IGMP join to the router, and the router will begin forwarding the packets once more. Some call this long period needed to identify the loss of an active multicast member "leave latency". IGMP Version 2 IGMP version 2 introduced a number of critical changes to IGMP. These modifications made IGMP more efficient by adding a new operational mechanism, and two additional message types. The new operational mechanism involves the election of the IGMP querier. In IGMP version 1 more than one device on a segment could and often does send IGMP version 1 queries as illustrated by the following debug ip igmp output on R2: R2#show logging | IGMP(0): Received IGMP(0): Received IGMP(0): Received
inc Received v1 Query v1 Query on GigabitEthernet0/0 from 172.16.100.5 v1 Query on GigabitEthernet0/0 from 172.16.100.4 v1 Query on GigabitEthernet0/0 from 172.16.100.1
This output demonstrates that R2 has received IGMP version 1 Query messages on GigabitEthernet0/0 from each of its neighbors on the VLAN 1245 segment. Recognizing that having more than one device on a segment constantly sending query messages was less than ideal; this behavior in IGMP version 2 was changed. Once we execute the ip igmp version 2 commands at the interface level on R1, R2, R4 and R5 the devices will now elect a single querier for the VLAN 1245 segment. The router with the lowest IP address on the segment becomes the querier. In the case of this topology, the process chooses R1. Verify this with show ip igmp interface on any device connected to VLAN 1245: R2#show ip igmp interface GigabitEthernet0/0 is up, line protocol is up Internet address is 172.16.100.2/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, 1 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 Multicast groups joined by this system (number of users):
Copyright © by IPexpert, Inc. All Rights Reserved.
2-10
IPv4/6 Multicast Operation and Troubleshooting
224.0.1.40(1)
Chapter 2: Internet Group Management Protocol (IGMP)
224.7.7.7(1)
This command provides a lot of output. The third line from the bottom identifies R1 as the IGMP querying router by its IP address 172.16.100.1. Note that the output notifies us that the current IGMP host version is 2, and that the current IGMP router version is 2. IGMP version 2 is backwards compatible with IGMP version 1. This is possible because IGMP version 2 still supports IGMP version 1 query and report messages. Where IGMP version 1 had 2 types of messages, IGMP version 2 has three: query messages, report messages and leave group messages. IGMP version 2 -‐ Query Messages An IGMP version 2 querier sends two types of query messages: • •
IGMPv2 General Query Messages -‐ Created by the querier -‐ Allows dynamic discovery of all multicast group members on a segment. IGMPv2 Group-‐Specific Query Messages -‐ Created by the querier -‐ Used to identify the existence of any members for a specific group.
Using the debug ip igmp command on R1 illustrates each message type: R1# IGMP(0): Send v2 general Query on FastEthernet0/1 IGMP(0): Received v2 Report on FastEthernet0/1 from 172.16.17.7 for 224.0.1.40 IGMP(0): Received Group record for group 224.0.1.40, mode 2 from 172.16.17.7 for 0 sources
We see that R1 has sent a IGMP version 2 general Query. Removing the group membership to 224.7.7.7 from the GigabitEthernet0/0 interface of R2 will force R1 to send a group-‐specific query: R2(config)#interface GigabitEthernet0/0 R2(config-if)#no ip igmp join-group 224.7.7.7
R1 should now send a group-‐specific query: R1# IGMP(0): Send v2 Query on FastEthernet0/0 for group 224.7.7.7 IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.5 for 224.0.1.40 IGMP(0): Received Group record for group 224.0.1.40, mode 2 from 172.16.100.5 for 0 sources
Note that R1 sent an IGMP version 2 query specifically for the group 224.7.7.7. IGMP version 2 -‐ Report Messages An IGMP version 2 host will send IGMP version 2 report messages under the following circumstances:
Copyright © by IPexpert, Inc. All Rights Reserved.
2-11
IPv4/6 Multicast Operation and Troubleshooting
• • •
Chapter 2: Internet Group Management Protocol (IGMP)
On joining a multicast group -‐ the host will immediately notify the elected querier that it has actively joined a multicast group. Upon receiving a General Query -‐ the host will send a report after a random delay in the same fashion employed in IGMP version 1 in response to a general query. Upon receiving a Group-‐Specific Query -‐ the host will send a report in response to a group-‐ specific query if it is a member of the group queried.
IGMP Version 2 -‐ Leave Messages An IGMP version 2 host will send a leave group message when it is no longer interested in a multicast group. Once this message reaches the elected querier a group-‐specific query is generated. As discussed in the section on IGMP version 2 query messages, the group-‐specific query determines if other members of a group exist. If a report message for a group-‐specific query arrives the IGMP version 2 router maintains the membership information for that specific group. In the case where no report messages arrive for a given group-‐specific query, the querier will discard the membership information. Typically, an IGMP version 2 router will transmit two queries with an interval of 1 second before discarding any information. Leave messages enable IGMP version 2 to find multicast groups without active members quickly. This alleviates the "leave latency" issues common in the older version of the protocol. In an effort to illustrate this process, R2 will remove its membership to the group 224.7.7.7 (debug ip igmp is running): R2(config)#interface GigabitEthernet0/0 R2(config-if)#no ip igmp join-group 224.7.7.7 R2(config-if)#end R2# IGMP(0): IGMP delete group 224.7.7.7 on GigabitEthernet0/0 IGMP(0): Received Group record for group 224.7.7.7, mode 3 from 172.16.100.2 for 0 sources IGMP(0): Send Leave for 224.7.7.7 on GigabitEthernet0/0 IGMP(0): Received v2 Query on GigabitEthernet0/0 from 172.16.100.1 IGMP(0): Lower expiration timer to 2000 msec for 224.7.7.7 on GigabitEthernet0/0
R2 deletes the group, sends the leave message, and adjusts the expiration timer for its 224.7.7.7 entry to 2 secs. This results in an efficient leave process and the IGMP version 2 router will stop forwarding the multicast packets for this group. IGMP Version 3 This enhancement to IGMP introduced the concept of Group-‐Source Report messages. As stated earlier in the IGMP Technology Review, these messages allow a host to elect to receive traffic from specific
Copyright © by IPexpert, Inc. All Rights Reserved.
2-12
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
sources of a multicast group; a concept referred to as Source Specific Multicast (SSM). Chapter 13: Multicast Security and Advanced Features will cover this topic in depth. IGMP and Multicast Forwarding IGMP is part of the last leg of multicast packet delivery. This is because IGMP is only concerned with forwarding multicast traffic from the local router to a group of members that share a common network. IGMP is a host-‐to-‐router communications protocol. For router-‐to-‐router delivery of multicast services, it is mandatory to define multicast routing protocols. These protocols are outside the scope of this chapter, but IGMP is an integral component to these protocols. The role of IGMP is to notify the querier/IGMP router, of the existence of devices that have joined multicast groups or group ranges. We have thoroughly examined the operational mechanisms for each version of IGMP in the previous sections of this chapter. Now we will look at the general operational process of IGMP as it relates to the overall multicast process: Step One -‐ The client/host sends an IGMP join message to a designated multicast router. The destination MAC address maps to the Class D address of the group being joined not to the MAC address of the router. The body of the IGMP datagram also includes the Class D group address. Step Two -‐ The IGMP router logs the join message and uses a multicast routing protocol (covered later in this document) to add this segment to the multicast distribution tree. Step Three -‐ IP multicast traffic is then transmitted from the server via the designated router. The designated router manages the distribution of multicast packets to the host's subnet. The destination MAC address that is used corresponds to the Class D address of the multicast group. Step Four -‐ The switch receives the multicast packet and examines its forwarding table. If no entry exists for the MAC address, the packet will be flooded to all ports within the broadcast domain. If an entry does exist in the switch table, only the designated ports will forward packets. Step Five -‐ With IGMP version 2, the client can end a group membership by sending an IGMP leave message to the router. With IGMP version 1, the client remains a member of the group until it fails to send a join message in response to a query from the router. Multicast routers also periodically send an IGMP query to the "all multicast hosts" group (224.0.0.1) or if using IGMP version 2, to a specific multicast group on the subnet to determine which groups are still active within the subnet. Each host delays its response to a query for a small random period and will only respond if no other hosts in the group have already responded. This mechanism prevents multiple hosts from congesting the network with simultaneous reports.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-13
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Common Issues with IGMP IGMP is a very simple protocol to troubleshoot. IGMP uses a simple operational mechanism to accomplish its duties forwarding multicast packets. Even though the overall process is simple, dividing it into specific phases makes troubleshooting more straightforward. To simplify troubleshooting common issues while deploying IGMP, we identify three categories of problems: Host Fails to Send IGMP joins, Switch Fails to Forward IGMP Packets, and IGMP Packet Filtering. Host Fails to Send IGMP joins In the Troubleshooting IGMP section, this text discussed the different versions of IGMP and what message types they utilize. The remainder of this chapter will deal specifically with IGMP version 2 because it is the default IGMP version employed by Cisco IOS. It is important to note that successful troubleshooting of IGMP depends on role-‐based operations within the protocol. A host failing to send a IGMP membership report is a common issue encountered while deploying IGMP. In effect, this means that a host is not notifying the IGMP router that it has joined a multicast group. Failure of a host to send IGMP joins would most probably be the result of a poorly written multicast application, or a configuration mistake in a testing scenario. Configuration mistakes may include but are not limited to; failure to apply an ip igmp join-‐group command or ip igmp static-‐group command under an interface. Additionally, the wrong multicast group applied to an interface prevents a host router from sending a membership report for the correct multicast group. Switch Fails To Forward IGMP Packets Thus far, we have addressed the fact that IGMP Multicast involves both a method of delivery and discovery of senders and receivers of multicast data. This information is transmitted via IP multicast addresses called groups. A multicast address that includes a group and source IP address is a channel or stream. The fact that the successful operation of multicast IGMP depends on the correct configuration of the upstream switch has not been addressed as of yet. By default, switches like the Catalyst 3560 utilize a concept called IGMP Snooping. IGMP snooping, scopes the flooding of multicast traffic by dynamically configuring Layer 2 interfaces so that multicast traffic is forwarded to only those interfaces associated with IP multicast devices. IGMP snooping requires the LAN switch to monitor IGMP transmissions between the host and the router and to keep track of multicast groups and member ports. When a switch receives an IGMP report from a host for a particular multicast group, the switch adds the host port number to its forwarding table entry; when it receives an IGMP Leave Group message from a
Copyright © by IPexpert, Inc. All Rights Reserved.
2-14
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
host, it removes the host port from the table entry. It also periodically deletes entries if it does not receive IGMP membership reports from any multicast clients. The most common issue that can cause problems where a switch does not forward IGMP messages are where IGMP Filtering and Throttling have been erroneously configured, or previous configurations have not been completely removed. •
•
IGMP Filtering -‐ filters multicast joins on a per-‐port basis by configuring IP multicast profiles and associating them with individual switch ports. IGMP filtering controls only group-‐specific query and membership reports, including join and leave reports and does not control general IGMP queries. IGMP filtering is applicable only to the dynamic learning of IP multicast group addresses, not static configuration. IGMP Throttling -‐ throttling sets the maximum number of IGMP groups that Layer 2 interfaces can join. Utilization of this technique can cause a switch to drop IGMP membership reports.
Apply IGMP Filtering using the ip igmp filter command. Apply IGMP Throttling using the ip igmp max-‐ groups command. Both are interface level commands. IGMP Packet Filtering IGMP Throttling and Filtering deal with IGMP packets at Layer 2 on a switch. There are versions of the same concepts designed to function at Layer 3. On routers, the ip igmp access-‐group and ip igmp limit commands accomplish these same goals: •
•
ip igmp access-‐group -‐ used to filter groups from IGMP membership reports by applying a standard access list. This command restricts hosts on a subnet to joining only multicast groups permitted by the configured standard IP access list. ip igmp limit -‐ used to configure a limit on the number of mroute states that are created as a result of IGMP membership reports (IGMP joins). Membership reports exceeding the configured limits do not enter the IGMP cache.
The most common issue that can cause problems where a router does not accept IGMP join messages are where IGMP Filtering or limiting have been erroneously configured, or previous configurations have not been completely removed. In the IGMP Sample Troubleshooting Scenarios section that follows, troubleshooting of these issues are demonstrated. For each problem, the text demonstrates how to quickly and efficiently verify each symptom, isolate the cause, and remediate the issue.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-15
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
IGMP Sample Troubleshooting Scenarios This section provides a detailed look at how to best approach troubleshooting some of the common issues discussed in previous sections. It includes coverage of a methodology for identification, isolation, and remediation of faults in the IGMP operational process. The intent here is to hone and develop troubleshooting skills tailored to first identify if a problem is IGMP related, and then how to begin isolating the cause of the fault in the most efficient manner possible. Figure 2-‐3 illustrates the topology used to explore this topic. Note that R1 is the IGMP Router (Querier), and R2, R4, and R5 are emulating hosts:
Figure 2-‐3: A Sample IGMP Topology
In the Common Issues with IGMP section, three primary types of problems were identified: Host Fails to Send IGMP joins; Switch Fails to Forward IGMP Packets, and IGMP Packet Filtering. This section explores these three categories of failure, by directing our attention to the commands necessary to identify that a problems exists. There are three types of devices in this topology: Hosts (R2, R4 and R5), FastEthernet Switch (CAT1), and an IGMP router (R1). Host Fails To Send IGMP Joins This situation is where a host does not send membership reports for a specific multicast group address. The best tool available in our troubleshooting arsenal to verify the existence of this type of problem is the debug ip igmp command: R2#debug ip igmp IGMP debugging is on R2# IGMP(0): Received v2 Query on GigabitEthernet0/0 from 172.16.100.1 IGMP(0): Set report delay time to 3.1 seconds for 224.0.1.40 on GigabitEthernet0/0 R2# IGMP(0): Received v2 Report on GigabitEthernet0/0 from 172.16.100.1 for 224.0.1.40
Copyright © by IPexpert, Inc. All Rights Reserved.
2-16
IPv4/6 Multicast Operation and Troubleshooting
IGMP(0): sources IGMP(0): IGMP(0): IGMP(0):
Chapter 2: Internet Group Management Protocol (IGMP)
Received Group record for group 224.0.1.40, mode 2 from 172.16.100.1 for 0 Cancel report for 224.0.1.40 on GigabitEthernet0/0 Updating EXCLUDE group timer for 224.0.1.40 MRT Add/Update GigabitEthernet0/0 for (*,224.0.1.40) by 0
R2 is receiving IGMP membership reports, but it is not sending any for 224.2.2.2. Based on Figure 2-‐3, R2's GigabitEthernet0/0 interface should have joined the group 224.2.2.2. The quickest and simplest way to determine what multicast groups a device has joined on an interface-‐by-‐interface basis is to execute the show ip igmp interface command: R2#show ip igmp interface GigabitEthernet0/0 is up, line protocol is up Internet address is 172.16.100.2/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: 9 joins, 7 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 Multicast groups joined by this system (number of users): 224.0.1.40(1)
This output indicates that R2 has only joined the multicast group 224.0.1.40 on GigabitEthernet0/0. There is no listing for 224.2.2.2. According to Figure 2-‐3, this address should appear here. To verify why, the next step would be to look for an ip igmp join-‐group command under GigabitEthernet0/0 for the group 224.2.2.2: R2#show run interface GigabitEthernet0/0 Building configuration... Current configuration : 116 bytes ! interface GigabitEthernet0/0 ip address 172.16.100.2 255.255.255.0 ip pim dense-mode duplex auto speed auto end
Copyright © by IPexpert, Inc. All Rights Reserved.
2-17
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
The join command is missing. Applying the ip igmp join-‐group 224.2.2.2 command on the GigabitEthernet0/0 interface of R2 will force R2 to begin sending IGMP version 2 membership reports on the VLAN 1245 segment for 224.2.2.2. R2(config)#interface GigabitEthernet0/0 R2(config-if)#ip igmp join-group 224.2.2.2 R2(config-if)#end %SYS-5-CONFIG_I: Configured from console by console R2#debug ip igmp IGMP debugging is on IGMP(0): Send v2 Report for 224.2.2.2 on GigabitEthernet0/0 IGMP(0): Received v2 Report on GigabitEthernet0/0 from 172.16.100.2 for 224.2.2.2 IGMP(0): Received Group record for group 224.2.2.2, mode 2 from 172.16.100.2 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.2.2.2 IGMP(0): MRT Add/Update GigabitEthernet0/0 for (*,224.2.2.2) by 0
This indicates that R2 has joined the group 224.2.2.2 as expected. Switch Fails To Forward IGMP Packets This situation occurs when a host transmits a membership report for a given multicast group, but the Layer 2 switch drops or fails to forward these packets to the IGMP router. The quickest method to detect this type of scenario is a three-‐step process. Step One: Is the host sending membership reports for the specific multicast group? In this scenario, we will look at R4 to determine if it is sending membership report messages for 224.4.4.4. This was accomplished with the debug ip igmp command on R4: R4#debug ip igmp IGMP debugging is on R4# IGMP(0): Send v2 Report for 224.4.4.4 on FastEthernet0/0 IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.4 for 224.4.4.4 IGMP(0): Received Group record for group 224.4.4.4, mode 2 from 172.16.100.4 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.4.4.4 IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.4.4.4) by 0
The IGMP membership reports are being transmitted for the group 224.4.4.4, based on the debug output. What device is acting as the querier on the VLAN 1245 segment? This can be determined with the show ip igmp interface command: R4#show ip igmp interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up Internet address is 172.16.100.4/24
Copyright © by IPexpert, Inc. All Rights Reserved.
2-18
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
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: 11 joins, 7 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 Multicast groups joined by this system (number of users): 224.4.4.4(1) 224.0.1.40(1)
The third line from the bottom of this show output indicates that the membership reports are being sent to R1 (172.16.100.1). Step 2: Are the IGMP version 2 membership reports making it to the querier? The answer to this question is best provided by the output of the show ip igmp groups command: R1#show ip igmp groups IGMP Connected Group Membership Group Address Interface Accounted 224.4.4.4 FastEthernet0/0 224.5.5.5 FastEthernet0/0 224.2.2.2 FastEthernet0/0 224.0.1.40 FastEthernet0/1 224.0.1.40 FastEthernet0/0
Uptime
Expires
Last Reporter
00:11:12 01:05:44 00:37:20 1d02h 1d02h
00:02:19 00:02:21 00:02:14 00:02:21 00:02:13
172.16.100.4 172.16.100.5 172.16.100.2 172.16.17.7 172.16.100.4
Group
The output indicates that R1 does indeed know about the multicast group 224.4.4.4, and it did indeed learn about the Group Address membership from the "Last Reporter" R4 (172.16.100.4). In a situation where the host is sending the membership report and the IGMP router is not receiving it, a logical assumption is that the switch is blocking it. Step Three: Is the switch blocking or limiting the IGMP traffic? The switch in this topology is CAT1. The easiest way to learn what multicast enabled IGMP devices are connected to the switch is by using the show ip igmp snooping mrouter command: CAT1#show ip igmp snooping mrouter Vlan ports
Copyright © by IPexpert, Inc. All Rights Reserved.
2-19
IPv4/6 Multicast Operation and Troubleshooting
---1245
Chapter 2: Internet Group Management Protocol (IGMP)
----Gi0/2(dynamic), Fa0/1(dynamic), Fa0/4(dynamic), Fa0/5(dynamic)
After identifying what ports are connected to IGMP enabled routers on the catalyst switch, the next step is to verify if there are any commands configured on the switch that will alter the forwarding of IGMP packets. The first thing to look for is if the ip igmp filter and/or ip igmp max-‐groups command(s) have been applied to any of these interfaces: CAT1#show run interface FastEthernet0/5 Building configuration... Current configuration : 150 bytes ! interface FastEthernet0/5 switchport access vlan 1245 switchport mode access spanning-tree portfast ip igmp max-groups 5 ip igmp filter 1 end
The output of this command on CAT1 for the interface connected to R5 illustrates examples of the commands we are looking for. In this particular instance, the configured commands are not effecting the current environment. IGMP Packet Filtering This situation occurs when a host transmits a membership report for a given multicast group, but the Layer 3 router drops or fails to forward these packets. The quickest method to isolate this type of problem is to look for Inbound IGMP access groups or Interface IGMP State Limits configured on the IGMP router via the show ip igmp interface command: R1#show ip igmp interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up Internet address is 172.16.100.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 1 IGMP activity: 14 joins, 10 leaves Interface IGMP State Limit : 4 active out of 10 max Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 (this system) Multicast groups joined by this system (number of users): 224.0.1.40(1)
Copyright © by IPexpert, Inc. All Rights Reserved.
2-20
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Note that the seventh line up from the bottom notifies us that the interface will support only 10 maximum IGMP groups. The ninth line up from the bottom identifies a standard access-‐list has been applied to the interface. In this environment, there are no issues on R1, but if there were; a closer examination of the access-‐list or the maximum IGMP state limit could isolate a fault.
IGMP Show Command Tools As a quick reference, here are the show command tools utilized in this chapter. This section utilizes the IGMP topology in Figure 2-‐4 for all example output.
Figure 2-‐4: A Sample IGMP Topology
show COMMAND: show ip igmp [vrf vrf-‐name] interface [interface-‐type interface-‐number] This command displays multicast-‐related information about an interface. Where: • •
vrf – optional; specifies the name of the multicast VRF instance Interface – used to filter the information based on the interface
EXAMPLE OUTPUT: R2#show ip igmp interface GigabitEthernet0/0 GigabitEthernet0/0 is up, line protocol is up Internet address is 172.16.100.2/24 IGMP is enabled on interface Current IGMP host version is 2 Current IGMP router version is 2
Copyright © by IPexpert, Inc. All Rights Reserved.
2-21
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
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: 11 joins, 7 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 Multicast groups joined by this system (number of users): 224.0.1.40(1) 224.2.2.2(1)
show COMMAND: show ip igmp [vrf vrf-‐name] groups [group-‐name | group-‐address | interface-‐type interface-‐number] [detail] This command displays the multicast groups with receivers directly connected to the router and learned through IGMP. Where: • • • • •
vrf – optional; Specifies the name of the multicast VRF instance group-‐name – optional; Name of the multicast group, as defined in the Domain Name System (DNS) hosts table. group-‐address – optional; Address of the multicast group. This is a multicast IP address in four-‐ part, dotted-‐decimal notation. interface-‐type interface-‐number – optional; Interface type and Interface number. detail – optional; Provides a detailed description of the sources known through IGMP Version 3 (IGMPv3), IGMPv3lite, or URL Rendezvous Directory (URD).
EXAMPLE OUTPUT: R1#show ip igmp groups IGMP Connected Group Membership Group Address Interface Accounted 224.4.4.4 FastEthernet0/0 224.5.5.5 FastEthernet0/0 224.2.2.2 FastEthernet0/0 224.0.1.40 FastEthernet0/1 224.0.1.40 FastEthernet0/0
Uptime
Expires
Last Reporter
Group
02:04:36 00:00:24 02:04:31 1d06h 1d06h
00:02:38 00:02:35 00:02:34 00:02:37 00:02:35
172.16.100.4 172.16.100.5 172.16.100.2 172.16.17.7 172.16.100.4
Ac Ac Ac Ac
Copyright © by IPexpert, Inc. All Rights Reserved.
2-22
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
show COMMAND: show ip igmp snooping [groups [count | vlan vlan-‐id [ip-‐address | count]] | mrouter [[vlan vlan-‐id] | [bd bd-‐id]] | querier | vlan vlan-‐id | bd bd-‐id] This command displays the IGMP snooping configuration of a device. Where: • • • • • • •
groups – optional; Displays group information. count – optional; Displays the number of multicast groups learned by IGMP snooping. vlan – optional; Specifies a VLAN. Valid values are 1 to 1001. If this keyword is not configured, information is displayed for all VLANs. bd – optional; Specifies a bridge domain. Valid values are 1 to 1001. If this keyword is not configured, information is displayed for all bridge domains. count – optional; Displays group count inside a VLAN. mrouter – optional; Displays information about dynamically learned and manually configured multicast router ports. querier – optional; Displays IGMP querier information.
EXAMPLE OUTPUT: CAT1#show ip igmp snooping mrouter Vlan ports -------1245 Gi0/2(dynamic), Fa0/1(dynamic), Fa0/4(dynamic), Fa0/5(dynamic)
Copyright © by IPexpert, Inc. All Rights Reserved.
2-23
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
IGMP Debug Command Tools As a quick reference, here are the debug command tools utilized in this chapter. This section utilizes the IGMP topology in Figure 2-‐5 for all example output.
Figure 2-‐5: A Sample IGMP Topology
debug COMMAND: debug ip igmp [vrf vrf-‐name] [group-‐address] This command displays IGMP packets received and sent, and IGMP-‐host related events. Where: • •
vrf – optional; Specifies the name of the multicast VRF instance group-‐address – optional; Address of a particular group about which to display IGMP information.
EXAMPLE OUTPUT: IGMP(0): IGMP(0): IGMP(0): IGMP(0): IGMP(0): sources IGMP(0): IGMP(0): IGMP(0):
Received v2 Query on FastEthernet0/0 from 172.16.100.1 Set report delay time to 1.5 seconds for 224.0.1.40 on FastEthernet0/0 Set report delay time to 8.4 seconds for 224.2.2.2 on FastEthernet0/0 Received v2 Report on FastEthernet0/0 from 172.16.100.4 for 224.0.1.40 Received Group record for group 224.0.1.40, mode 2 from 172.16.100.4 for 0 Cancel report for 224.0.1.40 on FastEthernet0/0 Updating EXCLUDE group timer for 224.0.1.40 MRT Add/Update FastEthernet0/0 for (*,224.0.1.40) by 0
Copyright © by IPexpert, Inc. All Rights Reserved.
2-24
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
debug COMMAND: debug ip igmp snooping {group | management | router | timer} This command displays the mappings for the PIM group to the active Rendezvous Point(s). Where: • • • •
group – displays debugging messages related to multicast groups management – displays debugging messages related to management services router – displays debugging messages related to the local routers timer – displays debugging messages related to the IGMP timer
EXAMPLE OUTPUT: CAT1#debug ip igmp snooping router IGMPSN: router: Received IGMP pak on Vlan 1245, port Fa0/1 IGMPSN: router: Is a router port on Vlan 1245, port Fa0/1 IGMPSN: router: Learning port: Fa0/1 as rport on Vlan 1245
Copyright © by IPexpert, Inc. All Rights Reserved.
2-25
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Chapter Challenge: IGMP Sample Trouble Tickets The following section includes three sample Trouble Tickets designed to challenge the troubleshooting skills that have been developed in all previous sections of this chapter. These Trouble Tickets were designed using the Routing & Switching rental racks at www.ProctorLabs.com with the initial configurations provided in the file MCAST-‐CH2-‐IGMP-‐TT-‐INITIAL.txt. Keep in mind these sample Trouble Tickets were also tested against home practice racks and the most popular router emulators. The network topology used in this section is shown in Figure 2-‐6 below:
Figure 2-‐6: The Chapter Challenge Topology
Trouble Ticket #1 Your supervisor has brought to your attention that R2 is not generating IGMP version 2 membership reports for the multicast group 224.2.2.2. Correct this issue. Trouble Ticket #2 After solving Trouble Ticket #1, your supervisor has observed that membership reports generated by R4 for the multicast group 224.4.4.4 are not making it to the IGMP router. Correct this issue. Trouble Ticket #3 Your supervisor has notified you that membership reports generated by R2 for the multicast group 224.2.2.2 are not making it into the IGMP Groups table on R1. Correct this issue without the removal of existing configurations.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-26
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Chapter Challenge: IGMP Sample Trouble Tickets Solutions The following section includes the solutions to the three Trouble Tickets presented in the previous section. Figure 2-‐7 provides a flowchart that outlines a "quick fire" approach to isolating and remediating issues associated with IGMP.
Figure 2-‐7: IGMP Quick Fire Troubleshooting Flowchart
Trouble Ticket #1 Solution Your supervisor has brought to your attention that R2 is not generating IGMP version 2 membership reports for the multicast group 224.2.2.2. Correct this issue. Step 1 -‐ Fault Verification: Is R2 generating IGMP version 2 membership reports? R2#debug ip igmp IGMP debugging is on R2# IGMP(0): Received v2 Query on GigabitEthernet0/0 from 172.16.100.1 IGMP(0): Set report delay time to 3.8 seconds for 224.0.1.40 on GigabitEthernet0/0
Copyright © by IPexpert, Inc. All Rights Reserved.
2-27
IPv4/6 Multicast Operation and Troubleshooting
R2# IGMP(0): IGMP(0): sources IGMP(0): IGMP(0): IGMP(0):
Chapter 2: Internet Group Management Protocol (IGMP)
Received v2 Report on GigabitEthernet0/0 from 172.16.100.4 for 224.0.1.40 Received Group record for group 224.0.1.40, mode 2 from 172.16.100.4 for 0 Cancel report for 224.0.1.40 on GigabitEthernet0/0 Updating EXCLUDE group timer for 224.0.1.40 MRT Add/Update GigabitEthernet0/0 for (*,224.0.1.40) by 0
R2 is receiving reports and queries but is not sending reports for 224.2.2.2. This verifies that the problem actually exists. Step 2 -‐ Fault Isolation: The next course of action is to use the show ip igmp interface command on R2. R2#show ip igmp interface GigabitEthernet0/0 is up, line protocol is up Internet address is 172.16.100.2/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: 11 joins, 9 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 Multicast groups joined by this system (number of users): 224.0.1.40(1)
The last line of the output does not list 224.2.2.2 as a group that R2 has joined. This is most likely a missing or erroneous configuration of the ip igmp join-‐group command under the GigabitEthernet0/0 interface. This is verified with the show run interface command on R2: R2#show run interface GigabitEthernet0/0 Building configuration... Current configuration : 116 bytes ! interface GigabitEthernet0/0 ip address 172.16.100.2 255.255.255.0 ip pim dense-mode
Copyright © by IPexpert, Inc. All Rights Reserved.
2-28
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
duplex auto speed auto end
This isolates the fault. Step 3 -‐ Fault Remediation: In this scenario, the ip igmp join-‐group 224.2.2.2 command needs to be applied to the GigabitEthernet0/0 interface of R2. R2(config)#interface GigabitEthernet0/0 R2(config-if)#ip igmp join-group 224.2.2.2 R2(config-if)#end
Step 4 -‐ Verification of Remediation Once the error has been isolated and remediated it is highly recommended to verify that the Trouble Ticket has been repaired using the same method used to verify the fault initially. R2#debug ip igmp IGMP debugging is on R2# IGMP(0): Send v2 Report for 224.2.2.2 on GigabitEthernet0/0 IGMP(0): Received v2 Report on GigabitEthernet0/0 from 172.16.100.2 for 224.2.2.2 IGMP(0): Received Group record for group 224.2.2.2, mode 2 from 172.16.100.2 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.2.2.2 IGMP(0): MRT Add/Update GigabitEthernet0/0 for (*,224.2.2.2) by 0
R2 is now sending membership reports for the group 224.2.2.2. The solution has successfully remediated the problem. Trouble Ticket #2 Solution After solving Trouble Ticket #1, your supervisor has observed that membership reports generated by R4 for the multicast group 224.4.4.4 are not making it to the IGMP router. Correct this issue. Step 1 -‐ Fault Verification: Does R1 have a record of the IGMP joins for the group 224.4.4.4? R1#show ip igmp groups IGMP Connected Group Membership Group Address Interface Accounted 224.5.5.5 FastEthernet0/0 224.0.1.40 FastEthernet0/1
Copyright © by IPexpert, Inc. All Rights Reserved.
Uptime
Expires
Last Reporter
Group
00:47:43 1d06h
00:02:37 00:02:16
172.16.100.5 172.16.17.7
Ac
2-29
IPv4/6 Multicast Operation and Troubleshooting
224.0.1.40
FastEthernet0/0
Chapter 2: Internet Group Management Protocol (IGMP)
1d06h
00:02:30
172.16.100.2
Ac
R1 has no record of the group 224.4.4.4. Thus proving the problem exists. Step 2 -‐ Fault Isolation: Now, the first step is to determine if R1 even receives the membership reports from R4 at all. R1#debug ip igmp IGMP debugging is on R1# IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.2 for 224.2.2.2 IGMP(*): Group 224.2.2.2 access denied on FastEthernet0/0 IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.5 for 224.5.5.5 IGMP(0): Received Group record for group 224.5.5.5, mode 2 from 172.16.100.5 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.5.5.5 IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.5.5.5) by 0
R1 receives membership reports for the groups 224.2.2.2 and 224.5.5.5 but not 224.4.4.4. This means that the next step of the verification needs to be on CAT1. Use the debug ip igmp filter command on CAT1 to identify any interfaces that may have profiles filtering specific multicast groups: CAT1#debug ip igmp filter event debugging is on CAT1# IGMPFILTER: igmp_filter_process_pkt() checking group from Gi0/2 : no profile attached CAT1# IGMPFILTER: igmp_filter_process_pkt(): checking group 224.4.4.4 from Fa0/4: deny
CAT1 has an igmp-‐filter applied on interface FastEthernet0/4 that denies the multicast group 224.4.4.4. The actual parameters of the profile can be seen via the show ip igmp profile command: CAT1#show ip igmp profile IGMP Profile 1 range 224.4.4.4 224.4.4.4
This has isolated our fault. Step 3 -‐ Fault Remediation: In this scenario, the ip igmp filter 1 command needs to be removed from the FastEthernet0/4 interface of CAT1: CAT1(config)#interface FastEthernet0/4 CAT1(config-if)#no ip igmp filter 1
Copyright © by IPexpert, Inc. All Rights Reserved.
2-30
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Step 4 -‐ Verification of Remediation Once the error has been isolated and remediated, it is highly recommended to verify that the Trouble Ticket has been repaired using the same method used to verify the fault initially: R1#show ip igmp groups IGMP Connected Group Membership Group Address Interface Accounted 224.4.4.4 FastEthernet0/0 224.5.5.5 FastEthernet0/0 224.0.1.40 FastEthernet0/1 224.0.1.40 FastEthernet0/0
Uptime
Expires
Last Reporter
Group
00:00:28 01:06:49 1d07h 1d07h
00:02:31 00:02:24 00:02:17 00:02:22
172.16.100.4 172.16.100.5 172.16.17.7 172.16.100.1
Ac Ac Ac
R1, the IGMP router, now sees the group 224.4.4.4. Thus verifying that the error has been corrected. Trouble Ticket #3 Solution Your supervisor has notified you that membership reports generated by R2 for the multicast group 224.2.2.2 are not making it into the IGMP Groups table on R1. Correct this issue without the removal of existing configurations. Step 1 -‐ Fault Verification: Are membership reports from R2 for the group 224.2.2.2 making it to R1? R1#debug ip igmp IGMP debugging is on R1# IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.2 for 224.2.2.2 IGMP(*): Group 224.2.2.2 access denied on FastEthernet0/0 R1#
R1 is receiving the membership reports from R2 but they are being actively denied on FastEthernet0/0, thus verifying the validity of the trouble ticket. Step 2 -‐ Fault Isolation: To determine why the IGMP packets for the group 224.2.2.2 are being dropped use the show ip igmp interface command. R1#show ip igmp interface FastEthernet0/0 FastEthernet0/0 is up, line protocol is up Internet address is 172.16.100.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
Copyright © by IPexpert, Inc. All Rights Reserved.
2-31
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
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 1 IGMP activity: 16 joins, 13 leaves Interface IGMP State Limit : 3 active out of 10 max Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 172.16.100.5 IGMP querying router is 172.16.100.1 (this system) Multicast groups joined by this system (number of users): 224.0.1.40(1)
We see that we have a IGMP State limit of 10 maximum groups, but we only have 3 active. This rules the max-‐groups setting out as a cause. However, we also notice that there is an access-‐group applied to the interface. This access-‐group references the standard numbered access-‐list 1. At this point, the contents of that access-‐list are significant and can be viewed with the show ip access-‐list 1 command: R1#show ip access-list 1 Standard IP access list 1 10 deny 224.2.2.2 (39 matches) 20 permit any (139 matches)
Looking at this output, we see that the multicast group 224.2.2.2 is being denied by access-‐list 1. Additionally, the output tells us that IGMP report messages are arriving on R1, but we have denied 39 of them. This is the problem with the configuration. Step 3 -‐ Fault Remediation: In this scenario, access-‐list 1 should be edited such that line 10 is removed. R1(config)#ip access-list standard 1 R1(config-std-nacl)#no 10 R1(config-std-nacl)#exit
To verify that the editing worked we use the show ip access-‐list command: R1(config)#do show ip access-list 1 Standard IP access list 1 20 permit any (151 matches) R1(config)#
Step 4 -‐ Verification of Remediation
Copyright © by IPexpert, Inc. All Rights Reserved.
2-32
IPv4/6 Multicast Operation and Troubleshooting
Chapter 2: Internet Group Management Protocol (IGMP)
Once the error has been isolated and remediated, it is highly recommended to verify that the Trouble Ticket has been repaired using the same method used to verify the fault initially. R1#debug ip igmp IGMP debugging is on R1# IGMP(0): Send v2 general Query on FastEthernet0/0 IGMP(0): Set report delay time to 1.1 seconds for 224.0.1.40 on FastEthernet0/0 R1# IGMP(0): Received v2 Report on FastEthernet0/0 from 172.16.100.2 for 224.2.2.2 IGMP(0): Received Group record for group 224.2.2.2, mode 2 from 172.16.100.2 for 0 sources IGMP(0): Updating EXCLUDE group timer for 224.2.2.2 IGMP(0): MRT Add/Update FastEthernet0/0 for (*,224.2.2.2) by 0
R1 is no longer denying the membership report from R2 for the group 224.2.2.2. As a final verification this group should now appear in the output of the show ip igmp groups command: R1#show ip igmp groups IGMP Connected Group Membership Group Address Interface Accounted 224.4.4.4 FastEthernet0/0 224.5.5.5 FastEthernet0/0 224.2.2.2 FastEthernet0/0 224.0.1.40 FastEthernet0/1 224.0.1.40 FastEthernet0/0
Uptime
Expires
Last Reporter
Group
00:22:48 01:29:10 00:03:54 1d07h 1d07h
00:02:09 00:02:04 00:02:05 00:02:50 00:02:01
172.16.100.4 172.16.100.5 172.16.100.2 172.16.17.7 172.16.100.5
Ac Ac Ac Ac
R1 now has 224.2.2.2 in the list of active IGMP groups. Thus verifying that the issue has been corrected.
Copyright © by IPexpert, Inc. All Rights Reserved.
2-33
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: Protocol Independent Multicast - Dense Mode (PIM-DM)
Chapter 3: Protocol Independent Multicast -‐ Dense Mode (PIM-‐DM) This chapter of IPv4/6 Multicast Operation and Troubleshooting examines the processes and the functionality of the PIM dense-‐mode (PIM-‐DM) protocol in great depth. Once the operational characteristics of this important protocol are detailed completely, the focus becomes that of troubleshooting. This includes the careful examination of symptoms, a fault isolation methodology, and the implementation of repairs for the PIM dense-‐mode (PIM-‐DM) protocol. The chapter begins with a thorough review of PIM-‐DM, and then quickly launches into an exhaustive analysis of the “art” of troubleshooting this multicast routing protocol. This important chapter concludes with sample troubleshooting scenarios, reference materials for the most important show and debug commands, and exciting challenges that allow readers to practice implementing the troubleshooting skills they have obtained.
Copyright © by IPexpert, Inc. All Rights Reserved.
3-1
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
PIM-‐DM Technology Review Chapter 2: Internet Group Management Protocol (IGMP) discussed the important control protocol of IGMP in great length. We learned the nature of IGMP's role in multicast routing was to fulfill the last leg of the multicast routing process. IGMP reports the existence of hosts that have joined multicast groups to the underlying multicast routing protocol. Several types and varieties of multicast protocols exist, but the most common protocol used in Cisco networks today is Protocol Independent Multicast (PIM). Where IGMP is the protocol used to exchange information between hosts and routers, PIM is used between routers to build the multicast tree from the sender down to the interested hosts. PIM is protocol independent because no topology information is exchanged while the multicast tree is created. Instead, PIM relies on the underlying interior gateway protocol running in the network. This means that the multicast tree is built with no concern for the existence of loops in the topology. There is however, a convention built into the multicast forwarding and routing logic that works in unison with the routing protocol to prevent multicast loops. This convention, Reverse Path Forwarding (RPF), ensures that all multicast packets that arrive on an interface that are not used to reach the source of the packets are dropped. RPF will be covered in detail later in this chapter, but first it will be necessary to discuss the two current versions of PIM that can be deployed in a network. Just like IGMP; PIM has evolved over the years. By default, current versions of the IOS will run PIM version 2. In order to better, understand the nature of the enhancements made to the protocol in its current version a close examination of PIM version 1 is in order. PIMv1 PIM version 1 is a Cisco propriety protocol that can dynamically map RP's to multicast groups in concert with a standalone protocol called Auto-‐RP. PIM version 1 uses a time-‐to-‐live value to scope its announcements. PIM version 1 packets are transmitted inside IGMP packets. PIM routers that create the multicast tree use these PIM laden IGMP packets. IGMP packets containing PIM packets are designated as Type 5 IGMP messages, or "Router PIM Messages". PIMv2 PIM version 2 is a standards-‐based track protocol that made several improvements on the earlier Cisco proprietary version. These improvements include the concept of a single active RP per multicast group with multiple alternate RP's. PIM version 1 supported multiple active RPs for the same group. In version 2, PIM packets are stand-‐alone packets and no longer embedded in IGMP messages. These new PIM version 2 packets have support for automated fault tolerant RP discovery and distribution called a Bootstrap router (BSR). This means that PIMv2 does not need any standalone protocols like Auto-‐RP does to allow routers to dynamically learn group-‐to-‐RP mappings. Additional modifications to the PIM version 1 protocol also include more flexible encoding of future capability options inside PIM join and
Copyright © by IPexpert, Inc. All Rights Reserved.
3-2
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
prune messages, as well as a robust and flexible Hello Packet format that replaces the old Query packet operation adopted from IGMP. To better understand the operation of multicast in IP networks, it is best to separate the construction of the PIM control plane from the actual forwarding of multicast data (the data plane). Once the control plane protocols have actually constructed the multicast tree the actual forwarding of multicast packets will take place in the data plane. The data plane uses Reverse Path Forwarding (RPF) to ensure traffic is not forwarded in a fashion that results in a loop of the multicast stream. We mentioned briefly the fact that the multicast tree is built with no concern for loops in the tree. In fact, it is worth mentioning that commonly there will be valid deployments where the tree is built as a looped topology. Realizing this fact, PIM was created to use RPF at all times for all multicast traffic. Specifically, the reverse path forwarding check is going to ensure that multicast packets will only be forwarded when they arrive on interfaces that are designated as being loop-‐free unicast paths back to the source of the multicast stream. The main goal of the reverse path forwarding check is every time a device receives a multicast packet on an interface the router will perform a lookup based on the source IP address. This lookup recurses to the interface used by the underlying routing protocol to reach the source of the packet. This interface will be compared to the interface the packet actually arrived on. If the interfaces match then the RPF check passes. If the interfaces do not match then the RPF check fails and the packet is dropped. It is important to understand that these RPF checks are a data plane protection process, separate and apart from the control plane and they are performed against each and every multicast packet a device receives. So in the event of a loop in the IGP topology or if PIM was not able to create a loop-‐free tree, it is assured that multicast packets will not loop as they are forwarded. Essentially guaranteeing that even if a looped tree is built the data plane will determine which interfaces should or should not be used in forwarding. All this is based on the underlying unicast routing table. The majority of problems encountered when deploying or troubleshooting PIM will actually result in some part of the physical network design failing the RPF check mechanism. This means that most multicast issues are going to be related to RPF check failures that will need to be remediated either by changing the underlying unicast routing, implementing static multicast routes, deploying tunnels or by using multicast BGP. The last stage of data plane forwarding is going to be the creation of the multicast routing table for a particular device. PIM neighbors exchange messages, specifically join and prune messages that are used to create the multicast tree, these messages are also used in the creation of the multicast routing table. The role of the multicast routing table is to keep track of what interfaces point to multicast sources, and what interfaces lead to multicast receivers. This table can at first seem confusing and difficult to
Copyright © by IPexpert, Inc. All Rights Reserved.
3-3
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
interpret, but a short amount of time looking at how the information is organize will reveal just how powerful this table is when trying to troubleshoot any multicast routing problem. Two classifications of information found in the multicast routing table correspond to the interface classification mentioned previously. Interfaces that point toward the source of a multicast feed (upstream facing) are classified as incoming interfaces. These interfaces are placed in the section of the multicast routing table called the "incoming interface list". The remaining links (downstream facing) lead toward any possible multicast receivers. These interfaces compose what is called the Outgoing Interface List or "OIL". At this point it is important to note that there is a "split-‐horizon-‐like" behavior that multicast follows. This behavior prevents an interface from being able to be classified as both incoming and outgoing for a given multicast group simultaneously. This behavior can be disabled in some categories of PIM, but not in others. For troubleshooting purposes, it is important to remember this behavior as it can cause significant issues in network designs that have multipoint non-‐broadcast interfaces like some deployments of frame relay. It should also be noted that this behavior could also result in some network designs that make it impossible to deploy some modes of PIM. As a rule, it is best to run multicast over a Layer 2 technology such as frame-‐relay using point-‐to-‐point PIM enabled links everywhere. Once the multicast tree has been created using the associated PIM join and prune messages, and assuming the RPF checks pass, multicast routes (mroutes) will begin to populate the multicast routing table. These routes utilize an annotation scheme unique to multicast. This annotation format follows the model of (S,G) where "S" is the source and "G" is the group. This means that the router knows the identity of the source for a specific group as opposed to the (*,G) entry. The *,G entry means that the device knows the group but not the identity of the source. The (S,G) is often referred to as the "Source Tree", where the (*,G) is known as the "Shared Tree". Multicast routing has one other thing in common with unicast routing. The most specific route or "longest match" will always be preferred. This means that a *,G entry will always be less specific than a S,G entry in the multicast routing table. This being the case, once a multicast packet arrives on an interface the router will switch the packet from the incoming interface, to all interfaces in the OIL. The mechanism being described here is one where a "single" packet arrives on an interface, and a layer three replication of that single packet takes place and it is forwarded out all the interfaces in the OIL. PIM Dense Mode We have discussed the basic operation of PIM. The next step in this critical analysis of the protocol is to look at different modes of PIM operation. There are three modes to this essential multicast routing protocol: dense-‐mode (PIM-‐DM), sparse-‐mode (PIM-‐SM), and sparse-‐dense-‐mode (PIM-‐SM-‐DM).
Copyright © by IPexpert, Inc. All Rights Reserved.
3-4
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
The mode that this chapter will explore is PIM-‐DM. The remaining operational modes each will have their own dedicated chapters. It was decided to start with PIM-‐DM because the protocol is the simplest of the three, and affords a very streamline technology to introduce the basic and advanced verification commands, tools and processes associated with troubleshooting all of the PIM mode types. Figure 3-‐1 demonstrates a sample PIM-‐DM topology.
Figure 3-‐1: A Sample PIM-‐DM Topology
In this chapter, we are going to look critically at the specifics of PIM-‐DM to include the different verification techniques used to validate its operation, as well as the commands used to isolate faults in the protocol. PIM-‐DM operates via an implicit join paradigm. This implicit join model is often called a "push model" because the routers are going to flood all multicast traffic they receive out every single interface running PIM-‐DM (except the interface the packet arrived on). This means that the individual adjacent routers are responsible for deciding if they are interested in the multicast feed or not. If the router has no interest in the multicast feed, it will send a PIM Prune message. This message is the equivalent of an un-‐join instruction sent out the originating link. This "flood and prune" behavior makes PIM-‐DM operation unwieldy due to the sheer volume of state information it must maintain. The larger the network the more state information that needs to be maintained, therefore PIM-‐DM's biggest detractor is its lack of scalability.
The Operation and Troubleshooting of PIM-‐DM To better understand the process used by PIM-‐DM to create the multicast tree the protocols operation will be divided into four individual steps.
Copyright © by IPexpert, Inc. All Rights Reserved.
3-5
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
Step One: Application of PIM-‐DM on one router A PIM-‐DM router is first going to attempt to identify all the PIM-‐DM enabled neighbors on its individual links. In an effort to find these PIM enabled neighbors PIM-‐DM will use the reserved link-‐local multicast address 224.0.0.13. As a result of this methodology it is essential to ensure that any Layer 2 protocols, like frame-‐relay, are configured to support multicast transport when it comes to the neighbor discovery process or multicast forwarding. This is accomplished by ensuring that these links are configured to support pseudo-‐broadcast. The application of the "broadcast" command allows a link to support broadcast addresses like 255.255.255.255, but by extension, the command also supports multicast packets. A closer look at the operation of PIM-‐DM can be accomplished by using the debug ip packet detail command. Using this command before actually configuring multicast routing will afford valuable insight into the processes that take place on the router. Using the topology in Figure 3-‐2, we will demonstrate this in detail.
Figure 3-‐2: PIM-‐DM Topology
Looking at the output of debug ip packet on any of these devices after we apply the ip multicast-‐routing and the ip pim dense-‐mode commands we will see the underlying process take place on the console. In order to filter out traffic associated with our internal routing protocol we will apply an ACL to the debug ip packet command that will prevent EIGRP's locally process switched traffic from cluttering the console messages. Also, note that like other chapters in this text we have disabled the service timestamps feature, again in an effort to reduce any possible confusion regarding the interpretation of the debug output. R1(config)#access-list 101 deny eigrp any any R1(config)#access-list 101 permit ip any any
Copyright © by IPexpert, Inc. All Rights Reserved.
3-6
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
R1(config)#end R1# R1#debug ip packet detail 101 IP packet debugging is on (detailed) for access list 101
With this accomplished our next task is to enable ip multicast-‐routing and apply the ip pim dense-‐mode command under the FastEthernet0/0 interface of R1. Once completed, we will observe the output of the debug ip packet command: R1#conf t Enter configuration commands, one per line. R1(config)#ip multicast-routing R1(config)#interface FastEthernet0/0 R1(config-if)#ip pim dense-mode R1(config-if)#end
End with CNTL/Z.
Almost immediately, debug output begins to appear on the console of R1. It is this output we need to interpret in order to understand the process that is taking place. Specifically, we need to look at these three samples of output. Notice that each represents an instance where R1 is sending a broadcast/multicast packet, but there are two different protocol types, and three different destination addresses used. IP: s=172.16.15.1 (local), d=224.0.0.13 (FastEthernet0/0), len 54, sending broad/multicast, proto=103 IP: s=172.16.15.1 (local), d=224.0.0.1 (FastEthernet0/0), len 28, sending broad/multicast, proto=2 IP: s=172.16.15.1 (local), d=224.0.1.40 (FastEthernet0/0), len 28, sending broad/multicast, proto=2
First, we will look at the protocol types. In the sample output above, we see protocols 103 and 2. What are these protocol types? It is simple enough to find out by creating an extended access-‐list using the IP protocol number. The default behavior of Cisco IOS is to translate these protocol numbers into a human readable form. Taking advantage of this feature is a handy tool to identify the protocol types without needing external resources or materials. R1(config)#access-list 100 permit 103 any any R1(config)#access-list 100 permit 2 any any R1(config)#end %SYS-5-CONFIG_I: Configured from console by console R1#show ip access-list 100 Extended IP access list 100 10 permit pim any any 20 permit igmp any any
Copyright © by IPexpert, Inc. All Rights Reserved.
3-7
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
The output of the show ip access-‐list 100 command reveals that the protocol types in question are PIM (type 103) and IGMP (type 2) messages respectively. Now that we know, what type of messages R1 is sending the next logical step is to look at where the messages are going. The type 103 or PIM messages are being sent to the link-‐local multicast group 224.0.0.13. The type 2 messages are actually being sent to two different destination groups. The first group is 224.0.0.1, a link-‐local multicast group employed by all multicast hosts. This means that by virtue of enabling PIM on the interface R1 is now sending IGMP query messages to all hosts on the VLAN 15 segment. However, it is also observed that R1 is sending type two protocol messages to a new multicast destination address that has not been discussed as of yet; the multicast group 224.0.1.40. This address is used in the process of Auto-‐RP that was discussed briefly in Chapter 2: Internet Group Management Protocol (IGMP). Auto-‐RP will be discussed in detail in Chapter 8: AutoRP. At this point, it is enough to know that the group 224.0.1.40 is the multicast group that the Auto-‐RP mapping agent will use to disseminate Auto-‐RP information, but the important thing to note is that as soon as the multicast routing process is enabled, the router will automatically join the group 224.0.1.40. Regardless of what PIM mode we are running, the router will attempt to dynamically learn the identity of a rendezvous point (RP). PIM-‐DM does not utilize an RP as part of the multicast routing process but none-‐the-‐less the router will join the group. This behavior affords us an ideal opportunity to look at the multicast routing table while it has only one entry. R1#show 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, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group 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:42:27/00:01:54, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: FastEthernet0/0, Forward/Dense, 00:42:27/00:00:00
Observe the (*, 224.0.1.40) entry. This entry is referred to as a "star comma gee", and fits the annotation model of (*,G). This means that the router has joined this multicast group, but there are no
Copyright © by IPexpert, Inc. All Rights Reserved.
3-8
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
known sources for it at this time. How can we actually tell the router has joined this group? Remember the behavior of IGMP. An IGMP host records all the groups it has joined in an IGMP membership list. The contents of this list can be viewed with the show ip igmp membership command. R1#show ip igmp membership Flags: A - aggregate, T - tracked L - Local, S - static, V - virtual, R - Reported through v3 I - v3lite, U - Urd, M - SSM (S,G) channel 1,2,3 - The version of IGMP the group is in Channel/Group-Flags: / - Filtering entry (Exclude mode (S,G), Include mode (*,G)) Reporter:
- last reporter if group is not explicitly tracked / - reporter in include mode, reporter in exclude Channel/Group *,224.0.1.40
Reporter 172.16.15.1
Uptime Exp. Flags 00:48:30 02:59 2LA
Interface Fa0/0
The output verifies that R1 has actually joined the multicast group 224.0.1.40 on Interface FastEthernet0/0. These two show commands show ip mroute and show ip igmp membership, demonstrate that we have IP multicast-‐routing enabled globally, and at the interface level we are running PIM-‐DM. Also based on the output we have observed we know that R1 is sending PIM messages to 224.0.0.13 with a protocol number of 103, and IGMP messages related to the group 224.0.1.40. In fact, R1 has actually become an IGMP client for the Auto-‐RP mapping agent group. Step Two: PIM-‐DM on the remaining routers Now that we have observed the behavior of PIM-‐DM critically on one device and have an understanding of how it operates it is time to enable ip multicast-‐routing and PIM-‐DM on every router interface with an ip address in the topology. At this point in our critical analysis, we will enable PIM-‐DM on all interfaces in an effort to prevent any failures in the reverse path forwarding mechanism. Once this is accomplished, it is very simple to identify and map the multicast routing topology based on the output of a single show command: show ip pim neighbors. Using this command on all the routers in this topology will quickly allow us to construct a logical drawing of the multicast routing topology. Beginning on R1: R1#show ip pim nei PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, S - State Refresh Capable
Copyright © by IPexpert, Inc. All Rights Reserved.
3-9
IPv4/6 Multicast Operation and Troubleshooting
Neighbor Address 172.16.15.5
Chapter 3: PIM - Dense Mode (PIM-DM)
Interface
Uptime/Expires
Ver
FastEthernet0/0
00:07:26/00:01:41 v2
DR Prio/Mode 1 / DR S
We see that R1 has formed a PIM neighbor relationship with R5. The same command on R5 informs us that R5 is neighbored with R1 and R4: R5#show ip pim neighbor PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default S - State Refresh Capable Neighbor Interface Uptime/Expires Address 172.16.15.1 FastEthernet0/0 00:08:28/00:01:38 172.16.45.4 FastEthernet0/1 00:08:47/00:01:18
DR Priority, Ver v2 v2
DR Prio/Mode 1 / S 1 / S
Consistently repeating this command on all the routers in the topology will produce a topology drawing matching Figure 3-‐3.
Figure 3-‐3: PIM neighbor relationships
Note: When using the show ip pim neighbor command be sure to check for adjacencies on both ends of a link. There are scenarios where the PIM neighbor can show up on one side and not the other. Now that we see the topology, there are issues that need discussion. Observe that the PIM neighbor relationships between R4, R2 and R6 form a distinct loop. At first glance, this will seem extremely odd, but remember the control plane is formed with no thought toward possible loops. This is where the RFP check mechanism will come into play. Later in this section, this entire process will be laid out and dissected step-‐by-‐step, but for now it is time to move to the next stage of the process. Step Three: A host joins a multicast group
Copyright © by IPexpert, Inc. All Rights Reserved.
3-10
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
We have reviewed the nature and purpose of the PIM and IGMP messages that sent between PIM-‐DM enabled devices, now it is time to look at the IGMP join process. In Chapter 2: Internet Group Management Protocol (IGMP) we saw the inner workings of this protocol and we know that to force a router to join a multicast group we can employ a number of commands at the interface level. In this explanation, the FastEthernet0/1 interface of R9 will use the ip igmp join-‐group command to join the multicast group 224.9.9.9. R9(config)#interface FastEthernet0/1 R9(config-if)#ip igmp join-group 224.9.9.9 R9(config-if)#end
Once this is accomplished, the show ip mroute or show ip igmp membership commands will tell us if the router's interface has indeed joined the group 224.9.9.9. In order to develop more familiarity with the show ip mroute command, we use it below. R9#show 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, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing interface flags: H - Hardware switched, A - Assert winner Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 224.9.9.9), 00:42:21/00:02:33, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: FastEthernet0/1, Forward/Dense, 00:42:21/00:00:00 (*, 224.0.1.40), 00:42:22/00:02:38, RP 0.0.0.0, flags: DCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: FastEthernet0/1, Forward/Dense, 00:42:22/00:00:00
The output reveals that the router has in fact joined the group 224.9.9.9 as well as the group 224.0.1.40. Note that there is a (*,G) entry for each of these groups. In this instance, R9 is acting like a host and as a result will send its IGMP membership reports to R7. This can be observed via the show ip igmp membership command. R7#show ip igmp membership Flags: A - aggregate, T - tracked
Copyright © by IPexpert, Inc. All Rights Reserved.
3-11
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
L - Local, S - static, V - virtual, R - Reported through v3 I - v3lite, U - Urd, M - SSM (S,G) channel 1,2,3 - The version of IGMP the group is in Channel/Group-Flags: / - Filtering entry (Exclude mode (S,G), Include mode (*,G)) Reporter: - last reporter if group is not explicitly tracked / - reporter in include mode, reporter in exclude Channel/Group *,224.9.9.9 *,224.0.1.40 *,224.0.1.40
Reporter 172.16.79.9 172.16.79.9 172.16.67.7
Uptime 00:52:19 00:52:03 00:52:29
Exp. 02:53 02:58 02:30
Flags 2A 2A 2LA
Interface Fa0/1 Fa0/1 Fa0/0
R9 has notified the IGMP router R7 that it is interested in the multicast group 224.9.9.9. Does R7 forward any of this information to adjacent devices? No, R7 has no mechanism or requirement to forward these IGMP report messages to any of its adjacent neighbors in PIM-‐DM. This can be seen with either the show ip igmp membership or show ip mroute commands on R6. R6#show ip mroute 224.9.9.9 Group 224.9.9.9 not found
There is no entry for a (*, 224.9.9.9) on R6, nor is there an entry for that group in the IGMP membership list. R6#show ip igmp membership 224.9.9.9 Flags: A - aggregate, T - tracked L - Local, S - static, V - virtual, R - Reported through v3 I - v3lite, U - Urd, M - SSM (S,G) channel 1,2,3 - The version of IGMP the group is in Channel/Group-Flags: / - Filtering entry (Exclude mode (S,G), Include mode (*,G)) Reporter: - last reporter if group is not explicitly tracked / - reporter in include mode, reporter in exclude Channel/Group
Reporter
Uptime
Exp.
Flags
Interface
This clearly illustrates that the IGMP router is not forwarding any of the information learned from R9. The reason for this behavior is that PIM-‐DM uses an implicit join methodology where the protocol assumes all devices are interested in receiving the multicast feed. So rather than notifying any of its neighbors that R9 has joined a specific group, R7 instead will assume that any multicast feed for the group 224.9.9.9 will be flooded to it. This means that in PIM-‐DM, R4 will be listening for the multicast traffic to arrive on any of its interfaces, but it will not notify any other routers that it has an adjacent
Copyright © by IPexpert, Inc. All Rights Reserved.
3-12
IPv4/6 Multicast Operation and Troubleshooting
Chapter 3: PIM - Dense Mode (PIM-DM)
host that has joined any particular group. This is the flooding portion of the PIM-‐DM "Flood and Prune" behavior. Step Four: Flooding of a Multicast Feed The previous step outlined the relationship between the IGMP host and the IGMP router. The previous chapter described the IGMP mechanism as the protocol that encompasses the last leg of the multicast routing tree. We have observed that only the host and its adjacent IGMP router knows about the join-‐ group command under the FastEthernet0/1 interface of R9. The next step is to emulate a multicast source and observe how PIM-‐DM will flood the multicast stream. The source in our topology is R1, and to emulate a multicast feed we will initiate a ping destined to a multicast group. For testing purposes, this ping will not match the multicast group that R9 has joined. No host being interested in the multicast feed will result in the pings on R1 failing. Nevertheless, the object of this exercise is to follow the multicast feed through the network, observe its behavior, and note any related characteristics. We will use a very high repeat count on R1 to make sure that the multicast feed remains active throughout our testing. R1#ping 224.1.1.1 repeat 100000000 Type escape sequence to abort. Sending 100000000, 100-byte ICMP Echos to 224.1.1.1, timeout is 2 seconds: ...................................