Filter
Top Products
Troubleshooting Examples: Limitations Troubleshooting PIM-SM
page 16-28 OmniSwitch Troubleshooting Guide September 2005
-> show ip pimsm
Status = enabled,
BSR Address = 192.168.13.1,
BSR Expiry Time = 00h:01m:43s,
CBSR Address = 0.0.0.0,
CBSR Mask Length = 30,
CBSR Priority = 0,
CRP Address = 192.168.12.2,
CRP Hold Time = 150,
CRP Expiry Time = 00h:05m:00s,
CRP Interval = 60,
CRP Priority = 0,
Data Timeout = 210,
Join/Prune Interval = 60,
Max RPs = 32,
Probe Time = 5,
Register Checksum = header,
Register Suppress Timeout = 60
-> show ip pimsm rp-candidate
Group Address RP Address Status
------------------+---------------+--------
227.1.1.1/32 192.168.12.2 enabled
226.1.1.1/32 192.168.12.2 enabled
PIM-SM Limitations
Only one C-RP should be configured per PIM domain. Having multiple C-RPs is not currently supported.
The problem with fragmentation and reassembly of PIM-SM tunneled packets (PIM register-encapsulated
packets fall into this category), is if packets need to be fragmented, it might prevent mcast stream to be
delivered properly. A smaller MTU size would work around this issue.
Upstream Neighbor/Next Hop Debug Commands
Use following debug commands to find an upstream neighbor or to verify next hop.
-> debug ip pimsm rpf 172.100.1.254
Source IP Address = 172.100.1.254,
RPF Vlan = 100,
RPF Neighbor = 172.100.1.254,
RPF Route/Mask = 172.100.1.0/24,
RPF Metric Preference = 1,
RPF Metric = 0
-> debug ip pimsm rp-hash 224.0.0.0
Group Address RP Address
------------------+------------------
224.0.0.0 172.100.1.254