Avaya 8800 Troubleshooting Manual page 380

Multicast feature troubleshooting
2. If no local cache entries exist, to check for PIM mroute entries, enter the following
3. To check the foreign-cache entries at the receiver, enter the following command
4. If no foreign-cache entries exist, to check whether the RP address is the same as
5. If the MSDP peer is not the RPF peer, you must configure the originator ID. To check
6. PING the source and the RP to check for their reachability. If either is not reachable,
7. To view the RPF-check for a particular source, group, and RP, enter the following
8. To display the number of sources and groups that originated in MSDP source-active
9. To display the configured mesh groups, enter the following command using the CLI
380 Troubleshooting
show ip msdp sa-cache local
command using the CLI or ACLI:
show ip pim mroute
Check whether the A flag is set in the PIM mroute entries. If the A flag is not set,
this indicates that PIM has not provided mroute entries to MSDP. Only when PIM
advertises to MSDP can you see MSDP local cache entries.
using the CLI or ACLI:
show ip msdp sa-cache
the MSDP peer address, enter the following CLI command:
show ip msdp rpf-peer <rp-address>
OR
enter the following ACLI command:
show ip msdp rpf <rp-address>
the originator ID configuration, enter the following command using the CLI or ACLI:
show ip msdp summary
configure a static or dynamic route for source and RP reachability.
command using the CLI or ACLI:
show ip msdp sa-check source <source-address> group <group-
address> rp <rp-address> [peer <peer-address>]
This check fails if there is an RPF mismatch, which can happen if the configured
originator ID is not the same as the MSDP peer (therefore, SAs are not
accepted).
messages and the number of source-active messages from an MSDP peer in the
source-active cache, enter the following command using the CLI or ACLI:
show ip msdp count
or ACLI:
show ip msdp mesh-group
Comments? infodev@avaya.com
July 2013