Planning and Configuring HP-UX DCE 1.9

Chapter 6
Configuring HP-UX DCE Cells
Configuring Cells Using dce_config
61
If you want to remove and reconfigure a client, first unconfigure and remove the client from the cell, then
reconfigure the client. You may remove and reconfigure a client without reconfiguring the other members of a
cell.
NOTE You cannot use the dce_config UNCONFIGURE option to remove a Master Security Server or
Initial Directory Server system from a cell. You must either use the DCM to do this, or
reconfigure the entire cell. You can use the dce_config UNCONFIGURE option to remove
Additional CDS Server or Replica Security Server systems from a cell.
1. On the system you want to affect, run dce_config.
2. Select REMOVE from the DCE Main Menu:
DCE Main Menu (on hostname)
selection: 5 (REMOVE)
Attempting to stop all running DCE daemons...
Successfully stopped all running DCE daemons...
Attempting to remove all remnants of previous DCE configurations...
Successfully removed all remnants of previous DCE configurations for all components...
Re-initializing the dce_config environment
3. If you are unconfiguring an entire cell, repeat steps 1 and 2 on each cell member.
4. If you want to reconfigure the cell, do so as described starting with the section “Initial Cell Configuration”
on page 52". Reconfigure the cell only after you have run the REMOVE option on each cell member.
dce_config Error and Message Logging
dce_config and its component scripts write log messages containing errors, warnings, action summaries,
and action details. Some log messages are written to stdout; log messages are also written to
/var/opt/dce/config/dce_config.log.
Log messages have different priorities, based on content, which determine both where the messages are
logged and how they are formatted. Table 6-1 describes log message types (in priority order from highest to
lowest), their format, and their content.
Table 6-1 dce_config Message Categories
Priority Format Content
ERROR ERROR:<message> Result of an operation that was not as
expected, and is probably fatal. Always
followed by a prompt for user to continue or
quit.
WARNING WARNING:<message> Information the user should be aware of
before proceeding. Always non-fatal. Always
logged to display and to log file. Always
followed by a prompt for user to continue or
quit unless DO_CHECKS="n".
SUMMARY S:******<message> High-level summary of action being taken
or action completed. Always logged to log
file. Also logged to display unless
DISPLAY_THRESHOLD is WARNING or
ERROR.