免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
12下一页
最近访问板块 发新帖
查看: 3323 | 回复: 14
打印 上一主题 下一主题

sun cluster 安装新问题!!!!! [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2005-08-13 20:34 |只看该作者 |倒序浏览
sun cluster是否必须用4口网卡
我如果在两台机器上各有两块网卡,能配吗?
能配该如何配置?

msn: chentaobj1979@hotmail.com

论坛徽章:
0
2 [报告]
发表于 2005-08-13 20:38 |只看该作者

sun cluster 安装新问题!!!!!

一个有4口网卡
一个有2个单口网卡
能行不?

论坛徽章:
7
荣誉会员
日期:2011-11-23 16:44:17水瓶座
日期:2013-08-28 21:20:16丑牛
日期:2013-10-02 21:01:462015年迎新春徽章
日期:2015-03-04 09:54:45操作系统版块每日发帖之星
日期:2016-06-05 06:20:0015-16赛季CBA联赛之吉林
日期:2016-06-20 08:24:0515-16赛季CBA联赛之四川
日期:2016-08-18 15:02:02
3 [报告]
发表于 2005-08-13 20:40 |只看该作者

sun cluster 安装新问题!!!!!

最好多看看书,如果这个问题搞不清,那么后面肯定有很多问题也搞不懂。呵呵。

论坛徽章:
0
4 [报告]
发表于 2005-08-13 20:59 |只看该作者

sun cluster 安装新问题!!!!!

我就是看您的帖子配的,主要是现在任务急,您能否指点一下小弟

论坛徽章:
0
5 [报告]
发表于 2005-08-13 21:05 |只看该作者

sun cluster 安装新问题!!!!!

郁闷着呢.还是不行

论坛徽章:
0
6 [报告]
发表于 2005-08-13 21:27 |只看该作者

sun cluster 安装新问题!!!!!

可以的,和网卡的关系不大。

论坛徽章:
0
7 [报告]
发表于 2005-08-13 22:08 |只看该作者

sun cluster 安装新问题!!!!!

没问题的,放心做吧

论坛徽章:
0
8 [报告]
发表于 2005-08-14 00:36 |只看该作者

sun cluster 安装新问题!!!!!

最少3个,建议4个

论坛徽章:
0
9 [报告]
发表于 2005-08-14 17:41 |只看该作者

sun cluster 安装新问题!!!!!

最少3个.2个能安装下去吧.

论坛徽章:
0
10 [报告]
发表于 2005-08-14 20:23 |只看该作者

sun cluster 安装新问题!!!!!

我用两个安装不成功日志如下:


*** Installing all Nodes of a New Cluster ***
Sun Aug 14 15:15:23 CST 2005

    Attempting to contact "test2" ...

    Searching for a remote install method ...

rsh test2 -n "/bin/sh -c '/bin/true; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0
rsh to "test2" - return status 0.

ssh root@test2 -o "BatchMode yes" -o "StrictHostKeyChecking yes" -n "/bin/sh -c '/bin/true; /bin/echo SC_COMMAND_STATUS=\$?'"
No RSA host key is known for test2 and you have requested strict checking.
ssh to "test2" failed.

    The remote shell (see rsh(1)) will be used to install and configure
    this cluster.

    Testing for "/globaldevices" on "test1" ...
    Testing for "/globaldevices" on "test2" ...

rsh test2 -n "/bin/sh -c 'umask 0; /usr/bin/mkdir -m 0755 /var/cluster /var/cluster/run; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=2
mkdir: Failed to make directory "/var/cluster"; File exists
mkdir: Failed to make directory "/var/cluster/run"; File exists

rsh test2 -n "/bin/sh -c '/usr/bin/chgrp sys /var/cluster /var/cluster/run; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

rcp /usr/cluster/lib/scadmin/lib/scinstall_common test2:/var/cluster/run/scinstall_common

rsh test2 -n "/bin/sh -c '/usr/bin/chmod 0555 /var/cluster/run/scinstall_common; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

rcp /usr/cluster/lib/scadmin/lib/cmd_chk_globaldev test2:/var/cluster/run/cmd_chk_globaldev

rsh test2 -n "/bin/sh -c '/usr/bin/chmod 0555 /var/cluster/run/cmd_chk_globaldev; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

rsh test2 -n "/bin/sh -c '/var/cluster/run/cmd_chk_globaldev fs /globaldevices; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

rsh test2 -n "/bin/sh -c '/usr/bin/rm -f /var/cluster/run/scinstall_common /var/cluster/run/cmd_chk_globaldev; /bin/echo
SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

----------------------------------
- Installation and Configuration -
----------------------------------


    Checking installation status ...

rsh test2 -n "/bin/sh -c '/usr/bin/test -f /etc/cluster/.installed; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_test isinstalling; /bin/echo SC_COMMAND_STATUS=\$?'"
"" is not running.
SC_COMMAND_STATUS=0

rsh test2 -n "/bin/sh -c '/usr/bin/test -f /etc/cluster/nodeid; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=1

rsh test2 -n "/bin/sh -c '/usr/bin/test -x /usr/bin/gzcat; /bin/echo SC_COMMAND_STATUS=\$?'"
SC_COMMAND_STATUS=0

    The Sun Cluster software is already installed on "test1".
    The Sun Cluster software is already installed on "test2".

    Starting discovery of the cluster transport configuration.

===========================
test1
===========================
scrconf -n cmd=discover_send,adapters=hme1:hme2,token=suncluster_test,sendcount=30

===========================
test2
===========================

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_autodiscovery suncluster_test 2 30; /bin/echo
SC_COMMAND_STATUS=\$?'"
qfe2:test1:hme1
quit
SC_COMMAND_STATUS=0

===========================

    The following connection was discovered:

        test1:hme1  switch1  test2:qfe2

Only one connection was found for "test2".

    Probes were sent out from all transport adapters configured for this
    node ("test1". But, they were not seen by all of the other nodes.
    This may be due to any number of reasons, including improper cabling
    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, or fixing
    hardware.

===========================
test1
===========================
scrconf -n cmd=discover_send,adapters=hme1:hme2,token=suncluster_test,sendcount=30
scrconf:  expected DL_OK_ACK got DL_ERROR_ACK
scrconf:  expected DL_BIND_ACK got DL_ERROR_ACK
scrconf:  dlbindack:  short response ctl.len:  16

===========================
test2
===========================

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_autodiscovery suncluster_test 2 30; /bin/echo
SC_COMMAND_STATUS=\$?'"
qfe2:test1:hme1
quit
SC_COMMAND_STATUS=0

===========================

    The following connection was discovered:

        test1:hme1  switch1  test2:qfe2

Only one connection was found for "test2".

    Probes were sent out from all transport adapters configured for this
    node ("test1". But, they were not seen by all of the other nodes.
    This may be due to any number of reasons, including improper cabling
    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, or fixing
    hardware.

===========================
test1
===========================
scrconf -n cmd=discover_send,adapters=hme1:hme2,token=suncluster_test,sendcount=30
scrconf:  expected DL_OK_ACK got DL_ERROR_ACK
scrconf:  expected DL_BIND_ACK got DL_ERROR_ACK
scrconf:  dlbindack:  short response ctl.len:  16

===========================
test2
===========================

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_autodiscovery suncluster_test 2 30; /bin/echo
SC_COMMAND_STATUS=\$?'"
qfe2:test1:hme1
quit
SC_COMMAND_STATUS=0

===========================

    The following connection was discovered:

        test1:hme1  switch1  test2:qfe2

Only one connection was found for "test2".

    Probes were sent out from all transport adapters configured for this
    node ("test1". But, they were not seen by all of the other nodes.
    This may be due to any number of reasons, including improper cabling
    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, or fixing
    hardware.

===========================
test1
===========================
scrconf -n cmd=discover_send,adapters=hme1:hme2,token=suncluster_test,sendcount=30
scrconf:  expected DL_OK_ACK got DL_ERROR_ACK
scrconf:  expected DL_BIND_ACK got DL_ERROR_ACK
scrconf:  dlbindack:  short response ctl.len:  16

===========================
test2
===========================

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_autodiscovery suncluster_test 2 30; /bin/echo
SC_COMMAND_STATUS=\$?'"
qfe1:test1:hme1
qfe2:test1:hme1
quit
SC_COMMAND_STATUS=0

===========================

    The following connections were discovered:

        test1:hme1  switch1  test2:qfe1
        test1:hme1  switch1  test2:qfe2

    Completed discovery of the cluster transport configuration.

    Started sccheck on "test1".
    Started sccheck on "test2".

    sccheck failed for "test1".
    sccheck failed for "test2".

===========================
test1
===========================

/usr/cluster/lib/scadmin/lib/cmd_sccheck
sccheck -v1 -o /var/cluster/logs/install/sccheck
sccheck: Requesting explorer data and node report from test1.
sccheck: test1: Explorer finished.
sccheck: test1: Starting single-node checks.
sccheck: test1: Single-node checks finished.
sccheck: One or more checks failed.
sccheck: The greatest severity of all check failures was 2 (MODERATE).
sccheck: Reports are in /var/cluster/logs/install/sccheck.

********************************************************************************
* sccheck(1m)
* Sun(TM) Embedded Knowledge Engine (Sun EKE) (3.0.1) single *
********************************************************************************
          
Report #                      : 8ee016:105b3ef40a3:32767:192.168.0.221
Report Generation Date        : 2005.08.14 at 07:41:05 GMT
Knowledge Automation Engine   : 3.0.1

================================================================================
= SYSTEM INFORMATION                                                           =
================================================================================
System Type   : HOST
Explorer Data : /opt/SUNWexplo/output/explorer.80b1b853.test1-2005.08.14.07.37
HOSTID        : 80b1b853
SERIAL_NUMBER : unspecified
PRODUCT_TYPE  : Sun Microsystems  sun4u Sun (TM) Enterprise 250 (UltraSPARC-II 296MHz)

================================================================================
= ANALYSIS SUMMARY                                                             =
================================================================================
Critical : 0
High     : 0
Medium   : 1
Low      : 0
Passed   : 1
N/A      : 4
Erroneous: 0
---------------
Total    : 6

================================================================================
= ANALYSIS DETAILS                                                             =
================================================================================
      
--------------------------------------------------------------------------------


CHECK ID : 1393
SEVERITY : MODERATE
PROBLEM  : Sun Cluster 3.x node does not have the minimum required physical memory configuration.

ANALYSIS :
Sun Cluster 3.x requires a minimum of 512 MB of physical memory in each node. The minimum
physical memory resource requirements per node include: - 128 MB for the Solaris Operating
Environment - 128 MB for Sun Cluster - Additional memory used by Data Services Only 256Mb
of memory are installed.

RECOMMENDATIONS :
Add enough memory to this node to bring its physical memory up to the minimum required
level.

===============================================================================
Sun Confidential/Proprietary Information.
----------------------------------------

This report contains Sun(TM) confidential information in which Sun claims
trade secrets and other proprietary rights. The content is based upon Sun's
proprietary technology and is being provided to you pursuant the terms of your
SunSpectrum contract. By accepting a copy of this report, you agree to use it
for internal purposes only.

Copyright 2002 Sun Microsystems, Inc.
================================ End Of Report =================================

===========================
test2
===========================

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_sccheck; /bin/echo SC_COMMAND_STATUS=\$?'"
sccheck -v1 -o /var/cluster/logs/install/sccheck
sccheck: Requesting explorer data and node report from test2.
sccheck: test2: Explorer finished.
sccheck: test2: Starting single-node checks.
sccheck: test2: Single-node checks finished.
sccheck: One or more checks failed.
sccheck: The greatest severity of all check failures was 3 (HIGH).
sccheck: Reports are in /var/cluster/logs/install/sccheck.

********************************************************************************
* sccheck(1m)
* Sun(TM) Embedded Knowledge Engine (Sun EKE) (3.0.1) single *
********************************************************************************
          
Report #                      : 8ee016:105b3eaa0c6:32767:192.168.0.222
Report Generation Date        : 2005.08.14 at 07:36:02 GMT
Knowledge Automation Engine   : 3.0.1

================================================================================
= SYSTEM INFORMATION                                                           =
================================================================================
System Type   : HOST
Explorer Data : /opt/SUNWexplo/output/explorer.8093c43a.test2-2005.08.14.07.33
HOSTID        : 8093c43a
SERIAL_NUMBER : unspecified
PRODUCT_TYPE  : Sun Microsystems  sun4u Sun Ultra 450 (UltraSPARC-II 400MHz)

================================================================================
= ANALYSIS SUMMARY                                                             =
================================================================================
Critical : 0
High     : 1
Medium   : 0
Low      : 0
Passed   : 1
N/A      : 4
Erroneous: 0
---------------
Total    : 6

================================================================================
= ANALYSIS DETAILS                                                             =
================================================================================
      
--------------------------------------------------------------------------------


CHECK ID : 1398
SEVERITY : HIGH
PROBLEM  : An unsupported server is being used as a Sun Cluster 3.x node.

ANALYSIS :
It may not be supported to use this server as a Sun Cluster 3.x node. Only servers that
have been qualified with Sun Cluster 3.x are supported as Sun Cluster 3.x nodes. Server
type in question: Sun Microsystems sun4u Sun Ultra 450

RECOMMENDATIONS :
Because the list of supported servers is always being updated, check with your Sun
Microsystems representative to get the latest information on what servers are currently
supported and only use a server that is supported with Sun Cluster 3.x.

===============================================================================
Sun Confidential/Proprietary Information.
----------------------------------------

This report contains Sun(TM) confidential information in which Sun claims
trade secrets and other proprietary rights. The content is based upon Sun's
proprietary technology and is being provided to you pursuant the terms of your
SunSpectrum contract. By accepting a copy of this report, you agree to use it
for internal purposes only.

Copyright 2002 Sun Microsystems, Inc.
================================ End Of Report =================================
SC_COMMAND_STATUS=3

===========================

The sccheck command failed on both of the nodes.


    Removing the downloaded files ...


===========================
test2
===========================


rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_test isinstalling; /bin/echo SC_COMMAND_STATUS=\$?'"
"" is not running.
SC_COMMAND_STATUS=0

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_test isconfigured; /bin/echo SC_COMMAND_STATUS=\$?'"
Sun Cluster is not configured.
SC_COMMAND_STATUS=0

    Configuring "test2" ...

rsh test2 -n "/bin/sh -c '/usr/cluster/lib/scadmin/lib/cmd_install -logfile /var/cluster/logs/install/scinstall.log.2021 -k
-C test -F -T node=test1,node=test2,authtype=sys -A trtype=dlpi,name=qfe1 -A trtype=dlpi,name=qfe2 -B
type=switch,name=switch1 -B type=switch,name=switch1 -m endpoint=:qfe1,endpoint=switch1 -m endpoint=:qfe2,endpoint=switch1;
/bin/echo SC_COMMAND_STATUS=\$?'"

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

Initializing cluster name to "test" ... done
Initializing authentication options ... done
Initializing configuration for adapter "qfe1" ... done
Initializing configuration for adapter "qfe2" ... done
Initializing configuration for junction "switch1" ... done
Initializing configuration for junction "switch1" ... failed

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

SC_COMMAND_STATUS=1
scrconf:  Failed to add connection point - already exists.
scinstall:  Failed to initialize cluster configuration ("-B type=switch,name=switch1"

scinstall:  scinstall did NOT complete successfully!


Failed to configure "test2".


===========================

*** Installing just the First Node of a New Cluster ***
Sun Aug 14 15:47:33 CST 2005

    Running sccheck ...


The sccheck utility has detected potential problems.

    A copy of the following report of failed checks is in the install log
    as well as /var/cluster/logs/install/sccheck.


********************************************************************************
* sccheck(1m)
* Sun(TM) Embedded Knowledge Engine (Sun EKE) (3.0.1) single *
********************************************************************************
          
Report #                      : 8ee016:105b3fbc605:32767:192.168.0.221
Report Generation Date        : 2005.08.14 at 07:54:46 GMT
Knowledge Automation Engine   : 3.0.1

================================================================================
= SYSTEM INFORMATION                                                           =
================================================================================
System Type   : HOST
Explorer Data : /opt/SUNWexplo/output/explorer.80b1b853.test1-2005.08.14.07.51
HOSTID        : 80b1b853
SERIAL_NUMBER : unspecified
PRODUCT_TYPE  : Sun Microsystems  sun4u Sun (TM) Enterprise 250 (UltraSPARC-II 296MHz)

================================================================================
= ANALYSIS SUMMARY                                                             =
================================================================================
Critical : 0
High     : 0
Medium   : 1
Low      : 0
Passed   : 1
N/A      : 4
Erroneous: 0
---------------
Total    : 6

================================================================================
= ANALYSIS DETAILS                                                             =
================================================================================
      
--------------------------------------------------------------------------------


CHECK ID : 1393
SEVERITY : MODERATE
PROBLEM  : Sun Cluster 3.x node does not have the minimum required physical memory configuration.

ANALYSIS :
Sun Cluster 3.x requires a minimum of 512 MB of physical memory in each node. The minimum
physical memory resource requirements per node include: - 128 MB for the Solaris Operating
Environment - 128 MB for Sun Cluster - Additional memory used by Data Services Only 256Mb
of memory are installed.

RECOMMENDATIONS :
Add enough memory to this node to bring its physical memory up to the minimum required
level.

===============================================================================
Sun Confidential/Proprietary Information.
----------------------------------------

This report contains Sun(TM) confidential information in which Sun claims
trade secrets and other proprietary rights. The content is based upon Sun's
proprietary technology and is being provided to you pursuant the terms of your
SunSpectrum contract. By accepting a copy of this report, you agree to use it
for internal purposes only.

Copyright 2002 Sun Microsystems, Inc.
================================ End Of Report =================================

scinstall:  scinstall did NOT complete successfully!
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP