H3C Technologies H3C S12500 Series Switches - Manual (Page 212)

196
is different from the actual RP address must be designated for SA messages so that the messages can
pass the RPF check.
To configure the SA message content:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter public network MSDP view or
VPN instance MSDP view. msdp [ vpn-instance
vpn-instance-name ]
N/A
3. Enable encapsulation of multicast
data in SA messages.
encap-data-enable
Optional.
Disabled by default.
4. Configure the interface address as
the RP address in SA messages. originating-rp interface-type
interface-number Optional.
PIM RP address by default.
Configuring SA request messages
IMPORTANT:
Before you can enable the device to send SA requests, be sure to disable the SA message cache
mechanism.
By default, after receiving a new join message, a switch does not send an SA request message to any
MSDP peer. Instead, it waits for the next SA message from its MSDP peer. This will cause the receiver to
delay obtaining multicast source information. To enable a new receiver to get the active multicast source
information as early as possible, you can configure switches to send SA request messages to the
designated MSDP peers after receiving a join message of a new receiver.
To configure SA message transmission and filtering:
Step Command Remarks
1. Enter system view. system-view N/A
2. Enter public network MSDP view
or VPN instance MSDP view.
msdp [ vpn-instance
vpn-instance-name ]
N/A
3. Enable the device to send SA
request messages. peer peer-address
request-sa-enable Optional.
Disabled by default.
4. Configure a filtering rule for SA
request messages.
peer peer-address
sa-request-policy [ acl
acl-number ]
Optional.
SA request messages are not
filtered by default.
Configuring SA message filtering rules
By configuring an SA message creation rule, you can enable the switch to filter the (S, G) entries to be
advertised when creating an SA message, so that the propagation of messages of multicast sources is
controlled.