l Run the display msdp [ vpn-instance vpn-instance-name | all-instance ] sa-cache [ group-
address | source-address | [ 2-byte-as-number | 4-byte-as-number ] ]
*
command to check
SA Cache of the public network instance, VPN instance, or all instances.
----End
Example
Run the display msdp peer-status [ peer-address ] command, and you can view the SA-
Requests field and check whether the configuration is valid. For example:
<Quidway> display msdp peer-status
MSDP Peer 172.40.41.1, AS ?
Description:
Information about connection status:
State: Up
Up/down time: 00:26:41
Resets: 0
Connection interface: Vlanif10 (172.40.41.2)
Number of sent/received messages: 27/28
Number of discarded output messages: 0
Elapsed time since last connection or counters clear: 00:26:56
Information about (Source, Group)-based SA filtering policy:
Import policy: none
Export policy: none
Information about SA-Requests:
Policy to accept SA-Request messages: 2000
Sending SA-Requests status: enable
Minimum TTL to forward SA with encapsulated data: 0
SAs learned from this peer: 0, SA Cache maximum for the peer: none
Input queue size: 0, Output queue size: 0
Counters for MSDP message:
Count of RPF check failure: 0
Incoming/outgoing SA messages: 16/0
Incoming/outgoing SA requests: 0/0
Incoming/outgoing SA responses: 0/0
Incoming/outgoing data packets: 0/0
Peer authentication: configured
Peer authentication type: Key-Chain
7.8 Transmitting Burst Multicast Data Between Domains
By default, an SA message carries only (S, G) information. Then, if burst multicast data need
be transmitted between domains, you can configure multicast data encapsulation for an SA
message on the source RP. In addition, you can set the TTL threshold to limit the transmission
scope of multicast data encapsulated in an SA message.
7.8.1 Establishing the Configuration Task
After PIM-SM inter-domain multicast or anycast RP in a PIM-SM domain is configured, you
can configure the transmission of burst multicast data between domains as required.
Applicable Environment
The time during which certain multicast sources send multicast data is long, and is longer than
the timeout of an (S, G) entry. In this case, the source DR encapsulates multicast data packets
in Register messages one by one, and sends the messages to the source RP. The source RP then
uses SA messages to forward (S, G) entries to the remote RP.
The remote RP then sends a Join message to the source DR. An SPT is thus set up. Because of
the timeout of the (S, G) entry, remote users cannot receive multicast data sent by S.
Quidway S7700 Smart Routing Switch
Configuration Guide - Multicast 7 MSDP Configuration
Issue 01 (2011-07-15) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
246
To Next Page
Loading...
Need help?
General
