APAR status
Closed as documentation error.
Error description
When the agent is installed in global zone, the binaries are propagated to local zones too. Also the svc service is propagated to local zones. but the masthead is not present in local zones, so the client fails to start, svc service attempts to start the agent but it fails consistently so sets itself in maintenance mode. if the customer decides to see in BES console also the local zones client, he needs to copy the mastheadin each zone, as documented in the patch management guide. but when he attempts to start the agent using svcadm enable BESClient it fails because the service is in maintenance mode if the client is started in the legacy way: /etc/init.d/besclient start it start fine, but, after the first reboot of the local zone it does not restart authomatically because the svc service is in maintenance mode.
Local fix
Basing on solaris documentation: http://docs.oracle.com/cd/E23824_01/html/821-1451/eqbrs.html paragraph: How to Restore a Service That Is in the Maintenance State the correct steps are: . correct procedure can be: 1) check the status of the service svcs -x BESClient 2) in case it is in maintenance mode, stop the besclient using the legacy method: /etc/init.d/besclient stop 3) enable again the BESClient svcadm clear BESClient 4) check if the service is in "online" mode and the client is actually started scvs -x BESClient svcs -p BESClient
Problem summary
Official BigFix 9.2 documentation has been updated. For details refer to the following link: http://www-01.ibm.com/support/knowledgecenter/SS63NW_9.2.0/com.i bm.tivoli.tem.doc_9.2/Platform/Adm/c_solaris_installation_instru cti.html
Problem conclusion
Official BigFix 9.2 documentation has been updated.
Temporary fix
Comments
APAR Information
APAR number
IV75791
Reported component name
TIV EP MGR AGEN
Reported component ID
5725C43AG
Reported release
91M
Status
CLOSED DOC
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2015-08-06
Closed date
2015-10-13
Last modified date
2015-10-13
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SSBQVS","label":"Tivoli Endpoint Manager"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"91M","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
13 October 2015