If the lease cannot be renewed, the dhcpagent daemon takes down the interface at the end of the lease time. It automatically starts when the system boots, renegotiates leases, and stops when the system shuts down. You cannot manually start and stop the dhcpagent daemon. However, you can use the ifconfig command as superuser on the client system to affect the client's management of the network interface if necessary.
This might be useful when you change information that you want a client to use immediately, such as when you add IP addresses or change the subnet mask. Request network configuration information only — The command ifconfig interface dhcp inform causes dhcpagent to issue a request for network configuration parameters, with the exception of the IP address.
This is useful for situations where the network interface has a valid IP address, but the client system needs updated network options. For example, this might be useful if you do not use DHCP to manage IP addresses, but do use it to configure hosts on the network. Request a lease extension — The command ifconfig interface dhcp extend causes dhcpagent to issue a request to renew the lease.
This happens automatically, but you might want to use this command if you change the lease time and want clients to use the new lease time immediately rather than waiting for the next attempt at lease renewal.
Release the IP address — The command ifconfig interface dhcp release causes dhcpagent to relinquish the IP address used by the network interface. This happens automatically when the lease expires. You might want to issue this command if the lease time is long and you need to take down the network interface for an extended period of time or you want to remove the system from the network. Drop the IP address — The command ifconfig interface dhcp drop causes dhcpagent to take down the network interface without informing the DHCP server that it is doing so.
This enables the client to use the same IP address when it reboots. Ping the network interface — The command ifconfig interface dhcp ping lets you test to see if the interface is under the control of DHCP. The display indicates the following: If an IP address has been bound to the client. Times when the lease was obtained, when it expires, and when attempts to renew it will or did start. These names are examples of clients you might have on your network. Write a script that creates the options and macros by using the dhtadm command.
See Writing a Script That Uses dhtadm to Create Options and Macros for information about how to write scripts that create these options and macros. Note that the total size of the vendor options that are provided to a particular client must not exceed bytes, including the option codes and length information.
Generally, you should pass the minimum amount of vendor information needed. You should use short path names in options that require path names. If you create symbolic links to long paths, you can use the shorter link names. Add the clients that you want to install with DHCP as install clients of your network installation server. For information about how to add a client to an install server, see Chapter 4, Installing From the Network Overview. Configure your DHCP server.
Note - Roles contain authorizations and privileged commands. Notice that the vendor client classes are only suggested values. You should create classes to indicate the actual client types that need to obtain Solaris installation parameters from the DHCP service. The values for code, data type, granularity, and maximum are most likely to need modification. See Table and Table for the values.
You can now create macros to pass the options to network installation clients, as explained in the following procedure. Create the DHCP options that you want to use in your macro. To include another macro, type Include as the option name and type the macro name as the option value. If you plan to use DHCP in an installation over the network, you need to set up an installation server and add the system as an installation client.
You can create a Korn shell script by adapting the example in Example to create all the options listed in Table and Table and some useful macros. Be sure to change all IP addresses and values contained in quotes to the correct IP addresses, server names, and paths for your network.
As superuser, execute dhtadm in batch mode. Specify the name of the script to add the options and macros to your dhcptab. For example, if your script is named netinstalloptions , type the following command.
For more information about how to use the dhtadm command, see dhtadm 1M. For more information about the dhcptab file, see dhcptab 4. Search Scope:. Preconfiguring System Configuration Information Tasks 3. Next Solaris Express build will probably contain one of the long awaited features: Solaris NewBoot architecture for x86 systems. The procedure described below describes steps necessary for PXE booting and installing a client with Grub bootloader, which is the default one in Solaris since Nevada b Here is the full list of server-side components you need to have in order to be able to PXE-boot and install a client machine over network:.
Here you have to look at your topology and decide, which networks are going to be served by your DHCP server. On our server it looks like this:. Follow the instructions from this page: Creating a profile for networked system. This command will also enable TFTP server on your machine.
0コメント