Changing SystemEDGE managed mode status
search cancel

Changing SystemEDGE managed mode status

book

Article ID: 22054

calendar_today

Updated On:

Products

CA Server Automation CA Virtual Assurance for IM

Issue/Introduction

A new feature to the SystemEDGE 5.x Agent is for it to be run in a "managed" mode. When the agent is configured to be managed, it gives control of its configuration to a specific CA Virtual Assurance for Infrastructure Managers or CA Server Automation manager system. The managed mode can be set through individual installations of the agents directly on the target machine or it can be set through a deployment feature available through CA Virtual Assurance for Infrastructure Managers r12.x and CA Server Automation r12.x

When the SystemEDGE 5.x Agent is configured to be managed, changes made to the agent's configuration locally or directly (through the sysedge.cf file for example) are overwritten by the manager. Running the SystemEDGE 5.x Agent in managed mode has benefits including: configuration enforcement and centrally managed configurations.

Please Note: Managed mode as it refers to policy/configuration is not related to the managing/unmanaging of the resource monitoring.

The agent must not have been installed in "Legacy Mode". When installing in Legacy Mode components required for running an agent in managed mode do not get installed.

How can the "managed" mode of an agent be enabled/disabled?

 

 

 

 

 

 

Environment

CA Virtual Assurance for Infrastructure Managers \ SystemEDGE

Versions: 12.8.x, 12.9

Resolution

Note: Any references to the manager hostname should all point to the desired distribution server if running more than one distribution server in the environment.

To take a SystemEDGE 5.x Agent out of managed mode, perform the following steps:

  1. Comment out or remove the manager_name [name] directive from the sysedge.cf in the following directory:

    Windows: [sysedge install dir]\config\sysedge.cf (where [sysedge install dir] is generally C:\Program Files\CA\SystemEDGE)
    UNIX/Linux: $CASYSEDGE/config/sysedge.cf

  2. Delete (or rename) the sysedge.cf file in the following directory:
    Windows 2003: %ALLUSERSPROFILE%\Application Data\CA\SystemEDGE\port[xxxx]
    Windows 2008/Windows 7: %PUBLIC%\CA\SystemEDGE\port[xxxx]
    UNIX/Linux: $CASYSEDGE/config/port[xxxx]

  3. Delete the .sysedge.id file from the same directory as noted in step 2.

  4. Restart SystemEDGE

To put a SystemEDGE 5.x Agent into managed mode, perform the following steps:

  1. Add the manager_name [name] directive to the sysedge.cf in the following directory:

    Windows: [sysedge install dir]\config\sysedge.cf (where [sysedge install dir] is generally C:\Program Files\CA\SystemEDGE)
    UNIX/Linux: $CASYSEDGE/config/sysedge.cf

  2. Delete (or rename) the sysedge.cf file in the following directory:

    Windows 2003: %ALLUSERSPROFILE%\Application Data\CA\SystemEDGE\port[xxxx]
    Windows 2008/Windows 7: %PUBLIC%\CA\SystemEDGE\port[xxxx]
    UNIX/Linux: $CASYSEDGE/config/port[xxxx]

  3. Delete the .sysedge.id file from the same directory as noted in step 2.

  4. Restart SystemEDGE

To modify the manager that a SystemEDGE 5.x Agent reports to, perform the following steps:

  1. Modify the manager_name [name] directive to the sysedge.cf in the following directory:

    Windows: [sysedge install dir]\config\sysedge.cf (where [sysedge install dir] is generally C:\Program Files\CA\SystemEDGE)
    UNIX/Linux: $CASYSEDGE/config/sysedge.cf

  2. Delete (or rename) the sysedge.cf file in the following directory:

    Windows 2003: %ALLUSERSPROFILE%\Application Data\CA\SystemEDGE\port[xxxx]
    Windows 2008/Windows 7: %PUBLIC%\CA\SystemEDGE\port[xxxx]
    UNIX/Linux: $CASYSEDGE/config/port[xxxx]

  3. Delete the .sysedge.id file from the same directory as noted in step 2.

  4. Restart SystemEDGE
Powered by Wolken Software