05-17-2007 09:26 AM - edited 03-05-2019 04:08 PM
I am having a problem with multicast streams not flowing and have started troubleshooting.
On one of the routers the stream passes through I did a 'sh ip mroute 239.192.10.1'
and got this output:
ACN-RT7206-CORE#sh ip mroute 239.192.10.1
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,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group
Outgoing interface flags: H - Hardware switched, A - Assert winner
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.192.10.1), 03:55:21/00:02:36, RP 164.72.239.42, flags: SF
Incoming interface: FastEthernet5/0, RPF nbr 164.72.178.1
Outgoing interface list:
GigabitEthernet0/3, Forward/Sparse, 03:55:21/00:02:36
(164.72.100.71, 239.192.10.1), 00:02:51/00:00:38, flags:
Incoming interface: FastEthernet5/0, RPF nbr 164.72.178.1
Outgoing interface list:
GigabitEthernet0/3, Forward/Sparse, 00:02:51/00:02:36
(164.72.245.5, 239.192.10.1), 00:02:58/00:00:31, flags: T
Incoming interface: GigabitEthernet0/3, RPF nbr 0.0.0.0
Outgoing interface list:
FastEthernet5/0, Forward/Sparse, 00:02:58/00:02:30
ACN-RT7206-CORE#
The source of the 239.192.10.1 stream is 164.72.100.71 which shows up in the list. But the other S,G entry that shows up, (164.72.245.5, 239.192.10.1)is showing a router interface, 164.72.245.5, as the source.
ACN-RT7206-CORE#sh run int g0/3
Building configuration...
Current configuration : 271 bytes
!
interface GigabitEthernet0/3
description To ACN-6506B-CD-CR port g1/24
ip address 164.72.245.5 255.255.255.252
ip pim sparse-mode
ip route-cache flow
load-interval 30
duplex full
speed 1000
media-type gbic
negotiation auto
end
Is this possible? What would cause a router interface to be the 'S' in the S,G field?
05-24-2007 05:21 AM
router receiving a source announcement from one peer, will forward it to its other peers. In this way, the source announcements can be flooded throughout a network of peers. When an RP receives a source announcement for a group with local interest, which means that someone has previously sent a (*,G)-join to this RP, it will send (S,G)-join towards the source S, building a SPT from the source in the other domain. Data received on the SPT can then be forwarded as usual.
05-24-2007 05:58 AM
Is this then a temporary, short-lived S,G with a router interface as the source?
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