How to check VCS version and update ?
Dear all, I've been asked to manage few asymmetric failover win 2003 systems with Veritas Cluster Server installed: how can i check the current verision and if there was some hot-fix, and services pach installed ? Thanks in advance and Best Regards, /fabrizio32KViews2likes10CommentsVCS Cluster not starting.
Hello All, I am having difficulties trying to get VCS started on this system. I have attached what I have got so far. I apperciate any comments or suggestions as to go from here. Thank you The hostnames in the main.cf corrosponds to that of the servers. hastatus -sum VCS ERROR V-16-1-10600 Cannot connect to VCS engine VCS WARNING V-16-1-11046 Local system not available hasys -state VCS ERROR V-16-1-10600 Cannot connect to VCS engine hastop -all -force VCS ERROR V-16-1-10600 Cannot connect to VCS engine hastart / hastart -onenode dmesg: Exiting: Another copy of VCS may be running engine_A.log 2013/10/22 15:16:43 VCS NOTICE V-16-1-11051 VCS engine join version=4.1000 2013/10/22 15:16:43 VCS NOTICE V-16-1-11052 VCS engine pstamp=4.1 03/03/05-14:58:00 2013/10/22 15:16:43 VCS NOTICE V-16-1-10114 Opening GAB library 2013/10/22 15:16:43 VCS NOTICE V-16-1-10619 'HAD' starting on: db1 2013/10/22 15:16:45 VCS INFO V-16-1-10125 GAB timeout set to 15000 ms 2013/10/22 15:17:00 VCS CRITICAL V-16-1-11306 Did not receive cluster membership, manual intervention may be needed for seeding #gabconfig -a GAB Port Memberships =============================================================== #lltstat -nvv LLT node information: Node State Link Status Address * 0 db1 OPEN bge1 UP 00:03:BA:15 bge2 UP 00:03:BA:15 1 db2 CONNWAIT bge1 DOWN bge2 DOWN bash-2.05$ lltconfig LLT is running ps -ef | grep had root 826 1 0 15:16:43 ? 0:00 /opt/VRTSvcs/bin/had root 836 1 0 15:16:45 ? 0:00 /opt/VRTSvcs/bin/hashadowSolved18KViews3likes4Commentshow to probe resources
[root@system1]# /opt/VRTSvcs/bin/hastatus -sum -- SYSTEM STATE -- System State Frozen A system1 RUNNING 0 A system2 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService system1 Y N ONLINE B ClusterService system2 Y N OFFLINE B appsGroup system1 N N PARTIAL B appsGroup system2 N N OFFLINE B vxfen system1 Y N OFFLINE B vxfen system2 Y N OFFLINE -- RESOURCES NOT PROBED -- Group Type Resource System E appsGroup IP SysIP system1 E appsGroup IP SysIP system2 E appsGroup Mount mntGroup system1 E appsGroup Mount mntGroup system2 E appsGroup NIC SysNIC system1 E appsGroup NIC SysNIC system2 cant get my SysIP online because the resource has not been probed how do you probe the appsgroups in bold thanks mig31Solved18KViews2likes16CommentsHow to find the LUN size with veritas commands ?
HI , How to find out the LUN size for this disk emc0_1364 Here is the vxdisk list output vxdisk list emc0_1364 Device: emc0_1364 devicetag: emc0_1364 type: auto hostid: eusdlsdb005.logistics.corp disk: name=dgBNLDBD_ind03 id=1334844563.144. group: name=dgBNLDBD_ind id=1330446642.89.i nfo: format=cdsdisk,privoffset=256,pubslice=3,privslice=3 flags: online ready private autoconfig noautoimport imported thinrclm pubpaths: block=/dev/vx/dmp/emc0_1364s3 char=/dev/vx/rdmp/emc0_1364s3 guid: - udid: EMC%5FSYMMETRIX%5F000292601366%5F6601364008 site: - version: 3.1 iosize: min=512 (bytes) max=1024 (blocks) public: slice=3 offset=65792 len=33863488 disk_offset=0 private: slice=3 offset=256 len=65536 disk_offset=0 update: time=1337532691 seqno=0.42 ssb: actual_seqno=0.0 headers: 0 240 configs: count=1 len=51360 logs: count=1 len=4096 Defined regions: config priv 000048-000239[000192]: copy=01 offset=000000 enabled config priv 000256-051423[051168]: copy=01 offset=000192 enabled log priv 051424-055519[004096]: copy=01 offset=000000 enabled lockrgn priv 055520-055663[000144]: part=00 offset=000000 Multipathing information: numpaths: 2 sdgg state=enabled sdgh state=enabled I see two paths for this disk when i did fdisk on one disk it shows me two why from fdisk /dev/sdgg3 u 0 704 16964640 5 Whole disk /dev/sdgg8 u 0 704 16964640 f Unknown fdisk -l /dev/sdgg Disk /dev/sdgg (Sun disk label): 255 heads, 189 sectors, 704 cylinders Units = cylinders of 48195 * 512 bytes Device Flag Start End Blocks Id System /dev/sdgg3 u 0 704 16964640 5 Whole disk /dev/sdgg8 u 0 704 16964640 f Unknown [18KViews1like11CommentsVCS Cluster not starting.
Hi I am facing problem while trying to start VCS . From LOG : ============================================================== tail /var/VRTSvcs/log/engine_A.log 2014/01/13 21:39:14 VCS NOTICE V-16-1-11050 VCS engine version=5.1 2014/01/13 21:39:14 VCS NOTICE V-16-1-11051 VCS engine join version=5.1.00.0 2014/01/13 21:39:14 VCS NOTICE V-16-1-11052 VCS engine pstamp=Veritas-5.1-10/06/09-14:37:00 2014/01/13 21:39:14 VCS INFO V-16-1-10196 Cluster logger started 2014/01/13 21:39:14 VCS NOTICE V-16-1-10114 Opening GAB library 2014/01/13 21:39:14 VCS NOTICE V-16-1-10619 ‘HAD’ starting on: nsscls01 2014/01/13 21:39:16 VCS INFO V-16-1-10125 GAB timeout set to 30000 ms 2014/01/13 21:39:16 VCS NOTICE V-16-1-11057 GAB registration monitoring timeout set to 200000 ms 2014/01/13 21:39:16 VCS NOTICE V-16-1-11059 GAB registration monitoring action set to log system message 2014/01/13 21:39:31 VCS CRITICAL V-16-1-11306 Did not receive cluster membership, manual intervention may be needed for seeding ============================================================================================= root@nsscls01# hastatus -sum VCS ERROR V-16-1-10600 Cannot connect to VCS engine VCS WARNING V-16-1-11046 Local system not available Please advice how can I start the VCS.Solved16KViews2likes11CommentsHow to verify VCS installation on a system
Symantec recommends that you verify your installation of Symantec Cluster Server (VCS) on a system before you install or upgrade VCS. This allows you to know about the product prerequisites, installed product version, and configuration. You can verify installation of VCS on a system using the following techniques: Operating System (OS) commands Script-based Installer Symantec Operations Readiness Tools (SORT) checks VCS command validation OS commands You can run native OS commands on the system to verify whether VCS is installed. The following table lists the commands to verify the VCS installation and the VCS version and patches installed on the system. Use cases AIX HP-UX Linux Solaris Verifying VCS installation lslpp -l VRTSvcs swlist VRTSvcs rpm –qi VRTSvcs For Solaris 10: pkginfo –l VRTSvcs For Solaris 11: pkg info VRTSvcs Verifying VCS version and patches lslpp -l VRTSvcs swlist VRTSvcs rpm –qi VRTSvcs showrev –p | grep VRTSvcs You can use these commands to verify which product packages are installed on the system.To get a complete list of required and optional packages for VCS, see the product release notes on theSORTwebsite. Note:On Linux, there is no sparse patch or patch ID. Therefore, the package version itself indicates the patch version of the installed VCS. Advantage of using the OS command technique By default, native commands are available on a system and can be used with ease. Limitations of using the OS command technique You must run OS commands as root on the cluster nodes. OS commands are useful for package and patch validation. However, these commands do not provide complete information about the VCS product installation. You need to run multiple commands to validate whether the required packages are installed on the system Script-based Installer Symantec recommends that you use the script-based installer to install Symantec products. The script-based installercan be used to identify which products from the Storage Foundation and High Availability (SFHA) family are installed on the system. The installer script can be executed to get a list of VCS packages and their versions installed on the system. These commands can be executed on AIX, HP-UX, Linux, and Solaris. The installer also allows you to configure the product, verify the pre-installation requisites, and view the description of the product. The following command provides the major version of the product and packages installed on the system. However, it does not provide details such as join version, build date, and patches installed on the other nodes in the cluster. To use this command, VCS must be already installed on the system. To use the script-based installer to verify the version of VCS installed on the system Run the following command: #/opt/VRTS/install/installvcs<version> –version Whereversionis the specific release version. For example, to validate the VCS 6.1 installation on the system, run the following command: #/opt/VRTS/install/installvcs61 –version To initiate the VCS installation validation using the product DVD media provided by Symantec, run the following installer script: #<dvd-media-path>/installer -version The installer script lists the Symantec products installed on the system along with the version details of the products. You can also use this script to perform a pre-check of the required package dependencies to install the product. If the product is already installed on the system and you want to validate the list of packages and patches along with their version, run the following command: #/opt/VRTS/install/showversion This command provides details of the product installed on all the nodes in a cluster. This information includes the product name, required and optional packages installed on the system, installed and available product updates, version, and product license key. Advantage of using script-based installer A single script validates all nodes in the cluster. Therefore, it does not need any platform-specific commands for performing validation. Limitation of using script-based installer The VRTSsfcpi package must be installed on the systems. Note: The VRTSsfcpi package was first released in VCS 6.0 and is available in the later versions. For earlier versions, use the installer from the DVD media. As an alternative, you can launch theinstaller from the DVD provided by Symantec, regardless of the product version. For more information about installing VCS using installer, seeInstalling VCS using the installer. SORT checks SORT provides a set of web-based tools to automate and simplify time-consuming administrator tasks. For example, the data collector tool gathers system-related information and generates web-based and text-based custom reports. These reports capture the system and platform-related configuration details and list the Symantec products installed on the system. SORT generates the following custom reports: Installation and Upgrade Risk Assessment License/Deployment You can generate and view custom reports to check which Symantec products are installed on a system. These reports list the passed and failed checks and other significant details you can use to assess the system. The checks and recommendations depend on the installed product. For SORT checks, see System Assessments. To generate a SORT custom report, On theData Collectortab, download the appropriate data collector for your environment. Follow the instructions in the README file to install the data collector. Run the data collector. It analyzes the nodes in the cluster and stores results in an XML file. On theUpload Reportstab, upload the XML file to the SORT website. SORT generates a custom report with recommendations and links to the related information. For more information about custom reports, visithttps://sort.symantec.com. Advantage of using the SORT checks SORT checks provide comprehensive information about the installed product. Limitation of using the SORT checks SORT data collector is not a part of product media and must be downloaded and installed on the system to generate reports. VCS command validation VCS provides a set of commands to validate and provide additional details of the components installed as a part of VCS product installation. For more information about verifying the VCS installation using VCS commands, seeSymantec™ Cluster Server 6.1 Administrator's Guide. The VCS command validation method allows you to check if VCS is correctly configured on the nodes in a cluster. To verify the status of the VCS components such as Low-Latency Transport (LLT), Group Membership Services/Atomic Broadcast (GAB), and the VCS engine, you can inspect the content of the key VCS configuration files or run the following VCS commands. Component Command Provides GAB #gabconfig -W GAB protocol version LLT #lltconfig -W LLT protocol version VCS engine #had -version HAD engine version and join version Cluster #hasys -state Cluster state Advantages of using VCS commands VCS commands provide comprehensive information about the cluster. VCS commands can be used for configuring the cluster. Limitation of using VCS commands VCS commands can be used only after the VCS product is completely installed and configured on the system. Frequently asked questions The following is a list of VCS installation-related frequently asked questions: Where do I check the availability of the CPI installer on a system? The installer script is located at /opt/VRTS/install. Where are the CPI installation logs located? The installation logs are located at /opt/VRTS/install. Where do I find information about SORT checks and reports? For information about SORT checks and reports, visithttps://sort.symantec.com. How do I validate a system before installing VCS? Before you install VCS, you must make sure the system is ready. To validate the system, use the installer script on the Symantec DVD. To start the pre-installation validation on the system and verify whether the system meets the product installation requirements, run the following command: #installer –precheck14KViews0likes1CommentVxVM vxdg ERROR V-5-1-585 Unable to create shared disk group
Hi, To setup SFRAC, I need to configure I/O fencing on a 2-node VCS configuration. I am unable to create the shared diskgroup after configuring I/O Fencing. Without I/O Fencing, I am able to create the shared dikgroup. The error is: VxVM vxdg ERROR V-5-1-585 Disk group oradg: cannot create: Record not in disk group The two SPARC v400 servers "node1" and "node2 are connected to a Sun StorageTek 6140 array and the details are as follows: On "node1": node1 * / # vxdisk -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR disk_0 auto:none - - online invalid c1t3d0s2 - disk_1 auto:none - - online invalid c1t2d0s2 - disk_2 auto:cdsdisk disk_2 vxfencoorddg online c2t6d0s2 - disk_3 auto:cdsdisk disk_3 vxfencoorddg online c2t7d0s2 - disk_4 auto:cdsdisk - - online c2t0d0s2 - disk_5 auto:cdsdisk disk_5 vxfencoorddg online c2t5d0s2 - disk_6 auto:cdsdisk - - online c2t3d0s2 - disk_7 auto:none - - online invalid c2t1d0s2 - disk_8 auto:cdsdisk - - online c2t2d0s2 - disk_9 auto:none - - online invalid c2t4d0s2 - disk_10 auto:none - - online invalid c1t1d0s2 - disk_11 auto:ZFS - - ZFS c1t0d0s2 - On "node2": node2 * / # vxdisk -e list DEVICE TYPE DISK GROUP STATUS OS_NATIVE_NAME ATTR disk_0 auto:none - - online invalid c1t3d0s2 - disk_1 auto:none - - online invalid c1t1d0s2 - disk_2 auto:ZFS - - ZFS c1t0d0s2 - disk_3 auto:cdsdisk - - online c3t6d0s2 - disk_4 auto:cdsdisk - - online c3t7d0s2 - disk_5 auto:cdsdisk - - error c3t0d0s2 - disk_6 auto:cdsdisk - - online c3t5d0s2 - disk_7 auto:cdsdisk - - online c3t3d0s2 - disk_8 auto:none - - online invalid c3t1d0s2 - disk_9 auto:cdsdisk - - online c3t2d0s2 - disk_10 auto:none - - online invalid c3t4d0s2 - disk_11 auto:none - - online invalid c1t2d0s2 - On "node1": node1 * / # vxdg -s init oradg oradg01=disk_4 VxVM vxdg ERROR V-5-1-585 Disk group oradg: cannot create: Record not in disk group node1 * / # vxdg -s init oradg oradg01=disk_8 VxVM vxdg ERROR V-5-1-585 Disk group oradg: cannot create: Record not in disk group I have installed the latest ASL libraries for StorageTek 6140 array. Can anyone please help? Best Regards, Bruce12KViews1like21CommentsHow to check Veritas SF version installed
Hello everyone, I have installed Veritas (SF)5.0 MP1 in a couple of Solaris servers, however Ihave to verify another one, which version has installed. Is it there anything rather than pkginfo | grep ... etc? Is it there any command or file that shows the version currently installed? Thanks!Solved12KViews1like4CommentsFencing and Reservation Conflict
Hi to all I have redhat linux 5.9 64bit with SFHA 5.1 SP1 RP4 with fencing enable ( our storage device is IBM .Storwize V3700 SFF scsi3 compliant [root@mitoora1 ~]# vxfenadm -d I/O Fencing Cluster Information: ================================ Fencing Protocol Version: 201 Fencing Mode: SCSI3 Fencing SCSI3 Disk Policy: dmp Cluster Members: * 0 (mitoora1) 1 (mitoora2) RFSM State Information: node 0 in state 8 (running) node 1 in state 8 (running) ******************************************** in /etc/vxfenmode (scsi3_disk_policy=dmp and vxfen_mode=scsi3) vxdctl scsi3pr scsi3pr: on [root@mitoora1 etc]# more /etc/vxfentab # # /etc/vxfentab: # DO NOT MODIFY this file as it is generated by the # VXFEN rc script from the file /etc/vxfendg. # /dev/vx/rdmp/storwizev70000_000007 /dev/vx/rdmp/storwizev70000_000008 /dev/vx/rdmp/storwizev70000_000009 ****************************************** [root@mitoora1 etc]# vxdmpadm listctlr all CTLR-NAME ENCLR-TYPE STATE ENCLR-NAME ===================================================== c0 Disk ENABLED disk c10 StorwizeV7000 ENABLED storwizev70000 c7 StorwizeV7000 ENABLED storwizev70000 c8 StorwizeV7000 ENABLED storwizev70000 c9 StorwizeV7000 ENABLED storwizev70000 main.cf cluster drdbonesales ( UserNames = { admin = hlmElgLimHmmKumGlj } ClusterAddress = "10.90.15.30" Administrators = { admin } UseFence = SCSI3 ) ********************************************** I configured the coordinator fencing so I have 3 lun in a veritas disk group ( dmp coordinator ) All seems works fine but I noticed a lot of reservation conflict in the messages of both nodes On the log of the server I am constantly these messages: /var/log/messages Nov 26 15:14:09 mitoora2 kernel: sd 7:0:1:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 8:0:0:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 8:0:1:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 10:0:0:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 10:0:1:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 9:0:1:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 9:0:0:1: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 7:0:1:3: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 8:0:0:3: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 8:0:1:3: reservation conflict Nov 26 15:14:09 mitoora2 kernel: sd 10:0:1:3: reservation conflict You have any idea? Best Regards VincenzoSolved11KViews1like15Commentsvxddladm show DMP state as not active
Goodmorning, I have issue that I can't seem to solve and I'm dire need of assistance. I have veritas cluster 5.1 running on solaris 10 connected to an 6180 storage array. The array is directly connected to 2 hotsts. (no switch!). Controller port 1A is connected to host A controller port 1B is connected to host A controller port 2A is connected to host B controller port 2B is connected to host B. DMP is taking care of the multipathing bit and looks ok, however I see that the state is set to not active: Output fromt the vxddladm listsupport libname=libvxlsiall.so : LIB_NAME ASL_VERSION Min. VXVM version ========================================================== Libvxlsiall.so vm-5.1.100-rev-1 5.1 The output of the vxdmpadm list dmpEngenio : Filename: dmpEngenio APM name: dmpEngenio APM version: 1 Feature : VxVM VxVMversion 51 Array Types Supporred: A/PF-LSI Depending Array TypesA/P State :Not-Ative Output from vxdctl mode: mode : enabled. Both hosts show the same result state : Not-Active So my question is : How do I set the state to Active. Bare in mind that this is a full production system so I have make sure that any commands given will not disrupt production. I will schedule downtime in that case. Can someone assist me? Many thanks! Remco