Sun Microsystems Sun HPC 3.0, Руководство пользователя

Страница: 56 / 67

(Continuation)
8. Netmask section - Accepts the netmask for the private SCI
sub-nets.
For example, a cluster with less than 15 hosts
per switch should select a netmask of 0xf0 while a cluster
with 15 hosts or more but less than 31 hosts would choose
0xe0. A sample template for this section -
Netmask = f0
USAGE
The root user can start sm_config from the command line
using the -f option to provide an input file to it.
A cluster can have 3 topologies -
(i) Switched - All hosts are connected to each other via
SCI switches. Can have 2 or more hosts.
(ii) Non-switched - Two hosts connected directly via SCI
cables (direct links). Has exactly 2 hosts.
(iii) Hybrid - Contains switches and direct links. Can have
2 or more hosts.
NOTE - At this point, PDB does not support more than two
switches in a cluster (see (i) above), nor does it support
case (iii) from above.
NOTE - sm_config can be run on any host in the cluster, but
it should not be run on multiple hosts simultaneosly (eg.
via cconsole). If this occurs, the results are unpredict-
able - in the worst case, the adapter flash memory might get
programmed with corrupt data.
NOTE - After running sm_config, the system should be
rebooted.
FILES
/opt/SUNWcluster/bin/sm_config
/etc/sma.config
/etc/sma.ip
SEE ALSO
sm_configd(1M)
DIAGNOSTICS
sm_config prints error and warning messages to stderr. If a
fatal error occurs on any host or locally where sm_config is
running, then the process is aborted and no
/etc/sma.config
is generated till the error is rectified. Do not reboot
the machine till a successful run of sm_config has been com-
pleted.
RELEASE NOTES -
If nis+ is being used as the name service then the default
behaviour is to look up the global nis+ map but if that
doesn’t exist, the local /etc/services file is not searched.
This
behaviour is different from the default nis behaviour.
In this scenario inetd will be unable to start the
(continued)
46
Sun HPC 3.0 SCI Guide
♦
June 1999, Revision A