Troubleshooting Msdp; Msdp Peers Stay In Down State - 3Com S7906E Configuration Manual

(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 router.
If no route is available between the MSDP peers, the TCP connection setup will also fail.
Solution
1) Check that a route is available between the routers. Carry out the display ip routing-table
command to check whether the unicast route between the routers is correct.
2) Check that a unicast route is available between the two routers that will become MSDP peers to
each other.
3) Verify the interface address consistency between the MSDP peers. 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.
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 ?
1-33
? 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