Veritas Cluster Server Release Notes

More documents

Recommendations

Info

Veritas Cluster Server Release Notes Known issues 34 Unable to configure application when a new LSI Logic SCSI controller is added dynamically [2937623] In case of SLES operating system, it is possible that hot plug drivers do not get loaded and hence the operating system is unable to recognize the newly added SCSI controllers. Workaround: Load the drivers into the kernel before attempting to configure application or add a new SCSI controller. You can add the drivers by using the command: # modprobe acpiphp # modprobe pci_hotplug During snapshot reversal, VCS commands fail, and an unrelated error message may appear [2939177] If a virtual machine is under VCS control, and you revert to the virtual machine configuration snapshot, the VCS configuration file moves to the read- only mode. During this time, if you run a VCS command, the command fails. Also, the following unrelated error message appears in the log entries: Failed to delete the attribute key of attribute DiskPaths in the VCS configuration with error 11335 (Configuration must be ReadWrite : Use haconf -makerw) Workaround: No workaround. This message is safe to ignore. vSphere UI may not show applications and their status [2938892] The vSphere UI may show that it cannot connect to the virtual machine and may prompt for username and password of the virtual machine. Even after entering correct username and password, vSphere UI may not show the list of applications monitored by VCS. This can happen if the VOM MH configuration has authorization problems. Workaround: Restart the xprtld daemon on the virtual machine with the following commands: /etc/init.d/xprtld stop /etc/init.d/xprtld start
Veritas Cluster Server Release Notes Known issues 35 SSO configuration fails if the system name contains non-English locale characters [2910613] If you install the Symantec High Availability guest components on a system that has non-English locale characters in its name, then the SSO configuration between such a system and the Symantec High Availability Console host fails. (2910613) Workaround: Ensure that the system name does not contain any non-English locale characters. Application instances are ignored if its dependent storage is configured for other instance [2966123] Application instances are ignored if its dependent storage is already configure under VCS for other instances. The following message is logged in healthview_A.log when you try to configure a new application instance. Skipping the instance: , because the storage is already configured or an application running under VCS control. Workaround: Reconfigure all the instances that use common storage in a single run of the wizard. VMwareDisks agent may fail to start or storage discovery may fail if SELinux is running in enforcing mode [2854053] The VMwareDisks agent and discFinder binaries refer to the libvmwarevcs.so shared library. SELinux security checks prevent discFinder from loading the libvmwarevcs.so library, which requires text relocation. If SELinux is running in enforcing mode, these two executables may report the "Permission denied" error and may fail to execute. Workaround: Enter the following command and relax the security check enforcement on the Symantec libvmwarevcs.so library: # chcon -t textrel_shlib_t '/opt/VRTSvcs/lib/libvmwarevcs.so' Stale NFS file handle on the client across failover of a VCS service group containing LVMLogicalVolume resource (2016627) A VCS service group for a LVM volume group will be online automatically after a failover. However, the client applications may fail or be interrupted by stale NFS file handle error.
Page 1 and 2: Veritas Cluster Server Release Note
Page 3: Symantec Corporation 350 Ellis Stre
Page 6 and 7: Support agreement resources If you
Page 85 and 86:
Veritas Cluster Server Release Note
Page 87 and 88:
Veritas Cluster Server Release Note
show all

Veritas Cluster Server Release Notes

Create successful ePaper yourself

Delete template?

Save as template?