White paper
Physical Host Discovery in EMC ViPR SRM 3.7
Abstract
This white paper explains the available methods for performing
physical host discovery in EMC ViPR SRM 3.7, including the
agentless, agent-based and passive mechanisms.
October 2015
Copyright © 2015 EMC Corporation. All Rights Reserved.
EMC believes the information in this publication is accurate as
of its publication date. The information is subject to change
without notice.
The information in this publication is provided “as is.” EMC
Corporation makes no representations or warranties of any kind
with respect to the information in this publication, and
specifically disclaims implied warranties of merchantability or
fitness for a particular purpose.
Use, copying, and distribution of any EMC software described in
this publication requires an applicable software license.
For the most up-to-date listing of EMC product names, see EMC
Corporation Trademarks on EMC.com.
VMware is a registered trademark of VMware, Inc. in the United
States and/or other jurisdictions. All other trademarks used
herein are the property of their respective owners.
Part Number H14602
Physical Host Discovery in EMC ViPR SRM 3.7
2
Table of Contents
Overview ................................................................................................................. 4
Audience................................................................................................................. 4
Purpose .................................................................................................................. 4
Discovery Methods .................................................................................................. 5
Agentless host discovery: SolutionPack for Physical Hosts ....................................... 5
Deployment scenarios ........................................................................................................ 6
Considerations for host discovery (Windows and UNIX) ...................................................... 6
Considerations for hostname and IP address ................................................................. 6
Considerations for SNIA libraries and HBA drivers .......................................................... 6
Windows Host configuration for discovery and data collection ........................................... 7
Prerequisites for Windows Discovery .............................................................................. 7
Specific software needed on host................................................................................... 7
Using Host Configuration script ...................................................................................... 8
UNIX Host configuration for discovery and data collection ................................................ 10
Prerequisites for UNIX Discovery................................................................................... 10
SSH key based authentication...................................................................................... 11
Troubleshooting Agentless Host Discovery ....................................................................... 11
Windows host discovery troubleshooting ..................................................................... 11
UNIX host discovery troubleshooting ............................................................................ 13
Agent based Host Discovery : EMC Host Interface ................................................... 16
Passive Host Discovery .......................................................................................... 17
Enable passive host discovery.......................................................................................... 17
Troubleshooting Passive Host Discovery........................................................................... 18
Verify passive hosts from the collection logs ................................................................ 18
Verifying passive hosts from the RDF/topology store .................................................... 18
Verifying that LUNs from an array are being mapped to host ......................................... 19
Upgrade considerations ............................................................................................... 19
Frequently Asked Questions .................................................................................. 19
Q: Can VIPR SRM provide IOPS and response time on the host level without any
customization? ................................................................................................................. 19
Q: Are there guidelines on how to obtain and install agents such as INQ on hosts? .......... 19
Q: How do I enforce the physical collector to use INQ for storage data collection? ............ 21
Q: If INQ is placed in a different location, how do I add it to SolutionPack for Physical
Hosts? .............................................................................................................................. 21
Q: For Physical Hosts discovery, what are the least privileges that I need for Windows
systems? .......................................................................................................................... 24
Physical Host Discovery in EMC ViPR SRM 3.7
3
Overview
Host discovery is a primary use case for EMC ViPR SRM reporting, providing valuable
information about the relationship of hosts to storage systems and their components,
including file system capacity, volume groups, and disks. ViPR SRM supports multiple
methods for performing physical host discovery, which are detailed in this article.
Audience
This article is intended for EMC employees, partners, and customers including storage
administrators who want to understand the available methods of host discovery in
ViPR SRM 3.7.
Purpose
This article is intended to provide information to help you weigh the benefits of each of the
available host discovery methods in ViPR SRM, including how to set up hosts for discovery
through ViPR SRM and troubleshooting host discovery issues which may occur through
agentless discovery.
Refer to the SolutionPack for Physical Hosts in the EMC ViPR SRM SolutionPack Installation
Guide for the latest supported versions of software.
Physical Host Discovery in EMC ViPR SRM 3.7
4
Discovery Methods
VIPR SRM supports three methods for physical host discovery. Supporting a broad set
of discovery capabilities ensures that heterogeneity in customer data centers is
addressed.
•
Agentless mechanism using the SolutionPack for Physical Hosts
•
Agent based mechanism using the SolutionPack for EMC Host Interface
•
Passive host discovery using the SolutionPack for Brocade FC Switch and the
SolutionPack for Cisco MDS/Nexus switches.
The following table summarizes the operating systems and SolutionPacks that apply
to each discovery mechanism.
Discovery Mechanism
OS
SolutionPack
Agentless
Windows/UNIX
SolutionPack for Physical Hosts
Agent Based
Windows
SolutionPack for EMC Host Interface
Passive Host Discovery
All
Solution pack for Brocade/Cisco/HDS
Agentless host discovery: SolutionPack for Physical Hosts
The ViPR SRM SolutionPack for Physical Hosts is an agentless solution designed to
smartly utilize standard protocols and native commands running on operating
systems to collect all possible information about the host and generate reports
quickly for you to analyze and monitor your datacenter. The SolutionPack for Physical
Hosts can report information about the host performance, host capacity, host
connectivity and path details along with the basic host information/inventory.
Preparing host discovery requires understanding of the environment and selecting the
right discovery method. Agentless host discovery requires upfront configuration of
hosts. VIPR SRM should be able to collect data from hosts with varying configuration
parameters:
•
Operating system variants (Windows/UNIX) installed on servers.
•
Authentication types: Password/password-less
•
User privileges: host admin/non-admin or root/non-root users, public/private
keys
•
Types of communication protocols: http/https/SSH/SOAP
•
HBA vendors such as Emulex/QLogic etc.
Physical Host Discovery in EMC ViPR SRM 3.7
5
Use the checklist below to prepare hosts and VIPR SRM for discovery:
Windows Hosts
UNIX Hosts
❑
Install the pre-requisite software required on hosts
(PowerShell 2.0)
❑
Determine type of method for discovery:
Password based / Key based
❑
For Windows 2003, additional software needs to be
installed on target Windows hosts
❑
Prepare Hosts for powerbroker,
sudo/public keys
❑
Configure hosts for WinRM Settings
❑
Manage credentials for hosts and
configure VIPR SRM Generic-RSC collector
❑
o
Use host configuration tool
o
Use Group Policy
Manage credentials for hosts and configure VIPR
SRM Generic-RSC collector
Deployment scenarios
VIPR SRM supports the capability to discover Windows and Linux hosts from a vApp
or from a Windows binary installer. A user can discover Windows/UNIX hosts from a
Linux Collector VM or a Windows Collector VM, provided Physical Host Solution Pack
is installed on those Collector VMs. Physical Host SP comes packaged with scripts
(perl scripts for UNIX discovery and powershell script for Windows Host discovery)
and gets deployed under Generic-RSC instance which gets deployed with base ViPR
SRM OVF.
Considerations for host discovery (Windows and UNIX)
Considerations for hostname and IP address
Follow these guidelines to ensure a successful host discovery and data collection by
SolutionPack for Physical Hosts. Ensure that:
•
The host names are in Domain Name Server (DNS) format with fully qualified
domain name (FQDN).
•
IP addresses are registered with the appropriate domain name servers and
resolved for reverse DNS lookup.
Considerations for SNIA libraries and HBA drivers
In order to discover SNIA-qualified HBA-related information for all the host platforms
you should ensure the right versions of SNIA library, drivers and firmware are in place.
•
Ensure EMC-supported host bus adapter (HBA) drivers and firmware are
installed on hosts.
•
EMC Storage Resource Management Suite Support Matrix provides information
for the supported SNIA compliant version of the HBA driver.
•
The vendor-specific SNIA libraries must be installed on the target host.
Physical Host Discovery in EMC ViPR SRM 3.7
6
•
The HBA model number and part number should be verified before updating
the hosts with SNIA libraries for HBA.
•
You can install the SNIA library as part of HBA driver installation package or
install the latest version of HBAnywhere (for Emulex installations) or SAN
Surfer (for Qlogic installation).
•
To discover an HP-UX host with a multi-port Fibre Channel card, the package
CommonIO bundle 0812(Dec 2008) or later should be present on the host to
obtain the updated FC-SNIA file set.

ELAB interoperability matrix - You can verify the HBA models and driver
versions qualified by EMC with the information provided at
http://elabnavigator.emc.com.

You can also browse on the vendor sites for EMC compliant drivers https://elabnavigator.emc.com/eln/components
Windows Host configuration for discovery and data collection
Prerequisites for Windows Discovery
The host should have Powershell 2.0 or later installed. Powershell can be
downloaded from http://support.microsoft.com/kb/968929/en-us.
Powershell execution policy should be set to RemoteSigned using the following
command on the PowerShell prompt:
Set-ExecutionPolicy RemoteSigned
Specific software needed on host
For Windows 2003:
•
Install the latest version of Fcinfo software, which is required to fetch HBA and
Host device information. You can download fcinfo.exe from:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17
530
•
For 64-bit OS platforms, INQ 8.1.0.4 needs to be made available on the host
(starting with ViPR SRM 3.6). For 32-bit OS platforms, INQ 7.6.2 needs to be
manually copied to the target hosts. This is required to fetch SAN/Local disk
information. Platform specific INQ can be downloaded from:
ftp://ftp.emc.com/pub/symm3000/inquiry/ The downloaded platformspecific binary should be renamed to inq and placed in any one of the
following locations:
o
C:\inq.exe
o
C:\temp\inq.exe
o
C:\windows\Temp\nl_dwd\inq.exe
Physical Host Discovery in EMC ViPR SRM 3.7
7
Configurations to be done on the host
The SolutionPack for Physical Hosts uses a WinRM listener to connect and collect
data for the host.
One of the following listeners must be configured:
•
WinRM HTTP listener with the following configuration:
o Negotiate authentication mode should be true.
o Firewall exception to be added for port 5985 [default].
•
WinRM HTTPS listener with following configuration:
o Negotiate authentication mode should be true.
o A certificate needs to be generated and placed in personal store. For
details on how to generate a certificate, refer to the SolutionPack for
Physical Hosts installation documentation, which is available on the
ViPR SRM Documentation Index in the EMC ViPR SRM 3.7 SolutionPack
Installation Guide.
o Firewall exception to be added for port 5986 [default].
These changes can be accomplished via two methods:
1. Host Configuration utility - To be run on each host.
2. Group policy configuration - To be run on domain server.
Using Host Configuration script
The host configuration utility is packaged along with SolutionPack for Physical Hosts.
It is available in:
<APG home directory>/Collecting/Stream-Collector/GenericRSC/conf/scripts/windows/
The script performs the following actions:
•
Ensures that the WINRM service is running
•
Creates a listener port for accepting WS-MAN requests
•
Adds firewall exceptions to open port 5985 as non-SSL and 5986 as SSL
•
Sets Negotiate authentication mode, whichever is given as argument
•
Sets (-authType <Authentication_type>), to true
•
Sets MaxTimeout value
•
If Windows 2003, checks whether fcinfo package is present on the host
•
If Windows 2003, verifies the presence of INQ on the host and checks its
version
The following are details on each step that is performed:
Physical Host Discovery in EMC ViPR SRM 3.7
8
1. WinRM service should be running on hosts. This is the basic step to be verified
on all hosts. By default, the service will be disabled on Windows 2003 hosts.
On Windows 2008 and 2012 hosts, it will be enabled by default. Users can
start the service on Windows hosts:
2. A listener port should be created on the Windows hosts to accept requests
from clients. The host configuration script will run a command: winrm –
quickconfig, to enable listeners.
http://msdn.microsoft.com/en-us/library/aa384372%28v=vs.85%29.aspx
3. The WinRM firewall ports are established for https and http based
communication. WinRM 2.0: The default HTTP port is 5985, and default HTTPS
port is 5986
4. Set Authentication type: By default, the Negotiate type of authentication is
recommended, which is set to true.
Install certificates to encrypt traffic between ViPR SRM collectors and Windows
hosts. For secure communication, the data transport should be made secure
where SOAP packets would need to be encrypted with certificates.
5. Set MaxTimeout value on hosts. By default, a timeout of 1 minute is enabled
on WinRM server setting on hosts. The host configuration script can be used to
set a timeout of 5 minutes.
Physical Host Discovery in EMC ViPR SRM 3.7
9
6. For Windows 2003 hosts only, the host configuration script checks whether
fcinfo package is present on hosts. The pre-requisites section in this document
explains the link where Microsoft utility can be downloaded.
7. For Windows 2003 hosts only, WinRM capabilities are limited by the features
supported by HBA vendors. Observed behavior indicates that WMI provider
capabilities on certain HBA drivers do not have full-fledged support for
reporting of LUN details. Therefore, INQ must be placed on Windows 2003
hosts in specific locations so that SRM can execute the tool (INQ) and obtain
LUN details mapped on hosts.
Usage syntax
./hostconfig-srm.ps1 <-verify | -set | -set -force> [-authType
<authentication_type>] [-ssl [-thumbprint <thumbprint_value>]
[-CN <certificate_hostname>]] [-user <username>][-help]
The table below describes options available for the hostconfig.ps1 command.
Command Options
Meaning
-help
Displays the help menu of the script.
-verify
Verifies current settings on the Windows host.
-set
Configures settings on the Windows host.
-force
Changes configuration settings without prompting the user.
The -force option must be used with the -set option.
-authType
Provide this option to set the authentication type for WS-MAN
to Negotiate.
authentication-type
-ssl
Configures and verifies the SSL certificate specific settings on
the host for WS-MAN discovery with SSL.
-thumbprint
Configures the SSL certificate with the specified
thumbprint_value on the host. This option can be used only
with the -ssl option and the -set option.
thumbprint_value
-certhostname
certificate_hostname
-user
username
Configures the SSL certificate with the specified
certificate_hostname value on the host. This option can be
used only with the -ssl option and the -set option.
Configures the host to enable discovery using the domain /
non-admin username provided
UNIX Host configuration for discovery and data collection
Prerequisites for UNIX Discovery
UNIX hosts can be discovered using 2 methods:
•
Password based
•
SSH public/private key based
Physical Host Discovery in EMC ViPR SRM 3.7
10
To discover a UNIX host, some configurations are needed because data collection
requires root privileges to execute commands on the host.
For configuration procedures for each discovery method, refer to the “SolutionPack
for Physical Hosts” section of the EMC ViPR SRM 3.7 SolutionPack Installation Guide
which is available on the ViPR SRM Documentation Index.
SSH key based authentication
SSH key based authentication is required when you prefer a secure mechanism to
discover hosts from ViPR SRM. Instead of using passwords, keys should be
configured on ViPR SRM collector and UNIX hosts for a successful handshake based
authentication.
While using the SSH key based authentication to discover UNIX hosts, you can
choose any key generation tool to generate a valid public and private key pair (for
example ssh-keygen).
You could create SSH keys in any UNIX environments and import them into the ViPR
SRM collector. EMC recommends public-private SSH keys to be created on ViPR SRM
collectors (Linux VMs) where host discovery will be initiated.
You must have a public key present on all the UNIX hosts that are to be discovered.
The private key should be copied on the ViPR SRM collector discovering the specific
host.
The steps to generate a public and private key pair for UNIX host using the ssh-keygen
tool is explained in the SolutionPack for Physical Hosts Summary Sheet.
Troubleshooting Agentless Host Discovery
This section describes some troubleshooting methods you can use when configuring
Windows or UNIX agentless host discovery.
Windows host discovery troubleshooting
Debugging authentication failures
From the VIPR SRM user interface, navigate to Administration-> Discovery Center->
Host Configuration.
If the host is already added for discovery, click on the instance and check if the
credentials are keyed-in right. If so, click the Test button to troubleshoot any
authentication/authorization problems.
Performing a configuration check
Ensure that the host configuration utility runs successfully to troubleshoot any
environment problems on the host. Also, make sure the host OS is supported in VIPR
SRM.
Physical Host Discovery in EMC ViPR SRM 3.7
11
Using logs
Initially, you should review the Generic-RSC collecting-0-0.log in the logs folder.
Further debugging requires the support mode logs:
1. Enable support mode in the LunMappingDetection.ps1 script on the host.
$supportOption="enabled"
2. Run the command for support mode (to be run on the host in question).
powershell.exe -noprofile -file LunMappingDetection.ps1 > test.log
Run the support mode using the user that was used for discovery.
SNIA Library check
To verify if SNIA library is correctly installed:
•
If the HBA is an Emulex model, check whether HBAAnyware or ocmanager is
installed.
•
If the HBA is a Qlogic model, check whether SAN surfer software is installed.
To gather HBA information:
1. Run wbemtest tool.
2. Connect to root/cimv2 and run the query:
select Name from Win32_SCSIController where ProtocolSupported=10 or
Manufacturer='EMC Corporation' or Manufacturer='Emulex' or
Manufacturer='QLogic'
3. Double click on the rows returned by query, click on show MOF, note down the
HBA Make and Model.
Alternatively, you can verify the HBAs are installed by doing the following:
1. Right-click My Computer.
2. Select Manage from the Server Manager window.
3. Expand the Diagnostics tab.
4. Click on Device Manager.
5. Expand Storage Controllers within Device Manager and note the HBA Make
and Model.
Installing or modifying Emulex drivers
If you are running the OneCommand/Hbanyware Vision application, you must stop
the Services before installing the OneCommand Manager application.
To stop the services:
1. Select Start > Programs > Administrative Tools > Services.
2. Stop the EmulexSensor service.
Physical Host Discovery in EMC ViPR SRM 3.7
12
3. Stop the EmulexWMIAgent service.
4. Stop the Emulex PDH agent service.
5. Stop the EmulexScope agent service.
6. Install the OneCommand Manager/Hbanyware application.
To restart the sensor after the installation is complete:
1. Stop SNMP service in case of SNMPv2c [Stop Net-SNMP Agent in case of
SNMPv3].
2. Start SNMP service in case of SNMPv2c [Start Net-SNMP Agent in case of
SNMPv3].
3. Start the EmulexSensor service.
Installing or modifying QLogic drivers
Use the procedure in the ReadMe provided with the downloaded package.
UNIX host discovery troubleshooting
Environment check – sudo configurations
Ensure the host OS is supported in VIPR SRM and the sudoers file configurations are
correct.
Using logs
Initially, you should review the Generic-RSC collecting-0-0.log in the logs folder.
For further debugging, we need the support mode logs. Command for support mode
logs (to be run on host in question):
./LunMappingDetection.pl support=test_log
SNIA Library check
To verify if SNIA library is correctly installed:
Check the contents of hba.conf
Example:
more /etc/hba.conf
qla2xxx /usr/lib/libqlsdm.so
qla2xxx64 /usr/lib64/libqlsdm.so
Extra information to verify in 64 bit machines is to look for the presence of
libHBAAPI.so
Example:
ls /usr/lib64/libHBAAPI.so
Example:
Physical Host Discovery in EMC ViPR SRM 3.7
13
linbgm103:/lib # more /etc/hba.conf
com.emulex.emulexapilibrary /usr/lib64/libemulexhbaapi.so
com.emulex.emulexapilibrary /usr/lib/libemulexhbaapi.so
Another way to verify Emulex HBA Related softwares are installed is to check whether
/usr/sbin/hbanyware or /usr/sbin ocmanager is present or not.
Gathering information about AIX HBAs
1. Verify HBA instances are installed.
/usr/sbin/lsdev -Cc adapter
2. Verify HBA Model
lscfg –vl fcs
Gathering information about HP-UX HBAs
1. Look for the HBA instances installed in the host, the following command looks
for both types of HP drivers, fcd and td.
ls /dev | egrep “fcd|td”
or
/usr/sbin/ioscan -knfC fc
2. Gather vital product data about each HBA instance such as the part number
and model. The hba type and number should be replaced with #
/opt/fcms/bin/fcmsutil /dev/<fcd#/td#> vpd
3. Gather useful data about each HBA instance such as WWN.
/opt/fcms/bin/fcmsutil /dev/<fcd#/td#>
Gathering information about Solaris HBAs
Show HBA model and firmware level for all the instances.
fcinfo hba-port
Gathering information about Linux HBAs
1. Verify the HBA instances are installed.
lspci | grep "Fibre Channel"
2. Verify HBA model
dmesg | grep scsi
Installing or modifying Emulex HBA drivers on Linux
The following must be installed before you can install the utilities.
•
The appropriate driver for your operating system:
Physical Host Discovery in EMC ViPR SRM 3.7
14
o Linux driver version 8.2.0.33.3p or later (For RHEL5 and SLES10
operating systems.)
o Linux driver version 8.2.8.x or later (For SLES11 operating systems.)
o Linux driver version 8.3.5.X or later (For RHEL 6 SLES 11 SP1 operation
systems.)
•
Previous versions of the Linux driver must be uninstalled. You must run the
uninstall script that shipped with the version of the Linux driver you want to
remove.
To install the OneCommand Manager application in Linux:
1. Log on as ‘root’.
2. Download the utilities from the Emulex Web site or copy them to the system
from the installation CD.
3. Copy the installation and uninstallation scripts to a known location, for easy
access by other users.
4. Copy the OneCommand elxocm-<Platform>-<AppsRev>.tgz file to a directory on
the install machine.
5. Change (use cd command) to the directory to which you copied the tar file.
6. Untar the file.
•
•
For RHEL 5 and RHEL 6 type: tar zxvf elxocm-rhel5-rhel6-<apps_ver>-
<rel>.tgz
For SLES 10 and SLES 11 type: tar zxvf elxocm-sles10-sles11-
<apps_ver>-<rel>.tgz
7. Change (use cd command) to the elxocm directory created in step 6.
•
For RHEL 5 and RHEL 6 type: cd elxocm-rhel5-rhel6-<apps_ver>-<rel>
8. Run the install script.
Installing or modifying Emulex HBA drivers on UNIX
The following must be installed before you can install the utilities:
•
The Solaris FC/FCoE driver version 2.50 or later
•
The NIC driver version 1.10 or later for NIC capability
To install the OneCommand Manager application in Solaris:
1. Copy the Solaris utility kit to a temporary directory on your system.
2. Untar the utility kit:
tar xvf elxocm-solaris-<version>.tar
3. Change to the newly created elxocm-solaris-<version> directory:
cd ./elxocm-solaris-<version>/
Physical Host Discovery in EMC ViPR SRM 3.7
15
4. Execute the install script to begin installation. If the HBAnyware utility,
OneCommand Manager Core or OneCommand Manager Enterprise
applications or the Solaris driver utilities are already present on the system,
the install script attempts to remove them first: ./install
5. When prompted, enter the type of management you want to use:
•
1 Local Mode : HBA's on this Platform can be managed by
OneCommand clients on this Platform Only.
•
2 Managed Mode: HBA's on this Platform can be managed by local or
remote OneCommand clients.
•
3 Remote Mode : Same as '2' plus OneCommand clients on this
Platform can manage local and remote HBA'
Installing or modifying QLogic HBA drivers on UNIX/LINUX
The SNIA API library package (example: qlapi-<api_version>-rel.tgz) is included in the
driver combo package (example:qla2x00- vx.yy.zz-dist.tgz) or (qla2x00-vx.yy.zz-fodist.tgz).
Using the files you downloaded from Qlogic website . copy the tgz file
(example:qla2xxx-vx.yy.zz-dist.tgz) distribution file to /qla2x00.
The example below shows how the above package is installed. Follow these steps
from the / (root) directory:
1. mkdir qla2x00
2. cd qla2x00*
3. mount /mnt/floppy
4. cp /mnt/floppy/*.tgz . (the period at the end is required)
5. tar -xvzf *.tgz
6. cd qlogic
To install and set up the API library, enter the following command in ./libinstall. This
installs/sets up HBA API library.
Agent based Host Discovery : EMC Host Interface
EMC Host interface (EHI) provides a very simple option for customers to discover their
host environments. The EHI installer will deploy and SMI compliant provider on hosts,
which will collect data required for VIPR SRM. The one step deployment process
should be simple for customers to deploy using standard installation procedures
followed in a data center.
Refer to the “SolutionPack for EMC Host Interface” section of the EMC ViPR SRM 3.7
SolutionPack Installation Guide which is available on the ViPR SRM Documentation
Index.
Physical Host Discovery in EMC ViPR SRM 3.7
16
VIPR SRM currently supports EHI on Windows platforms only.
Passive Host Discovery
Passive host discovery is a capability where hosts are intelligently guessed from SAN
zoning records. SAN zoning discovery will yield hostnames, IP address and HBA port
WWN values from zoning records. Customers are generally recommended to discover
hosts primarily using passive discovery, to recognize their SAN attached hosts. Once
hosts are resolved, storage administrators could obtain additional credentials from
server admins to completely discover hosts.
Passive discovery through Brocade and Cisco SolutionPacks is disabled by default.
Enable passive host discovery
You can enable passive host discovery while installing the SolutionPack, or by
reconfiguring the SolutionPack
In the case of the SolutionPack for Brocade FC Switch, SMI Data Collection block should be
reconfigured.
In the case of SolutionPack for Cisco MDS/Nexus, edit the Generic-SNMP independent
SolutionPackBlock instance
After you have enabled passive host discovery, there are two options for passive host
configuration.
Enable DNS Resolution: This option is enabled by default. In this option, ViPR SRM resolves
the IP address by using the DNS lookup handler. You can un-check this option to avoid
using the DNS lookup feature.
Customize zone naming patterns: This option allows you to customize the zone naming
pattern. By default, this option is disabled. ViPR SRM uses the four default zone naming
patterns. You can enable this option to add, delete, or modify the default zone naming
patterns and host positions in zones. The default zone naming patterns in ViPR SRM are:
• z_%h%
• z_%h%_*
• z_%h%_*_*
• %h%_*
To enable and edit customized zone naming patterns:
1. Select the Enable Passive Host Discovery checkbox.
2. Select the Customized zone naming patterns checkbox.
The system displays the four default zone naming templates.
Physical Host Discovery in EMC ViPR SRM 3.7
17
3. Click the Add button (plus icon) to view the zone naming pattern and host position for a
template. Edit the pattern or position if desired. Only Java-based zone naming patterns
are supported. Only plain numbers can be used for the position. Special characters (like
$) are not required.
The following table provides sample zone naming patterns:
Troubleshooting Passive Host Discovery
Verify passive hosts from the collection logs
Enable the file connector in the corresponding Brocade or Cisco SolutionPack
Review the collection information in file-connector.log, and look for PassiveHost as
the devtype in the collection details. For example:
1421139292: group::Brocade-Collectorz_losan239_110000000C93995CF1000000533E94F010000AFFF00000008({isremote=true, partsn=0000AFFF00000008, part=10000000C93995CF,
ip=10.247.22.239, zmemid=10000000C93995CF, source=Brocade-Collector, w4ncert=1.0,
hasDevice=Yes, parttype=Disk, zname=z_losan239_1, devtype=PassiveHost,
hostname=losan239, vendrcode=0000C9, name=ZoneMemIdentifier, actdisc=0,
hostwwn=10000000C93995CF, device=losan239, datagrp=BROCADE_ZONEMEMBER})=0.0
Verifying passive hosts from the RDF/topology store
If you have Sesame windows client, execute the following query:
PREFIX SRM: <http://ontologies.emc.com/2013/08/SRM#>
SELECT ?s ?p ?o
WHERE {
?s a SRM:PassiveHost .
?s ?p ?o
} LIMIT 1000
Physical Host Discovery in EMC ViPR SRM 3.7
18
Verifying that LUNs from an array are being mapped to host
The partsn value (with LUNWWNS) is retrieved using a sparql query on the Topology
RDF store. When searching for this value in VIPR SRM, note that both the passivelydiscovered host and the connected array both need to have been discovered. For
example:
1421139292: group::BrocadeCollectorz_losan239_110000000C93995CF1000000533E94F010000AFFF00000008({isremote=true, partsn=0000AFFF00000008,
part=10000000C93995CF, ip=10.247.22.239, zmemid=10000000C93995CF,
source=Brocade-Collector, w4ncert=1.0, hasDevice=Yes, parttype=Disk,
zname=z_losan239_1, devtype=PassiveHost, hostname=losan239, vendrcode=0000C9,
name=ZoneMemIdentifier, actdisc=0, hostwwn=10000000C93995CF, device=losan239,
datagrp=BROCADE_ZONEMEMBER})=0.0
Upgrade considerations
If ViPR SRM was updated from earlier versions such as 3.0 to 3.5 or any higher versions, ensure
the front end reports are also updated along with the collectors. This is necessary as the
changes to support passive discovery is both on the collector and reports.
Frequently Asked Questions
Q: Can VIPR SRM provide IOPS and response time on the host level without any
customization?
A: Total Throughput and Total IOPS can be viewed on global reports as well as when you drill
down under reports from the SolutionPack for Physical Hosts. Examples:
All > Explore > Hosts > hostname
All > Report Library > Physical Hosts > Host Information > hostname > Disks Performance
where hostname is the instance of the host.
Q: Are there guidelines on how to obtain and install agents such as INQ on
hosts?
A: The “Push INQ” check box should be enabled on generic-rsc block. This will allow
VIPR SRM to push files directly to a host.
Note: ViPR SRM does not support push of INQ on Windows host. A user/admin should
place it on Windows folders.
Default locations for INQ on Windows hosts:
$inqPath="c:\inq.exe", "C:\temp\inq.exe" , "C:\WINDOWS\Temp\nl_dwd\inq.exe"
INQ is installed along with SolutionPack for Physical Hosts on UNIX variants. To verify
if INQ archive is installed correctly, see files listed below (Linux collector example) on
Physical Host Discovery in EMC ViPR SRM 3.7
19
Generic-RSC collector instance (Generic-RSC is the instance name you have provided
in your deployment.
#/opt/APG/Collecting/Stream-Collector/Generic-RSC/conf/scripts/ # ls –lR
.:
total 0
drwxr-xr-x 2 apg apg 120 Feb 25 02:45 aix
drwxr-xr-x 2 apg apg 120 Feb 18 11:35 hpux
drwxr-xr-x 2 apg apg 144 Feb 18 11:37 linux
drwxr-xr-x 2 apg apg 120 Feb 18 11:35 solaris
drwxr-xr-x 2 apg apg 96 Feb 18 11:35 windows
./aix:
total 9964
-rwxr-xr-x
-rwxr-xr-x
-rwxr-xr-x
-rwxr-xr-x
-rwxr-xr-x
1
1
1
1
1
apg
apg
apg
apg
apg
apg
56197
apg
456
apg
17818
apg
21673
apg 10096640
Feb
Feb
Feb
Feb
Feb
20
18
18
18
18
10:22
11:38
11:38
11:38
11:35
LunMappingDetection.pl
LunMappingDetection_conf.txt
RSC.pm
RSCPP.pm
inq-archive.tar
./hpux:
total 33784
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
apg
apg
apg
apg
apg
apg
56075
apg
456
apg
17818
apg
21673
apg 34488320
Feb
Feb
Feb
Feb
Feb
18
18
18
18
18
11:40
11:40
11:40
11:40
11:35
LunMappingDetection.pl
LunMappingDetection_conf.txt
RSC.pm
RSCPP.pm
inq-archive.tar
./linux:
total 27748
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
apg
apg
apg
apg
apg
apg
apg
56075
apg
456
apg
17818
apg
21673
apg
36
apg 28303360
Feb
Feb
Feb
Feb
Feb
Feb
18
18
18
18
18
18
11:37
11:35
11:37
11:35
11:20
11:35
LunMappingDetection.pl
LunMappingDetection_conf.txt
RSC.pm
RSCPP.pm
example-script.sh
inq-archive.tar
./solaris:
total 17376
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
-rwxr-xr-x 1
apg
apg
apg
apg
apg
apg
56075
apg
456
apg
17818
apg
21673
apg 17684480
Feb
Feb
Feb
Feb
Feb
18
18
18
18
18
11:41
11:41
11:40
11:40
11:35
LunMappingDetection.pl
LunMappingDetection_conf.txt
RSC.pm
RSCPP.pm
inq-archive.tar
./windows:
total 108
-rwxr-xr-x 1 apg apg 100861 Feb 18 11:35 LunMappingDetection.ps1
-rwxr-xr-x 1 apg apg
456 Feb 18 11:35 LunMappingDetection_conf.txt
-rw-r--r-- 1 apg apg
22 Feb 18 11:20 example-script.ps1
/opt/APG/Collecting/Stream-Collector/Generic-RSC/conf/scripts
Physical Host Discovery in EMC ViPR SRM 3.7
20
Q: How do I enforce the physical collector to use INQ for storage data
collection?
A: The SolutionPack for Physical Hosts searches for specific locations on target host to be
discovered.
For Windows, INQ is required only for Windows 2003 hosts.
For UNIX hosts, the absolute location for INQ can be provided in generic-host
SolutionPack (if it is pre-installed). The locations in which ViPR SRM looks for INQ in
the target host are present in the script:
# list of possible locations for some binaries
my %cands=(
inq => [qw( ./inq /tmp/nl_dwd/inq /opt/sca/bin/inq )],
If INQ is not found in any of these locations, it will be pushed to ./inq.
Alternatively, if a user selects “Push INQ” in Generic-RSC SolutionPackBlock, VIPR
SRM will push INQ in $USR_HOME directory configured on hosts.
Q: If INQ is placed in a different location, how do I add it to SolutionPack for
Physical Hosts?
A: You can configure ViPR SRM to look in additional paths for INQ:
1. Log into the ViPR SRM UI with an account that has administrator privileges.
Physical Host Discovery in EMC ViPR SRM 3.7
21
2. Select Administration on the top menu.
3. In the left pane, navigate to Administration > Centralized Management >
SolutionPacks. A new browser tab is launched to administer your installed
SolutionPacks.
4. In the new browser tab, select Infrastructure > Physical Hosts.
5. Click the pencil icon to edit the scripts component of the SolutionPack for
Physical Hosts. The SolutionPack Reconfiguration page displays.
Physical Host Discovery in EMC ViPR SRM 3.7
22
6. Select the Use advanced settings checkbox to display the Location of the inq
binary field.
7. Type the path where INQ is located on the target host into the Location of the
inq binary field. For example, /usr/site/bin.
8. Click Reconfigure and apply the change.
Physical Host Discovery in EMC ViPR SRM 3.7
23
Q: For Physical Hosts discovery, what are the least privileges that I need for
Windows systems?
A: For the agentless collection method:

The users can be domain users (or local administrators although it is not
mandatory that local admin credentials needs to be provided).

Local user privileges will not provide VIPR SRM with access to all the
information required for agentless collection. Specifically Internal Disks and
SAN Disks data cannot be collected.

The users should be part of local administrator group as higher privilege levels
are required to access miniport driver API’s to obtain host port to array LUN
connectivity.
A: For the EMC Host Interface agent collection method :

Admin privileges are not required.

Refer to VIPR SRM documentation for the EMC Host Interface for credentials
required for EMC Host Interface.
Physical Host Discovery in EMC ViPR SRM 3.7
24