Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2811

July 10th, 2012 00:00

ProSphere .ovf file is not working

Hello,

I am trying to install prosphere from .ovf file downloaded from  https://community.emc.com/docs/DOC-15851

Any idea what is wrong.

Thanks,

Kapil

233 Posts

July 23rd, 2012 03:00

Hi Kapil,

When creating the discovery job for the DMX arrays the IP you have to enter is the IP of the EMC SMI-S Provider host.

Also for the access credential the username/password is the username and password of the SMI-S agent which will be the default unless it was manually changed.

The ProSphere Deployment Guide and Administrator Guide will provide additional details information on how to discover arrays in ProSphere. These are available here  https://support.emc.com/products/15995 and within the UI "?" > "Search All Documentation"

Ensure you can see the array in question listed for the SMI-S agent. Log in to the TestSmiProvider tool for the SMI-S Provider and run the dv command this will show all the arrays the agent is currently managing.

 

C:\Program Files\EMC\ECIM\ECOM\bin\TestSmiProvider.exe or /opt/emc/ECIM/ECOM/bin/TestSmiProvider

Regards

Conor

July 10th, 2012 00:00

i got the answer, my cluster is not DRS enabled.

July 11th, 2012 01:00

Hello all,

Its like I am crawling here, somehow I managed to install vApp and now I am not able to get login prompt for the proSphere, I am trying to access from the IP address

https:

Can someone please help.

Thanks,

Kapil

15 Posts

July 11th, 2012 13:00

Hi Kapil,

So DRS is a requirement to deploy Prosphere on an ESXi 5.0 cluster?

Thanks!

Caio

July 11th, 2012 19:00

We do not have ESX5i but 4.0 yeh for sure....

Anyone can please tell me how to access prosphere login page, I have deployed vApp and its not working after that.

Kapil

472 Posts

July 11th, 2012 23:00

Hi Kapil,

I see that you have SR48942608 with Customer Support for this issue.

Regards,

Seamus Coffey

Customer Support Services (CSS)

July 23rd, 2012 00:00

Hi Seamus,

Yes I opened the case and solution provided was to reinstall the vAPP, which actually resolved the problem.

I have one more query,

How can I discover a DMX box, what to fill in IP range when I create a discover job.

I have completed all the prerequisute but not able to discover the DMX

SMC has prosphere role

SPA is installed

SMIS is latest

Thanks,

Kapil

July 23rd, 2012 19:00

Thanks Conor,

that helped but seems like I need help in every step for any EMC product , i had bad experience with ECC before.

now I have another problem with Namespace with TestSmiProvider.exe I can see DMX only with namespace root\emc and I can not see that option in prosphere.

Any idea what is going wrong in here...

Thanks a Ton,

Kapil

233 Posts

July 24th, 2012 01:00

Hi Kapil,

This is correct selecting the interop options within ProSphere will do for the Interop Namespace and is the recommended namespace. It will pick up the information from root\emc from the S-SMI Provider. Review the online help for more details.

Did the DMX fully discover in ProSphere when the discover job was run?

If you continue having issues please open an SR for each issue using either the "Join Live Chat" or "Create Service Requests"  options from https://support.emc.com/

Also if possible on this forum please open new posts for any new issues you encounter and not just add to this post.

Regards

Conor

July 24th, 2012 01:00

Thanks Conor,

I would open a SR, anyways I use interop and DMX was not discovered, it says there might be some problem with access credentials.

Thanks,

Kapil

233 Posts

July 24th, 2012 02:00

Hi Kapil,

Ensure the Username and password used is that of the SMI-S agent and not the SMI-S host.

The default user name and password of the SMI-S agent is the following

Username: admin
Password: #1Password

Confirm from a host on the same subnet of ProSphere you can connect/reach the ecom service for the SMI-S agent

http://< Provider IP>>:5988/ECOMConfig

Login with the SMI Provider access credentials when prompted (these are the same details used in the access credentials window in ProSphere)

If the browser fails to connect/display the login page from http://< Provider IP>>:5988/ECOMConfig ensure if a firewall is in place between ProSphere and SMI-S agent host that the port 5988 is opened. Restart the ECOM service on the SMI-S host to ensure it running correctly.

If you have no issue with connecting to http://< Provider IP>>:5988/ECOMConfig and the access credentials are correct open an SR with support

 

Regards
Conor

No Events found!

Top