Pages

Wednesday, July 23, 2014

Create DHCP Scopes From Command Line

Sorry everyone, I know it has been a while again. I recently started a new job again and it is back in the education field except it is now at the post-secondary level. Huge difference between the K-12 enviroment I was in before.

Anyway, I have been helping out on a subnetting project implementing a lot of VLANs (almost 50). I was given the task of creating the DHCP scopes for all of these new VLANs on the Windows 2012 R2 server. Sounds fun right? Not really when you think about going through the scope wizard 40+ times but I found a way to do it from the command line.

To get started you have to open up a command prompt and use the netsh command. 

Once you get to the netsh> prompt, type in the following:
dhcp server IP Address/ServerName add scope NetworkAddress SubnetMask  ScopeName ScopeDescription
 The NetworkAddress, SubnetMask, and ScopeName are required. *Side note: You need the quote marks " " if the ScopeName and ScopeDescription have spaces.

Here is an example of a complete command looks like:
dhcp server 192.168.1.10 add scope 192.168.2.0 255.255.255.0 "Wireless 200" "Wireless VLAN for 200 Building"
Now that the scope is created, we need to add a range of addresses for the server to hand out. That command looks like:
dhcp server IP Address/ServerName scope NetworkAddress add iprange RangeStart RangeEnd
Here is my example:
dhcp server 192.168.1.10 scope 192.168.2.0 add iprange 192.168.2.10 192.168.2.0.254 
Another command that I used was to add the gateway address. To set different options, you will need to know the option number; for my case, the Router option is number 003.

dhcp server 192.168.1.10 scope 192.168.2.0 set optionvalue 003 IPADDRESS 192.168.2.1

There are a lot of other things that you do like add/delete scopes, super-scopes, etc., just click on the resource link below.



Resource:
http://technet.microsoft.com/en-us/library/cc787375(v=ws.10).aspx

Tuesday, January 28, 2014

Taking A Look At XenServer

Sorry ladies and gents, this post is not a how to, it is about my impressions of XenServer. With that said, on to the post.

For the last couple of weeks, I have gotten a chance to play around with a spare server at work and a copy of XenServer 6. From my experience with it so far, I really like it.

As with anything new, there is a little bit of a learning curve, but if you are familiar with virtual machines and hosts, like me, you shouldn't have a problem.

Now, unlike Hyper-V and vmWare, XenServer is open source and free, you only pay for a support contrat, if you want. I know this seems right because XenServer is owned by Citrix, but I assure you it is free. XenServer was created way back in 2003 and along the way somewhere, Citrix bought up the company.


XenServer is based on Linux, that is free.