I am seeing currently seeing an issue where multicast traffic is not reaching client boxes at a particular location. When I check the first router upstream from the client everything looks normal with the joins, but the multicast isn't getting that far.
(*, 239.1.1.1), 2d16h/00:02:53, RP 0.0.0.0, flags: DC
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
GigabitEthernet2/0, Forward/Sparse-Dense, 2d16h/00:00:00
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
239.1.1.1 GigabitEthernet0/0/0.605 2d16h 00:02:54 10.11.50.50
The traffic is getting dropped on the router upstream from the one shown above. I can see they get dropped as "Other drops"...however, the OIF is not null, and there is no rate-limiting...so for what other reasons would they get dropped?
sh ip mroute 239.1.1.1:
(10.5.250.50, 239.1.1.1), 00:01:18/00:01:41, flags:
Incoming interface: POS2/0, RPF nbr 192.168.1.9, Mroute
Outgoing interface list:
GigabitEthernet6/0, Forward/Sparse-Dense, 00:01:18/00:00:00
sh ip mroute 239.1.1.1 count:
Group: 239.1.1.1, Source count: 1, Group pkt count: 0
Source: 10.5.250.50/32, Forwarding: 0/0/0/0, Other: 2493/40/2453
Furthermore, when I send multicast from another source in the same subnet, to the same client box, it is succssful.
Group: 239.1.1.1, Source count: 2, Group pkt count: 3
Source: 10.5.250.70/32, Forwarding: 3/1/32/0, Other: 4/1/0
Source: 10.5.250.50/32, Forwarding: 0/0/0/0, Other: 3142/101/3041
One thing that I did notice is that the TTL is too low on the one that is dropping. The application sending the multicast needs to bump the TTL up by 1. However, I would not expect the traffic to get dropped on this router. The traffic I think should get forwarded to the next router, where the TTL would then be 1, and get dropped there. I'm going to bump up the TTL by 1 tonight, but was really just curious as to why it was being dropped like this.
