User is unable to add DB2 monitoring to a Windows host.
Error when setting up DB2 instances in Foglight.
A command shell connection could not be established
* this is the most common issue *
Insufficient WMI permissions
DB2 credentials are incorrect
Ports for WMI are blocked
* this is the most common issue *
When using DCOM/WMI
DB2 agents that connect to Windows machines using the Agent Manager’s WindowsShellService need to make the following specific registry changes to allow the connection.
Two keys mainly required for Windows monitoring host. The others are for scenario when FglAMs are installed on Unix/Linux hosts and need to make WMI connections to Windows DB2 hosts
Windows relevant keys:
{72C24DD5-D70A-438B-8A42-98424B88AFB8} (Windows Script Host Shell Object)
{0D43FE01-F093-11CF-8940-00A0C9054228} (FileSystem Object)
Please refer to KB 65870 to enable WindowsShellService access on registry keys.
When using WinRM
The user can connect via WinRM instead of using DCOM and in doing so will not need to change any registry settings.
The DB2 agent does not support the short domain userid, such as corp\db2admin, this may require adding a compatible local ID into DB2.
Verify that the DB2 hostname is correct, that it can be resolved from the agent manager server, and that ports are open between the FglAM and monitored host.
Please ensure that the following ports are open bidirectionally between the FglAM and DB2 host with WMI connections
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center