For Multicast to work 100& you do need your Unicast routing protcol to work first. So make sure all subnet's etc are pingable after you "enabled" them for pim.<br><br>But yes foundry code is bugged to some extent with multicast. I would make sure you run at least 3.8 or newer.<br>
<br>Regards Andreas<br><br><div class="gmail_quote">On Tue, Feb 24, 2009 at 6:45 PM, debbie fligor <span dir="ltr"><<a href="mailto:fligor@illinois.edu">fligor@illinois.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
<br>
On Feb 24, 2009, at 11:10, Kenneth Hellmann wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Good feedback Debbie, but I have to remind everyone that this isn't magic.<br>
Everything happens for a reason, and throwing out every config config line<br>
in the book and hoping that something sticks isn't the correct way to<br>
proceed.<br>
</blockquote>
<br></div>
Absolutely right Ken. I wrote that longer example before the config had been posted with no idea what he'd set or not set yet.<div class="im"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Bjorn,<br>
<br>
The reason that your original config worked is because both ports were on<br>
the same vlan. Even though they had separate ip addresses, they were both on<br>
vlan 1. Because they were on the same vlan and you had ip multicast active,<br>
igmp would allow the join.<br>
<br>
When you changed the vlan to 13, they were not on the same vlan, and since<br>
pim wasn't configured on the ve, there was no multicast routing protocol to<br>
route from one subnet to the other.<br>
</blockquote>
<br></div>
sorry about that Bjorn, we usually use "route-only" in devices where we put IP addresses on physical interfaces, and so that was how I was thinking about it. we very seldom put IP addresses directly on ports, we do almost everything with VEs. I think Ken has pegged your problem.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
If you want to send a multicast from one subnet to another, simply enable<br>
pim on both subnets.<br>
</blockquote>
<br></div>
That will work while everything is in box A, but if he wants it to work between interfaces in box A and box B as he asked originally, I think he'll still need to get OSPF on some more interfaces or things wont go.<div class="im">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
It is not magic. And Foundry doesn't do it any differently from anyone else.<br>
</blockquote>
<br></div>
We're constantly being told by Foundry that we can do certain things only on routed ports, not on VEs, so there are some things that can be different. I think you're right though, this isn't one of them.<div>
<div></div><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Ken<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:foundry-nsp-bounces@puck.nether.net" target="_blank">foundry-nsp-bounces@puck.nether.net</a><br>
[mailto:<a href="mailto:foundry-nsp-bounces@puck.nether.net" target="_blank">foundry-nsp-bounces@puck.nether.net</a>] On Behalf Of debbie fligor<br>
Sent: Wednesday, February 25, 2009 1:03 AM<br>
To: <a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
Subject: [f-nsp] Fwd: Multicasting config example?<br>
<br>
I hadn't meant to take this off list. In case someone else is<br>
following along and having fun with multicast on the MLXs, here's what<br>
I sent yesterday.<br>
<br>
Begin forwarded message:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
From: debbie fligor <<a href="mailto:fligor@illinois.edu" target="_blank">fligor@illinois.edu</a>><br>
Date: February 23, 2009 15:09:06 CST<br>
To: Bjørn Skovlund Rydén <<a href="mailto:BSR@fullrate.dk" target="_blank">BSR@fullrate.dk</a>><br>
Cc: debbie fligor <<a href="mailto:fligor@illinois.edu" target="_blank">fligor@illinois.edu</a>><br>
Subject: Re: [f-nsp] Multicasting config example?<br>
<br>
For multicast between subnets to work you need more info than you'll<br>
find in the MLX config guides (IMO).<br>
<br>
Some of this you might have done, but here's the steps:<br>
<br>
globally enable ip multicast-routing. reboot even if it doesn't<br>
tell you to. turn on pim routing<br>
<br>
tell pim routing to use your favorite mix of routes in what order.<br>
we do multicast specific, unicast specific, multicast default, and<br>
unicast default, in that order. our default leaves campus though,<br>
and multicast leaves in a different path than unicast does. If your<br>
multicast and unicast networks are identical, it's not too important<br>
which order is setup.<br>
<br>
Pick an IP address to be your RP. preferably one on a loopback so<br>
it's not tied to a specific subnet or device. set that to be the RP<br>
candidate on the MLX it's configured on. Tell all the MLXs that is<br>
the RP address. you can use BSR, but best practice is currently to<br>
hard code it and not use BSR.<br>
<br>
Then make sure you've got ip pim-sparse set on the ve for the vlan,<br>
as well as the routed interface and the loopback that is the RP and<br>
all the routing links between the two boxes.<br>
<br>
<br>
so for the device that's the RP here's an example bit of config:<br>
<br>
<br>
ip multicast-routing<br>
<br>
router pim<br>
route-precedence mc-non-default uc-non-default mc-default uc-default<br>
<br>
interface loopback 2<br>
port-name RP for on-campus<br>
ip ospf area 0<br>
ip address <a href="http://130.126.0.145/32" target="_blank">130.126.0.145/32</a><br>
ip pim-sparse<br>
<br>
router pim<br>
rp-address 130.126.0.145<br>
rp-candidate loopback 2<br>
!<br>
interface ve 3502<br>
port-name uiuc-core1-dist11-lnk<br>
ip ospf area 0<br>
ip address <a href="http://172.20.20.5/30" target="_blank">172.20.20.5/30</a><br>
ip pim-sparse<br>
ip mtu 9000<br>
!<br>
<br>
<br>
and then here's the config bits on distribution devices that matter<br>
for getting things between the MLXs and to the user networks.<br>
<br>
<br>
router pim<br>
route-precedence mc-non-default uc-non-default mc-default uc-default<br>
<br>
router pim<br>
rp-address 130.126.0.145<br>
<br>
<br>
interface ve 3502<br>
port-name uiuc-core1-dist11-lnk<br>
ip ospf area 0<br>
ip address <a href="http://172.20.20.6/30" target="_blank">172.20.20.6/30</a><br>
no ip redirect<br>
ip pim-sparse<br>
<br>
interface ve 499<br>
port-name uiuc-test2wireless-net<br>
ip ospf area 1<br>
ip ospf passive<br>
ip address <a href="http://192.17.201.1/24" target="_blank">192.17.201.1/24</a><br>
no ip redirect<br>
ip helper-address 128.174.45.8<br>
ip pim-sparse<br>
<br>
<br>
<br>
If this wasn't enough detail, let me know what questions you still<br>
have. Some weeks we feel like we are Foundry's only multicast QA<br>
department.<br>
<br>
I almost forgot, you want to be running something really current<br>
like 3.9.00a or later for them to have fixed most of the multicast<br>
bugs.<br>
<br>
-debbie<br>
<br>
<br>
On Feb 23, 2009, at 14:45, Bjørn Skovlund Rydén wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi everyone,<br>
<br>
Sorry to bother you for this, but my technical friend at Foundry<br>
seems to have gone on vacation for a few weeks, and I’d like to get<br>
on with this.<br>
<br>
We’re running a mesh of 6 MLX’s with distribution rings based on<br>
FES/FESX. I’m now starting to look at multicasting and having read<br>
back and forth in the config-guide, I’m still a bit clueless as to<br>
how to get the simplest thing to work.<br>
<br>
I would like to receive multicast traffic on a VLAN on MLX A and<br>
have recipient on MLX B on a routed interface. Very basic stuff,<br>
I’d say, but after a day in the test-lab, I’m still not successful :<br>
( So can someone give me the most basic configuration example on<br>
how to do this?<br>
<br>
Kind regards,<br>
Bjørn<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</blockquote>
<br>
-----<br>
-debbie<br>
Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il<br>
email: <a href="mailto:fligor@illinois.edu" target="_blank">fligor@illinois.edu</a> <<a href="http://www.uiuc.edu/ph/www/" target="_blank">http://www.uiuc.edu/ph/www/</a><br>
fligor><br>
"My turn." -River Tam<br>
<br>
<br>
<br>
<br>
<br>
</blockquote>
<br>
-----<br>
-debbie<br>
Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il<br>
email: <a href="mailto:fligor@illinois.edu" target="_blank">fligor@illinois.edu</a> <<a href="http://www.uiuc.edu/ph/www/" target="_blank">http://www.uiuc.edu/ph/www/</a>fligor><br>
"My turn." -River Tam<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</blockquote>
<br>
-----<br>
-debbie<br>
Debbie Fligor, n9dn Network Engineer, CITES, Univ. of Il<br>
email: <a href="mailto:fligor@illinois.edu" target="_blank">fligor@illinois.edu</a> <<a href="http://www.uiuc.edu/ph/www/fligor" target="_blank">http://www.uiuc.edu/ph/www/fligor</a>><br>
"My turn." -River Tam<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
foundry-nsp mailing list<br>
<a href="mailto:foundry-nsp@puck.nether.net" target="_blank">foundry-nsp@puck.nether.net</a><br>
<a href="http://puck.nether.net/mailman/listinfo/foundry-nsp" target="_blank">http://puck.nether.net/mailman/listinfo/foundry-nsp</a><br>
</div></div></blockquote></div><br>