Where install VIOM: on Windows? or on Linux?
Hi every one: I want to install VIOM, I never do it before, and my first question is: Where I should do it? In Windows envioroment? or in Linux Envioroment? All my clusters are in Linux Envioroment: Infoscale 8.0 on Red Hat 8.9. Other question: Is it posible install Cordination Point Service in the same server? All my clusters have 2 nodos: node one in one CPD (site 1) and the node two in other CPD (site 2). I think that the new server (VIOM+CP) shultd be another CPD (site 3). Correct? Thanks Jaime.
Apache doesn't start
Hi! I got a VCS configured with apache web server agent. I tried to put it online (from command line it works) in the cluster and I see the following in the Apache_A.log 2016/06/16 12:45:52 VCS ERROR V-16-10061-20318 Apache:ApacheDMZ:online:<Apache::Start> Could not determine Apache Version. 2016/06/16 12:45:52 VCS ERROR V-16-10061-20133 Apache:ApacheDMZ:online:Failed to online resource Anyone can tell me why is it? I run "httpd -v" from command line and I see apache version: 2.2.15 Thanks!
VCS on Linux using NPAR and VLAN tagging
I’m trying to enable a new configuration using NPAR and VLAN tagging to create private heartbeat networks. Which tool should I use to create my heartbeat interfaces which need to be vlan tagged? Does anyone know if the tagged interface should share the MAC of the real interface or should I try to create a unique MAC through software? Thanks
vxlicrep ERROR V-21-3-1015 Failed to prepare report for key
Dear all, we got a INFOSCALE FOUNDATION LNX 1 CORE ONPREMISE STANDARD PERPETUAL LICENSE CORPORATE. I have installed key using the vxlicinst -k <key> command. But when I want to check it using vxlicrep I'm getting this error for the given key: vxlicrep ERROR V-21-3-1015 Failed to prepare report for key = <key> We have Veritas Volume Manager 5.1 (VRTSvxvm-5.1.100.000-SP1_RHEL5 and VRTSvlic-3.02.51.010-0) running on RHEL 5.7 on 64 bits. I've read that the next step is to run vxkeyless set NONE, but I'm afraid to run this until I cannot see the license reported correctly by vxlicrep. What can I do to fix it? Thank you in advance. Kind regards, Laszlo
InfoScale 7.1 and large disks (8Tb) with FSS
Hi everyone, I had been successfully running FSS with (thin) 8Tb disk drives on SFCFSHA 6.1 and 6.2.1 (see:http://vcojot.blogspot.ca/2015/01/storage-foundation-ha-61-and-flexible.html) I am trying to reproduce the same kind of setup with InfoScale 7.1 and it seems to have issues with 8Tb drives. Here's the full setup description: 2 * RHEL6.8 hosts with 16gb RAM. 4 LSI virtual adapters, each with 15 drives. c0* and c1* have 2Tb drives. c2* and c3* have 8Tb drives. Both 2tb and 8tb drives are 'exported' and the cluster is stable. Here's what I noticed.. Creating an FSS DG works on 2tb drives but not on 8tb drives (it used to on 6.1 and 6.2.1): [root@vcs18 ~]# /usr/sbin/vxdg -s -o fss=on init FSS00dg ssd_2T_00 [root@vcs18 ~]# vxdg list FSS00dg Group: FSS00dg dgid: 1466522672.427.vcs18 import-id: 33792.426 flags: shared cds version: 220 alignment: 8192 (bytes) local-activation: shared-write cluster-actv-modes: vcs18=sw vcs19=sw ssb: on autotagging: on detach-policy: local dg-fail-policy: obsolete ioship: on fss: on storage-sources: vcs18 copies: nconfig=default nlog=default config: seqno=0.1027 permlen=51360 free=51357 templen=2 loglen=4096 config disk ssd_2T_00 copy 1 len=51360 state=clean online log disk ssd_2T_00 copy 1 len=4096 On the 8Tb drives, it fails with: [root@vcs18 ~]# vxdg destroy FSS00dg [root@vcs18 ~]# /usr/sbin/vxdg -s -o fss=on init FSS00dg ssd_8T_00 VxVM vxdg ERROR V-5-1-585 Disk group FSS00dg: cannot create: Record not in disk group One thing that I noticed is that the 8Tb drives, even though exported, do -not- show up on the remote machine: [root@vcs18 ~]# vxdisk list|grep _00 ssd_2T_00 auto:cdsdisk - - online exported ssd_2T_00_1 auto:cdsdisk - - online remote ssd_8T_00 auto:cdsdisk - - online exported One other thing to note is that the 'connectivity' seems a bit messed up on the 8Tb drives: [root@vcs18 ~]# vxdisk list ssd_2T_00|grep conn connectivity: vcs18 [root@vcs18 ~]# vxdisk list ssd_2T_00_1|grep conn connectivity: vcs19 [root@vcs18 ~]# vxdisk list ssd_8T_00|grep conn connectivity: vcs18 vcs19 That's (IMHO) an error since those 'virtual'drives are local to each of the nodes and the SCSI busses aren't shared vcs18 and vcs19 are two fully independent VMWare machines. This looks like a bug to me but since I don't work for a company with a vx software support contrat anymore I cannot report the issue. Thanks for reading, Vincent
Configuring VCS with main.cf and types.cf files
From release 7.0 onwards, VCS is a component that is bundled with InfoScale Availability and InfoScale Enterprise products. When you configure VCS, the Veritas High Availability Engine needs to know definitions of the cluster, service groups, resources, and dependencies among service groups and resources. VCS uses the main.cf and types.cf configuration files to convey the cluster, service groups, and resource definitions. The main.cf file comprises include clauses and definitions for the cluster, systems, service groups, and resources. The SystemList attribute designates the priority order and the list of systems where a service group can come up online. The types.cf defines the standard resource types for the VCS engine and the data type that can be set for an attribute. It also defines the parameters that are passed to the VCS engine. These configuration files can be generated in a variety of ways. For more information, see VCS configuration language. By default, both these files reside in the /etc/VRTSvcs/conf/config file. Only the first online system in the cluster reads the configuration files and keeps it in memory. Systems that are brought online after the first system derive configuration information from the existing systems in the cluster. You can also define environment variables to further configure VCS. For more information, see VCS environment variables. You can find other versions of Cluster Server on the SORT documentation page.
