Veritas Cluster Server Release Notes
Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec Veritas⢠Cluster Server Release Notes: Linux - SORT - Symantec
Veritas Cluster Server Release Notes Known issues 38 Table 1-19 Whether attributes are configured and required actions that you need to perform during upgrade Options RouteOptions and/or IPv4AddrOptions IPv4RouteOptions Comment Actions that you need to perform during upgrade Configured May or may not be configured May or may not be configured In this case the ifconfig command is used. If RouteOptions is set, attribute value is used to add/delete routes using command route. No need to configure IPv4RouteOptions . As the Options attribute is configured, IPv4RouteOptions values are ignored. Not configured May or may not be configured Must be configured In this case the ip command is used. IPv4RouteOptions must be configured and are used to add/delete routes using the ip route command. As Options attribute is not configured, RouteOptions value is ignored. Configure IPv4RouteOptions and set the IP of default gateway. The value of this attribute typically resembles: IPv4RouteOptions = “default via gateway_ip” For example: IPv4RouteOptions = “default via 192.168.1.1”
Veritas Cluster Server Release Notes Known issues 39 Issues with keyless licensing reminders after upgrading VRTSvlic [2141446] After upgrading from 5.1 to higher versions of VCS, some keyless licenses may be left in the system. As a result, you may see periodic reminders being logged if the VOM server is not configured. This happens if you are using keyless licenses before upgrading to 5.1SP1 or higher versions of VCS. After the upgrade, you install real keys and run vxkeyless set NONE. In this case, the keyless licenses may not be completely removed and you see warning messages being logged after two months (if VOM server is not configured). 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 NONE 3. Find and delete the keyless licenses left over in the system. To do this, perform the following steps for every key stored in /etc/vx/licenses/lic: ■ ■ Verify if the key has VXKEYLESS feature Enabled using the following command: # vxlicrep -k | grep VXKEYLESS Delete the key if and only if VXKEYLESS feature is Enabled. Note: When performing the search, do not include the .vxlic extension as part of the search string. 4. Restore the previous list of products with the command: # vxkeyless set product1[|,product] SELinux error during installation of VRTSvcsag RPM During the installation of VRTSvcsag RPM on RHEL 5 SELinux enabled machine, you may observe following SELinux error: /usr/sbin/semodule: Failed on /opt/VRTSvcs/bin/selinux/vcsag.pp! This error occurs due to improper installation of the SELinux package. As a result, SELinux commands may not function properly.
- 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 9 and 10: Veritas Cluster Server Release Note
- Page 11 and 12: Veritas Cluster Server Release Note
- Page 13 and 14: Veritas Cluster Server Release Note
- Page 15 and 16: Veritas Cluster Server Release Note
- Page 17 and 18: Veritas Cluster Server Release Note
- Page 19 and 20: Veritas Cluster Server Release Note
- Page 21 and 22: Veritas Cluster Server Release Note
- Page 23 and 24: Veritas Cluster Server Release Note
- Page 25 and 26: Veritas Cluster Server Release Note
- Page 27 and 28: Veritas Cluster Server Release Note
- Page 29 and 30: Veritas Cluster Server Release Note
- Page 32 and 33: Veritas Cluster Server Release Note
- Page 34 and 35: Veritas Cluster Server Release Note
- Page 37: Veritas Cluster Server Release Note
- Page 41 and 42: Veritas Cluster Server Release Note
- Page 43 and 44: Veritas Cluster Server Release Note
- Page 45 and 46: Veritas Cluster Server Release Note
- Page 47 and 48: Veritas Cluster Server Release Note
- Page 49 and 50: Veritas Cluster Server Release Note
- Page 51 and 52: Veritas Cluster Server Release Note
- Page 53 and 54: Veritas Cluster Server Release Note
- Page 55 and 56: Veritas Cluster Server Release Note
- Page 57 and 58: Veritas Cluster Server Release Note
- Page 59 and 60: Veritas Cluster Server Release Note
- Page 61 and 62: Veritas Cluster Server Release Note
- Page 63 and 64: Veritas Cluster Server Release Note
- Page 65 and 66: Veritas Cluster Server Release Note
- Page 67 and 68: Veritas Cluster Server Release Note
- Page 69 and 70: Veritas Cluster Server Release Note
- Page 71 and 72: Veritas Cluster Server Release Note
- Page 73 and 74: Veritas Cluster Server Release Note
- Page 75 and 76: Veritas Cluster Server Release Note
- Page 77 and 78: Veritas Cluster Server Release Note
- Page 79 and 80: Veritas Cluster Server Release Note
- Page 81 and 82: Veritas Cluster Server Release Note
- Page 83 and 84: Veritas Cluster Server Release Note
- Page 85 and 86: Veritas Cluster Server Release Note
- Page 87 and 88: Veritas Cluster Server Release Note
<strong>Veritas</strong> <strong>Cluster</strong> <strong>Server</strong> <strong>Release</strong> <strong>Notes</strong><br />
Known issues<br />
39<br />
Issues with keyless licensing reminders after upgrading<br />
VRTSvlic [2141446]<br />
After upgrading from 5.1 to higher versions of VCS, some keyless licenses may be<br />
left in the system. As a result, you may see periodic reminders being logged if the<br />
VOM server is not configured.<br />
This happens if you are using keyless licenses before upgrading to 5.1SP1 or higher<br />
versions of VCS. After the upgrade, you install real keys and run vxkeyless set<br />
NONE. In this case, the keyless licenses may not be completely removed and you<br />
see warning messages being logged after two months (if VOM server is not<br />
configured). This does not result in any functionality impact.<br />
To resolve this issue, perform the following steps:<br />
1. Note down the list of products configured on the node for keyless licensing.<br />
Run vxkeyless display to display the list.<br />
2. Set the product level to NONE with the command:<br />
# vxkeyless set NONE<br />
3. Find and delete the keyless licenses left over in the system. To do this, perform<br />
the following steps for every key stored in /etc/vx/licenses/lic:<br />
■<br />
■<br />
Verify if the key has VXKEYLESS feature Enabled using the following<br />
command:<br />
# vxlicrep -k | grep VXKEYLESS<br />
Delete the key if and only if VXKEYLESS feature is Enabled.<br />
Note: When performing the search, do not include the .vxlic extension as<br />
part of the search string.<br />
4. Restore the previous list of products with the command:<br />
# vxkeyless set product1[|,product]<br />
SELinux error during installation of VRTSvcsag RPM<br />
During the installation of VRTSvcsag RPM on RHEL 5 SELinux enabled machine,<br />
you may observe following SELinux error:<br />
/usr/sbin/semodule: Failed on /opt/VRTSvcs/bin/selinux/vcsag.pp!<br />
This error occurs due to improper installation of the SELinux package. As a result,<br />
SELinux commands may not function properly.