From: Dustin.Yates@ercgroup.com
Date: Fri Mar 28 2003 - 23:18:47 GMT-3
Posted this one over to network professionals connection and got a quick
reply to delete the following from the FA1/0 interface:
ip multicast ttl-threshold 16
After I did that, it worked.
-----Original Message-----
From:
Sent: Friday, March 28, 2003 7:10 PM
To:
Subject: Re: Multicast Config
Your fa1/0 is not listed on the Outgoing interface list: which means that
the
router thinks that no one on that interface is asking for multicast traffic.
Could be your PCs ability to send join message, have you tried plugging your
fa1/0 to a swith with the PC?
Bal
> This should have been straight forward, but.... Here's the hardware:
>
> 6509 (native mode IOS) ---- 4006 (CatOS) --- 3620 --- PC via crossover
cable
>
>
> The 6509 has other 6509's & 4006's hanging off of it with the WAN routers
> tied to those. Mutlicast traffic is running throughout the network and is
> seen on the PCs connected to the 4006 that the 3620 is connected to.
Here's
> the config on the 3620 (the PC is connected to FA1/0) and the "show ip
> mroute 239.192.1.101" for a test stream:
>
> ip multicast-routing
> !
> interface Loopback0
> ip address 1.1.254.1 255.255.255.255
> ip pim sparse-dense-mode
> no ip mroute-cache
> !
> interface FastEthernet0/0
>
> description Connection to 4006
> ip address 1.1.1.1 255.255.252.0
> ip pim sparse-dense-mode
> !
> interface FastEthernet1/0
>
> description Connection to PC
> ip address 1.1.4.1 255.255.255.252
> ip pim sparse-dense-mode
> ip multicast ttl-threshold 16
> !
> router eigrp 1
> network 1 .0.0.0
> no auto-summary
> no eigrp log-neighbor-changes
> !
> ip pim bidir-enable
> ip pim rp-address 1.1.1.1
> ip pim send-rp-announce Loopback0 scope 15
> ip pim send-rp-discovery scope 15
> !
> !
> sh ip mroute 239.192.1.101
> IP Multicast Routing Table
> Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
Connected,
>
> L - Local, P - Pruned, R - RP-bit set, F - Register flag,
> T - SPT-bit set, J - Join SPT, M - MSDP created entry,
> X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
> U - URD, I - Received Source Specific Host Report
> Outgoing interface flags: H - Hardware switched
> Timers: Uptime/Expires
> Interface state: Interface, Next-Hop or VCD, State/Mode
>
> (*, 239.192.1.101), 00:01:32/00:02:59, RP 3.177.200.254, flags: S
> Incoming interface: Null, RPF nbr 0.0.0.0
> Outgoing interface list:
> FastEthernet0/0, Forward/Sparse-Dense, 00:00:55/00:02:34
>
> (3.115.80.220, 239.192.1.101), 00:01:32/00:01:27, flags: PX
> Incoming interface: FastEthernet0/0, RPF nbr 3.177.140.17
> Outgoing interface list: Null
>
> (3.177.36.245, 239.192.1.101), 00:00:39/00:02:59, flags: PTX
> Incoming interface: FastEthernet0/0, RPF nbr 3.177.140.17
> Outgoing interface list: Null
>
> (3.177.137.220, 239.192.1.101), 00:00:12/00:02:47, flags: PX
> Incoming interface: FastEthernet0/0, RPF nbr 3.177.140.17
> Outgoing interface list: Null
>
> When I connect the PC to the 4006 that the 3620 is connected to, I get the
> stream. But, I can't get it across the 3620. Any suggestions?
This archive was generated by hypermail 2.1.4 : Sat Apr 05 2003 - 08:51:46 GMT-3