Link to home
Start Free TrialLog in
Avatar of Jay555
Jay555Flag for United States of America

asked on

VMware Host IP versus Gusts IP

I am going to setup the 1st VMware host for handling a few Microsoft gust servers. I was wondering if I could give 192.168.1.1 to the VMware host and 192.168.0.X for the windows 2008 servers to be installed on the VMware Host. If so, is there any safety benefits? should I I use a totaly different network for VMware Host and it's guests?

Thanks
SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
All the hosts and guests in our environment are all on the same subnet. The main reason to not do this is to create some kind of sandbox environment for testing.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jay555

ASKER

I am not currently using VLAN, but may use it in the near future.
My current individual servers are set up like:
First Server:      192.168.0.2
Second Server: 192.168.0.3
Third Server:      192.168.0.4
The subnet mask is 255.255.254.0
Because of what I just explianed above, if I use 192.168.1.1 for VMware Host, I gues  I won't have any problem for VCenter and other things.
Please advise if I am correct and it is not going to give me any headache for Vcenter, and future setup of VLANs.

Thanks
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Can I ask why you would like to complicate the network?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jay555

ASKER

The reason to slightly different IP for the vmware host is possibly a little hacker freerer, if may say that. I should add that I have a good firewall appliance for whole network.
I have Cisco layer 3 switches, but haven't set up VLAN yet. All the switches are on VLAN1 for same network
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
is this system going to be in a DMZ?
Avatar of Jay555

ASKER

No, it will be behind the firewall
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jay555

ASKER

I do not have much experience with VMware, except a simple VMware vsphere 4.1 free version I installed on one host at my home.
I think it is better for me at this time to keep the VMware 5.0 instaaltion at work simple. Right now I only have one new HP DL 385 G7 with 2 NICs. The final plan is to have 3 Hosts (2 for HA onsite and the 3rd one at a remote site for Disaster Recovery).
I am the only IT person to take care of everything.Although I have replaced all the outdated Cisco swiches with Layer 3 Gigabit ones, but all of them  (8 Switches)are running on default configuration (Vlan1). I understand I can use 192.168.1.1 for my new HP VMware host while my network clients and windows servers could continue having 192.168.0.X. As I mentioned before the subnet mask is 255.255.254.0.
I assume I won't need to create different VLANs on the Cisco Switches at this time.  
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
keep it simple and use the same address range with no vlans.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Jay555

ASKER

Thanks Tech Eng and Hanccocka