No Sa Entries Exist In The Router's Sa Message Cache; No Exchange Of Locally Registered (S, G) Entries Between Rps - HP 6125XLG Ip Multicast Configuration Manual

The TCP connection setup fails 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 fails.
•
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. 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 exist in the router's SA message 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
and no (S, G) entries of the local domain are advertised.
• If you do not use the import-source command, the system advertises all the (S, G) entries of the local
domain. If MSDP fails to send (S, G) entries through SA messages, verify that the import-source
command has been correctly configured.
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.

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