Skip to main content

PXE, SunRay, Beacen dhcpd.conf


I have my "play" network where I test out a bunch of stuff.  I have a satellite server for testing which handles the DHCP stuff for me.  I just broke that portion of my lab, but I needed to test out Tim Beatty's Beacen product using PXE, a SunRay station.

This configuration would not likely be used in a production environment, but I wanted to document how you add "custom" dhcp options (in this case Option 194).

PXE, SunRay, Beacen dhcpd.conf


#deny unknown-clients;
# BEGIN - SunRay stuff
option space SunRay;
option SunRay.AuthSrvr code 21 = ip-address;
option SunRay.AuthSrvr 10.10.31.104;
option SunRay.FWSrvr code 31 = ip-address;
option SunRay.FWSrvr 10.10.31.104;
option SunRay.NewTVer code 23 = text;
option SunRay.NewTVer "3.0_51,REV=2004.11.10.16.18";
option SunRay.Intf code 33 = text;
option SunRay.Intf "eth0";
option SunRay.LogHost code 24 = ip-address;
option SunRay.LogHost 10.10.31.103;
option SunRay.LogKern code 25 = integer 8;
option SunRay.LogKern 6;
option SunRay.LogNet code 26 = integer 8;
option SunRay.LogNet 6;
option SunRay.LogUSB code 27 = integer 8;
option SunRay.LogUSB 6;
option SunRay.LogVid code 28 = integer 8;
option SunRay.LogVid 6;
option SunRay.LogAppl code 29 = integer 8;
option SunRay.LogAppl 6;
# END - SunRay stuff
# BEGIN - Beacen stuff
# Option 66
option tftp-server-name "vserver.example.com";
option option-194 code 194 = string;
# END - Beacen stuff

not authoritative;
ddns-update-style       none;
ddns-updates off;
ignore client-updates;
log (info, concat ( "DHCP VCI: " , option vendor-class-identifier ) ) ;
log-facility local7;

allow bootp;
allow booting;

option ip-forwarding    false;  # No IP forwarding
option mask-supplier    false;  # Don't respond to ICMP Mask req

subnet 10.10.31.0 netmask 255.255.255.0 {
  option domain-name              "example.com";
  option domain-name-servers      10.10.31.103, 10.10.31.104, 8.8.8.8;
  option routers        10.10.31.1;
  option subnet-mask    255.255.255.0;
  option broadcast-address 10.10.31.255;
  option ip-forwarding off;
  option netbios-node-type 2;
  option ntp-servers 10.10.31.103, 10.10.31.104;
  range 10.10.31.200 10.10.31.210;
  max-lease-time 21600;
  default-lease-time 21600;

  # BEGIN - Beacen stuff
  next-server 10.10.31.104;          # IP of your vServer (this breaks kickstart)
  option option-194 "10.10.31.104";  # IP of the vServer
  # END - Beacen stuff

  if substring (option vendor-class-identifier, 0, 9) = "PXEClient" {
    filename "/pxelinux.0";
  }
  elsif substring (option vendor-class-identifier , 0, 7 ) = "rhel-server-6.0-x86_64" {
    # rhel-server-6.0-x86_64
    filename "/export/kickstart/Profiles/rhel-server-6.0-x86_64.ks";
  }
  elsif substring (option vendor-class-identifier , 0, 7 ) = "CentOS-5.5-x86_64" {
    # CentOS-5.5-x86_64
    filename "/export/kickstart/Profiles/CentOS-5.5-x86_64.ks";
  }
}

Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...