Veritas Configuration Manager (VCM) 6.0 agent driver, emxdrv, may cause Oops message on Red Hat Enterprise Linux 4 kernel 2.6.9-34.ELsmp

Article:TECH61209  |  Created: 2008-01-25  |  Updated: 2009-01-25  |  Article URL http://www.symantec.com/docs/TECH61209
Article Type
Technical Solution


Environment

Issue



Veritas Configuration Manager (VCM) 6.0 agent driver, emxdrv, may cause Oops message on Red Hat Enterprise Linux 4 kernel 2.6.9-34.ELsmp

Solution



VCM 6.0 has a known issue in agent driver (emxdrv) that may result in Oops message on a RHEL 4 kernel 2.6.9-34.ELsmp.

The attached zip file contains the fixed driver jar: Linux_RH40_2.6.9-34.ELsmp_i686_32.jar

NOTE: If the problem occurs on a different Linux kernel, please contact Symantec Support to obtain the correct driver jar.


Steps to install the fix:
-------------------------------
1) Please remove an exiting Linux_RH40_2.6.9-34.ELsmp_i686_32.jar file from the VCM Server UI  (Admin UI -> Agent Drivers)
2) Login to the affected Linux system
3) Confirm the VCM agent is stopped (<agent_home>/6.0/bin/emx_agentd.sh stop)
4) Remove <agent_home>/6.0/drivers/Linux_RH40_2.6.9-34.ELsmp_i686_32 directory
5) Start the VCM agent (<agent_home>/6.0/bin/emx_agentd.sh start)
6) VCM agent will start up and appear as Connected in the UI with an Alert indicating the agent is in Driverless mode
7) Import the attached Linux_RH40_2.6.9-34.ELsmp_i686_32.jar file to the VCM Server UI (Admin UI -> Agent Drivers)
8) VCM Agent will poll for the new driver and the Alert will clear up after several minutes










Attachments

VCM60patch1039162_305255.zip (468 kBytes)

Supplemental Materials

SourceETrack
Value1039162
DescriptionRH4 crashes/hangs during stress test

Legacy ID



305255


Article URL http://www.symantec.com/docs/TECH61209


Terms of use for this information are found in Legal Notices