急问：装了cluster以后就ping不通那台机器了，怎么办

wilda

我的安装过程如下：

Download suncluster-3_1_904-sparc.zip and unzip
Install sun_web_console and sun_cluster(framework?)
cd /export/home/cluster/Solaris_sparc/Product/sun_web_console/2.1
./setup
cd /export/home/cluster/Solaris_sparc/Product/sun_cluster
./installer

cd /export/home/cluster/Solaris_sparc/Product/sun_cluster/Solaris_9/Packages
pkgadd -d . SUNWscrif
pkgadd -d . SUNWsci
pkgadd -d . SUNWscid
pkgadd -d . SUNWscidx
pkgadd -d . SUNWscrdt

Modify PATH and MANPATH entries in /etc/skel/.profile
a. Set the PATH to include /usr/sbin/ and /usr/cluster/bin/.
b. Set the MANPATH to include /usr/cluster/man/.

Establishing the Cluster
Enable remote shell (rsh(1M)) or secure shell (ssh(1)) access for superuser to all cluster nodes.
/usr/cluster/bin/scinstall

  *** Main Menu ***

    Please select from one of the following (*) options:

      * 1) Install a cluster or cluster node
        2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node

      * ?) Help with menu options
      * q) Quit

    Option:  1

  *** Install Menu ***

    Please select from any one of the following options:

        1) Install all nodes of a new cluster
        2) Install just this machine as the first node of a new cluster
        3) Add this machine as a node in an existing cluster

        ?) Help with menu options
        q) Return to the Main Menu

    Option:  2

  *** Installing just the First Node of a New Cluster ***


    This option is used to establish a new cluster using this machine as
    the first node in that cluster.

    Once the cluster framework software is installed, you will be asked
    for the name of the cluster. Then, you will have the opportunity to
    run sccheck(1M) to test this machine for basic Sun Cluster
    pre-configuration requirements.

    After sccheck(1M) passes, you will be asked for the names of the
    other nodes which will initially be joining that cluster. In
    addition, you will be asked to provide certain cluster transport
    configuration information.

    Press Control-d at any time to return to the Main Menu.


    Do you want to continue (yes/no) [yes]?  

  >;>;>; Software Patch Installation <<<

    If there are any Solaris or Sun Cluster patches that need to be added
    as part of this Sun Cluster installation, scinstall can add them for
    you. All patches that need to be added must first be downloaded into
    a common patch directory. Patches can be downloaded into the patch
    directory either as individual patches or as patches grouped together
    into one or more tar, jar, or zip files.

    If a patch list file is provided in the patch directory, only those
    patches listed in the patch list file are installed. Otherwise, all
    patches found in the directory will be installed. Refer to the
    patchadd(1M) man page for more information regarding patch list files.

    Do you want scinstall to install patches for you (yes/no) [yes]?  no

  >;>;>; Cluster Name <<<

    Each cluster has a name assigned to it. The name can be made up of
    any characters other than whitespace. Each cluster name should be
    unique within the namespace of your enterprise.

    What is the name of the cluster you want to establish [suncluster]?  

  >;>;>; Check <<<

    This step allows you to run sccheck(1M) to verify that certain basic
    hardware and software pre-configuration requirements have been met.
    If sccheck(1M) detects potential problems with configuring this
    machine as a cluster node, a report of failed checks is prepared and
    available for display on the screen. Data gathering and report
    generation can take several minutes, depending on system
    configuration.

    Do you want to run sccheck (yes/no) [yes]?  no

  >;>;>; Cluster Nodes <<<

    This Sun Cluster release supports a total of up to 16 nodes.

    Please list the names of the other nodes planned for the initial
    cluster configuration. List one node name per line. When finished,
    type Control-D:

    Node name:  tbs139
    Node name:  tbs125
    Node name (Control-D to finish):  ^D


    This is the complete list of nodes:

        tbs139
        tbs125

    Is it correct (yes/no) [yes]?  

  >;>;>; Authenticating Requests to Add Nodes <<<

    Once the first node establishes itself as a single node cluster,
    other nodes attempting to add themselves to the cluster configuration
    must be found on the list of nodes you just provided. You can modify
    this list using scconf(1M) or other tools once the cluster has been
    established.

    By default, nodes are not securely authenticated as they attempt to
    add themselves to the cluster configuration. This is generally
    considered adequate, since nodes which are not physically connected
    to the private cluster interconnect will never be able to actually
    join the cluster. However, DES authentication is available. If DES
    authentication is selected, you must configure all necessary
    encryption keys before any node will be allowed to join the cluster
    (see keyserv(1M), publickey(4)).

    Do you need to use DES authentication (yes/no) [no]?  

  >;>;>; Network Address for the Cluster Transport <<<

    The private cluster transport uses a default network address of
    172.16.0.0. But, if this network address is already in use elsewhere
    within your enterprise, you may need to select another address from
    the range of recommended private addresses (see RFC 1597 for details).

    If you do select another network address, bear in mind that the Sun
    Cluster software requires that the rightmost two octets always be
    zero.

    The default netmask is 255.255.0.0. You can select another netmask,
    as long as it minimally masks all bits given in the network address.

    Is it okay to accept the default network address (yes/no) [yes]?  

    Is it okay to accept the default netmask (yes/no) [yes]?  

  >;>;>; Point-to-Point Cables <<<

    The two nodes of a two-node cluster may use a directly-connected
    interconnect. That is, no cluster transport junctions are configured.
    However, when there are greater than two nodes, this interactive form
    of scinstall assumes that there will be exactly two cluster transport
    junctions.

    Does this two-node cluster use transport junctions (yes/no) [yes]?  

  >;>;>; Cluster Transport Junctions <<<

    All cluster transport adapters in this cluster must be cabled to a
    transport junction, or "switch". And, each adapter on a given node
    must be cabled to a different junction. Interactive scinstall
    requires that you identify two switches for use in the cluster and
    the two transport adapters on each node to which they are cabled.

    What is the name of the first junction in the cluster [sw1]?  sw139

    What is the name of the second junction in the cluster [sw2]?  sw125

  >;>;>; Cluster Transport Adapters and Cables <<<

    You must configure at least two cluster transport adapters for each
    node in the cluster. These are the adapters which attach to the
    private cluster interconnect.

    What is the name of the first cluster transport adapter [adapter139]?  

    All transport adapters support the "dlpi" transport type. Ethernet
    adapters are supported only with the "dlpi" transport; however, other
    adapter types may support other types of transport. For more
    information on which transports are supported with which adapters,
    please refer to the scconf_transp_adap family of man pages
    (scconf_transp_adap_hme(1M), ...).

    Is "adapter139" an Ethernet adapter (yes/no) [yes]?  

    The "dlpi" transport type will be set for this cluster.

    Name of the junction to which "adapter139" is connected [sw139]?  

    Each adapter is cabled to a particular port on a transport junction.
    And, each port is assigned a name. You can explicitly assign a name
    to each port. Or, for Ethernet switches, you can choose to allow
    scinstall to assign a default name for you. The default port name
    assignment sets the name to the node number of the node hosting the
    transport adapter at the other end of the cable.

    For more information regarding port naming requirements, refer to the
    scconf_transp_jct family of man pages (e.g.,
    scconf_transp_jct_dolphinswitch(1M)).

    Use the default port name for the "adapter139" connection (yes/no) [yes]?  

    What is the name of the second cluster transport adapter [adapter125]?  

    Name of the junction to which "adapter125" is connected [sw125]?  

    Use the default port name for the "adapter125" connection (yes/no) [yes]?  

  >;>;>; Global Devices File System <<<

    Each node in the cluster must have a local file system mounted on
    /global/.devices/node@<nodeID>; before it can successfully participate
    as a cluster member. Since the "nodeID" is not assigned until
    scinstall is run, scinstall will set this up for you.

    You must supply the name of either an already-mounted file system or
    raw disk partition which scinstall can use to create the global
    devices file system. This file system or partition should be at least
    512 MB in size.

    If an already-mounted file system is used, the file system must be
    empty. If a raw disk partition is used, a new file system will be
    created for you.

    The default is to use /globaldevices.

    Is it okay to use this default (yes/no) [yes]?  

  >;>;>; Automatic Reboot <<<

    Once scinstall has successfully installed and initialized the Sun
    Cluster software for this machine, it will be necessary to reboot.
    After the reboot, this machine will be established as the first node
    in the new cluster.

    Do you want scinstall to reboot for you (yes/no) [yes]?  

  >;>;>; Confirmation <<<

    Your responses indicate the following options to scinstall:

      scinstall -ik \
           -C suncluster \
           -F \
           -T node=tbs139,node=tbs125,authtype=sys \
           -A trtype=dlpi,name=adapter139 -A trtype=dlpi,name=adapter125 \
           -B type=switch,name=sw139 -B type=switch,name=sw125 \
           -m endpoint=:adapter139,endpoint=sw139 \
           -m endpoint=:adapter125,endpoint=sw125 \
           

    Are these the options you want to use (yes/no) [yes]?  

    Do you want to continue with the install (yes/no) [yes]?  


Checking device to use for global devices file system ... done

Initializing cluster name to "suncluster" ... done
Initializing authentication options ... done
Initializing configuration for adapter "adapter139" ... done
Initializing configuration for adapter "adapter125" ... done
Initializing configuration for junction "sw139" ... done
Initializing configuration for junction "sw125" ... done
Initializing configuration for cable ... done
Initializing configuration for cable ... done


Setting the node ID for "tbs139" ... done (id=1)


Checking for global devices global file system ... done
Updating vfstab ... done

Verifying that NTP is configured ... done
Installing a default NTP configuration ... done
Please complete the NTP configuration after scinstall has finished.

Verifying that "cluster" is set for "hosts" in nsswitch.conf ... done

Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done

Verifying that power management is NOT configured ... done

Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done

Ensure network routing is disabled ... done

Log file - /var/cluster/logs/install/scinstall.log.18044


Rebooting ...