problem with vlan traffic through procurve 2510G

[AnswerFirst]

I'm having trouble passing data through my procurve from one device to another...

I have a 2510G with several vlans (10 and 20) that I use for ISP traffic (public addresses from broadband carriers).  Since each carrier has 1 ehternet handoff, and I have several public addresses, I plug each carrier's modem into a flat switch (provided by my hosted voip pbx vendor), and their voice router also plugs into that flat switch to pickup it's public addresses.  They simply multinet their WAN interface with both ISP's addresses.

I have a link from the flat switch to my procurve for each ISP (2 links) and I set each of those to an untagged vlan (one is vlan 10, one is vlan 20) to isolate their traffic in the procurve.

I then have an interface on the procurve that is tagged with vlan 10 and 20, that uplinks to my brocade controller.

The brocade controller is a rfs4000 that I use for my WLAN controller, and broadband data network, and I have it's uplink configured as a trunk port, with vlans 10 and 20 tagged.  

From the brocade, I can ping the procurve (if I give the procurve an address - for testing).  From the procurve, I can ping the brocade's addresses.  But I can't ping through the procurve from the brocade to the gateway, or to the public address on my voice router.  I also can't do the opposite direction through the procurve.

Here is a simplified drawing of this setup (I know it's not ideal, but the voice side is what is supported by our pbx vendor).

Drawing

My procurve setup is very simple, basically just untagged and tagged vlan ports.  The interface to my brocade I have tried as an acces port, trunk type trunk, and lacp type trunk, all vlan tagged.

Any ideas for me?

[Arimo]

Hi

Based on what you say the configuration seems to be correct. I'd suggest calling support.

[AnswerFirst]

Thanks Arimo.  I was really hoping that I was the problem, as that's typically easier to fix.

I'll give them a call and see what they suggest.

[Richard Brodie_1 · Accepted solution]

Are you running spanning-tree or loop protection? You appear to have a loop between the two links to the Linksys.

[AnswerFirst]

I am not running either Richard.  I will investigate this and see if that helps.  Thanks for the heads-up.  I didn't think it would be needed since they were going to different vlans, but since the linksys can't tell the difference, maybe that's the issue.