1-15
Follow these steps to configure a filtering rule for receiving or forwarding SA messages:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter public instance MSDP
view or VPN instance MSDP
view
msdp
[
vpn-instance
vpn-instance-name
]
—
Configure an SA message
creation rule
import-source
[
acl
acl-number
]
Required
No restrictions on (S, G) entries
by default
Configure a filtering rule for
receiving or forwarding SA
messages
peer peer-address sa-policy
{
import
|
export
} [
acl
acl-number
]
Required
No filtering rule by default
Configure the TTL threshold for
multicast data packet
encapsulation in SA messages
peer peer-address
minimum-ttl
ttl-value
Optional
0 by default
Configuring the SA Cache Mechanism
To reduce the time spent in obtaining the multicast information, you can enable the SA cache
mechanism to cache (S, G) entries contained in SA messages locally on the router. However, the more
(S, G) entries are cached, the larger memory space of the router is used.
With the SA cache mechanism enabled, when receiving a new (*, G) join message, the router searches
its SA cache first:
z
If the corresponding (S, G) entry does not exist in the cache, the router waits for the SA message its
MSDP peer will send in the next cycle;
z
If the corresponding (S, G) entry exists in the cache, the router joins the corresponding SPT rooted
at S.
To protect the router effectively against denial of service (DoS) attacks, you can set a limit on the
number of (S, G) entries the router can cache.
Follow these steps to configure the SA message cache:
To do...
Use the command...
Remarks
Enter system view
system-view
—
Enter public instance MSDP view or
VPN instance MSDP view
msdp
[
vpn-instance
vpn-instance-name
]
—
Enable the SA cache mechanism
cache-sa-enable
Optional
Enabled by default
Configure the maximum number of (S,
G) entries learned from the specified
MSDP peer that the router can cache
peer peer-address
sa-cache-maximum
sa-limit
Optional
8192 by default
Summary of Contents for S7906E - Switch
Page 82: ...1 4 DeviceA interface tunnel 1 DeviceA Tunnel1 service loopback group 1...
Page 200: ...1 11 DeviceB display vlan dynamic No dynamic vlans exist...
Page 598: ...ii...
Page 1757: ...4 9...
Page 1770: ...6 4...
Page 2017: ...2 11 Figure 2 3 SFTP client interface...
Page 2238: ...1 16 DeviceA cfd linktrace service instance 1 mep 1001 target mep 4002...