H3C Technologies H3C S7500E Series Switches - Manual (Page 233)

7-32
Analysis
z A TCP connection–based MSDP peering relationship is established between the local interface
address and the MSDP peer after the configuration.
z The TCP connection setup will fail if there is a consistency between the local interface address
and the MSDP peer address configured on the router.
z If no route is available between the MSDP peers, the TCP connection setup will also fail.
Solution
1) Check that a route is available between the routers. Carry out the display ip routing-table
command to check whether the unicast route between the routers is correct.
2) Check that a unicast route is available between the two routers that will become MSDP peers to
each other.
3) Verify the interface address consistency between the MSDP peers. Use the display
current-configuration command to verify that the local interface address and the MSDP peer
address of the remote router are the same.
No SA Entries in the Router’s SA Cache
Symptom
MSDP fails to send (S, G) entries through SA messages.
Analysis
z The import-source command is used to control sending (S, G) entries through SA messages to
MSDP peers. If this command is executed without the acl-number argument, all the (S, G) entries
will be filtered off, namely no (S, G) entries of the local domain will be advertised.
z If the import-source command is not executed, the system will advertise all the (S, G) entries of
the local domain. If MSDP fails to send (S, G) entries through SA messages, check whether the
import-source command has been correctly configured.
Solution
1) Check that a route is available between the routers. Carry out the display ip routing-table
command to check whether the unicast route between the routers is correct.
2) Check that a unicast route is available between the two routers that will become MSDP peers to
each other.
3) Check configuration of the import-source command and its acl-number argument and make sure
that ACL rule can filter appropriate (S, G) entries.
Inter-RP Communication Faults in Anycast RP Application
Symptom
RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP
application.
Analysis
z In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP
peers to achieve load balancing among the RPs.
z An MSDP peer address must be different from the anycast RP address, and the C-BSR and
C-RP must be configured on different devices or interfaces.