ATE: Installation and configuration of ViPR SRM solution packs for 3rd party arrays and VNX Monitoring & reporting.

This discussion is now open. We look forward to your questions and to a lively interactive discussion.

Hi there,

What are the currently supported IBM arrays on ViPR SRM.

Hi Dan, thanks for taking time to visit this forum.

Following are the supported IBM models on ViPR SRM 3.5.1

IBM SVC v5.1 and above

IBM Storwize v3700, v7000 v6.4 and above

DS 3000, 4000, 5000, 6000, 8000 series

IBM XIV

Hope this helps.

Will the Physical host SP on ViPR SRM provide details on IBM SVC LUNs? I need to know what capacity is allocated to the host from IBM SVC, also is there a way to identify what LUN is mapped to a host?

Thanks in Advance.

When configuring Brocade SMI agent, SRM solution pack has to establish connection to SMI and the SMI to the switches, is that correct?

I couldn't find any document that details the procedure. Your help here would be appreciated.

You have to first add the switches on the SMI and SRM will communicate with the SMI to gather information on the switches

Please refer the following link on how to add switches on SMI

https://inside.emc.com/docs/DOC-102830

Hey Roger,

Thanks for dropping in. Currently IBM SVC SP isn't integrated with global reports. So an end to end view report for SVC volumes is not possible at current version. You can look forward to this feature in the coming major release.

Hope this helps.

Hello expert,

I have a question regarding HDS support on ViPR SRM - is it possible to see details of array virtualized behind a USPv on SRM.

Thank you for the documentation on SMI for Brocade solution pack.

I am now facing a problem while adding the SMI on SRM - I have added the SMI details on device discovery and the test retrieves some information however when proceeding to the next step following error is seen

line 20: xpath: command returned with a non-zero status (status:1)"

Hey, thanks for visiting this forum.

ViPR SRM does not provide information on a array virtualized behind a USPv, nor does it provide details of any LUN from external array encapsulated on the USPv. You may use the respective solution pack for that particular array if it is supported by SRM.

Hope this helps.

The error looks like its due to an unsupported CMCNE/ BNA. Please try to use the supported version and the switch configuration on SRM should work fine.

Following are the supported versions

CMCNE/BNA 11.1.x, 11.2.1, 12.0.x and 12.1.x.

CMDCE/DCFM 10.4.x

For all versions of CMCNE/BNA, ViPR SRM do not support Single Sign On and Launch-in- Context

Have fun

Yes, it was a problem with the version. I was on a lower version.

Could you clarify a bit on the passive discovery of hosts using the

discovered switches, I know this was possible on the Prosphere.

Below is some information on passive discovery

ENABLING PASSIVE HOST DISCOVERY THROUGH BROCADE FC SOLUTIONPACK

You have to enable passive host discovery when you want to see end to end topology from hosts to array and identify chargeback on SAN enabled hosts, without active host discovery.

You can passively resolve hosts, discovered through the SolutionPack for Brocade FC Switch, from zoning records.

The zone naming patterns supported in ViPR SRM are:

z_%h%

z_%h%_*

z_%h%_*_*

%h%_*

If you want to add a new host zone naming pattern, then you have to add the corresponding regular expression to the configuration file vhf-mds-zone-dns.xml located in /opt/APG/Collecting/Variable-Handling-Filter/brocade-fc-switch/conf directory.

ENABLING PASSIVE HOST DISCOVERY FOR CISCO MDS/NEXUS THROUGH GENERIC-SNMP

If you cannot access the active host, you cannot use active host discovery. In this case, you have to enable passive host discovery if you want to see end to end topology from hosts to array and identify chargeback on SAN enabled hosts.

To enable passive host discovery through the SolutionPack for Cisco MDS/Nexus, you need to reconfigure the Generic-SNMP independent SolutionPack block instance after selecting the Enable Passive Host Discovery checkbox.

The default zone naming patterns supported in SolutionPack for Cisco MDS/Nexus are:

z_%h%

z_%h%_*

z_%h%_*_*

%h%_*

z_%h% specifies where the host name occurs in a zone name. The wildcard character (*) indicates that any character can occur at that location in a zone name.

Only add to or modify the existing zone naming patterns if default zoning patterns do not support your zoning configurations.

To add to or modify existing zone naming patterns, add or modify the regex patterns in the VHF xml file /opt/APG/Collecting/Variable-Handling-Filter/Generic-SNMP-block-instance-name/conf/vhf-mds-zone-dns.xml.

Hi,

Does ViPR SRM support both NetApp Block and File?

Thanks Amit