As stated by Illvilja above. If the VM starts using more than the host can provide it will start swapping memory which has a very noticeable performance impact. I would push this as hard as you ...
See more...
As stated by Illvilja above. If the VM starts using more than the host can provide it will start swapping memory which has a very noticeable performance impact. I would push this as hard as you can for approval as the performance impact can be dramatic + the more RAM you have will allow you to future proof in case you need to add another VM or two in there. Thanks, Jake
I don't see a problem with it although I have not tested. I upgraded IS, Webclient, SSO, vCenter etc all in one. Worked a charm. Could have just done the SSO to resolve the SSO problem I had bu...
See more...
I don't see a problem with it although I have not tested. I upgraded IS, Webclient, SSO, vCenter etc all in one. Worked a charm. Could have just done the SSO to resolve the SSO problem I had but did all services and working ok.
I agree with the posts in here. I've tried multiple times to use the web client and everytime I just get sick of it, due to it being so slow and finding things in there is a pain. Obviously im ne...
See more...
I agree with the posts in here. I've tried multiple times to use the web client and everytime I just get sick of it, due to it being so slow and finding things in there is a pain. Obviously im new to it, but from using the c# client to the web client, it is a lot more difficult to pick up. My decision to do the VCP510 over the VCP550 was purely based on me not using the vSphere web client for my training etc. I will be doing my VCAP-DCA soon and will be doing the 510 version aswell if possible. If that gives you any idea how much of a pain in the @ss it is. Hopefully the next release of the web client blows the old out of the water. Forcing people to migrate to the web client is a shit business decision as everyone agrees. On the + side. I love vmware and the customer support but vsphere client gets a 0/10 from me.
As stated above. In the first screenshot the username is wrong. Also secondly I have seen an issue kind of similar to this before, providing you correct the username error and are still unable...
See more...
As stated above. In the first screenshot the username is wrong. Also secondly I have seen an issue kind of similar to this before, providing you correct the username error and are still unable to login. Confirm that the virtualcenter server service has started correctly. This would cause the issue where you can login to the vSphere webclient but are unable to see any listed vcenter servers.
Personally I would not do this unless it was a high risk environment and willing to pay the consequences for extra management / overhead. Previously when I have added DMZ VM's to a cluster I wil...
See more...
Personally I would not do this unless it was a high risk environment and willing to pay the consequences for extra management / overhead. Previously when I have added DMZ VM's to a cluster I will have a setup like the following: All these are for DMZ use only; - Physical Switch - At least one physical NIC in each host for DMZ use only - Dedicated DMZ vSwitch / VM port group on each host - Configure a static access port for your DMZ VLAN on the physical switch port Here's a screenshot of how it was setup. Isolation is key in my opinion.
The easiest / simplest way would be to have it setup like you currently do. 3 different vSwitch's and configure nic teaming. I would configure VLAN's aswell for best practice / to divide the n...
See more...
The easiest / simplest way would be to have it setup like you currently do. 3 different vSwitch's and configure nic teaming. I would configure VLAN's aswell for best practice / to divide the network traffic apart properly.
I believe it can be a straight forward upgrade from 5.1 to 5.1 update 2. (This is not from experience, just reading). here is a link to the release notes: vCenter Server 5.1 Update 2 Release N...
See more...
I believe it can be a straight forward upgrade from 5.1 to 5.1 update 2. (This is not from experience, just reading). here is a link to the release notes: vCenter Server 5.1 Update 2 Release Notes
I agree with the above posters. If your physical switch supports VLAN's configure a trunk port and do the VLAN tagging on the vSwitch's on your hosts. Like said above, this will save you having...
See more...
I agree with the above posters. If your physical switch supports VLAN's configure a trunk port and do the VLAN tagging on the vSwitch's on your hosts. Like said above, this will save you having a dedicated physical uplink for every subnet. goodluck.