Posted on 10. Jan, 2013 by in EMC Install Guides, EMC Related, StorageResourceManagement.

 

 

Hopefully you had a chance to review my “How to install ProSphere” blog post and areProSphere-ICON now ready to continue adding more discovery objects into ProSphere to get a larger overview of your environment.  The next object we will be adding is our VMware vSphere infrastructure.  This will get us one step closer to a true, end-to-end view of your environment as seen by ProSphere. 

So, let’s get this started !

First things first, let’s login to ProSphere.  

1. Once you log in, go to Discovery and then click on Access Credentials and then click “Create Access Credentials”.

40 - lets setup vcenter

2. From the drop down menu, select VMware Infrastructure.

41 - create new access creds for vCenter

3. Now, simply label your credentials and enter in vCenter’s admin/password as well then click Okay.

42 - enter in your vCenter creds

4. Now, just like we did with the VNX, we need to create a Discovery Job, so click on it and then create a job.

43 - Create Discovery Job

5. Select Hosts, and then enter in the IP address of the vCenter Host into the box.44 - Enter in vCenter Creds

6. Next step is you need to add the newly created vCenter Access Credentials to this job, so select them and add it.

45 - select your vCenter Creds and click Add All

7. Now click on Finish.

46 - click Finish

8.Now you are back at the discovery jobs area, notice that the job has never run so let’s run it.

47 - lets run this now

9. Select the job, and then click RUN and watch the log below for the “Success” results.  If you run into an issue, check your credentials and make sure the username/password are correct.

48 - Discovery Completed

10. Now, let’s see what we’ve collected. – Click on Objects and you should see all the VM’s and vSphere hosts in your environment.

40 - lets explore what we can see

11. Let’s drill a little further down. In my case, I’m going to select Lotus (Physical vSphere Host).  I can see it’s IP address, I can also see the multipathing software as well as the OS version, CPU and memory info.  Pretty cool, but let’s go a little deeper.

70 - vCenter - Lotus - Attributes

 

12. If you click on Path Details we can get more info on how we are connected into the array.

71 - vCenter - Path Details

13. If you click on VM’s you will get a list of the Virtual Machines currently running on that host, as well as info on the amount of memory they are consuming and IP address info etc.

72 - vCenter - VMs

14. If we click on Connectivity we can see the physical connectivity and the info we can grab from it.

73 - vCenter - Connectivity

15. Let’s skip over performance, (i;’ll be blogging about it later) and choose Capacity. You can see more information on what Pool the host is using etc. 

75 - vCenter - Capacity

 

So there you have it, in my first blog we installed and setup ProSphere 1.7, we added in our VNX and in this blog I take you through adding your VMware Infrastructure into ProSphere. 

In my next blog post I’ll take you through collecting the fabric switch information.  Once we get that squared away, We will have true, end-to-end topography view of this environment as well as end-to-end performance collecting.  Stay tuned !

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Facebook Twitter Linkedin Email Snailmail

4 Responses to “How to collect VMware info in ProSphere”

 
  1. [...] vTexan – How to collect VMware info in ProSphere [...]

  2. Anonymous says:

    [...] How to collect VMware info in ProSphere Popular postsHow to setup your first Desktop Pool in VMware View 5How to install configure and deploy VMware View 5 on vSphere 5 [...]

  3. Anonymous says:

    [...] Anonymous says: January 10, 2013 at 9:44 am [...]

  4. [...] vTexan – How to collect VMware info in ProSphere [...]


Leave a Reply


 

wordpress visitors
The opinions expressed here are my personal opinions. Content published here is not read or approved in advance by EMC and does not necessarily reflect the views and opinions of EMC nor does it constitute any official communication of EMC.