Configuring Originating Rp; Configuring Sa Caching State - 3Com 8800 Configuration Manual

3Com Switch 8800 Configuration Guide
rp-policy parameter are configured, any peer that receives an SA message will
forward it to the other peers.
Not using the rp-policy parameter universally: According to the configuration
sequence, only the first static RPF peer whose connection state is UP is activated.
All SA messages from the peer will be received and those from other static RPF
peers will be discarded. Once the activated static RPF peer turns invalid (possibly
out of configuration removed or connection interrupted), the following first static
RPF peer with UP connection state according to the configuration sequence will
assume its role.

30.2.4 Configuring Originating RP

During the creation of SA message, an MSDP peer can be configured to use the IP
address of a specified interface as the RP address in its SA message.
Please perform the following configurations in MSDP view.
Table 30-4 Configuring Originating RP
Configure an MSDP peer to use the IP address of
a specified interface as the RP address of its SA
message
Remove the above operation
By default, the RP address in SA message is the one configured by PIM.

30.2.5 Configuring SA Caching State

When SA messages are cached on a router, the new join-in groups can directly access
all the active sources and join to the corresponding source tree, instead of waiting for
the arrival of the next SA message.
Please perform the following configurations in MSDP view.
Table 30-5 Configuring SA caching state
Configure SA caching state
Disable SA caching state
By default, the router caches the SA state, or rather the (S, G) entry when receiving an
SA message.
Some memory is consumed as the join delay of groups is shortened by this
configuration.
Operation
Operation
30-6
Chapter 30 MSDP Configuration
Command
originating-rp
interface-number
undo originating-rp
Command
cache-sa-enable
undo cache-sa-enable
interface-type