Troubleshooting Msdp; Msdp Peers Stay In Down State - HP A5500 SI Switch Series Configuration Manual

MSDP Total Source-Active Cache - 8 entries
MSDP matched 8 entries
(Source, Group)
(10.110.3.100, 225.1.1.0)
(10.110.3.100, 225.1.1.1)
(10.110.3.100, 225.1.1.2)
(10.110.3.100, 225.1.1.3)
(10.110.3.100, 226.1.1.0)
(10.110.3.100, 226.1.1.1)
(10.110.3.100, 226.1.1.2)
(10.110.3.100, 226.1.1.3)
# View the (S, G) entries cached in the SA cache on Switch D.
[SwitchD] display msdp sa-cache
MSDP Source-Active Cache Information of VPN-Instance: public net
MSDP Total Source-Active Cache - 4 entries
MSDP matched 4 entries
(Source, Group)
(10.110.3.100, 226.1.1.0)
(10.110.3.100, 226.1.1.1)
(10.110.3.100, 226.1.1.2)
(10.110.3.100, 226.1.1.3)

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 there is a consistency between the local interface address and
•
the MSDP peer address configured on the switch.
If no route is available between the MSDP peers, the TCP connection setup will also fail.
•
Solution
Verify that a route is available between the devices. Use the display ip routing-table command to
1.
determine whether the unicast route between the devices is correct.
Verify that a unicast route is available between the two devices that will become MSDP peers to
2.
each other.
Verify the interface address consistency between the MSDP peers. Use the display current-
3.
configuration command to verify that the local interface address and the MSDP peer address of the
remote switch are the same.
Origin RP Pro
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
Origin RP Pro
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
1.1.1.1 ?
218
AS Uptime Expires
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
? 02:03:30 00:05:31
AS Uptime Expires
? 00:32:53 00:05:07
? 00:32:53 00:05:07
? 00:32:53 00:05:07
? 00:32:53 00:05:07