170
Solution
1. Use the display ip routing-table command to verify that the unicast route between the routers is
reachable.
2. Verify that a unicast route is available between the two routers that will become MSDP peers to
each other.
3. Verify the configuration of the import-source command and its acl-number argument, and make
sure the ACL rule filters appropriate (S, G) entries.
4. If the problem persists, contact HP Support.
No exchange of locally registered (S, G) entries between RPs
Symptom
RPs fail to exchange their locally registered (S, G) entries with one another in the Anycast RP application.
Analysis
• In the Anycast RP application, RPs in the same PIM-SM domain are configured to be MSDP peers to
achieve redundancy backup among the RPs.
• An MSDP peer address must be different from the Anycast RP address, and the C-BSR and the C-RP
must be configured on different devices or interfaces.
• If you configure the originating-rp command, MSDP replaces the RP address in the SA messages
with the address of the interface specified in the command.
• When an MSDP peer receives an SA message, it performs an RPF check on the message. If the
MSDP peer finds that the remote RP address is the local RP address, it discards the SA message.
Solution
1. Use the display ip routing-table command to verify that the unicast route between the routers is
reachable.
2. Verify that a unicast route is available between the two routers that will establish an MSDP peering
relationship.
3. Verify the configuration of the originating-rp command. In the Anycast RP application environment,
use the originating-rp command to configure the RP address in the SA messages, which must be
the local interface address.
4. Verify that the C-BSR address is different from the Anycast RP address.
5. If the problem persists, contact HP Support.
To Next Page
Loading...
Need help?
General
