Risks, Limitations & Assumptions

  • Application can handle Critical/Recovery failure notifications for below two cases when user enables App Failure Notifications in configuration:
    • Connectivity Exception
    • Authentication Exception
  • Application uses the provided IP Address/hostname, Credentials for API communications.
  • Application will send any duplicate/repeat failure alert notification for every 6 hours.
  • Application cannot control monitoring pause/resume actions based on above alerts. Metrics can be used to monitor the resources and can generate alerts based on the threshold values.
  • Metrics can be used to monitor CommServer and Hyperscale StoragePool components and can generate alerts based on the threshold values. .
  • Component level thresholds can be configured on each resource level.
  • No support of showing activity logs.
  • The Template Applied Time will only be displayed if the collector profile (Classic and NextGen Gateway) is version 18.1.0 or higher.
  • This application supports both Classic Gateway and NextGen Gateway.
  • Latest snapshot metric support from Gateway 14.0.0.

Troubleshooting

Before troubleshooting, ensure all prerequisites prerequisites are met.

If Commvault Hyperscale integrations fail to discover or monitor, troubleshoot using the following steps:

  • Check if any alerts have been generation on Commserver, the gateway, or any error logs in vprobe.

  • If there is an error or alert related to the end device connectivity or authentication, try checking the reachability of the end device from the gateway with the following commands:

    • to ping the IP address provided in the configuration: {ping <IP Address>}
    • to try telnet: {telnet <IP Adress> <Port>}

  • If there are no connectivity or authentication issues, reach out to the support team for further assistance.

  • To retrieve API responses for each native type, follow these steps:

    • Select Execute Command Against Configuration, then choose the Get Target Response command. Next, select the desired native types and click Execute Command. This will return the list of APIs and their responses for the selected native types.
    • Additionally, you can use specific parameters (as listed in the table below) to fetch resource-specific API data for each native type.

    Native Type: Hyperscale Storage Pool Params: storagePoolId and nodeId

  • To collect vProbe logs from the gateway, enable the following flags to activate DEBUG-level logging in gcli terminal For Discovery:

loglevel set com.opsramp.commvaulthyperscale.app.processor.handlers.GenericMessageHandler DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.app.processor.handlers.DiscoveryHandler DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.actions.impl.discovery.DiscoveryUtil DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.domain.TargetDiscovery DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.util.BaseUtil DEBUG 60
loglevel set com.opsramp.app.content.core.publisher.AppPublisher DEBUG 60

For Monitoring:

loglevel set com.opsramp.commvaulthyperscale.app.processor.handlers.GenericMessageHandler DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.app.processor.handlers.MonitoringHandler DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.actions.impl.monitor.MonitoringUtil DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.domain.TargetMonitoring DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.domain.TargetMonitoringUtil DEBUG 60
loglevel set com.opsramp.commvaulthyperscale.gateway.app.util.BaseUtil DEBUG 60
loglevel set com.opsramp.app.content.core.alerthandler.AlertUtils DEBUG 60
loglevel set com.opsramp.app.content.core.publisher.AppPublisher DEBUG 60