HPE FlexNetwork HSR6800 Routers

Transcription

1 HPE FlexNetwork HSR6800 Routers IP Multicast Configuration Guide Part number: R Software version: HSR6800-CMW520-R3303P25 Document version: 6W

2 Copyright 2015 Hewlett Packard Enterprise Development LP The information contained herein is subject to change without notice. The only warranties for Hewlett Packard Enterprise products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein. Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or copying. Consistent with FAR and , Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor s standard commercial license. Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise website. Acknowledgments Intel, Itanium, Pentium, Intel Inside, and the Intel Inside logo are trademarks of Intel Corporation in the United States and other countries. Microsoft and Windows are trademarks of the Microsoft group of companies. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. Java and Oracle are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.

3 Contents Multicast overview 1 Overview 1 Multicast overview 1 Multicast features 3 Common notations in multicast 4 Multicast advantages and applications 4 Multicast models 4 Multicast architecture 5 Multicast addresses 5 Multicast protocols 8 Multicast packet forwarding mechanism 10 Multicast support for VPNs 11 Introduction to VPN instances 11 Multicast application in VPNs 12 Configuring IGMP snooping 13 Overview 13 Basic concepts in IGMP snooping 13 How IGMP snooping works 15 IGMP snooping proxying 16 Protocols and standards 17 IGMP snooping configuration task list 17 Configuring basic IGMP snooping functions 18 Configuration prerequisites 18 Enabling IGMP snooping 18 Specifying the IGMP snooping version 19 Setting the maximum number of IGMP snooping forwarding entries 19 Configuring IGMP snooping port functions 20 Configuration prerequisites 20 Setting aging timers for dynamic ports 20 Configuring static ports 21 Configuring a port as a simulated member host 21 Enabling IGMP snooping fast-leave processing 22 Disabling a port from becoming a dynamic router port 23 Configuring IGMP snooping querier 23 Configuration prerequisites 24 Enabling IGMP snooping querier 24 Configuring parameters for IGMP queries and responses 24 Configuring source IP addresses for IGMP queries 25 Configuring IGMP snooping proxying 26 Configuration prerequisites 26 Enabling IGMP snooping proxying 26 Configuring the source IP addresses for the IGMP messages sent by the proxy 26 Configuring IGMP snooping policies 27 Configuration prerequisites 27 Configuring a multicast group filter 27 Configuring multicast source port filtering 28 Enabling dropping unknown multicast data 28 Enabling IGMP report suppression 29 Setting the maximum number of multicast groups that a port can join 29 Enabling multicast group replacement 30 Setting the 802.1p precedence for IGMP messages 31 Enabling the IGMP snooping host tracking function 31 Displaying and maintaining IGMP snooping 32 IGMP snooping configuration examples 33 Group policy and simulated joining configuration example 33 Static port configuration example 35 i

4 IGMP snooping querier configuration example 38 IGMP snooping proxying configuration example 40 Troubleshooting IGMP snooping 43 Layer 2 multicast forwarding cannot function 43 Configured multicast group policy fails to take effect 43 Appendix 44 Processing of multicast protocol messages 44 Configuring multicast routing and forwarding 45 Overview 45 RPF check mechanism 45 Static multicast routes 47 Multicast forwarding across unicast subnets 49 Multicast traceroute 49 Configuration task list 50 Enabling IP multicast routing 50 Configuring multicast routing and forwarding 51 Configuration prerequisites 51 Configuring static multicast routes 51 Configuring a multicast routing policy 52 Configuring a multicast forwarding range 53 Configuring the multicast forwarding table size 53 Configuring static multicast MAC address entries 54 Tracing a multicast path 55 Displaying and maintaining multicast routing and forwarding 55 Configuration examples 57 Changing an RPF route 57 Creating an RPF route 59 Multicast forwarding over GRE tunnels 60 Troubleshooting multicast routing and forwarding 63 Static multicast route failure 63 Configuring IGMP 65 Overview 65 IGMP versions 65 IGMPv1 overview 65 IGMPv2 overview 66 IGMPv3 overview 67 IGMP SSM mapping 68 IGMP proxying 69 IGMP support for VPNs 70 Protocols and standards 70 IGMP configuration task list 71 Configuring basic IGMP functions 71 Configuration prerequisites 71 Enabling IGMP 72 Specifying the version of IGMP 72 Configuring an interface as a static member interface 73 Configuring a multicast group filter 73 Setting the maximum number of multicast groups that an interface can join 74 Adjusting IGMP performance 74 Configuration prerequisites 74 Configuring Router-Alert option handling methods 75 Configuring IGMP query and response parameters 75 Enabling IGMP fast-leave processing 77 Enabling the IGMP host tracking function 78 Configuring IGMP SSM mapping 79 Configuration prerequisites 79 Enabling SSM mapping 79 Configuring SSM mappings 79 Configuring IGMP proxying 80 Configuration prerequisites 80 ii

5 Enabling IGMP proxying 80 Configuring multicast forwarding on a downstream interface 81 Displaying and maintaining IGMP 81 IGMP configuration examples 83 Basic IGMP functions configuration example 83 SSM mapping configuration example 85 IGMP proxying configuration example 88 Troubleshooting IGMP 90 No membership information exists on the receiver-side router 90 Membership information is inconsistent on the routers on the same subnet 91 Configuring PIM 92 Overview 92 PIM-DM overview 92 PIM-SM overview 94 BIDIR-PIM overview 100 Administrative scoping overview 103 PIM-SSM overview 105 Relationship among PIM protocols 106 PIM support for VPNs 107 Protocols and standards 107 Configuring PIM-DM 107 PIM-DM configuration task list 107 Configuration prerequisites 108 Enabling PIM-DM 108 Enabling state-refresh capability 109 Configuring state-refresh parameters 109 Configuring PIM-DM graft retry period 110 Configuring PIM-SM 110 PIM-SM configuration task list 110 Configuration prerequisites 111 Enabling PIM-SM 112 Configuring an RP 112 Configuring a BSR 114 Configuring administrative scoping 118 Configuring multicast source registration 120 Configuring switchover to SPT 120 Configuring BIDIR-PIM 121 BIDIR-PIM configuration task list 121 Configuration prerequisites 121 Enabling PIM-SM 122 Enabling BIDIR-PIM 123 Configuring an RP 123 Configuring a BSR 125 Configuring administrative scoping 128 Configuring PIM-SSM 130 PIM-SSM configuration task list 130 Configuration prerequisites 130 Enabling PIM-SM 131 Configuring the SSM group range 132 Configuring common PIM features 132 Configuration task list 132 Configuration prerequisites 133 Configuring a multicast data filter 133 Configuring a hello message filter 134 Configuring PIM hello options 134 Setting the prune delay timer 135 Configuring common PIM timers 136 Configuring join/prune message sizes 137 Configuring PIM to work with BFD 138 Displaying and maintaining PIM 138 PIM configuration examples 139 iii

6 PIM-DM configuration example 139 PIM-SM non-scoped zone configuration example 142 PIM-SM admin-scoped zone configuration example 147 BIDIR-PIM configuration example 153 PIM-SSM configuration example 157 Troubleshooting PIM 160 A multicast distribution tree cannot be built correctly 160 Multicast data abnormally terminated on an intermediate router 161 RPs cannot join SPT in PIM-SM 161 RPT establishment failure or source registration failure in PIM-SM 162 Configuring MSDP 163 Overview 163 How MSDP works 163 MSDP support for VPNs 168 Protocols and standards 168 MSDP configuration task list 168 Configuring basic MSDP functions 169 Configuration prerequisites 169 Enabling MSDP 169 Creating an MSDP peer connection 170 Configuring a static RPF peer 170 Configuring an MSDP peer connection 170 Configuration prerequisites 171 Configuring MSDP peer description 171 Configuring an MSDP mesh group 171 Configuring MSDP peer connection control 172 Configuring SA message related parameters 173 Configuration prerequisites 173 Configuring SA message content 173 Configuring SA request messages 174 Configuring SA message filtering rules 174 Configuring the SA cache mechanism 175 Displaying and maintaining MSDP 175 MSDP configuration examples 176 PIM-SM Inter-domain multicast configuration 176 Inter-AS multicast configuration by leveraging static RPF peers 181 Anycast RP configuration 185 SA message filtering configuration 189 Troubleshooting MSDP 192 MSDP peers stay in down state 192 No SA entries exist in the router's SA cache 193 No SA entries exist in the router's SA cache 193 Configuring MBGP 195 MBGP overview 195 Protocols and standards 195 MBGP configuration task list 195 Configuring basic MBGP functions 196 Configuration prerequisites 196 Configuration procedure 196 Controlling route advertisement and reception 196 Configuration prerequisites 196 Configuring MBGP route redistribution 197 Configuring default route redistribution into MBGP 197 Configuring MBGP route summarization 198 Advertising a default route to an IPv4 MBGP peer or peer group 198 Configuring outbound MBGP route filtering 199 Configuring inbound MBGP route filtering 200 Configuring MBGP route dampening 201 Configuring MBGP route attributes 201 Configuration prerequisites 201 iv

7 Configuring MBGP route preferences 201 Configuring the default local preference 202 Configuring the MED attribute 202 Configuring the NEXT_HOP attribute 202 Configuring the AS_PATH attribute 203 Optimizing MBGP networks 204 Configuration prerequisites 204 Configuring MBGP soft reset 204 Enabling the MBGP ORF capability 205 Configuring the maximum number of MBGP routes for load balancing 206 Configuring a large scale MBGP network 206 Configuration prerequisites 206 Configuring IPv4 MBGP peer groups 206 Configuring MBGP community 207 Configuring an MBGP route reflector 208 Displaying and maintaining MBGP 208 Displaying MBGP 208 Resetting MBGP connections 210 Clearing MBGP information 210 MBGP configuration example 210 Network requirements 210 Configuration procedure 211 Configuring multicast VPN 214 Overview 214 MD-VPN overview 216 Multicast across VPNs 219 Protocols and standards 221 How MD-VPN works 221 Share-MDT establishment 222 Share-MDT-based delivery 225 MDT switchover 229 Multi-AS MD VPN 230 Multicast VPN configuration task list 231 Configuring MD-VPN 231 Configuration prerequisites 231 Enabling IP multicast routing in a VPN instance 232 Configuring a share-group and an MTI binding 232 Configuring MDT switchover parameters 233 Enabling switch-group reuse logging 233 Configuring BGP MDT 234 Configuration prerequisites 234 Configuring BGP MDT peers or peer groups 234 Configuring a BGP MDT route reflector 234 Specifying the source IP address for multicast across VPNs 235 Configuration prerequisites 235 Configuration procedure 235 Displaying and maintaining multicast VPN 236 Multicast VPN configuration examples 236 Single-AS MD VPN configuration example 237 Multi-AS MD VPN configuration example 249 Troubleshooting MD-VPN 261 A share-mdt cannot be established 261 An MVRF cannot be created 262 Configuring IPv6 multicast routing and forwarding 263 Overview 263 RPF check mechanism 263 RPF check implementation in IPv6 multicast 264 IPv6 multicast forwarding across IPv6 unicast subnets 265 Configuration task list 266 Enabling IPv6 multicast routing 266 v

8 Configuring IPv6 multicast routing and forwarding 266 Configuration prerequisites 266 Configuring an IPv6 multicast routing policy 266 Configuring an IPv6 multicast forwarding range 267 Configuring the IPv6 multicast forwarding table size 267 Configuring IPv6 static multicast MAC address entries 268 Displaying and maintaining IPv6 multicast routing and forwarding 269 IPv6 multicast forwarding over GRE tunnel configuration example 270 Network requirements 271 Configuration procedure 271 Verifying the configuration 273 Troubleshooting abnormal termination of IPv6 multicast data 274 Configuring MLD 275 Overview 275 MLD versions 275 How MLDv1 works 275 How MLDv2 works 277 MLD message types 278 MLD SSM mapping 280 MLD proxying 281 Protocols and standards 282 MLD configuration task list 282 Configuring basic MLD functions 282 Configuration prerequisites 283 Enabling MLD 283 Configuring the MLD version 283 Configuring static joining 284 Configuring an IPv6 multicast group filter 284 Setting the maximum number of IPv6 multicast groups that an interface can join 284 Adjusting MLD performance 285 Configuration prerequisites 285 Configuring Router-Alert option handling methods 285 Configuring MLD query and response parameters 286 Enabling MLD fast-leave processing 288 Enabling the MLD host tracking function 289 Configuring MLD SSM mapping 289 Configuration prerequisites 289 Enabling MLD SSM mapping 289 Configuring MLD SSM mapping 290 Configuring MLD proxying 290 Configuration prerequisites 290 Enabling MLD proxying 290 Configuring IPv6 multicast forwarding on a downstream interface 291 Displaying and maintaining MLD 291 MLD configuration examples 293 Basic MLD functions configuration example 293 MLD SSM mapping configuration example 295 MLD proxying configuration example 298 Troubleshooting MLD 299 No member information exists on the receiver-side router 299 Membership information is inconsistent on the routers on the same subnet 300 Configuring IPv6 PIM 301 Overview 301 IPv6 PIM-DM overview 301 IPv6 PIM-SM overview 304 IPv6 BIDIR-PIM overview 309 IPv6 administrative scoping overview 312 IPv6 PIM-SSM overview 314 Relationship among IPv6 PIM protocols 315 Protocols and standards 316 vi

9 Configuring IPv6 PIM-DM 316 IPv6 PIM-DM configuration task list 316 Configuration prerequisites 317 Enabling IPv6 PIM-DM 317 Enabling state-refresh capability 317 Configuring state refresh parameters 318 Configuring IPv6 PIM-DM graft retry period 318 Configuring IPv6 PIM-SM 319 IPv6 PIM-SM configuration task list 319 Configuration prerequisites 319 Enabling IPv6 PIM-SM 320 Configuring an RP 320 Configuring a BSR 322 Configuring IPv6 administrative scoping 326 Configuring IPv6 multicast source registration 327 Configuring switchover to SPT 328 Configuring IPv6 BIDIR-PIM 328 IPv6 BIDIR-PIM configuration task list 328 Configuration prerequisites 329 Enabling IPv6 PIM-SM 329 Enabling IPv6 BIDIR-PIM 330 Configuring an RP 330 Configuring a BSR 332 Configuring IPv6 administrative scoping 335 Configuring IPv6 PIM-SSM 336 IPv6 PIM-SSM configuration task list 336 Configuration prerequisites 337 Enabling IPv6 PIM-SM 337 Configuring the IPv6 SSM group range 337 Configuring common IPv6 PIM features 338 Configuration task list 338 Configuration prerequisites 338 Configuring an IPv6 multicast data filter 339 Configuring a hello message filter 339 Configuring IPv6 PIM hello options 340 Setting the prune delay timer 341 Configuring common IPv6 PIM timers 341 Configuring join/prune message sizes 343 Displaying and maintaining IPv6 PIM 343 IPv6 PIM configuration examples 344 IPv6 PIM-DM configuration example 344 IPv6 PIM-SM non-scoped zone configuration example 347 IPv6 PIM-SM admin-scoped zone configuration example 352 IPv6 BIDIR-PIM configuration example 364 IPv6 PIM-SSM configuration example 368 Troubleshooting IPv6 PIM 371 A multicast distribution tree cannot be built correctly 371 RPs cannot join the SPT in IPv6 PIM-SM 372 RPT cannot be established or a source cannot register in IPv6 PIM-SM 372 Configuring IPv6 MBGP 1 Overview 1 IPv6 MBGP configuration task list 1 Configuring basic IPv6 MBGP functions 2 Configuration prerequisites 2 Configuring an IPv6 MBGP peer 2 Configuring a preferred value for routes from a peer or a peer group 2 Controlling route distribution and reception 3 Configuration prerequisites 3 Injecting a local IPv6 MBGP route 3 Configuring IPv6 MBGP route redistribution 3 Configuring IPv6 MBGP route summarization 4 vii

10 Advertising a default route to a peer or peer group 4 Configuring outbound IPv6 MBGP route filtering 4 Configuring inbound IPv6 MBGP route filtering 5 Configuring IPv6 MBGP route dampening 6 Configuring IPv6 MBGP route attributes 7 Configuration prerequisites 7 Configuring IPv6 MBGP route preferences 7 Configuring the default local preference 7 Configuring the MED attribute 7 Configuring the NEXT_HOP attribute 8 Configuring the AS_PATH attribute 8 Optimizing IPv6 MBGP networks 9 Configuration prerequisites 9 Configuring IPv6 MBGP soft reset 9 Enabling the IPv6 MBGP ORF capability 10 Configuring the maximum number of equal-cost routes for load-balancing 11 Configuring a large scale IPv6 MBGP network 12 Configuration prerequisites 12 Configuring an IPv6 MBGP peer group 12 Configuring IPv6 MBGP community 12 Configuring an IPv6 MBGP route reflector 13 Displaying and maintaining IPv6 MBGP 14 Displaying IPv6 MBGP 14 Resetting IPv6 MBGP connections 15 Clearing IPv6 MBGP information 15 IPv6 MBGP configuration example 16 Configuring PIM snooping 19 Overview 19 Configuring PIM snooping 20 Displaying and maintaining PIM snooping 20 PIM snooping configuration example 21 Troubleshooting PIM snooping 23 PIM snooping does not work 23 Some downstream PIM routers cannot receive multicast data 24 Configuring multicast VLANs 25 Overview 25 Multicast VLAN configuration task list 27 Configuring a sub-vlan-based multicast VLAN 27 Configuring a port-based multicast VLAN 27 Configuration prerequisites 28 Configuring user port attributes 28 Configuring multicast VLAN ports 28 Setting the maximum number of forwarding entries in a multicast VLAN 29 Displaying and maintaining a multicast VLAN 30 Multicast VLAN configuration examples 30 Sub-VLAN-based multicast VLAN configuration example 30 Port-based multicast VLAN configuration example 34 Document conventions and icons 37 Conventions 37 Network topology icons 38 Support and other resources 39 Accessing Hewlett Packard Enterprise Support 39 Accessing updates 39 Websites 40 Customer self repair 40 Remote support 40 Documentation feedback 40 viii

11 Index 42 ix

12 Multicast overview Overview As a technique that coexists with unicast and broadcast, the multicast technique effectively addresses the issue of point-to-multipoint data transmission. By enabling high-efficiency point-to-multipoint data transmission over a network, multicast greatly saves network bandwidth and reduces network load. By using multicast technology, a network operator can easily provide new value-added services, such as live webcasting, web TV, distance learning, telemedicine, web radio, real-time video conferencing, and other bandwidth-critical and time-critical information services. Unless otherwise stated, the term "multicast" in this document refers to IP multicast. Multicast overview The information transmission techniques include unicast, broadcast, and multicast. Unicast In unicast transmission, the information source must send a separate copy of information to each host that needs the information. Figure 1 Unicast transmission Host A Receiver Host B Source Host C Receiver Host D IP network Packets for Host B Packets for Host D Packets for Host E Receiver Host E In Figure 1, assume that Host B, Host D and Host E need the information. A separate transmission channel must be established from the information source to each of these hosts. In unicast transmission, the traffic transmitted over the network is proportional to the number of hosts that need the information. If a large number of hosts need the information, the information source must send a separate copy of the same information to each of these hosts. Sending many copies can place a tremendous pressure on the information source and the network bandwidth. 1

13 Broadcast Unicast is not suitable for batch transmission of information. In broadcast transmission, the information source sends information to all hosts on the subnet, even if some hosts do not need the information. Figure 2 Broadcast transmission In Figure 2, assume that only Host B, Host D, and Host E need the information. If the information is broadcast to the subnet, Host A and Host C also receive it. In addition to information security issues, broadcasting to hosts that do not need the information also causes traffic flooding on the same subnet. Broadcast is disadvantageous in transmitting data to specific hosts. Moreover, broadcast transmission is a significant waste of network resources. Multicast Unicast and broadcast techniques cannot provide point-to-multipoint data transmissions with the minimum network consumption. Multicast transmission can solve this problem. When some hosts on the network need multicast information, the information sender, or multicast source, sends only one copy of the information. Multicast distribution trees are built through multicast routing protocols, and the packets are replicated only on nodes where the trees branch. 2

14 Figure 3 Multicast transmission As shown in Figure 3, the multicast source sends only one copy of the information to a multicast group. Host B, Host D and Host E, which are receivers of the information, must join the multicast group. The routers on the network duplicate and forward the information based on the distribution of the group members. Finally, the information is correctly delivered to Host B, Host D, and Host E. To summarize, multicast has the following advantages: Advantages over unicast Because multicast traffic flows to the farthest-possible node from the source before it is replicated and distributed, an increase in the number of hosts does not increase the load of the source or remarkably add to the usage of network resources. Advantages over broadcast Because multicast data is sent only to the receivers that need it, multicast uses network bandwidth reasonably and enhances network security. In addition, data broadcast is confined to the same subnet, but multicast is not. Multicast features Multicast transmission has the following features: A multicast group is a multicast receiver set identified by an IP multicast address. Hosts join a multicast group to become members of the multicast group before they can receive the multicast data addressed to that multicast group. Typically, a multicast source does not need to join a multicast group. An information sender is called a "multicast source." A multicast source can send data to multiple multicast groups at the same time, and multiple multicast sources can send data to the same multicast group at the same time. All hosts that have joined a multicast group become members of the multicast group. The group memberships are dynamic. Hosts can join or leave multicast groups at any time. Multicast groups are not subject to geographic restrictions. Routers or Layer 3 switches that support Layer 3 multicast are called "multicast routers" or "Layer 3 multicast devices." In addition to providing the multicast routing function, a multicast router can also manage multicast group memberships on stub subnets with attached group members. A multicast router itself can be a multicast group member. For a better understanding of the multicast concept, you can compare multicast transmission to the transmission of TV programs. 3

15 Table 1 Comparing TV program transmission and multicast transmission TV program transmission A TV station transmits a TV program through a channel. A user tunes the TV set to the channel. The user starts to watch the TV program transmitted by the TV station through the channel. The user turns off the TV set or tunes to another channel. Multicast transmission A multicast source sends multicast data to a multicast group. A receiver joins the multicast group. The receiver starts to receive the multicast data that the source is sending to the multicast group. The receiver leaves the multicast group or joins another group. Common notations in multicast The following notations are commonly used in multicast transmission: (*, G) Rendezvous point tree (RPT), or a multicast packet that any multicast source sends to multicast group G. Here, the asterisk represents any multicast source, and "G" represents a specific multicast group. (S, G) Shortest path tree (SPT), or a multicast packet that multicast source S sends to multicast group G. Here, "S" represents a specific multicast source, and "G" represents a specific multicast group. For more information about the concepts RPT and SPT, see "Configuring PIM" and "Configuring IPv6 PIM." Multicast advantages and applications The multicast technique has the following advantages: Enhanced efficiency Reduces the processor load of information source servers and network devices. Optimal performance Reduces redundant traffic. Distributed application Enables point-to-multipoint applications at the price of minimum network resources. The multicast technique can be use for the following applications: Multimedia and streaming applications, such as web TV, web radio, and real-time video/audio conferencing Communication for training and cooperative operations, such as distance learning and telemedicine Data warehouse and financial applications (stock quotes) Any other point-to-multipoint application for data distribution Multicast models Based on how the receivers treat the multicast sources, the multicast models include any-source multicast (ASM), source-filtered multicast (SFM), and source-specific multicast (SSM). ASM model In the ASM model, any sender can send information to a multicast group as a multicast source, and receivers can join a multicast group (identified by a group address) and obtain multicast information addressed to that multicast group. In this model, receivers do not 4

16 know the positions of the multicast sources in advance. However, they can join or leave the multicast group at any time. SFM model The SFM model is derived from the ASM model. To a sender, the two models appear to have the same multicast membership architecture. The SFM model functionally extends the ASM model. The upper-layer software checks the source address of received multicast packets and permits or denies multicast traffic from specific sources. Therefore, receivers can receive the multicast data from only part of the multicast sources. Because not all multicast sources are valid to receivers, they are filtered. SSM model Users might be interested in the multicast data from only certain multicast sources. The SSM model provides a transmission service that enables users to specify the multicast sources that they are interested in at the client side. The main difference between the SSM model and the ASM model is that in the SSM model, receivers have already determined the locations of the multicast sources by some other means. In addition, the SSM model uses a multicast address range that is different from that of the ASM/SFM model, and dedicated multicast forwarding paths are established between receivers and the specified multicast sources. Multicast architecture IP multicast addresses the following issues: Where should the multicast source transmit information to? (multicast addressing) What receivers exist on the network? (host registration) Where is the multicast source that will provide data to the receivers? (multicast source discovery) How should information be transmitted to the receivers? (multicast routing) IP multicast is an end-to-end service. The multicast architecture involves the following parts: 1. Addressing mechanism A multicast source sends information to a group of receivers through a multicast address. 2. Host registration Receiver hosts can join and leave multicast groups dynamically. This mechanism is the basis for management of group memberships. 3. Multicast routing A multicast distribution tree (namely, a forwarding path tree for multicast data on the network) is constructed for delivering multicast data from a multicast source to receivers. 4. Multicast applications A software system that supports multicast applications, such as video conferencing, must be installed on multicast sources and receiver hosts. The TCP/IP stack must support reception and transmission of multicast data. Multicast addresses Network-layer multicast addresses (namely, multicast IP addresses) enable communication between multicast sources and multicast group members. In addition, a technique must be available to map multicast IP addresses to link-layer multicast MAC addresses. The membership of a group is dynamic. Hosts can join or leave multicast groups at any time. IP multicast addresses IPv4 multicast addresses The IANA assigned the Class D address space ( to ) for IPv4 multicast. 5

17 Table 2 Class D IP address blocks and description Address block to to to Description Reserved permanent group addresses. The IP address is reserved. Other IP addresses can be used by routing protocols and for topology searching, protocol maintenance, and so on. Table 3 lists common permanent group addresses. A packet destined for an address in this block will not be forwarded beyond the local subnet regardless of the TTL value in the IP header. Globally scoped group addresses. This block includes the following types of designated group addresses: /8 SSM group addresses /8 Glop group addresses. Administratively scoped multicast addresses. These addresses are considered locally unique rather than globally unique, and can be reused in domains administered by different organizations without causing conflicts. For more information, see RFC "Glop" is a mechanism for assigning multicast addresses between different autonomous systems (ASs). By filling an AS number into the middle two bytes of , you get 255 multicast addresses for that AS. For more information, see RFC Table 3 Some reserved multicast addresses Address Description All systems on this subnet, including hosts and routers All multicast routers on this subnet Unassigned DVMRP routers OSPF routers OSPF designated routers and backup designated routers ST routers ST hosts RIPv2 routers Mobile agents DHCP server/relay agent All PIM routers RSVP encapsulation All CBT routers SBM All SBMs VRRP. IPv6 multicast addresses 6

18 Figure 4 IPv6 multicast format The following describes the fields of an IPv6 multicast address, as shown in Figure 4: 0xFF The most significant eight bits are , which indicates that this address is an IPv6 multicast address. Flags The Flags field contains four bits, as shown in Figure 5 and described in Table 4. Figure 5 Flags field format Table 4 Flags field description Bit Description 0 Reserved, set to 0. R P T When set to 0, this address is an IPv6 multicast address without an embedded RP address. When set to 1, this address is an IPv6 multicast address with an embedded RP address (the P and T bits must also be set to 1). When set to 0, this address is an IPv6 multicast address not based on a unicast prefix. When set to 1, this address is an IPv6 multicast address based on a unicast prefix (the T bit must also be set to 1). When set to 0, this address is an IPv6 multicast address permanently-assigned by IANA. When set to 1, this address is a transient, or dynamically assigned IPv6 multicast address. Scope The Scope field contains four bits, which indicate the scope of the IPv6 internetwork for which the multicast traffic is intended. Table 5 describes the values of the Scope field. Table 5 Values of the Scope field Value Meaning 0, F Reserved. 1 Interface-local scope. 2 Link-local scope. 3 Subnet-local scope. 4 Admin-local scope. 5 Site-local scope. 6, 7, 9 through D Unassigned. 8 Organization-local scope. 7

19 Value E Meaning Global scope. Group ID The Group ID field contains 112 bits. It uniquely identifies an IPv6 multicast group in the scope that the Scope field defines. Ethernet multicast MAC addresses A multicast MAC address identifies a group of receivers at the data link layer. IPv4 multicast MAC addresses As defined by IANA, the most significant 24 bits of an IPv4 multicast MAC address are 0x01005E. Bit 25 is 0, and the other 23 bits are the least significant 23 bits of a multicast IPv4 address. Figure 6 IPv4-to-MAC address mapping As shown in Figure 6, the most significant four bits of a multicast IPv4 address are 1110, which indicates that this address is a multicast address. Only 23 bits of the remaining 28 bits are mapped to a MAC address, so five bits of the multicast IPv4 address are lost. As a result, 32 multicast IPv4 addresses map to the same IPv4 multicast MAC address. Therefore, in Layer 2 multicast forwarding, a switch might receive some multicast data destined for other IPv4 multicast groups. The upper layer must filter such redundant data. IPv6 multicast MAC addresses As shown in Figure 7, the most significant 16 bits of an IPv6 multicast MAC address are 0x3333. The least significant 32 bits are the least significant 32 bits of a multicast IPv6 address. Figure 7 IPv6-to-MAC address mapping Multicast protocols Generally, Layer 3 multicast refers to IP multicast working at the network layer. The corresponding multicast protocols are Layer 3 multicast protocols, which include IGMP, MLD, PIM, IPv6 PIM, MSDP, MBGP, and IPv6 MBGP. Layer 2 multicast refers to IP multicast working at the data link layer. The 8

20 corresponding multicast protocols are Layer 2 multicast protocols, including IGMP snooping, PIM snooping, and multicast VLAN. IGMP snooping, PIM snooping, multicast VLAN, IGMP, PIM, MSDP, and MBGP are for IPv4, and MLD, IPv6 PIM, and IPv6 MBGP are for IPv6. This section provides only general descriptions about applications and functions of the Layer 2 and Layer 3 multicast protocols in a network. For more information about these protocols, see the related chapters. Layer 3 multicast protocols Layer 3 multicast protocols include multicast group management protocols and multicast routing protocols. Figure 8 Positions of Layer 3 multicast protocols Multicast group management protocols Typically, the Internet Group Management Protocol (IGMP) or Multicast Listener Discovery (MLD) protocol is used between hosts and Layer 3 multicast devices that directly connect to the hosts. These protocols define the mechanism of establishing and maintaining group memberships between hosts and Layer 3 multicast devices. Multicast routing protocols A multicast routing protocol runs on Layer 3 multicast devices to establish and maintain multicast routes and forward multicast packets correctly and efficiently. Multicast routes constitute loop-free data transmission paths (namely, a multicast distribution tree) from a data source to multiple receivers. In the ASM model, multicast routes include intra-domain routes and inter-domain routes. An intra-domain multicast routing protocol discovers multicast sources and builds multicast distribution trees within an AS to deliver multicast data to receivers. Among a variety of mature intra-domain multicast routing protocols, Protocol Independent Multicast (PIM) is most widely used. Based on the forwarding mechanism, PIM has dense mode (often referred to as "PIM-DM") and sparse mode (often referred to as "PIM-SM"). An inter-domain multicast routing protocol is used for delivery of multicast information between two ASs. So far, mature solutions include Multicast Source Discovery Protocol (MSDP) and Multicast Border Gateway Protocol (MBGP). MSDP propagates multicast source information among different ASs. MBGP is an extension of the Multiprotocol Border Gateway Protocol (MP-BGP) for exchanging multicast routing information among different ASs. 9

21 For the SSM model, multicast routes are not divided into intra-domain routes and inter-domain routes. Because receivers know the position of the multicast source, channels established through PIM-SM are sufficient for the transport of multicast information. Layer 2 multicast protocols Layer 2 multicast protocols include IGMP snooping, PIM snooping, and multicast VLAN. Figure 9 Positions of Layer 2 multicast protocols IGMP snooping: IGMP snooping is a multicast constraining mechanism that run on Layer 2 devices. They manage and control multicast groups by monitoring and analyzing IGMP messages exchanged between the hosts and Layer 3 multicast devices, effectively controlling the flooding of multicast data in a Layer 2 network. PIM snooping: PIM snooping runs on Layer 2 devices. It determines which ports are interested in multicast data by analyzing the received PIM messages, and add the ports to a multicast forwarding entry to make sure multicast data can be forwarded to only the ports that are interested in the data. Multicast VLAN: In the traditional multicast-on-demand mode, when users in different VLANs on a Layer 2 device need multicast information, the upstream Layer 3 device must forward a separate copy of the multicast data to each VLAN of the Layer 2 device. When the multicast VLAN feature is enabled on the Layer 2 device, the Layer 3 multicast device sends only one copy of multicast to the multicast VLAN on the Layer 2 device. This approach avoids wasting network bandwidth and placing an extra burden on the Layer 3 device. Multicast packet forwarding mechanism In a multicast model, a multicast source sends information to the host group identified by the multicast group address in the destination address field of IP multicast packets. To deliver multicast packets to receivers located at different positions of the network, multicast routers on the forwarding paths usually need to forward multicast packets that an incoming interface receives to multiple outgoing interfaces. Compared with a unicast model, a multicast model is more complex in the following aspects: 10

22 To ensure multicast packet transmission in the network, unicast routing tables or multicast routing tables (for example, the MBGP routing table) specially provided for multicast must be used as guidance for multicast forwarding. To process the same multicast information from different peers received on different interfaces of the same device, every multicast packet undergoes a reverse path forwarding (RPF) check on the incoming interface. The result of the RPF check determines whether the packet will be forwarded or discarded. The RPF check mechanism is the basis for most multicast routing protocols to implement multicast forwarding. For more information about the RPF mechanism, see "Configuring multicast routing and forwarding" and "Configuring IPv6 multicast routing and forwarding." Multicast support for VPNs Multicast support for VPNs refers to multicast applied on virtual private networks (VPNs). Multicast support for VPNs is not available on IPv6 networks. Introduction to VPN instances VPNs must be isolated from one another and from the public network. As shown in Figure 10, VPN A and VPN B separately access the public network through PE devices. Figure 10 VPN networking diagram VPN A CE a2 CE b2 PE 2 CE b3 VPN B VPN B CE b1 P CE a1 PE 1 Public network PE 3 CE a3 VPN A VPN A The provider (P) device belongs to the public network. The customer edge (CE) devices belong to their respective VPNs. Each CE device serves its own VPN and maintains only one set of forwarding mechanisms. The provider edge (PE) devices connect to the public network and the VPNs. Each PE device must strictly distinguish the information for different networks, and maintain a separate forwarding mechanism for each network. On a PE device, a set of software and hardware that serve the same network forms an instance. Multiple instances can exist on the same PE device, 11

23 and an instance can reside on different PE devices. On a PE device, the instance for the public network is called the public network instance, and those for VPNs are called VPN instances. Multicast application in VPNs A PE device that supports multicast for VPNs does the following operations: Maintains an independent set of multicast forwarding mechanisms for each VPN, including the multicast protocols, PIM neighbor information, and multicast routing table. In a VPN, the device forwards multicast data based on the forwarding table or routing table for that VPN. Implements the isolation between different VPNs. Implements information exchange and data conversion between the public network and VPN instances. As shown in Figure 10, when a multicast source in VPN A sends a multicast stream to a multicast group, only the receivers that belong to both the multicast group and VPN A can receive the multicast stream. The multicast data is multicast both in VPN A and on the public network. 12

24 Configuring IGMP snooping Overview IGMP snooping is a multicast constraining mechanism that runs on Layer 2 devices to manage and control multicast groups. By analyzing received IGMP messages, an IGMP snooping-enabled Layer 2 device establishes mappings between ports and multicast MAC addresses, and forwards multicast data based on these mappings. As shown in Figure 11, without IGMP snooping, a Layer 2 switch floods multicast packets out of all ports but the incoming port. IGMP snooping enables a Layer 2 switch to forward multicast packets destined for a known multicast group address out of only ports that have multicast receivers. This feature improves bandwidth efficiency, enhances multicast security, and helps per-host accounting for multicast users. IGMP snooping is supported only when the SAP module is operating in bridge mode. Figure 11 Before and after IGMP snooping is enabled on the Layer 2 device Basic concepts in IGMP snooping This section lists the basic concepts in IGMP snooping. IGMP snooping related ports As shown in Figure 12, Router A connects to the multicast source, IGMP snooping runs on Router B and Router C, and Host A and Host C are multicast receivers. 13

25 Figure 12 IGMP snooping related ports As shown in Figure 12, IGMP snooping divides the ports on the router into the following types: Router port Layer 3 multicast device-side port. Layer 3 multicast devices include DRs and IGMP queriers. In the figure, GigabitEthernet 1/0/1 of Router B and GigabitEthernet 1/0/1 of Router C are router ports. The router registers all its local router ports in its router port list. Do not confuse the "router port" in IGMP snooping with the "routed interface" commonly known as the "Layer 3 interface." The router port in IGMP snooping is the Layer 2 interface. Member port Multicast receiver-side port. In the figure, GigabitEthernet 1/0/2 and GigabitEthernet 1/0/3 of Router B and GigabitEthernet 1/0/2 of Router C are member ports. The router registers all the member ports on the local device in its IGMP snooping forwarding table. Unless otherwise specified, router ports and member ports in this document include both static and dynamic router ports and member ports. Dynamic router ports include ports that receive IGMP general queries with the source IP address other than and ports that receive PIM hello messages. For more information about PIM hello messages, see "Configuring PIM." Aging timers for dynamic ports in IGMP snooping and related messages and actions Timer Description Message before expiration Action after expiration Dynamic router port aging timer. When a port receives an IGMP general query with the source address other than or a PIM hello message, the Layer 2 device starts an aging timer for the port. When the timer expires, the dynamic router port ages out. IGMP general query of which the source address is not or PIM hello. The router removes this port from its router port list. Dynamic member port aging timer. When a port dynamically joins a multicast group, the router starts an aging timer for the port. When the timer expires, the dynamic member port ages out. IGMP membership report. The router removes this port from the IGMP snooping forwarding table. 14

26 NOTE: In IGMP snooping, only dynamic ports age out. Static ports never age out. How IGMP snooping works An IGMP snooping-enabled router performs different actions when it receives different IGMP messages. The ports in this section are dynamic ports. For information about how to configure and remove static ports, see "Configuring static ports." When receiving a general query The IGMP querier periodically sends IGMP general queries to all hosts and routers ( ) on the local subnet to determine whether any active multicast group members exist on the subnet. After receiving an IGMP general query, the router forwards it to all ports in the VLAN, except the port that received the query. The router also performs one of the following actions: If the receiving port is a dynamic router port in the router port list, restarts the aging timer for the port. If the receiving port is not in the router port list, adds it into the router port list as a dynamic router port and starts an aging timer for the port. When receiving a membership report A host sends an IGMP report to the IGMP querier for the following purposes: Responds to an IGMP query if the host is a multicast group member. Applies for joining a multicast group. After receiving an IGMP report, the router forwards it through all the router ports in the VLAN, resolves the address of the reported multicast group, and performs the following actions: If no forwarding entry matches the group address, the router creates a forwarding entry for the group, adds the port that received the IGMP report as a dynamic member port to the forwarding entry, and starts an aging timer for the port. If a forwarding entry matches the group address, but the port that received the IGMP report is not in the forwarding entry for the group, the router adds the port as a dynamic member port to the forwarding entry, and starts an aging timer for the port. If a forwarding entry matches the group address and the port that received the IGMP report is in the forwarding entry for the group, the router restarts the aging timer for the port. A router does not forward an IGMP report through a non-router port. If the router forwards a report message through a member port, the IGMP report suppression mechanism causes all attached hosts that monitor the reported multicast address to suppress their own reports. This makes the router unable to know whether the reported multicast group still has active members attached to that port. For more information about the IGMP report suppression mechanism, see "Configuring IGMP." When receiving a leave message An IGMPv1 host silently leaves a multicast group and the router is not notified of the leave. However, because the host stops sending IGMP reports as soon as it leaves the multicast group, the router removes the port that connects to the host from the forwarding entry for the multicast group when the aging timer for the port expires. An IGMPv2 or IGMPv3 host sends an IGMP leave message to the multicast router when leaving a multicast group. When the router receives an IGMP leave message on a dynamic member port, the router first examines whether a forwarding entry matches the group address in the message, and, if a match is found, whether the forwarding entry for the group contains the dynamic member port. 15

27 If no forwarding entry matches the group address, or if the forwarding entry does not contain the port, the router directly discards the IGMP leave message. If a forwarding entry matches the group address and the forwarding entry contains the port, the router forwards the leave message to all router ports in the VLAN. Because the router does not know whether any other hosts attached to the port are still listening to that group address, the router does not immediately remove the port from the forwarding entry for that group. Instead, it restarts the aging timer for the port. After receiving the IGMP leave message, the IGMP querier resolves the multicast group address in the message and sends an IGMP group-specific query to the multicast group through the port that received the leave message. After receiving the IGMP group-specific query, the router forwards it through all its router ports in the VLAN and all member ports of the multicast group. The router also performs the following judgment for the port that received the IGMP leave message: If the port (assuming that it is a dynamic member port) receives an IGMP report in response to the group-specific query before its aging timer expires, it means that some host attached to the port is receiving or expecting to receive multicast data for the multicast group. The router restarts the aging timer for the port. If the port receives no IGMP report in response to the group-specific query before its aging timer expires, it means that no hosts attached to the port are still listening to that group address. The router removes the port from the forwarding entry for the multicast group when the aging timer expires. IGMP snooping proxying You can configure the IGMP snooping proxying function on an edge device to reduce the number of IGMP reports and leave messages sent to its upstream device. The device configured with IGMP snooping proxying is called an IGMP snooping proxy. It is a host from the perspective of its upstream device. Even though an IGMP snooping proxy is a host from the perspective of its upstream device, the IGMP membership report suppression mechanism for hosts does not affect it. For more information about the IGMP report suppression mechanism for hosts, see "Configuring IGMP." Figure 13 Network diagram IP network IGMP Querier Router A Proxy & Querier Router B Query from Router A Report from Switch A Query from Switch A Report from Host Host A Receiver Host C Receiver Host B As shown in Figure 13, Router B operates as an IGMP snooping proxy. As a host from the perspective of the querier Router A, Router B represents its attached hosts to send membership reports and leave messages to Router A. 16