the config looks good. 

 

Sorry, ihave no input for the DHCP server portion.

 

 

This might be a stupid question but do i have to plug the dhcp server in and particular port?

 

 

 

i followed the directions there to create the config file i posted above. I thought that when you enable dhcp relay and give it the dhcp server address, that creates the route.

 

My computer are getting ip address, just not the correct ones for their subnet.

 

How do i create the static route from the router to the server?

 

 

I think  there is a problem with the configuration on the DHCP server.

 

Could someone point me in the right the direciton as how to have the DHCP server set up?

Is it just me, or is port 8 not assigned to a VLAN?  It should trunk VLANs 2 and 3 to your server.  Then, if your server has the VLANs configured, you should be able to assign IP's to them and the DHCP server should assign IP's based on the incoming VLAN.  Plus the IP you have assigned for your DHCP forwarder doesn't exist on any defined VLANs.

 

 

This should be pretty straight forward, let me give you an example.

 

You have 3 subnets,

 

Subnet a - 10.10.10.0

Subnet b - 10.10.20.0

Subnet c - 10.10.30.0

 

Subnet a is for clients, Subnet b is for clients, Subnet c is for the dhcp server

 

Setup vlan 10,11,12 on the switch assinging vlan interfaces as follows

 

vlan 10 - 10.10.10.1 (subnet a)

vlan 20 - 10.10.20.1 (subnet b)

vlan 30 - 10.10.30.1 (subnet c)

 

to keep it simple setup port 1 to access vlan 10, port 2 to vlan 20 and port 3 to vlan 30.

 

your DHCP server would be 10.10.30.2 with its default gateway pointing to 10.10.30.1. Plug it into port 3

 

add the server ip to the DHCP helper address in the switch

 

on the DHCP server create 2 scopes

 

scope 1 - 10.10.10.2 - 10.10.10.254  on a /24 subnet. Setup the default gateway to 10.10.10.1

scope 2 - 10.10.20.2 - 10.10.20.254  on a /24 subnet. Setup the default gateway to 10.10.20.1

 

 

Now, you shouldnt have to touch routing tables. By default when a local interface comes up on the 6024 the switch will route it (unless you have ACL's setup).

 

Now when you plug a client into port 1 or port 2 the switch should relay the DHCP request to the DHCP server which will reply with an address from the appropriate pool based on the routing interface on the switch it came from.

 

 

 

From what i see in your initial post you dont have a vlan with the DHCP server in it setup, so the switch doesnt know where to forward the packets. Try the above scenario it should work fine.

 

DRNO10,

 

 

THANKS A LOT ! My DHCP was misconfigured.

Dr No,

 

I seem to still need some of your assistance.

 

Currently i have the 6024 configured with 6 VLANs:

 

1

100    192.168.1.1

400    192.168.4.1

500    192.168.5.1

600    192.168.6.1

700    192.168.7.1

 

i have 2 ports that combine to form a Lag. This Lag is part of every vlan.

 

I have the 6024 connected to a 3448 switch using the  lag.

 

the 3448 have vlans configured all with the lag as a member. The vlan members on the switch are getting the corrected ip address based on the ip address of the vlan. But, all of the computers can ping each other. Doesn't it defeat the point of vlans if all of the computer can communicate with each other? Or am i utilizing the lags incorrectly?

 

 

 

 

 

 

 

 

 

 

 

 

By default on the 6024 when the routing interfaces come up it allows full routing between all interfaces. Now as pointless as that seems, this still keeps the subnet broadcasts and snooping contained within each specific vlan unless the person knows the ip they want to connect to.

 

The beauty of having the 6024 at the core handling your routing is you can control of the traffic crossing the interfaces. You can lock things down and only allow specific port/ip ranges ect to certain vlans using ACL's(access control lists). One thing to remember is on the 6024 ACL's are applied to the ingress traffic as it enters the vlans not egress. the 62XX series allows both ingress and egress traffic ACL's.