Troubleshooting MSDP
MSDP peers stay in down state
Symptom
The configured MSDP peers stay in the down state.
Analysis
A TCP connection–based MSDP peering relationship is established between the local interface
•
address and the MSDP peer after the configuration.
The TCP connection setup will fail if the local interface address is not consistent with the MSDP peer
•
address configured on the peer router.
•
If no route is available between the MSDP peers, the TCP connection setup will fail.
Solution
Check that a route is available between the routers. Carry out display ip routing-table to check
1.
whether the unicast route between the routers is correct.
Check that a unicast route is available between the two routers that will become MSDP peers to
2.
each other.
Verify the interface address consistency between the MSDP peers. Use display current-configuration
3.
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 SA cache
Symptom
MSDP fails to send (S, G) entries through SA messages.
Analysis
•
The import-source command controls 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.
If import-source 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
Check that a route is available between the routers. Carry out display ip routing-table to check
1.
whether the unicast route between the routers is correct.
Check that a unicast route is available between the two routers that will become MSDP peers to
2.
each other.
Check configuration of import-source and its acl-number argument and make sure that ACL rule can
3.
filter appropriate (S, G) entries.
192