Troubleshooting MSDP 697
[SwitchD] display pim routing-table
Total 1 (*, G) entry; 1 (S, G) entry
(*, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: WC
UpTime: 00:12:07
Upstream interface: Register
Upstream neighbor: NULL
RPF prime neighbor: NULL
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
Protocol: igmp, UpTime: 00:12:07, Expires: -
(10.110.6.100, 225.1.1.1)
RP: 10.1.1.1 (local)
Protocol: pim-sm, Flag: SPT 2MSDP ACT
UpTime: 00:40:22
Upstream interface: Vlan-interface104
Upstream neighbor: 10.110.4.2
RPF prime neighbor: 10.110.4.2
Downstream interface(s) information:
Total number of downstreams: 1
1: Vlan-interface200
Protocol: pim-sm, UpTime: - , Expires: -
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.
To Next Page
Loading...
