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

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...