HP VPN Firewall Appliances Network Management Configuration Guide

672
(10.110.3.100, 226.1.1.0) 1.1.1.1 ? ? 00:32:53 00:05:07
(10.110.3.100, 226.1.1.1) 1.1.1.1 ? ? 00:32:53 00:05:07
(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 down state
Symptom
The configured MSDP peers stay in 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
1. Use the display ip routing-table command to verify that the unicast route between the routers is
correct.
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.
No SA entries exist in the router's 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 you do not configure 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
1. Use the display ip routing-table command to verify that the unicast route between the routers is
correct.