Change the Host IP address in the Veritas cluster
Hello All, We have a Veritas cluster server setup (VCS-HA,VCS-CFS & VERITAS-RAC) where on few setup we required to change the data IP address of some host(node). I refer few notes but not sure except /etc/hosts is there any file need to update/edit. Please help me if you have any process/technote to make those change & make that changed IP persistant. Also would like to know the impact of this activity. The systems are Linux 6.5 & 6.6 & cluster versions are VCS 6.2 & 6.1.Solved3.6KViews0likes3Commentsdetaching vmdk files on vmware vm
When the application failover happens in VMware Guest enviorments, the VCS is responsible for failing over the application to other vm/vcs node on diffrent ESX host. In a scenario where the ESX/ESXi host itself faults, the VCS agents begin to fail over the application to the failover target system that resides on another host. The VMwareDisks agent communicates with the new ESX/ESXi host and initiates a disk detach operation on the faulted virtual machine. The agent then attaches the disk to the new failover target virtual machine. In this senario, how are the stale i/o from failing over guest/ESX host avoided? Are we on the mercy of VMware to take care of it? With SCSI3 PR this was the main problem that was solved. Moreover in such senario's even a garceful online detach wouldnt have gone through. I didnt find any references on VMware discussions forums as well. My customer wants to know about it, before he can deploy the application. Thanks, Raf3KViews0likes7CommentsConfiguring 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.2.1KViews0likes1CommentUsing third party Multipathing with VCS LVM agents
Using third party Multipathing with VCS LVM agents is mostly not clear in the documentation. With SF, you can understand why 3rd party Multipathing needs to be tested to be supported as SF integrates at a low-level with the storage and multipathing effect this, but with VCS, VCS integrates with LVM at a high level, activating and deactivating he volume groups (equivalent to importing and deporting Veritas diskgroups), so it is first unclear why any 3rd party multipathing software should not be supported, except for perhaps O/S multipathing which is tightly integrated with LVM where the command to activate or deactivate the diskgroup MAY be different if multipathing is involved. For AIX, the HCL specifically mentions VCS LVM agentswith third party Multipathing: The VCS LVM agent supports the EMC PowerPath third-party driver on EMC's Symmetrix 8000 and DMX series arrays. The VCS LVM agent supports the HITACHI HDLM third-party driver on Hitachi USP/NSC/USPV/USPVM, 9900V series arrays. but VCS LVM agentsare not mentioned for Linux or HP-ux - these should be, even if this is to say "no third party Multipathing is supported with VCS LVM agents" In the Linux 5.1 bundled agents guide, it IS clear thatno third party Multipathing is supported with VCS LVM agents: You cannot use the DiskReservation agent to reserve disks that have multiple paths. The LVMVolumeGroup and the LVMLogicalVolume agents can only be used with the DiskReservation agent, Symantec does not support the configuration of logical volumes on disks that have multiple paths However, it is not so clear with 6.0 which says: No fixed dependencies exist for LVMVolumeGroup Agent. When you create a volume group on disks with single path, Symantec recommends that you use the DiskReservation agent So in 6.0, DiskReservation is optional, not mandatory as in 5.1, but thebundled agents guide does not say why theDiskReservation agent is mandatory in 5.1 and it does not elaborate why it is recommended in 6.0 - i.e. the 6.0bundled agents guide does not explain the benefits of using theDiskReservation agent or the issues you may encounter if you don't use theDiskReservation agent. The6.0bundled agents guide says for theDiskReservation agent: In case of Veritas Dynamic Multi-Pathing, the LVMVolumeGroup and the LVMLogicalVolume agents can be used without the DiskReservation agent This says you can use Veritas Dynamic Multi-Pathing with LVM, but it doesn't explicitly say you can't use other multipathing software, and for the LVMVolumeGroup agent, the 6.0bundled agents guidegives examples using multipathing, but it does not say if this is Veritas Dynamic Multi-Pathing or third party. To me, as the examples say multipathing and NOT specifically Veritas DMP, this implies ALL multipathing is supported, but it is not clear. So it seems that for 5.1 and before, for Linux and HP-ux (if you go by HCL), all disk multipathing was not supported with VCS LVM agents, but in the 10 years I worked for a consultant at Symantec, not one customer did NOT use disk multipathing - this is essential redundancy and there is no point having LVM agents if they don't support disk multipathing, so I am not sure it can be correct that multipathing is not supported with VCS LVM agents. This is redeemed in part by the recent introduction of Veritas Dynamic Multi-Pathing being available as a separate product which doesn't require SF and can be used on non-VxVM disks. So can the support be clarified for 5.1 and 6.0 of the support ofthird party Multipathing with VCS LVM agents on this forum and the documents updated to make what is supported clearer. Thanks Mike2.1KViews0likes5CommentsRegarding Service grp in W_OFFLINE_PROPAGATE
Hi, We have a status ofW_OFFLINE_PROPAGATE for SAP_RPT_CI_GRP. O/P is root@mapls111# hastatus -sum -- SYSTEM STATE -- System State Frozen A mapls111 RUNNING 0 A mapls222 RUNNING 0 -- GROUP STATE -- Group System Probed AutoDisabled State B ClusterService mapls111 Y N OFFLINE B ClusterService mapls222 Y N ONLINE B SAP_RPT_CI_GRP mapls111 Y N OFFLINE B SAP_RPT_CI_GRP mapls222 Y N ONLINE Now the service grp is switched to another node, but we want to know that What isW_OFFLINE_PROPAGATE state?Why it comes?If it comes, then how to resolve it? Please assist. OS - Linux2KViews0likes1CommentI/O error on vxfs volume
Hello everyone, Please I need help regarding a volume I cannot mount. It is 2Symmetrix EMC SAN meta (emcpower), forming one dg (supposedly clonedg), divided into vol01 and vol02. Each day, the metasare cloned from the principal server and mounted, but yesterday we had this issue : /dev/vx/dsk/clonedg/vol01 460G 379G 77G 84% /clone/hydra/oracle df: `/clone/hydra/ora11g': Input/output error (for /dev/vx/dsk/clonedg/vol02) Note that vol01 works perfectly, but not 02. Last time it happened, it did a umount -l and waited for the next day for the clone and it worked. So I umounted it again and then tried to clone and remount, but this time, it does not work. I then tried to deport the dg, in the hope to import it, but no luck : # vxdg -C import clonedg VxVM vxdg ERROR V-5-1-10978 Disk group clonedg: import failed: No valid disk found containing disk group # vxdg -f import clonedg VxVM vxdg ERROR V-5-1-10978 Disk group clonedg: import failed: No valid disk found containing disk group I also did : vxdctl initdmp vxdisk scandisks and now I have this : # vxdisk list DEVICE TYPE DISK GROUP STATUS cciss/c0d0 auto:none - - online invalid emcpowera auto:cdsdisk - - error emcpowera auto - - error emcpowera auto - - error emcpowera auto - - error emcpowera auto - - error emcpowera auto - - error emcpowerb auto:cdsdisk - - error emcpowerb auto - - error emcpowerb auto - - error emcpowerb auto - - error emcpowerb auto - - error emcpowerb auto - - error emcpowerb auto - - error emcpowerc auto - - error emcpowerc auto - - error emcpowerc auto:cdsdisk - - error emcpowerc auto - - error emcpowerc auto - - error emcpowerc auto - - error emcpowerd auto:cdsdisk - - online udid_mismatch emcpowerd auto - - error emcpowere auto:cdsdisk - - online udid_mismatch emcpowere auto - - error emcpowerf auto - - error emcpowerf auto:cdsdisk - - online emcpowerf auto - - error emcpowerf auto - - error emcpowerf auto - - error emcpowerf auto - - error emcpowerg auto:LVM - - LVM Note that many volume are in error, and they are duplicated. From here, I don't know what to do, since I'm not expert in vxfs. so any help would be appreciated! Thank you.1.8KViews0likes4Comments‘vxdmppr’ utility information
Hello, With VxVM, we get ‘vxdmppr’ utility which performs SCSI 3 PR operations on the disks similar to sg_persist on Linux. But we don’t find much documentation around this utility. In one of the blogs we saw that its unsupported utility. Can someone throw light on it. Has someone used it in the past? Or does anyone know how this utility is getting used in VxVM? How to know if this is supported or not? Rafiq1.8KViews1like7CommentsVeritas InfoScale 7.0: Licensing Veritas InfoScale 7.0
You require a license to install and use Veritas InfoScale products. There are two ways you can register the Veritas InfoScale product license keys: Use key-based licensing When you purchase a Veritas InfoScale product, you receive a License Key certificate. The certificate specifies the product keys and the number of product licenses purchased. Use keyless licensing The license is registered based on the product you install. Within 60 days of choosing this option, you must install a valid license key corresponding to the license level, or continue with keyless licensing by managing the systems with Veritas InfoScale Operations Manager. You can register the product license keys either manually or by using the installer. You can use the vxlicinstupgrade utility, if you want to: Upgrade to another Veritas InfoScale product Upgrade a temporary license to a permanent license Manage co-existence of multiple licenses For more information on licensing Veritas InfoScale products, see: About Veritas InfoScale product licensing Registering Veritas InfoScale using product license keys Registering Veritas InfoScale product using keyless licensing Updating your product licenses Using the vxlicinstupgrade utility Veritas InfoScale documentation can be found on the SORT website.1.5KViews3likes0CommentsCFS NFS configuration
Hello team, I'm trying to configure a CFS NFS HA service, so I've executed this command on the cluster: cfsshare config -p nfs apbasedg locks /locks and then configured all the shares. The cfsnfs_locks volume was already created and mounted on the vcs, but now it's not able to mount it anymore: cfsshare display VCS WARNING V-16-1-10260 Resource does not exist: cfsnfs_locks CNFS metadata filesystem : Protocols Configured : none #RESOURCE MOUNTPOINT PROTOCOL OPTIONS scs-ESP-nfsshare_ESPgoldclient /ESP/goldclient NFS scs-ESP-nfsshare_ESPusrsaptrans /ESP/usr/sap/trans NFS scs-ESP-nfsshare_sapmntESP /sapmnt/ESP NFS scs-ESP-nfsshare_userdataESP /userdata/ESP NFS #cfsmntadm display List of mount points registered with cluster-configurationbut not associated with any node : /locks # vxdisk -g apbasedg list DEVICE TYPE DISK GROUP STATUS vmdk0_10 auto:sliced apbasedg_0 apbasedg online shared this is the volume where the cfsnfs_locks volume is available v cnfs_locks fsgen ENABLED 2097152 - ACTIVE - - pl cnfs_locks-01 cnfs_locks ENABLED 2097152 - ACTIVE - - but I'm not able to mount the volume: # cfsmount /locks Error: V-35-33: cfsmount: Cluster mount /locks not associated with any node It worked at first, but now no more. Can you please help Thanks1.1KViews1like2Comments