A P P E N D I X B - Setting up DHCP to Configure the IP Addresses for Solaris Blades

A P P E N D I X B

Setting up DHCP to Configure the IP Addresses for Solaris Blades

This appendix supplements the instructions in the Solaris Advanced Installation Guide and the DHCP Administration Guide. It enables you to complete the configuration of the Network Install Server and the DHCP server on your data network so that the server blades on the system chassis can receive their IP addresses dynamically.

The instructions assume that you have added the Solaris image to a Network Install Server and that you have a DHCP server on the data network.

This appendix contains the following sections:

Section B.1, Network Install Server Tasks

Section B.2, DHCP Server Tasks

Section B.3, Server Blade Tasks

B.1 Network Install Server Tasks

On the Network Install Server, run add_install_client with the -d option.

This command copies a DHCP-capable inetboot file from the Solaris image to the /tftpboot directory. To execute the command, type:

# cd path/Solaris_8/Tools

# ./add_install_client -d -s installserv:/images/2.8 -c

configsrv:/config -p configsrv:/config SUNW.Serverblade1 sun4u

To enable SUNW.Serverblade1 in the DHCP server, add an entry to the server with the following data:

Install server      (SinstNM)  : installserv

Install server IP   (SinstIP4) : 192.168.160.12

Install server path (SinstPTH) : /images/2.8

Root server name    (SrootNM)  : installserv

Root server IP      (SrootIP4) : 192.168.160.12

Root server path      (SrootPTH) : /images/2.8/Solaris_8/Tools/Boot

Profile location    (SjumpsCF) : configsrv:/config

sysidcfg location   (SsysidCF) : configsrv:/config

where path is the location of the Solaris image on the Network Install Server. (Note that the second command in the above example has wrapped onto the next line.) The output above uses sample IP data.

B.2 DHCP Server Tasks

1. On the DHCP server create the options that you want passed to the blades during the Solaris Jumpstart.

(This is the information that would be gathered from the /etc/bootparams file during a non-DHCP Jumpstart.)

The options you need to create are listed in TABLE B-1.


Option name	Description
`SrootIP4`	IP address of root server
`SrootNM`	Hostname of root server
`SrootPTH`	Path to the boot image (for example, `/images/2.8/Solaris_8/Tools/Boot`)
`SinstIP4`	IP address of the Network Install Server
`SinstNM`	Hostname of Network Install Server
`SsysidCF`	Location of the `sysidcfg` file (for example, `configsrv:/config`)
`SjumpsCF`	Location of profile and `rules.ok` directory (for example, `configsrv:/config`)
`SbootFIL`	Path to the kernel (for example, `/platform/sun4u/kernel/sparcv9/uni`)
`Sterm`	Terminal type used during the install

The following are sample commands for creating the options listed in TABLE B-1:

# dhtadm -A -s SrootIP4 -d 'Vendor=SUNW.Serverblade1,2,IP,1,1'

# dhtadm -A -s SrootNM -d 'Vendor=SUNW.Serverblade1,3,ASCII,1,0'

# dhtadm -A -s SrootPTH -d 'Vendor=SUNW.Serverblade1,4,ASCII,1,0'

# dhtadm -A -s SbootFIL -d 'Vendor=SUNW.Serverblade1,7,ASCII,1,0'

# dhtadm -A -s SinstIP4 -d 'Vendor=SUNW.Serverblade1,10,IP,1,1'

# dhtadm -A -s SinstNM -d 'Vendor=SUNW.Serverblade1,11,ASCII,1,0'

# dhtadm -A -s SinstPTH -d 'Vendor=SUNW.Serverblade1,12,ASCII,1,0'

# dhtadm -A -s SsysidCF -d 'Vendor=SUNW.Serverblade1,13,ASCII,1,0'

# dhtadm -A -s SjumpsCF -d 'Vendor=SUNW.Serverblade1,14,ASCII,1,0'

# dhtadm -A -s Sterm -d 'Vendor=SUNW.Serverblade1,15,ASCII,1,0'

2. Create macros containing the options you require (including the options you created in the Step 1).


Macro name	Macro contents (macros can contain other macros)
`Solaris`	`SrootIP4, SrootNM, SinstIP4, SinstNM, Sterm, SjumpsCF, SsysidCF`
`sparc`	`SrootPTH, SinstIP4`
`sun4u`	`Solaris, sparc`
SUNW.Serverblade1	`SbootFIL`, `sun4u`
network name`*`	`Subnet, Router, Broadcst, and BootSrvA`

*network name is the IP address that identifies the network containing the clients. You need to create one of these macros for each client subnet except the subnet containing the primary interface of the DHCP server.

The following are sample commands for creating the macros you require:

# dhtadm -A -m Solaris -d ':SrootIP4=192.168.160.12:SrootNM="bootsrv":SinstIP4=192.168.160.15:SinstNM="installsrv":Sterm="xterm":SjumpsCF="configsrv:/config":SsysidCF="configsrv:/config":'

# dhtadm -A -m sparc -d ':SrootPTH="/images/2.8/Solaris_8/Tools/Boot":SinstPTH="/images/2.8":'

# dhtadm -A -m sun4u -d ':Include=Solaris:Include=sparc:'

# dhtadm -A -m SUNW.Serverblade1 -d ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":Include=sun4u:'

# dhtadm -A -m 192.168.160.0 -d ':Subnet=255.255.255.0:Router=192.168.160.254:Broadcst=192.168.160.255:BootSrvA=192.168.160.12:'

3. Add the client's host name and IP address to the hosts database (that is, to /etc/hosts).

4. Map the SUNW.Serverblade1 macro to the client.

Type:

# pntadm -A dhcpclient01 -i 01MACaddress -m SUNW.Serverblade1 -s DHCP server network name

where:

MACaddress is the client's MAC address,

DHCP server is the DHCP server's hostname, and

network name is the IP address that identifies the network containing the client (note that the sample comand line above has wrapped onto the next line).

B.3 Server Blade Tasks

When the network environment is configured to provide the server blades with two IP addresses each, follow the instructions in this section. These instructions assume that the server blade you are configuring has booted from the network and been provided with an IP configuration for its primary (ce0) interface.

1. From the System Controller's sc> prompt, access the blade console.

Type:

sc> console sn

where n is the slot number for the blade you are configuring.

2. From Solaris prompt, type:

# ifconfig ce1 plumb

3. Finally, type:

# ifconfig ce1 auto-dhcp up