Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec Veritas Storage Foundation⢠and High ... - SORT - Symantec
44About Veritas Storage Foundation and High Availability SolutionsKnown issuesTo upgrade the CVM protocol on the CVM master node1 Find out which node is the CVM master:# vxdctl -c mode2 On the CVM master node, upgrade the CVM protocol:# vxdctl upgradeUnable to stop some SF processes (2329580)If you install and start SF, but later configure SF using installvcs601, somedrivers may not stop successfully when the installer attempts to stop and restartthe SF drivers and processes. The reason the drivers do not stop is because somedependent SF processes may be in the running state.Workaround: To re-configure the product, use the correspondinginstallproductversion command to re-configure the product. Otherwise someprocesses may fail to stop or start.For example, use installsfrac601 to re-configure SF rather than usinginstallvcs601.The vxdisksetup command fails to initialize disks in cdsdiskformat for LDOM disks greater than 1 TB (2557072)The vxdisksetup command fails to initialize disks in cdsdisk format for LDOMdisks greater than 1 TB. This issue is due to an LDOM operating system commandwhich fails when the number of partitions in the GUID partition table (GPT) labelis greater than 9. The cdsdisk format requires at least 128 partitions to becompatible with Linux systems.Workaround: There is no workaround for this issue.Verification of Oracle binaries incorrectly reports as failedduring Oracle Grid Infrastructure installationThe verification of Oracle binaries may incorrectly report as failed during theOracle Grid Infrastructure installation using the SF installer. The message iserroneously reported due to a break in passwordless SSH communication. TheSSH communication fails because execution of the root.sh script changes theowner of the operating system root directory to the grid user directory.
About Veritas Storage Foundation and High Availability SolutionsKnown issues45Issues with keyless licensing reminders after upgradingVRTSvlic [2141446]After upgrading from 5.1 to higher versions of VCS, some keyless licenses maybe left in the system. As a result, you may see periodic reminders being logged ifthe VOM server is not configured.This happens if you are using keyless licenses before upgrading to 5.1SP1 orhigher versions of VCS. After the upgrade, you install real keys and run vxkeylessset NONE. In this case, the keyless licenses may not be completely removed andyou see warning messages being logged after two months (if VOM server is notconfigured). This does not result in any functionality impact.To resolve this issue, perform the following steps:1. Note down the list of products configured on the node for keyless licensing.Run vxkeyless display to display the list.2. Set the product level to NONE with the command:# vxkeyless set NONE3. Find and delete the keyless licenses left over in the system. To do this, performthe following steps for every key stored in /etc/vx/licenses/lic:■■Verify if the key has VXKEYLESS feature Enabled using the followingcommand:# vxlicrep -k | grep VXKEYLESSDelete the key if and only if VXKEYLESS feature is Enabled.Note: When performing the search, do not include the .vxlic extension aspart of the search string.4. Restore the previous list of products with the command:# vxkeyless set product1[|,product]Instaling VRTSvlic package on Solaris system with local zonesdisplays error messages [2555312]If you try to install VRTSvlic package on a Solaris system with local zones ininstalled state, the system displays the following error messages:cp: cannot create /a/sbin/vxlicinst: Read-only file systemcp: cannot create /a/sbin/vxlicrep: Read-only file systemcp: cannot create /a/sbin/vxlictest: Read-only file system
- Page 1 and 2: Veritas Storage Foundationand High
- Page 3 and 4: Symantec Corporation350 Ellis Stree
- Page 5 and 6: ■■■■■■■Hardware infor
- Page 7 and 8: ContentsTechnical Support .........
- Page 9 and 10: Contents9Chapter 4 Upgrading to 6.0
- Page 11 and 12: Chapter1About Veritas StorageFounda
- Page 13 and 14: About Veritas Storage Foundation an
- Page 15 and 16: About Veritas Storage Foundation an
- Page 17 and 18: About Veritas Storage Foundation an
- Page 19 and 20: About Veritas Storage Foundation an
- Page 21 and 22: About Veritas Storage Foundation an
- Page 23 and 24: About Veritas Storage Foundation an
- Page 25 and 26: About Veritas Storage Foundation an
- Page 27 and 28: About Veritas Storage Foundation an
- Page 29 and 30: About Veritas Storage Foundation an
- Page 31 and 32: About Veritas Storage Foundation an
- Page 33 and 34: About Veritas Storage Foundation an
- Page 35 and 36: About Veritas Storage Foundation an
- Page 37 and 38: About Veritas Storage Foundation an
- Page 39 and 40: About Veritas Storage Foundation an
- Page 41 and 42: About Veritas Storage Foundation an
- Page 43: About Veritas Storage Foundation an
- Page 47 and 48: About Veritas Storage Foundation an
- Page 49 and 50: About Veritas Storage Foundation an
- Page 51 and 52: About Veritas Storage Foundation an
- Page 53 and 54: About Veritas Storage Foundation an
- Page 55 and 56: About Veritas Storage Foundation an
- Page 57 and 58: About Veritas Storage Foundation an
- Page 59 and 60: About Veritas Storage Foundation an
- Page 61 and 62: About Veritas Storage Foundation an
- Page 63 and 64: About Veritas Storage Foundation an
- Page 65 and 66: About Veritas Storage Foundation an
- Page 67 and 68: About Veritas Storage Foundation an
- Page 69 and 70: About Veritas Storage Foundation an
- Page 71 and 72: About Veritas Storage Foundation an
- Page 73 and 74: About Veritas Storage Foundation an
- Page 75 and 76: About Veritas Storage Foundation an
- Page 77 and 78: About Veritas Storage Foundation an
- Page 79 and 80: About Veritas Storage Foundation an
- Page 81 and 82: About Veritas Storage Foundation an
- Page 83 and 84: About Veritas Storage Foundation an
- Page 85 and 86: About Veritas Storage Foundation an
- Page 87 and 88: About Veritas Storage Foundation an
- Page 89 and 90: About Veritas Storage Foundation an
- Page 91 and 92: About Veritas Storage Foundation an
- Page 93 and 94: About Veritas Storage Foundation an
44About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issuesTo upgrade the CVM protocol on the CVM master node1 Find out which node is the CVM master:# vxdctl -c mode2 On the CVM master node, upgrade the CVM protocol:# vxdctl upgradeUnable to stop some SF processes (2329580)If you install <strong>and</strong> start SF, but later configure SF using installvcs601, somedrivers may not stop successfully when the installer attempts to stop <strong>and</strong> restartthe SF drivers <strong>and</strong> processes. The reason the drivers do not stop is because somedependent SF processes may be in the running state.Workaround: To re-configure the product, use the correspondinginstallproductversion comm<strong>and</strong> to re-configure the product. Otherwise someprocesses may fail to stop or start.For example, use installsfrac601 to re-configure SF rather than usinginstallvcs601.The vxdisksetup comm<strong>and</strong> fails to initialize disks in cdsdiskformat for LDOM disks greater than 1 TB (2557072)The vxdisksetup comm<strong>and</strong> fails to initialize disks in cdsdisk format for LDOMdisks greater than 1 TB. This issue is due to an LDOM operating system comm<strong>and</strong>which fails when the number of partitions in the GUID partition table (GPT) labelis greater than 9. The cdsdisk format requires at least 128 partitions to becompatible with Linux systems.Workaround: There is no workaround for this issue.Verification of Oracle binaries incorrectly reports as failedduring Oracle Grid Infrastructure installationThe verification of Oracle binaries may incorrectly report as failed during theOracle Grid Infrastructure installation using the SF installer. The message iserroneously reported due to a break in passwordless SSH communication. TheSSH communication fails because execution of the root.sh script changes theowner of the operating system root directory to the grid user directory.
Change language