If you have the power of multiple servers connected to a UPS, you probably need to shut them down when the power goes down and before the UPS runs out of juice. Unless your UPS can be connected to the network, you usually can only connect a single device to it using good old serial or brand new USB. That single host now knows about the UPS status, but what about all the other systems?...
I have had a strange issue lately with Windows servers on VMware vSphere 5.1 hosts. Throughput of TCP connections between some virtual machines were very very slow, barely 10 mbit/s . The behavior was easily reproducible : just start an iperf connection between a Windows Server 2008 and a Windows 2012 server, and you get 10 mbit/s . Moving both virtual machines on the same ESXi host, or on different hosts, did not change anything....
A few months ago, I was unable to login on my vCSA. At that time, I thought it ws a glitch, I rebooted (didn’t fix the issue) and changed the password of the users, which fixed the issue. Recently, I had the same issue. I concluded it could not be a glitch anymore and decided to search for root cause. The reason given by Veeam was “username or password incorrect”, which was wrong....
I had to configure a bunch of ESXi 5.1 servers with LSI 9240-4i hardware RAID controllers the other day. This RAID controller is perfectly supported in ESXi 5.1 but it lacks the monitoring features. To have these, you need to install first the LSI SMIS package on your ESXi hosts. With this, the ESXi server acts as a proxy to query the RAID controller from the network. Then you need a Windows computer running LSI MegaRaid Storage Manager (MSM) software....
Update: I just saw that since April 25th, SQL Server 2012 and Windows Server 2012 are supported by VMware vCenter 5.1U1 . All information is available here : http://blogs.vmware.com/vsphere/2013/04/vmware-vcenter-server-5-1-update-1-released.html Original November 21th 2012: While it is working with the SSO service, vCenter and vCloud Director, it just doesn’t work with Update Manager service. Well, at least with the SQL Server native client v11. Then Update Manager service just doesn’t start and throws an unhelpful 1067 Error....
So, like me, you want to have redundancy for your virtual machine network. For my lab setup, I use a refurbished Cisco router 3825 with two gigabit interfaces, two Procurve 2810-24G and a small server with 4 gigabit interfaces for the ESXi. You just have to: team the NICs on the ESXi (use src-mac + beacon probing), use port-channel on the Cisco router and src-mac too, configure the switches exactly the same way as if there wasn’t any redundancy, add a link between the two switches and configure it to transmit the VLANs you need, don’t forget to add STP on the switches and put a high priority (low number) on the link between the switches....
Vos machines virtuelles sont lentes, vous pensez que le CPU n’est pas en cause parce que vous avez une utilisation faible des pCPU ? Regardez-y à deux fois, il se pourrait que vos VM attendent du pCPU disponible! Pour vérifier que vos VM n’attendent pas pour avoir du CPU, allez dans l’onglet performance, advanced, CPU. Dans chart options, choisissez “Ready (ms)”. C’est bien joli, mais ça ne vous dit pas encore grand chose....
Yo. Si vous voulez migrer des Windows vers une VM VMware, vous rencontrerez sans doute le fameux BSOD 0x7b. Le problème vient du fait que Windows n’a pas les infos pour gérer le disque. Pour aider à la résolution du problème, VMware a posté un item sur sa KB : http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005208 Maintenant la VM devrait démarrer, mais vous n’aurez sans doute pas de connection réseau. Mais si vous essayez de configurer votre ancienne IP sur la nouvelle carte détectée, Windows vous insulte parce que l’IP est déjà configurée sur une autre carte....
Il y a quelques mois, j’ai dû installer ESXi sur des serveurs blades sans contrôleur RAID supporté par VMware. J’ai donc naturellement emprunté le chemin d’AutoDeploy. J’ai testé la méthode sur un blade, je l’ai configuré comme il faut (vDS, vSwitch, iSCSI, HA, …), reboot un nombre incalculable de fois, migré des VM depuis et vers ce blade, tout fonctionnait parfaitement. Nous voilà arrivé à vendredi passé lorsqu’il a été décidé d’installer les autres blades de la même manière....