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

Table of Contents

EMC Support Matrix compliance features

Learn how to use the EMC Support Matrix compliance policy in ViPR SRM. Learn how to match your environment to the EMC Support Matrix, understand the breach report, and research interoperability breaches.

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 and bulk 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. 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 match breaches and use bulk match

You can fix match breaches by performing a manual match and then a bulk match in ViPR SRM.

Assume that you want to fix the match issue described in the Message column in the following figure. A similar message occurs several times in the report, and you are hoping to fix all of them with one bulk match.



Example match issue in a breach report

Procedure

  1. Navigate to the match list.
    1. Log in to the Console, and click Administration in the banner.
    2. In the Administration navigation tree, click Modules > Storage Compliance > Match to EMC Support Matrix.
      A new browser tab opens with EMC M&R platform in the banner. The page contains the following match table.

  2. To find the unmatched item in the match list:
    1. In our example breach report, (Example match issue in a breach report), the Device Type column indicates that the affected device is a hypervisor. Therefore, click the VMWare Hosts tab.


    2. Click in the header of the Configuration Item column to sort the rows in ascending order by configuration identifiers.


    3. Locate the unmatched host in the Configuration Items column.
      In our example breach report (Example match issue in a breach report), the Device column shows the IP address of the host as 172.8.188.160. We find five rows for that IP address, as the following example shows.

      Notice that the entries for the HBA Driver and HBA Firmware are labeled as Not Matched, which agrees with the message in the breach report (Example match issue in a breach report).



  3. To match the first unmatched component (HBA Driver):
    1. Click Edit (the pencil icon) on the HBA Driver line.
      The Match Value dialog appears.

    2. Refer back to the match list to obtain the discovered value, if available, as a starting point for finding elements in the support matrix.


    3. Because a discovered value was included in the HBA Driver row, it makes sense to search for that value. Type lpfc820 in the Search field.
      As you type, the search finds several matches for that value.

    4. Select a value from the list.
    5. Click Ok.
      The Bulk Matching dialog appears, which means that ViPR SRM found additional instances of the same unmatched value.

    6. Select an option to specify the scope of the match.
      • Select the first option to bulk match all found instances.
      • Select the second option to individually select which objects to update. Then select desired objects in the list.
    7. Click OK at the bottom of the Bulk Matching dialog.
      Another dialog appears that verifies the match.
    8. Click OK to verify the match.
  4. To match the second unmatched component (HBA Firmware):


    1. Click Edit (the pencil icon) on the HBA Firmware line.
      The Match Value dialog appears.
    2. Examine the match list above to obtain a value to start the search.
      On the match list, the Discovered Value for the HBA Firmware line is "Unknown." However, it makes sense to start the search using the HBA Model name indicated in the third row of the match list.
    3. On the Match Value dialog, in the Search field, type LPe12000.
      The search for LPe12000 returns firmware strings for Dell and for other hosts.

    4. Do some research offline and then select the firmware that is installed on the HBA. Then click OK.
      A second dialog verifying the match appears.
    5. Click OK.
    The Match to EMC Support Matrix list reappears indicating that the previously unmatched rows are now matched.

  5. Save the new matches in the database by clicking Save at the top of the page.


  6. Rerun the EMC Support Matrix policy.
    1. In the left pane (still on the EMC M&R platform interface), click Policy & Rules Management.
    2. Right-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.

Results

In this scenario, you resolved two breaches.

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.

Procedure

  1. Navigate to the Match List:
    1. Log in to the Console, and click Administration in the banner.
    2. In the Administration navigation tree, click Modules > Storage Compliance > Match to EMC Support Matrix.
  2. Find the rows that apply to device MHMPC111:
    1. Click the Windows Hosts tab.
    2. Click in the header of the Configuration Item column to sort the table by host values.
    3. Scroll to find the rows that apply to MHMPC111.





  3. Verify the match value for the OS Version:
    1. Place the pointer over the value in the Matched To column to display the entire string.



    2. To see what other possible values are in the EMC Support Matrix, click the Edit icon, and type the beginning of the matched value.


      You find entries for Itanium systems, but you decide that the previously matched value is correct.

    3. Click Cancel.
  4. Verify the match value for the Host Model:
    1. Click the Edit icon on the Host Model row and type the beginning of the matched value.

      You find two possible matches.


    2. Perform offline research to determine whether the MHMPC111 is a Dell 2950 or 2950 III.
      You discover that it is a 2950 III.
    3. Select Dell 2950 III, and then click OK.
    4. Click OK again on the verifying dialog.
  5. Match the HBA Model:
    1. Use information in the Match List to find a starting point for the match search.

      The HBA Model has a discovered value of Emulex Corporation LP982. The component is marked Not Matched because that discovered value did not match a value in the EMC Support Matrix. Regardless, you can use a portion of the discovered value as a starting point to search the database.

    2. Click the Edit icon on the HBA Model row and start typing LP98.
      • Match values are case-sensitive.
      • Type a partial value to see more possibilities.
      • The discovered value was LP982 but as you type you notice that the search finds several values for LP9802.



    3. Scroll to find values for the Emulex family.



    4. Assume that you perform offline research and verify that the Emulex 2GB FC HBA is correct for the HBA connected to MHMPC111. Select that string, and click OK.
    5. Click OK again on the verification dialog.

      The Match List reappears showing the changes that you just made. Notice that all components are now Manual matched.



  6. Click Save at the top of the Match List to write the changes to the database.
  7. To rerun the EMC Support Matrix compliance policy:
    1. In the left pane (still on the EMC M&R interface), click Policy & Rules Management.
    2. Right-click the EMC Support Matrix row, and select Run Now.
      The Last Run column indicates 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.

Results

In this scenario, you fixed an interoperability breach by verifying and correcting match values for each of the components listed in the message. The changes you made also corrected the related match breach, resulting in two fixed breaches.

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