SUN cluster详细安装步骤(cluster3.0+vxvm3.2) 一

这个有些老了,但是,基本原理都应该差不多.做为参考吧!
设备：1)A1000（两台）：磁盘阵列8×36g硬盘
2)SUN Netra t1405（两台）：内置2×36g硬盘，四个100M网口
3)TC（一台）：8个控制口，一个网口
软件：1)SUN Solaris 8：操作系统。两张software
2）SUN Solaris 8 patch：操作系统补丁
3）Raid Manager：版本是6.22.1，该软件用来创建LUN。主要是针对A1000、A3000型号的磁盘阵列。
4）Raid Manage patch：112126补丁。
5）SC3.0：创建Cluster。主要用于SUN Netra t1405热备
6）Volume Manager 3.2：做A1000卷
7）Volume Manager 3.2 patch
磁盘阵列划分：
对于A1000磁盘阵列，Veritas Volume Manager将其作成RAID5+1方式，所谓RAID5+1，就是A1000采用raid5，A1000之间采用raid1。Raid5可用6块硬盘（206g），一块容错，一块热备。Raid1指两台A1000之间做镜像，用volume manager实现。
        硬件组成：
        二台SUN Netra t1405小型机（每台小型机配置：双CPU、4G内存、36G内置硬盘两块、集成网卡一块、单口PCI网卡一块、四口PCI网卡一块、磁带机一个、SCSI卡两块）
        两台A1000磁盘阵列，里有八块36.0G硬盘（RAID5+1方式）
        一台终端集线器TC
        一台微机控制台或SUN工作站控制台
附件：两根直连网线，三根RS232<->RJ45电缆（用于与TC连接），四根SCSI线， 3个接线板 ，至少八根普通网线，各主机，控制台电源线，直流电源插头等。

注意：若有磁带机，请将磁带机跳线，因磁带机默认c0t0d0,这与内置硬盘冲突，将其跳线为5，即c0t5d0，跳线方法
A的串口A通过RS232<->RJ45电缆连接TC的2口，B的串口A通过RS232<->RJ45电缆连接TC的3口（TC的1口留作配置TC用）

系统软件的安装及配置
Terminal Concentrator设置
        在iGWB/HA中，主机为不带显示卡和显示器的Netra t小型机，因此使用TC将两台主机上控制台（Console）信号接出到监控台上显示。
        由于在Solaris没有启动前，无法对a1/b1进行控制，必须先设置TC。如果TC已经设置好，则可以不用重设。
        下面给出TC的配置步骤（TC一经配置完成就无须每次开机后再次配置）。
        （1） 用一根RS232<->RJ45电缆将管理工作站（SUN工作站）的串口A和终端集线器的 1口（注：1口为TC的配置端口）连接，在管理工作站/etc/remote文件中加上：
        a:dv=/dev/term/a:br#9600:el=^C^S^Q^U^D^:ie=%/$e=^D
        （2）确保TC已经上电。
        （3）在ROOT用户下键入：# tip a
        （4）复位TC（即重新开电）。
        （5）按住TC的Test键2-3秒，直到电源指示灯（Power指示灯）快速闪动。
        （6）等Test灯熄灭后，再次按Test键。确认Test指示灯亮进入测试模式。注意不能等到其进入正常运行态，应当在电源灯快速闪动后不久就按Test。这一步相当于PC机中按“DEL”进入设置状态。

游客 未注册

发表于 2007-4-6 14:44 7）SUN出现monitor::提示符，在monitor::提示符下使用addr命令为TC配置正确的IP地址 （8）确认TC是由自己而不是由网络启动。 在monitor::提示符下输入seq命令，选择启动顺序为self。 （9）退出tip应用程序 在monitor ::提示符下： monitor ::boot annex::~.         （注：这里不用在显示器上看到键盘输入的“～”，另外“～”后还有一个“.”） （10）关掉TC电源并重新开机，若 能 telnet 上去，即验证了上述配置的正确性。此时对TC的各端口进行配置： # telnet 10.243.80.231 Trying 129.1.1.8... Connected to 129.1.1.8 Escape character is '^]'. Enter Annex port name or number: cli annex: su （切换到超级用户状态） Password: 此处键入TC的IP地址 如：10.243.80.170 annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports . admin : set port=1-8 type dial_in imask_7bits N You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : set port=2-7 mode slave You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : quit annex# boot bootfile: warning: *** Annex （129.1.1.8） shutdown message from port v1 ***        Annex （129.1.1.8） going down IMMEDIATELY Connection closed by foreign host 安装完毕，撤消1口的串口线。以上操作过程中可键入“？”或“help"命令给出帮助提示信息。若在现场开局无SUN工作站时，可用使用PC机的超级终端等程序对TC进行设置。 调节scsi-initiator-id         由于出厂时主机上的scsi-initiator-id均为缺省值7，为避免冲突，两台主机中的任意一台的scsi-initiator-id不能再使用出厂值，要进行调节。         注意：为保证两台机器的scsi-initiator-id都是初始的值，两台机器都先后进入ok状态下执行以下的操作，注意此操作同时只能有一台机器上电         操作步骤如下：         # telnet 10。243。80。170         Escape character is '^]'.         Enter Annex port name or number: 2 （表示选择TC的端口号为2口，此时修改的机器按照连线应是标识为 A 的机器）         此处快速按键 “Ctrl+]”组合进入telnet界面，在telnet>下键入send brk进入ok状态。                  注意，scsi-initator-id不能设为8；在改动之前，应该确认磁盘阵列连接在主机上。                           （2）下面的操作只用在双机中的一台上进行设置。（注：Ctrl+]必须得快，不得等到出现boot……的信息） {0} ok probe-scsi-all /pci@1f,4000/scsi@4,1 /pci@1f,4000/scsi@4 Target 5   Unit 0   Disk     Symbios StorEDGE A1000  0205   Unit 1   Device type 20     Symbios StorEDGE A1000  0205   Unit 2   Device type 20     Symbios StorEDGE A1000  0205   Unit 3   Device type 20     Symbios StorEDGE A1000  0205   Unit 4   Device type 20     Symbios StorEDGE A1000  0205   Unit 5   Device type 20     Symbios StorEDGE A1000  0205   Unit 6   Device type 20     Symbios StorEDGE A1000  0205   Unit 7   Device type 20     Symbios StorEDGE A1000  0205 /pci@1f,4000/scsi@2,1 /pci@1f,4000/scsi@2 Target 5   Unit 0   Disk     Symbios StorEDGE A1000  0205   Unit 1   Device type 20     Symbios StorEDGE A1000  0205   Unit 2   Device type 20     Symbios StorEDGE A1000  0205   Unit 3   Device type 20     Symbios StorEDGE A1000  0205   Unit 4   Device type 20     Symbios StorEDGE A1000  0205   Unit 5   Device type 20     Symbios StorEDGE A1000  0205   Unit 6   Device type 20     Symbios StorEDGE A1000  0205   Unit 7   Device type 20     Symbios StorEDGE A1000  0205 /pci@1f,4000/scsi@3,1 /pci@1f,4000/scsi@3 Target 0   Unit 0   Disk     SEAGATE ST318404LSUN18G 4203 Target 1   Unit 0   Disk     SEAGATE ST318404LSUN18G 4203 Target 3   Unit 0   Disk     FUJITSU MAJ3182M SUN18G 0804 Target 6   Unit 0   Removable Read Only device    TOSHIBA XM6201TASUN32XCD1103 ok nvedit    0: probe-all install-console banner    1: cd /pci@1f,4000/scsi@4    2: 6 " scsi-initiator-id" integer-property    3: device-end    4: cd /pci@1f,4000/scsi@2    5: 6 " scsi-initiator-id" integer-property    6: device-end    7:   ok nvstore ok setenv use-nvramrc? true use-nvramrc? =        true         注意：1.在scsi-initiator-id前有一个空格。另外“ 后有一个空格 ，”后也有一个空格，即上述2，5条为： 6（空格）“（空格）scsi-initiator-id”（空格）integer-property              2.上面nvedit中的1和5条中cd后的内容为运行probe-scsi-all命令后检测出来的内容， （3）执行 ok reset-all 双机安装操作系统 安装SUN Solaris 8 注意：两台机器系统安装过程中，相关设置一定要一致。 版本号：Sun Solaris 8 Hardware：02/02 中文（简体） 安装过程中，下划线内表示输入，尖括号内表示选择，其它表示显示。 将Solaris 8 安装光盘（安装盘两张中的第一张盘，非installation盘）放入光驱，使用微机控制台，通过telnet应用程序联上Terminal Concentrator，IP： 10.243.80.170。并在进入后输入“2”， ENTER，进入主机控制台。再在控制台打开一个窗口，输入“3”，ENTER进入备机控制台。

游客 未注册

发表于 2007-4-6 14:45 如果主机没安装过系统，就在相应控制台上按“Ctrl+]”，并键入“Send brk”，这相当于在Sun工作站键盘上按“Stop+a”，进入Solaris的OK状态。OK状态下输入 boot cdrom 让CDROM 引导安装程序。         举例如下：         root@qyp # telnet 10.243.80.170         Escape character is '^]'.  [Enter]         Rotaries Defined:             cli                              -                  Enter Annex port name or number: 2         Attached to port 2         screen not found.         Can't open input device.         Keyboard not present.  Using ttya for input and output.         telnet>  send brk         Netra t 1400/1405 （4 X UltraSPARC-II 440MHz), No Keyboard         OpenBoot 3.23, 1024 MB memory installed, Serial #14327748.         Ethernet address 8:0:20:da:9f:c4, Host ID: 80da9fc4.                  Initializing Memory \         {0} ok  boot cdrom                  （除非特殊说明，在安装过程中，都按F2 继续安装下一步）         下面为一些关键步骤：         提示：What type of terminal are you using?  根据实际情况选择vt100；         提示：Networked： 选择         提示：输入主机名：A  1号主机（ 或 B   2号主机）         提示：Primary network interface            注意：选择主网口与缺省网关相对应，所以此处是qfe1。         提示：输入IP地址：10.243.60.129 1号主机 （或 10.243.60.130 2号主机）         选择Name Service            提示：System part of a subnet               提示：Netmask      255.255.255.224         提示：Regions              提示：Timezones           提示：To start the initial option            提示：安装方式：< Entire Distribution plus OEM support> 完全安装         提示：选择磁盘：  表示本机硬盘         提示：磁盘分区方式：To manually layout file system         提示：分区大小：To customize the layout   人工控制分区大小         本地硬盘的分区（36G） 实际屏幕如下：（下方的2049为系统把输入的2048自动调整，实际输入2048即可） - Customize Disk: c0t0d0--------------------------------------------------------------------------- Boot Device: c0t0d0s0 =============================================================   Slice  Mount Point                        Size      0                                        16.70GB      1   swap                           4.88GB      2   overlap                         33.92GB      3   /globaldevices                   200.31MB      4                                   21.16MB      5   /opt                              4.09GB      6   /var                              4.00GB      7   /export/home                      4.00GB ===================================== ========================= 分区中注意，由于硬盘大小可能有一点不同，只要保持与上面分区基本相同就可以了。其中3号分区"/golbaldevices"必须存在，且大小约为200M ；4号分区必须存在，且大小约为20M，否则系统安装卷管理软件时将无法创建rootdg ,SC3.0将无法安装。 系统安装完成后会重启动，要求输入root密码，请并牢记root密码，（出厂默认密码设置为 root ）。 然后系统会依次安装第二张系统盘 ，以及语言盘。         安装SUN Solaris 的patch，并设置环境变量 以root用户进入系统，在#提示符下操作         （1）放入补丁盘SUN PATCH         # cd /cdrom/cdrom0/sun/install         # sh ./setup-standard.sh         Running setup-standard with EIS-CD Vn 25-JUN-02         ===============================================                           ******************************************************         *    You are using a EIS-CD that is > 40 days old!   *         * Please ensure that you use the most recent version *         ******************************************************                  Loading /opt/sun/bin...         Loading /opt/sun/patchdiag-1.0.4 & patchdiag.xref...                  Setting up /.profile...         Creating /var/sun for scripts, log files etc...         Sep 27 09:54:32 a1 sendmail[243]: unable to qualify my own domain name （a1) -- using short name                           Is the power saving daemon to be disabled? [y/n]: y         /etc/power.conf has been modified.                  Sun keyboard Power button to be disabled? [y/n]: y                  /usr/openwin/lib/speckeysd.map has been modified.                  Are the buttons & dials to be disabled? [y/n]: y         File /etc/rc2.d/S89bdconfig has been renamed to /etc/rc2.d/noS89bdconfig                  Are remote root logins to be allowed? [y/n]: y         /etc/default/login has been modified.                  For Solaris 7 & higher the crash dump is automatically enabled!         Minfree being set to 2000 k.               Dump content: kernel pages                Dump device: /dev/dsk/c0t0d0s1 （swap)         Savecore directory: /var/crash/a1 （minfree = 2000KB)           Savecore enabled: yes               Dump content: kernel pages                Dump device: /dev/dsk/c0t0d0s1 （swap)         Savecore directory: /var/crash/a1 （minfree = 2000KB)           Savecore enabled: yes                  Automated Core File Analysis Tool （ACT).....         ACT Package is not installed - Version 7.22 available....                  Do you want to install the ACT package? [y/n]:  n                  Explorer Package not present - will install Version 3.5.3.1,...                  Processing package instance from                  Sun（TM) Explorer Data Collector         （sparc,i386) 3.5.3.1, FCS         Copyright 1996-2002 Sun Microsystems, Inc.         All rights reserved.                  SUN MICROSYSTEMS, INC.                  SOFTWARE LICENSE AGREEMENT                  SUN IS WILLING TO LICENSE THE ACCOMPANYING SOFTWARE TO YOU ONLY UPON THE         CONDITION THAT YOU ACCEPT ALL OF THE TERMS CONTAINED IN THIS LICENSE AGREEMENT.         READ THE TERMS AND CONDITIONS OF THIS LICENSE CAREFULLY BEFORE DOWNLOADING THE         SOFTWARE. BY DOWNLOADING AND OR USING THE SOFTWARE, YOU AGREE TO THE TERMS AND         CONDITIONS OF THIS AGREEMENT. IF YOU ARE NOT WILLING TO BE BOUND BY THIS         AGREEMENT, YOU ARE NOT AUTHORIZED TO DOWNLOAD OR USE THIS SOFTWARE.                  1. License to Use. Customer is granted a royalty-free non-exclusive and         non-transferable license （"License") for the use of the accompanying software,         together with accompanying documentation, if any, （"Software"), only in         combination with the specific software previously licensed by you from Sun with         which this Software is intended to operate.  No other use or distribution of the         Software is authorized.                  2. Restrictions. Software is copyrighted and title to all copies is retained by         Sun and/or its licensors. Customer shall not make copies of the Software, other         than as authorized above plus a single copy for archival purposes and, if         applicable, Customer may, for its internal use only, print the number of copies         of on-line documentation, if any, for which it has been authorized, in which         event all proprietary rights notices on the Software shall be reproduced and         applied. Unless enforcement of this provision is prohibited by applicable law,         Customer shall not modify, decompile, disassemble, decrypt, extract, or         otherwise reverse engineer the Software. The Software is not designed or         licensed for use in on-line control equipment in hazardous environments such         as operation of nuclear facilities, aircraft navigation or control, or direct         life support machines.                  3. Confidentiality. The Software is confidential and proprietary information of         Sun and/or its licensors. Customer agrees to take adequate steps to protect the         Software from unauthorized disclosure or use.                  4. Disclaimer of Warranty. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT A WARRANTY         OF ANY KIND. EXCEPT AS SPECIFIED IN THIS LICENSE, ALL EXPRESS OR IMPLIED         CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF         MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE         HEREBY EXCLUDED TO THE EXTENT ALLOWED BY APPLICABLE LAW.                  5. Limitation of Liability. IN NO EVENT WILL SUN BE LIABLE FOR ANY LOST REVENUE,         PROFIT OR DATA, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE         DAMAGES HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY ARISING OUT OF         THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE         POSSIBILITY OF SUCH DAMAGES.  IN NO EVENT WILL SUN BE LIABLE FOR ANY DAMAGES,         REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO         USE THE SOFTWARE, WHICH ARE GREATER THAN THE  ACTUAL PURCHASE PRICE CUSTOMER

游客 未注册

发表于 2007-4-6 14:45 PAID TO SUN FOR SUCH SOFTWARE.                  6. Termination. This License is effective until terminated. Customer may         terminate this License at any time by destroying all copies of the Software         including any documentation.  This License will terminate immediately without         notice from Sun if Customer fails to comply with any provision of this License.         Upon termination, Customer must destroy all copies of the Software.                  7. Export Regulations. The Software, including technical data, is subject to         U.S. export control laws, including the U.S. Export Administration Act and its         associated regulations, and may be subject to export or import regulations in         other countries. Customer agrees to comply strictly with all such regulations         and acknowledges that it has the responsibility to obtain licenses to export,         re-export, or import the Software.                  8. U.S. Government Restricted Rights. If Customer is acquiring the Software         including accompanying documentation, if any, on behalf of the U.S.  Government,         the following provisions apply. If the Software is supplied to the Department of         Defense （"DOD"), the Software is subject to "Restricted Rights", as that term is         defined in the DOD Supplement to the Federal Acquisition Regulations （"DFAR") in         paragraph 252.227-7013（c) （1). If the Software is supplied to any unit or agency         of the United States Government other than DOD, the Government's rights in the         Software will be as defined in paragraph 52.227-19（c) （2) of the Federal         Acquisition Regulations （"FAR"). Use, duplication, reproduction or disclosure by         the Government is subject to such restrictions or successor provisions.         Contractor/Manufacturer is: Sun Microsystems, Inc., 2550 Garcia Ave., Mountain         View, CA 94043.                  9. Governing Law. This Agreement is made under, shall be governed by and         construed in accordance with the laws of the State of California, U.S.A.,         excluding its choice of law provisions.                  10. Severability. If any of the above provisions are held to be in violation of         applicable law, void, or unenforceable  in any jurisdiction, then such         provisions are herewith waived to the extent necessary for the License to be         otherwise enforceable in such jurisdiction,   However, if in Sun's opinion         deletion of any provisions of the License by operation of this paragraph           unreasonably compromises the rights or liabilities of Sun or its licensors, Sun         reserves the right to terminate the License and require the destruction or         return of the Software.                  11. Integration. This Agreement is the entire agreement between Customer and Sun         relating to this Software and: （i) supersedes all prior or contemporaneous oral         or written communications, proposals and representations with respect to its         subject matter; and （ii) prevails over any conflicting or additional terms of         any quote, order, acknowledgment, or similar communication between the parties         during the term of this Agreement. No modification to the Agreement will be         binding, unless in writing and signed by a duly authorized representative of         each party.                  Agree to these terms? [y,n]  y                  -----                  Sun Microsystems, Inc. respects your desire for privacy. Personal information         collected from this form will not be shared with organizations external to Sun         without your consent, except to process data on Sun's behalf in connection with         this transaction. We will use your personal information for communications         regarding Sun equipment and service related topics associated with the data         submitted.                  Sun, as a global company, may transfer your personal information to countries         which may not provide an adequate level of protection. Sun, however, is         committed to providing a suitable & consistent level of protection for your         personal information regardless of the country in which it resides.                  Completing the form below implies agreement with the above processing.                  If you have any questions please refer to the Sun Privacy Policy or contact us         at .                  If you have any questions about this form or in the future wish to update or         delete any of the information provided, please contact                  -----                  For any prompt, defaults appear in square brakets, e.g. [default].         Pressing return without entering any data will take the default.         You may specify an empty reply, as opposed to the default, by replying         with a single dash, '-'.                  Where should this package be installed? [/opt/SUNWexplo]: [Enter]                  Company name []: huawei         Contract ID []: [Enter]         System serial number []: [Enter]         Contact name []: [Enter]         Contact email address []: [Enter]         Phone number []: [Enter]         Address （line 1) []: [Enter]         Address （line 2) []: [Enter]         City []: [Enter]         State []: [Enter]         Zip []: [Enter]         Country []: [Enter]                  Geographic Region         1 - AMERICAS - North and South America         2 - EMEA     - Europe, Middle-east and Africa         3 - APAC     - Asia, Pacific         []: 3                  Automatic Email Submission                  Would you like all explorer output to be sent to:                      at the completion of explorer when -mail or -e is specified?         [y,n] n                  Alternate Email Addresses                  Would you like explorer output to be sent to alternate email         addresses at the completion of explorer?  If not, enter a single -         only for your reply.                  To enter multiple addresses, seperate them with a comma （,).         []: [Enter]                  Return address for explorer email output []: [Enter]                           You have answered:                      Company name: huawei                       Contract ID:                       System serial number:                               Contact name:             Contact email address:                      Phone number:                  Address （line 1):                  Address （line 2):                              City:                             State:                               Zip:                           Country:                                  Geography: APAC                    Mail output to:                  Mail output from:                      Are these values okay? [y,n] y                  We recommend running explorer once a week and emailing the results         to the explorer database.  If you agree with this, the root crontab         will be modified.                  Do you wish to run explorer once a week? [y,n] n                  If this is a new install of explorer, please run explorer and         mail the results to Sun.                  The command to do this would be:

游客 未注册

发表于 2007-4-6 14:46 /opt/SUNWexplo/bin/explorer -q -e                  Would you like to do this now? [y,n] y                  The selected base directory must exist before         installation is attempted.                  Do you want this directory created now [y,n,?,q] y           Using as the package base directory.         ## Processing package information.         ## Processing system information.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.         ## Checking for setuid/setgid programs.                  This package contains scripts which will be executed with super-user         permission during the process of installing this package.                  Do you want to continue with the installation of [y,n,?]  y                  Installing Sun（TM) Explorer Data Collector as                  ## Installing part 1 of 1.         /opt/SUNWexplo/README         /opt/SUNWexplo/bin/capture.sparc         /opt/SUNWexplo/bin/core_check.sh         /opt/SUNWexplo/bin/diskinfo.i386         /opt/SUNWexplo/bin/diskinfo.sparc         /opt/SUNWexplo/bin/explorer         /opt/SUNWexplo/bin/gzip.i386         /opt/SUNWexplo/bin/gzip.sparc         /opt/SUNWexplo/bin/rprtfru.sparc         /opt/SUNWexplo/bin/t3client.i386         /opt/SUNWexplo/bin/t3client.sparc         /opt/SUNWexplo/etc/cmd.txt         /opt/SUNWexplo/etc/t3files.txt         /opt/SUNWexplo/java/fruid-scappclient.jar         /opt/SUNWexplo/java/libfru.jar         /opt/SUNWexplo/lib/exp_check         /opt/SUNWexplo/lib/exp_common         /opt/SUNWexplo/lib/exp_file         /opt/SUNWexplo/lib/exp_ftp         /opt/SUNWexplo/lib/exp_mail         /opt/SUNWexplo/lib/exp_main         /opt/SUNWexplo/lib/exp_postproc         /opt/SUNWexplo/lib/exp_tools         /opt/SUNWexplo/lib/exp_tools_check         /opt/SUNWexplo/lib/exp_transport         /opt/SUNWexplo/lib/libfru.so         /opt/SUNWexplo/lib/libfru.so.1         /opt/SUNWexplo/lib/libfrujni.so         /opt/SUNWexplo/lib/libfrujni.so.1         /opt/SUNWexplo/lib/libfrureg.so         /opt/SUNWexplo/lib/libfrureg.so.1         /opt/SUNWexplo/lib/libfrurmi.so         /opt/SUNWexplo/lib/libfrurmi.so.1         /opt/SUNWexplo/lib/libfruutils.so         /opt/SUNWexplo/lib/libfruutils.so.1         /opt/SUNWexplo/lib/locale/C/LC_MESSAGES/explorer.mo         /opt/SUNWexplo/lib/locale/C/LC_MESSAGES/explorer.po         /opt/SUNWexplo/lib/uu2b64         /opt/SUNWexplo/man/man1m/explorer.1m         /opt/SUNWexplo/man/man4/explorer.4         /opt/SUNWexplo/man/man5/explorer.5         /opt/SUNWexplo/man/windex         /opt/SUNWexplo/tools/cluster         /opt/SUNWexplo/tools/cmdline         /opt/SUNWexplo/tools/cst         /opt/SUNWexplo/tools/disks         /opt/SUNWexplo/tools/emc         /opt/SUNWexplo/tools/etc         /opt/SUNWexplo/tools/fcal         /opt/SUNWexplo/tools/firelink         /opt/SUNWexplo/tools/fru         /opt/SUNWexplo/tools/init         /opt/SUNWexplo/tools/lic         /opt/SUNWexplo/tools/lp         /opt/SUNWexplo/tools/messages         /opt/SUNWexplo/tools/nbu         /opt/SUNWexplo/tools/nbu_extended         /opt/SUNWexplo/tools/ndd         /opt/SUNWexplo/tools/netinfo         /opt/SUNWexplo/tools/patch         /opt/SUNWexplo/tools/photon         /opt/SUNWexplo/tools/pkg         /opt/SUNWexplo/tools/sanextended         /opt/SUNWexplo/tools/sbu         /opt/SUNWexplo/tools/scextended         /opt/SUNWexplo/tools/sds         /opt/SUNWexplo/tools/secure         /opt/SUNWexplo/tools/sf15k-ndd         /opt/SUNWexplo/tools/sf15k-sc         /opt/SUNWexplo/tools/sonoma         /opt/SUNWexplo/tools/ssa         /opt/SUNWexplo/tools/ssp         /opt/SUNWexplo/tools/storedge         /opt/SUNWexplo/tools/stortools         /opt/SUNWexplo/tools/sunray         /opt/SUNWexplo/tools/sysconfig         /opt/SUNWexplo/tools/t3         /opt/SUNWexplo/tools/t3extended         /opt/SUNWexplo/tools/test         /opt/SUNWexplo/tools/u4ft         /opt/SUNWexplo/tools/var         /opt/SUNWexplo/tools/vtsst         /opt/SUNWexplo/tools/vxfs         /opt/SUNWexplo/tools/vxvm         [ verifying class ]         Modifying /opt/SUNWexplo/etc/default/explorer         Modifying /opt/SUNWexplo/etc/saninput.txt         Modifying /opt/SUNWexplo/etc/scinput.txt         Modifying /opt/SUNWexplo/etc/t3input.txt         [ verifying class ]         [ verifying class ]         ## Executing postinstall script.         Executing '//opt/SUNWexplo/bin/explorer -q -e'         WARNING: EXP_SERIAL_80fe4f22 not set!         WARNING: EXP_CONTRACT_ID not set!         WARNING: EXP_USER_NAME not set!         WARNING: EXP_USER_EMAIL not set!         WARNING: EXP_PHONE not set!         WARNING: EXP_ADDRESS_1 not set!         WARNING: EXP_ADDRESS_CITY not set!         WARNING: EXP_ADDRESS_STATE not set!         WARNING: EXP_ADDRESS_ZIP not set!         WARNING: EXP_ADDRESS_COUNTRY not set!         WARNING: EXP_REPLY not set!                  11 warnings found in //opt/SUNWexplo/etc/default/explorer                  Creating man index                  Installation of was successful.         ******************************************************         *   You have used an EIS-CD that is > 40 days old!   *         * Please ensure that you use the most recent version *         ******************************************************                  Note: /.profile was created/modified - please check/edit this file!!!         You must log out & back in for the PATH to be modified                  Completed                  #            # .  /.profile          安装 推荐补丁的说明         安装Sun Solaris 的补丁盘，以root用户进入系统，在#提示符下操作         a1@root# cd /cdrom/cdrom0/sun/patch/8         a1@root# unpack-patches         按照系统提示,到相应目录下运行补丁安装脚本，如:         a1@root# cd /tmp/8         a1@root# ./install_all_patches         重启系统         a1@root# sync         a1@root# sync         a1@root#  reboot                  （3）执行TERM=vt100;export TERM         （注：这里可以设置一下终端，在/.profile文件末尾加         TERM=vt100;export TERM         DISPLAY=129.1.1.4:0.0;export DISPLAY         其中129.1.1.4为管理工作站（如U80）的ip         （4）（注：如果装系统补丁的时候已经有“Are remote root logins to be allowed? [y/n]: y”         则下面这部不需要再做）                  /etc/default/login的以下注释掉，如下：         #CONSOLE=/dev/console         原因如下：         # If CONSOLE is set, root can only login on that device.         # Comment this line out to allow remote login by root.）         （5）把/etc/ftpusers文件中 的“root”（一般为第一行）注释掉 1.1.1         修改etc/hosts文件 vi     etc/hosts         增加Ip：         服务器A         127.0.0.1       localhost               10.243.80.129   A      loghost         B.moto.com         10.243.80.176   qfe0         10.243.80.145   qfe3         10.243.80.131   cg1         10.243.80.147   cg2            服务器B         127.0.0.1       localhost               10.243.80.130   B      loghost         B.moto.com         10.243.80.175   qfe0         10.243.80.146   qfe3         10.243.80.131   cg1         10.243.80.147   cg2         （此处的loghost  B.moto.com ：只是为了系统显示locolhost太短的提示）         vi  /etc/netmasks 添加各网段子网掩码。         cat > /etc/defaultrouter 添加缺省路由。

游客 未注册

发表于 2007-4-6 14:46 双机创建hostname文件         TJ-cg1的etc目录下创建         文件1、hostname.qfe0         vi hostname .qfe0        其中内容为：qfe0         文件2、hostname.qfe3         vi hostname .qfe3        其中内容为：qfe3                  b1的etc目录下创建                 文件1、hostname.qfe0         vi hostname .qfe0        其中内容为：qfe0         文件2、hostname.qfe3         vi hostname .qfe3        其中内容为：qfe3         到此，SUN Solaris操作系统应该正常安装完成。                  再安装另一台机器。注意此时如果是第一次安装，则要在相应的控制台上执行前一台机器类似的操作。          1.1         安装 Raid Manager 并建 LUN 1.1.1         安装Raid Manager         1. 任务说明         Raid Manager版本是6.22.1，该软件用来创建LUN。主要是针对A1000、A3000型号的磁盘阵列。如果系统冷备方式，则需要安装此软件，如果系统采用热备方式，则不需要安装。         2. 操作指引         （1）将Raid Manager安装盘放入光驱         （2）以root用户登录，拷贝安装软件包到本地相应目录         root@a1 # cd /cdrom/cdrom0/sun-internal/progs/RM         root@a1 # cp RM-6.22.1.tar.gz   /opt/sun         root@a1 # cd ../veritas-vm/3.2         root@a1 # cp foundationproduct3.4sunw.tar.gz   /opt/sun         （3）解开软件包         root@a1 # cd /opt/sun         root@a1 # gunzip  RM-6.22.1.tar.gz         root@a1 #tar xvf   RM-6.22.1.tar         root@a1 # cd RM-6.22.1/Raid_Manager/Packages         在当前目录下应有如下文件：         SUNWosafw  SUNWosamn  SUNWosanv  SUNWosar   SUNWosau         （4）开始安装         root@a1 # pkgadd -d .  SUNWosar SUNWosafw SUNWosamn SUNWosanv SUNWosau         系统将会显示如下的安装信息：         Processing package instance from                  Open Storage Array （Root)         （sparc) 06.22,REV=01.54         Copyright 2000 Sun Microsystems, Inc.  All rights reserved.                  Copyright （C) 1995, 1996, 1997, 1998, 1999, 2000         LSI Logic Corporation         3718 North Rock Road         Wichita, KS 67226-1397         All Rights Reserved                  Using as the package base directory.         ## Processing package information.         ## Processing system information.            12 package pathnames are already properly installed.         ## Verifying package dependencies.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.         ## Checking for setuid/setgid programs.                  This package contains scripts which will be executed with super-user         permission during the process of installing this package.                  Do you want to continue with the installation of [y,n,?] y         如果安装成功，将会有如下的提示信息：         Installation of was successful.         根据提示，安装其余的软件包。          安装Raid Manager的patch         1.任务说明         需要的补丁版本是112126，请根据SUN工程师的要求更新。         2. 操作指引         （1）将补丁盘放入光驱中。         （2）以root用户登录。         root@a1 # cd /cdrom/cdrom0/sun/patch/RM/6.22.1         在当前目录下应有如下文件：         112125-03.tar.gz  README            manual.txt         112126-03.zip     info.txt         （3）安装patch软件包         root@a1 # unpack-patches         Are you ready to unpack patches into /tmp/6.22.1? [y/n]: y         root@a1 # cd /tmp/6.22.1         root@a1 # patchadd 112126-03         如果安装成功，将会显示如下信息：         Patch number 112126-03 has been successfully installed.         See /var/sadm/patch/112126-03/log for details         Executing postpatch script...         Patch packages installed:           SUNWosafw           SUNWosar           SUNWosau          修改相关参数（两台机都运行）         1.任务说明         安装完成后，需要修改相关参数。         2. 操作指引         （1）以root用户登录。         （2）编辑rmparams 文件         root@a1 # cd /etc/osa         root@a1 # vi rmparams         修改其中的两个参数如下：         Rdac_RetryCount=1  （此参数用来表示访问磁盘失败时，重新尝试的次数）         Rdac_NoAltOffline=True         （3）完成后重启。         root@a1 # sync         root@a1 # sync         root@a1 # init 6     创建LUN（只在一台机上做）         1. 任务说明         在两个A1000中分别创建虚拟磁盘LUN0、LUN1。LUN0用来作为锁盘，大小为10M；LUN1用来创建igwbdg ,LUN1大小剩余磁盘容量。         A1000中磁盘的框位为20,22,10,12 。         2.操作指引         （1）查看磁盘信息         root@a1 # format                  AVAILABLE DISK SELECTIONS:                0. c0t0d0                   /pci@1f,4000/scsi@3/sd@0,0                1. c0t1d0                   /pci@1f,4000/scsi@3/sd@1,0                2. c1t5d0                   /pseudo/rdnexus@1/rdriver@5,0                3. c2t5d0                   /pseudo/rdnexus@2/rdriver@5,0         Specify disk (enter its number): ^D                  （2）如果磁盘中已经有信息，则删除两个A1000中原有磁盘信息         root@a1 # raidutil -c c1t5d0 -D all         root@a1 # raidutil -c c2t5d0 -D all         （3）创建LUN0         root@a1 # raidutil -c c1t5d0 -r fast -n 0 -l 5 -s 10 -z 32,32 -g 20,21,22,23,10,11,12                  Registering new logical unit 0 with system.         No RAID devices found.                  raidutil failed!          注：可用下方的命令查看LUN的情况          root@a1 # raidutil -c c1t5d0 -i          LUNs found on c1t5d0.            LUN 0    RAID 0    10 MB            LUN 1    RAID 0    68900 MB

游客 未注册

发表于 2007-4-6 14:48 Vendor ID         Symbios          ProductID         StorEDGE A1000            Product Revision  0301          Boot Level        03.01.04.00          Boot Level Date   04/05/01          Firmware Level    03.01.04.75          Firmware Date     04/11/02          raidutil succeeded!                  root@a1 # raidutil -c c2t5d0 -r fast -n 0 -l 5 -s 10 -z 32,32 -g 20,21,22,23,10,11,12                  Registering new logical unit 0 with system.         No RAID devices found.                  raidutil failed!                           （4）创建LUN1         root@TJ-cg1 # raidutil -c c1t5d0 -r fast -n 1 -l 5 -s 208100 -z 32,32 -g 20,21,22,23,10,11,12                   LUNs successfully created         raidutil succeeded!                  root@TJ-cg1 # raidutil -c c2t5d0 -r fast -n 1 -l 0 -s 208100 -z 32,32 -g 20,2122,23,10,11,12                            LUNs successfully created                   （5）创建热备盘                  root@TJ-cg1 # raidutil –c c1t5d0 –h 13         root@TJ-cg1 # raidutil –c c2t5d0 –h 13                   参数说明：-n 1其中1表示创建LUN1，-l 5其中5表示Raid5，-s 208100其中208100表示LUN1的大小，-g 20,2122,23,10,11,12 其中20,21,22,23,10,11,12 表示磁盘框位号；-h 13表示热备盘为硬盘13。          1.2         安装SC3.0 和 Veritas Volume Manager3.2 1.2.1         a1安装SC3.0创建Cluster         root@A # cd /cdrom/sun_cluster_3.0/SunCluster_3.0/Tools         root@A # ./scinstall          *** Main Menu ***                      Please select from one of the following （*) options:                        * 1) Establish a new cluster using this machine as the first node               * 2) Add this machine as a node in an established cluster                 3) Configure a cluster to be JumpStarted from this install server                 4) Add support for new data services to this cluster node                 5) Print release information for this cluster node                        * ?) Help with menu options * q) Quit                      Option:  1                    *** Establishing 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, sccheck（1M) is run 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 Ctrl-d at any time to return to the Main Menu.                      Do you want to continue （yes/no) [yes]?  [Enter]                    >>> Software Package Installation <<<                      Installation of the Sun Cluster framework software packages will take             a few minutes to complete.                      Is it okay to continue （yes/no) [yes]?  [Enter]                  ** Installing SunCluster 3.0 **                 SUNWscr.....done                 SUNWscu.....done                 SUNWscdev...done                 SUNWscgds...done                 SUNWscman...done                 SUNWscsal...done                 SUNWscsam...done                 SUNWscvm....done                 SUNWmdm.....done                 SUNWscva....done                 SUNWscvr....done                 SUNWscvw....done                  Hit ENTER to continue:  [Enter]                    >>> Cluster Name <<<                      Each cluster has a name assigned to it. The name can be made up of             any characters other than whitespace. It may be up to 256 characters             in length. And, you may want to assign a cluster name which will be             the same as one of the failover logical host names in the cluster.             Create each cluster name to be unique within the namespace of your             enterprise.                      What is the name of the cluster you want to establish?   sc-tjigwb                    >>> Check <<<                      This step runs 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 list of warnings is printed.                      Hit ENTER to continue:  [Enter]                      Running sccheck ... done             All sccheck tests passed.                  Hit ENTER to continue:  [Enter]                    >>> Cluster Nodes <<<                      This release of Sun Cluster supports a total of up to 8 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:  A             Node name:  B             Node name （Ctrl-D to finish):  ^D      （CTRL + D)                      This is the complete list of nodes:                          A                 B                      Is it correct （yes/no) [yes]?  [Enter]                    >>> 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. The list can be             modified once the cluster has been established using scconf（1M) or             other tools.                      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]?  [Enter]                    >>> 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, please bear in mind that             the Sun Clustering software requires that the rightmost two octets             always be zero.                      The default netmask is 255.255.0.0; you may select another netmask,             as long as it minimally masks all bits given in the network address             and does not contain any "holes".                      Is it okay to accept the default network address （yes/no) [yes]?  [Enter]                      Is it okay to accept the default netmask （yes/no) [yes]?  [Enter]                    >>> 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]?  no                    >>> Cluster Transport Adapters and Cables <<<                      You must configure at least two transport adapters on each node which             serve as connection points to the private cluster transport. More             than two connection points are allowed, but this interactive form of             scinstall assumes exactly two.                      Note that interactive scinstall does not allow you to specify any             special transport adapter properties settings. If your adapters have             special properties which must be set, you may need to use             non-interactive scinstall by specifying a complete set of command             line options. For more information, please refer to the man pages for             your adapters in the scconf_transp_adap family of man pages （e.g.,             scconf_transp_adap_hme（1M)).                               Hit ENTER to continue:  [Enter]                               Select the first cluster transport adapter to use:                          1) hme0                 2) hme1                 3) Other                      Option:  1         （Notes :  Please Choose the "hme0")                      Adapter "hme0" is an ethernet adapter.                      Searching for unexpected network traffic on "hme0" ... done             Verification completed. No traffic was detected over a 10 second             sample period.                      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), ...).                      The "dlpi" transport type will be set for this cluster.                      Select the second cluster transport adapter to use:                          1) hme1                 2) Other                      Option:  1         （Notes :  Please Choose the "hme1")                      Adapter "hme1" is an ethernet adapter.                      Searching for unexpected network traffic on "hme1" ... done             Verification completed. No traffic was detected over a 10 second             sample period.                    >>> Global Devices File System <<<                      Each node in the cluster must have a local file system mounted on             /global/.devices/node@ 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. However, in             order to do this, you must supply the name of either an             already-mounted file system or raw disk partition at this time. This             file system or partition should be at least 100 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]?  [Enter]                    >>> 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]?  yes                      You will need to manually reboot this node in "cluster mode" after             scinstall successfully completes.                               Hit ENTER to continue:  [Enter]                    >>> Confirmation <<<                      Your responses indicate the following options to scinstall:                        scinstall -ik \                    -C sc-igwb \                    -F \                    -T node=a1,node=b1,authtype=sys \                    -A trtype=dlpi,name=hme0 -A trtype=dlpi,name=hme1 \                    -B type=direct                      Are these the options you want to use （yes/no) [yes]?  [Enter]                      Do you want to continue with the install （yes/no) [yes]?  [Enter]                  Checking device to use for global devices file system ... done                  Initializing cluster name to "sc-igwb" ... done         Initializing authentication options ... done         Initializing configuration for adapter "hme0" ... done         Initializing configuration for adapter "hme1" ... done                           Setting the node ID for "a1" ... done （id=1)                  Setting the major number for the "did" driver ... 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.092802101021         Power management is incompatible with the HA goals of the cluster.         Please do not attempt to re-configure power management.                  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.                      Hit ENTER to continue:  [Enter]                  Log file - /var/cluster/logs/install/scinstall.log.638                  Rebooting ...                  Nov 17 18:44:38 a1 reboot: rebooted by root         Nov 17 18:44:38 a1 rpcbind: rpcbind terminating on signal.         Nov 17 18:44:38 a1 syslogd: going down on signal 15         Terminated         root@a1 # syncing file systems... done         rebooting...         Resetting ...                  机器重新启动后，继续安装 B安装SC3.0加入Cluster         同a1得到软件包         root@b1 #         root@b1 # cd /cdrom/sun_cluster_3.0/SunCluster_3.0/Tools         root@b1 # ./scinstall           *** Main Menu ***                      Please select from one of the following （*) options:                        * 1) Establish a new cluster using this machine as the first node               * 2) Add this machine as a node in an established cluster                 3) Configure a cluster to be JumpStarted from this install server                 4) Add support for new data services to this cluster node                 5) Print release information for this cluster node                        * ?) Help with menu options               * q) Quit                      Option:  2                    *** Adding a Node to an Established 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 Ctrl-d at any time to return to the Main Menu.                      Do you want to continue （yes/no) [yes]?  [Enter]                    >>> Software Package Installation <<<                      Installation of the Sun Cluster framework software packages will take             a few minutes to complete.                      Is it okay to continue （yes/no) [yes]?  [Enter]                  ** Installing SunCluster 3.0 **                 SUNWscr.....done                 SUNWscu.....done                 SUNWscdev...done                 SUNWscgds...done                 SUNWscman...done                 SUNWscsal...done                 SUNWscsam...done                 SUNWscvm....done                 SUNWmdm.....done                 SUNWscva....done                 SUNWscvr....done                 SUNWscvw....done                  Hit ENTER to continue:  [Enter]                    >>> 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?  A                    >>> 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?  sc-tjigwb                      Attempting to contact "a1" ... done             Cluster name "sc-igwb" is correct.                      Hit ENTER to continue:  [Enter]                    >>> Check <<<                      This step runs 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 list of warnings is printed.                      Hit ENTER to continue:  [Enter]                      Running sccheck ... done             All sccheck tests passed.                  Hit ENTER to continue:  [Enter]                    >>> 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.                      Do you want to use autodiscovery （yes/no) [yes]?  [Enter]             Probing  .........                      The following connections were discovered:                          a1:hme0  -  b1:hme0                 a1:hme1  -  b1:hme1                      Is it okay to add these connections to the configuration （yes/no) [yes]?  [Enter]                    >>> Global Devices File System <<<                      Each node in the cluster must have a local file system mounted on             /global/.devices/node@ 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. However, in             order to do this, you must supply the name of either an             already-mounted file system or raw disk partition at this time. This             file system or partition should be at least 100 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]?  [Enter]                    >>> 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]?  yes                    >>> Confirmation <<<                      Your responses indicate the following options to scinstall:                        scinstall -ik \                    -C sc-igwb \                    -N a1 \                    -A trtype=dlpi,name=hme0 -A trtype=dlpi,name=hme1 \                    -B type=direct \                    -m endpoint=:hme0,endpoint=a1:hme0 \                    -m endpoint=:hme1,endpoint=a1:hme1                      Are these the options you want to use （yes/no) [yes]?  [Enter]                      Do you want to continue with the install （yes/no) [yes]?  [Enter]                  Checking device to use for global devices file system ... done                  Adding node "b1" to the cluster configuration ... done         Adding adapter "hme0" to the cluster configuration ... done         Adding adapter "hme1" to the cluster configuration ... done         Adding cable to the cluster configuration ... done         Adding cable to the cluster configuration ... done                  Copying the config from "a1" ... done

游客 未注册

发表于 2007-4-6 14:48 Setting the node ID for "b1" ... done （id=2)                  Setting the major number for the "did" driver ...         Obtaining the major number for the "did" driver from "a1" ... 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.092802101021         Power management is incompatible with the HA goals of the cluster.         Please do not attempt to re-configure power management.                  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.713                  Rebooting ...                     双机重新启动后，继续安装 在a1上配置Quorum Disks         首先a1上运行下方命令，得到目前SC所能检测到的磁盘                  root@a1 # scdidadm  -L         1        A:/dev/rdsk/c0t0d0    /dev/did/rdsk/d1              2        A:/dev/rdsk/c0t1d0    /dev/did/rdsk/d2              3        A:/dev/rdsk/c0t6d0    /dev/did/rdsk/d3              4        A:/dev/rdsk/c1t5d1    /dev/did/rdsk/d4              4        B:/dev/rdsk/c1t5d1    /dev/did/rdsk/d4              5        A:/dev/rdsk/c2t5d0    /dev/did/rdsk/d5              5        B:/dev/rdsk/c2t5d0    /dev/did/rdsk/d5              6        A:/dev/rdsk/c1t5d0    /dev/did/rdsk/d6              6        B:/dev/rdsk/c1t5d0    /dev/did/rdsk/d6              7        A:/dev/rdsk/c2t5d1    /dev/did/rdsk/d7              7        B:/dev/rdsk/c2t5d1    /dev/did/rdsk/d7              8        B:/dev/rdsk/c0t0d0    /dev/did/rdsk/d8              9        B:/dev/rdsk/c0t1d0    /dev/did/rdsk/d9              10       B:/dev/rdsk/c0t6d0    /dev/did/rdsk/d10            8190     B:/dev/rmt/0          /dev/did/rmt/2               8191     A:/dev/rmt/0          /dev/did/rmt/1                注意：                                                                                                                                    1、命令输出信息中 行首标为4、7 （上述用彩色标注的部分），表示a1和b1 组成的SC 能够检测到的磁盘阵列中的磁盘 LUN1（我们使用的LUN1存在有2个），这些部分在下面设置 quorum disks 时要用到。          2、并且以“4”开头的LUN（命令输出信息中行末标为d4的LUN），以“7”开头的LUN（命令输出信息中行末标为d7的LUN）。表明分别归不同的SCSI控制器控制。          3、其余的都是以 c0  开头的磁盘为a1本地的磁盘，  d6 和 d5是LUN0                                                               root@a1 #         root@a1 # scsetup           >>> Initial Cluster Setup <<<                      This program has detected that the cluster "installmode" attribute is             still enabled. As such, certain initial cluster setup steps will be             performed at this time. This includes adding any necessary quorum             devices, then resetting both the quorum vote counts and the             "installmode" property.                      Please do not proceed if any additional nodes have yet to join the             cluster.                      Is it okay to continue （yes/no) [yes]?  [Enter]                      Do you want to add any quorum disks （yes/no) [yes]?  [Enter]                      Dual-ported SCSI-2 disks may be used as quorum devices in two-node             clusters. However, clusters with more than two nodes require that             SCSI-3 PGR disks be used for all disks with more than two             node-to-disk paths. You can use a disk containing user data or one             that is a member of a device group as a quorum device.                      Each quorum disk must be connected to at least two nodes. Please             refer to the Sun Cluster documentation for more information on             supported quorum device topologies.                      Which global device do you want to use （d）?  d4         （注：此处的d4 为 “dev/rdsk/c1t5d1         /dev/did/rdsk/d4”中的d4）                      Is it okay to proceed with the update （yes/no） [yes]? [Enter]                    scconf -a -q globaldev=d4                      Command completed successfully.                  Hit ENTER to continue:                        Do you want to add another quorum disk （yes/no)?  y                      Which global device do you want to use （d)?  d7         （注：此处的d7 为 “dev/rdsk/c2t5d1         /dev/did/rdsk/d7”中的d7）                      Is it okay to proceed with the update （yes/no) [yes]?  [Enter]                  scconf -a -q globaldev=d7                      Command completed successfully.                  Hit ENTER to continue:                        Do you want to add another quorum disk （yes/no)?  no                      Once the "installmode" property has been reset, this program will             skip "Initial Cluster Setup" each time it is run again in the future.             However, quorum devices can always be added to the cluster using the             regular menu options. Resetting this property fully activates quorum             settings and is necessary for the normal and safe operation of the             cluster.                      Is it okay to reset "installmode" （yes/no) [yes]?    [Enter]                  scconf -c -q reset         scconf -a -T node=.                      Cluster initialization is complete.                      Type ENTER to proceed to the main menu:     [Enter]                    *** Main Menu ***                      Please select from one of the following options:                          1) Quorum                 2) Resource groups                 3) Cluster interconnect                 4) Device groups and volumes                 5) Private hostnames                 6) New nodes                 7) Other cluster properties                          ?) Help with menu options                 q) Quit                      Option:  q                           编辑文件/etc/inet/ntp.conf.cluster ，将未用到的节点删除；如果是双节点，则将节点3、4、5、6、7和8删除。 在SC3.0的引导下安装Veritas Volume Manager 3.2 （双机安装）         root@A # scvxinstall                  Do you want Volume Manager to encapsulate root [no]?  no                  Where is the Volume Manager cdrom [/cdrom/cdrom0]?                    Disabling DMP.         Installing packages from /cdrom/cdrom0/pkgs.         Installing VRTSlic.         Installing VRTSvxvm.         Installing VRTSvmdev.         Installing VRTSvmman.         Obtaining the clusterwide vxio number...         Using 315 as the vxio major number.         Volume Manager installation is complete.                  Please remember to re-boot this node before configuring VxVM.                  如果还要装图形方式，继续下面的步骤，否则跳过下面从下一节继续安装：                  root@a1 #         root@a1 # cd /cdrom/foundationproduct3.4sunw/pkgs         root@a1 # pkgadd -d  .  VRTSvmsa                  Processing package instance from                  VERITAS Volume Manager Storage Administrator         （sparc) 3.2,REV=07.27.2001.19.47         Copyright （C) 2001 VERITAS Software Corporation.  All Rights Reserved.         VERITAS, VERITAS SOFTWARE, the VERITAS logo, Business Without Interruption, VERITAS The Data Availability Company and Volume Manager are trademarks or         registered trademarks of VERITAS Software Corporation in the US and/or         other countries. Other product names mentioned herein may be trademarks or         registered trademarks of their respective companies.                  Where should this package be installed? （default: /opt/VRTSvmsa]) [?,q] [Enter]                  Should the Volume Manager Storage Administrator Server be installed         on this system?  （The Volume Manager Storage Administrator Client will         be installed regardless) （default: y) [y,n,?,q] [Enter]                  The selected base directory must exist before         installation is attempted.                  Do you want this directory created now [y,n,?,q]  y         Using as the package base directory.         ## Processing package information.         ## Processing system information.            4 package pathnames are already properly installed.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.         ## Checking for setuid/setgid programs.                  This package contains scripts which will be executed with super-user         permission during the process of installing this package.                  Do you want to continue with the installation of [y,n,?]  y                  Installing VERITAS Volume Manager Storage Administrator as                  ## Installing part 1 of 1.         /opt/VRTS/man/man1m/autostart.1m         /opt/VRTS/man/man1m/vmsa.1m         /opt/VRTS/man/man1m/vmsa_server.1m         /opt/VRTS/man/man4/properties.4         [ verifying class ]         /opt/VRTSvmsa/jre/COPYRIGHT         /opt/VRTSvmsa/jre/LICENSE.ps         /opt/VRTSvmsa/jre/bin/.java_wrapper         /opt/VRTSvmsa/jre/bin/javakey         /opt/VRTSvmsa/jre/bin/jre         /opt/VRTSvmsa/jre/bin/rmiregistry         /opt/VRTSvmsa/jre/bin/sparc/green_threads/.extract_args         /opt/VRTSvmsa/jre/bin/sparc/green_threads/javakey         /opt/VRTSvmsa/jre/bin/sparc/green_threads/jre         /opt/VRTSvmsa/jre/bin/sparc/green_threads/rmiregistry         /opt/VRTSvmsa/jre/bin/sparc/native_threads/.extract_args         /opt/VRTSvmsa/jre/bin/sparc/native_threads/javakey         /opt/VRTSvmsa/jre/bin/sparc/native_threads/jre         /opt/VRTSvmsa/jre/bin/sparc/native_threads/rmiregistry         /opt/VRTSvmsa/jre/jre_config.txt

游客 未注册

发表于 2007-4-6 14:49 /opt/VRTSvmsa/jre/lib/awt.properties         /opt/VRTSvmsa/jre/lib/content-types.properties         /opt/VRTSvmsa/jre/lib/font.properties-         /opt/VRTSvmsa/jre/lib/font.properties.ISO8859_15_FDIS         /opt/VRTSvmsa/jre/lib/font.properties.UTF8         /opt/VRTSvmsa/jre/lib/font.properties.UTF8.2.6         /opt/VRTSvmsa/jre/lib/font.properties.cs         /opt/VRTSvmsa/jre/lib/font.properties.el         /opt/VRTSvmsa/jre/lib/font.properties.hu         /opt/VRTSvmsa/jre/lib/font.properties.ja         /opt/VRTSvmsa/jre/lib/font.properties.ko         /opt/VRTSvmsa/jre/lib/font.properties.ko.2.5.1         /opt/VRTSvmsa/jre/lib/font.properties.ko_KR_UTF8         /opt/VRTSvmsa/jre/lib/font.properties.lt         /opt/VRTSvmsa/jre/lib/font.properties.lt_ISO8859_13         /opt/VRTSvmsa/jre/lib/font.properties.lv         /opt/VRTSvmsa/jre/lib/font.properties.lv_ISO8859_13         /opt/VRTSvmsa/jre/lib/font.properties.pl         /opt/VRTSvmsa/jre/lib/font.properties.ru         /opt/VRTSvmsa/jre/lib/font.properties.tr         /opt/VRTSvmsa/jre/lib/font.properties.zh_EUC_CN         /opt/VRTSvmsa/jre/lib/font.properties.zh_GBK         /opt/VRTSvmsa/jre/lib/font.properties.zh_TW_Big5         /opt/VRTSvmsa/jre/lib/font.properties.zh_TW_EUC_TW         /opt/VRTSvmsa/jre/lib/font.properties.zh_TW_EUC_TW.2.5.1         /opt/VRTSvmsa/jre/lib/i18n.jar         /opt/VRTSvmsa/jre/lib/i18n_g.jar         /opt/VRTSvmsa/jre/lib/psfont.properties.ja         /opt/VRTSvmsa/jre/lib/rt.jar         /opt/VRTSvmsa/jre/lib/rt_g.jar         /opt/VRTSvmsa/jre/lib/security/java.security         /opt/VRTSvmsa/jre/lib/serialver.properties         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libJdbcOdbc.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libXm.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libXm.so.3         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libawt.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libjava.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libjpeg.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libmath.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libmmedia.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libnet.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libsysresource.so         /opt/VRTSvmsa/jre/lib/sparc/green_threads/libzip.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libJdbcOdbc.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libawt.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libjava.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libjpeg.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libmath.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libmmedia.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libnet.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libsunwjit.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libsysresource.so         /opt/VRTSvmsa/jre/lib/sparc/native_threads/libzip.so         [ verifying class ]         /opt/VRTSvmsa/vmsa/java/vmsa.jar         /opt/VRTSvmsa/vmsa/os_properties         /opt/VRTSvmsa/vmsa/properties         [ verifying class ]         /opt/VRTSvmsa/bin/autostart         /opt/VRTSvmsa/bin/gen_params         /opt/VRTSvmsa/bin/pkg_params         /opt/VRTSvmsa/bin/server_params         /opt/VRTSvmsa/bin/vmsa_server         /opt/VRTSvmsa/vmsa/server/cmdserver         /opt/VRTSvmsa/vmsa/server/lib/2.x/libunixdevices.so         /opt/VRTSvmsa/vmsa/server/lib/2.x/libvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/2.x/libvxvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libcvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libunixdevices.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libvmdmp.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libvmdmpjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libvmtask.so         /opt/VRTSvmsa/vmsa/server/lib/3.0.x/libvxvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libcvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libsrvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libsrvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libunixdevices.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libvmdmp.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libvmdmpjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libvmtask.so         /opt/VRTSvmsa/vmsa/server/lib/3.1.1/libvxvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libcvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libsrvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libsrvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libunixdevices.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libvmdmp.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libvmdmpjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libvmtask.so         /opt/VRTSvmsa/vmsa/server/lib/3.1/libvxvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/libcvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/libjutil.so         /opt/VRTSvmsa/vmsa/server/lib/libnativetable.so         /opt/VRTSvmsa/vmsa/server/lib/libsrvmjava.so         /opt/VRTSvmsa/vmsa/server/lib/libsrvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/libsystemutils.so         /opt/VRTSvmsa/vmsa/server/lib/libunixdevices.so         /opt/VRTSvmsa/vmsa/server/lib/libvmdmp.so         /opt/VRTSvmsa/vmsa/server/lib/libvmdmpjava.so         /opt/VRTSvmsa/vmsa/server/lib/libvmstatjava.so         /opt/VRTSvmsa/vmsa/server/lib/libvmtask.so         /opt/VRTSvmsa/vmsa/server/lib/libvmtaskjava.so         /opt/VRTSvmsa/vmsa/server/lib/libvs.so         /opt/VRTSvmsa/vmsa/server/lib/libvxvmjava.so         /opt/VRTSvmsa/vmsa/server/vmsad         /opt/VRTSvmsa/vmsa/server/vmsaexec         [ verifying class ]         /opt/VRTSvmsa/bin/vmsa         /opt/VRTSvmsa/vmsa/java/help.jar         /opt/VRTSvmsa/vmsa/java/swingall.jar         [ verifying class ]         ## Executing postinstall script.                  Installation of was successful.         root@a1 # 安装Veritas Volume Manager 3.2的patch 注：                                                                                                      安装Volume Manager3.2的patch前得先装 SAN 以及它的patch，          不然Volume Manager3.2的部分patch会安装不成功 。         把Solaris的patch光盘放入CD-ROM or DVD-ROM                  root@a1 #         root@a1 # cd /cdrom/cdrom0/sun/progs/SAN         root@a1 # cp Solaris_8_SFK_packages.tar.gz  /tmp         root@a1 # gzcat -d SFKpackages.tar.Z |tar xf f -         x SUNWcfpl, 0 bytes, 0 tape blocks         x SUNWcfpl/pkgmap, 134 bytes, 1 tape blocks         x SUNWcfpl/pkginfo, 417 bytes, 1 tape blocks         x SUNWcfpl/install, 0 bytes, 0 tape blocks         x SUNWcfpl/install/copyright, 59 bytes, 1 tape blocks         x SUNWcfpl/install/depend, 932 bytes, 2 tape blocks         x SUNWcfpl/install/i.initd, 6368 bytes, 13 tape blocks         x SUNWcfplx, 0 bytes, 0 tape blocks         x SUNWcfplx/pkgmap, 101 bytes, 1 tape blocks         x SUNWcfplx/pkginfo, 447 bytes, 1 tape blocks         x SUNWcfplx/install, 0 bytes, 0 tape blocks         x SUNWcfplx/install/copyright, 59 bytes, 1 tape blocks         x SUNWcfplx/install/depend, 875 bytes, 2 tape blocks         x SUNWsan, 0 bytes, 0 tape blocks         x SUNWsan/pkgmap, 1237 bytes, 3 tape blocks         x SUNWsan/pkginfo, 520 bytes, 2 tape blocks         x SUNWsan/install, 0 bytes, 0 tape blocks         x SUNWsan/install/copyright, 59 bytes, 1 tape blocks         x SUNWsan/install/i.initd, 6368 bytes, 13 tape blocks         x SUNWsan/install/postinstall, 342 bytes, 1 tape blocks         x SUNWsan/install/postremove, 162 bytes, 1 tape blocks         x SUNWsan/reloc, 0 bytes, 0 tape blocks         x SUNWsan/reloc/etc, 0 bytes, 0 tape blocks         x SUNWsan/reloc/etc/init.d, 0 bytes, 0 tape blocks         x SUNWsan/reloc/etc/init.d/san_driverchk, 1266 bytes, 3 tape blocks         x SUNWsan/reloc/opt, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/bin, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/bin/san_recover, 4402 bytes, 9 tape blocks         x SUNWsan/reloc/opt/SUNWsan/etc, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/etc/san_drivers, 334 bytes, 1 tape blocks         x SUNWsan/reloc/opt/SUNWsan/etc/san_os, 266 bytes, 1 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man/sman1m, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man/sman1m/cfgadm_fp.1m, 20386 bytes, 40 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man/sman1m/luxadm.1m, 62449 bytes, 122 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man/sman7d, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/man/sman7d/scsi_vhci.7d, 10213 bytes, 20 tape blocks         x SUNWsan/reloc/opt/SUNWsan/patches, 0 bytes, 0 tape blocks         x SUNWsan/reloc/opt/SUNWsan/patches/patchconf, 364 bytes, 1 tape blocks                  root@a1 # pkgadd -d .                  The following packages are available:           1  SUNWcfpl      fp cfgadm plug-in library                            （sparc) 11.8.0,REV=2001.07.14.21.42           2  SUNWcfplx     fp cfgadm plug-in library （64-bit)                            （sparc) 11.8.0,REV=2001.07.14.21.42           3  SUNWsan       SAN Foundation Kit                            （sparc) 1.0                  Select package（s) you wish to process （or 'all' to process         all packages). （default: all) [?,??,q]: [Enter]                  Processing package instance from                  fp cfgadm plug-in library         （sparc) 11.8.0,REV=2001.07.14.21.42         Copyright 2001 Sun Microsystems, Inc. All rights reserved.         ## Processing package information.         ## Processing system information.         ## Verifying package dependencies.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.         ## Checking for setuid/setgid programs.                  This package contains scripts which will be executed with super-user         permission during the process of installing this package.                  Do you want to continue with the installation of [y,n,?] y                  Installing fp cfgadm plug-in library as                  ## Installing part 1 of 1.                  Installation of was successful.                  Processing package instance from                  fp cfgadm plug-in library （64-bit)         （sparc) 11.8.0,REV=2001.07.14.21.42         Copyright 2001 Sun Microsystems, Inc. All rights reserved.         ## Processing package information.         ## Processing system information.         ## Verifying package dependencies.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.         ## Checking for setuid/setgid programs.                  Installing fp cfgadm plug-in library （64-bit) as                  ## Installing part 1 of 1.                  Installation of was successful.                  Processing package instance from                  SAN Foundation Kit         （sparc) 1.0         Copyright 2001 Sun Microsystems, Inc. All rights reserved.         Using as the package base directory.         ## Processing package information.         ## Processing system information.            1 package pathname is already properly installed.         ## Verifying disk space requirements.         ## Checking for conflicts with packages already installed.                  The following files are already installed on the system and are being         used by another package:           /etc/init.d           /etc/rc3.d           /opt                  Do you want to install these conflicting files [y,n,?,q]  y         ## Checking for setuid/setgid programs.                  This package contains scripts which will be executed with super-user         permission during the process of installing this package.                  Do you want to continue with the installation of [y,n,?]  y                  Installing SAN Foundation Kit as                  ## Installing part 1 of 1.         /opt/SUNWsan/bin/san_recover         /opt/SUNWsan/man/sman1m/cfgadm_fp.1m         /opt/SUNWsan/man/sman1m/luxadm.1m         /opt/SUNWsan/man/sman7d/scsi_vhci.7d         [ verifying class ]         Modifying /opt/SUNWsan/etc/san_drivers         Modifying /opt/SUNWsan/etc/san_os         Modifying /opt/SUNWsan/patches/patchconf         [ verifying class ]         [ verifying class ]         /etc/rc3.d/S50san_driverchk         ## Executing postinstall script.                  Installation of was successful.                  The following packages are available:           1  SUNWcfpl      fp cfgadm plug-in library                            （sparc) 11.8.0,REV=2001.07.14.21.42           2  SUNWcfplx     fp cfgadm plug-in library （64-bit)                            （sparc) 11.8.0,REV=2001.07.14.21.42           3  SUNWsan       SAN Foundation Kit                            （sparc) 1.0                  Select package（s) you wish to process （or 'all' to process         all packages). （default: all) [?,??,q]:  q                  root@a1 #         root@a1 # cd /cdrom/cdrom0/sun/patch/SAN/8         root@A # cp 111847-07.zip /tmp         root@A # cd 8         root@A # unpack-patches                  Are you ready to unpack patches into /tmp/8? [y/n]: y                  Cleaning out /tmp/8...                  Unpacking.....         Patch 111095-13         Patch 111096-06         Patch 111097-12         Patch 111412-11         Patch 111413-10         Patch 111846-06         Patch 113766-02         Patch 113767-02         Patch 114475-01                  You should run: cd /tmp/8; ./install_patches                  *****************************************         * Special Information for these patches *         *****************************************                  Before installing these patches you require the SAN Foundation Kit.                  Also the patch 111847-xx in directory above.                  To install patches in this directory the current versions of         patches 108982, 108983, 108984 and 109529 must have already been         installed. They are part of the Solaris 8 extra patches and will         have been installed if you follow the EIS checklists.                  root@A # cd /tmp         root@A # unzip 111847-07.zip         Archive:  111847-07.zip            creating: 111847-07/           inflating: 111847-07/.diPatch                 inflating: 111847-07/patchinfo                 creating: 111847-07/SUNWsan/           inflating: 111847-07/SUNWsan/pkgmap             inflating: 111847-07/SUNWsan/pkginfo              creating: 111847-07/SUNWsan/install/           inflating: 111847-07/SUNWsan/install/checkinstall             inflating: 111847-07/SUNWsan/install/copyright             inflating: 111847-07/SUNWsan/install/i.none             inflating: 111847-07/SUNWsan/install/patch_checkinstall             inflating: 111847-07/SUNWsan/install/patch_postinstall             inflating: 111847-07/SUNWsan/install/postinstall             inflating: 111847-07/SUNWsan/install/preinstall              creating: 111847-07/SUNWsan/reloc/            creating: 111847-07/SUNWsan/reloc/opt/            creating: 111847-07/SUNWsan/reloc/opt/SUNWsan/            creating: 111847-07/SUNWsan/reloc/opt/SUNWsan/bin/           inflating: 111847-07/SUNWsan/reloc/opt/SUNWsan/bin/san_recover              creating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/            creating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman1m/           inflating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman1m/cfgadm_fp.1m             inflating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman1m/luxadm.1m              creating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman7d/

游客 未注册

发表于 2007-4-6 14:49 inflating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman7d/qlc.7d             inflating: 111847-07/SUNWsan/reloc/opt/SUNWsan/man/sman7d/scsi_vhci.7d             inflating: 111847-07/README.111847-07           root@A # patchadd -d 111847-07                  Checking installed patches...         Verifying sufficient filesystem capacity (dry run method)...         Installing patch packages...                  Patch number 111847-07 has been successfully installed.         See /var/sadm/patch/111847-07/log for details                  Patch packages installed:           SUNWsan                  root@A # cd /tmp/8; ./install_patches                  Patch cluster install script for SAN for Solaris 8                  *WARNING* SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES:         With or without using the save option, the patch installation process         will still require some amount of disk space for installation and         administrative tasks in the /, /usr, /var, or /opt partitions where         patches are typically installed.  The exact amount of space will         depend on the machine's architecture, software packages already         installed, and the difference in the patched objects size.  To be         safe, it is not recommended that a patch cluster be installed on a         system with less than 4 MBytes of available space in each of these         partitions.  Running out of disk space during installation may result         in only partially loaded patches.  Check and be sure adequate disk space         is available before continuing.                  Are you ready to continue with install? [y/n]:  y         Determining if sufficient save space exists...         Sufficient save space exists, continuing...         Installing patches located in /tmp/8         Installing 110696-04...           Installation of 110696-04 failed. Return code 8.         Installing 111095-10...           Installation of 111095-10 failed. Return code 25.         Installing 111096-04...           Installation of 111096-04 failed. Return code 25.         Installing 111097-10...           Installation of 111097-10 failed. Return code 25.         Installing 111412-09...         Installing 111413-08...         Installing 111846-04...           Installation of 111846-04 failed. Return code 25.         Installing 111847-04...         Installing 111893-04...           Installation of 111893-04 failed. Return code 8.                  The following patches were not able to be installed:                 110696-04                 111095-10                 111096-04                 111097-10                 111846-04                 111893-04                  For more installation messages refer to the installation logfile:           /var/sadm/install_data/SAN_for_Solaris_8_log                  Use '/usr/bin/showrev -p' to verify installed patch-ids.         Refer to individual patch README files for more patch detail.         Rebooting the system is usually necessary after installation.         root@a1 # ./install_patches                  Patch cluster install script for SAN for Solaris 8                  *WARNING* SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES:         With or without using the save option, the patch installation process         will still require some amount of disk space for installation and         administrative tasks in the /, /usr, /var, or /opt partitions where         patches are typically installed.  The exact amount of space will         depend on the machine's architecture, software packages already         installed, and the difference in the patched objects size.  To be         safe, it is not recommended that a patch cluster be installed on a         system with less than 4 MBytes of available space in each of these         partitions.  Running out of disk space during installation may result         in only partially loaded patches.  Check and be sure adequate disk space         is available before continuing.                  Are you ready to continue with install? [y/n]:  y         Determining if sufficient save space exists...         Sufficient save space exists, continuing...         Installing patches located in /tmp/8         Installing 111412-11...         Installing 113766-02...           Installation of 113766-02 failed. Return code 8 - Attempting to patch a package that is not installed         Installing 114475-01...           Installation of 114475-01 failed. Return code 8 - Attempting to patch a package that is not installed         Installing 113767-02...           Installation of 113767-02 failed. Return code 25 - A required patch is not applied         Installing 111095-13...         Installing 111096-06...         Installing 111097-12...         Installing 111413-10...         Installing 111846-06...                  The following patches were not able to be installed:                 113766-02                 114475-01                 113767-02                  For more installation messages refer to the installation logfile:           /var/sadm/install_data/SAN-SNIA_for_Solaris_8_log                  Use '/usr/bin/showrev -p' to verify installed patch-ids.         Refer to individual patch README files for more patch detail.         Rebooting the system is usually necessary after installation.                           root@a1 # cd  /cdrom/cdrom0/sun/patch/veritas-vm/3.2/8         root@A # unpack-patches                  Are you ready to unpack patches into /tmp/8? [y/n]: y                  Target for unpacking patches /tmp/8 exists!         May I delete /tmp/8? [y/n]: y                  Cleaning out /tmp/8...                  Unpacking.....         Patch 111904-07         Patch 113201-04                  You should run: cd /tmp/8; ./install_patches         root@a1 # cd /tmp/8; ./install_patches                  Patch cluster install script for VxVM 3.2 for Solaris 8                  *WARNING* SYSTEMS WITH LIMITED DISK SPACE SHOULD *NOT* INSTALL PATCHES:         With or without using the save option, the patch installation process         will still require some amount of disk space for installation and         administrative tasks in the /, /usr, /var, or /opt partitions where         patches are typically installed.  The exact amount of space will         depend on the machine's architecture, software packages already         installed, and the difference in the patched objects size.  To be         safe, it is not recommended that a patch cluster be installed on a         system with less than 4 MBytes of available space in each of these         partitions.  Running out of disk space during installation may result         in only partially loaded patches.  Check and be sure adequate disk space         is available before continuing.                  Are you ready to continue with install? [y/n]:  y         Determining if sufficient save space exists...         Sufficient save space exists, continuing...         Installing patches located in /tmp/8         Installing 111904-07...         Installing 113201-04...         For more installation messages refer to the installation logfile:           /var/sadm/install_data/VxVM_3.2_for_Solaris_8_log                  Use '/usr/bin/showrev -p' to verify installed patch-ids.         Refer to individual patch README files for more patch detail.         Rebooting the system is usually necessary after installation.                  root@a1 # 安装Volume Manager的License         在安装完成之后，需要安装Volume Manager的License。（注：因安装License与机器的hostid有关系，请先确认与hostid对应的Lincense）         root@a1 #         root@a1 # vxlicense -c         Please enter your key: 6170 9613 6908 0562 1549 898                  输入获得的license（例如： 61709613690805621549898）即可。          1.2.7        创建卷rootdg         分别在两台小型机（a1和b1 ）上运行一下命令创建rootdg卷：         # vxconfigd -m disable         # vxdctl init         # vxdg init rootdg         # vxdisk -f init c0t0d0s4 type=simple         # vxdctl add disk c0t0d0s4  type=simple         # vxdg adddisk c0t0d0s4         # vxdctl enable         # rm /etc/vx/reconfig.d/state.d/install-db                  然后运行以下命令，使双机重新启动 创建卷happydg         happy的卷的创建只需在一台机器上操作。 取消DMP功能         root@a1 #         root@a1 # vxdiskadm         Volume Manager Support Operations         Menu: VolumeManager/Disk                   1      Add or initialize one or more disks          2      Encapsulate one or more disks          3      Remove a disk          4      Remove a disk for replacement          5      Replace a failed or removed disk          6      Mirror volumes on a disk          7      Move volumes from a disk          8      Enable access to （import) a disk group          9      Remove access to （deport) a disk group          10     Enable （online) a disk device          11     Disable （offline) a disk device          12     Mark a disk as a spare for a disk group          13     Turn off the spare flag on a disk          14     Unrelocate subdisks back to a disk          15     Exclude a disk from hot-relocation use          16     Make a disk available for hot-relocation use          17     Prevent multipathing/Suppress devices from VxVM's view                  Hit RETURN to continue.  [Enter]                   18     Allow multipathing/Unsuppress devices from VxVM's view          19     List currently suppressed/non-multipathed devices          20     Change the disk naming scheme          21     Get the newly connected/zoned disks in VxVM view          list   List disk information                            ?      Display help about menu          ??     Display help about the menuing system          q      Exit from menus                  Select an operation to perform:  list                  List disk information         Menu: VolumeManager/Disk/ListDisk                    Use this menu operation to display a list of disks.  You can           also choose to list detailed information about the disk at           a specific disk device address.                  Enter disk device or "all" [ ,all,q,?] （default: all) [Enter]                  DEVICE       DISK         GROUP        STATUS         c0t0d0       -            -            error         c0t0d0       c0t0d0s4     rootdg       online         c0t1d0       -            -            online         c6t9d0       -            -            online         c6t10d0      -            -            online         c7t9d0       -            -            online         c7t10d0      -            -            online                  Device to list in detail [ ,none,q,?] （default: none) [Enter]         Volume Manager Support Operations         Menu: VolumeManager/Disk                   1      Add or initialize one or more disks          2      Encapsulate one or more disks          3      Remove a disk          4      Remove a disk for replacement          5      Replace a failed or removed disk          6      Mirror volumes on a disk          7      Move volumes from a disk          8      Enable access to （import) a disk group          9      Remove access to （deport) a disk group          10     Enable （online) a disk device          11     Disable （offline) a disk device          12     Mark a disk as a spare for a disk group          13     Turn off the spare flag on a disk          14     Unrelocate subdisks back to a disk          15     Exclude a disk from hot-relocation use          16     Make a disk available for hot-relocation use          17     Prevent multipathing/Suppress devices from VxVM's view                  Hit RETURN to continue. [Enter]                   18     Allow multipathing/Unsuppress devices from VxVM's view          19     List currently suppressed/non-multipathed devices          20     Change the disk naming scheme          21     Get the newly connected/zoned disks in VxVM view          list   List disk information