175
10.110.3.100 226.1.1.2 1.1.1.1 ? ? 00:32:53 00:05:07
10.110.3.100 226.1.1.3 1.1.1.1 ? ? 00:32:53 00:05:07
Troubleshooting MSDP
This section describes common MSDP problems and how to troubleshoot them.
MSDP peers stay in disabled state
Symptom
The configured MSDP peers stay in disabled state.
Solution
To resolve the problem:
1.
Use the
display ip routing-table
command to verify that the unicast route between the routers
is reachable.
2.
Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3.
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.
4.
If the problem persists, contact Hewlett Packard Enterprise Support.
No SA entries exist in the router's SA message cache
Symptom
MSDP fails to send (S, G) entries through SA messages.
Solution
To resolve the problem:
1.
Use the
display ip routing-table
command to verify that the unicast route between the routers
is reachable.
2.
Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3.
Verify the configuration of the
import-source
command and its
ipv4-acl-number
argument, and
make sure the ACL rule filters appropriate (S, G) entries.
4.
If the problem persists, contact Hewlett Packard Enterprise Support.
No exchange of locally registered (S, G) entries between RPs
Symptom
RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP
application.
Solution
To resolve the problem:
1.
Use the
display ip routing-table
command to verify that the unicast route between the routers
is reachable.
2.
Verify that a unicast route is available between the two routers that will establish an MSDP
peering relationship.
