UNSOLVED
F
freeway727
18 Posts
0
18044
January 30th, 2008 18:00
VLAN Predicament ( Please HELP)
Hi Everybody
I need help achieving the following setup for vlans, i have been at this for about a month now and i cant get it to work. here is how my network setup
Floor1 - 1x PC3448
Floor 2- 1x PC3424
Floor 3- 1 x PC 3448
Server Room - 1x PC6248
Floor 1 and Floor 3 (PC3448) have two ports each in lag setup connecting to the 6248, Floor 2 is one link. We are one company with two divisions spread across all floors. i would like to create three vlans 10,20,30 across all switches
10--> division 1
20--> division 2
30--> Guest Access
I have seven servers connected to the 6248 from port g1 to g7 and watchguard firewall on g8, and g9.
I would like to setup vlan 10 and 20 to access g1 to g8 on the 6248. I would like vlan 30 to access g9 only , straight to the internet. I know all the ports that need to be on each vlan but dont know how to approach it. i have tried setting up this before and went know where with it.
i will provide any information required, please help and provide me with your ideas , suggestions to resolve this problem.
Message Edited by freeway727 on 01-30-2008 02:39 PM
Message Edited by freeway727 on 01-30-2008 02:40 PM
Message Edited by freeway727 on 01-30-2008 02:41 PM
freeway727
18 Posts
314
0
Posted January 30th, 2008 21:00
thanks for the response, i will look in to that, the big issue at the moment is how to get the 3448/24 switches to pass on the vlans to the 6248, i have tried trunking the lags and everything fails, i cant get to my gateway or get an ip assigned. how did you around that.- There are a few things you need to do and decide for this type of setup.First question is you mentioned the servers need access to both vlans. Now its easy to pass both vlans you need to the servers over a trunk, but this will require your servers to be vlan aware with an ip in each vlan.Now the way i would approach this is to create a 4th vlan with only the servers in it, the 62XX will route the other vlans through to this vlan no problem. This way you would get the added control of ACL's to control traffic across the routing interfaces. The only reason i would avoid this is if you have a specific application or software that would require the clients to be on the same subnet as the server.Now for the edge switches (34XX) i would create vlans on the switches. They allow whichever ports you want to have access mode to the vlan you desire. Trunk your uplink back to the 62XX and add both vlans in tagged mode.On the 62XX create all the vlans and give them all interface ip's in thier destination vlan's subnet. once you create all these the switch will bring the interfaces up and allow traffic to route across the interfaces. You then use ACL's to control that traffic. You can then setup the default gateway on the routing part of the switch to your firewall so it pushes all unlocal traffic (internet) to your firewall.As for dhcp, assuming you have only 1 server you need to setup a multiscope dhcp server and use the dhcp helper function in the 62XX to pass all DHCP requests to this server. Now the key that alot of people miss here is when you setup the DHCP scopes you need to set the client default gateway to the interface on the 62XX so it can properly route the traffic.And dont forget to add some static routes to your firewall so it knows where to send all the traffic back to (the 62XX)I realize this is very brief and only touches on these subjects, but if you search this forum you will find alot more information on these areas listed above.Have fun!
freeway727
18 Posts
314
0
Posted January 31st, 2008 18:00
Thank you DRNO10 , i appreciate your feedback. I will look in to your suggestions. The biggest problem i have is trunking at the moment,i can't seem to get it working between the edge switches and core. also what is the cli code to setup interfaces for vlan. i have tried looking at the forum but there is not alot of complete solutions, the posts with issues similar to mine usually go unread.- Take a look at this thread.He is trying to achieve what i believe is the same thing as you. Although he is using the 6024, it will be almost identical to the 62XX switches. You can see some CLI code posted showing how to setup interface ip's, which is as simple asinterface vlan1ip address x.x.x.x 255.255.255.0As for your trunking, not sure what to say there. Are you using lags out to each edge switch or just a single link?
freeway727
18 Posts
314
0
Posted January 31st, 2008 19:00
i am using lags for the 3448 and just an uplink for the 24.- So on the 3448's you have created the above mentioned vlans and the lags. You switch the lag mode to trunk (or even general will work) and for each of those vlans you have added them as tagged to the lag? Have you switched the ethernet ports on the switch to access mode to thier particular vlan? make sure the PVID for each port matches the vlan it has access to. Same thing on the 62XX side. Once you assign an ip to the 6224 interface you should be able to ping it from one of the edge switches.
freeway727
18 Posts
314
0
Posted February 1st, 2008 15:00
i was able to get the vlans working across all the switches. all of my servers are vlan aware. i was able to set the servers with Broadcom nics correctly but unfortunetly my dhcp server with oneintel pro 1000 nic keeps going offline when i set the vlans in the proset utility. its really odd i set vlan 10 and default vlan 1 , did the configuration but machines on vlan 10 and 1 can't receive leases and even ping once manual ip is set. mind you my broadcom equiped servers are running smoothly.
QRiff
16 Posts
314
0
Posted January 30th, 2008 20:00
Message Edited by QRiff on 01-30-2008 05:14 PM