ProSphere Version 1.5 Release Notes

RELEASE NOTES
EMC ProSphere
1.5
Release Notes
P/N 300-013-622 REV A01 March 7, 2012
These release notes contain supplemental information about EMC ProSphere release 1.5. Topics include:

Revision history ........................................................................................................ 4 Product description................................................................................................... 5 New features and changes ........................................................................................ 5 Problems fixed in ProSphere 1.5 ............................................................................... 8 Deployment .............................................................................................................. 9 Downloading files ..................................................................................................... 9 Deployment .............................................................................................................. 9 Known problems and limitations............................................................................. 11 Documentation Errata ............................................................................................. 33 Technical notes ....................................................................................................... 40 Documentation library ............................................................................................ 41 Troubleshooting and getting help............................................................................ 41
Revision history
Revision history
The following table presents the revision history of this document:
Revision A01 Date February 27, 2012 Description Final documentation build prior to the 1.5 release of ProSphere
ProSphere 1.5 Release Notes
Product description
Product description
EMC ProSphere is an integrated family of components that provide you with a coherent approach to managing your storage environment and simplifying many of your common storage management tasks. ProSphere is designed for use in heterogeneous environments containing multi-vendor networks, hosts, and storage devices. The information this system collects and the functionality it manages can reside on technologically disparate devices in geographically diverse locations. However, ProSphere moves a step beyond storage management and provides a platform for the cross domain correlation of device information and resource topology, allowing you to obtain a broader view of your storage environment as well as your enterprise data center.
New features and changes

This major release contains the following new functionality:
Alerting
Alert management features have been expanded to include the following options in the Admin area. Note: Alert Management is no longer available in the Operations area. Manage Performance Alert Thresholds Earlier called Set Performance Threshold, this feature has been moved from the Operations > Alerts > All Alerts view to the Admin > Alert Management tab. Manage SNMP Trap Destinations New feature for management (add, edit, and delete) of Simple Network Management Protocol (SNMP) destinations for forwarding ProSphere alerts as SNMP traps. You can also disable or enable SNMP trap forwarding using this option. Note: The ProSphere Management Information Base (MIB) file (available for download from Powerlink) supports only OCTET STRING and NUMERIC syntaxes for alert object identifiers (OIDs).
EMC ProSphere Administrators Guide, Alerting chapter provides detailed

information on the MIB structure and required SNMP configuration. Manage Alert Sources New feature for consolidation of alerts from Symmetrix Performance Analyzer (SPA) element manager directly, and from the Symmetrix Management Console (SMC) through the EMC SMI-S Provider. List of external alerts supported in ProSphere on page 37 provides a list of the SPA and SMC alerts collected and displayed in ProSphere.
New Source column added to the Operations > Alerts > All Alerts view helps you determine the alert source ProSphere, SPA, or SMC. A corresponding new Source field is also added to the All Alerts view > Details panel.
Capacity
The new Explore Console icon and series of view blocks supports the detailed enumeration of all discovered configuration items of a given type. The view blocks can be filtered and reordered. The Explore > Service Levels tab allows management of array utilization by tiers based on various pre-defined or custom criteria. ProSphere uses these criteria to tag LUNs and display disk capacity data. Metrics, tables and graphical representations for historical and real time array capacity data.
Discovery and performance
Discover topology and collect performance data for WS-MAN configured Windows hosts. Gather performance data for virtual hosts using VMware vCenter Server. Collect performance metrics from VMware using the VAMI API. For the 1.5 release, all ESX Server host metrics are supported. The following two metrics are not supported on VMware Guests: Host Devices - Response Time Host Devices - Queue Length
Compare and examine array performance metrics using the Compare Days feature in the Configuration Item dialog box. View performance charts of a switch with the connected host, Inter Switch Link (ISL), or array ports. The performance charts can be categorized either by top five by average throughput or custom port selection. View topology from the perspective of a switch. Discover hosts based on partial host information obtained from zoning data. Delete configuration items in Discovery > Objects List view. View details of a configuration items discovery status in the new Discovery Log dialog box from Discovery > Objects List > Discovery Status column link.
Security
The new Manage Application Software option allows the Security Administrator to check for and apply ProSphere updates instead of using a web browser to access the update interface. Note: The VMware vCenter interface is required to upgrade from ProSphere 1.0 to 1.5.
For Secure Hypertext Transfer Protocol (HTTPS) communications, ProSphere now supports only Transport Layer Security (TLS). Secrets in ProSphere 1.5 are encrypted and stored using RSA JSafe application programming interfaces (APIs) which are Federal Information Processing Standard (FIPS) Publication 140-2 compliant.
Ability to edit the default passwords for the root and appadmin accounts. The Security Administrator can modify the default passwords for these accounts on first login after update and first login after deployment, respectively. Provision to disable SSH access to ProSphere virtual machines. Synchronization of data across multiple ProSphere deployments requires the Security Administrator to set a common synchronization passphrase with the new Configure Synchronization Passphrase option in the Admin > Users and Security tab.
Serviceability
REST API contains new URIs for array capacity, performance, topology data, GET operation on all alerts, and retrieval of metric information from the historical database. New logs have been added to the following components in Admin > Manage Logs: Alerting > Alert indication client (new sub-component) Capacity (new component, with the sub-components Capacity UI server, Capacity Input Server, and Service level service) Database Infrastructure > Configuration service and Admin Service Topology > Topology Change Notification
SMI-S indications for SMC are also logged in the Admin > Manage Logs > Discovery component > Indication domain manager sub-component logs. Install ConnectEMC feature to enable collection and transfer of health information of your ProSphere deployments. The health information would include the following details: Site information (site name) ProSphere component version details (ProSphere Application, Discovery Engine, and database) Number of collectors Number of discovered objects Compliance details Performance details (system usage resource)
Single Sign On and Launch-in-Context
ProSphere Single Sign On and Launch-in-Context is expanded to support Symmetrix Management Console (SMC) and the Connectrix Manager Converged Network Edition (CMCNE) Top Talkers. Brocade element managers on page 24 describes how CMCNE support is currently handled.
Launch-in-Context for Symmetrix Performance Analyzer (SPA) from the ProSphere UI now includes these additional launch points: A storage group within SPA from the Array LUNs Details dialog box
ProSphere 1.5 Release Notes 7
Problems fixed in ProSphere 1.5
The SPA Front End Directors from the Array Adapter Details dialog box. Note: The Release Notes are only available from Powerlink.
Problems fixed in ProSphere 1.5

Problems fixed in ProSphere are organized alphabetically by product feature, then numerically by issue number. This table lists those problems that existed in 1.0.0.x, and were fixed in 1.5.0.0.
Table 1 Problems fixed in ProSphere 1.5 Issue number 566901 566907 Product feature Discovery Discovery Problem summary ProSphere is unable to establish host to array relationship. VMware ESX server discovery fails with the following errors:
vmx failed for unknown reason Internal Probe Error'
632708
Discovery
Discovery of CLARiiON CX4-960 arrays failing in ProSphere 1.0.0.2 with the following error:
Indication destination has not been configured. Indications cannot be received and will not trigger rediscoveries. Failed to discover SCSIProtocolControllers for Array CLARiiON+<array>
633503 555390 555779 555930 558827
Discovery Performance Performance Performance Performance
Symmetrix VMAX array discovery fails. Path performance data collection fails for storage arrays in ProSphere 1.0.0.1 when the access credential is modified. ProSphere fails to detect Cisco switches when the SNMP Agent does not return any data. ProSphere SNMP v3 access credential is not collecting switch performance data even that full path is discovered. ESX performance data not collected.
Deployment
Deployment
Downloading files
ProSphere is delivered in a variety of file formats for different purposes. Refer to Table 2, ProSphere file types and deployments, for a description of the file types and their purposes. All of the required files can be downloaded from Powerlink.emc.com. Once you have logged in, navigate to Support -> Software Downloads and Licensing -> P-R -> ProSphere.
Table 2 ProSphere file types and deployments Deployment purpose New deployment Files to download OVF files and VMDK files ProSphere-1.5.0.x.<build#>.ovf DiscoveryAppliance_system-3.0.2.x.<build#>.vmdk HistoricalDatabase_system-1.5.0.x.<build#>.vmdk HistoricalDatabase_sdb-1.5.0.x.<build#>.vmdk StorageResourceManager_system-1.5.0.x.<build#>.vmdk StorageResourceManager_sdb-1.5.0.x.<build#>.vmdk CollectorAppliance_Update-3.0.2.x.<build#>.ovf CollectorAppliance_system-3.0.2.x.<build#>.vmdk ZIP files DiscoveryAppliance_Update-3.0.2.x.<build#>.zip HistoricalDatabase_Update-1.5.0.x.<build#>.zip StorageResourceManager_Update-1.5.0.x.<build#>.zip CollectorAppliance_Update-3.0.2.x.<build#>.zip ISO files DiscoveryAppliance_Update-3.0.2.x.<build#>.iso HistoricalDatabase_Update-1.5.0.x.<build#>.iso StorageResourceManager_Update-1.5.0.x.<build#>.iso CollectorAppliance_Update-3.0.2.x.<build#>.iso Method Deploy using the vCenter software
Update an existing deployment
Extract files and deploy using an existing Web server
New deployment or update an existing deployment
Load files into an existing virtual CD-ROM drive
Deployment
ProSphere 1.5 component builds

ProSphere 1.5 is composed of the following VM builds:
Table 3 ProSphere 1.5 builds ProSphere Virtual Machine ProSphere Application Discovery Engine Discovery Engine Collector Historical Database Build 1.5.0.0.408 3.0.2.0.362 3.0.2.0.362 1.5.0.0.378
Deployment procedures
EMC ProSphere: Preparing for Deployment describes background software and
configuration steps that must be completed before an initial deployment commences. The procedures for new deployments are documented in the EEMC ProSphere Deployment Guide. The procedures for updates are documented in Chapter 9 of the EMC ProSphere Administrators Guide.
Backup
The EMC ProSphere Administrators Guide, Chapter 9, provides information about the recommended procedures for backups and other preparations prior to the updating of ProSphere.
10
Known problems and limitations

Alerting................................................................................................................... Browsers................................................................................................................. Capacity.................................................................................................................. Configuration Item dialog........................................................................................ Console .................................................................................................................. Deployment ............................................................................................................ Discovery ................................................................................................................ Element Managers .................................................................................................. Groups.................................................................................................................... Log files .................................................................................................................. Performance data and UI......................................................................................... EMC SMI-S Provider................................................................................................. Rediscovery ............................................................................................................ Search for objects ................................................................................................... Security .................................................................................................................. Synchronization of ProSphere Deployments ............................................................ UI display................................................................................................................ Updates, Shut down, and Reboot ............................................................................ VMware................................................................................................................... Wiki and help software............................................................................................
11 12 13 16 16 16 17 24 25 26 27 29 29 29 30 30 31 31 32 32
Alerting
Alert message format in ProSphere differs from original SMC message format Engineering Issue 634815
For some alerts, you might see a difference in the message format between SMC and ProSphere. This is because ProSphere receives SMC alerts from SMI-S Provider indications and not from SMC.
Workaround
There is no workaround available.
Consolidated SMC alert occurrence count is incremented multiple times for a single SMI-S Provider indication Engineering Issue 634386
The occurrence count for SMC (SMI-S) alerts in the All Alerts view may exceed the actual number of alerts received.
Workaround
There is no workaround at this time.
Help buttons missing for some alerting dialog boxes Engineering Issue 583579
The following dialog boxes are missing Help buttons, although the help topics exist:
Create Destination Details Edit Destination Details
Workarounds
1. Open the help system and search for Create Destination Details or Edit Destination Details. 2. Open the help system and navigate through the Contents to: ProSphere Console > Admin > Alert Management > Manage SNMP Trap Destinations then open the relevant help topic.
Browsers
Potential memory leak Engineering Issue 561703
When logging out of the ProSphere Application (or when your session is terminated due to inactivity) EMC strongly recommends shutting down your browser before logging back in. Failing to do so may result in poor client performance as some resources are not fully released when reusing the same browser application.
Workaround
Close the browser window and restart your session. Simply logging out and back in will not necessarily address this issue.
Console page can be stale because IE is retrieving stored pages rather than getting fresh content Engineering Issue
The ProSphere console is displayed within a browser, and some browsers default to retrieving older cached pages rather than the current page.
Workaround
Use IE 8 or one of the other browsers. Specify that newer versions of the pages should be used rather than stored versions. For IE 8, use the following procedure: 1. Go to Tools -> Internet Options -> Browsing History -> Settings 2. In the Temporary Internet Files section, select Every time I visit the webpage for when to check for newer versions of stored pages. Click OK. 3. Go to Tools -> Internet Options -> Browsing History -> Delete 4. Check -> Temporary Internet files 5. Clear -> Preserve Favorites website data. Click Delete. 6. Restart Internet Explorer. IE 9 does not appear to recognize the configuration change in steps 1 and 2, so you may have to use IE 8 or another browser.
12
Capacity
Symmetrix Configured Including RAID and RAID Overhead may vary from SYMCLI Engineering Issue 557944
EMC has discovered that the methodology used to calculate the Symmetrix raw capacities may vary from what the Solutions Enabler SYMCLI utility reports. The discrepancy in the capacity values is caused by the way in which system overhead is being calculated for a given array. Data from SYMCLI or SYMDISK represents the disk drives and hypers with no specific organization, while ProSphere organizes the disk drives and hypers into a set of pools, pool of pools, and storage volumes allocated from various pools. EMC is working on resolving the discrepancy in the capacity values in a future release. The discrepancies are reflected in these metrics: Configured Including RAID and RAID Overhead.
Workaround
There is no workaround at this point.
CLARiiON in Equalizing state will return incorrect values

When a CLARiiON disk which had failed and was being replaced with a hot spare is itself replaced with a good new drive, the disk is put into the Equalizing state, and the data on the hot spare is copied back to the new drive. While the CLARiiON array status does not show as degraded when disk is in equalizing state, the EMC SMI-S Provider may return inaccurate numbers, include negative values.
Workaround
Once all the disks are in a Ready state the next discovery of the array will resolve the invalid metrics.
Thin pool used value reported by ProSphere may exceed SMC or SYMCLI value Engineering Issue 561849
ProSphere reports a higher thin pool used value than reported by SMC and Symmetrix Command Line interface (SYMCLI).
Cause
ProSphere calculates the thin pool used by summing up the capacity of all the pool LUNs, whereas SMC and SYMCLI report pool used and free values using the pool statistics. The difference in these two approaches may result in slight variations in values.
Workaround
13
CLARiiON devices are incorrectly marked with LUN type Write Intent Log which impacts capacity metrics Engineering Issue 583293
Clone Private LUNs are reflected as Write Intent Logs. Clone Private LUNs should be categorized under Local Replica capacity, however they are categorized under Remote Replica capacity.
Workaround
Usable Capacity includes duplicate values Engineering Issue 583663

For CLARiiON arrays:
The Usable Capacity for an array may not match with the sum of all Usable Capacity for pools because the Snap Pool, Local Replica Mirror Pool, and Remote Replica Mirror Pool are created on top of a RAID group, so the RAID group capacity values already include those 3 pools, resulting in these values being counted twice.
Usable Capacity for a CLARiiON array = Configured Usable for RAID Group + Configured Usable for Storage Pool
The Usable Capacity for a RAID Group may not match with the sum of Used + Free + Pool Free. This is related to the first bullet, as Usable Capacity includes LUN Contributors for Snap and Replica pools, and Usable is not the same as Used + Free + Pool Free. It must include pool contributors to make the number match.
Usable Capacity for a RAID Group = Used + Free + Pool Free + LUN Contributors
The Usable Capacity for a Storage Pool may not match with Used + Free + Pool Free. Similar to a RAID group, a Storage Pool can provide storage for a Snap pool, but must also include LUN contributors for Snap Pool to make the numbers match.
Usable Capacity for a Storage Pool = Used + Free + Pool Free + LUN Contributors
For Symmetrix arrays:
For a Symmetrix thin pool, when there are disabled DATA devices, the Usable Capacity of a Pool does not match with Pool Used + Pool Free + Free
Instead, the following two definitions should be used:

Enabled Capacity of the Pool = Used + Free + Pool Free
or
Usable Capacity of the Pool = Used + Free + Pool Free + sum of disabled DATA devices
Workaround
14 ProSphere 1.5 Release Notes
VCMDB and ACLX devices on Symmetrix Engineering Issue 562068

Symmetrix arrays use the system devices Volume Control Manager Database (VCMDB) and Access Control Logix (ACLX) to manage the mapping and masking of LUNS from the array front end ports to a host. These devices may be visible to hosts, however in capacity reports for ProSphere 1.5 the relationship from the array LUN to the host devices is not shown. The host and host device columns for these devices will be empty.
Workaround
Some capacity metrics are incorrectly reported Engineering Issue 557944

The capacity metric Configured Including RAID for a Symmetrix will be incorrect for the following reasons:

The RAID overhead for RDF devices was not properly accounted for. The RAID overhead/space consumed is not handled property for private devices such as Vault devices.
The capacity metric Configured Usable for a Symmetrix will be incorrect because it includes Diskless Devices. The capacity metric Unusable for Symmetrix will be incorrectly computed for all Symmetrix arrays with the Hot Spare capacity.
Workaround
No workaround available.
Arrays missing from Capacity reports after synchronization of multiple ProSphere deployments Engineering Issue 583419
When synchronization is done with a new ProSphere deployment, the arrays discovered in the new ProSphere deployment may not be available to the ProSphere Capacity repository for up to a week. This affects the Capacity reports.
Workaround
EMC recommends that when you add a new ProSphere deployment for synchronization, ensure that discovery is not in progress for any array in the new ProSphere deployment. You can do this by checking that the Discovery > Objects List > Arrays > Discovery Status column for the arrays does not display Running. If it is, wait until the discovery is complete before adding the ProSphere deployment for synchronization. If the arrays are missing despite the recommended precaution, take one of these measures to correct the problem:

Manually rediscover the missing arrays. Wait for ProSpheres weekly full rediscovery job to run. The arrays should be automatically rediscovered when this job completes.
Configuration Item dialog

Potential memory leak Engineering Issue 561703
When viewing the Configuration Item (CI) Dialog repeatedly, the client browser may begin to exhibit performance issues.
Workaround
Close the browser window and restart your session. Simply logging out and back in will not necessarily address this issue.
Switch performance charts produce an error Engineering Issue 561695

Switch performance charts are populated when the switch CI dialog is opened and Performance tab is selected. However, from Array or Host CI dialog, when the switch is selected in the map and Performance tab is selected, there is an attempt to load data into the charts which fails with 'No performance data is available' message. This message is misleading, the views should display a message that indicates the view is not implemented.
Workaround
There is no workaround currently.
Console
Network Latency Causes Timeouts (502 Error)
Depending on network latency or machine load, occasional messages during normal operation will report failures relating to Apache Error code 502. This can happen during various operations. Due to the mechanisms used to communicate between components in ProSphere, EMC recommends checking the status of such an operation through the ProSphere application prior to restarting it. These errors do not always imply the underlying operation failed, but may refer to post-operation communication of status.
Deployment
Allow time for file download and deployment
The download time for the OVF files and the associated VMDK files can vary from minutes to many hours, depending upon the network bandwidth and the location of the files. If necessary, schedule the file downloads for time periods when critical personnel are not required to be present. In addition, actual deployment time depends on the location of the downloaded OVF files relative to the vCenter/ESX where the vApps are going to be created. In other words, to reduce the deployment time, the host containing the OVF files should be on the same subnet as the ESX server on which the vApps are created.
16
Uppercase characters cause log service to fail Issue

If you deploy ProSphere using any uppercase characters for the host names, the error ADM-0003 is displayed and the log management service fails to run.
Workaround
Use only lowercase characters in the host names when deploying ProSphere.
Discovery
On start of DST, Discovery Job does not allow schedule between 00:00 02:00 Engineering Issue 584584
On the start of Daylight Saving Time (DST), the Discovery Job wizard > Set Schedule does not allow users to select any time between 00:00 and 2:00 from the drop-down. Manual entry of time between 00:00 and 2:00 is incremented by one. For example, if 0:05 is typed, it is automatically incremented to 1:05. Note: This issue does not affect any day other than start of DST.
Workaround
Auto-refresh does not work for Discovery > Object Views Engineering Issue 584056, 584057
The auto-refresh feature is not available in Objects List views for Arrays, Switches, Fabrics and Hosts. Due to this, the newly discovered CIs or any changes to the CIs are not refreshed automatically.
Workaround
The changes to the CIs can be seen through a manual refresh by clicking on the refresh icon in the view title bar
Domain user account is not supported with WS-MAN Basic authentication Engineering Issue 635024
Windows Remote Management (WinRM) service on Microsoft Windows hosts supports Basic authentication only for local administrator accounts. ProSphere 1.5 supports Basic Authentication with SSL certificates for encryption of passwords.
Workaround
Discover Windows hosts with local administrator accounts. The EMC ProSphere Support Matrix also indicates that domain user accounts are not supported in ProSphere for WS-MAN based discoveries.
17
Discovery job using the WS-MAN access credentials appear to be hung in the ProSphere UI when 240 IPs are scheduled for discovery Engineering Issue 583933
During subnet discovery, the WS-MAN discovery job takes a longer time to discover the hosts if you have 100 IPs and above scheduled for discovery in a single discovery job.
Workaround
Create separate WS-MAN discovery jobs, each having 64 IPs, to successfully complete discovery within 3 to 4 hours.
EMC SMI-S Provider configuration The problem

Symmetrix masking and mapping data is not discovered when new access pools have been created and contain devices.
The solution
Set up the proper Access Control Lists and permissions on the EMC SMI-S Provider host.
How do I configure Symmetrix ACL?

If Symmetrix Access Control is being used to protect Symmetrix devices, the host from which you run the device masking commands must be configured in an access control group with an ACL (Access Control List) granting VLOGIX rights to ALL_DEVS. If Solutions Enabler Access Control is enabled on the Symmetrix array, then the host on which the SMI-S Provider is running must have sufficient privileges to perform the necessary operations. At a minimum, the host on which the SMI-S Provider is running must be in a group that has access to ALL_DEVS with BASE and VLOGIX privileges.
VLOGIX behavior
During initial setup of the system, the access group UnknwGrp !INPOOLS ALL is present. In this scenario, the VLOGIX privilege returns as True since you are granted access to all devices in the Symmetrix array. Initially, because no pools are present, the VLOGIX privilege is associated implicitly with all devices by this ACL. Once you create an access pool and add a device to it, the VLOGIX privilege is no longer implicitly associated with all devices and, therefore, a check for the VLOGIX privilege would now fail. For the UnknwGrp to still have VLOGIX privilege, that privilege must be explicitly granted to the UnknwGrp and associated with ALL_DEVS.
How to determine if the EMC SMI-S Provider is configured properly

1. Determine if Access Control Lists are enabled on the Provider host Note: Do not confuse an Access Control of N/A with access control being Disabled. N/A simply means that the host where this command is being run does not have the ADMIN privileges to view the ACLs and Groups. 2. Verify Access Control List configuration allows the EMC SMI Provider to access the masking database
18 ProSphere 1.5 Release Notes
(Expanded discussion of these points in the following SYMCLI examples section)
SYMCLI examples
1. Determine if Access Control Lists are enabled on the Provider host. Example of Access Control being OFF (Disabled)
>symacl list -v -sid 000187400019 S Y M M E T R I X A C C E S S C O N T R O L Symmetrix ID: 000187400019 Access Control : Disabled Session Locked : N/A Time Held in Seconds : 0 Lock Identifier : N/A Time Enabled Time Disabled Time Updated ADMIN priv ADMINRD priv : N/A : N/A : N/A : N/A : N/A S T A T U S
>symacl list -acl -sid 019 Symmetrix ID: 000187400019 Symmetrix access control is disabled for this Symmetrix
Example of Access Control being enabled but EMC SMI-S Provider host does not have ADMIN privileges
Note: Do not confuse an Access Control of N/A with access control being Disabled. N/A simply means that the host where this command is being run does not have the ADMIN privileges to view the ACLs and Groups.
>symacl list -v -sid 854 S Y M M E T R I X A C C E S S C O N T R O L S T A T U S
Symmetrix ID: 000194900854 Access Control Session Locked Time Held in Seconds Lock Identifier Time Enabled Time Disabled Time Updated ADMIN priv ADMINRD priv : : : : N/A N/A 0 N/A
: N/A : N/A : N/A : No : No
2. Verify Access Control List configuration allows the EMC SMI-S Provider to access the masking database.
19
a. If Access Control is disabled then there is no need to do anything and the EMC SMI-S Provider should be able to access the masking database. b. If Access Control is enabled and there are no other access pools other than ALL_DEVS and !INPOOLS, then the EMC SMI-S Provider should be able to access the masking database. c. If Access Control is enabled and there are additional access pools with devices allocated to them, then verify that the EMC SMI-S Provider host belongs to a group that has VLOGIX access to the ALL_DEVS access pool. IMPORTANT If volumes were never added to an access pool then the Provider may appear to have the correct privileges since it will return masking information. However, as soon as an access pool is created and a volume assigned to it then the EMC SMI-S Provider will no longer be able to access the array's masking and mapping database until the Provider host is added to an access group that has VLOGIX access to the ALL_DEVS access pool.
Example of an EMC SMI-S Provider host that has Access Control enabled but does not have any other access pools In this case, the Provider host belongs to UnknwGrp which does not have the VLOGIX access listed under Access Type. But, as long as there are no access pools that have devices added, then this Provider would be able to access the masking database since the !INPOOLS pool exists with access type ALL. However, as soon as an access pool is created and a device added (!INPOOLS pool access type changes to BASE) then this same Provider would no longer have access to the masking database.
>symacl list -acl -sid 854 Symmetrix ID: 000194900854 Group Name Pool Name Access Type ----------------------------------------------UnknwGrp ALL_DEVS BASE UnknwGrp !INPOOLS ALL
The following command checks for additional access pools that contain devices which, if found, would cause a change in the !INPOOLS default behavior:
>symacl list -accpool -sid 407 Symmetrix ID: 000194900407 Number of Devices --------10 Number of ACLs --------0
Pool Name --------------------------------TestPool
>symacl list -acl -sid 407 Symmetrix ID: 000194900407 Group Name ---------------TestGRP Pool Name ---------------TestPool Access Type ----------BASE
20
Deleted objects may not be removed from the Discovery > Objects list Engineering Issue 561689
Under some conditions, deleting an object in the Objects List does not remove it from display, even though the object is removed from the database.
Workaround
Log out then log back in, thereby forcing a refresh of the displayed objects.
VM initial discovery fails Issue

The initial discovery of VM host fails occasionally with an error:
Querying VMware web service for previously found VM <VM DNS name> failed for unknown reason. Aborting VM/IP/OS discovery.
The VM host which was detected initially, changed its state during discovery or just before discovery. It was either powered down or deleted resulting in discovery failure. The UI may show inconsistent failure results and empty Object Name for this VM host.
Workaround
Rerun the initial discovery policy to fix this issue.
Discovery of ESX and VM Guests without a DNS entry creates inaccurate data in the Objects list Issue
Discovering ESX and VM guests without a DNS name will result in an inaccurate Inventory view for these objects.
Workaround
Assign DNS names to ESX and VM guests before discovery of the vCenter by ProSphere.
Proper credentials required for ESX discovery Issue

If you use the ESX host credentials for discovery of an ESX server, both the ESX host and the VM are discovered. However, in the ESX object details view the tabs labeled VMs and Path Details are missing.
Workaround
Discover ESX through the VMware Virtual Center.
Connectivity view: Missing HBA Vendor and Firmware for ESX Engineering Issue 547444
In the Connectivity view for ESX, the HBA Vendor and Firmware details are missing.
21
Workaround
Although there is no workaround for this problem, it is recommended that ESX and the associated VM discovery be done through the VMware vCenter host using the VMware Infrastructure credentials.
Faulty schedule timer in the Create Discovery Job wizard Engineering Issue 548759
While setting a schedule for a job in the Create Discovery Job wizard, the specified hour value resets automatically to unintended values.
Workaround

Set the hour value first, followed by the minute value. If you set the minute value first followed by the hour value, then you must set the hour value twice.
Job Execution Results dialog box takes several minutes to show discovery job progress Issue
In the Discovery Jobs > Log tab > Run Date column, when you click on the run date for a job that is discovering a very large number of objects, it takes several minutes for the Job Execution Results dialog box to show the job progress.
Workaround
Click the discovery job values in the # Failed Detections, # Partially Discovered Objects, and # Fully Discovered Objects to display the job status.
Job Execution Results: Object name missing Issue

For discovery jobs that involve VMware discovery, the Job Execution Results dialog box could contain an empty object name. This happens when the virtual machine object corresponding to that result is deleted from the system due to a DNS change event, or when a user deletes the host after it is discovered. The second case is possible with any physical host other than the ESX server.
Workaround
There is no workaround.
Job Execution Results shows object name after discovery failure Issue
When viewing Discovery Jobs -> Details -> Run Date -> Job Execution Results - Job Run Date table, the Object Name column cells will be populated with an object even when there has been a detection failure. In these cases, the cells should be empty.
22
Workaround
Launch the Failed Detections and Fully Discovered Objects dialogs using the individual links in the cells of the # Failed Detections and the # Fully Discovered Objects columns.
ProSphere discovers Symmetrix arrays that are local to an EMC SMI-S Provider Issue
A Symmetrix array is considered local to the EMC SMI-S Provider when it is directly accessible over Fibre Channel through Symmetrix gatekeepers. Symmetrix arrays that are remote to the EMC SMI-S Provider are indirectly accessed through another Symmetrix by way of a Symmetrix Remote Data Facility (SRDF) connection. These remote Symmetrix arrays are not discovered by ProSphere because masking and mapping data cannot be obtained. A detection failure is present for each remote Symmetrix array found during an initial discovery to alert the user.
Workaround
Two EMC SMI-S Providers are necessary for ProSphere to discover both Symmetrix arrays connected in an SRDF configuration. In this case, each EMC SMI-S Provider will have a Fibre Channel connection to one of the Symmetrix arrays which represents one end of the SRDF connection. For example, EMC SMI Provider on host AtoB will see Symmetrix A through a fibre connection and Symmetrix B through an SRDF connection. In contrast, EMC SMI Provider on host BtoA will see Symmetrix B through a fibre connection and Symmetrix A through an SRDF connection. Therefore, ProSphere requires array discovery policies that include both EMC SMI-S Providers so that both Symmetrix A and B are discovered. As expected, each array discovery policy will report a detection failure for each remote Symmetrix.
Insufficient number of Symmetrix Gatekeepers causes slow Provider performance and discovery failures Issue
An insufficient number of Symmetrix gatekeepers results in slow Provider performance and contributes to discovery failures due to timeouts.
Workaround
For optimal EMC SMI-S Provider performance and stability, ensure that there are at least six gatekeepers per Symmetrix that is fibre-connected to an EMC SMI-S Provider host. Adding more than six Gatekeepers for larger Symmetrix arrays marginally improves performance.
Array discovery will fail if the SMI Indication Destination cannot be obtained Issue
Array discovery may fail and the following errors may appear in the discovery job results:
Indication destination has not been configured. received and will not trigger rediscoveries. Indications cannot be
23
Invalid subscription destination. Check network settings. Event rediscovery may be affected.
Cause
The Broker temporarily loses contact with SMI Indication Adapter and cannot pass its location to the array discovery so the indication destination can be determined. When the array discovery attempts to subscribe to indications it must pass this indication destination and ultimately fails because no destination is available.
Workaround
Run the array discovery job again since the broker may have re-established communications with the SMI Indication Adapter.
CPU and OS version are not reported for Virtual Guest Issue
In the Attributes tab for Virtual Guest, the CPU and OS version information is not reported.
Workaround
The Operating System attribute provides information on the OS version.
Element Managers
Brocade element managers
EMC recommends the use of CMCNE version 11.1.1, which is available now. While users can perform discovery with it, it does not support Single Sign On or Top Talkers (link-and-launch) functionality. In April, CMCNE version 11.1.3 will be available on Powerlink. With this version of CMCNE, users can get Single Sign On and Top Talkers (link-and-launch) functionality.
SPA metric names differ from ProSphere metric names Engineering Issue 633734
The names for alert metrics reported in SPA and the ProSphere UI may differ. For example:

SPA uses the term IOs/sec, but ProSphere uses the term IO_RATE SPA uses the term Avg Read Response Time (ms), but ProSphere uses the term RESPONSE_TIME_READ
Workaround
24
Groups
Group operations may be affected when Topology Server or discovery load is high Engineering Issue 635107
If the Topology Server or discovery load (high number of discovery jobs are in progress) is high, normal group operations group creation, edit, and so on slow down. Users may even encounter a 502 error.
Workaround
Wait for a few minutes and refresh the Groups view. Since most operations are recorded at the back end, they will not be lost. Changes in the Groups view should become visible a few minutes after refresh.
Group operations may return the 502 error Engineering Issue 584002
When discovery or rediscovery operations are in progress, the creation, deletion, or modification of groups may sometimes return the HTTP 502 error through the ProSphere Console. But although the operation is delayed, it will be processed. The updated group data may not be reflected immediately.
Workaround
Refresh the Console after 10 minutes to verify the operation was successful.
Groups expand button visible Engineering Issue 574185

In Groups tree an expand button appears for a group, though there are no members or subgroups associated with this group.
Smart Group criteria cannot have special characters Issue

The Value field in Create Smart Group and Edit Smart Group dialog boxes cannot have special characters like , #, and :. If a Smart group is created using these special characters, the Value field is blank when you edit the smart group.
Name and Display Name are displayed for synchronized objects Engineering Issue 580901
Objects can be discovered by multiple ProSphere installations, and those ProSphere installations can then be synchronized, with those objects placed in a Smart Group. If you view the Smart Group on any ProSphere installation other than the one used to discover the object, only the Name and Display Name are displayed. It is also observed that only the physical host icon is displayed for both the physical and virtual synchronized hosts and the Type value for synchronized physical host is displayed as Host (Virtual).
Fabric criteria is not supported for Smart Group Engineering Issue 573357
In the Discovery > Groups > Create Smart Group, there is no option to create a Smart Group for fabrics. The CI type has options only for hosts, arrays, and switches and not for fabrics. Hence, a Smart Group with fabric attribute cannot be created.
Workaround
Log files
Error while unzipping Database log ZIP file on Windows hosts Engineering issue 584613
While unzipping the Database logs downloaded from Admin > System > Manage Logs, the following error occurs:
gpsegstop..py_svthistapp:gpadmin_20120216-Historical_Database.log
This error is caused by the semi-colon in the downloaded ZIP filename, which is not a valid character for filenames on Windows hosts.
Workaround
Instead of WinZip, use WinRAR to unzip the Database logs.
Downloading log files

When you download a set of selected log files, its status appears at the bottom of the browser. Log file downloads can take a very long time depending upon their size. You can minimize the window and work with other modules of ProSphere. However, there is no option to terminate the download. Once you click Download for a set of selected files, the Download Logs button in the user interface (UI) is disabled, thus disabling concurrent downloads of log files. However, another set of log files can be downloaded from another open instance of the same ProSphere appliance.
Editing log levels

The log levels for a few components cannot be edited through the Manage Logs dialog box. The Log files chapter in the EMC ProSphere Administrators Guide provides a list of components that do not support editing of log levels. IMPORTANT Log levels should not be set to the Debug or Trace levels for more than one or two hours. After collecting your log files, you should reset the log level back to Info.
26
Performance data and UI

Migration of WLA switch data uses WWN Engineering Issue 584524
When importing WLA data, only switch ports which are represented using a WWN will yield results within the switch summary view.
Workaround
The data is available using the ProSphere REST API. Refer to the REST API help system on Powerlink for more information.
Path performance collection is not enabled for few hosts in a Smart group after upgrade to ProSphere 1.5 Engineering Issue 583955
In ProSphere 1.0.x, path performance collection was enabled and successfully done for all hosts in a Smart group. However, on upgrade to ProSphere 1.5, path collection performance is found to be disabled for a few newly discovered hosts in the group that match the Smart group criteria.
Workaround
Create a new Smart group with the same criteria as in ProSphere 1.0, and enable path performance collection for the group.
Collection of path performance data for arrays displays incorrect timed out status message Engineering Issue 634321
Collection of path performance data for arrays results in the following timed out status message, even though ProSphere successfully collects the path performance data:
Discovery timed out waiting for status events
This is issue is caused due to missing events during collection of path performance data from SPA.
Workaround
Ignore this status message.
Limitations to path performance collection for virtual machines

If you discover a virtual machine using ESX Server, you will be able to turn on Path Performance Collection with the following limitations:
VMware Guest Performance Charts Host Devices - Response Time and Host Devices - Queue Length are not supported. You can rediscover VM-Guest using WMI/SSH to collect details for the missing charts.
27
Performance data can be interrupted by new discoveries

Once initial discovery of an environment is complete, performance data collection may fail for subsequent discoveries of additional objects. This failure occurs for the polling period (typically 5 minutes). The initial discovery establishes entry points in the database for performance data; if subsequent passes collect data for new objects, these passes are treated as failed data collections.
Workaround
The situation is self-correcting. Data collection passes that happen after the failed one are processed correctly if there are no further changes relative to the failed time interval.
Response time chart is empty for Windows 2008 hosts when queue is 1 Issue
There is an anomaly in Queue Length within Windows 2008 where the queue length is actually N-1. Therefore, if the queue depth is reported as 1, the queue will actually be reported as idle. This has the potential to skew the response time within the Host Summary Performance view.
Workaround
There is no workaround at this point.
Host Device Response Time versus Array LUN Response Time

The host device response time, in comparison to the array LUN response time, might have a deviation such that the corresponding numbers do not match one to one. This is because the following formulas are used to compute the values:
Host Device Response Time = Queue Length / IOs per second Array Device Response Time = (Sample Average Read Time + Sample Average Write Time) / (Sample Average Reads + Sample Average Writes)
Naming of devices is mixed Issue

There are device naming inconsistencies in the Host Devices - Chart Details dialog box that cause devices to appear with two different name formats, depending on whether or not the device is associated with a known array LUN.
Workaround
28
EMC SMI-S Provider

ProSphere discovery engines that are powered off will impact Provider performance and stability Issue
ProSphere discovery engines that are powered off and have array indication subscriptions with an EMC SMI-S Provider cause the Provider to repeatedly attempt to deliver indications, and thus impacts the Provider's performance and stability. A discovery engine creates indication subscriptions as part of an initial discovery or rediscovery of an array. Once the indication subscriptions are created, the Provider attempts to deliver an indication to the discovery engine whenever the specific array event that triggers the indication occurs.
Workaround
Discovery engines should remain powered on if they have indication subscriptions with a Provider to prevent the Provider from repeated attempts to deliver new indications. For optimal EMC SMI Provider indication delivery performance, it is recommended that no more than three ProSphere discovery engines should access the same EMC SMI Provider. If a discovery engine must be powered off permanently or for several days and the Provider continues to be used, then refer the Remove subscriptions to EMC SMI Provider indications chapter in the EMC ProSphere Administrators Guide for information on removing the indication subscriptions.
Rediscovery
ProSphere displays deleted VMware virtual disks and data stores Engineering Issue 584249
After VMware virtual disks and data stores are deleted and rediscovery is run, Prosphere continues to display them in the Configuration Item dialog box > Path Details and VMs tabs.
Workaround
Remove the ESX host and then run the discovery job.
Rediscovery and DST

Scheduled or unscheduled rediscovery should not be run when the physical servers or VMware virtual machines are operating at the same time as Daylight Saving Time (DST) changes.
Search for objects

Search field may lose original text entry Engineering Issue 549161
If you enter text in the Search field, then navigate to one of the other Console views, the Search field replaces any text you entered with the Search ..." string.
Workaround
Reenter the original text in the Search field.
Security
SSL option functions perfectly with incorrect server certificate Engineering Issue 579917
Initially, LDAP is configured with SSL without providing a server certificate. However, if you provide an invalid SSL certificate, SSL will still function. In this case, the newly provided certificate is not used at all.
Collector registration fails when IP of ProSphere Application is provided instead of FQDN Engineering Issue 634306
Registering of additional collectors fails if you provide the IP address instead of the ProSphere Application hostname.
Workaround
Not available at the time. Type the hostname FQDN.
Synchronization of ProSphere Deployments

ProSphere Application Credentials
ProSphere Applications cannot enter into a synchronized relationship if the login credentials of the Administrator establishing the synchronization are not valid on the various ProSphere Applications being synchronized.
Workaround
Ensure that the Administrator logged into a ProSphere Application to add another ProSphere Application for synchronization has identical user credentials on both ProSphere Applications. The same would also apply if the Administrator were adding more than one ProSphere Application for synchronization.
Time window for discoveries

Delay initiating discoveries on newly synchronized ProSphere Applications for at least 10 minutes after the initial synchronization has successfully completed. This applies to the Master ProSphere Application as well. Because of limitations in the way discovered data propagates through the system, all ProSphere Applications in your synchronized deployment should not have any discovered data at the time when they are first synchronized.
Data across multiple data centers may be incomplete

The goal of ProSphere is to discover and report the network objects and their relationships across your entire enterprise, without regard to what items are physically located in a given data center.
30
ProSphere can discover objects across the enterprise, such as a host in Site A, and switches and arrays in Site B. However, ProSphere does not currently report on the relationships between these disparate (federated) objects. So, the relationship data in maps and tables where relationships cross instances of ProSphere may be incomplete. All relationships within a single instance of ProSphere will be accurately reported, regardless of which ProSphere instance you are using.
Synchronization of hosts
Hosts, once added to the Synchronize Multiple ProSphere Applications dialog box, cannot be removed. Consequently, if you uninstall the ProSphere vApp from a host that is added to the dialog box, the application continues to attempt synchronization with this host without success.
UI display
Host object view page does not refresh Engineering Issue 561689
Refreshing the Host object view page does not remove the deleted host from the UI when more that 500 hosts are present in the list.
Workaround
Sorting functionality is limited in the Select Array LUNs and Select Host Devices dialogs Engineering Issue 554565
The sort functionality of the Avg IOps, Avg TP KBps and Avg RT ms columns in the Select Array LUNs and Select Host Devices dialogs may not work properly when the values in the columns are of differing sizes such as 2 and 3-digit values.
Workaround
Sorting functionality is not supported across pages in Access Credentials and Discovery Jobs Engineering Issue 521449
Sorting of a column in Access Credentials and Discovery Jobs view is effective only within a page. If the data exceeds a single page, sorting is not supported. It just sorts the items in the page.
Updates, Shut down, and Reboot

Displayed time after update incorrect Engineering Issue 566563
After completion of the update process, the displayed time of completion will be shown in GMT, and not the local zone time that may have been previously configured.
Cause
This is being investigated as a defect in the VMware software.
Workaround
Manually perform the conversion from GMT to your local time after the update.
VMware
Live Storage vMotion does not work with ProSphere in vSphere5 Engineering Issue 558818, 584054
While live Storage vMotion works with non-vApp Virtual Machines (VMs) in both vSphere 4.x and vSphere 5.x, it does not work with VMs that are part of a vApp. This is a known issue discussed in VMware Knowledge Base 2012122 which can be found at http://kb.vmware.com/kb/2012122.
Workaround
There is no workaround for live Storage vMotion. Each VM must be shutdown first before performing offline storage migration. ProSphere vApp VMs must be manually shutdown in the reverse order of the start order. VM shutdown order: 1. Collector Appliance 2. Storage Resource Manager 3. Historical Database 4. Discovery Appliance The manual shutdown procedure is: 1. Right-click the virtual machine and click Shut Down Guest. 2. Right-click the virtual machine and click Migrate. 3. Complete the steps to move the virtual machine to the destination datastore.
Wiki and help software

This section lists the known issues and workarounds related to the software supporting the wiki and the help system.
Help window may not display a second time after closing Engineering Issue 537667
Within the ProSphere Console> Admin > System > Synchronize ProSphere Applications > Add > Add Application dialog box, if you click the Help button once, then close the help topic after display, the help topic will fail to open a second time.
Workaround
Click on the Help button a third time to display the help topic.
32
Documentation Errata
This section contains content that did not make it into the books and help system before production. This content will be migrated into those documents in the next release.
vCenter misspelled in ProSphere Deployment Guide

Page 12 incorrectly states: Use only a vCetner to connect the vSphere Client to an ESX server. Attempts to deploy directly to an ESX server will fail. It should state: Use only a vCenter to connect the vSphere Client to an ESX server. Attempts to deploy directly to an ESX server will fail.
Underscores in hostnames
In the EMC ProSphere: Preparing for Deployment, Configure Hosts chapter, this information should appear as the first section:
Avoid underscores in hostnames

The Internet standards for protocols mandate that hostname labels can contain only the ASCII letters a through z (in a non-case-sensitive manner), the digits 0 through 9', and the hyphen (-). No other symbols, punctuation characters, or white spaces are permitted. If ProSphere encounters a host name with an underscore, users can be prevented from logging in. You can confirm the situation by searching the log files for the following string:
IllegalArgumentException: Host cannot be null
Launching SMC instance with array name alias

In the online help > Discovery > Objects List > To launch SMC topic > step 5 of the procedure is missing a note on how SMC Launch-in-Context behaves when an array serial number, also referred to as array name alias, is present in the link for an SMC instance. Note: If you click on an SMC instance appearing with the array serial number or alias in the drop-down list (for example, https://HK111100111:7070), an error indicating that the SMC instance is either down or not reachable occurs. To avoid this error, add the array alias name to your DNS server.
Path performance collection topic needs to mention delay in stopping action for groups
The following note is missing from the documentation: Note: When you stop path performance collection for groups, it will take few moments for the action to complete and reflect the changes in the Object List view. This note needs to be included in the following topics:
33
EMC ProSphere Administrators Guide > Resource Discovery chapter > Collect
performance data for discovered hosts on page 63. Online Help > Performance > All Alerts > To switch off path performance collection topic, the end of the second section.
Additional WS-MAN certificate import issue

The EMC ProSphere Administrators Guide, Troubleshooting chapter, WS-MAN certificate import issues section is missing this additional troubleshooting scenario occurs while adding a certificate to the listener.
HttpSetServiceConfiguration failure
While adding the certificate to the listener, you might encounter the following error:
WSManFault Message ProviderFault WSManFault Message = The function: "HttpSetServiceConfiguration" failed unexpectedly. Error=1312. Error number: -2147023584 0x80070520 A specified logon session does not exist. It may already have been terminated.
This error is generally seen when the certificate is inappropriate or has been tampered with. To troubleshoot the error, import the certificate again. Then, try to create the listener again with the thumbprint of the certificate.
Correction to procedure for disabling SSH access to virtual machines

In the EMC ProSphere Security Configuration Guide, Access Control Settings chapter, Disable SSH access to virtual machines section, sshd is incorrectly mentioned as a folder in the /etc/ directory. The correct folder name is ssh as given in this updated procedure: To disable SSH access to a ProSphere virtual machine: 1. Log into the ProSphere Linux virtual machine with the root user credentials. 2. Navigate to the folder /etc/ssh. 3. Using vi Editor, open the file sshd_config. 4. Search for the line PermitRootLogin and modify it to PermitRootLogin no. 5. Save the modified sshd_config file. 6. Execute the following command to restart the SSH daemon:
service sshd restart
Support Matrix - SMI-S Provider

Table 3 Array discovery incorrectly states that the the minimal version for the SMI-S Provider is 4.3.2.2 or higher. It should state 4.3.2.1. or higher.
34
Corrections to Support Matrix Host discovery table

The following table, indicating that WS-MAN is supported for Windows 2003 and providing the correct Emulex and QLogic HBA links, should be used rather than Table 7 found on page 7 of the EMC ProSphere Support Matrix:
Table 1
Host discovery Version 11.11 11.23 11.31 5.1 5.2 5.3 6.1 7.1 Method SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH SSH WMI/WS-MAN WMI/WS-MAN Standard Enterprise Datacenter WMI/WS-MAN WMI/WS-MAN WMI/WS-MAN WMI/WS-MAN WMI/WS-MAN Solaris 9 Solaris 10 Solaris 11 SSH SSH SSH VMware Infrastructure
Vendor HP
OS HP-UX 11i v1 HP-UX 11i v2 HP-UX 11i v3
IBM
AIX
Linux
RHEL
AS/ES 4.0 AS/ES 5.0 ES 6.0
SUSE
ES 9 ES 9.3 ES 10 ES 11
Microsoft
Windows Server 2003 Windows Server 2003 R2 SP2 Windows Server 2003 SP2 Windows Server 2008 Core Windows Server 2008 SP1 Windows Server 2008 SP2 Windows Server 2008 R2
Oracle/Sun
Solaris
VMware
VMware
4.0 4.1 5.0
35
Note: For ProSphere to discover SNIA qualified HBAs: - The HBA driver installed must be SNIA HBA API 2.0 compliant. - The vendor specific SNIA libraries must be installed on the target host. The HBA model number and part number should be verified before updating the hosts with SNIA libraries for HBA. Additional information for Emulex HBAs are located at www.emulex.com and QLogic HBAs at www.qlogic.com
Sentence fragment in EMC ProSphere: Preparing for Deployment

In the EMC ProSphere: Preparing for Deployment, Configure Arrays chapter, Requirements for discovery data collection section, the following text appears: To discover supported Symmetrix, CLARiiON, and VNX storage devices and collect resource data from them in ProSphere, the following requirements must be met:
CLARiiON SPA IP address or FQDN, CLARiiON SPB IP address or FQDN, and CLARiiON username and password.
The bullet should read as follows:
CLARiiON SPA IP address or FQDN, CLARiiON SPB IP address or FQDN, and CLARiiON username and password must be known.
Correction to Deployment Checklist

In the EMC ProSphere Deployment Guide Checklist, "Switch Considerations" section, the following information appears: Install any of the following on a separate host and discover fabrics to be managed in the SMI-S Provider before discovering it from ProSphere

Brocade SMI Agent Brocade Connectrix Manager Data Center Edition (CMDCE) Connectrix Manager Converged Network Edition (CMCNE) SNMP v1, v2, and v3 access credentials to discover Cisco switches."
This should read as follows: Install any of the following on a separate host and discover fabrics to be managed in the SMI-S Provider before discovering it from ProSphere

Connectrix Manager Converged Network Edition (CMCNE) SNMP v1, v2, and v3 access credentials to discover Cisco switches."
FHQN is a spelling error

In the EMC ProSphere Administrators Guide, FHQN appears in place of FQHN. This occurs in the following locations:

Table of contents, page 6 Appendix B: Troubleshooting, pages 111, 125
36
ESX credentials
In EEMC ProSphere: Preparing for Deployment, Hosts chapter, Discovery Requirements, section, the following text incorrectly states: ProSphere requires: Individual ESX credentials or broader VirtualCenter credentials with Browse Datastore permissions. These credentials are entered as VMware Infrastructure credentials in ProSphere. The EMC ProSphere Administrators Guide provides instructions for creating discovery access credentials. It should read as follows: ProSphere requires: Assignment of individual ESX credentials or assignment of VirtualCenter credentials. In either case, Read-only permissions must be included, with the addition of Browse Datastore permissions. These credentials are entered as VMware Infrastructure credentials in ProSphere. The EMC ProSphere Administrators Guide provides instructions for creating discovery access credentials.
Alerts are displayed even though ProSphere has not discovered CIs
The following note describing why alerts are displayed in a new ProSphere deployment, even though ProSphere has not discovered CIs, is missing from the documentation. Note: Only active alerts appear in the All Alerts view. If there are no active alerts to display, the All Alerts view will appear blank. However, occasionally alerts appear in a new ProSphere deployment on first launch, even before ProSphere discovers the CIs. This is because the IP configurations used with the new deployment is same as a previous deployment and these alerts are received from SMI-S Providers and not from the yet to be discovered CIs. This note needs to be included in the following topics:
EMC ProSphere Administrators Guide > Alerting chapter > Overview of Alert Sources
on page 50. Online Help > Operations > All Alerts > All Alerts view topic.
SNMP V2c must be V2

The EMC ProSphere Administrators Guide lists V2c as one of the SNMP versions supported by ProSphere alerting. V2c needs to be replaced with V2 in the following sections:
EMC ProSphere Administrators Guide > Alerting chapter > Table 7 - SNMP
Notifications on page 46.
EMC ProSphere Administrators Guide > Alerting chapter > Add an SNMP trap
destination on pages 47 and 48.
List of external alerts supported in ProSphere

A list of SPA and SMC (SMI-S) alerts supported in ProSphere is currently missing in the documentation.
37
This information should appear in:
EMC ProSphere Administrators Guide > Alerting chapter > Overview of Alert
Sources as a new section. Online Help > Operations > All Alerts as a new topic.
External alerts supported in ProSphere

Table 4 on page 38 lists the alerts collected from all instances of the alert sources and displayed in the ProSphere All Alerts view.
Table 4 List of external alerts supported in ProSphere Alert source SPA Source alert policy or category Array Cache Partition Disk FE Director BE Director Port Link Status RDF Director Device Group Composite Group Storage Group Disk Group RDF/A Group System Alerts (Critical Database errors only) ProSphere categorization Performance alert
38
Table 4 List of external alerts supported in ProSphere Alert source SMC Source alert policy or category Array Events SP Alerts Device Config Change Thin Device Usage Device Pool Config Change Port Link Status HotSpare Invoked CG Tripped SRDF Alerts SRDF Link Status SRDF/A Session User Approval Required For Optimize/FAST Config Change FAST Controller Switched State Optimizer Switched Mode DB Checksum Triggered GK TimeOut Thin Pool Rebalancing Complete Alert GK Utilization Deferred Service Threshold Alert Migration Complete Alert Array Component Events ProSphere categorization Health alert
SPA System alerts supported in ProSphere

In the EMC ProSphere Administrators Guide > Alerting chapter > What are native and external alerts? section has the following statement:
SPA Indicates Symmetrix Performance Analyzer (SPA) alerts consolidated directly from SPA instances.
It should read as follows:
SPA Indicates Symmetrix Performance Analyzer (SPA) alerts consolidated directly from SPA instances. External alerts supported in ProSphere provides a list of all the supported SPA alerts.
39
Technical notes
In the Online Help > Operations > External alerts in ProSphere topic includes the following statement. It needs to be removed. Except for System type alerts, ProSphere supports all SPA alerts and categorizes them as performance alerts and all SMC (SMI-S) alerts as health alerts under Operations > All Alerts.
Technical notes
Numerical values
Numerical values in ProSphere are expressed in the normal KB, MB, and GB designations. These values should be interpreted as binary in nature, not decimal. So, a value of 8 MB indicates 8,388,608, not 8,000,000.
40
Documentation library
Documentation library
The online help is available from any of the Help menus (?) within the ProSphere Console. The PDF files are linked to the main documentation landing page, available from the (? -> Search All Documentation) in the main Console. Table 5 lists the contents of the ProSphere documentation library.
Table 5 ProSphere documentation Title Description A brief summary of software that needs to be installed before ProSphere is deployed Description of supporting third-party software required for object discovery and data collection Deployment and configuration instructions for ProSphere Describes security considerations when installing and configuring ProSphere. Includes port information for setting up firewalls. Describes the range of network objects that can be discovered and managed by ProSphere Describes the open source software used in development of this product, or delivered with ProSphere Describes all of the GPL Version 3 software and licenses shipped with ProSphere Describes the ProSphere boundaries for performance times and the scale for discovery and data collection Provides a wide range of information of interest to SAN administrators about resource discovery, security, user roles, database maintenance, log files, LDAP/AD authentication, and troubleshooting
EMC ProSphere Deployment Checklist EMC ProSphere: Preparing for Deployment EMC ProSphere Deployment Guide EMC ProSphere Security Configuration Guide EMC EMC ProSphere Support Matrix Open Source License and Copyright Information Open Source License and Copyright Information for GPLv3 as Included with a Distribution of SLES 11 EMC ProSphere Performance and Scalability Guidelines EMC ProSphere Administrators Guide
Note: In the lower left corner of the Documentation Library page there are two links: Professional Services and Customer Support. These are intended as locations for these organizations to install any documents they create on your behalf. These links do not have to be used; they are there simply as a convenience.
Troubleshooting and getting help

EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, licensing, and service, go to the EMC online support website (registration required) at:
http://Powerlink.EMC.com
41
Technical support For technical support, go to EMC online support and select Support. On the Support page, you will see several options, including one to create a service request. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Logging into Powerlink

If you do not have an EMC Powerlink account, set one up by going to: http://Powerlink.EMC.com and clicking New Member Registration. Use this site to gain access to additional product resources, as well as documentation updates. Note: Allow one to two days for EMC to set up your account. You will receive a password to confirm your account has been set up.
Technical support
For technical support, go to EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC Sales Representative fordetails about obtaining a valid support agreement or to answer any questions about your account.
Commenting on the documentation

Your suggestions help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your thoughts and requests to:
ProSphere_doc_comments@emc.com
42
Copyright 2012 EMC Corporation. All rights reserved. Published in the USA. Published March 4, 2012 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.
EMC2, EMC, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Connectrix, CopyCross, CopyPoint, CX, Dantz, Data Domain, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer, EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony, Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, VMAX, VNX, VNXe, Voyence, VPLEX, VSAM-Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and the RSA logo, are registered trademarks or trademarks of EMC Corporation in the United States and other countries. Vblock is a trademark of EMC Corporation in the United States.
VMware, and <insert other marks in alphabetical order>, are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.
43

ProSphere Version 1.5 Release Notes

Загружено:

Сведения о документе

Исходное описание:

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ProSphere Version 1.5 Release Notes

Загружено:

Авторское право:

Доступные форматы

RELEASE NOTES

ProSphere 1.5 Release Notes

New features and changes

EMC ProSphere Administrators Guide, Alerting chapter provides detailed

ProSphere 1.5 Release Notes

New features and changes

Discovery and performance

ProSphere 1.5 Release Notes

New features and changes

Single Sign On and Launch-in-Context

Problems fixed in ProSphere 1.5

Problems fixed in ProSphere 1.5

633503 555390 555779 555930 558827

Discovery Performance Performance Performance Performance

ProSphere 1.5 Release Notes

Update an existing deployment

Extract files and deploy using an existing Web server

New deployment or update an existing deployment

Load files into an existing virtual CD-ROM drive

ProSphere 1.5 Release Notes

ProSphere 1.5 component builds

ProSphere 1.5 Release Notes

Known problems and limitations

Known problems and limitations

Known problems and limitations

Create Destination Details Edit Destination Details

ProSphere 1.5 Release Notes

Known problems and limitations

CLARiiON in Equalizing state will return incorrect values

ProSphere 1.5 Release Notes

Known problems and limitations

Usable Capacity includes duplicate values Engineering Issue 583663

For Symmetrix arrays:

Instead, the following two definitions should be used:

Known problems and limitations

VCMDB and ACLX devices on Symmetrix Engineering Issue 562068

Some capacity metrics are incorrectly reported Engineering Issue 557944

Known problems and limitations

Configuration Item dialog

Switch performance charts produce an error Engineering Issue 561695

ProSphere 1.5 Release Notes

Known problems and limitations

Uppercase characters cause log service to fail Issue

ProSphere 1.5 Release Notes

Known problems and limitations

EMC SMI-S Provider configuration The problem

How do I configure Symmetrix ACL?

How to determine if the EMC SMI-S Provider is configured properly

Known problems and limitations

(Expanded discussion of these points in the following SYMCLI examples section)

>symacl list -v -sid 854 S Y M M E T R I X A C C E S S C O N T R O L S T A T U S

: N/A : N/A : N/A : No : No

ProSphere 1.5 Release Notes

Known problems and limitations

Pool Name --------------------------------TestPool

ProSphere 1.5 Release Notes

Known problems and limitations

VM initial discovery fails Issue

Proper credentials required for ESX discovery Issue

ProSphere 1.5 Release Notes

Known problems and limitations

Job Execution Results: Object name missing Issue

ProSphere 1.5 Release Notes