How to move agents from one Foglight Agent Manager to another? (4302460)

The Foglight Management Server (FMS) and Foglight Agent Manager (FglAM) provides support for moving agents between FglAM clients (that connect to the same FMS).

For SQL Server and Oracle database agents

Use the agent migration utility that is detailed in Migrating SQL Server and Oracle database agents to a different Foglight Agent Manager (FglAM) (4289423).

For FileLogMonitorAgent, UnixAgentPlus, WindowsEventLogMonitorAgent, MultiHostProcessMonitorAgent, PowerVMHMCAgent, UnixAgent, and WindowsAgent

The Agent Status dashboard allows you to move the FglAM agents within various FglAM hosts

1. On the navigation panel, under Dashboards, go to Administration > Agents > Agent Status.
2. Select the agents to be moved from the agents list, and click the Move icon. 
3. 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; both the source and destination need to be online.

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.

Move all agents from the Script Console dashboard

From the Script Console, the transferAllAgents method can be invoked to move all agents from one FglAM to another.

1. Go to Administration > Tooling > Script Console
2. Select Scripts tab
3. Click Add
4. Select the FglAM-Adapter-Devkit cartridge from the drop-down list
   
   
5. Copy and paste the contents of the groovy script below providing the source p1 and target p2 FglAM display names.

   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")

6. Click the Run button

Notes:

• The FglAM hostnames are case sensitive and must be entered as displayed in the Agent Managers dashboard.
• Both source and destination FglAMs must be online in order to move the agents.

Move specific agents from the Script Console dashboard

From the Script Console the transferAgent method can be invoked to move specific agents to another FglAM.

1. Go to Administration > Tooling > Script Console
2. Select Scripts tab
3. Click Add
4. Select the FglAM-Adapter-Devkit cartridge from the drop-down list
5. Copy and paste the contents of the groovy script below providing the agentId and target-display-name

   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)
   

6. Click Run
7. By default the script is set to move a single agent; to move multiple agents by Id, comment out the line under // single agent and uncomment the two lines under // list of agents to provide the agentIds and target-display-name

Notes:

• The FglAM hostnames are case sensitive and must be entered as indicated in the Agent Managers dashboard.
• This method should allow moving agents even if the source FglAM is not online.
• To move multiple agents, update Arrays.asList(1,2,3,4,5) with the list of comma separated agent Ids. that need to be moved. In this example, the agent Ids. are 1,2,3,4,5.
• The target-display-name refers to the target FglAM display name as displayed within the Agent Managers dashboard. Remember to add opening double quote ( " ) and closing double quote ( " ) to target-display-name.
• To find the Agent ID refer to Getting the agentid for an agent (4229151).

Move agents using the JMX-Console

The transferAllAgents and transferAgent methods can be invoked from the JMX console.

1. Access the JMX-Console (E.g. https://foglight.yourdomain.com:port/jmx-console) and login with the "foglight" user.
2. Search and click on the link to access the FglAM:name=TransferAgentHandler MBean
3. Invoke the transferAllAgents and transferAgent methods after specifying the input parameters.

Note: Refer to the attached documents Move selected agents to another FglAM and Move all agents to another FglAM for screenshots and additional details on the procedure.