New Vlan/Subnet Setup Help

Dursh · ‎06-08-2010

Hey guys,

Heres an overview of what the IT manager wants implemented..

Currently I every PC/Server/Switch runs of the same subnet of 192.168.1.x.

We have a new server for Programmers and IT department and this is what the manager wants it setup...

The new server has a 4port nic, hes wants a 2ports in a lag to connect to the 192.168.1.x subnet.
He then wants the other 2port lag to run into the HP 4104gl switch in my room on a 192.168.2.x subnet. ( I will run a DHCP server on the server to issue IP's in the 192.168.2.x subnet accordingly)

I will then run a trunk link from the Helpdesk room who uses a HP 2524 and a Programmers room that also has a 4104gl into the 4104gl in my room.

Now my questions are:-

1. I need personally need to be on the 192.168.1.x subnet. Therefore I must need to run a Vlan's on my switch. Therefore how do I go about setting say module A to be on the 192.168.1.x subnet and module B being on the 192.168.2.x subnet?

2. The catch is the programmers and Helpdesk will still need access to the 192.168.1.x subnet as that where the mail server and what not reside. So how do I make sure that they have access to them?

Thanks so much in advance

Josh Boyer · ‎06-10-2010

Hey Dursh,

Since no one has posted anything ill see if I can be of some assistance.

1. Yes you will need to add a second Vlan for your 192.168.2.x subnet. To configure each module for one Vlan you would do the following:

Create the vlan in configuration mode:

Switch#configure terminal

Switch(config)#vlan 10

switch(vlan-10)#name XXXXX (optional if you want to name the vlan something)

Switch(vlan-10)#ip address 192.168.2.252 255.255.255.0

switch(vlan-10)#untagged b1-b22 (I would Leave b23-b24 for a trunk to one of the other switches)

All the ports in Module A should already be members of the default Vlan-1 so you don't need to do anything with these.

2.I'm guessing everyone will be a native member of the 192.168.1.x subnet? So you will need to either you an external router or one of your switches to route between the vlans. I would suggest you use your switch; to enable routing type the following at the switch configure prompt:

Switch(config)#ip routing

Users on the 192.168.1.x (vlan 1) should now be able to access devices on the 192.168.2.x subnet (vlan 10)

I did not mention creating trunks to the server or to the other switches let me know if you need help with these as well.

Regards,

Josh Boyer · ‎06-10-2010

Sorry I need to add to the routing configuration.

If you don't already have an ip address assigned to your default vlan (vlan 1) then you will need to add one so the switch creates the route.

Swich(config)#vlan 1
Switch(config)#ip address 192.168.1.252 255.255.255.0
switch(config)#exit

you will need to ensure members of vlan1 use 192.168.1.252 as their default gateway and members of vlan 10 use 192.168.2.252 as there default gateway.

You will then also need to make a default route directing all other traffic to your firewall/router/ISP modem so that clients still have access to the internet.

switch(config)#ip route 0.0.0.0 0.0.0.0 x.x.x.x (x = The ip address of your firewall/router/ISP modem.)

Depending on what other devices you have in your network it might be easier to let your firewall or router (if you have one handle the routing) as you might already have all your clients setup with this as your default gateway.

You will then need to configure what is call a "Router on a stick" configuration.

Regards,