waris at cisco
Sep 2, 2012, 3:29 AM
Post #6 of 6
(451 views)
Permalink
|
|
Re: ME3600X sends Multicast-Copies out of same Interface
[In reply to]
|
|
Hi Christian,
Below is the reply from the development team. Can you please send me the requested information?
" This is expected behavior.
When the Multicast packet comes it is sent on all the interface which are interested, Here the loopback interface is also interested. When the packet hits the loopback it comes back to the router and the router forwards again.
So all other interface will see the packets twice if the loopback has igmp join.
Can you please send me the following details
1) Configuration on the Loopback.
2) Reason why the customer has a igmp join on the Loopback?
3) How is the customer sending igmp join from Loopback"
Regards,
Waris
-----Original Message-----
From: Christian Meutes [mailto:christian [at] errxtx]
Sent: Friday, August 10, 2012 2:51 AM
To: Waris Sagheer (waris)
Cc: cisco-nsp [at] puck
Subject: Re: [c-nsp] ME3600X sends Multicast-Copies out of same Interface
Hi Waris,
it's 15.2(2)S.
On Aug 7, 2012, at 12:22 PM, Waris Sagheer (waris) <waris [at] cisco> wrote:
> Hi Christian,
> Can you tell me the software release?
>
> Regards,
> Waris
>
>
> -----Original Message-----
> From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Christian Meutes
> Sent: Friday, August 03, 2012 1:37 AM
> To: cisco-nsp [at] puck
> Subject: [c-nsp] ME3600X sends Multicast-Copies out of same Interface
>
> Hi,
>
> when IGMP-joining (ip igmp join-group) interface of ME3600X eg. a Loopback, while other interfaces on same ME are programmed to forward this group, copies are sent out of those interfaces (every incoming Multicast packet for the group is sent out of the same interface twice).
>
> Couldn't find bug for this behavior and don't want to spend too much time in TAC discussions to get told that the usage of such configurations is highly doubtful and a plattform limitation or that it's indeed a bug but gets lowest priority.
>
> Maybe here is chance that just anyone can confirm this and Cisco gets aware of it.
>
> regards
> Christian
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
|
