Table of Contents
Advertisement
Configuration utilities
ccmd
ccmd
ccmd (Complex Configuration Management Daemon) is a daemon that
maintains a database of information about the V2500/V2600 hardware.
ccmd also monitors the system and reports any significant changes in
system status. It supports multiple nodes, multiple complexes and nodes
that have the same node number.
There are two types of related information in the database: node
information (node numbers, IP addresses and scan data) and
configuration data which is initialized by POST. The node information is
scanned from the hardware and processed with the aid of data files at
/spp/data. The POST configuration data is required so that certain
scan based utilities can emulate various hardware functions.
ccmd periodically sends out a broadcast to determine what nodes are
available. If ccmd can not talk to a node that it previously reached, it
sends a response to the console and the log. If it establishes or re-
establishes contact, or if a node powers up, ccmd reads hardware
information from the node and interrogates it through scan to determine
the node configuration. From this data, a complete database is built on
the SSP that will be used for all scan based diagnostics.
Once running, ccmd checks for power-up, power-down, reset, error, and
environmental conditions on regular intervals. If at any time ccmd
detects a change in the configuration, it changes the database, updates
the /spp/data/complex.cfg file, sets up a directory in /spp/data for
each complex and initializes a node_#.pwr file for each node in the
complex specific subdirectory.
If ccmd detects an error condition, it invokes an error analysis tool
(hard_logger) that logs and diagnoses error conditions. After an error
is investigated, ccmd reboots the node or complex associated with the
error. The reboot operation can be avoided with the use of the
autoreset [complex] on|off|chk utility in /spp/scripts.
ccmd is listed in /etc/inittab as a process that should run continuously. It
may be started manually, but since it kills any previous copies at start-
up, diagnostic processes that may be running will be orphaned. Only one
copy of ccmd may run on a SSP.
100
Chapter 5
Advertisement
Table of Contents
