JedwardsUSVA's Posts

No it just allows you to add those servers to VCenter.  They just have to be removed from the old one.  
Where does the boot fail? Can you get into safe mode?
Do you really want the resolution that high?  If I were you, I would knock that down to 1024x768 and call it a day.  If you need to access the machine full screen, just RDP in.  It's always bette... See more...
Do you really want the resolution that high?  If I were you, I would knock that down to 1024x768 and call it a day.  If you need to access the machine full screen, just RDP in.  It's always better than the VM Console.
Oh an one more thing, FCoE is the best option if you got the dough!
Hands down, I would go with FC.  iSCSI works fine, but FC will be far more reliable and faster if you can go with 2 x 4 Gbps FC HBAs.  If you go that route, you probably won't have to worry about... See more...
Hands down, I would go with FC.  iSCSI works fine, but FC will be far more reliable and faster if you can go with 2 x 4 Gbps FC HBAs.  If you go that route, you probably won't have to worry about I/O.  8 Gpbs is available for a little more $.  If you are on a tight budget and can't get 2 HBAs, then iSCSI will do the trick, just not as well.  
While there are many ways of doing this, here is the method I personally prefer as it doesn't require using converter. Point your new vCenter 5 instance to the 3.5 licensing.  Go to Administr... See more...
While there are many ways of doing this, here is the method I personally prefer as it doesn't require using converter. Point your new vCenter 5 instance to the 3.5 licensing.  Go to Administration>vCenter Server Settings.  Under Licensing>License Server, enter the name of your 3.5 vCenter server.  Should look something like 27000@myoldvcenter.mydomain.com Configure your old LUNs and vSwitches on the new ESX hosts In the old VIC, remove your ESX 3.5 hosts from any clusters then disconnect them from the 3.5 vCenter. Add the old ESX hosts to the new VCenter VMotion your VMs to the new ESX hosts.  At this point your are still left with old 3.5 VMs and VMFS. Next steps will require brief downtime depending upon the size of your VMDKs.  Do a "hardware upgrade" on the VMs and reboot them VMOTION Storage to new LUNs with new VMFS Done! Gotcha's to watch for while migrating: New MAC Addresses (if you use converter or other methods) When VMotion as described above, you may have to edit each VM to update the network settings especially if you are moving to a distributed switch If your ESX 3.5 hosts are unstable and/or you don't remove them from your old clusters prior to disconnecting them, they may crash
I would commit two for iSCSI and use VLANs to break up the other 4 into a single vSwitch with VLANs for your internal network, VMKernal (if you have a separate management network), DMZ, and VMoti... See more...
I would commit two for iSCSI and use VLANs to break up the other 4 into a single vSwitch with VLANs for your internal network, VMKernal (if you have a separate management network), DMZ, and VMotion.  While ideally you would have 2 dedicated to VMotion, you should be fine with this setup.  You'll get more use out of your NICs this way and better redundancy.  It's not like your using VMotion all day. If you have Enterprise Plus and use the Distributed Switch, I would still go the same route with 4 uplinks on the Distributed Switch and keep your iSCSI in a vSwitch or separate Distributed Switch. If you have 2 onboard NIC ports and a 4 port NIC.  In that case, place one of the onboards in each vSwitch.  Same goes for 3 x 2 ports.             
You can likely do more than 10 VMs.  I would imagine if you don't have the numbers already, you probably don't have anything too I/O intense.  Providing you are able to reach 1 Gbps, your have a ... See more...
You can likely do more than 10 VMs.  I would imagine if you don't have the numbers already, you probably don't have anything too I/O intense.  Providing you are able to reach 1 Gbps, your have a separate connection for VMotion traffic, and your average 17 Mbps in disk I/O per VM (which is probably higher than your average), your environment could theoretically hold a maximum of 59 VMs.  Of course, you could have a VM that throws that completely out the window. What type of servers are in your environment?      
VCenter/VSphere doesn't having any built-in reporting mechanisms.  Aside from using 3-rd party tools, you could always query the historical data from the VCenter SQL database using something like... See more...
VCenter/VSphere doesn't having any built-in reporting mechanisms.  Aside from using 3-rd party tools, you could always query the historical data from the VCenter SQL database using something like SQL Reporting Services or a progamming language of your choice.  It would take some digging to correlate all the data but it's there.  Look at the views such as "..._HIST_STAT..."
Not sure if you have the capabilities of doing this in your environment, but if you want to isolate your management interfaces, here is how it could be done in general. Create separate VLANs f... See more...
Not sure if you have the capabilities of doing this in your environment, but if you want to isolate your management interfaces, here is how it could be done in general. Create separate VLANs for each of your subnets using VLAN tagging on your switch (that is if you have a managed switch).  Connect your router to both VLANs.  Ensure you have routes between each VLAN/Subnet and setup your ACL to allow access to the Management Interface.  This link should tell you what ports you need. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1012382 Otherwise, put the Management Interface into the same subnet as your other network.
The feature you are looking for is called traffic shaping.  Not sure why you are trying to set these limits at 20 Mbps this explains where it can be applied. https://www.aiotestking.com/vmwar... See more...
The feature you are looking for is called traffic shaping.  Not sure why you are trying to set these limits at 20 Mbps this explains where it can be applied. https://www.aiotestking.com/vmware/2012/02/which-two-vsphere-elements-can-traffic-shaping-be-configured/ This article explains what to do at the vswitch level.  You would of course be applying this to all VMs that use that vswitch.  A messy work around would be to dedicate a vswitch for the VM you want to shape. http://oreilly.com/windows/excerpts/9780596805227/recipe-3-11-ethernet-traffic-shaping.html I doubt you are working with Enterprise Plus, but if you are, this should help you. http://www.vmware.com/files/pdf/vsphere-vnetwork-ds-migration-configuration-wp.pdf
VMWare uses all of the same basic networking principles in the physical world, just virtualized.  It doesn't route for you.
If this is an FC LUN, then you will need to provide your SAN with the WWN for your HBAs.  Once that is done, "Rescan All" in the VIC and you should see the LUN. If this is iSCSI, you need to e... See more...
If this is an FC LUN, then you will need to provide your SAN with the WWN for your HBAs.  Once that is done, "Rescan All" in the VIC and you should see the LUN. If this is iSCSI, you need to ensure that your SAN and NICs on the ESX host are on the same VLAN/Subnet for each path you are setting up, that CHAP is setup properly if in use, etc.  Look up the documentation for your iSCSI storage. If this is local storage in another server, then you need to do something serious reading, take a class, or just quit your job.   j/k
You can do this on the virtual port if you use a vNetwork distributed switch.  Distributed Switches are the way to go bu they only come with Enterprise Plus