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
LLT, GAB, fencing services may fail to start after full upgrade or during phased upgrade using product installer (4052473)
The InfoScale product installer may fail to perform the add_drv operations during full upgrades or phased upgrades on Solaris systems. Consequently, the LLT, GAB, and fencing services may fail to load, and the following type of error messages may get logged:
Storage Foundation Cluster File System HA Startup did not complete successfully llt failed to start on punorat71-02-ldom18 gab aborted to start on punorat71-02-ldom18 vxfen aborted to start on punorat71-02-ldom18
Workaround: Run the add_drv command manually with some delay and then start the LLT, GAB, and fencing services.
Perform the following tasks to start the LLT services manually. Replace the llt string in each of these commands with gab and vxfen to perform the same sequence of tasks to start the GAB and the fencing services respectively.
Check whether the module appears in the list of currently loaded kernel modules.
# modinfo | grep llt
Identify the current state of the module.
# modinfo -c| grep llt
Sample output:
253 3 llt UNLOADED/UNINSTALLED
Identify the status of the corresponding service on the local instance.
# svcs llt
Sample output:
STATE STIME FMRI maintenance 09:35:08 svc:/system/llt:default
Disable the service on the local instance if it is not already in the disabled state.
# svcadm disable llt
Verify that the service on the local instance is disabled.
# svcs llt
Sample output:
STATE STIME FMRI disabled 09:51:58 svc:/system/llt:default
Add the corresponding device driver to the system.
# add_drv -v llt
Sample output:
exit status = 0 Driver (llt) installed.
Load the kernel module.
# modload -p drv/llt
Check whether the module appears in the list of currently loaded kernel modules.
# modinfo |grep llt
Sample output:
253 7bce6000 4d188 263 1 llt (LLT 8.0.0)
Enable the service on the local instance.
# svcadm enable system/llt
Finally, verify that the service is running:
For LLT, run lltconfig.
Sample output:
LLT is running
For GAB, run gabconfig -l.
Sample output:
GAB Driver Configuration Driver state : Configured