470-48T switches can I do this?

Setup 3 VLAN's on your switch as your mention first. After it, set fiber ports as a trunk port with MLT to connect ERS8600.

All ports that are members of a Multi Link Trunk must be in the same VLANs or things won't work right. All MLT port members must be configured identically.

Ok, so call 204.80.158.x VLAN 1, 172.16.0.0 VLAN 2, 172.16.32.0 VLAN

3, and 192.168.1.0 VLAN 4. The actual VLAN numbers you use must match those that are used on the core switch.

You don't "pull down" VLAN info dynamically. You configure all the VLANs statically, first for the trunk:

vlan port 1/48,3/48 tagging tagAll vlan members add 1 1/48,3/48 vlan members add 2 1/48,3/48 vlan members add 3 1/48,3/48 vlan members add 4 1/48,3/48 vlan port 1/48,3/48 pvid 1 mlt 1 member 1/48,3/48 mlt 1 enable

Then the user ports e.g. on stack unit number 2:

auto-pvid vlan members add 1 2/1-24 vlan members add 3 2/25-40 vlan members add 2 2/41-48

OK I am doing this all through the console, can I do that? I've setup my mlt and that seems to to working, my stack ip is

172.16.32.14 and my mlt is plugged into the core and on vlan172_32

my vlans are: vlan172_0 vlan172_16 vlan172_32 vlan192 vlan204

I've created vlans on my stack named the same as on the core eg: vlan172_16 etc, and made them active

I created the vlan192 and set port 3 on switch 1 to it, even though the whole stack is on the vlan172_32 I then plugged a PC into port 3 on switch one and tried to pull a

192.168.1.x address and it would not get one. I then statically gave it an address of 192.168.1.119 and still I had no access to my netowrk.

If I plug something into the switch ports and give it a 172.16.32.x address I am fine and can get on the network.

Why is my vlan192 not getting through to port 3? Any ideas?

thanks.

You should set the same VLAN for 192 on core switch. After it, set the ports or MLT on ES470 and core switch as trunk port. Finally, set DHCP relay (IP helper) on your core switch to let your clients in VLAN 192 can get IP address from DHCP server.

My core has all my vlans on it, I can make any port on the core any of my vlans. I put my fibers into ports 4 and 6 on the core, I then set core ports

4 and 6 to vlan172_32 because my stack IP is 172.16.32.14

If my switch stack IP was: 192.168.1.14 I would make ports 4 and 6 on ports be vlan192, but my switch stack has a 172.16.32.14 address.

Now when I am plugged into the fiber my 3 switches in the stack all work, meaning any PC plugged into any switch and any port on the switch can be assigned a 172.16.32.x address.

But I want to for example plug PC into switch 1 of my group and ports

3 through 20, I want to be able to plug in computers with a 192.168.1.x address .....When I goto switch 1 and choose to make ports 3 through 20 vlan192 it seems to work but If I plug a 192.168.1.x PC into one of those ports it can not get out on the network...its like the 192 is not being passed to those ports.

any ideas?

For your question, I would like to know what you set for port 4 and 6 of the core switch. I assume that you only assign port 4 and 6 of the core switch to VLAN172_32 and use fibers to connect to the ES470 stack. The packets of VLAN172_32 can go to core switch through ES470 because you set port 4 and 6 to VLAN172_32. If you want the packets of VLAN192_168 can also go to core switch, you should also set port 4 and

6 to VLAN192_168 on core switch. As the result, port 4 and 6 on core switch will be the members of both VLAN172_32 and VLAN192.168 as trunk ports. These can be done by 802.1q tagging on ERS8600 and ES470.

For example, the port members of VLAN's should look like this when you use port 2/48 and 3/48 to connect to ERS8600;

ES470-48T stack VLAN172_32 : 2/1-3/48 VLAN192_168: 1/3, 2/48, 3/48 (2/48 and 3/48 are trunk ports and MLT members)

ERS8600 VLAN172_32 : 1/4, 1/6 VLAN192_168 : 1/4, 1/6 (1/4 and 1/6 are trunk ports)

On ERS8600, turn on the DHCP relay on the interface IP of VLAN192_168 and setup relay agent IP address.

When I turn on Perform Tagging for Ports 1/4 and 1.6 on my core the

470 stack goes dead, meaning I can no longer see it on my network.

You might want to read "Configuring VLANs, Spanning Tree, and MultiLink Trunking" here, starting at page 37:

Your management VLAN has to be defined in your trunk group and the switch stack told what VLAN you want to use.