I am in the process of building a new vCenter environment, we are currently waiting on IPs and patch ports from our networks team but I would like to 'if I can' start building the vCenter server for this environment, it is going to be a virtual server.
We have a test environment in place at the moment which we have a shared iscsi datastore which once the environment has been build we can remove from inventory and re-add to the new environment once complete.
Can anyone see any issues with IP addressing if I build the server with a temp IP then import to my new environment then change the IP?
Yes,
As you said you have a DB server as physical which will not change even if you are going for production.
So, all you required
1) SSO -- For SSO db if you are using existing DB for that then tha'ts fine, but if you are planning to have additionnel server for DB, there you will find difficulty
2) SQL server for VC - As you said you are using existing DB.. Thats fine
3) Installing vcenter and inventory server..you reqire to have SSO server details. If you are using IP convention for installing VC, there you will find difficulty, where you need to uninstall VC and Inventory services.
Regards,
Sachin Bhardwaj
Hi,
one hint if you have connected hosts to your vcenter server.
Frank
Which version of vCenter?
vCenter 5.5 update 1c
Are you planning to put everything (SSO, Inventory Service, Web Client, vCenter) on the same server?
Yes the only thing which will be on a different server is the database, everything else will be installed on the virtual server.
My plan as we are in the process of building the environment was to:
Are you going to export the database from your 2012 Test SQL Farm to a new Farm ?
Changing ip's and databases may be tricky.
May be easier to just do an uninstall and re-install once you have the new ip on the vCenter. I have done an uninstall and re-install several times when a component changes. It is much easier to do that, than try to track down every file that needs to be changed or try to figure out why something is not working.
Sorry there maybe abit of confusion, we are keeping our current test environment and this vCenter server will be for an additional license we have (Essentials plus) which we are not using, so our current test infrastructure will be staying in place. I thought I could just get ahead of the game by building the vCenter server within our current environment and migrating via datastores (Remove from inventory) (Add to inventory across our shared datastore.
Our database server is a physical SQL box... so the DB would remain in the same place, it is just the vCenter server IP which would change
Yes,
As you said you have a DB server as physical which will not change even if you are going for production.
So, all you required
1) SSO -- For SSO db if you are using existing DB for that then tha'ts fine, but if you are planning to have additionnel server for DB, there you will find difficulty
2) SQL server for VC - As you said you are using existing DB.. Thats fine
3) Installing vcenter and inventory server..you reqire to have SSO server details. If you are using IP convention for installing VC, there you will find difficulty, where you need to uninstall VC and Inventory services.
Regards,
Sachin Bhardwaj
Thank you, in this case I will hold fire until we have our first ESXi host setup and then build the server
