Troubleshooting msdp, Msdp peers stay in down state, Symptom – H3C Technologies H3C S10500 Series Switches User Manual

Page 249: Analysis, Solution, No sa entries in the switch’s sa cache

Advertising
background image

234

(10.110.3.100, 226.1.1.3) 1.1.1.1 ? ? 00:32:53 00:05:07

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 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.

Verify that a route is available between the routers. Use the display ip routing-table command to
determine whether 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.

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.

No SA entries in the switch’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 are filtered out.

That is, no (S, G) entries of the local domain is advertised.

If the import-source command is not executed, the system will advertise all the (S, G) entries of the
local domain. If MSDP fails to send (S, G) entries through SA messages, check whether the

import-source command has been correctly configured.

Solution

1.

Verify that a route is available between the routers. Use the display ip routing-table command to
determine whether 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.

Evaluate the configuration of the import-source command and its acl-number argument and be
sure that ACL rule can filter appropriate (S, G) entries.

Advertising