|
Posted by Dophi on April 10, 2007, 9:54 am
If you were Registered and logged in, you could reply and use other advanced thread options >
>
>
> > > I have a stack of three 470-48T switches cascaded and I have a gigabit
> > > modual in switch 1 and 3 and I have a multi link trunck set up and two
> > > fibers going to my core from the switches.
> > > My fibers are going into the core, one is on the 172.16.x.x vlan while
> > > another is on the 192.168.1.x vlan.
>
> > 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.
>
> > > I have a number of vlans running out of my 8600 core a 204.80.158.x,
> > > 172.16.0.0, a 172.16.32.0 and 192.168.1.0.
>
> > 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.
>
> > > My question is with the switch stack IP of 172.16.16.76 can I push out
> > > all my vlans to the switch group and then say make ports 1 through 24
> > > vlan 204.80.158.x and ports 25 through 40 vlan 172.16.32.x and ports
> > > 41 through 48 vlan 172.16.16.x can I do this push my vlans out to
> > > the port even though the 470's are layer 2 switches I heard I can do
> > > this....is that right and how would I do it?
>
> > > I guess how do I pull down all the vlan info from my core to the stack
> > > and then go from there?
>
> > 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.
| 
Yahoo! 
Google 
Windows Live 
del.icio.us 
digg 
Netscape 
XML site map