Manual Pages
Table of Contents
na_setup - Updates node configuration.
setup
setup queries the user for the node configuration
parameters such as hostname, IP address, and timezone. It
installs new versions of /etc/rc, /etc/hosts,
/etc/exports, /etc/resolv.conf, /etc/hosts.equiv, and
/etc/dgateways to reflect the new configuration. When
setup completes, the configuration files have been been
updated, but their new contents do not take effect until
the node is rebooted (see na_reboot(1)). The old contents
of the configuration files are saved in rc.bak,
exports.bak, resolv.conf.bak, hosts.bak, hosts.equiv.bak,
and dgateways.bak.
One piece of information that setup requests is the name
and IP address for adminhost. In /etc/exports, adminhost
is granted root access to / so that it can access and
modify the configuration files in /etc. All other NFS
clients are granted access only to /home. If no adminhost
is specified, then all clients are granted root access to
/. This is not recommended for sites where security is a
concern.
If an adminhost is specified, then an additional line is
added to the /etc/hosts file to point the default mailhost
to the adminhost. This is used by the autosupport daemon
(see na_autosupport(8)) to send email notification.
If a default gateway is provided to setup, it will be used
in /etc/rc to specify a default route (see na_route(1)),
and will also be used as the first entry in
/etc/dgateways.
The hostname that is provided to setup is used to
construct default names for all of the configured network
interfaces. Ethernet interfaces are given names
hostname-0, hostname-1, and so on.
- /etc
- directory of node configuration and
administration files
- /etc/rc
- system initialization command script
- /etc/exports
- directories exported by the server
- /etc/hosts
- host name data base
- /etc/hosts.equiv
- list of hosts and users with rsh
permission
- /etc/resolv.conf
- list of DNS name servers
- /etc/dgateways
- list of preferred default gateways for
routed
/etc/nsswitch.conf list of preferred name services
After a takeover, you can enter the setup command in
partner mode to configure the failed node. However, only
the network interfaces on the failed node that were taken
over appear in the prompts displayed by setup. For
example; if the e1 interface on the failed node was not
configured and taken over by the live node, the setup
command does not prompt you for the IP address of the e1
interface.
When run from a vfiler context, (for example via the
vfiler run command), setup operates on the concerned
vfiler. If the vfiler is not vfiler0, setup only allows
the configuration of a subset of parameters that are
meaningful for a vfiler. Specifically, the operator is
prompted for the IP address bindings of the vfiler, the
name and IP address of the vfiler's adminhost, the
vfiler's DNS configuration and its NIS configuration. The
command allows the configuration of the password of the
root user of the vfiler. Running this command also sets up
default versions of the /etc/exports, /etc/hosts and
/etc/hosts.equiv files. A command line version of setup
can also be used in the context of a vfiler. This version
has the form:
setup [-e <ifname>:<ipaddress>:<netmask>,...] [-d <DNS
domaname>:<DNS server IP 1>:...] [-n <NIS
domainname>:<NIS server1>:...] [-a <ipaddress>
<name>:<ipaddress>] [-p <root password>]
The -e option allows the bindings of the IP addresses of
the vfiler to be created. The -d option allows the
specification of a DNS domain name and the IP addresses of
one or more DNS servers. The -n option allows the
specification of an NIS domain name and the IP addresses
of one or more NIS servers (or the use of broadcast
discovery by using * as the NIS server name). The -a
option allows the admin hosts name and IP address to be
specified. Finally, the -p option allows the password of
the root user of this vfiler to be set.
na_ifconfig(1), na_partner(1), na_reboot(1), na_vfiler(1),
na_dgateways(5), na_exports(5), na_hosts(5),
na_hosts.equiv(5), na_resolv.conf(5), na_rc(5),
na_autosupport(8)
Some Ethernet boards determine the media type
automatically. It is not necessary to specify the media
type for them, but it is best to do so anyway in case the
board is replaced with one that does not determine media
type automatically.
As the /etc/rc file is rewritten after running the setup
command in vfiler0, all aliases, mtu and vlans configured
earlier in the /etc/rc file will be lost. If these
settings are required, they will have to be added to the
/etc/rc file again before reboot. It is recommended to
verify the /etc/rc file for these configurations after
running the setup command.
Table of Contents
