Veritas Cluster Server Release Notes

Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec Veritas™ Cluster Server Release Notes: Linux - SORT - Symantec

d1mj3xqaoh14j0.cloudfront.net
from d1mj3xqaoh14j0.cloudfront.net More from this publisher
17.08.2015 Views

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.

<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.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!