No Sa Entries Exist In The Router's Sa Cache - HP A8800 Configuration Manual
Ip multicast
Hide thumbs
Also See for A8800:
- Installation manual (121 pages) ,
- Command reference manual (153 pages) ,
- Fundamentals command reference (193 pages)
Table of Contents
Advertisement
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.
Use the display ip routing-table command to verify that 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.
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 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 will be filtered
off. Namely, no (S, G) entries of the local domain will be advertised.
If you do not configure 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
correct.
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 that ACL rule can filter appropriate (S, G) entries.
Inter-RP communication faults in Anycast RP application
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 load balancing among the RPs.
An MSDP peer address must be different from the Anycast RP address, and the C-BSR and C-RP must
•
be configured on different devices or interfaces.
218
Advertisement
Table of Contents
Troubleshooting
