Solaris 11.2 SRU 8 or above with VCS Asynchronous Monitoring Framework (AMF) enabled can cause VCS agent processes to be unresponsive, cause system panic or encounter AMF errors.
Article ID: 100032449
Updated On:
Cause
Starting with Solaris 11.2 SRU 8, the kernel header is modified. AMF functionality is affected by the changes in the kernel headers. VCS agent processes like Mount, Oracle, Netlistener and Process, that are enabled with AMF functionality, may hang, may panic the system due to corruption on lwp_ap, or may report errors during AMF registration.
Resolution
The AMF code has been modified to handle the changes in the kernel headers for Solaris 11.2 SRU 8 to address the issue.
For SFHA 6.2.1 Release, apply the patch:
https://sort.veritas.com/patch/detail/11211
For InfoScale 7.0.1 Release, apply the patch:
https://sort.veritas.com/patch/detail/11376
For SFHA 6.1.1 release, contact Veritas Technical Support to obtain the fix.
For SFHA 6.2.1 Release, apply the patch:
https://sort.veritas.com/patch/detail/11211
For InfoScale 7.0.1 Release, apply the patch:
https://sort.veritas.com/patch/detail/11376
For SFHA 6.1.1 release, contact Veritas Technical Support to obtain the fix.
Issue/Introduction
On Solaris 11.2 SRU 8, or above, with the Asynchronous Monitoring Framework (AMF) enabled, Veritas Cluster Server (VCS) agent processes may not respond, or may cause the system to panic, or may encounter AMF errors during registration.
Was this article helpful?
Yes
No
Powered by
