Dell Avamar

Introduction

Dell EMC Avamar enables fast, efficient backup and recovery through its integrated variable-length non-redundant technology. Avamar is optimized for fast, daily full backups of physical and virtual environments, NAS servers, enterprise applications, remote offices and desktops/laptops.

OpsRamp integrates with Dell Avamar using SSH and CLI commands.

Prerequisites

• OpsRamp Classic Gateway 10.0 and above.

• Ensure that “adapter integrations” add-on is enabled in client configuration. Once enabled you can see Dell Avamar integration under Setup > Integrations > Adapter section.

• For a non-root SSH user, you need to provide permissions to get discovery, monitoring data. Make an entry as below in “/etc/sudoers”.

{userName}  ALL=NOPASSWD:sudo /etc/init.d/avagent status,sudo avmaint cpstatus,sudo avmaint nodelist,sudo dmidecode | egrep  "Power Supply State:",sudo mccli server show-prop,sudo mccli server show-services,sudo dpnctl status unattended-startup,sudo mccli event show --unack=True | wc -l,sudo status.dpn,sudo mccli activity show --queued=true | wc -l,sudo avmaint nodelist | grep -i3 license | egrep "status=",sudo avmaint hfscheckstatus,sudo avmaint gcstatus,sudo mccli activity show,sudo mccli server show-util,sudo mccli event show

Install the integration

1. From All Clients, select a client.

2. Go to Setup > Integrations > Integrations.

3. From Available Integrations, select Adapter > Dell Avamar. The Install Dell Avamar Integration popup appears.
   Note: Ensure that Adapter addon is enabled at client and partner levels.

4. Enter the following information:
   a. Name: Name of the integration
   b. Upload Logo: Optional logo for the integration.
   c. GateWay Profiles: Select a gateway management profile to associate with the client.
   

5. Click Install. The Integration page displays the installed integration.

Configure the integration

1. In CONFIGURATION section, click + Add.

2. On Create Adapter Configuration, enter:

   • Name: Configuration name.
   • IP Address/Host Name: IP address/host name of the target.
   • Alert Configuration: Configure the alert filters, alert severity mappings, etc. based on your requirements.
   Default configuration:

       {"alertFilters":{"alertSeverity":["WARNING","ERROR"]},"alertSeverityMapping":{"ERROR":"Critical","WARNING":"Warning"}}
       

   • Notification Alerts: Select TRUE or FALSE.
     Notes:
     • By default False is selected.
     • If you select TRUE, application will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.

3. In the Credentials section, select Custom and enter the Username and Password.

4. In the Resource Types & Metrics section, select the metrics you want and configure for availability and alert conditions.

5. In the Discovery Schedule section, select Recurrence Pattern to add one of the following patterns:

   • Minutes
   • Hourly
   • Daily
   • Weekly
   • Monthly
     
     

6. In the Monitoring Schedule section, configure how frequently the monitoring action should trigger.

7. Click Save.

The configuration is saved and displayed on the page.

After saving the integration, the Dell Avamar resource is discovered and monitoring is enabled as specified by the configuration profile.

You can perform the actions manually, like Discovery, Monitoring or even Disable the configuration.

The discovered resource is displayed in the Infrastructure page under Server.

View resource metrics

To confirm Dell Avamar monitoring, review the following:

• Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
• Alerts: Alerts are generated for metrics that are configured as defined for integration.

Supported metrics

Risks, Limitations & Assumptions

• Application can handle Critical/Recovery failure alert notifications for the below two cases when user enables Notification Alerts in configuration:
  • Connectivity Exception
  • Authentication Exception
• Application will not send any duplicate/repeat failure alert notification until the already existing critical alert is recovered.
• Application cannot control monitoring pause/resume actions based on the above alerts.
• Component level threshold configuration is not possible.
• Resource level metric threshold customization and frequency setting are not possible.
• Usability issues in application configuration page while adding/editing.
• Optional configuration parameters cannot be defined.
• Application upgrade is manual process without version change.
• The availability is shown unknown for few resources even if it is enabled on the respective resource metrics. This is because of the presence of multiple native type resources under the same resource type.

References

Dell EMC Avamar MCCLI commands guide: https://dl.dell.com/content/docu91838