White Papers

Table Of Contents

-rw-rw-rw- 1 root root 119340 May 5 12:25 system_config.xml

[root@sandXD nfs]#

Here is an example of the edited Profile file that is used for this workflow. Observe that unwanted attributes

have been removed. Storage related attributes are added to create a virtual drive and to place

HardDisk.List.1-1 as first device in the BIOS boot order.

<SystemConfiguration Model="PowerEdge R740" ServiceTag="69T0C42" TimeStamp="Tue

May 5 17:26:40 2020">

<Attribute Name="Telnet.1#Enable">Enabled</Attribute>

<Attribute Name="IPv6.1#Enable">Enabled</Attribute>

</Component>

<Attribute Name="RAIDaction">Create</Attribute>

7. On the Linux DHCP/NFS server, update the dhcpd.conf file for Auto Config. After editing the

dhcpd.conf file, save the changes and restart the DHCP services. The example below is the edited

dhcpd.conf file. The entries in bold are added to enable the DHCP server and NFS share to support

Auto Config:

option myname code 43 = text;

subnet 192.168.0.0 netmask 255.255.0.0 {

#default gateway

option routers

192.168.0.1;

option subnet-mask

255.255.255.0;

option nis-domain

"domain.org";

option domain-name

"domain.org";

option domain-name-server

192.168.1.1;

option time-offset

-18000; # Eastern Standard Time

option vendor-class-identifier "iDRAC";

set vendor-string = option vendor-class-identifier;

option myname "-f system_config.xml –i 192.168.0.130 –n /nfs –s 0";

range dynamic-bootp

192.168.0.128 192.168.0.254;

default-lease-time

21600;

max-lease-time

}

43200;

11. On the Linux DHCP/NFS server, view the /var/lib/dhcpd/dhcpd.leases file to ensure that a

DHCP IP address has been assigned to the iDRAC. If the new server is locally accessible and the

server supports an LCD panel, the iDRAC IP address can be verified by using the LCD panel:

[root@sandXD ~]# tail -n 11 /var/lib/dhcpd/dhcpd.leases

lease 192.168.0.125 {