sm_config(1M) Maintenance Commands sm_config(1M)
NAME
sm_config - SCI adapter configuration utility for clusters
SYNOPSIS
sm_config [-t] -f filename
AVAILABILITY
SUNWsma
INTERFACE CLASSIFICATION
Sun Private
DESCRIPTION
sm_config is the SCI adapter configuration utility. It acts
as a client of sm_configd(1M) daemon. sm_config contacts
the sm_configd(1M) daemon on all the hosts and works in a
distributed fashion to retrieve the adapter inventory and
configure the adapter cards on these hosts. The configura-
tion process involves programming -
(a) the adapter Node-Ids into the adapter's flash memory
and
(b) IP addresses into the cards.
Upon successful completion, a configuration file named
/etc/sma.config is installed on all the hosts in the clus-
ter. This file contains a snapshot view of the cluster
members, switches, adpaters etc. It also installs a file
called /etc/sma.ip which contains the IP addresses of all
the SCI interfaces in the cluster.
OPTIONS
-t starts sm_config in debug mode.
-f filename takes the filename as an input file. The
input file template is available in
/opt/SUNWsma/bin directory as (a)
template.pdb (for PDB clusters) and (b)
template.hpc (for HPC clusters). These tem-
plate files provide detailed information
about the type of information required by
sm_config.
This input file template contains 8 sections -
1. Cluster configuration section - specifies the type of
cluster being configured (PDB or HPC). A sample template
for this section -
Cluster is configured as = PDB
2. Host names section - requires the names of all the hosts
in the cluster. If the hosts in the cluster do not have
full public-net connectivity then the name of the host
without connectivity must be preceded by "_%". This indi-
cates to sm_config not to contact this host via the public-
net.
For example, consider a case where host2 in a cluster of
host1, host2, host3 and host4 lacks public-net connectivity.
When sm_config is started with the following template_1, it
will contact host1, host3 and host4 over the net and config-
ure their SCI interfaces. However, it is now the user's
responsibility to run sm_config on host2 in the stand-alone
mode using template_2 below.
template_1 - used on host1, host3 and host4 :-
HOST 0 = host1
HOST 1 = _%host2
HOST 2 = host3
HOST 3 = host4
template_2 - used on host2 :-
HOST 0 = _%host1
HOST 1 = host2
HOST 2 = _%host3
HOST 3 = _%host4
A caveat to keep in mind when running sm_config in stand-
alone mode is that, sm_config cannot guarantee the coherency
of the /etc/sma.config generated during the different invo-
cations (for eg. in the above case - /etc/sma.config on
host2 versus the ones on host1, host3 and host4) if the user
were to supply inconsistent input data for the two cases.
3. Number of Switches section - Accepts input for the total
no. of switches in the cluster.
However, if the cluster being configured has some unused SCI
adapters meant for use in the future, then the cluster
should be configured as it would look in the future, when
all the adapters are fully connected. For instance, a 1-
switch cluster containing 4 hosts with 2 adapters on each
(second set of adapters idle), which will later evolve into
a 2-switch cluster should be configured as a 2-switch clus-
ter.
This ensures that when the cluster evolves to its final form
in future, new communication channels (SMA sessions) will be
created on the new links (say, through a new switch) on the
fly. This eliminates having to run sm_config later and
rebooting the machine. A detailed example of this is given
in the input template file.
A sample template for this section -
Number of Switches in cluster = 2
4. Number of Direct Links section - Accepts input for the
total no. of direct SCI links in the cluster. A sample tem-
plate for this section -
Number of Direct Links in cluster = 2
5. Allow Rings section - Whether the cluster supports confi-
gurations with multiple hosts connected to the same port of
the same switch. A sample template for this section -
Allow Rings in cluster (Y/N)? = N
6. Adapter information section - Accepts detailed informa-
tion for each adapter on each host. A sample template for
this section is -
host 0 :: adp 0 is connected to = switch 0 :: port 0
host 0 :: adp 1 is connected to = link 1 :: endpt 0
7. Network IP address section - Accepts the first 3 octets
(network) of the IP address for a particular switch or link.
A sample template for this section -
Network IP address for Switch 0 = 204.152.65
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
sm_configd daemon.
SunOS 5.5.1 Last change: 30 March 1997
|
