ViPR SRM 3.7 – Ensure Compliance to the EMC Support Matrix using ViPR SRM

Table of Contents

EMC Support Matrix compliance features

The EMC Support Matrix compliance policy in ViPR SRM matches your environment to the EMC Support Matrix. Breaches to this policy point out noncompliant components and unsupported combinations of components. Using the ViPR SRM breach report and support matrix match list, you can research and fix these issues.

What is the EMC Support Matrix?

The EMC Support Matrix is a database of interoperability rules for EMC arrays, supported switches and switch firmware, and hosts running UNIX, Windows, and VMWare operating systems.

The EMC Support Matrix compliance policy ensures that all components in your EMC storage network comply to EMC support standards and best practices.

The ViPR SRMSolutionPack for Storage Compliance includes exported information from the EMC Support Matrix. Each new version of the SolutionPack for Storage Compliance includes the latest information from the EMC Support Matrix database.

Which conditions are validated?

The EMC Support Matrix compliance policy validates interoperability and versioning among combinations of components, such as:

What is the match list?

For this compliance policy to work, the attributes of all components in your storage infrastructure must be matched to attribute values in the EMC Support Matrix database. The Match List is accessible from the ViPR SRM Administration portal.

The Match List uses the terms in the following table to describe how each match was derived.

This compliance policy generates the EMC Support Matrix Active Breaches report. The report lists issues and provides detailed information for researching and fixing the issues.

Unmatched and multimatched components are breaches. You can resolve match issues by performing manual matches.

When components in the storage infrastructure do not comply with the EMC Support Matrix database, the report identifies other breach types, such as interoperability and path management breaches. You can research these breaches using the information provided in the report. The E-LAB Interoperability Navigator is a useful resource for researching supported configurations and upgrade requirements.

What about RPQs?

Your site might obtain a verified EMC Request Per Qualification (RPQ) that permits alternate components in conflict with the EMC Support Matrix. In this case, you can create a customized scope and apply it to this policy so that the nonconforming but approved component does not continuously appear as a breach.

Back to Top

Enable and schedule the EMC support matrix policy

To implement the ViPR SRM EMC Support Matrix compliance policy, you must first enable the policy and edit it to set a scope, enable rules, and set a schedule.

Assume that you are an administrator for data centers in a large enterprise. You want to monitor the storage network and identify noncompliant configurations within a day. You decide to enable the EMC Support Matrix compliance policy. You want to run a new EMC Support Matrix Active Breaches report first thing each morning and again mid-day.

Procedure

  1. Log in to the ViPR SRM Console, and click Administration in the banner.
  2. In the Administration navigation tree, click Modules > Storage Compliance > Policy & Rules Management.
    A table of storage compliance policies appears.
  3. In the Name column, locate the policy named EMC Support Matrix.
  4. Click the checkbox in the first column for that row, and then click Enable.


  5. Click the checkbox again, and then click Edit.
    The Edit Policy window opens.
  6. Configure the scope for this policy:
    1. Click the Scope tab.
    2. Select the scopes that you want this policy to monitor.
      Scope selections depend on the rules that you intend to enable in the next step. Typical native scopes to associate to this policy are:
      • All Arrays
      • All Hosts
      • All ESX Servers
      • All Fabrics
      • All Virtual Machines
    3. If needed, you can create a customized scope. For example, rather than monitoring All Hosts, you might want to monitor only Linux hosts.
  7. Enable the rules that you want to implement:
    1. Click the Rules tab.
    2. In the first column, click to select each rule that you want to implement.
    3. Click Enable at the bottom of the window.


  8. To schedule automatic runs for this policy:
    1. Click the Schedule tab.
    2. Complete the form to schedule when this compliance policy should run.
      For example, the following settings run the policy at 5 AM and 2 PM each day.

  9. To save the changes on all tabs, click Save on any tab.
    The Policy & Rules Management page redisplays.

Results

On the next scheduled date and time, the policy will run and generate new breach reports.

Back to Top

Run the policy manually

You can run a compliance policy on demand, outside of its scheduled time, from the Administration portal in ViPR SRM.

Procedure

  1. Log in to the Console, and click Administration in the banner.
  2. In the Administration navigation tree, click Modules > Storage Compliance > Policy & Rules Management.
  3. Click the row for the policy named EMC Support Matrix, and then select Run Now.


  4. Verify that the Last Run column changes to Running.....
    If it does not:
    1. Click the policy again and choose Edit.
    2. On the Scope tab, make sure at least one scope is selected. See the previous task for scope suggestions.
    3. On the Rules tab, make sure at least one rule is enabled.
    4. Click Save.
    5. Rerun the policy.
  5. To view the results of the policy run:
    1. Return to the browser tab that contains the ViPR SRM interface.
    2. Click User Interface in the banner.
    3. Navigate to Operations > Compliance > Storage Compliance > Breach Report > Active Breaches by Policy > EMC Support Matrix.
Back to Top

View the EMC Support Matrix Active Breaches report

The EMC Support Matrix Active Breaches report in ViPR SRM lists noncompliance to the EMC support matrix and provides information for researching and fixing the issues.

Assume that you are a storage administrator with several data centers that recently configured new storage arrays. You want to check the latest EMC Support Matrix Active Breaches report to ensure that the new configurations are compliant.

Procedure

  1. Log into the Console.
  2. Navigate to Operations > Compliance > Storage Compliance > Breach Report > Active Breaches by Policy > EMC Support Matrix.
    The Support Matrix Active Breaches report appears.
  3. To determine when the Support Matrix policy was last run, look in the Last Modified Time column.


    Note Image
    To update the data in a compliance policy report, you must run the policy. The policy runs on its scheduled time or on-demand from the Administration portal. You can not run the policy and generate a new report from the User Interface portal.

  4. To determine which components are not in compliance, look in the Device column. To identify the role of the noncompliant device in the configuration, look in the Device Type column.
    In the following example, two hypervisors have issues.

  5. To understand and fix compliance issues, analyze the information in the Message column.
    See subsequent sections for examples.
Back to Top

Fix not matched and multi-matched devices

Discovered devices in your environment that are not matched to a support matrix value or match to multiple values cause breaches of the EMC Support Matrix compliance policy. You need to perform manual matches for all Not Matched and Multi-matched devices.

For example, the Message column in the following figure describes a host that needs to be matched. A similar message could occur in several breaches in the report. If you fix the match issue, all associated breaches will be fixed.



Example match issue in a breach report

Procedure

  1. Navigate to the EMC Support Matrix match list.
    1. Log in to the Console, and click Administration in the banner.
    2. Click Modules > Storage Compliance > Match to EMC Support Matrix.
      The match list is initially sorted to show the Not matched entries first.
  2. Use these methods to find items in the list:
    • Type a portion of the discovered value in the Search box, and press Enter.

    • To sort the report by the values in a column, click in the header of a column.
  3. (Optional) To see information about the devices associated with this unmatched value, click the number in the Devices Affected column.
    A dialog appears with known information. At the end, a table shows the affected device names. Close the dialog to continue with the matching process.
  4. To match an item, click Edit (the pencil icon) in the row.
  5. In the dialog, type a portion of the discovered value to search the EMC Support Matrix for a match .
    For example, type SUN.
    Note Image
    Although the discovered value did not result in an automatch to any value in the EMC Support Matrix, the discovered value in most cases is close to the Support Matrix entry or at least contains useful hints.

    To narrow the list, type a more specific value, such as 375.
  6. If a reasonable match appears, select it, and click OK.
    If you do not see an appropriate match value:
    • The component might not be supported, and therefore does not exist on the EMC Support Matrix list. It might be end-of-life or never supported. To resolve breaches, upgrade to a supported component.
    • The discovered value might be misleading. Perform offline research about the affected device to find a better match value.
  7. After matching some components, rerun the EMC Support Matrix policy, as follows:
    1. In the left pane (still on the EMC M&R platform interface), click Policy & Rules Management.
    2. In the list of policies in the right pane, click the EMC Support Matrix row, and select Run Now.


      The Last Run column changes to indicate that the policy is currently running.

    3. When the Last Run column displays the current date and time, click the web browser Refresh button to refresh the window.
      The refresh action updates the # of Breaches column.

Back to Top

Fix base connectivity interoperability breach

The EMC Support Matrix Active Breaches report contains all of the information you need to research a base connectivity interoperability breach in ViPR SRM.

Assume that you are a storage administrator and want to correct the interoperability breach described in the following figure.

Example base connectivity issue in a breach report

Use the following general process for researching and fixing interoperability breaches:
  1. Verify and correct the match values for each component listed in the breach message.

    The automatch feature makes the best assumption possible based on discovered values but sometimes an automatched value is incorrect. Also, manual matches can be erroneous.

  2. After fixing match values, rerun the policy to determine if the breach is fixed.
  3. If the breach still exists, use the tools in E-LAB Interoperability Navigator to research the incompatible component and obtain a list of possible compatible replacements.
  4. If your site has a negotiated EMC RPQ that covers support for the incompatible component, you can edit the policy, changing the scope to cover the component in question and prevent the breach from appearing on subsequent report runs. The process for creating a customized scope is described in another article.

To fix the base connectivity breach shown in the report above, use this procedure.

Procedure

  1. Go to the Match List:
    1. Log in to the Console, and click Administration in the banner.
    2. Click Modules > Storage Compliance > Match to EMC Support Matrix.
  2. Verify the Operating System component in the incompatibility message: Windows 2008 R2 SP1.
    1. In the search box on the upper right corner of the report, enter Windows 2008 R2, and press Enter.
      You notice that the component is not matched.
    2. Click the Edit (pencil) icon on the row.
    3. Type Windows 2008 R2 on the dialog to find all matches.
      Notice that there are no matches for SP1 or Service Pack 1, which is the version listed in the breach message. SP1 is no longer supported.

    You know you must upgrade this host to Service Pack 2 to resolve the breach. However, there might be additional interoperability problems with this configuration, so continue to verify all other components listed in the breach message.
  3. Verify the Host System component in the incompatibility message: PowerEdge 2950.
    1. In the search box on the upper right corner of the report, enter 2950, and press Enter.
      You notice that the component is matched, but you want to verify the match.
    2. Click the Edit icon on the row and type 2950 in the dialog.

      You find two possible matches.


    3. Perform offline research to determine whether the configuration for device MHMPC111 is a PowerEdge 2950 or 2950 III.
      You discover that it is a 2950 III.
    4. Select that value and then click OK.
  4. Verify the Host Bus Adapter component in the incompatibility message: LP982-E
    1. In the search box, type LP982-E.
    2. Click the Edit icon on the found row and type LP982 in the dialog.
      The entry is found and listed as End of Life.
    You now know that the Host Bus Adapter on the MHMPC111 device is out of date and must be updated to resolve this breach.
  5. Continue to verify the other components in the breach message to discover all outdated components.
  6. Perform the physical updates to bring the MHMPC111 device up to date and in compliance with the EMC Support Matrix.
Back to Top

Research path management breaches in E-LAB Interoperability Navigator

You can research a PowerPath or path management interoperability issue by using information from a ViPR SRM Support Matrix Breach report. The breach report provides information to plug into the EMC E-LAB Interoperability Navigator.

Assume that you want to fix the breach in the following figure.



Example path management issue in a breach report

Procedure

  1. In a web browser, go to the EMC E-LAB Interoperability Navigator at the following URL:
  2. Scroll to the bottom of the E-LAB Navigator page and click Advanced Queries.
  3. To create a query:
    1. In the tool on the right side of the page, create a query name, and then click Save.


    2. Use the component tree on the right to fill in the query categories on the left.
      Use the values listed in the breach message, and make selections that match the message as closely as possible.
      For our example, we do not include the multipathing software that is listed in the breach message, because we assume that it is the noncompliant component causing the breach. We want this tool to provide us with valid multipathing software for the combination of storage array and operating systems.

      The following figure shows the completed query that matches the first three components that are listed in the breach message. Note that two storage array entries are supplied, one that mentions Symmetrix and one that mentions the S/N. These choices most closely match the breach message.



    3. Click Save again.
  4. To generate results that will list valid multipathing software for this combination of array and OS:
    1. Scroll down to expose step 2.
    2. Select Path Management Software in the Configuration Name column.
    3. Click Get Results for Selected Configurations.


  5. Click the breach_example Results tab.
    Note Image
    The tab name includes the query name. Our query name is breach_example.

    The result is a table that lists valid multipathing software for the provided combination of components.

    Note Image
    If no results are reported, try eliminating other components from the list, or try using less specific component choices.

Results

In this scenario, you researched the reason behind a path management interoperability breach. The EMC E-LAB Navigator shows that the supported EMC PowerPath versions for the combination of components are:

Referring back to the breach report, you find that EMC PowerPath version 5.7 SP2 is currently installed. You need to update the software to resolve this breach.

Back to Top

View inactive (fixed) breaches

Fixed breaches are called inactive breaches in ViPR SRM. The Inactive Breaches report lists the support matrix policy breaches that were fixed during the current reporting cycle.

Procedure

  1. Navigate to Operations > Compliance > Storage Compliance > Breach Report > Compliance Reports > All Inactive Breaches.
    The report shows the four breaches that you fixed in previous scenarios in this article.

  2. Click in a row to view more details about a specific inactive breach.
    The following figure shows more details about the last inactive breach.

Results

The inactive breaches reports provide details about the breaches that were fixed in the reporting period.

Back to Top