BigIron RX Series Configuration Guide 62553-1001810-01Configuring Multicast Source Discovery Protocol (MSDP) 23Designating an interface’s IP address as the RP’s IP addressWhen an RP receives a Source Active message, it checks its PIM Sparse multicast group table forreceivers for the group. If it finds a receiver, the RP sends a Join message for that receiver back tothe RP that originated the Source Active message. The originator RP is identified by its RP address.By default, the IP address included in the RP address field of the SA message is the IP address ofthe originating RP, but an SA message can use the IP address of any interface on the originating RP.(The interface is usually a loopback interface.)To designate an interface’s IP address to be the IP address of the RP, enter commands such as thefollowing.BigIron RX(config)# interface loopback 2BigIron RX(config-lbif-2)# ip address 2.2.1.99/32BigIron RX(config)# router msdpBigIron RX(config-msdp-router)# originator-id loopback 2BigIron RX(config-msdp-router)# exitSyntax: [no] originator-id The originator-id parameter instructs MSDP to use the specified address as the IP address of theRP in an SA message. This address must be the address of the interface used to connect the RP tothe source. There are no default originator-ids.The parameter indicates the type of interface used by the RP. Ethernet, loopback andvirtual routing interfaces (ve) can be used.The parameter specifies the interface number (for example: loopback number, portnumber or virtual routing interface number.)Filtering MSDP source-group pairsYou can filter individual source-group pairs in MSDP Source-Active messages. The filter only barsthe DUT from local processing of the MSDP SAs.• sa-filter in – Filters source-group pairs received in Source-Active messages from an MSDPneighbor.• sa-filter originate – Filters source-group pairs in Source-Active messages in advertisements toan MSDP neighbor.Filtering incoming source-active messagesThe following example configures filters for incoming Source-Active messages from three MSDPneighbors:• For peer 2.2.2.99, all source-group pairs in Source-Active messages from the neighbor arefiltered out (ignored) from local processing of the MSDP SAs.• For peer 2.2.2.97, all source-group pairs except those with 10.x.x.x as the source arepermitted.• For peer 2.2.2.96, all source-group pairs except those associated with RP 2.2.42.3 arepermitted.
