Configuration Guide User guide

FastIron Configuration Guide 1567
53-1002494-02
Multicast Source Discovery Protocol (MSDP)
The route-map <map-tag> parameter specifies a route map. The Layer 3 switch applies the filter to
source-group pairs that match the route map. Use the match ip address <acl-id> command in the
route map to specify an extended ACL that contains the source and group addresses.
NOTE
The default filter action is deny. If you want to permit some source-group pairs, use a route map. A
permit action in the route map allows the Layer 3 switch to receive the matching source-group pairs.
A deny action in the route map drops the matching source-group pairs.
MSDP mesh groups
A PIM Sparse domain can have several RPs that are connected to each other to form an MSDP
mesh group. To qualify as a mesh group, the RPs have to be fully meshed; that is, each RP must be
connected to all peer RPs in a domain. (See Figure 177.)
A mesh group reduces the forwarding of SA messages within a domain. Instead of having every RP
in a domain forward SA messages to all the RPs within that domain, only one RP forwards the SA
message. Since an MSDP mesh group is fully meshed, peers do not forward SA messages received
in a domain from one member to every member of the group. The RP that originated the SA or the
first RP in a domain that receives the SA message is the only one that can forward the message to
the members of a mesh group. An RP can forward an SA message to any MSRP router as long as
that peer is farther away from the originating RP than the current MSRP router.
Figure 177 shows an example of an MSDP mesh group. In a PIM-SM mesh group the RPs are
configured to be peers of each other. They can also be peers of RPs in other domains.
Configuring an MSDP mesh group
To configure an MSDP mesh group, enter commands such as the following on each device that will
be included in the mesh group:
Brocade(config)# router msdp
Brocade(config-msdp-router)# msdp-peer 1.1.3.1 connect-source loopback 1
Brocade(config-msdp-router)# msdp-peer 1.1.4.1 connect-source loopback 1
Brocade(config-msdp-router)# msdp-peer 1.1.2.1 connect-source loopback 1
Brocade(config-msdp-router)# msdp-peer 17.17.17.7
Brocade(config-msdp-router)# mesh-group 1234 1.1.4.1
Brocade(config-msdp-router)# mesh-group 1234 1.1.3.1
Brocade(config-msdp-router)# mesh-group 1234 1.1.2.1
Brocade(config-msdp-router)# exit
Syntax: [no] mesh-group <group-name> <peer-address>
The example configuration above reflects the configuration in Figure 177. On RP 1.1.1.1, you
specify its peers within the same domain (1.1.3.1, 1.1.4.1, and 1.1.2.1).
You first configure the MSDP peers using the msdp-peer command to assign their IP addresses
and the loopback interfaces. This information will be used as the source for sessions with the
neighbor.
Next, place the MSDP peers within a domain into a mesh group. Use the mesh-group command.
There are no default mesh groups.
The group-name parameter identifies the group. Enter up to 31 characters for group-name. You can
have up to 4 mesh groups within a multicast network. Each mesh group can include up to 32 peers.