Question : Problem: Best way to handle VLANs on 3com 4800G and 4200G

I have a cluster of (3) 4200Gs with no configuration minus the clustering at this time.  They will be used as my distribution/access layer.  I will be setting up link aggregation and connecting each switch back to the 4800G for redundancy and faster switching on the back end.  Sitting in front of the 4800G will be a 3Com Layer 3 Device (Office Connect gigabit VPN Firewall 3CREVF100-73).

My question is what is the best way to handle the creation and propagation of VLANs?

Initially I was going to create them on the Layer3 device and make sure that each interface/link on the 4800G connecting to the Layer 3 were set to Trunk.  And then do the same for the aggregation links on the 4200Gs so that the Vlan traffic will pass to all switches.

I understand I'll still have to create the basic Vlan info on each switch with the same IDs and then assign the static ports to the VLAN respectively.

Just wondering if it makes sense to create the VLAN Interfaces (with their IP scopes) on the Layer3 or the Layer2 core switch.  I was really leaning towards the Layer3 so that the Vlans can interroute. But I'd really like some advice on this.

Thanks in advance!

James

Answer : Problem: Best way to handle VLANs on 3com 4800G and 4200G

Create vlans on all switches. (manual process, but very simple)
Create vlan interfaces only on the core switch.
Connect all switches using trunk ports that permit all vlans.

This would make all vlans communicate with each other. I would also add a static route on the core switch to make the Office Connect Firewall be it's default gateway to internet. (which I guess is why you have it).