================================================================== Hi, Now i was trying to configure on single node and getting this error as below. i think we can try to configure on single node it should not give any error to start LLT, GAB,HAD, sh-3.2# /opt/VRTS/install/installvcs -configure Veritas Cluster Server 5.1 Configure Program Copyright (c) 2009 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. The Licensed Software and Documentation are deemed to be "commercial computer software" and "commercial computer software documentation" as defined in FAR Sections 12.212 and DFARS Section 227.7202. Logs are being written to /var/tmp/installvcs-201201231443EYn while installvcs is in progress. Enter the Solaris x64 system names separated by spaces: [q,?] (hostname) Veritas Cluster Server 5.1 Configure Program hostname Logs are being written to /var/tmp/installvcs-201201231443EYn while installvcs is in progress Verifying systems: 100% Estimated time remaining: 0:00 5 of 5 Checking system communication ........................................................................................... Done Checking release compatibility .......................................................................................... Done Checking installed product .............................................................................................. Done Checking platform version ............................................................................................... Done Performing product prechecks ............................................................................................ Done System verification checks completed successfully If you plan to run VCS on a single node without any need for adding cluster node online, you have an option to proceed without starting GAB and LLT. Starting GAB and LLT is recommended. Do you want to start GAB and LLT? [y,n,q] (y) VCS is already configured. If you re-configure VCS, you will lose all the current configurations in main.cf. Do you want to re-configure VCS? [y,n,q] (n) y Veritas Cluster Server 5.1 Configure Program hostname To configure VCS, answer the set of questions on the next screen. When [b] is presented after a question, 'b' may be entered to go back to the first question of the configuration set. When [?] is presented after a question, '?' may be entered for help or additional information about the question. Following each set of questions, the information you have entered will be presented for confirmation. To repeat the set of questions and correct any previous errors, enter 'n' at the confirmation prompt. No configuration changes are made to the systems until all configuration questions are completed and confirmed. Press [Enter] to continue: Veritas Cluster Server 5.1 Configure Program hostname To configure VCS the following information is required: A unique Cluster name A unique Cluster ID number between 0-65535 Two or more NIC cards per system used for heartbeat links One or more heartbeat links are configured as private links One heartbeat link may be configured as a low priority link All systems are being configured to create one cluster Enter the unique cluster name: [q,?] vcscluster Enter a unique Cluster ID number between 0-65535: [b,q,?] (0) 1 Discovering NICs on hostname ........................................................ Discovered e1000g0 e1000g1 e1000g2 To use aggregated interfaces for private heartbeat, enter the name of an aggregated interface. To use a NIC for private heartbeat, enter a NIC which is not part of an aggregated interface. Enter the NIC for the first private heartbeat link on hostname: [b,q,?] e1000g1 Would you like to configure a second private heartbeat link? [y,n,q,b,?] (y) Enter the NIC for the second private heartbeat link on hostname: [b,q,?] e1000g2 Do you want to configure an additional low priority heartbeat link? [y,n,q,b,?] (n) Checking Media Speed for e1000g1 on hostname ...................................................................... 1000 Checking Media Speed for e1000g2 on hostname ...................................................................... 1000 Veritas Cluster Server 5.1 Configure Program hostname Cluster information verification: Cluster Name: vcscluster Cluster ID Number: 1 Private Heartbeat NICs for hostname: link1=e1000g1 link2=e1000g2 Is this information correct? [y,n,q,b,?] (y) Veritas Cluster Server 5.1 Configure Program hostname Virtual IP can be specified in RemoteGroup resource, and can be used to connect to the cluster using Java GUI The following data is required to configure the Virtual IP of the Cluster: A public NIC used by each system in the cluster A Virtual IP address and netmask Do you want to configure the Virtual IP? [y,n,q,?] (n) Veritas Cluster Server 5.1 Configure Program hostname Veritas Cluster Server can be configured to utilize Symantec Security Services Running VCS in Secure Mode guarantees that all inter-system communication is encrypted, and users are verified with security credentials. When running VCS in Secure Mode, NIS and system usernames and passwords are used to verify identity. VCS usernames and passwords are no longer utilized when a cluster is running in Secure Mode. Before configuring a cluster to operate using Symantec Security Services, another system must already have Symantec Security Services installed and be operating as a Root Broker. Refer to the Veritas Cluster Server Installation Guide for more information on configuring a Symantec Product Authentication Service Root Broker. Would you like to configure VCS to use Symantec Security Services? [y,n,q] (n) Veritas Cluster Server 5.1 Configure Program hostname The following information is required to add VCS users: A user name A password for the user User privileges (Administrator, Operator, or Guest) Do you want to set the username and/or password for the Admin user (default username = 'admin', password='password')? [y,n,q] (n) Do you want to add another user to the cluster? [y,n,q] (n) Veritas Cluster Server 5.1 Configure Program hostname VCS User verification: User: admin Privilege: Administrators Passwords are not displayed Is this information correct? [y,n,q] (y) Veritas Cluster Server 5.1 Configure Program hostname The following information is required to configure SMTP notification: The domain-based hostname of the SMTP server The email address of each SMTP recipient A minimum severity level of messages to send to each recipient Do you want to configure SMTP notification? [y,n,q,?] (n) Veritas Cluster Server 5.1 Configure Program hostname The following information is required to configure SNMP notification: System names of SNMP consoles to receive VCS trap messages SNMP trap daemon port numbers for each console A minimum severity level of messages to send to each console Do you want to configure SNMP notification? [y,n,q,?] (n) All VCS processes that are currently running must be stopped Do you want to stop VCS processes now? [y,n,q,?] (y) Veritas Cluster Server 5.1 Configure Program hostname Logs are being written to /var/tmp/installvcs-201201231443EYn while installvcs is in progress Stopping VCS: 100% Estimated time remaining: 0:00 8 of 8 Performing VCS prestop tasks ............................................................................................ Done Stopping vxatd .......................................................................................................... Done Stopping had ............................................................................................................ Done Stopping hashadow ....................................................................................................... Done Stopping CmdServer ...................................................................................................... Done Stopping vxfen .......................................................................................................... Done Stopping gab ............................................................................................................ Done Stopping llt ............................................................................................................ Done Veritas Cluster Server Shutdown completed successfully Veritas Cluster Server 5.1 Configure Program hostname Logs are being written to /var/tmp/installvcs-201201231443EYn while installvcs is in progress Starting VCS: 87% ______________ Estimated time remaining: 0:40 7 of 8 Performing VCS configuration ............................................................................................ Done Starting llt ............................................................................................................ Done Starting gab ............................................................................................................ Done Starting vxfen .......................................................................................................... Done Starting had ............................................................................................................ Done Starting hashadow ....................................................................................................... Done Starting CmdServer ...................................................................................................... Done Veritas Cluster Server Startup did not complete successfully llt failed to start on hostname gab failed to start on hostname vxfen failed to start on hostname had failed to start on hostname hashadow failed to start on hostname It is strongly recommended to reboot the following systems: hostname Execute '/usr/sbin/shutdown -y -i6 -g0' to properly restart your systems installvcs log files, summary file, and response file are saved at: /opt/VRTS/install/logs/installvcs-201201231443EYn bash-3.2# ========================================================================== bash-3.2# dladm show-dev e1000g0 link: up speed: 1000 Mbps duplex: full e1000g1 link: unknown speed: 0 Mbps duplex: half e1000g2 link: unknown speed: 0 Mbps duplex: half bash-3.2# pkginfo -l VRTSllt PKGINST: VRTSllt NAME: Veritas Low Latency Transport by Symantec CATEGORY: system ARCH: i386 VERSION: 5.1 BASEDIR: / VENDOR: Symantec Corporation DESC: Veritas Low Latency Transport by Symantec PSTAMP: Veritas-5.1-10/06/09-18:05:35 INSTDATE: Jan 23 2012 12:32 STATUS: completely installed FILES: 91 installed pathnames 28 shared pathnames 31 directories 15 executables 2831 blocks used (approx) bash-3.2# pkginfo -l VRTSgab PKGINST: VRTSgab NAME: Veritas Group Membership and Atomic Broadcast by Symantec CATEGORY: system ARCH: i386 VERSION: 5.1 BASEDIR: / VENDOR: Symantec Corporation DESC: Veritas Group Membership and Atomic Broadcast by Symantec PSTAMP: Veritas-5.1-10/06/09-18:05:35 INSTDATE: Jan 23 2012 12:32 STATUS: completely installed FILES: 103 installed pathnames 27 shared pathnames 30 directories 7 executables 2749 blocks used (approx) bash-3.2# ifconfig -a lo0: flags=2001000849 mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 e1000g0: flags=1000843 mtu 1500 index 2 inet 192.168.0.222 netmask ffffff00 broadcast 192.168.0.255 ether 0:c:29:42:db:a5 bash-3.2# cat /etc/llttab set-node hostname set-cluster 1 link e1000g1 /dev/e1000g:1 - ether - - link e1000g2 /dev/e1000g:2 - ether - - bash-3.2# cat /etc/llthosts 0 hostname bash-3.2#bash-3.2# cat path_to_inst # # Caution! This file contains critical kernel state # "/iscsi" 0 "iscsi" "/pseudo" 0 "pseudo" "/options" 0 "options" "/xsvc" 0 "xsvc" "/objmgr" 0 "objmgr" "/scsi_vhci" 0 "scsi_vhci" "/isa" 0 "isa" "/isa/i8042@1,60" 0 "i8042" "/isa/i8042@1,60/keyboard@0" 0 "kb8042" "/isa/i8042@1,60/mouse@1" 0 "mouse8042" "/isa/lp@1,378" 0 "ecpp" "/isa/asy@1,3f8" 0 "asy" "/isa/asy@1,2f8" 1 "asy" "/isa/fdc@1,3f0" 0 "fdc" "/isa/fdc@1,3f0/fd@0,0" 0 "fd" "/ramdisk" 0 "ramdisk" "/cpus" 0 "cpunex" "/cpus/cpu@0" 0 "cpudrv" "/pci@0,0" 0 "npe" "/pci@0,0/pci8086,7191@1" 0 "pci_pci" "/pci@0,0/display@f" 0 "vgatext" "/pci@0,0/pci15ad,7a0@15" 0 "pcieb" "/pci@0,0/pci15ad,7a0@15,1" 1 "pcieb" "/pci@0,0/pci15ad,7a0@15,2" 2 "pcieb" "/pci@0,0/pci15ad,7a0@15,3" 3 "pcieb" "/pci@0,0/pci15ad,7a0@15,4" 4 "pcieb" "/pci@0,0/pci15ad,7a0@15,5" 5 "pcieb" "/pci@0,0/pci15ad,7a0@15,6" 6 "pcieb" "/pci@0,0/pci15ad,7a0@15,7" 7 "pcieb" "/pci@0,0/pci15ad,7a0@16" 8 "pcieb" "/pci@0,0/pci15ad,7a0@16,1" 9 "pcieb" "/pci@0,0/pci15ad,7a0@16,2" 10 "pcieb" "/pci@0,0/pci15ad,7a0@16,3" 11 "pcieb" "/pci@0,0/pci15ad,7a0@16,4" 12 "pcieb" "/pci@0,0/pci15ad,7a0@16,5" 13 "pcieb" "/pci@0,0/pci15ad,7a0@16,6" 14 "pcieb" "/pci@0,0/pci15ad,7a0@16,7" 15 "pcieb" "/pci@0,0/pci15ad,7a0@17" 16 "pcieb" "/pci@0,0/pci15ad,7a0@17,1" 17 "pcieb" "/pci@0,0/pci15ad,7a0@17,2" 18 "pcieb" "/pci@0,0/pci15ad,7a0@17,3" 19 "pcieb" "/pci@0,0/pci15ad,7a0@17,4" 20 "pcieb" "/pci@0,0/pci15ad,7a0@17,5" 21 "pcieb" "/pci@0,0/pci15ad,7a0@17,6" 22 "pcieb" "/pci@0,0/pci15ad,7a0@17,7" 23 "pcieb" "/pci@0,0/pci15ad,7a0@18" 24 "pcieb" "/pci@0,0/pci15ad,7a0@18,1" 25 "pcieb" "/pci@0,0/pci15ad,7a0@18,2" 26 "pcieb" "/pci@0,0/pci15ad,7a0@18,3" 27 "pcieb" "/pci@0,0/pci15ad,7a0@18,4" 28 "pcieb" "/pci@0,0/pci15ad,7a0@18,5" 29 "pcieb" "/pci@0,0/pci15ad,7a0@18,6" 30 "pcieb" "/pci@0,0/pci15ad,7a0@18,7" 31 "pcieb" "/pci@0,0/pci-ide@7,1" 0 "pci-ide" "/pci@0,0/pci-ide@7,1/ide@0" 0 "ata" "/pci@0,0/pci-ide@7,1/ide@0/cmdk@0,0" 0 "cmdk" "/pci@0,0/pci-ide@7,1/ide@1" 1 "ata" "/pci@0,0/pci-ide@7,1/ide@1/sd@0,0" 0 "sd" "/pci@0,0/pci15ad,1976@10" 0 "mpt" "/pci@0,0/pci15ad,1976@10/sd@0,0" 1 "sd" "/pci@0,0/pci15ad,790@11" 1 "pci_pci" "/pci@0,0/pci15ad,790@11/pci15ad,750@0" 0 "e1000g" "/pci@0,0/pci15ad,790@11/pci1274,1371@1" 0 "audioens" "/pci@0,0/pci15ad,790@11/pci15ad,750@3" 1 "e1000g" "/pci@0,0/pci15ad,790@11/pci15ad,750@4" 2 "e1000g" "/agpgart" 0 "agpgart" bash-3.2#