Technical article 110031

Documentation for aasd configuration under SCO OpenServer 5.0.5.

OpenServer 5.0.5

Written · Last revised

Problem

As described in ta110030, the man page for configuring aasd is not available in SCO OpenServer Enterprise Release 5.0.5.

Solution

This problem has been resolved in SCO OpenServer Release 5.0.6.

For earlier releases, the following pages, from UnixWare 7, may be used to configure aasd and aasd.conf.

                             aasd(1Mtcp)
_________________________________________________________________
aasd -- Address Allocation Server
Synopsis
in.aasd [ -D debug_level ]
Description

The Address Allocation Server daemon, aasd, allocates addresses to network services, such as DHCP, which need to assign temporary addresses. It manages the information about allocated addresses, such as the service requesting the address and for how long the address is reserved.

If the configuration file (/etc/aasd.conf) exists, aasd starts automatically. The configuration file defines the address pools available for allocation along with server parameters.

aasd maintains an address database of current allocation information in memory and records changes to the database in a transaction log stored on disk. At startup, aasd rebuilds the database from the transaction log. aasd will compress the transaction log when the log reaches a configurable size.

At a ``checkpoint'' interval, aasd constructs a transaction log which
represents the current allocation information and stores this log as a
checkpoint file. aasd will rebuild the address database with the most
recent checkpoint file if the current transaction log is lost or
corrupted. The checkpoint interval along with the number and location
of the checkpoint files are configurable parameters.
Options
-D debug_level
     Sets the debug_level variable that controls the amount of
     debugging messages generated. For example, -D 1 will set the
     debugging level to 1. Recognized values are 0, 1, 2, and 3 or
     greater. Zero generates no messages and 1 to 3 generate
     increasing amounts of messages. Specifying an integer greater
     than 3 has the same result as specifying 3. If aasd is running
     in ``standalone mode'' and you specify 3 or greater, messages
     will be directed to standard error (not to syslog) and aasd
     does not go into the background.

The Address Allocation Server Configuration Manager does not support an alternate configuration database to aasd.conf nor does it support an alternative location for this file.

References
aasd.conf(4tcp), dhcpd(1Mtcp), bootpd(1Mtcp),
  _________________________________________________________________

UnixWare 7.0.1 Release -- September 11, 1998 1998 The Santa Cruz Operation, Inc. All rights reserved.

********************************************************************
                           aasd.conf(4tcp)
_________________________________________________________________
aasd.conf -- Address Allocation Server configuration file format
Synopsis
# Server parameter settings
keyword value
...
# Address pool definitions
pool name:address_type {
address|address_range
...
}
Description
The default configuration file for the Address Allocation Server (AAS)
is /etc/aasd.conf. The file has a text-based, line-oriented
format, and is composed of lines containing keyword-value pairs that
set server parameters, and address pool definitions.

Each line of the configuration file must be no more than 1023 characters in length, including the newline character. There is no facility for line continuation.

Spaces or tabs are required between lexical elements, and may be used at the beginning and end of lines arbitrarily. Blank lines may appear anywhere.

Comments are denoted by a ``#'' preceded by a space or tab or the
beginning of a line. Everything from the ``#'' to the end of the line
is ignored.
Server parameter settings

The Address Allocation Server supports several operating parameters that can be set in the configuration file using keyword-value pairs. The defined keywords are described below. database_dir Absolute path Directory in which the address server stores and looks for the live database file. max_db_size The size in bytes at which the server will automatically compress the database. The value must be an integer, optionally followed by k or K to multiply by 1024, or m orM to multiply by 1048576. checkpoint_dir An absolute pathname that defines the directory in which the server stores checkpoint files. checkpoint_intvl The interval in seconds between checkpoints. The value must be an integer. num_checkpoints The number of most recent checkpoint files to save. password Password used for authentication on a network connection. There can be any number of passwords defined, each of which is a valid password. The value must be a string, an must not contain any quote marks.

Address pool definitions

The pool keyword defines an address pool with name name of type address_type. Currently, the Address Allocation Server only supports the INET address type for IPv4 addresses. Each pool can define individual addresses or address ranges separated by spaces or tabs. An address range is specified by two addresses separated by only a dash (no spaces or tabs).

The following is an example pool definition: pool subnet35:INET { 152.122.35.48 152.122.35.60 152.122.35.64-152.122.35.95 152.122.35.128-152.122.35.191 }

References
aasd(1Mtcp), dhcpd(1Mtcp), dhcpd.conf(4tcp), ppptalk(1M)
  _________________________________________________________________

UnixWare 7.0.1 Release -- September 11, 1998 1998 The Santa Cruz Operation, Inc. All rights reserved.

See also

ta110030, "SCOHelp for SCO OpenServer 5.0.5 refers to DHCP man pages that don't exist."

From the Xinuos technical article database, record 110031. Reproduced with permission. The original is at www.sco.com/ta/110031, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.