JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris DHCP Service Developer's Guide     Oracle Solaris 11 Express 11/10
search filter icon
search icon

Document Information

Preface

1.  Overview of Solaris DHCP Data Access Architecture

2.  Architecture Features for Module Writers

Function Categories

Considerations for Multithreading

Synchronizing Access to File-System-Based Containers

Avoiding Update Collisions

Naming the Public Module and Data Store Containers

Public Module Name

Container Name

Container Record Formats

Passing Data Store Configuration Data

Upgrading Container Versions

Data Service Configuration and DHCP Management Tools

Public Module Management Bean API Functions

getComponent()

Synopsis

Description

getDescription()

Synopsis

Description

getPath()

Synopsis

Description

getAdditional()

Synopsis

Description

Public Module Management Bean Packaging Requirements

3.  Service Provider Layer API

4.  Code Samples and Testing

Index

Container Record Formats

The Solaris DHCP service uses two types of DHCP containers: the dhcptab container and the DHCP network container.

The dhcptab container holds DHCP configuration data, described in the dhcptab man page. Only one instance of a dhcptab container is maintained in the DHCP service.

dhcptab records are passed between the Framework Configuration Layer and the Service Provider Layer by way of an internal structure, dt_rec_t. The include file /usr/include/dhcp_svc_public.h shows the structure.

Your public module must ensure that there are no duplicate dhcptab records. No two records can have identical key field values.

DHCP network containers contain IP address records, described in the dhcp_network man page. These containers are named to indicate the data store and the dotted IP address of the network to which the IP addresses belong, such as 10.0.0.0. Any number of DHCP network containers may exist, one for each network supported by the DHCP service.

DHCP network records are passed between the Framework Configuration Layer and the Service Provider Layer by way of an internal structure, dn_rec_t. The include file /usr/include/dhcp_svc_public.h shows the structure.

Your public module must ensure that there are no duplicate network container records. No two records can have identical key field values.