IBM RS/6000 SP, Руководство пользователя

Страница: 451 / 480

Appendix E. SP/CES Tools
427
7. Wrappers
setup_server
setup_server is a crucial function since it is called on every node and BIS
(Boot/Install Server) on bootup and is central to configuring and maintaining the
SP NIM environment. For more detailed information on boot/install servers, refer
to PSSP: Administration Guide, SA22-7348.
The setup_server Perl source code configures and controls a huge portion of the
SPs environment but is smaller than expected with less than 1000 lines of code.
This is because setup_server (since PSSP 2.2) is modular. It can be broken
down into stand-alone pieces of code (wrappers), such as delnimmast, allnimres,
mkconfig, and so forth. Each one of these wrappers is called as part of
setup_server but can also be called manually from the command line.
Exactly how
setup_server
runs these wrappers depends upon how the
environment is currently configured and the changes that have to be made, such
as allocating some resources or building an extra boot install server.
setup_server only has a single allowable flag with which it can be called:
-
h.
However, all this does is display the help text.
setup_server runs on every boot of a node, boot/install server, or the CWS
(called from /etc/rc.sp). However, setup_server will also need to run manually
whenever we are changing an element of a node install.
For example, if the node is set to install and we set it back to disk, we need to run
setup_server
so that it will deallocate the NIM resources, remove the nodes
entry in /etc/tftpboot, unexport the exported file systems, and so on.
System Data Repository
The System Data Repository (SDR) is something unique to the SP. It contains
SP-specific information in a central repository that resides on the CWS. It is held
in plain ASCII text format under the /spdata/sys1/sdr/ directory structure.
All nodes within the SP system may need to query data or change an attribute of
the SDR at some point; so, on the CWS, the sdrd daemon runs to handle
requests from the nodes and itself (the CWS) and listens on TCP port 5712.
The activity of this daemon is also written to a log in
/var/adm/SPlogs/sdr/sdrlog.syspar_ip_addr.pid where syspar_ip_addr is the IP
address of the system partition, and pid is the process identifier (PID) of the SDR
daemon.