Ethernet Routing Switch 8600 Engineering Interconnecting Multiple PIM-SM Domains Using MSDP for ERS 8600 Technical Configuration Guide Avaya Data Solutions Document Date: Document Number: NN48500-582 Document Version: 1.1
2010 Avaya Inc. All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes. Documentation disclaimer Avaya shall not be responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. End User agree to indemnify and hold harmless Avaya, Avaya s agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation, to the extent made by End User. Link disclaimer Avaya is not responsible for the contents or reliability of any linked Web sites referenced within this site or documentation(s) provided by Avaya. Avaya is not responsible for the accuracy of any information, statement or content provided on these sites and does not necessarily endorse the products, services, or information described or offered within them. Avaya does not guarantee that these links will work all the time and has no control over the availability of the linked pages. Warranty Avaya provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language, as well as information regarding support for this product, while under warranty, is available to Avaya customers and other parties through the Avaya Support Web site: http://www.avaya.com/support Please note that if you acquired the product from an authorized reseller, the warranty is provided to you by said reseller and not by Avaya. Licenses THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER (AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE. BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING, DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER REFERRED TO INTERCHANGEABLY AS "YOU" AND "END USER"), AGREE TO THESE TERMS AND CONDITIONS AND CREATE A BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE APPLICABLE AVAYA AFFILIATE ("AVAYA"). Copyright Except where expressly stated otherwise, no use should be made of the Documentation(s) and Product(s) provided by Avaya. All content in this documentation(s) and the product(s) provided by Avaya including the selection, arrangement and design of the content is owned either by Avaya or its licensors and is protected by copyright and other intellectual property laws including the sui generis rights relating to the protection of databases. You may not modify, copy, reproduce, republish, upload, post, transmit or distribute in any way any content, in whole or in part, including any code and software. Unauthorized reproduction, transmission, dissemination, storage, and or use without the express written consent of Avaya can be a criminal, as well as a civil offense under the applicable law. Third Party Components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information regarding distributed Linux OS source code (for those Products that have distributed the Linux OS source code), and identifying the copyright holders of the Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: http://support.avaya.com/copyright. Trademarks The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) provided by Avaya are the registered or unregistered Marks of Avaya, its affiliates, or other third parties. Users are not permitted to use such Marks without prior written consent from Avaya or such third party which may own the Mark. Nothing contained in this site, the documentation(s) and product(s) should be construed as granting, by implication, estoppel, or otherwise, any license or right in and to the Marks without the express written permission of Avaya or the applicable third party. Avaya is a registered trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.com/support. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http:// www.avaya.com/support. for ERS 8600 Technical Configuration Guide 2
Abstract This document covers in detail the application of Inter-domain PIM-SM using Multicast Source Discovery Protocol (MSDP) on the ERS 8600. This allows a multicast receiver in one PIM-SM domain to receive a multicast stream generated by a multicast source in a different domain. A step by step configuration of a sample topology is provided followed by a walk-through of the operation. This TCG applies to the ERS 8600 software release 5.1 Revision Control No Date Version Revised by Remarks 1 06/2009 1.0 CSE Initial version of Interdomain PIM-SM using MSDP application document for ERS 8600 Technical Configuration Guide 3
Table of Contents Document Updates... 5 Conventions... 5 1. Introduction to Interdomain PIM-SM on ERS 8600... 6 1.1 Generating MSDP Source-Active Updates... 6 1.2 Receiving MSDP Source-Active Updates... 6 1.3 MSDP Message Control... 7 2. Network Topology... 7 3. Configuration... 8 3.1 Initial Connectivity... 8 3.2 Inter-AS Routing... 9 3.3 PIM-SM - Intra-AS Multicast... 11 3.4 MSDP - Inter-AS Multicast... 12 4. Operation... 15 4.1 SA Propagation... 15 4.2 Delivering the Multicast Stream... 18 5. Reference Documentation... 21 6. Customer service... 22 6.1 Getting technical documentation... 22 6.2 Getting product training... 22 6.3 Getting help from a distributor or reseller... 22 6.4 Getting technical support from the Avaya Web site... 22 for ERS 8600 Technical Configuration Guide 4
Document Updates Conventions This section describes the text, image, and command conventions used in this document. Symbols: Text: Tip Highlights a configuration or technical tip. Note Highlights important information to the reader. Warning Highlights important information about an action that may result in equipment damage, configuration or data loss. Bold text indicates emphasis. Italic text in a Courier New font indicates text the user must enter or select in a menu item, button or command: ERS5520-48T# show running-config Output examples from Avaya devices are displayed in a Lucinda Console font: ERS5520-48T# show running-config! Embedded ASCII Configuration Generator Script! Model = Ethernet Routing Switch 5520-24T-PWR! Software version = v5.0.0.011 enable configure terminal for ERS 8600 Technical Configuration Guide 5
1. Introduction to Interdomain PIM-SM on ERS 8600 The Multicast Source Discovery Protocol (MSDP) is used for two networking applications. First, it enables the advertisement of multicast source information between different Protocol Independent Multicast Sparse Mode (PIM-SM) domains [1]. Also, MSDP is used within an Autonomous System (AS) to synchronize PIM information between two or more Anycast Rendezvous Points (RPs) to provide RP redundancy [2]. This TCG focuses on the first application. 1.1 Generating MSDP Source-Active Updates MSDP enabled routers form adjacencies, similar in concept to Border Gateway Protocol (BGP), using TCP port 639 in order to advertise and share multicast source information. MSDP routers typically make use of reachability information exchanged via BGP in order to form adjacencies and to perform a Reverse Path Forward check (see below) when receiving multicast source information. When an RP router in the multicast source s PIM domain learns of a new (S,G), via a directly connected source or PIM Register message, it stores this information along with the RP address in its MSDP Source-Active (SA) Local Cache. This RP router then transmits an SA Update message containing (S,G,RP) information to its MSDP peers which propagate the SA to RPs in their local domains and to their MSDP peers in other PIM-SM domains. Note that a PIM-domain refers to a set of routers, typically in a single AS, which use the same RP for a given multicast group. 1.2 Receiving MSDP Source-Active Updates When an RP router in another PIM-SM domain receives the SA it first performs a Reverse Path Forward (RPF) check. The RPF check ensures that the SA is received from the MSDP peer that is closest to the originating RP in order to prevent SA loops. Note that this RPF check is different than the multicast routing RPF check. If the RPF rules pass then the receiving RP router stores the SA information in its SA Foreign Cache and this information is made available to the local PIM-SM domain. Each MSDP peer receives and floods the SA information away from the originating RP and this process is referred to as peer RPF flooding. If the RPF checks fail then the SA is discarded unless the router is configured with a single Implicit Default MSDP peer. The RPF check also helps determine which SA should be stored in the SA Foreign Cache in the event that the router receives the same SA information from multiple MSDP peers. If multiple SAs are received with equal cost then the SA from the MSDP peer with the higher IP address is cached. An MSDP router configured with multiple MSDP peers can designate some or all of them as a Default MSDP peer. In this case only the first configured MSDP Default Peer will accept SAs. If the first configured Default Peer is no longer reachable then SAs received from the second configured Default Peer are accepted and so on. In the case of redundant connections this helps control which received SAs a MSDP router caches. Once the RFP checks are complete the MSDP router determines whether or not there are any local multicast receivers that have requested to join the multicast group advertised in the SA. If a receiver exists then the RP router in the receiver s domain will transmit a PIM Join request to the PIM Designated Router on the multicast source subnet, not to the source domain s RP. As a result the multicast stream is delivered to the multicast receiver using the Shortest Path Tree (SPT). Thus, it is important that there is IP connectivity between the multicast source and receiver s subnets. for ERS 8600 Technical Configuration Guide 6
1.3 MSDP Message Control There are various mechanisms that can be employed for controlling the advertisements of SAs. On the RP that originates the SAs an MSDP Redistribute route policy filter can be applied to control which SAs are advertised to all MSDP peers. Similarly, an SA Filter can be applied to a specific MSDP peer in the inbound and/or outbound directions on any MSDP router. See the configuration section below for more details regarding these filtering techniques. MSDP Mesh Groups can be used to reduce SA flooding, similar to the BGP route reflector concept. When an MSDP enabled router learns a new SA, and it passes the RPF check, it floods it to all other members of the Mesh Group. The receiving routers accept the SA and subsequently only forward it to any non-mesh Group MSDP peers, not to other Mesh Group members. All members of a Mesh Group must be directly connected; thus, this feature is typically used within an AS. An example of Mesh Group within an AS is provided in the Configuration section below. 2. Network Topology The demonstration network consisted of six ERS 8600s running release 5.1 software. There were three Autonomous Systems with the multicast receiver in AS 10 and the multicast source in AS 30. EBGP peering was configured between adjacent ERS 8600s residing in different Autonomous Systems (not shown in diagram). In this case Source-Active information originated in AS 30 and was advertised via MSDP to the RP in AS 20 which relayed the information via MSDP to the RP in AS 10. Note that within AS 20 the SA information is shared with other routers which form a Mesh Group. PIM-SM was enabled on all ERS 8600 interfaces. This is important because the RP in the receiver s domain must be able to join a shortest path tree to the source using standard PIM-SM mechanisms. for ERS 8600 Technical Configuration Guide 7
The Multicast Source transmits streams for three multicast groups however in this example only the SA for (30.30.30.101, 224.1.1.10) was advertised. The other multicast groups were filtered by configuring an outbound SA Filter on 8600-31. The ERS 4500 was configured with a single layer 2 VLAN. IGMP Snooping and IGMP proxy were enabled on this VLAN. 3. Configuration The configuration shown below is using ACLI. The equivalent configuration can be performed using Passport CLI as well as using Java Device Manager (JDM). See the ERS 8600 product documentation for more information [3]. First basic layer 2 and layer 3 configuration was performed. Then EBGP peers and the redistribution of EBGP routes into OSPF was configured. For the multicast configuration, PIM-SM was configured on each ERS 8600. Finally, the MSDP peers, Mesh Groups, and SA Filtering was configured. 3.1 Initial Connectivity The basic layer 2 and layer 3 configuration for 8600-11 is shown below. Similar configuration was performed on the other 8600s in the network. Using ACLI enter configuration mode by typing config term. First, set the name of the 8600: prompt 8600-11 Create the VLANs. Then assign ports, an IP address, and enable OSPF. Note that OSPF is only active on the intra-as VLAN 11 and set to passive on the WAN VLAN 1121. vlan create 11 type port 1 vlan create 1121 type port 1 vlan members add 11 vlan members add 1121 interface vlan 11 ip address 10.11.11.11 255.255.255.0 ip ospf enable interface vlan 1121 ip address 10.11.21.11 255.255.255.0 ip ospf network passive ip ospf enable for ERS 8600 Technical Configuration Guide 8
Configure the Loopback interface which will be used as the RP address, OSPF router-id, and BGP routerid. interface loopback 1 ip address 11.11.11.11/32 ip ospf Configure the 8600 as an OSPF ASBR because EBGP routes will be redistributed into OSPF in the next section. Set the Router Id, and then globally enable OSPF. router ospf router-id 11.11.11.11 as-boundary-router enable router ospf enable Disable Spanning Tree on the routed ports: interface gigabitethernet, no spanning-tree stp 1 enable 3.2 Inter-AS Routing The EBGP sessions are formed between adjacent 8600s residing in different Autonomous Systems in order to exchange network reachability information. It is important to advertise reachability to the loopback interfaces since these are used for MSDP peering. Also, the multicast source s subnet must be reachable so that the shortest path tree can be established by the routers along the path using PIM-SM. The configuration for ERS 8600-11 is shown below. The local AS 10 is first defined. Then the AS 10 networks that need to be advertised to the other ASes are imported into BGP including the loopback interfaces and the receiver subnet. Reachability to the loopback interfaces is required for MSDP peering. An EBGP session to the neighbor 8600-21 is created and enabled. Then BGP is enabled globally. OSPF is configured to redistribute EBGP learned routes into OSPF for redundancy in case one of the EBGP peers in AS 10 is no longer active. The BGP process will automatically use the same Router-Id that was previously configured for OSPF. router bgp 10 router bgp for ERS 8600 Technical Configuration Guide 9
no auto-summary no synchronization network 11.11.11.11/32 network 12.12.12.12/32 network 10.10.10.0/24 neighbor 10.11.21.21 neighbor 10.11.21.21 remote-as 20 neighbor 10.11.21.21 enable router bgp 10 enable router ospf redistribute bgp redistribute bgp enable ERS 8600-12, 8600-21, 8600-22, and 8600-23 were configured similarly to 8600-11. The configuration for ERS 8600-31 consists of 2 EBGP sessions to AS 20. ERS 8600-31 is also in the same AS as the multicast source. Therefore, it is responsible for advertising the 30.30.30.0/24 network. This was achieved by using the network 30.30.30.0/24 command. router bgp 30 router bgp no auto-summary no synchronization network 30.30.30.0/24 network 31.31.31.31/32 neighbor 20.21.31.21 neighbor 20.21.31.21 remote-as 20 neighbor 20.21.31.21 enable neighbor 20.22.31.22 neighbor 20.22.31.22 remote-as 20 for ERS 8600 Technical Configuration Guide 10
neighbor 20.22.31.22 enable router bgp 30 enable 3.3 PIM-SM - Intra-AS Multicast Within each AS the PIM-SM multicasting control protocol is configured. A loopback interface on one of the 8600s in each AS is enabled with PIM and designated as an RP. In this network static-rp configuration s used. PIM-SM is enabled on all VLANs, including the VLANs connecting the ASes. This is required because the RP in the receiver s AS 10 will send a PIM Join towards the multicast source out this interface once it learns the SA, executes the RPF check successfully, and confirms that it has receivers that want to join the multicast stream. Finally, PIM must be enabled globally. The configuration for 8600-11 is shown below. Note that multicast group range 224.1.1.0/24 is mapped to the RP which is the loopback interface on 8600-11. interface loopback 1 ip pim interface vlan 11 ip pim enable interface vlan 1121 ip pim enable ip pim static-rp ip pim static-rp 224.1.1.0/24 11.11.11.11 ip pim enable The configuration for all other ERS 8600s is similar to the configuration for 8600-11. for ERS 8600 Technical Configuration Guide 11
3.4 MSDP - Inter-AS Multicast The MSDP peering is configured between adjacent 8600s using the loopback IP interfaces. The MSDP peers must be configured in such a way to avoid any loops. On 8600-11 there is a single MSDP Peering to the RP in AS 20. Note that the connect-source parameter is used so that the source IP address of MSDP packets is set to the loopback address. ip msdp peer 21.21.21.21 connect-source 11.11.11.11 remote-as 20 ip msdp peer 21.21.21.21 enable ip msdp enable Within AS 20 there are three 8600s that are configured as a Mesh Group. A Mesh Group reduces the number of SAs flooded within an AS and prevents looping of SA information. In this case 8600-21 learns the SA from 8600-31 and advertises it to 8600-22 and 8600-23 which subsequently do not advertise the SA to one another because they are members of the same Mesh Group. Although there are no multicast receivers in AS 20 this configuration illustrates how SA information could be shared amongst redundant RPs within in AS. 8600-21: ip msdp peer 11.11.11.11 connect-source 21.21.21.21 remote-as 10 ip msdp peer 11.11.11.11 enable ip msdp peer 31.31.31.31 connect-source 21.21.21.21 remote-as 30 ip msdp peer 31.31.31.31 enable ip msdp peer 22.22.22.22 connect-source 21.21.21.21 remote-as 20 ip msdp peer 22.22.22.22 enable ip msdp peer 23.23.23.23 connect-source 21.21.21.21 remote-as 20 ip msdp peer 23.23.23.23 enable ip msdp mesh-group group20 23.23.23.23 ip msdp mesh-group group20 22.22.22.22 ip msdp enable 8600-22: ip msdp peer 21.21.21.21 connect-source 22.22.22.22 remote-as 20 ip msdp peer 21.21.21.21 enable ip msdp peer 23.23.23.23 connect-source 22.22.22.22 remote-as 20 ip msdp peer 23.23.23.23 enable for ERS 8600 Technical Configuration Guide 12
ip msdp mesh-group group20 21.21.21.21 ip msdp mesh-group group20 23.23.23.23 ip msdp enable 8600-23: ip msdp peer 21.21.21.21 connect-source 23.23.23.23 remote-as 20 ip msdp peer 21.21.21.21 enable ip msdp peer 22.22.22.22 connect-source 23.23.23.23 remote-as 20 ip msdp peer 22.22.22.22 enable ip msdp mesh-group group20 21.21.21.21 ip msdp mesh-group group20 22.22.22.22 ip msdp enable In AS 30, the Source AS, a single MSDP peer is configured. Once 8600-31 learns of the multicast source via PIM it will generate the SA for the (S,G) and advertise it to 8600-21. In this network the Multicast Source transmits streams for 3 groups: 224.1.1.10-.12. An outbound SA Filter is applied so that only an SA corresponding to the first multicast group 224.1.1.10 is advertised. This involves first creating an Extended ACL which allows both the source IP address and the multicast group addresses to be used as match criteria. Note that Multiple (S,G) entries can be associated with a single Extended ACL. Currently Extended ACLs are only used for MSDP on the ERS 8600. Then a Route-Map is created referencing the Extended ACL as a match criteria using the extendedprefix parameter. By default the action of the Route-Map is permit which is required when filtering specific SAs. If a Route-Map is created with an action of deny then all SAs will be blocked. Finally, the Route-Map is referenced when configuring SA Outbound filtering for the specific MSDP peer. Note that the terms Route-Map and Route-Policy are used interchangeably in ACLI. ip msdp peer 21.21.21.21 connect-source 31.31.31.31 remote-as 20 ip msdp peer 21.21.21.21 enable ip msdp enable ip access-list extended Acl1 30.30.30.101 255.255.255.255 224.1.1.10 255.255.255.255 route-map MsdpAdv10 1 match extended-prefix Acl1 enable ip msdp sa-filter out 21.21.21.21 route-policy MsdpAdv10 for ERS 8600 Technical Configuration Guide 13
Note that SA Filtering can also be achieved by configuring MSDP Redistribution. In this case the term redistribution refers to the which SAs are redistributed to other MSDP peers. MSDP Redistribution is only applicable on the router, i.e. RP, that originates the SAs. It allows the router to filter outbound SAs to all of its MSDP peers as opposed to SA Filtering which is applied to specific MSDP peers in both directions. Similar to SA Filtering, an Extended ACL and Route-Map are initially configured to specify which SA(s) are permitted and then the Route-Map is referenced when configuring MSDP Redistribution. The configuration below is shown as an example of MSDP Redistribution although it was not applied to the demonstration network as SA Filtering was used to achieve the same result. Note that after msdp redistribute is configured it is required to end configuration mode and execute the ip msdp apply redistribute command in privileged mode in order for the Route-Policy to take affect. ip access-list extended Acl1 30.30.30.101 255.255.255.255 224.1.1.10 255.255.255.255 route-map MsdpAdv10 1 match extended-prefix Acl1 enable ip msdp redistribute route-policy MsdpAdv10 end ip msdp apply redistribute for ERS 8600 Technical Configuration Guide 14
4. Operation 4.1 SA Propagation The multicast source in AS 30 is transmitting to three unique group addresses, 224.1.1.10. The PIM mroute table on 8600-31 contains three corresponding entries as shown below. Note that the A Flag is set for each (S,G) indicating that the information has been advertised to the MSDP process. 8600-31:5# show ip pim mroute ================================================================================ PIM Multicast Route - GlobalRouter ================================================================================ Src: 30.30.30.101 Grp: 224.1.1.10 RP: 31.31.31.31 Upstream: NULL Flags: CACHE SG A Incoming Port: Vlan30-4/5, Outgoing Ports: Joined Ports: Pruned Ports: Vlan2131-4/29, Vlan2231-4/30,... ------------------------------------------------------------------------------- Src: 30.30.30.101 Grp: 224.1.1.11 RP: 31.31.31.31 Upstream: NULL Flags: CACHE SG A Incoming Port: Vlan30-4/5, Outgoing Ports: Joined Ports: Pruned Ports:... ------------------------------------------------------------------------------- Src: 30.30.30.101 Grp: 224.1.1.12 RP: 31.31.31.31 Upstream: NULL Flags: CACHE SG A Incoming Port: Vlan30-4/5, Outgoing Ports: Joined Ports: Pruned Ports:... ------------------------------------------------------------------------------- Total Num of Entries Displayed 3/3 Flags Legend: SPT = Shortest path tree, WC=(*,Grp) entry, RP=Rendezvous Point tree, CACHE=Kern el Cache, ASSERTED=Asserted, SG=(Src,Grp) entry, PMBR=(*,*,RP) entry, FWD_TO_RP= Forwarding to RP, FWD_TO_DR=Forwarding to DR, SG_NODATA=SG Due to Join, A=SG Adv for ERS 8600 Technical Configuration Guide 15
ertised to MSDP, M=SG Created by MSDP, CP_TO_CPU=Copy to CPU, STATIC_MROUTE=Stat ic Mroute, MRTF_SMLT_PEER_SG=Peer SG On Non-DR For SMLT As a result the 8600-31 stores these three entries in its SA Local Cache which can be viewed with the following show command: 8600-31:5# show ip msdp sa-cache local MSDP Source-Active Local Cache - 3 entries (30.30.30.101, 224.1.1.10), RP 31.31.31.31 (30.30.30.101, 224.1.1.11), RP 31.31.31.31 (30.30.30.101, 224.1.1.12), RP 31.31.31.31 The SAs are then advertised to all MSDP peers. In this configuration 8600-31 has a single MSDP peer to 8600-21 and an outbound SA Filter was applied such that only 224.1.1.10 was advertised. When 8600-21 receives the SA it stores it in its SA Foreign Cache. This can be viewed using the show ip msdp sa-cache command as shown below. Note the two time stamps at the end of the entry. The first time stamp increments and represents the amount of time the entry has been in the cache. The second time stamp decrements and the time remaining before the cache entry ages out. When 8600-21 receives a periodic SA update this value resets to 6 minutes and 30 seconds (i.e. 390 seconds). 8600-21:5# show ip msdp sa-cache MSDP Source-Active Foreign Cache - 1 entries (30.30.30.101, 224.1.1.10), RP 31.31.31.31, BGP/AS 30, 01:51:10/00:06:19 for ERS 8600 Technical Configuration Guide 16
In this demonstration network the identical SA information was also learned by 8600-22 and 8600-23 since all three routers in AS 20 are members of the same Mesh Group. AS 10 2/43 Multicast Receiver 10.10.10.43 Joins 224.1.1.10 ERS 4500 2/45 4/1 V10 10.10.10.x 8600-11 RP 8600-12 V11 10.11.11.x SA Update V1121 10.11.21.x V1222 10.12.22.x AS 20 AS 30 SA Update 8600-21 RP V20 20.20.20.x 8600-22 4/29 4/30 SA Update 4/29 4/30 V21 20.21.21.x V22 20.22.22.x SA Update 8600-23 V2131 20.21.31.x V2231 20.22.31.x 8600-31 4/29 4/30 RP 4/5 V30 30.30.30.x Multicast Source 30.30.30.101 Group 224.1.1.10 Group 224.1.1.11 Group 224.1.1.12 ERS 8600-21 also propagates the SA information to ERS 8600-11. This is seen in 8600-11 s SA Foreign Cache. This implies that the SA passed RPF checks on 8600-11. 8600-11:6#show ip msdp sa-ca MSDP Source-Active Foreign Cache - 1 entries (30.30.30.101, 224.1.1.10), RP 31.31.31.31, BGP/AS 30, 02:09:08/00:06:04 for ERS 8600 Technical Configuration Guide 17
4.2 Delivering the Multicast Stream Meanwhile, the multicast receiver transmitted a request, via IGMP, to receive the 224.1.1.10 multicast stream. ERS 8600-12 sends a PIM Join message towards the RP in AS 10, 8600-11 s loopback address. Upon receiving the PIM Join message 8600-11 creates a (*,G) in its PIM mroute table. Once it receives the SA message for the Group 224.1.1.10 via MSDP it now knows where the source is located. This triggers 8600-11 to generate a PIM Join message out port towards the source 30.30.30.101/32 which is forwarded via 8600-21 using PIM-SM to 8600-31. Less than one second later the multicast stream is delivered to 8600-11 which forwards it to 8600-12 out port, i.e. the port on which it received the original PIM Join. This flow of this multicast stream is shown in the diagram below: AS 10 2/43 Multicast Receiver 10.10.10.43 Joins 224.1.1.10 ERS 4500 2/45 4/1 V10 10.10.10.x 8600-11 RP 8600-12 V11 10.11.11.x V1121 10.11.21.x V1222 10.12.22.x AS 20 AS 30 8600-21 RP V20 20.20.20.x 8600-22 4/29 4/30 4/29 4/30 V21 20.21.21.x V22 20.22.22.x 8600-23 V2131 20.21.31.x V2231 20.22.31.x 8600-31 4/29 4/30 RP 4/5 V30 30.30.30.x Multicast Source 30.30.30.101 Group 224.1.1.10 Group 224.1.1.11 Group 224.1.1.12 Once ERS 8600-12, the PIM Designated Router on VLAN 10, receives and delivers the first packet of the 224.1.1.10 it transmits a PIM Join out port towards the Source 30.30.30.101/32. This is standard PIM-SM behavior on the ERS 8600 in order to transition from the multicast shared path tree to the shortest path tree. The PIM Join is propagated by 8600-22 via PIM-SM to ERS 8600-31 which now joins port 4/30 to the multicast tree for group 224.1.1.10. At this point 8600-12 receives the multicast stream from both the RP (8600-11), or the shared path tree, and the shortest path tree directly from the source. Up to one minute later the 8600-12 transmits a PIM Prune to 8600-11 indicating that it no longer wants to receive the multicast stream from the RP. This triggers 8600-11 to generate a PIM Prune towards the source to 8600-21 which forwards the PIM Prune to 8600-31. Less than a second later 8600-31 stops transmitting the multicast stream down the shared path tree. ERS 8600-31 continues to forward the multicast stream over the shortest path tree to the receiver as shown in the diagram below: for ERS 8600 Technical Configuration Guide 18
AS 10 AS 20 AS 30 8600-11 RP V1121 10.11.21.x 8600-21 RP 4/29 4/30 V21 20.21.21.x 8600-23 V2131 20.21.31.x 8600-31 4/29 2/43 ERS 4500 V11 10.11.11.x V20 20.20.20.x 4/30 RP 4/5 V30 30.30.30.x Multicast Receiver 10.10.10.43 Joins 224.1.1.10 2/45 4/1 V10 10.10.10.x 8600-12 V1222 10.12.22.x 4/29 4/30 8600-22 V22 20.22.22.x V2231 20.22.31.x Multicast Source 30.30.30.101 Group 224.1.1.10 Group 224.1.1.11 Group 224.1.1.12 This is reflected in the PIM mroute table on 8600-12 which shows that the multicast stream is received on Incoming Port on VLAN 1222 from Upstream neighbor 10.12.22.22 (8600-22). The multicast stream is forwarded to Outgoing Ports 4/1 on VLAN 10. 8600-12:5# show ip pim mroute source 30.30.30.101 group 224.1.1.10 ================================================================================ PIM Multicast Route - GlobalRouter ================================================================================ Src: 30.30.30.101 Grp: 224.1.1.10 RP: 11.11.11.11 Upstream: 10.12.22.22 Flags: SPT CACHE SG Incoming Port: Vlan1222-, Outgoing Ports: Vlan10-4/1, Joined Ports: Pruned Ports: Leaf Ports: Vlan10-4/1,... for ERS 8600 Technical Configuration Guide 19
Similarly, viewing the PIM mroute table on 8600-31 show that the multicast stream is transmitted out VLAN 2231 port 4/30 which connects to 8600-22. Note that VLAN 2131 port 4/29 which connects to 8600-21 was Pruned. 8600-31:5# show ip pim mroute source 30.30.30.101 group 224.1.1.10 ================================================================================ PIM Multicast Route - GlobalRouter ================================================================================ Src: 30.30.30.101 Grp: 224.1.1.10 RP: 31.31.31.31 Upstream: NULL Flags: CACHE SG A Incoming Port: Vlan30-4/5, Outgoing Ports: Vlan2231-4/30, Joined Ports: Vlan2231-4/30, Pruned Ports: Vlan2131-4/29,... for ERS 8600 Technical Configuration Guide 20
5. Reference Documentation Reference # Document Title Publication Number 1 RFC 3618 Multicast Source Discovery Protocol (MSDP) 2 RFC 3446 - Anycast Rendezvous Point (RP) mechanism using Protocol Independent Multicast (PIM) and Multicast Source Discovery Protocol (MSDP) 3 Avaya Ethernet Routing Switch 8600 - Configuration Multicast Source Discovery Protocol, Release: 5.1 NN46205-524 for ERS 8600 Technical Configuration Guide 21
6. Customer service Visit the Avaya Web site to access the complete range of services and support that Avaya provides. Go to www.avaya.com or go to one of the pages listed in the following sections. 6.1 Getting technical documentation To download and print selected technical publications and release notes directly from the Internet, go to www.avaya.com/support. 6.2 Getting product training Ongoing product training is available. For more information or to register, you can access the Web site at www.avaya.com/support. From this Web site, you can locate the Training contacts link on the left-hand navigation pane. 6.3 Getting help from a distributor or reseller If you purchased a service contract for your Avaya product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller for assistance. 6.4 Getting technical support from the Avaya Web site The easiest and most effective way to get technical support for Avaya products is from the Avaya Technical Support Web site at www.avaya.com/support. for ERS 8600 Technical Configuration Guide 22