.jpg "Opportunities, Appliacation, Openings"){kind=small}
.jpg "Hand Job, Blow Job, Job Search, Monster Job"){kind=small}
.jpg "pusat resume, daftar kerja, cari kerja"){kind=small}
.jpg "Project Manager, SOftware Engineer, SAP Consultant"){kind=small}
ip multicast boundary
Hi Feras, I usually put the ip multicast boundary command on my last-hop’s upstream neighbor, in the case we don’t want that last-hop router to get the traffic.
So it would be something like this:
R3========R5— Source 224.1.1.1 I I R1
I would place my boundary on R3 so that R1 doesn’t get that traffic if that’s what you want to do. Hope this helps.
Carlos Campos
—–Original Message—– From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Feras Abunamous (fabunamo) Sent: Tuesday, June 06, 2006 3:06 AM To: ccielab@groupstudy.com Subject: ip multicast boundary
All,
I implemented a multicast lab scenario and I configured the “ip multicast boundary” command. It did not stop it from receiving the multicast ping echo-replys. Even that I configured the access list to match the group. Are there any specifications on where we should place this command?
