244
• 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, 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 be 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.
• If the originating-rp command is executed, MSDP will replace 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 RPF check on the message. If the MSDP
peer finds that the remote RP address is the same as the local RP address, it will discard the SA
message.
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 peer to
each other.
3. Verify the configuration of the originating-rp command. In the Anycast RP application environment,
be sure to 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.
To Next Page
Loading...
Need help?
General