Storage Essentials Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Storage Essentials 6.3

SOLVED
Go to solution
Highlighted
SSteve
Occasional Contributor

Storage Essentials 6.3

Hi,

 

We are currently testing SE in our company. We like to see the agentless features, but scentless discovery does not show any servers. Have you faced the same problem? Do you have an idea where to start troubleshooting?

 

BR,

 

Steve

17 REPLIES
AnthonySE
Acclaimed Contributor

Re: Storage Essentials 6.3

There are naming conventions that need to be followed for the Discovery to work.

Going into the "Help" section in the Discovery page will show you various examples of rules to follow for agentless discovery.  There is also on the Discovery page, a "Test" function which can show you what possibly may be the problem with your entry.

 

How did you get SE installed?  HP Sales ?

Although I am an HP employee, I am speaking for myself and not for HP.
WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

To elaborate, the new SE 6.2/6.3  "agentless" method of inferring 'host containers' is for the purpose of storage allocation (presented SAN storage capacity) reporting (and a side effiect is the topology looks much cleaner!)

 

The setup requires that one (or more) rules are defined to parse a host name out of either the fabric zone/alias or array host securitygroup... therefore the first thing to confirm is that both fabric and arrays are fully discovered and part of ongoing data collection (GAED, or "Get Details" schedule). Then, it's a matter of identifying where in your naming convention(s) a host name is located, so it can be parsed using the user defined rules. In most cases, the fabric zone or alias will contain the host name. Using the built-in help will give you about a dozen examples of regular expressions that may apply to your environment. When the rules are run, either manually, or automatically after GAED, SE will attempt to perform a fwd and reverse nslookup of the hostname (based on the DNS server for the SE CMS) and determine if any hosts can be resolved. If so, we will take the generic fabric switch placeholders (aka "discovered hosts") which are seen as Host_##### with a "?" in the SE System Topology, group them accordingly, and include the IP Address and FQDN to these objects. If you then drill in to the object, there will be a "Presented Storage" tab that will show the total presented SAN storage (sum of array LUNs presented to the WWNs) for the inferred host.

 

SE 6.3 also provides a new 'named generic host' option, for the cases where a host name cannot be parsed for a given system. In this case, you would simply manually group the generic switch placeholders (right-click) and then edit the default name "Host_#####" of the generic object (typically supplying the actual host name, though not required)... and like the above scenario, we will then provide the "Presented Storage" tab with the total allocated storage capacity to those WWNs. The inferred host method is preferred as it can provide an automatic correlation based on the rules, and when set to run after scheduled GAEDs it will assure that the generic placeholders fond on the fabric are grouped and named accordingly without need for continued user interaction.

 

Assuming your fabrics and arrays are fully discovered, and you have defined a GAED schedule, and have a naming convention which can be parsed... use the included examples and test functionality to determine if the rules and regular expression is working propery.

 

Also note that there are a number of other "agentless" methods used in SE today, including the agentless discovery of VMware via ESX or VC, Solaris Zones/Containers, and use of WMI to gather limited details for Windows hosts (WMI does not include HBA discovery, so these hosts will not show SAN storage relationship details, topology stitching, or other agent (SE CIM Extension) based capabilities such as cluster detection, multi-path visibility, application/db discovery, file system viewer support, etc.

 

See the SE 6.3 "Agentless whitepaper" on hp.com/go/srm for more detials:

https://h10078.www1.hp.com/cda/hpdc/navigation.do?action=downloadPDF&caid=44532&cp=54_4000_100&zn=bto&filename=4AA0-4501ENW.pdf

 

 

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Thanks for the reply!

 

I managed to identify many hosts by agentless discovery. Could you please write a bit more about WMI discovery? How can it be setup and used?

 

Thanks in advance!

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

Hi Steve,

 

So, to be clear, you used the SE 6.2/6.3 "agentless inferred" option successfully to remap the generic host WWNs using rules? And you are also interested in using WMI "agentless" discovery? Just to note that these are completely separate methods, the former does not communicate with the host server, only infers a host object, and provides the capacity of SAN presented storage to grouped generic containers in SE. The latter (WMI) is direct communication from the SE CMS to Windows servers, performing aspects of discovery and data collection via WMI, resulting in a managed host object (and consuming 1 MAP license per system) - with _some_ host details related to capacity and performance utilization at the host level, but not any HBA discovery or SAN relationships. And, that the "agentless inferred" and "agentless WMI" will not merge or reconcile data for a given system if both are used in conjunction - you will have a "stitched" inferred host container with presented storage in the topology - with the name/IP address in our reports and also a duplicate WMI discovered host object that "floats" in the topology with some ability to drill down into utilization details for the system.

 

There is no setup required for WMI discovery - it's enabled by default via the property under Configuration > Product Health > Advanced > Custom Properties... Default Properties:

discovery.exclude.Win32Provider=false 

And all you need to do is use Discovery > Setup > Step 1, add an entry for a Windows server, and use an account that has rights/permissions to access WMI (Administrators have this as a default).

My best practice recommendation is to disable SE's WMI as it tends to confuse matters for most environments and lacking FC HBA and SAN relationship details while costing 1 MAP each tends to lend minimal value-add (and for that matter, other providers that pertain to systems not in a given environment). The exception to this for WMI would be in an SE/P4000 (LhN) iSCSI environment, as in that specific case, the WMI provider can return iSCSI details and relationships - so w/o installing any instrumentation (SE CIM Extension/CXWS Host Agent) on the server, you can provide end-to-end mapping for WMI hosts to the P4000 device.  And example of how to customize the default properties do disable providers here (note: SE will completely ignore the disabled providers, so if you later add a device, you would need to modify the custom properties before SE would be able to probe and discover them.

 

Default:

#Disable testing of certain internal providers to speed up step 1 discovery.exclude.Win32Provider=false discovery.exclude.CxwsProvider=true discovery.exclude.SunDotHillProvider=true discovery.exclude.CiscoSNMPProvider=true #discovery.exclude.LSISSI_Provider=false #discovery.exclude.HdsProvider=false #discovery.exclude.ClariionProvider=false #discovery.exclude.EmcProvider=false #discovery.exclude.NetAppFilerProvider=false #discovery.exclude.HPEVA_Provider=false #discovery.exclude.VCProvider=false #discovery.exclude.CelerraProvider=false discovery.exclude.CenteraProvider=true 

 

Custom example for an environment consisting of Brocade Fabric, HP EVA, HP XP, VMware, and discovery of managed hosts with CIM Extensions (not WMI) - excluding WMI, LSI, EMC and NetApp discovery.

 

#Disable testing of certain internal providers to speed up step 1 discovery.exclude.Win32Provider=true discovery.exclude.LSISSI_Provider=true#discovery.exclude.HdsProvider=falsediscovery.exclude.ClariionProvider=true discovery.exclude.EmcProvider=true discovery.exclude.NetAppFilerProvider=true#discovery.exclude.HPEVA_Provider=false
#discovery.exclude.VCProvider=falsediscovery.exclude.CelerraProvider=true

 

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Hi Wiley,

 

Thank you so much for the detailed answer!

 

I have an other question / problem:

 

I try to discover XP storages. If I try to connect them via Command View XP machine , the XPs are getting discovered. I heard that it is better to use the built-in provider for SE for connecting to XPs. Based on the manuals I give the IP of one of the XPs and the credentials, but only the HDS Provider part seems to discover something. Log is pasted below.

Do I need additional components on the XP storage or on SE?

 

Thank you in advance!

 

 

[2011-02-09 09:18]    Test Discovery Started
[2011-02-09 09:18]    
ping -w 1000 -n 3 XX.XX.XX.XX


Pinging XX.XX.XX.XX with 32 bytes of data:



Reply from XX.XX.XX.XX: bytes=32 time<1ms TTL=128

Reply from XX.XX.XX.XX: bytes=32 time=595ms TTL=128

Reply from XX.XX.XX.XX: bytes=32 time=-847ms TTL=128



Ping statistics for XX.XX.XX.XX:

    Packets: Sent = 3, Received = 3, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 0ms, Maximum = -847ms, Average = 1431655681ms


[2011-02-09 09:18]    XX.XX.XX.XX: Probing for SMI-S Server (cxws)
[2011-02-09 09:19]    cxws://XX.XX.XX.XX: No response received
[2011-02-09 09:19]    XX.XX.XX.XX: Probing for SMI-S Server (https)
[2011-02-09 09:19]    https://XX.XX.XX.XX:5989: No response received
[2011-02-09 09:19]    XX.XX.XX.XX: Probing for SMI-S Server (http)
[2011-02-09 09:20]    http://XX.XX.XX.XX:5988: No response received
[2011-02-09 09:20]    
Origin: XX.XX.XX.XX: 
User: administrator

FAILED as Win32Provider for: XX.XX.XX.XX
   Failed.  Return code value unknown. 0
Failure type is other


Origin: XX.XX.XX.XX: 
User: administrator

FAILED as LSISSI_Provider for: XX.XX.XX.XX
   Failed to establish connection.

Origin: XX.XX.XX.XX: 
User: administrator

FAILED as EmcProvider for: XX.XX.XX.XX
   Can't connect
   SymInitialize() failed with error code 515 (A remote send or receive operation failed)

Origin:
XX.XX.XX.XX: 
User: administrator

FAILED as LHNProvider for: XX.XX.XX.XX
   Can't establish communication with device

Origin: XX.XX.XX.XX: 
User: administrator

FAILED as NetAppFilerProvider for: XX.XX.XX.XX
   Can't establish communication with filer

Origin: XX.XX.XX.XX: 
User: administrator

FAILED as ClariionProvider for: XX.XX.XX.XX
   NaviCLI not installed

Origin: XX.XX.XX.XX: 
User: administrator



SUCCESS as HdsProvider for: XX.XX.XX.XX
   Connection OK
   Connected to storage array 75174 (XP24000) using RMI



Origin: XX.XX.XX.XX: 
User: administrator

FAILED as HPEVA_Provider for: XX.XX.XX.XX
   EVA discovery determined that we should use the external SMI-S provider

Origin: XX.XX.XX.XX: 
User: administrator

FAILED as VCProvider for: XX.XX.XX.XX
   Cannot connect as Virtual Center Host or ESX Server Host

Origin: XX.XX.XX.XX: 
User: administrator

FAILED as CelerraProvider for: XX.XX.XX.XX
   Can't discover Celerra Server XX.XX.XX.XX
   FAILED

[2011-02-09 09:20]    Test Discovery Completed
Test Discovery completed in 1 minute 47 seconds 

 

WileyThrasher
Regular Collector
Solution

Re: Storage Essentials 6.3

Hi,

 

We don't use SMi-S, so ignore anything related to :5989 and anything else not related to the HDS provider in context.

 

And if you have already discovered the XPs via CV AE using the XML-API... you would have to delete from SE Setup Step 3 prior to using the direct discovery method, as we will ignore duplicates.

 

HDS provider shows success... using our built-in provider against the SVP (our RMI-API)

 

SUCCESS as HdsProvider for: XX.XX.XX.XX
   Connection OK
   Connected to storage array 75174 (XP24000) using RMI

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Hi,

 

Great, thanks!

 

Are you also familiar to reporting also?

 

In capacity manager part I have to select "Unallocated-RAID-5" to see the real free space (we use raid-5). This is OK. But If I would like to report it, on a "Storage System Capacity" report I only see the pre raid raw capacity. We have also report optimizer, but I haven't found the post raid information among the parameters... Is it possible to report the real (post raid) free usable space per storage??

 

 

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

Hi,

 

The pre-raid/post-raid views calculations in were instrumented directly in the SE Capacity Manager GUI and do not yet have equavalent reports in SE Reporter (Report Optimizer)... possible to build a custom report that would use the same (or additional) formulas, but not something we have out-of-the box yet today.

 

I'll ask around if this is something we're planning for a future release.

 

Wiley

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

Hi,

 

Just to confirm... you're referring to the SE Capacity Manager GUI for EVA which offers an hard coded on-the-fly break-down of post-raid capacity per a drop down list for RAID selection (0,1,5, 6)... using factors of 1, 2, 1.25 (5/4), and 1.5 (3/2) respectively.

 

Was the context of my answer, as this feature is unique to the EVA.... and your previous question was on XP for which there is no equavalent option in SE Capacity Manager.

 

 

 

 

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Hi,

 

Thanks for all the help!

MY previous questtion was related to EVA. It would be nice to see the post raid-5 capacity in reports, but I understand that it is not on the map now.

 

A discovered some warning / error messages at step3 detail discovery. See attached. Could you please give a quick look at it? Maybe it is just a minor issue.

 

Thanks in advance!

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

Hi,

 

Can you provide some additional detail about this environment:

 

1) What are the specs of the CommandView EVA server?

OS:

  Mem:

CPU:

CV Version:

 

2) Appears you have 3 EVAs currently managed by this instance, are there any other CV EVA servers in the environment?

 

3) Are there any other layered applications running on the CV EVA server? (EVAperf, RSM, CLX, CVTL, DP, etc)

 

 

My best guess is that the CV EVA server is one of the older g2 appliances, and may have insufficient system resources to handle the current configuration, would be suggested to see if there were another server that could take over management for these arrays.

 

Wiley

 

 

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Hi,

 

Sorry for the late answer...

 

1,

DL385 G2, AMD Opteron 2,4, 4 cpu

OS: Windows 2003

MEM: 4GB

CV: 9.2

 

2, yes we have 20 EVAs, managed by 3 CV (different sites)

 

3, I don1t know about them

 

Your guest was right, it is a G2 server...

 

What do you suggest? Increase the memory amount?

 

BR,

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

Hi,

 

I'm guessing you're running right on the edge of this systems performance based on the current configuration (# of arrays, #  of objects per array, and combination of layered apps)  hard to say w/o deper analysis which resource is becoming saturated - it could be RAM, but possibly an internal resource like WMI buffers ...so a first simple step might be to look at if there are any unnecessary software services and applications running that could be disabled - for example, the Storage Essentials Host Agent (CIM Extension) is not required for EVA discovery - and could be uninstalled (if it were there - AppStormWin32Agent). If there are other 3rd partry apps such as other device managers or proxies (CommandView Tape Library, Brocade SMI-Agent, or similar) you could look at moving these to another server.

 

And second, to see if a reboot of the CV server, waiting about 15-20 minutes, and then re-running a SE Data Collection encounters the same error messages persist - if so, then you might be OK with adding a reboot (weekly, or bi-weekly?) to the CV server to free up the resource contention.

 

Since you mention 20 EVAs on 3 CV servers, and this system has only 3 arrays - it would probably not be an option to change management to another server. With the newer generation of servers, we've seen that they can typically cover ~8 EVAs with a comparatively high # of objects  while servicing multiple layered applications... where the older servers would tap out a bit earlier, when factoring layered application access (where CV itself seems OK, but external applications might be impacted to some degree).

 

Just putting some options out here for you to look at, and would suggest that opening a support case to assist in analysis might be a good next step if you're unable to make progress.

 

Hope this helps!

 

Wiley-

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

Hi,

 

thanks for the tips, I try to check the out.

 

On other CV server we dound other errors:

 

Some lines from the logs:

 

[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_diskportscsiprotocolcontroller.creationclassname=\"HPEVA_DiskPortSCSIProtocolController\",deviceid=\"PAFUCB49SY901S.looppair1loopb\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"14080710804301609CAADE050050000000001F05\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_diskportscsiprotocolcontroller.creationclassname=\"HPEVA_DiskPortSCSIProtocolController\",deviceid=\"PAFUCB49SY901S.looppair2loopa\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"12080710804301609CAADE05005000000000A503\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_diskportscsiprotocolcontroller.creationclassname=\"HPEVA_DiskPortSCSIProtocolController\",deviceid=\"PAFUCB49SY901S.looppair2loopb\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"0A080710804301609CAADE050050000000007602\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"0E080710804301609CAADE050050000000008802\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"0F080710804301609CAADE050050000000008902\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_viewprotocolcontroller.creationclassname=\"HPEVA_ViewProtocolController\",deviceid=\"11080710804301609CAADE050050000000009802\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE150242010\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"59400710804301601F79DE0500C0000000008202\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"6E400710804301601F79DE0500C0000000004803\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"35400710804301601F79DE0500C0000000000C02\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"93400710804301607E78DE0500A0000000005F00\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"4D400710804301601F79DE0500C0000000004602\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"85400710804301607E78DE0500A0000000000800\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""
[2011-04-07 16:53]    https://swma2:5989: ERROR computing device membership for: ":hpeva_storagevolume.creationclassname=\"HPEVA_StorageVolume\",deviceid=\"2A400710804301607E78DE05009000000000DA00\",systemcreationclassname=\"HPEVA_StorageSystem\",systemname=\"50001FE15023DCE0\""

 

As a result of this eg. one of the 4 EVAs managed by ths CV is not doscovered.

 

Have you seen something similar?

 

Regards,

 

Steve

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

I'd get a support case opened via the SSO portal... hard to suggest what partiular issue you're hitting. Based on the errors for that device, I would not expect it to be visible in SE - troubleshooting would focus on the CV server, SMI-S, and the array reporting errors.

 

http://support.openview.hp.com/casemanager/incident-index

 

 

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
SSteve
Occasional Contributor

Re: Storage Essentials 6.3

I will do so, thanks.

 

I discovered that after discovery step 1 I get the following warnings:

 

[2011-04-08 15:04]    Discovery Started
[2011-04-08 15:04]    swma2: Probing with Win32Provider
[2011-04-08 15:04]    swma2: Probing with EmcProvider
[2011-04-08 15:04]    swma2: Probing with LSISSI_Provider
[2011-04-08 15:04]    swma2: Probing with CelerraProvider
[2011-04-08 15:04]    swma2: Probing with VCProvider
[2011-04-08 15:04]    swma2: Probing with HPEVA_Provider
[2011-04-08 15:04]    swma2: Probing with HdsProvider
[2011-04-08 15:04]    swma2: Probing with ClariionProvider
[2011-04-08 15:04]    swma2: Probing with NetAppFilerProvider
[2011-04-08 15:04]    swma2: Probing with LHNProvider
[2011-04-08 15:04]    swma2: Probing for SMI-S Server (cxws)
[2011-04-08 15:04]    swma2: Probing for SMI-S Server (https)
[2011-04-08 15:04]    https://swma2:5989: DISCOVERED SMI-S Server for HP EVA
[2011-04-08 15:04]    WARNING: While processing address: https://swma2:5989 found a stranded element,
                      element name is MKB_EVA13, element id  is 259775, element address id is 251234.
[2011-04-08 15:04]    https://swma2:5989: FOUND HPEVA_StorageSystem 50001FE15023DD00
[2011-04-08 15:04]    WARNING: While processing address: https://swma2:5989 found a stranded element,
                      element name is MKB_EVA16, element id  is 259776, element address id is 251234.
[2011-04-08 15:04]    https://swma2:5989: FOUND HPEVA_StorageSystem 50001FE150242020
[2011-04-08 15:04]    https://swma2:5989: FOUND HPEVA_StorageSystem 50001FE150242010
[2011-04-08 15:04]    https://swma2:5989: FOUND HPEVA_StorageSystem 50001FE15023DCE0
[2011-04-08 15:04]    Discovery Completed
Discovery completed in 27 seconds 

 It is a bit strange for me that two defices share the same "element address id"...

WileyThrasher
Regular Collector

Re: Storage Essentials 6.3

I'd guess that the element address id refers to the CV server address (since it's proxy for multiple devices, would be the same for all the elements behind it)

Wiley Thrasher
Storage Management Expert
HP Storage TCE and Quality Tiger Team
WW L3 Pre-sales Support
Hewlett-Packard Company
//Add this to "OnDomLoad" event