Enabling Trace Messages For Igmp And Pim Troubleshooting; Msdp - Avaya 8800 Troubleshooting Manual

Multicast feature troubleshooting
4. Verify that PIM SSM is enabled on the interface and also verify if neighborships are

Enabling trace messages for IGMP and PIM troubleshooting

If the preceding sections do not resolve your issue, use the following procedure to enable trace
messages for further troubleshooting.
Also, see Using PIM debugging commands
commands
1. Run IGMP trace and look for error conditions:
2. Run PIM trace and look for error conditions:

MSDP

This section provides procedures to troubleshoot MSDP. Possible reasons for MSDP failure
are:
• MSDP is not enabled globally.
• Admin status of MSDP peer is not enabled.
• MSDP peer operational state is disabled.
• MSDP peer connection status is not established.
• If a circuitless IP interface is used to configure the peer, the connect-source must be
configured for that peer. Otherwise, the peer cannot be established.
• MD5 password configuration mismatch.
• MSDP peer is not reachable through the routing table.
Possible reason for MSDP SAs not being received and advertised:
• no active RPs
• no source reachability
• no RP reachability
378 Troubleshooting
show ip pim (ACLI)
established.
show ip pim interface (CLI or ACLI)
on page 232 for information on additional PIM debugging commands.
trace level 23 <1-4> trace scr on (CLI or ACLI)
trace level 48 <1-4> trace level 27 <1-4> trace screen on (CLI
or ACLI)
Comments? infodev@avaya.com
on page 143 and Using PIM debugging
July 2013