Dell Brocade DCX, Configuration Manual

Page: 697 / 1436

BigIron RX Series Configuration Guide 625
53-1001810-01
Configuring Multicast Source Discovery Protocol (MSDP)
23
Designating an interface’s IP address as the RP’s IP address
When an RP receives a Source Active message, it checks its PIM Sparse multicast group table for
receivers for the group. If it finds a receiver, the RP sends a Join message for that receiver back to
the 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 of
the 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 the
following.
BigIron RX(config)# interface loopback 2
BigIron RX(config-lbif-2)# ip address 2.2.1.99/32
BigIron RX(config)# router msdp
BigIron RX(config-msdp-router)# originator-id loopback 2
BigIron RX(config-msdp-router)# exit
Syntax: [no] originator-id <type> <number>
The originator-id parameter instructs MSDP to use the specified address as the IP address of the
RP in an SA message. This address must be the address of the interface used to connect the RP to
the source. There are no default originator-ids.
The <type> parameter indicates the type of interface used by the RP. Ethernet, loopback and
virtual routing interfaces (ve) can be used.
The <number> parameter specifies the interface number (for example: loopback number, port
number or virtual routing interface number.)
Filtering MSDP source-group pairs
You can filter individual source-group pairs in MSDP Source-Active messages. The filter only bars
the DUT from local processing of the MSDP SAs.
•
sa-filter in – Filters source-group pairs received in Source-Active messages from an MSDP
neighbor.
•
sa-filter originate – Filters source-group pairs in Source-Active messages in advertisements to
an MSDP neighbor.
Filtering incoming source-active messages
The following example configures filters for incoming Source-Active messages from three MSDP
neighbors:
•
For peer 2.2.2.99, all source-group pairs in Source-Active messages from the neighbor are
filtered 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 are
permitted.
•
For peer 2.2.2.96, all source-group pairs except those associated with RP 2.2.42.3 are
permitted.