Msdp Peer Not Established; Msdp Peer Established, But No Msdp Local Cache And Foreign Cache Entries - Avaya 8800 Troubleshooting Manual

• originator ID not configured on RP switch
• RPF check failure
See the following sections to troubleshoot a specific MSDP issue:
•

MSDP peer not established

•

MSDP peer established, but no MSDP local cache and foreign cache entries

379
MSDP peer not established
If the MSDP peer is not established, perform the following procedure.
Procedure steps
1. To verify if MSDP functionality is enabled globally, enter the following command
2. To verify if the peer admin status is enabled, enter the following command using
MSDP peer established, but no MSDP local cache and foreign cache
entries
If the MSDP peer is established, but no MSDP local or foreign cache entries are present,
perform the following procedure.
Procedure steps
1. To verify the local cache entries, enter the following command using the CLI or ACLI:
Troubleshooting
using the CLI or ACLI:
show ip msdp summary
From the command output, you can also verify if the MSDP Peer state is
established. If not, perform the following step.
the CLI or ACLI:
show ip msdp peer <peer-address>
If the MSDP interface uses circuitless IP, you can also verify the connect-source
configuration from this command output. With circuitless IP interfaces, you must
configure the connect-source for proper MSDP peer establishment.
on page 379
MSDP
on page
July 2013 379