SFHA Solutions 6.0.1: Understanding the udid_mismatch flag
Beginning with the Veritas Storage Foundation and High Availability release 5.0, a unique disk identifier (UDID) is added to the disk's private region when the disk is initialized or when the disk is imported into a disk group (if this identifier does not already exist). When a disk is brought online, the current UDID value that is known to the Device Discovery Layer (DDL) is compared with the UDID that is set in the disk’s private region. If the UDID values do not match, the udid_mismatch flag is set on the disk. This usually means that the disk has been copied from another disk. For example, a disk may be copied by creating a hardware snapshot or clone, by using dd or some other command to replicate the disk, or by building a new logical unit (also known as a LUN or virtual disk device) from the space that was previously used by a deleted LUN. Duplicated disks are prevented from being imported to avoid duplicate disk IDs. The vxdisk list command displays the udid_mismatch flag in the event that the UDID values do not match. For information on the udid_mismatch flag, see: Handling cloned disks with duplicated identifiers Writing a new UDID to a disk Importing a disk group containing cloned disks Sample cases of operations on cloned disks Clearing the udid_mismatch flag for non-clone disks For information on what the udid_mismatch flag indicates, and how to solve mismatches, see: TechNote128957 - Explanation of what the udid_mismatch flag indicates in vxdisk list output Information regarding the udid_mismatch flag can also be found in the PDF versions of the following guides: Veritas Storage Foundation Cluster File System High Availability Administrator's Guide Veritas Storage Foundation and High Availability Solutions Troubleshooting Guide vxdisk (1M) 6.0.1 manual pages: AIX HP-UX Linux Solaris vxdisk (1M) manual pages and Veritas Storage Foundation and High Availability documentation for other platforms and releases can be found on the SORT website.
SFHA Solutions 6.0.1: Using Veritas Cluster Server Simulator
Veritas Cluster Server (VCS) Simulator enables you to simulate and test cluster configurations. You can use VCS Simulator to view and modify service group and resource configurations and test failover behavior. VCS Simulator can run on a stand-alone system and does not require any additional hardware. You can install VCS Simulator only on a Windows operating system. VCS Simulator runs an identical version of the VCS High Availability Daemon (HAD) as in a cluster, ensuring that failover decisions are identical to those in an actual cluster. Using VCS Simulator, you can test configurations from different operating systems. For example, you can run VCS Simulator to test configurations for VCS clusters on Windows, AIX, HP-UX, Linux, and Solaris operating systems. VCS Simulator also enables you to create and test global clusters. You can administer VCS Simulator from the Java Console or from the command line. To download VCS Simulator, see: http://go.symantec.com/vcsm_download For more information on installing and administering VCS Simulator, see: Installing VCS Simulator on a Windows System Upgrading VCS Simulator Administering VCS Simulator Predicting VCS behavior using VCS Simulator Administering VCS Simulator from the Java Console Administering VCS Simulator from the command line interface VCS documentation for other releases and platforms can be found on the SORT website.
vxdisk list shows Simple type disks as "error"
Hi , Am facing issue on Aix 7 with VxVm VRTSvxvm 6.0.300.0 A F Veritas Volume Manager by and am using the Third party Multipathing software (Dynapath). Problem is that after the "vxdisk scandisk" vxdisk list is showing the foriegn disk in "error " state.Please suggest a way. Steps: - creating nodes in /dev/vx/dmp, /dev/vx/rdmp - Added as foreign disk - vxdisk scandisks -vxdctl enable -vxdisk list bash-3.2# vxdisk list DEVICE TYPE DISK GROUP STATUS hdisk0 auto:LVM - - LVM hdiskdpd0 simple - - error hdisk1 auto:LVM - - LVM hdisk3 auto:LVM - - LVM hdisk4 auto:none - - online invalid hdisk5 auto:LVM - - LVM bash-3.2# vxdisk list hdiskdpd0 Device: hdiskdpd0 devicetag: hdiskdpd0 type: simple flags: error private foreign pubpaths: block=/dev/hdiskdpd0 char=/dev/rhdiskdpd0 guid: - udid: INVALID site: - errno: Device path not valid‘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? RafiqUnderstanding the V-16-1-10600 error message for Windows
The hacli command communicates with the high availability daemon (HAD) process for any operations on objects such as clusters, systems, service groups, and resources. If the hacli command cannot communicate with the HAD process, the following error message occurs: VCS ERROR V-16-1-10600 Cannot connect to VCS engine This message is displayed when: The cluster cannot start, because GAB cannot seed the cluster. As a result, HAD cannot start on a node. Veritas Cluster High Availability Engine (Had.exe) hangs in the Starting state. GAB requires a minimum number of nodes be online to successfully seed the cluster. The minimum number of nodes is defined in the C:\Program Files\VERITAS\comms\gab\gabtab.txt file. When all nodes go down and one or more nodes do not come online, it is possible that the minimum node requirement is not reached. Symantec Product Authentication Service (vxat or vxeat depending on version) is having problems even if HAD is in the Running state. To determine the cause of the error: Check if the HAD error message is displayed in the Application Event Viewer, as shown in the figure below: Figure 1 - Command Prompt and Application Event Viewer. Check the Services Control Panel to see if the Veritas High Availability Engine Startup service is in the Starting state. Use one of the following commands to determine the state of the cluster: C:\>hastatus -sum or C:\>hasys –state To fix the error in the case where HAD cannot start: Check the gabtab.txt file for information that defines the seeding requirement: the minimum number of nodes for this cluster that must be available before HAD can start. HAD will not start until the cluster is seeded, even on only a subset of nodes. HAD must be running on a node for cluster operations to commence on that node. If the Veritas High Availability Engine Startup service is in the Starting state, you must manually seed GAB. Enter the following commands: C:\>gabconfig -c –x (This command configures GAB, if needed, and seeds a node or nodes, regardless of the minimum specified in the gabtab.txt file.) C:\>hasys –state (This command displays the current status of all cluster nodes that are online.) Note: Starting with version 6.0.2, the VCS Administrator’s Guide instructs users to use gabconfig -x to manually seed the cluster, while the VCS Administrator’s Guides for 6.0.1 and earlier versions specify using gabconfig -c -x instead. The -x option forces a subset of the required minimum nodes to seed. In a two node cluster that has only one node online, this seeds the one node and allows HAD to start on that node. Once HAD has started on one node, bringing the other node online allows it to join the cluster, as long as the private network communication between nodes is working. If the configuration file is valid, the node should transition from LOCAL_BUILD to RUNNING. However, you must run the hasys –state command repeatedly to see if the status changes, as the command shows a snapshot of the current state. In the case where Symantec Product Authentication Service is having issues, you need to fix and reconfigure the Symantec Product Authentication Service to resolve the HAD connectivity issue. For more information, see: About the high availability daemon (HAD) About the Symantec Product Authentication Service About Group Membership Services and Atomic Broadcast (GAB) VCS ERROR V-16-1-10600 Cannot connect to VCS engine Had.exe, the Veritas Cluster High Availability Engine, hangs in a "Starting" state Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.SFHA Solutions 6.1: Checking Storage Foundation and High Availability Solutions product versions
Symantec provides several methods to check Storage Foundation and High Availability (SFHA) Solutions product versions, plus various requirement information. You can check the existing product versions using the installer command with the -version option before or after installation. After you have installed the current version of the product, you can use the showversion script in the /opt/VRTS/install directory to find version information. For details on checking the product version using the installer, see: Checking installed product versions and downloading maintenance releases and hot fixes You can check the base version or the batch version of the SFHA Solutions product that is installed, using the following commands for different platforms: lslpp –L for AIX rpm –qi for Linux pkginfo –l for Solaris For example, to display the version of Veritas Volume Manager for Solaris, enter: pkginfo -l VRTSvxvm The PSTAMP value in the output has the version information. For example: PSTAMP: 6.1.0.000-GA-2013-10-21 You can also check the product version using the Deployment Server. For more details, see: SFHA Solutions 6.1: Support for centralized installations using the Deployment Server If you use a GUI with your SFHA Solutions product, the About information on the Help tab provides a simple way to check the product version. For details on checking Symantec Dynamic Multi-Pathing for VMware product versions, see the following Symantec Connect article: SFHA Solutions 6.1: Checking Symantec Dynamic Multi-Pathing for VMware product versions Symantec Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.Symantec High Availability 6.1 Solution: Configuration in VMware Site Recovery Manager (SRM) environment
The Symantec High Availability 6.1 Solution provides scripts to perform some of the configuration tasks required for application monitoring continuity in a VMware SRM environment. In the event of a failure, when the SRM recovery plan is executed, the Symantec High Availability recovery command retrieves the application status, and the Symantec Cluster Server (VCS) network and application-specific agents bring the network and application components online. This ensures application monitoring continuity after the failover. For information about configuring the Symantec High Availability Solution in a VMware SRM environment, see: Configuring Symantec High Availability Solution in VMware SRM environment This quick reference guide provides: A complete workflow of the configuration tasks involved A quick start for each high-level task A list of reference documents and their download location Storage Foundation and High Availability and ApplicationHA documentation for other releases and platforms can be found on the SORT website.
VxVM: Understanding the V-5-1-587 error message
The V-5-1-587 error message indicates that a disk import failed. The second portion of the message briefly describes the reason for the error. Depending on the reason, you can either clear the locks or force the disk group to be imported to solve the issue. UMI V-5-1-587 Clearing the locks Second Part of the Message Description Disk is in use by another host Indicates the disk group that you tried to import has disk(s) moved from a crashed system, or from a system that fails to detect the group before the move. You must clear the locks stored on the disks. No valid disk found containing disk group Indicates the disk group does not contain any valid disks (but it might contain disks). A mismatch between the host ID in the configuration copies and that stored in the /etc/vx/volboot file may make the disks invalid. To solve these issues, do one of the following: Clear the locks on a specific set of devices: # vxdisk clearimport devicename ... Clear the locks during import: # vxdg -C import diskgroup Warning: When you use the vxdisk clearimport or vxdg -C import command to clear the locks, make sure that the disks in this disk group are not in use by another host. If the disks are in use by another host, clearing the locks allows the disks to be accessed at the same time from multiple hosts. This can result in data corruption. Forcing the disk group to be imported Second Part of the Message Description Disk for disk group not found Indicates the disk(s) is not accessible after the last successful import of the disk group. This is a recoverable error. Disk group has no valid configuration copies Indicates a fatal error. You must repair the hardware or create a new disk group, and recover the disk group configuration and data. To solve these issues, force the disk group to be imported: # vxdg -f import diskgroup The -f option forces an import if one or more disks are currently unusable or inaccessible. When you use the -f option to force the import of an incomplete disk group, it counts as a successful import. The next time this disk group is imported, the –f option is no longer required. The import completes successfully as long as all the disks in this disk group are accessible. Warning: Be careful when you use the -f option. It can cause the same disk group to be imported twice from different sets of disks. Consequently, the disk group configuration may become inconsistent. You can also use the vxdiskadm utility to clear the locks or force the disk groups to be imported: Select the menu item “Enable access to (deport) a disk group” to deport a disk group. Select the menu item “Enable access to (import) a disk group” to import a disk group. The vxdiskadm import operation checks for host import locks and prompts to see if you want to clear any that are found. It also starts volumes in the disk group. For more information on importing the disk groups, see: Importing a disk group Forcibly importing a disk group Troubleshooting issues with importing disk groups vxdg (1M) 6.0.1 manual pages: AIX HP-UX Linux Solaris vxdiskadm (1M) 6.0.1 manual pages: AIX HP-UX Linux Solaris Veritas Storage Foundation and High Availability documentation for other releases can be found on the SORT website.