At this point, you have two
options when you create a new Baremetal Agent:
Before You Begin
Use a single
network for both management and PXE traffic.
networks: one for management and another for PXE traffic.
The BMA 5.0 ovf
must be deployed and its network must be configured.
Director 5.0 Multi-Node configuration must be completed.
You must have
created VMs in the VMware vSphere hypervisor. The network must be configured,
the Baremetal Agent VM must be completely booted up, and the VMware vSphere VM
Console must be closed. You have the IP address of the Baremetal Agent VM.
You must have an
environment that supports the network configuration you intend to use: either
the single network or the separate network configuration. Refer as necessary to
the topics in this documentation set that explain these different
To provide required
DHCP services, locate one DHCP server in the same PXE VLAN as
Cisco UCS Director
Baremetal Agent and configure that DHCP server with an appropriate IP
Cisco UCS Director Baremetal Agent to PXE boot
a given operating system, you must first provision that operating system image.
|| On the Menu
|| Click the
Baremetal Agents tab.
Baremetal Agent Appliance dialog box, complete the appropriate
fields as described in the following table:
Cisco UCS Director Baremetal Agent for
multi-node capabilities, set the
UCSD Database Address to use the
IP address. See the entry in the table below.
name you assign to the Bare Metal Agent for a given purpose. As a best
practice, apply a naming convention that includes the names of the managed
system components. This will enable you to recognize the constraints and
capabilities of the agent.
Management /PXE Address field
address of the BMA manager. If you are using a single network for both BMA
manager and the PXE, then this same address will automatically be assigned as
the PXE address.
This address must be reachable from the UCSD appliance.
Login ID field
Login ID for the Baremetal Agent administrator.
Password for the same Baremetal Agent administrator.
uses Different Interfaces for Management and PXE Traffic checkbox
this box if you want the network hosting the PXE server to be separate from the
network hosting the traffic manager.
If you check this box, a different set of fields will appear in
this form below the checkbox.
PXE Interface Address field
address for the BMA PXE server, if different from the address of the BMA
||This field appears only if the
BMA uses Different Interfaces... checkbox above has
Additional useful information about this Baremetal agent.
Location of this Baremetal agent. A physical location name, for
UCSD Database Address drop-down list
the IP address associated with the UCSD database that this BMA is going to use.
you are configuring BMA for multi-node capabilities, select the
Be aware that
the first BMA defined in
Cisco UCS Director
Baremetal Agent is automatically labeled as the Default BMA.
row appears in the Baremetal Agents tab, showing current information for this
services by clicking
If the DHCP
sever is not correctly configured, the status displayed in the Enabled Services
column will indicate that services are not enabled.
status will become "active" once the network services are started correctly.
first BMA created with Release 5.0 or later will be designated as the "Default"
BMA. By default, the Default BMA will be used as the target BMA for the Setup
PXE Boot task, if you use this task in a Workflow. To designate a different BMA
as the Default, select it in the
Agents tab and click
What to Do Next
Check the service
status by clicking
To see the
SSH-based test connection status with the BMA, check the Baremetal Agents table
default, a test Connection request is triggered every 15 minutes. This
frequency can be adjusted by using the "BMA Heartbeat Task".
To check the BMA
To check for
Cisco UCS Director
Baremetal Agent database updates by BMA, check the Baremetal Agents
table column labeled
there is no update in the database then the status will be "Inactive"
To configure a PXE
interface IP address, click
Optional: Test by
using the agent to perform a PXE boot in a controlled test environment. For
details about setting up the PXE Boot request, see the documentation about
"Adding and Configuring PXE Boot Requests".