Sun Cluster Data Service for DHCP Guide for Solaris OS

Planning the Sun Cluster HA for DHCP Installation and Configuration

This section contains the information you need to plan your Sun Cluster HA for DHCP installation and configuration.

Configuration Restrictions

Consider the restrictions in this section to plan the installation and configuration of Sun Cluster HA for DHCP.This section provides a list of software and hardware configuration restrictions that apply to Sun Cluster HA for DHCP only.

Caution –

Your data service configuration might not be supported if you do not observe these restrictions.

For restrictions that apply to all data services, see the Sun Cluster Release Notes.

The Sun Cluster HA for DHCP data service can be configured only as a failover service – DHCP cannot operate as a scalable service and therefore the Sun Cluster HA for DHCP data service can be configured only to run as a failover service.
Sun Cluster Carrier-Grade —You can only use the Sun Cluster Carrier-Grade options in a Sun Cluster Carrier-Grade deployment.
DHCP server – DHCP must operate as a DHCP server and not as a relay host.
DHCP single instance per resource – You can configure only one DHCP instance within Sun Cluster, but you can have multiple DHCP networks within that DHCP instance.
DHCP network table – The DHCP network table can be text or binary files. You can mount it as either a Failover File System (FFS) or a Global File System (GFS).

Note –
It is considered best practice to mount Global File Systems with the /global prefix and to mount Failover File Systems with the /local prefix.

Configuration Requirements

These requirements apply to Sun Cluster HA for DHCP only. You must meet these requirements before you proceed with your Sun Cluster HA for DHCP installation and configuration.

Caution –

Your data service configuration might not be supported if you do not adhere to these requirements.

DHCP component and its dependencies —You can configure the Sun Cluster HA for DHCP data service to protect a DHCP component. This component and its dependencies are described.

Table 3 DHCP components and their dependencies (via -> symbol)


Componet	Description
DHCP server`(Mandatory)`	-> SUNW.HAStoragePlus resource The SUNW.HAStoragePlus resource manages the DHCP File System Mount points and ensures that DHCP is not started until these are mounted.

The DHCP component has a configuration and registration file under /opt/SUNWscdhc/util. These files allow you to register the DHCP components with Sun Cluster.

Example 1 DHCP configuration and registration file for Sun Cluster

# cd /opt/SUNWscdhc
# 
# ls -l util/*
total 6
-rwxr-xr-x   1 root     sys         1094 Dec 20 14:44 dhcp_config
-rwxr-xr-x   1 root     sys          514 Dec 20 14:44 dhcp_register
#
# more util/*
::::::::::::::
util/dhcp_config
::::::::::::::
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# This file will be sourced in by dhcp_register and the parameters
# listed below will be used.
#
# These parameters can be customized in (key=value) form
#
#        RS - name of the resource for the application
#        RG - name of the resource group containing RS
#      PORT - name of any port number, as it's ignored
#        LH - name of the LogicalHostname SC resource
#   NETWORK - name of the DHCP Network, separated with a /
#               where each network is made up of the following
#               <network>@<nafo or ipmp>@node number
#
# Additional parameters to Sun Cluster Carrier-Grade Edition
#  USE_CGTP - ff CGTP is being used (TRUE/FALSE)
#  USE_STATIC_DHCP - ff static DHCP tables should be used (TRUE/FALSE)
#  TEST_CLIENTID - the mac-address of the test-client
#  TFTPTESTFILE - path to Tftp testfile
#
#       The following two examples illustrate sample parameters
#       for DHCP on a 2 node cluster (tequila/sunrise)
#
#       Sun Cluster 3.0 using nafo
#
#       NETWORK=192.168.100.0@nafo0@1/192.168.100.0@nafo0@2
#
#       Sun Cluster 3.1 using ipmp
#
#       NETWORK=192.168.100.0@ipmp0@1/192.168.100.0@ipmp0@2
#
RS=
RG=
PORT=
LH=
NETWORK=
HAS_RS=

# Options to Sun Cluster Carrier-Grade Edition

USE_CGTP=FALSE
USE_STATIC_DHCP=FALSE
TEST_CLIENTID=
TFTPTESTFILE=
::::::::::::::

Sun Cluster HA for DHCP data service – Requires Solaris 8 7/01 (or later) with patches 109077-12 (or later) and 111302-02 (or later) or Solaris 9.

Note –

Ensure that /etc/inet/dhcpsvc.conf is consistent on all nodes within Sun Cluster that will host the DHCP service, or is linked on a directory on a Cluster File System.

/etc/inet/dhcpsvc.conf parameters – You must set the following /etc/inet/dhcpsvc.conf parameters:

DAEMON_ENABLED is always set to true.
PATH points to the Cluster File System for the DHCP network table.
RUN_MODE is always set to SERVER
RESOURCE is set to either SUNWbinfiles or SUNWfiles.

You cannot set the following parameter in etc/inet/dhcpsvc.conf unless Sun Cluster Carrier-Grade Edition is deployd.
INTERFACE can't be used

Note –

For responses to DHCP requests, use SUNWbinfiles for the DHCP network table to achieve the best DHCP performance.

Configuration Requirements for Sun Cluster Carrier-Grade deployment

These requirements apply to Sun Cluster HA for DHCP only. You must meet these requirements before you proceed with your Sun Cluster HA for DHCP installation and configuration.

Caution –

Your data service configuration might not be supported if you do not adhere to these requirements.

DHCP component and its dependencies —You can configure the Sun Cluster HA for DHCP data service to protect a DHCP component.

The DHCP component has a configuration and registration file under /opt/SUNWscdhc/util. These files allow you to register the DHCP components with Sun Cluster.

Example 2 DHCP configuration and registration file for Sun Cluster

# cd /opt/SUNWscdhc
# 
# ls -l util/*
total 6
-rwxr-xr-x   1 root     sys         1094 Dec 20 14:44 dhcp_config
-rwxr-xr-x   1 root     sys          514 Dec 20 14:44 dhcp_register
#
# more util/*
::::::::::::::
util/dhcp_config
::::::::::::::
#
# Copyright 2003 Sun Microsystems, Inc.  All rights reserved.
# Use is subject to license terms.
#
# This file will be sourced in by dhcp_register and the parameters
# listed below will be used.
#
# These parameters can be customized in (key=value) form
#
#        RS - name of the resource for the application
#        RG - name of the resource group containing RS
#      PORT - name of any port number, as it's ignored
#        LH - name of the LogicalHostname SC resource
#   NETWORK - name of the DHCP Network, separated with a /
#               where each network is made up of the following
#              <network>@<nafo or ipmp>@node number
#
# Additional parameters to Sun Cluster Carrier-Grade Edition
#  USE_CGTP - ff CGTP is being used (TRUE/FALSE)
#  USE_STATIC_DHCP - ff static DHCP tables should be used (TRUE/FALSE)
#  TEST_CLIENTID - the mac-address of the test-client
#  TFTPTESTFILE - path to Tftp testfile
#
#       The following two examples illustrate sample parameters
#       for DHCP on a 2 node cluster (tequila/sunrise)
#
#       Sun Cluster 3.0 using nafo
#
#       NETWORK=192.168.100.0@nafo0@1/192.168.100.0@nafo0@2
#
#       Sun Cluster 3.1 using ipmp
#
#       NETWORK=192.168.100.0@ipmp0@1/192.168.100.0@ipmp0@2
#
RS=
RG=
PORT=
LH=
NETWORK=
HAS_RS=

# Options to Sun Cluster Carrier-Grade Edition

USE_CGTP=FALSE
USE_STATIC_DHCP=FALSE
TEST_CLIENTID=
TFTPTESTFILE=
::::::::::::::

Sun Cluster HA for DHCP data service – Requires Solaris 8 7/01 (or later) with patches 109077-12 (or later) and 111302-02 (or later) or Solaris 9.

Note –

Ensure that /etc/inet/dhcpsvc.conf is consistent on all nodes within Sun Cluster that will host the DHCP service, or is linked on a directory on a Cluster File System.

If Tftp daemon check is being used you must create a non-zero testfile in defined tftpdirectory on all the nodes in the cluster that will use DHCP.

/etc/inet/dhcpsvc.conf parameters – You must set the following /etc/inet/dhcpsvc.conf parameters:

DAEMON_ENABLED is always set to true.
PATH points to the Cluster File System for the DHCP network table or local filesystem, if static DHCP is beeing used.
INTERFACE must be used, if Carrier-Grade Transport Procol is beeing used.
RUN_MODE is always set to SERVER
ICMP_VERIFY is always set to false, if active testing is being used.
RESOURCE is set to either SUNWbinfiles or SUNWfiles.