- 论坛徽章:
- 0
|
"did" driver major number set to 300
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
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done
Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.042006154016
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ... done
Ensure network routing is disabled ... done
Network routing has been disabled on this node by creating /etc/notrouter.
Having a cluster node act as a router is not supported by Sun Cluster.
Please do not re-enable network routing.
Log file - /var/cluster/logs/install/scinstall.log.2140
② 将sys-2作为第二节点加入到cluster中
#cd/cdrom/suncluster_31_u3_sol_sparc/Solaris_sparc/Product/sun_cluster/Solaris_9/Tools
#./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: 3
*** Adding a Node to an Existing Cluster ***
This option is used to add this machine as a node in an already
established cluster. If this is an initial cluster install, there may
only be a single node which has established itself in the new cluster.
Once the cluster framework software is installed, you will be asked
to provide both the name of the cluster and the name of one of the
nodes already in the cluster. Then, sccheck(1M) is run to test this
machine for basic Sun Cluster pre-configuration requirements.
After sccheck(1M) passes, you may 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]?
What is the name of the patch directory [/cdrom/suncluster_31_u3_sol_sparc/Solaris_sparc/Product/sun_cluster/Solaris_8/Packages]?
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 use a patch list file (yes/no) [no]?
>>> Sponsoring Node <<<
For any machine to join a cluster, it must identify a node in that
cluster willing to "sponsor" its membership in the cluster. When
configuring a new cluster, this "sponsor" node is typically the first
node used to build the new cluster. However, if the cluster is
already established, the "sponsoring" node can be any node in that
cluster.
Already established clusters can keep a list of hosts which are able
to configure themselves as new cluster members. This machine should
be in the join list of any cluster which it tries to join. If the
list does not include this machine, you may need to add it using
scconf(1M) or other tools.
And, if the target cluster uses DES to authenticate new machines
attempting to configure themselves as new cluster members, the
necessary encryption keys must be configured before any attempt to
join.
What is the name of the sponsoring node [sys-1]?
>>> Cluster Name <<<
Each cluster has a name assigned to it. When adding a node to the
cluster, you must identify the name of the cluster you are attempting
to join. A sanity check is performed to verify that the "sponsoring"
node is a member of that cluster.
What is the name of the cluster you want to join [test]?
Attempting to contact "sys-1" ... done
Cluster name "xxml" is correct.
Press Enter to continue:
>>> 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
>>> Autodiscovery of Cluster Transport <<<
If you are using Ethernet adapters as your cluster transport
adapters, autodiscovery is the best method for configuring the
cluster transport.
However, it appears that scinstall has already been run at least once
before on this machine. You can either attempt to autodiscover or
continue with the answers that you gave the last time you ran
scinstall.
Do you want to use autodiscovery anyway (yes/no) [no]? yes
Probing .....................
The following connection was discovered:
sys-1:ce1 switch2 sys-2:ce1
Probes were sent out from all transport adapters configured for
cluster node "sys-1". But, they were only received on one of the
network adapters on this machine ("sys-2"). This may be due to
any number of reasons, including improper cabling, an improper
configuration for "sys-1", or a switch which was confused by the
probes.
You can either attempt to correct the problem and try the probes
again or try to manually configure the transport. Correcting the
problem may involve re-cabling, changing the configuration for
"sys-1", or fixing hardware.
Do you want to try again (yes/no) [yes]? no
[H [J [H [J
>>> 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.
Is this a two-node cluster (yes/no) [yes]?
Does this two-node cluster use transport junctions (yes/no) [yes]?
[H [J [H [J
>>> 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 [switch1]?
What is the name of the second junction in the cluster [switch2]?
[H [J [H [J
>>> 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 (help) [ce0]?
Adapter "ce0" is an Ethernet adapter.
The "dlpi" transport type will be set for this cluster.
Name of the junction to which "ce0" is connected [switch1]?
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 "ce0" connection (yes/no) [yes]?
What is the name of the second cluster transport adapter (help) [ce1]?
Adapter "ce1" is an Ethernet adapter.
Name of the junction to which "ce1" is connected [switch2]?
Use the default port name for the "ce1" connection (yes/no) [yes]?
[H [J [H [J
>>> 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]?
[H [J [H [J
>>> Automatic Reboot <<<
Once scinstall has successfully installed and initialized the Sun
Cluster software for this machine, it will be necessary to reboot.
The reboot will cause this machine to join the cluster for the first
time.
Do you want scinstall to reboot for you (yes/no) [yes]?
[H [J [H [J
>>> Confirmation <<<
Your responses indicate the following options to scinstall:
scinstall -ik \
-C xxml \
-N sjz-xxml-1 \
-M patchdir=/cdrom/suncluster_31_u3_sol_sparc/Solaris_sparc/Product/sun_cluster/Solaris_8/Packages \
-A trtype=dlpi,name=ce0 -A trtype=dlpi,name=ce1 \
-m endpoint=:ce0,endpoint=switch1 \
-m endpoint=:ce1,endpoint=switch2 \
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
Installing patches ... failed
scinstall: Problems detected during extraction or installation of patches.
Adding node "sys-2" to the cluster configuration ... done
Adding adapter "ce0" to the cluster configuration ... done
Adding adapter "ce1" to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Adding cable to the cluster configuration ... done
Copying the config from "sys-1" ... done
Copying the cacao keys from "sys-1" ... done
Setting the node ID for "sys-2" ... done (id=2)
Setting the major number for the "did" driver ...
Obtaining the major number for the "did" driver from "sys-1" ... done
"did" driver major number set to 300
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
Adding the "cluster" switch to "hosts" in nsswitch.conf ... done
Verifying that "cluster" is set for "netmasks" in nsswitch.conf ... done
Adding the "cluster" switch to "netmasks" in nsswitch.conf ... done
Verifying that power management is NOT configured ... done
Unconfiguring power management ... done
/etc/power.conf has been renamed to /etc/power.conf.042206104133
Power management is incompatible with the HA goals of the cluster.
Please do not attempt to re-configure power management.
Ensure that the EEPROM parameter "local-mac-address?" is set to "true" ...
[ 本帖最后由 阿毛~ 于 2006-4-25 16:27 编辑 ] |
|