09-23-2009 09:58 PM - edited 03-06-2019 07:51 AM
multicast problem
top:
4506------10.44.1.10
|
10.44.20.10---7604-----7606
|
6509--------10.44.50.35
trouble description:
1) 10.44.50.35 can access 10.44.20.10ï¼
2) 10.44.50.35 can not access 10.44.1.10ã
remark:
1) 10.44.50.35 can ping 10.44.20.10 and 10.44.50.35, router or switch have not access-listã
2) multicast protocol is dense-mode;
3) pim neighbor is okï¼
4) show ip mroute infomationï¼
4506#show ip mroute 234.1.2.3
(10.44.1.10, 234.1.2.3), 00:00:05/00:02:54, flags: PT
Incoming interface: GigabitEthernet3/10, RPF nbr 10.44.222.3, RPF-MFD
Outgoing interface list:
GigabitEthernet3/1, Forward/Dense, 00:00:27/00:02:32 //connect 7606
7606#show ip mroute 234.1.2.3
(10.44.1.10, 234.1.2.3), 00:00:05/00:02:54, flags: PT
Incoming interface: null0, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet5/1, Forward/Dense, 00:00:27/00:02:32 //connect 4506
GigabitEthernet5/2, Forward/Dense, 00:00:27/00:02:32 //connect 7604
GigabitEthernet5/3, Forward/Dense, 00:00:27/00:02:32 //connect 6509
7606#show ip mroute 234.5.6.7
(10.44.20.10, 234.5.6.7), 4w0d/00:02:54, flags: PT
Incoming interface: GigabitEthernet5/2, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
GigabitEthernet5/1, Forward/Dense, 00:02:18/00:00:41
GigabitEthernet5/3, Forward/Dense, 00:02:18/00:00:41
6509#show ip mroute 234.1.2.3
6509#show ip mroute 234.5.6.7
(10.44.20.10, 234.5.6.7), 4w0d/00:02:54, flags: PT
Incoming interface: GigabitEthernet1/1, RPF nbr 0.0.0.0, RPF-MFD //connect 7606
Outgoing interface list:
Vlan10, Forward/Dense, 00:02:18/00:00:41
Vlan100, Forward/Dense, 00:02:18/00:00:41
problemï¼
1) 7606 show ip mroute 234.1.2.3 incoming interface is null0ï¼
2) 6509 have not 234.1.2.3 multicast infomationã
09-24-2009 04:36 AM
Hello Xian,
1) this depends where the source is placed.
group 234.1.2.3 has source 10.44.1.10
group 234.5.6.7 has source 10.44.20.10
if subnet 10.44.1.0 is directly connected to 7606 RPF=0.0.0.0 means that the local node is the source PIM node (= the source is in a connected subnet).
So this shouldn't be a problem if 10.44.1.10 is directly connected on C7606 (in other words if sh ip arp 10.44.1.10 is not empty on C7606)
2) this should depend from the fact C6509 thinks no one is interested in the stream (10.44.1.10, 234.1.2.3) but if so interface gi5/3 shouldn't appear in the oilist for (10.44.1.10, 234.1.2.3) on C7606.
Have you seen if over time sh ip mroute 234.1.2.3 keeps showing interface to C6509 in oilist?
is the PC trying to join to group 234.1.2.3?
what shows sh ip igmp groups on the C6509?
and is the RPF check passed on C6509?
use sh ip rpf 10.44.1.10
for this it should show the interface connected to C7606:gi5/3
Hope to help
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide