Lets say you have 3 nics you want to test just to give us a smaller number
for the example. You can do what you want with just one DHCP server with
one nic in it if you have a layer 3 switch available. Lets also assume the
switch has 24 ports. What you will do is::
Create DHCP server 192.168.1.1
Create the following scopes on DHCP server
-- 192.168.1.x
-- 192.168.2.x
-- 192.168.3.x
On Layer 3 swithc you will create 2 more vlans (VLAN1 default)
On Layer 3 switch you will configure DHCP realy for 192.168.1.1
On each VLAN you will assign it a IP
-- VLAN 1 = 192.168.1.254
-- VLAN 2 = 192.168.2.254
-- VLAN 3 = 192.168.3.254
Create Routes on switch to route between VLANS
** Some switches require routes setup before assigning VLAN IPs
All ports are VLAN 1 by default
Assign ports 7-12 to VLAN2
Assign ports 13-18 to VLAN3
Plug DHCP server into Port 1
Plug a each nic from test machine into each VLAN
--Nic 1 into port 2 (VLAN1)
--Nic 2 into port 7 (VLAN2)
--Nic 3 into port 13 (VLAN3)
Now when you boot the test machine with all the NICs in it, each will ask
for a DHCP address and since each is on a separately configured VLAN, it
will relay to back to the single DHCP server with all the scopes on it and
be issued the appropriate scope for each VLAN. The more nics you need to
test, the more VLANs and scopes you create. The good thing about this is no
more static routes and you just replace each nic as you need.
You will need to check your switch for more details on how to setup the
relaying
"Ace Fekay [Microsoft Certified Trainer]" <(E-Mail Removed)>
wrote in message news:Olx3nr1$(E-Mail Removed)...
"SPORES" <(E-Mail Removed)> wrote in message
news:3592B63C-8549-4907-9731-(E-Mail Removed)...
> Greetings,
>
> I have a test lab where we constantly are testing multiple NIC
> configurations. To try and speed this up, I was looking to create a DHCP
> server to assign IP addresses to systems under test. The static route is
> quite tedious when you have up to several ports to test.
>
> The way we test, is to break each port down to a separate segment to
> ensure
> that each NIC gets hammered during stress testing.
>
> What I am looking for, (since I don't play with DHCP that often in
> configurations like this) is if there is way for a DHCP server to assign a
> different subnet scope to each different NIC port that is issuing DHCP
> requests on the client under test.
>
> What I have:
>
> - Windows 2003 Server
> - Eight NICs, each assigned a static IP in each scope
> - Eight scopes
> - 192.168.0.1 - 192.168.0.254 (exception 192.168.0.1 = the static IP for
> the NIC)
> - 192.168.1.1 - 192.168.1.254 (exception 192.168.1.1 = the static IP for
> the NIC)
> - 192.168.2.1 - 192.168.2.254 (exception 192.168.2.1 = the static IP for
> the NIC)
> - 192.168.3.1 - 192.168.3.254 (exception 192.168.3.1 = the static IP for
> the NIC)
> - 192.168.4.1 - 192.168.4.254 (exception 192.168.4.1 = the static IP for
> the NIC)
> - 192.168.5.1 - 192.168.5.254 (exception 192.168.5.1 = the static IP for
> the NIC)
> - 192.168.6.1 - 192.168.6.254 (exception 192.168.6.1 = the static IP for
> the NIC)
> - 192.168.7.1 - 192.168.7.254 (exception 192.168.7.1 = the static IP for
> the NIC)
>
> Example:
>
> Server has eight nics.. so each nic would get one IP address from each of
> the segments instead of eight addresses from one scope.
>
> I haven't seen a clear way that this could be done other than using the
> MAC
> address of the NIC, and since we are testing so many random network
> adapters,
> this is not easily feasible.
>
> Any help would be greatly appreciated... even if it's a way to test it
> differently!
>
> Thanks!
Interesting setup. What I can say, and not sure about how this fits in with
testing, or it may help to understand how DHCP scopes work, is that if a
DHCP discover comes across say, the NIC with 192.168.3.1, DHCP will offer
the client an IP in the 192.168.3.2-.254 range. So it's based on the NIC's
config. The only exception to the rule I can think of (and hope someone else
jumps in to correct me or offer additional info), is if there is a DHCP
Scope created with an IP range that doesn't match any of the installed NICs'
IP range, and a DHCP Agent listening for requests from a router using IP
helpers for a subnet that matches that Scope's IP range, it will give an IP
in that scope accordingly.
Btw - I hope this is not a DC!
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup/forum to benefit from collaboration among
responding engineers, as well as to help others benefit from your
resolution.
Ace Fekay, MCT, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
(E-Mail Removed)
http://twitter.com/acefekay
For urgent issues, you may want to contact Microsoft PSS directly. Please
check
http://support.microsoft.com for regional support phone numbers.
Similar Threads
Linear Mode
