scinstall(1M)

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO

NAME

scinstall– install Sun Cluster software and initialize new cluster nodes

SYNOPSIS

scinstall -p [-v]
/usr/cluster/bin/scinstall -r [-N cluster-member] [-G mount-point]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -i [-k] [-d cdimage-dir] [-s srvc[,…]] [-M patch-options] [-F[-C clustername][-T authentication-options][-G [special | mount-point][-o only one]][-A adapter-options][-B junction-options][-m cable-options][-w netaddr-options]]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -i [-k] [-d cdimage-dir] [-s srvc[,…]] [-M patch-options] [-N cluster-member[-C clustername][-G {special | mount-point}][-A adapter-options][-B junction-options][-m cable-options]]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -a install-dir [-d cdimage-dir]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -c jumpstart-dir -h nodename [-d cdimage-dir] [-s srvc[,…]] [-M patch-options] [-F[-C clustername][-G {special | mount-point}]] [-T authentication-options[-A adapter-options][-B junction-options][-m cable-options][-w netaddr-options]]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -c jumpstart-dir -h nodename [-d cdimage-dir] [-s srvc[,…]] [-M patch-options] [-N cluster-member [-C clustername][-G {special | mount-point}][-A adapter-options][-B junction-options][-m cable-options]]
/SunCluster_3.1/Sol_release/Tools/scinstall cdrom-mnt-pt -u upgrade-mode [upgrade-options] [-M patch-options]

DESCRIPTION

The scinstall command performs a number of Sun Cluster node initialization, installation, and upgrade tasks, as follows.

• The “install” form (-i) of scinstall installs and initializes a node as a new Sun Cluster member. It either establishes the first node in a new cluster (-F) or adds a node to an already-existing cluster (-N).

  Always run this form of the scinstall command from the node that is being installed or added to the cluster.

• The “set up install server” form (-a) of scinstall creates an install-dir on any Solaris machine from which the command is run and then copies a Sun Cluster CD-ROM to that directory. Typically, you would create the target directory on an NFS server which has also been set up as a Solaris install server (see the setup_install_server(1M) man page).

• The “add install client” form (-c) of scinstall establishes the given nodename as a custom JumpStart client in the jumpstart-dir on the machine from which the command is run. Typically, the jumpstart-dir is located on an already-established Solaris install server configured to JumpStart the Solaris nodename install client (see the add_install_client(1M) man page).

• The “remove” form (-r) of scinstall removes cluster configuration information and uninstalls Sun Cluster software from a cluster node.

• The “upgrade” form (-u) of scinstall, which has several modes and options, upgrades a Sun Cluster node. Always run this form of the scinstall command from the node being upgraded.

• The “print release” form (-p) of scinstall prints release and package versioning information for the Sun Cluster software installed on the node from which the command is run.

Without options, the scinstall command attempts to run in interactive mode.

Run all forms of the scinstall command other than the “print release” form (-p) as superuser.

The scinstall command is located in the Tools directory on the Sun Cluster CD-ROM. If the Sun Cluster CD-ROM has been copied to a local disk, cdrom-mnt-pt is the path to the copied Sun Cluster CD-ROM image. The SUNWscu software package also includes a copy of the scinstall command.

OPTIONS

Basic Options

The following options direct the basic form and function of the command.

None of the following options can be combined on the same command line.

-a

Specifies the “set up install server” form of the scinstall command. This option is used to create an install-dir on any Solaris machine from which the command is run and then copy a Sun Cluster CD-ROM to that directory.

If the install-dir already exists, the scinstall command returns an error message. Typically, the target directory is created on an NFS server which has also been set up as a Solaris install server (see the setup_install_server(1M) man page).

-c

Specifies the “add install client” form of the scinstall command. This option establishes the given nodename as a custom JumpStart client in the jumpstart-dir on the machine from which you issued the command.

Typically, the jumpstart-dir is located on an already-established Solaris install server that is configured to JumpStart the nodename install client (see the add_install_client(1M) man page).

This form of the command enables fully-automated cluster installation from a JumpStart server by helping to establish each cluster node, or nodename, as a custom JumpStart client on an already-established Solaris JumpStart server. The command makes all necessary updates to the rules file in the given jumpstart-dir. In addition, special JumpStart class files and finish scripts that support cluster initialization are added to the jumpstart-dir, if they are not already installed. Configuration data that is used by the Sun Cluster-supplied finish script is established for each node that you set up by using this method.

Users can customize the Solaris class file that the -c option to the scinstall command installs by editing the file directly in the normal way. However, it is always important to ensure that the Solaris class file defines an acceptable Solaris installation for a Sun Cluster node. Otherwise, the installation might need to be restarted.

Both the class file and finish script installed by this form of the command are located in the following directory:

jumpstart-dir/autoscinstall.d/3.1

The class file is installed as autoscinstall.class, and the finish script is installed as autoscinstall.finish.

For each cluster nodename that you set up with the -c option as an automated Sun Cluster JumpStart install client, this form of the command sets up a configuration directory as the following:

jumpstart-dir/autoscinstall.d/nodes/nodename

Options for specifying Sun Cluster node installation and initialization are saved in files located in these directories. Never edit these files directly.

You can customize the JumpStart configuration in the following ways:

• You can add a user-written finish script as the following file name:

  jumpstart-dir/autoscinstall.d/nodes/nodename/finish

  The scinstall command runs the user-written finish scripts after it runs the finish script supplied with the product.

• If the directory

  jumpstart-dir/autoscinstall.d/nodes/nodename/archive

  exists, the scinstall command copies all files in that directory to the new installation. In addition, if an etc/inet/hosts file exists in that directory, scinstall uses the hosts information found in that file to supply name-to-address mappings when a name service (NIS/NIS+/DNS) is not used.

• If the directory

  jumpstart-dir/autoscinstall.d/nodes/nodename/patches

  exists, the scinstall command installs all files in that directory by using the patchadd(1M) command. This directory is intended for Solaris software patches and any other patches that must be installed before Sun Cluster software is installed.

You can create these files and directories individually or as links to other files or directories that exist under jumpstart-dir.

See the add_install_client(1M) man page and related JumpStart documentation for more information about how to set up custom JumpStart install clients.

Run this form of the command from the install-dir (see the -a form of scinstall) on the JumpStart server that you use to initialize the cluster nodes.

Before you use the scinstall command to set up a node as a custom Sun Cluster JumpStart client, you must first establish each node as a Solaris install client. The JumpStart directory you specify with the -c option to the add_install_client command should be the same directory you specify with the -c option to scinstall. However, the scinstall jumpstart-dir does not have a server component to it, since you must run the scinstall command from a Solaris JumpStart server.

To remove a node as a custom Sun Cluster JumpStart client, simply remove it from the rules file.

-i

Specifies the “install” form of the scinstall command. This form of the command can both install Sun Cluster software and initialize a node as a new cluster member. The new node is the node from which you issue the scinstall command.

If the -F option is used with -i, scinstall establishes the node as the first node in a new cluster.

If the -o option is used with the -F option, scinstall establishes a single-node cluster.

If the -N option is used with -i, scinstall adds the node to an already-existing cluster.

If the -s option is used and the node is an already-established cluster member, only the specified srvc (data service) is installed.

-p

Prints release and package versioning information for the Sun Cluster software installed on the node from which the command is run. This is the only form of scinstall that you can run as a non-root user.

-r

Removes cluster configuration information and uninstall Sun Cluster software from a cluster node. You can then reinstall the node or remove the node from the cluster. You must run the command on the node that you uninstall, from a directory that is not used by the cluster software, and the node must be in non-cluster mode.

-u upgrade-mode

Upgrades Sun Cluster software on the node from which you invoke the scinstall command. The upgrade form of scinstall will have several different modes of operation, depending upon the releases involved, as specified by upgrade-mode. See Upgrade Options below for information specific to the type of upgrade that you intend to perform.

Additional Options

You can combine additional options with the basic options to modify the default behavior of each form of the command. Refer to the SYNOPSIS section for additional details about which of these options are legal with which forms of scinstall.

The following additional options are supported:

-d cdimage-dir

Specifies an alternate directory location for finding the CD-ROM images of the Sun Cluster product and unbundled Sun Cluster data services. The -d option is legal with all forms of the command other than the interactive and “print release” (-p) forms.

If the -d option is not specified, the default directory is the CD-ROM image from which the current instance of the scinstall command is started.

-h nodename

Specifies the node name. The -h option is only legal with the “add install client” (-c) form of the command.

The nodename is the name of the cluster node (that is, JumpStart install client) to set up for custom JumpStart installation.

-k

Specifies that scinstall will not install Sun Cluster software packages. The -k option is only legal with the “install” (-i) form of the command.

If this option is not specified, the default behavior is to install any Sun Cluster packages that are not already installed.

-s srvc[,…]

Specifies a data service. The -s option is only legal with the “install” (-i), “upgrade” (-u), or “add install client” (-c) forms of the command to install or upgrade the specified srvc (data service package).

If a data service package cannot be located, a warning message is printed, but installation otherwise continues to completion.

-v

Prints release information in verbose mode. The -v option is only legal with the “print release” (-p) form of the command to specify verbose mode.

In the verbose mode of “print release,” the version string for each installed Sun Cluster software package is also printed.

-F [config-options]

Establishes the first node in the cluster. The -F option is only legal with the “install” (-i), “upgrade” (-u), or “add install client” (-c) forms of the command.

The installation of secondary nodes will be blocked until the first node is fully installed, instantiated as a cluster member, and prepared to perform all necessary tasks associated with adding new cluster nodes. If the -F option is used with the -o option, a single-node cluster is installed and no additional nodes can be added during the installation process.

-N cluster-member [config-options]

Specifies the cluster member. The -N option is only legal with the “install” (-i), “add install client” (-c), “remove” (-r), or “upgrade” (-u) forms of the command.

• When used with the -i, -c, or -u option, the -N option is used to add additional nodes to an existing cluster. The given cluster-member is typically the name of the first cluster node established for the cluster. However, it can be the name of any cluster node already participating as a cluster member. The node being initialized is added to the cluster of which cluster-member is already an active member. The process of adding a new node to an existing cluster involves updating the configuration data on the given cluster-member, as well as creating a copy of the configuration database onto the local file system of the new node.

• When used with the -r option, the -N option specifies the cluster-member, which can be any other node in the cluster that is an active cluster member. The scinstall command contacts the specified cluster-member to make updates to the cluster configuration. If the -N option is not given, scinstall makes a best attempt to find an existing node to contact.

Configuration Options

The config-options which can be used with the -F option or -N cluster-member option are as follows.

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Tools/scinstall 
{-i | -c jumpstart-dir -h nodename} 
[-F
   [-C clustername]
   [-G {special | mount-point} ]
   [-T authentication-options]
   [-A adapter-options]
   [-B junction-options]
   [-m endpoint=[this-node]:name[@port],endpoint=[node:]name[@port] ]
   [-o]
   [-w netaddr-options]
]

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Tools/scinstall 
{-i | -c jumpstart-dir -h nodename} 
[-N cluster-member
   [-C clustername]
   [-G {special | mount-point} ]
   [-A adapter-options]
   [-B junction-options]
   [-m endpoint=cable-options]
]

-m cable-options

Specifies the cluster interconnect connections. This option is only legal when the -F or -N option is also given.

The -m option helps to establish the cluster interconnect topology by configuring the cables connecting the various ports found on the cluster transport adapters and junctions. Each new cable configured with this form of the command establishes a connection from a cluster transport adapter on the current node to either a port on a cluster transport junction or an adapter on another node already in the cluster.

If you specify no -m options, the scinstall command attempts to configure a default cable. However, if you configure more than one transport adapter or junction with a given instance of scinstall, it is not possible for scinstall to construct a default. The default is to configure a cable from the singly-configured transport adapter to the singly-configured (or default) transport junction.

The -m cable-options are as follows.

-m endpoint=[this-node]:name[@port],endpoint=[node:]name[@port]

You must always specify two endpoint options with each occurrence of the -m option. The name component of the option argument specifies the name of either a cluster transport adapter or a cluster transport junction at one of the endpoints of a cable.

• If you specify the node component, the name is the name of a transport adapter.

• If you do not specify the node component, the name is the name of a transport junction.

If you specify no port component, the scinstall command attempts to assume a default port name. The default port for an adapter is always 0. The default port name for a junction endpoint is equal to the node ID of the node being added to the cluster.

Refer to the individual cluster transport adapter and cluster transport junction man pages for more information regarding port assignments and other requirements (for instance, scconf_transp_adap_hme(1M) scconf_transp_adap_eri(1M), scconf_transp_adap_sci(1M), scconf_transp_jct_etherswitch(1M), and scconf_transp_jct_dolphinswitch(1M)).

Before you can configure a cable, you must first configure the adapters and/or junctions at each of the two endpoints of the cable (see -A and -B).

The first line in the synopsis given at the beginning of this subsection attempts to express that at least one of the two endpoints must be an adapter on the node being installed. And so, it is not necessary to include this-node explicitly. The following is an example of adding a cable:

-m endpoint=:hme1,endpoint=switch1

In this example, port 0 of the hme1 transport adapter on this node (the node that scinstall is installing) is cabled to a port on transport junction switch1. The port used on switch1 defaults to the node number of this node.

-o

Specifies installation and configuration of a single node cluster. This option is only legal when the -i and -F options are also given.

Other - F options are supported, but not required. If the cluster name is not given, the name of the node is used as the cluster name. Transport configuration options may be given, and will be stored in the CCR. The -G option is only required if the global devices file system is not the default (/globaldevices). Once a single-node cluster is installed, it is not necessary to configure a quorum device or to disable installmode.

-w netaddr-options

Specifies the private network address. This option is only legal when the -F option is also given.

Use this option to specify a private network address (networks(4) and, optionally, netmasks(4)) for use on the private network. You should only need to use this option when the default private network address collides with an address already in use within the enterprise. The default network address is 172.16.0.0, with a default netmask of 255.255.0.0.

The -w netaddr-options are as follows:

–w netaddr=netaddr[,netmask=netmask]

netaddr=netaddr

Specifies the private network address. The default netaddr for the private interconnect, or cluster transport, is 172.16.0.0. The last two octets of this address must always be zero.

[netmask=netmask]

Specifies the netmask. The default netmask for the private interconnect is 255.255.0.0. The last two octets of the netmask must always be zero, and there cannot be any holes in the mask.

-A adapter-options

Specifies the transport adapter and, optionally, its transport type. This option is only legal when the -F or -N option is also given.

Each occurrence of the -A option configures a cluster transport adapter attached to the node from which scinstall is run.

If no -A options are given, an attempt is made to use a default adapter and transport type. The default transport type is dlpi. In Sun Cluster 3.1 for SPARC, the default adapter is hme1.

When the adapter transport type is dlpi, you do not need to specify the trtype suboption. In this case, you can use either of the following two forms to specify the -A adapter-options:

–A [trtype=type,]name=adaptername[,other-options] -A adaptername

[trtype=type]

Specifies the transport type of the adapter. Use the trtype option with each occurrence of the -A option for which you want to specify the transport type of the adapter. Examples of transport types are rsm and dlpi (see the sctransp_rsm(7P) and sctransp_dlpi(7P) man pages).

The default transport type is dlpi.

name=adaptername

Specifies the adapter name. You must use the name subobtion with each occurrence of the -A option to specify the adaptername. An adaptername is constructed from a device name, immediately followed by a physical-unit number (for instance, hme0).

If you specify no other suboptions with the -A option, you can specify the adaptername as a standalone argument to the -A option (that is, -A adaptername).

[other-options]

Specifies additional adapter options. When a particular adapter provides any other options, you can specify them by using the -A option. Refer to the individual cluster transport adapter man pages (for instance, scconf_transp_adap_hme(1M), scconf_transp_adap_eri(1M), and scconf_transp_adap_sci(1M)) for information on any special options that you might use with them.

-B junction-options

Specifies the transport junction. This option is only legal when the -F or -N option is also given.

Each occurrence of the -B option configures a cluster transport junction. Examples of such devices can include, but are not limited to, Ethernet switches, other switches of various types, and rings.

If you specify no -B options, scinstall attempts to add a default junction at the time that the first node is instantiated as a cluster node. When you add additional nodes to the cluster, no additional junctions are added by default. However, you can add them explicitly. The default junction is named switch1, and it is of type switch.

When the junction type is type switch, you do not need to specify the type suboption. In this case, you can use either of the following two forms to specify the -B junction-options.

-B [type=type,]name=name[,other-options] -B name

If a cluster transport junction is already configured for the given junction name, scinstall prints a message and ignores the -B option.

If you use directly-cabled transport adapters, you are not required to configure any transport junctions. To avoid configuring default transport junctions, use the following special -B option:

-B type=direct

[type=type]

Specifies the transport junction type. You can use the type option with each occurrence of the -B option. Ethernet switches and Dolphin SCI switches are examples of cluster transport junctions which are both of the junction type switch (see the scconf_transp_jct_etherswitch(1M) andscconf_transp_jct_dolphinswitch(1M) man pages).

You can specify the type suboption as direct to suppress the configuration of any default junctions. Junctions do not exist in a transport configuration made up of only directly-connected transport adapters. When the type suboption is set to direct, you do not need to use the name suboption.

name=name

Specifies the transport junction name. Unless the type is direct, you must use the name subobtion with each occurrence of the -B option to specify the transport junction name. The name can be up to 256 characters in length and is made up of either letters or digits, with the first character being a letter. Each transport junction name must be unique across the namespace of the cluster.

If no other suboptions are needed with -B, you can give the junction name as a standalone argument to -B (that is, -B name).

[other-options]

Specifies additional transport junction options. When a particular junction type provides other options, you can specify them with the -B option. Refer to the individual cluster transport junction man pages (for instance, scconf_transp_jct_etherswitch(1M)) and scconf_transp_jct_dolphinswitch(1M)) for information on any special options that you might use with them.

-C clustername

Specifies the name of the cluster. This option is only legal when the -F or -N option is also given.

• If the node being installed is the first node in a new cluster, the default clustername is the same as the name of the node being installed (or when upgrading, if it exists, the current cluster's clustername will be used as the default clustername).

• If the node being installed is being added to an already-existing cluster, the default clustername is the name of the cluster to which cluster-member already belongs.

It is an error to specify a clustername that is not the name of the cluster to which cluster-member belongs.

-G {special | mount-point}

Specifies a raw special disk device or a file system for the global-devices mount point. This option is only legal when the -F, -N, or -r option is also given.

• When used with the -F or -N option, the -G option specifies the raw special disk device or the file system mount-point to use in place of the /globaldevices mount point. Each cluster node must have a local file system mounted globally on /global/.devices/node@nodeID before the node can successfully participate as a cluster member. However, since the node ID is not known until the scinstall command is run, scinstall attempts to add the necessary entry to the vfstab(4) file when it does not find a /global/.devices/node@nodeID mount.

  By default, the scinstall command looks for an empty file system mounted on /globaldevices. If such a file system is provided, the scinstall command makes the necessary changes to the vfstab file. These changes create a new /global/.devices/node@nodeID mount point and remove the default /globaldevices mount point. However, if /global/.devices/node@nodeID is not mounted and an empty /globaldevices file system is not provided, the -G option must be given to specify the raw special disk device or the file system mount-point to use in place of /globaldevices.

  If a raw special disk device name is given and /global/.devices/node@nodeID is not mounted, a file system is created on the device using the newfs(1M) command. It is an error to supply the name of a device with an already-mounted file system.

  As a guideline, this file system should be at least 512 Mbytes in size. If this partition or file system is not available, or is not large enough, it might be necessary to reinstall the Solaris operating environment.

• When used with the -r option, the -G mount-point option specifies the new mount-point name to use to restore the former /global/.devices mount point. If the -G option is not specified, the mount point is renamed /globaldevices by default.

-T authentication-options

Specifies node-authentication options for the cluster. This option is only legal when the -F option is also given.

Use this option to establish authentication policies for nodes that attempt to add themselves to the cluster configuration. Specifically, when a machine requests that it be added to the cluster as a cluster node, a check is made to determine whether or not the node has permission to join. If the joining node has permission, it is authenticated and allowed to join the cluster.

You can only use the -T option with the scinstall command when you set up the very first node in the cluster. If the authentication list or policy needs to be changed on an already-established cluster, use the scconf(1M) command.

The default is to allow any machine to add itself to the cluster.

The -T authentication-options are as follows.

-T node=nodename[,…][,authtype=authtype]

node=nodename[,…]

Specifies node names to add to the node authentication list. You must specify at least one node suboption to the -T option. This option is used to add node names to the list of nodes that are able to install and configure themselves as nodes in the cluster. If the authentication list is empty, any node can request that it be added to the cluster configuration. However, if the list has at least one name in it, all such requests are authenticated using the authentication list. You can modify or clear this list of nodes at any time by using the scconf(1M) command from one of the active cluster nodes.

[authtype=authtype]

Specifies the type of node authentication. The only currently-supported authtypes are des and sys (or, unix). If no authtype is specified, sys is the default.

If you will you specify des (Diffie-Hellman) authentication, first add entries to the publickey(4) database for each cluster node to be added before you run the -T option to the scinstallcommand.

You can change the authentication type at any time by using the scconf(1M) command from one of the active cluster nodes.

Patch Options

The -M option installs the patches in the patch directory during the scinstall process by using the patchadd(1M) command. The patch-options to -M are as follows.

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Tools/scinstall [-M patchdir=dirname[,patchlistfile=filename]]


---

Note –

If you use the -M option, the scinstall command ignores the patch directory inside the jumpstart-dir directory.

---

patchdir=dirname

Specifies the path to the directory that contains the patches required for Sun Cluster. This directory must be on a file system that is accessible by all nodes.

If you are including Solaris patches in the /var/cluster/patches directory, view the /etc/release file to see the exact version of Solaris software that is installed on a node.

patchlistfile=filename

Specifies a file containing the list of patches to install. If you do not specify a patch list file, the scinstall command will install all the patches in the dirname directory, including tarred, jarred, and zipped patches.

For information on creating a patch list file, refer to the patchadd(1M) manual page.

Upgrade Options

The -u update option upgrades a cluster node to a later Sun Cluster software release. The upgrade-options to -u update are as follows.

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Tools/scinstall [-u update] [-s {srvc[,…] | all}] [-d cdimage-dir] [ -O ] [-S { interact | testaddr=testipaddr@adapter[,testaddr=…]} ]


-s {srvc[,…] | all}

Upgrades data services. If the -s option is not specified, only cluster framework software is upgraded. If the -s option is specified, only the specified data services are upgraded.

The following suboption to the -s option is specific to the update mode of upgrade:

all

Upgrades all data services.

This suboption to -s is only legal with the update mode.

This suboption upgrades all data services currently installed on the node, except those data services for which an update version does not exist in the update release.

The -s option is not compatible with the -S test IP address option.

-O

Overrides the hardware validation.

-S {interact | testaddr=testipaddr@adapter[,testaddr=…]

Specifies test IP addresses. This option allows the user either to direct the command to prompt the user for the required IP Network Multipathing addresses or to supply a set of IP Network Multipathing test addresses on the command line for the conversion of NAFO to IP Network Multipathing groups. See “IP Network Multipathing (Overview)” in System Administration Guide: IP Services for additional information on IP Network Multipathing.

---

Note –

The -S option is only required when one or more of the NAFO adapters in pnmconfig is not already converted to use IP Network Multipathing.

---

The suboptions of the -S option are the following:

interact

Prompt the user to supply one or more IP Network Multipathing test addresses individually.

testaddr=testipaddr@adapter

Allow the user to specify one or more IP Network Multipathing test addresses without being prompted for the list.

testipaddr

The IP address or hostname (in the /etc/inet/hosts file) that will be assigned as routable, no-failover and deprecated test IP address to the adapter. IP Network Multipathing uses test addresses to detect failures and repairs. See “Administering Multipathing Groups With Multiple Physical Interfaces” in System Administration Guide: IP Services for additional information on configuring test IP addresses.

adapter

The name of the NAFO network adapter to be added to an IP Network Multipathing group.

It is illegal to combine both the interact and the testaddr suboptions on the same command line.

EXAMPLES

---

Example 1 Installing and Initializing a Two-Node Cluster




The following sequence of commands installs and initializes a typical two-node cluster. Insert the framework CD-ROM and issue the following commands:

node1# cd /cdrom/cdrom0/SunCluster_3.1/Sol_8/Tools node1# ./scinstall -i -F node2# cd /cdrom/cdrom0/SunCluster_3.1/Sol_8/Tools node2# ./scinstall -i -N node1

---

---

Example 2 Installing and Initializing a Single-Node Cluster




The following commands install and initialize a single-node cluster, with all defaults accepted. Insert the framework CD-ROM and issue the following commands:

# cd /cdrom/cdrom0/SunCluster_3.1/Sol_8/Tools # ./scinstall -i -F -o

---

---

Example 3 Setting Up a Solaris Install Server




The following sequence of commands arranges to set up a Solaris install server to install and initialize a three-node SCI–PCI cluster. Insert the framework CD-ROM and issue the following commands:

installserver# cd /cdrom/cdrom0/SunCluster_3.1/Sol_9/Tools installserver# ./scinstall -a /export/sc3.1 installserver# cd /export/sc3.1/SunCluster_3.1/Sol_9/Tools installserver# ./scinstall –c /export/jumpstart \ -h node1 -F -A hme2 installserver# ./scinstall –c /export/jumpstart \ -h node2 -N node1 -A hme2 installserver# ./scinstall –c /export/jumpstart \ -h node3 -N node1 -A hme2

---

---

Example 4 Upgrading the Framework and Data Service Software




The following sequence of commands upgrades the framework and data service software of a cluster to the next Sun Cluster release. Do the following actions on each cluster node.

Insert the framework CD-ROM and issue the following commands:

ok> boot -x # cd /cdrom/cdrom0/SunCluster_3.1/Sol_9/Tools # ./scinstall -u update -S interact # cd / # eject /cdrom/cdrom0

Insert the Agents CD-ROM and issue the following commands:

# /usr/cluster/bin/scinstall -u update -s all \ -d /cdrom/cdrom0 # reboot

---

---

Example 5 Uninstalling a Node




The following sequence of commands places the node in non-cluster mode, then removes Sun Cluster software and configuration information from the cluster node, renames the global-devices mount point to the default name /globaldevices, and performs cleanup:

ok> boot -x node4# cd / node4# /usr/cluster/bin/scinstall -r

---

EXIT STATUS

The following exit values are returned:

0

Successful completion.

non-zero

An error occurred.

FILES

cdrom-mnt-pt/.cdtoc

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Product/.clustertoc

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Product/.order

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Product/.packagetoc

cdrom-mnt-pt/SunCluster_3.1/Sol_release/Tools/defaults

cdrom-mnt-pt/srvc/Product/.clustertoc

cdrom-mnt-pt/srvc/Product/.order

cdrom-mnt-pt/srvc/Product/.packagetoc

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Availability	Solaris CD-ROM, SUNWscu
Interface Stability	Evolving

SEE ALSO

add_install_client(1M), clustertoc(4), netmasks(4), networks(4), newfs(1M), order(4), packagetoc(4), patchadd(1M), sccheck(1M), scconf(1M), scconf_transp_adap_bge(1M), scconf_transp_adap_eri(1M), scconf_transp_adap_ge(1M), scconf_transp_adap_hme(1M), scconf_transp_adap_qfe(1M), scconf_transp_adap_sci(1M), scconf_transp_jct_dolphinswitch(1M), scconf_transp_jct_etherswitch(1M), sctransp_dlpi(7P), sctransp_rsm(7P), setup_install_server(1M)

Sun Cluster 3.1 5/03 Software Installation Guide

System Administration Guide: IP Services

Sun Cluster 3.1  Last Revised 22 Apr 2003

NAME | SYNOPSIS | DESCRIPTION | OPTIONS | EXAMPLES | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO