Msdp Peers Stay In Disabled State; No Sa Entries Exist In The Router's Sa Message Cache - HP FlexFabric 5950 series Configuration Manual

MSDP peers stay in disabled state

Symptom
The configured MSDP peers stay in disabled state.
Analysis
Possible reasons for the problem might include the following:
•
A TCP connection-based MSDP peering relationship is established between the local interface
address and the MSDP peer.
•
The TCP connection setup fails 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 fails.
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.
Analysis
Possible reasons for the problem might include the following:
•
The import-source command controls sending (S, G) entries through SA messages to MSDP
peers. If this command is executed without the ipv4-acl-number argument, all the (S, G) entries
are filtered out, and no (S, G) entries of the local domain are advertised.
•
If you do not use the import-source command, the system advertises all the (S, G) entries of
the local domain. If MSDP fails to send (S, G) entries through SA messages, verify that
the import-source command has been correctly configured.
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.
201