Home > Cisco UCS Configuration, Nexus 1000V, Physical Equipment, Uncategorized, VMware vSphere > VMware vSphere 5 AutoDeploy on Cisco UCS – Part 1: DHCP

VMware vSphere 5 AutoDeploy on Cisco UCS – Part 1: DHCP

12/19/2011

First, many thanks to Gabe and Duncan for their great Auto-Deploy guides that got me started.  Found here and here.  Their information answered a lot of questions, but left me with even more questions about how to implement it in my environment.

My goal is to demonstrate how to implement and configure vSphere Auto-deploy in a near-production environment that uses vSphere 5, Cisco UCS, EMC storage, Nexus 1000V and vShield Edge.

The first hurdle I ran into was trying to make DHCP cooperate.  I’m using vShield Edge for DHCP in some of the protected networks, but the Cisco 2900-series router is doing DHCP for the network where the vSphere Management addresses live.  In IOS for DHCP, you can assign a manual address in a pool via the “hardware-address” OR the “client-identifier” parameter.  Looks like “client-identifier” is used by DHCP, whereas “hardware-address” is used by BOOTP.  When booting, the blade first draws information via BOOTP, but after acquiring the details from TFTP, it changes its personality and sends another DHCP DISCOVER request.

Here’s how we got this working in our environment:

  • Identify permanent addresses for your hosts  (10.10.0.23 in this case)
  • Identify a temporary address for each host (10.10.0.123 is this case)
  • Make sure those addresses are not excluded

    ip dhcp excluded-address 10.10.0.0 10.10.0.20
    ip dhcp excluded-address 10.10.0.25 10.10.0.120
    ip dhcp excluded-address 10.10.0.125 10.10.0.210
    ip dhcp excluded-address 10.10.0.251 10.10.0.255

  • Create your “main” pool if it doesn’t already exist

    ip dhcp pool mgmt
    network 10.10.0.0 255.255.255.0
    default-router 10.10.0.253
    dns-server 10.10.0.61 10.10.0.62
    lease 0 8
    update arp

  • Create Pool for your permanent host address, make sure to use the “client-identifier” parameter

    ip dhcp pool AutoDeploy23
    host 10.10.0.23 255.255.255.0
    client-identifier 0100.25b5.0000.2d
    bootfile undionly.kpxe.vmw-hardwired
    next-server 10.10.0.50
    client-name AutoDeploy23
    dns-server 10.10.0.61 10.10.0.62
    option 66 ip 10.10.0.50
    option 67 ascii undionly.kpxe.vmw-hardwired
    default-router 10.10.0.253
    lease 0 8
    update arp

  • Create Pool for the temporary host address, assigned first by BOOTP and dropped after PXE boot

    ip dhcp pool AutoDeploy123
    host 10.10.0.123 255.255.255.0
    hardware-address 0025.b500.002d
    bootfile undionly.kpxe.vmw-hardwired
    next-server 10.10.0.50
    client-name AutoDeploy23
    dns-server 10.10.0.61 10.10.0.62
    option 66 ip 10.10.0.50
    option 67 ascii undionly.kpxe.vmw-hardwired
    default-router 10.10.0.253
    lease 0 8

Continue on to Part 2, covering the creation and assignment of the image profile

Advertisements
  1. 02/08/2012 at 11:05 am

    Brian,

    What do you recommend for learning UCS? Is there a lab of some sort I could setup? I know there is a UCS emulator, but will that be enough to deploy hosts and configurations?

    Many thanks,

    Miguel

  1. No trackbacks yet.
Comments are closed.
%d bloggers like this: