InfoScale™ 9.0 Release Notes - Solaris
- Introduction and product requirements
- Changes introduced in this release
- Fixed issues
- Limitations
- Storage Foundation software limitations
- Dynamic Multi-Pathing software limitations
- InfoScale Volume Manager software limitations
- File System (VxFS) software limitations
- SmartIO software limitations
- Replication software limitations
- Cluster Server software limitations
- Limitations related to bundled agents
- Limitations related to VCS engine
- Limitations related to the VCS database agents
- Cluster Manager (Java console) limitations
- Limitations related to LLT
- Limitations related to I/O fencing
- Limitations related to bundled agents
- Storage Foundation Cluster File System High Availability software limitations
- Storage Foundation for Oracle RAC software limitations
- Storage Foundation for Databases (SFDB) tools software limitations
- Storage Foundation software limitations
- Known issues
- Issues related to installation, licensing, upgrade, and uninstallation
- Storage Foundation known issues
- Dynamic Multi-Pathing known issues
- InfoScale Volume Manager known issues
- File System (VxFS) known issues
- Dynamic Multi-Pathing known issues
- Replication known issues
- Cluster Server known issues
- Operational issues for VCS
- Issues related to the VCS engine
- Issues related to the bundled agents
- Issues related to the VCS database agents
- Issues related to the agent framework
- Issues related to Intelligent Monitoring Framework (IMF)
- Issues related to global clusters
- Issues related to the Cluster Manager (Java Console)
- LLT known issues
- I/O fencing known issues
- GAB known issues
- Operational issues for VCS
- Storage Foundation and High Availability known issues
- Storage Foundation Cluster File System High Availability known issues
- Storage Foundation for Oracle RAC known issues
- Oracle RAC known issues
- Storage Foundation Oracle RAC issues
- Storage Foundation for Databases (SFDB) tools known issues
- Issues related to installation, licensing, upgrade, and uninstallation
vxconfigd fails to start on some nodes after full InfoScale upgrade on CVR or VVR configuration (4056958)
After a full upgrade of InfoScale on an existing CVR or VVR configuration, the vxconfigd
service fails to start on some of the cluster nodes. This issue occurs on Solaris, because the required /dev/vx
folder is not created on the node.
Workaround: Perform the following tasks on the nodes where the service has failed to start.
Check the state of the
.aslapm-configured
and the.vxvm-configured
files.# ls -la /etc/vx/reconfig.d/state.d/
Remove these files, if they are present.
# cd /etc/vx/reconfig.d/state.d/
# rm -rf .vxvm-configured
# rm -rf .aslapm-configured
Reboot the node.
Set the appropriate cluster protocol version.
# vxdctl setversion 260
Verify that the cluster has been formed successfully.
# /opt/VRTS/bin/hastatus -sum
Optionally, check whether the
cvm_clus
resource in a CVM configuration has failed. This issue occurs when the protocol version is set but it has not yet reflected on the cluster. Perform the following steps sequentially to recover.Clear the FAULTED state from the resource.
# /opt/VRTS/bin/hagrp -clear cvm
Bring the CVM configuration online.
# /opt/VRTS/bin/hagrp -online cvm -any