Re: Multicast Routing Table Woes posted 04/15/2008
- Subject: Re: Multicast Routing Table Woes
- From: "Sadiq Yakasai" <sadiqtanko@xxxxxxxxx>
- Date: Tue, 15 Apr 2008 15:45:03 +0100
- Cc: "Matt Bentley" <mattdbentley@xxxxxxxxx>, ccielab@xxxxxxxxxxxxxx
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=7TVUbd9OlLRGO0rgCcrZSQUtgJcJL9vNcn19AANWY2w=; b=seJgEHo4HCknoKa2f4y2Yr+kVeGjqkqxtssfumZNULTsztZ3zMRWQgnbutcL9BLc1hNBhbsD/TvRh/ToLmm6nr6i7UiLzetWrlx3fUb3ZspXNT4LbRm5XzibNzBD4rvACWpFur1vIdXscX4sJvoxgweBNLgZICxcHAVMWyMXPuY=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Tf3EBfElcHP65l6uFB7DVt1oawwv6zx7Z1uQuuPVthOHZiNOicYKCJmaZZ78bzeD39TPtNftPqLbxzKub3UCs10Vo6Z2pG2GN+yhDH3qlr88n+kdT/hSLRI6KX1cHZImr2ITAxSddCvosR+XwlmGLTaljxB1h+oWs6sh9GWDl9M=
- In-reply-to: <001901c89f05$ce050ef0$0200a8c0@Office>
- References: <email@example.com> <001901c89f05$ce050ef0$0200a8c0@Office>
Just to add a little to what you keep an eye out for Matt, "debug ip
pim" would be another resourceful debug to run when you are running
PIM. The FLAGS. I cannot over emphasize the importance of
understanding all the Flags. It always points you to a right direction
when troubleshooting an mrouting issue.
As for the mroute table:
(*, 18.104.22.168), 00:22:48/stopped, RP 22.214.171.124, flags: SJCLF
Incoming interface: FastEthernet0/3, RPF nbr 126.96.36.199
Outgoing interface list:
FastEthernet0/2, Forward/Sparse, 00:19:41/00:03:16, H
This entry tells you this router knows about the Group (188.8.131.52). It
knows how to get to it (Incoming Interface, F0/3) and has someone
already joined this group downstream (Outgoing Interface List, F0/2).
(184.108.40.206, 220.127.116.11), 00:00:06/00:02:53, flags: LFT
Incoming interface: FastEthernet0/1, RPF nbr 0.0.0.0, Registering
Outgoing interface list:
FastEthernet0/2, Forward/Sparse, 00:00:06/00:02:53, H
This entry tells you someone has already pushed traffic for the group.
And the mcast traffic is from 18.104.22.168, coming in through F0/1 and
going towards someone who is listening for the group, having joined
the group ealier, via F0/2.
Anyways, keep doing it over and over and over again, and it will all
makes sense eventually. One thing at a time.