-
Title
How to move agents from one Foglight Agent Manager to another? -
Description
The Foglight Management Server (FMS) and Foglight Agent Manager (FglAM) provides support for moving agents between FglAM clients (that connect to the same FMS).
There is no user interface for this task, but it can be invoked via an JMX-Console MBean or through a groovy script. -
Resolution
For SQL Server and Oracle database agents
Use the agent migration utility that is detailed in Knowledgebase article 158043
For FileLogMonitorAgent, UnixAgentPlus, WindowsEventLogMonitorAgent, MultiHostProcessMonitorAgent, PowerVMHMCAgent, UnixAgent, and WindowsAgent
- On the navigation panel, under Dashboards, click Administration | Agents | Status.
The Agent Status dashboard opens. - Select an agent that you want to move from the agents list, and click the move icon.
The Move selected agents to a different Agent Manager dialog box opens. - Use the group selector to select the target FglAM host from the Select Agent Manager drop-down list, and click Move.
Note: The target FglAM host must have the same lockbox as the source FglAM host.
Several Operating System (OS) and environment-specific issues, which include the following, may arise when moving an FglAM agent.The WindowsAgent stops collecting the data, if this WindowsAgent is moved from FglAM-A (an FglAM host installed with the Windows environment) to FglAM-B (an FglAM host installed with the Linux environment). See the “Access to DCOM objects and registry is denied” section in the Foglight Agent Manager Guide to resolve this issue.
When moving an FglAM agent which ASP configurations include a value of “localhost”, it is strongly recommended that you change the corresponding ASP value to the name or IP address of the local host; otherwise the unexpected result may occur.
The agent movement fails if an FglAM agent is moved from Solaris OS to Windows 2008 OS. This issue is a known issue.
After moving an FglAM agent to an FglAM host that has the invalid lockbox, this FglAm agent cannot be moved to other Foglight hosts any more. The invalid lockbox of the target FglAM host causes that the target FglAM host cannot release any FglAM agent.
Before moving an FglAM agent, you need be aware that all lockboxs should be released from the source FglAM host to the target FglAM host, in order to achieve a successful FglAM agent movement.
Using the "Move ALL agents" Method 1
Using the jmx-console (reference the attachment for screenshots and procedure).
Login with the 'foglight' user password accessing your FMS URL and port for the jmx-console:ie. http://your_FMS_hostname:port/jmx-console
Using "Move ALL agents" Method 2
Use the Script Console to invoke groovy code.
- Go to "Administration | Tooling & Diagnostics | Script Console"
- Select "Scripts" tab
- Click the green "+" icon
- Select the associated cartridge drop-down "FglAM-Adapter-Devkit"
- Copy / paste the contents of the groovy below providing the source "p1" and target "p2" FglAM hostnames.
NOTE: The FglAM hostnames are case sensitive and must be entered as indicated in your "Agent Managers" dashboard. - Click the Run button
import com.quest.glue.adapter.api.services.*; import com.quest.nitro.service.sl.*; def extensionLookup = ServiceLocatorFactory.getLocator().getExtensionContext(); def agentTransferService = extensionLookup.get(IAgentTransferService.class) agentTransferService.transferAllAgents("p1", "p2")"Move one agent" Method 1
Using the jmx-console (reference the attachment for screenshots and procedure.)
NOTE: Use procedure similar to listed the "Move All Agents" method 1 listed above but choose FglAM:name=TransferAgentHandler mbean in the JMX-Console."Move one agent" Method 2
Use the Script Console to invoke groovy code.
- Go to "Administration | Tooling & Diagnostics | Script Console"
- Select "Scripts" tab
- Click the green "+" icon
- Select the associated cartridge drop-down "FglAM-Adapter-Devkit"
- Copy / paste the contents of the groovy script below providing the agentId, target-display-name.
- Click Run
import com.quest.glue.adapter.api.services.*; import com.quest.nitro.service.sl.*; import java.util.*; def extensionLookup = ServiceLocatorFactory.getLocator().getExtensionContext(); def agentTransferService = extensionLookup.get(IAgentTransferService.class) // single agent agentTransferService.transferAgent(agentId, target-display-name, true,true,false) // list of agents List agentIds = Arrays.asList(1,2,3,4,5); agentTransferService.transferAgent(agentIds, target-display-name, true,true,false) ---
NOTE 1:
The FglAM hostnames are case sensitive and must be entered as indicated in your Agent Managers dashboard.
Choose the appropriate method.
//single agent method
//list of agents method.
NOTE 2:
Target-display-name refers to the target FglAM display name, that you see displayed within the Agent Manager dashboard. Remember to add opening double quote ( ” ) and closing double quote ( ” ) to target-display-name.
NOTE 3:
To move multiple agents, you need to change the 'Arrays.asList(1,2,3,4,5);' to the agentId for the agents you wish to move. In this example, 1,2,3,4,5 is the agentIds. You can obtain the agentId from the Script Console. API agentTransferService.transferAgent is only supported from FglAM-adapter-Devki version 6.1.2 included from FglAM 5.8.5.3.NOTE 4: To find the Agent ID refer to Knowledge base article 267419
- On the navigation panel, under Dashboards, click Administration | Agents | Status.
-
Attachments