OK, we are finally licensed to install and use VCOPS 5. Been running Cap IQ stand alone for quite some time. Not that that matters.
Question I cannot seem to find an answer to, and I'm sure it's basic, but the docs don't answer it either. We are a static IP shop in regards to server side systems. I understand IP pools. I have to request all IP addresses from our network group. No issues there at all. My issue is this. How many IP addresses do I actually NEED to set this up? Again, stupid question, but is it 2 or 3? Does the actual vapp need an IP? Or do I just need the two for the two VM's IN the vapp? Sorry, really confused on this as the only current "vapps" we use are older versions of vma's for a few different things.
Lasty, in a statis IP environment, do the two internal VM's require DNS entries etc? I would assume so, and again, need to request this when contacting our network team.
Sorry if this seems basic. Been working with ESX since the beginning, and frankly, this setup is confusing the hell out of me for some reason.:smileyconfused:
You will need 2 IPs for the 2 VMs inside the vApp, the IP pool needs to match the network setup. The existing CapIQ IPs need to stay until data conversion is completed, so after data import is done you could release those.
Hope this helps
For vAPP you need 2 IP Address. one IP is for the UI and the other IP is for the analytics VM. This needs to be configured in the vAPP settings.
You would need one internal DNS entry pointing to your UI server.
You will want DNS entries for those as well. The UI is available through the vSphere client, but when you start creating dashboards, you don't want to have everyone logging in through the client, and therefore can log on to the UI web interface directly. The analytics address should be there, but from what I recall, you switch to that view from the ui as needed.
OK - thanks all. So basically, I need two IP's and a DNS entry that points to the UI machine address for web\browser access. That helps. Wishing that basic bit of info was in the docs, but then again, I might have missed it.
The vAPP will use IP Pools within vSphere to configure DNS and Routing as you will only provide the static IP addresses for the internal VMs of the vApp. If you are using VLANs you will want to make sure you attach the IP Pool the the appropriate VLAN.