ProblemLate Breaking News ( LBN ) - Updates to the Release Notes for Veritas Cluster Server 5.1 to 5.1 Maintenance Pack 2 for VMware ESX and 5.1 Release Update 1 (RU1) for VMware ESX and cross references to product documentation
Patches and Documentation
Patches and product manuals are available at https://sort.veritas.com
For more information on how to obtain licensing keys and installation downloads refer to https://www.veritas.com/docs/000100418
Data Collector: https://sort.veritas.com/data_collectors/overview
Storage Management Community Forums, Blogs and more: http://www.veritas.com/community/business-continuity/forums
Cluster Server for VMWare ESX 5.1 Release Update 1 (RU1) on Linux
Cluster Server for VMWare ESX 5.1 Release Update 1 (RU1) on Linux is now available
5.1 MP2 P4 for VMware ESX cannot successfully migrate virtual machines when the migration is initiated through VCS
In some cases, VCS 5.1 MP2 P4 for VMware ESX cannot successfully migrate virtual machines when the migration is initiated through the VCS command hagrp -migrate. The reason for this is the migrate action fires a probe command for the resource on the target node. In this situation, if the value of MonitorHB attribute of the ESXVM resource is 1, the ESXVM agent marks the resource faulted and called clean entry point if the virtual machine does not have heartbeat at the time of firing the probe command.
The workaround is to comment out the probe line in the migrate action script and do not fire the probe command after starting migration of the virtual machine and for 1 minute after the migration is complete.
Comment out line number 41 of the "/opt/VRTSvcs/bin/ESXVM/actions/migrate" script on all nodes which issue the hares command to probe the ESXVM resource on the "tohost"/target node. The command at line number 41 in migrate action is:
$VCSHOME/bin/hares -probe $ResName -sys $tohost
After the change:
# $VCSHOME/bin/hares -probe $ResName -sys $tohost
The workaround will be included in the 5.1 MP3 release.
POINT PATCH FOR ESX AGENTS FOR VERITAS CLUSTER SERVER 5.1MP2 on ESX is now available
POINT PATCH FOR VERITAS VIRTUALIZATION MANAGER FOR VERITAS CLUSTER SERVER 5.1MP2P2 on ESX is now available
VCS versions 5.1 through 5.1 MP2 for VMware ESX are not compatible with ESX version 3.5 Update 2
Some VCS components, including GAB and LLT, cannot load in ESX 3.5 Update 2 due to a broken set of kernel ABI interfaces in this version of ESX.
The errors noticed (in the system logs or at the command prompt) are as follows:
# /etc/init.d/llt start
LLT: loading module...
ERROR: No appropriate modules found.
Error in loading module "llt". See documentation.
LLT:Error: cannot find compatible module binary
5.1 Maintenance Pack 2 Issues
VCS 5.1 to 5.1 MP2 for VMware ESX cannot take virtual machines offline on NFS datastores when the NFS server or NFS shares are inaccessible http://support.veritas.com/docs/306520
5.1 Maintenance Pack 1
5.1 Maintenance Pack 1 for VMware ESX is now available.
Incident 1115392 - The "vxlicrep" Command May Display the Wrong Version
Version 7 may be displayed instead of 5.1 if you use the "vxlicrep" command. This issue is fixed in 5.1 Maintenance Pack 1 for VMware ESX.
Here is an example:
Symantec License Manager vxlicrep utility version 3.02.18.0
Copyright (C) 1996-2006 Symantec Corporation. All rights reserved.
Creating a report on all VERITAS products installed on this system
License Key = ABCD-1234-DFGH-5678-IJKL-XY
Product Name = VERITAS Cluster Server
Serial Number = 1181
License Type = PERMANENT
OEM ID = 2006
Platform = VMWare ESX
Version = 7
Tier = Unused
Reserved = 0
Mode = VCS
Use the "had -version" command.
Veritas Cluster Server 5.1 for VMware ESX will display the values shown in this example:
# had -version
Engine Version 5.1
Join Version 5.0.00.0
Build Date Wed 15 Aug 2007 02:01:01 AM PDT