MCS was unable to populate the available file systems field for this profile type

Document ID : KB000121355
Last Modified Date : 19/11/2018
Show Technical Document Details
Issue:
You may receive an error message when you were trying to setup MCS to monitor disks/file systems, e.g.,
 
'MCS was unable to populate the available file systems field for this profile type.
verify that the appropriate remote probes and setup templates have been deployed to the monitoring host, and the remote probes are active.'
Environment:
- UIM v8.5.1
Cause:
- firewall blocking communication

In some customer environments, firewalls are so restrictive that ONLY the Primary hub (and/or the HA-Failover hub) can directly talk to robots, so in some cases where only the Primary is allowed to communicate with the robots, the robots will block direct communication attempts from the UMP robot server.  In such environments, you need to use this key/option to force the UMP's requests to go through the Primary/Failover hub to get around the firewall.
Resolution:
Enable Callback Proxy: This option allows USM to communicate with devices when firewalls are used in your environment. Some of the MCS profile types require data from probes. Selecting this option allows the mon_config_service probe to act as a proxy for all callback requests.This should allow MCS to contact the target robot.

After making this change, and if the communication is successful, the next time you try to create the <monitoring profile>, they should get a message that the robot doesn’t have the particular probe and then have an option to deploy the probe. Once MCS deploys the probe you should be able to create the profile.
 
Here are the steps to follow:
  1. In USM, select a group or a device and then click the pencil icon.
  2. Select the Edit Monitoring Profiles tab.
  3. Expand Administration in the left panel.
  4. Create a configuration profile if you do not see a profile.
  5. Hover over Configuration Service Options and click '+' to add a profile.
  6. Select the 'Configure probes immediately' option.
  7. Select the 'Enable Callback Proxy' option, if firewalls are used in your environment.
  8. The address of the primary hub appears in the 1st Callback Proxy Address and 2nd Callback Proxy Address fields.
  9. Leave the address of the primary hub as the 1st Callback Proxy Address.
  10. Enter the address of the secondary/HA failover hub mon_config_service probe that is used for failover in the 2nd Callback Proxy Address field. Enter the address using the format:
           /<domain>/<hub>/<robot_address>/mon_config_service

Note: If you do not have a failover Secondary Hub, leave the address of the primary hub in the 1st Callback Proxy Address and the 2nd Callback Proxy Address fields.

MCS Configuration Service Options in USM

This is a useful option only in cases where the UMP robot does not have access (e.g. due to firewall blocking) to the 'other' robots in the environment, but the primary hub does.  Normally, UMP tries to directly reach the robots (or use a tunnel if present.) If there is no tunnel, the UMP robot tries to set the probe configurations directly and not use the mon_config_service probe.   If a firewall prevents direct contact to the robots, then you can enable and configure the proxy callbacks which will cause the UMP to use the MCS probe (mon_config_service) to reach/talk to the robots and not try to talk to them directly.

When mon_config_service_proxy_callback is ENABLED via UMP, UMP will use the MCS probe to do its work.  When it is NOT enabled the UMP will do its work directly.  In general, this has nothing to do with secondary/HA failover node really other than the fact that the mon_config_service probe can only be deployed on a primary or HA/failover hub. That is just one scenario of how it could be configured. Essentially its a communication workaround when firewalls are blocking UMP's ability to reach target robots where MCS is trying to deploy profiles.
Additional Information:
Please also refer to the Help documentation for more information on the monitoring configuration service.

(Optional) Advanced Configuration Service Options

Enable Callback Proxy

https://docops.ca.com/ca-unified-infrastructure-management/8-5-1/en/using-ump/the-unified-service-manager-portlet/monitoring-configuration-service