Netgear XCM8810 - 8800 SERIES 10-SLOT CHASSIS SWITCH ユーザーズマニュアル

no longer available it informs MSDP, which in turn removes the SA information from the local 
database.

Caching makes it easy for local receivers to know immediately about inter-domain multicast 
sources and to initiate building a source tree towards the source. However, maintaining a 
cache is heavy both in CPU processing and memory requirements. 

Our implementation of MSDP does not support operating with local 

cache disabled.

To remove an SA cache server, use the following command:

unconfigure msdp sa-cache-server {vr <vrname>}

As MSDP uses the flood-and-join model to propagate information about sources, there is a 
restriction that no more than two advertisements per cache entry will be forwarded per 
advertisement interval. This is helpful in reducing an SA message storm and unnecessarily 
forwarding them to peers. 

By default, the router does not send SA request messages to its MSDP peers when a new 
member joins a group and wants to receive multicast traffic. The new member simply waits to 
receive SA messages, which eventually arrive. 

To configure the MSDP router to send SA request messages immediately to the MSDP peer 
when a new member becomes active in a group, use the following command:

configure msdp sa-cache-server <remoteaddr> {vr <vrname>}

To purge all SA cache entries, use the following command:

clear msdp sa-cache {{peer} <remoteaddr> | peer all} {group-address <grp-addr>} 

{vr <vrname>}

To display the SA cache database, use the following command:

show msdp [sa-cache | rejected-sa-cache] {group-address <grp-addr>} 

{source-address <src-addr>} {as-number <as-num>} {originator-rp 

<originator-rp-addr>} {local} {peer <remoteaddr>} {vr <vrname>}

Maximum SA Cache Entry Limit

You can configure a limit on the maximum number of SA cache entries that can be stored in 
the cache database. Once the number of SA cache entries exceeds the pre-configured limit, 
any newly received cache entries are discarded. You can configure the limit on a per-peer 
basis. By default, no SA message limit is set. The router can receive an unlimited number of 
SA entries from an MSDP peer. 

To configure a limit on the number of SA entries that can be stored in cache, use the following 
command:

configure msdp peer [<remoteaddr> | all] sa-limit <max-sa> {vr <vrname>}