Configuring connections to remote Windows platforms
Foglight Log Monitor requires that a Windows® command shell connection be established to execute Windows commands on remote machines. There are two types of command shell connections that can be established to execute remote commands: WinRMCommandShell and DCOMWindowsCommandShell. You need to setup the remote machine based on the type of command shell connection you need to establish.
To execute Windows commands on a local machine, a LocalWindowsCommandShell may be used, if local user credentials are provided.
The Foglight Log Monitor command shells are described in the following sections.
Uses Windows Remote Management (WinRM) to execute remote commands. For configuration information, see section “Configuring Windows Remote Management (WinRM)” in the Foglight Agent Manager Guide.
For configuration information, see sections “Configuring Windows Management Instrumentation (WMI)” and “Configuring Registry Settings for WinShell Access through DCOM” in the Foglight Agent Manager Guide.
The Foglight for Infrastructure WindowsAgent can use the WMI mechanism to establish remote connections for monitoring Windows resources. In this case it can collect data only from specific event logs, but not all (for details, see About the WindowsAgent).
To monitor event logs within the “Applications and Services” category, you must use the LogMonitor agents (FileLogMonitorAgent or WindowsEventLogMonitorAgent).
Foglight LogMonitor copies an executable to the remote machine and runs this executable, which outputs the collected data and then Foglight Agent Manager processes it. The executable uses Windows native APIs to obtain the relevant data from the Windows Event Logs. To copy and run the executable on the remote machine, access to the Windows command prompt is required. If DCOM is used, an extra setup step is required (for details, see “Configuring Registry Settings for WinShell Access through DCOM” in the Foglight Agent Manager Guide). There are no extra setup steps required if WinRM is used.
The remote monitoring of Windows® and UNIX® hosts has unique requirements, as presented in the Foglight Agent Manager Guide. For example, the following log entry indicates that the Remote Connection failed.
com.quest.glue.api.services.RemoteConnectionException: a shell connection could not be established
Monitoring IBM PowerVM environments
Foglight™ for PowerVM allows you to monitor IBM® PowerVM® environments. Foglight alerts you about infrastructure problems when they develop, enabling you to resolve issues pro actively before end users are affected. Early intervention ensures consistent application performance at established service levels. Foglight for PowerVM monitors the health of your virtual system by tracking the levels of resource utilization such as processor, network, and memory consumption of individual objects in your integrated environment.
Before you begin
Ensure that Foglight for Infrastructure is installed on the Management Server. For installation instructions, see the Foglight for Infrastructure Release Notes.
|
• |
To monitor PowerVM® servers, you need a running instance of the PowerVM HMC Agent. This agent is provided with Foglight for Infrastructure. |
Introducing the PowerVM infrastructure
Foglight for PowerVM focuses on the following components in your monitored PowerVM® environment:
|
• |
HMC (Hardware Management Console) manages a groups of PowerVM servers that are running in your integrated environment. |
|
• |
Managed Server is a collection of physical components managed by the PowerVM Hypervisor software layer. PowerVM Hypervisor divides physical system resources into isolated logical partitions. An HMC typically includes multiple logical partitions. |
|
• |
Partition encapsulates an operating system and application components that are running in a PowerVM Hypervisor. It has a dedicated share of the system’s physical resources. |
|
• |
VIOS provides a mechanism that enables logical partitions to share physical resources of a managed PowerVM server. |