Issues related to cluster server monitoring
This topic contains troubleshooting information about monitoring of cluster servers.
Issue | Resolution |
---|---|
Shares are not getting monitored | Shared are disabled by default. To enable Shares, include them in the Infrastructure Policy. |
Cluster containers are not getting created | Check the KM Configuration Status (ConfigStatus) attribute in the Cluster Monitoring (MCS_Remote) monitor types. An annotation message is displayed with the detailed description of the issue. If the issue still persists, contact BMC Support. |
Collect logs | Use Debug menu command to enable PSL trace. Set pconfig variable /MCS_Remote/Clusters/{clustername}/logginglevel to values INFO and NOLOGGING By default SEVERE is logging is enabled. Collect %patrol_home%\mcs\log\MCSCluster_PID.log |
Cluster is not getting discovered | Check the KM Configuration Status (ConfigStatus) attribute in the Cluster Monitoring (MCS_Remote) monitor types. An annotation message is displayed with the detailed description of the issue. If the issue still persists, contact BMC Support. |
PATROL McsMonitor (McsService.exe) not listed in the Control Panel Services Applet | One of the following is true:
|
MCS_Clusters application only contain two parameters No popup to select the clusters to monitor | The MCS_Clusters discovery process executes the cluster/list command to create the cluster list.
Check configuration From the MCS_Clusters application class, double-click the McsCheckConfiguration parameter. Your configuration information, such as cluster connection account and port number, is displayed in a text window. |
MCS_Cluster instances are not discovered | Turn on the application class debug for MCS_Cluster. If the debug output shows |
Create a trace session for mcsservice.exe and mcsgateway.exe | To start the PATROL MCS Monitor in trace mode:
|
The McsGwConAvailable parameter is continuously in ALARM (is McsGateway operational) | The McsGwConAvailable parameter enters a continuous alarm state if you shut down and restart/reinitialize the PATROL Agent while McsService (PATROL MCS Monitor) is running. To prevent this continuous alarm condition, whenever you shut down and restart/reinitialize the PATROL Agent, stop and restart McsService (PATROL MCS Monitor). |
Parameter values are -1 | If parameters generate a –1 value, check the PATROL Event Manager for an error message. The user account defined when loading/configuring the KM might not have connect permission to the PATROL Agent on the cluster node. Make sure your user account has the right "log on locally" permission granted on the cluster node. The ClusterStatus parameter does generate a value of –1. |
Any of the following error message is displayed:
| If there is a failover between cluster nodes, the nodes cannot access shared media via the drive letter. You will receive an error message stating
|
The following error message is displayed in the PATROL Console System Output window
| Turn on trace for the |
Comments
Log in or register to comment.