DHCP and reservations

This forum discusses topics about the Ultimate Deployment Appliance

Moderators: the_dude, Posters

DHCP and reservations

Postby WARLOCK » Fri Jun 04, 2010 9:02 am

Hi Guys,

I want to enable DHCP on the UDA appliance, but am concerend that it will issue IP address to server outside of my control.
How do I configure it to only issue IP to servers in a reservation list.

This is my current config.

Code: Select all
log-facility local6;

ddns-update-style ad-hoc;
ddns-hostname = concat("station-",binary-to-ascii(10,8,"-",leased-address));
option host-name = config-option server.ddns-hostname;

next-server 10.1.101.46 ;

if substring ( option vendor-class-identifier, 0, 9) = "PXEClient"
{
  filename "pxelinux.0" ;
  next-server 10.1.101.46 ;
}

# Jumpstart Support
option space SUNW;
option SUNW.root-mount-options code 1 = text;
option SUNW.root-server-ip-address code 2 = ip-address;
option SUNW.root-server-hostname code 3 = text;
option SUNW.root-path-name code 4 = text;
option SUNW.swap-server-ip-address code 5 = ip-address;
option SUNW.swap-file-path code 6 = text;
option SUNW.boot-file-path code 7 = text;
option SUNW.posix-timezone-string code 8 = text;
option SUNW.boot-read-size code 9 = unsigned integer 16;
option SUNW.install-server-ip-address code 10 = ip-address;
option SUNW.install-server-hostname code 11 = text;
option SUNW.install-path code 12 = text;
option SUNW.sysid-config-file-server code 13 = text;
option SUNW.JumpStart-server code 14 = text;
option SUNW.terminal-name code 15 = text;

subnet 10.1.101.0 netmask 255.255.255.0 {
  option routers 10.1.101.1;
  option domain-name-servers 10.1.4.12 ;
  range 10.1.101.254 10.1.101.254 ;
  max-lease-time 300;

### STATIC IP LEASES ###
# ESX Servers
host derblesx06 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.122;}
host derblesx07 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.123;}
host derblesx08 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.124;}
host derblesx09 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.125;}
host derblesx10 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.126;}
host derblesx11 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.127;}
host derblesx12 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.128;}
host derblesx13 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.129;}
host derblesx14 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.130;}
host derblesx15 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.131;}
host derblesx16 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.132;}
host derblesx17 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.133;}
host derblesx18 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.134;}
host derblesx19 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.135;}
host derblesx20 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.136;}
host derblesx21 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.137;}
host derblesx22 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.138;}
host derblesx23 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.150;}
host derblesx24 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.153;}
host derblesx25 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.154;}
host derblesx26 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.155;}
host derblesx27 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.156;}
host derblesx28 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.157;}
host derblesx29 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.158;}
host derblesx30 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.159;}
host derblesx31 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.160;}
host derblesx32 {hardware ethernet 00:11:6b:d6:a9:80; fixed-address 10.1.101.161;}



  # next line is to include template configurations without cluttering the main config file
  include "/var/public/files/dhcpd.d.conf";

}
WARLOCK
 
Posts: 4
Joined: Fri Aug 21, 2009 12:46 pm

Re: DHCP and reservations

Postby richic » Wed Jul 14, 2010 6:57 pm

ignore unknown-clients;

Your DHCP server will only respond to servers that you have configured it to listen to.

man dhcpd for further information.
richic
 
Posts: 1
Joined: Wed Jul 14, 2010 6:53 pm

Re: DHCP and reservations

Postby edwardjock » Tue Dec 27, 2011 12:03 pm

When I was searching for DHCP information, I gathered some useful info. There are many advantages to using dynamic host configuration protocol (DHCP) reservations for Windows NT clients (Server or Workstation) over statically assigning the client with an IP address.
Using DHCP reservations allows administrators to have a central point of reference for all IP allocations in the organization. When you use DHCP Administrator (Mappings/Show Reservations), a complete list of active reservations as well as active leases is available in one location. This is a major advantage, especially when you are tracking down particular clients or even reassigning new scopes.
The Dynamic Host Configuration Protocol (DHCP) is a network configuration protocol for hosts on Internet Protocol (IP) networks. Computers that are connected to IP networks must be configured before they can communicate with other hosts. The most essential information needed is an IP address, and a default route and routing prefix.
DHCP eliminates the manual task by a network administrator. It also provides a central database of devices that are connected to the network and eliminates duplicate resource assignments.
DHCP also provides other configuration information,and it is used for IPv4 as well as IPv6. While both versions perform much the same purpose, the details of the protocol for IPv4 and IPv6 are sufficiently different that they may be considered separate protocols.Hosts that do not use DHCP for address configuration may still use it to obtain other configuration information. Alternatively, IPv6 hosts may use stateless address autoconfiguration. IPv4 hosts may use link-local addressing to achieve limited local connectivity.
edwardjock
 
Posts: 1
Joined: Tue Dec 27, 2011 11:00 am


Return to Ultimate Deployment Appliance

Who is online

Users browsing this forum: No registered users and 0 guests

cron