Category: vCenter

Perf Charts service experienced an internal error in vCenter

After a long summer break I’m back with a new post ūüôā Today one of my customer got an error in vCenter performance monitor for all there hosts. “Perf Charts service experienced an internal error in vCenter message report application initialization is not completed successfully. retry in 60 seconds” So I found this KB from VMware that says you have to restart the VMware VirtualCenter Management Webservices service. This did not help at first. Then I could see that the SQL Server Browser service was not running I then changed the startup type to Automatic and the started the service and then I restated the VMware VirtualCenter Management Webservices service again. Now the performance monitor is working again! ūüôā If you have anything to add or just fund this usefull then pleas leave a comment below. Thanks!
perfCharterror


EVC Baselines for Intel and AMD CPU’s

Here you can see the EVC Cluster baselines and what CPU’s that will go together. I know you finde this information at vmware and other blog, but this is also for my onw refrence ūüôā
EVC Cluster Baseline
  Intel¬ģ Xeon¬ģ Host CPU Model
Intel¬ģ “Merom” Generation
Intel¬ģ “Penryn” Generation
Intel¬ģ “Nehalem” Generation
Intel¬ģ “Westmere” Generation
Intel¬ģ “Sandy Bridge” Generation
30xx Series
Yes
No
No
No
No
32xx Series
Yes
No
No
No
No
51xx Series
Yes
No
No
No
No
53xx Series
Yes
No
No
No
No
72xx Series
Yes
No
No
No
No
73xx Series
Yes
No
No
No
No
31xx Series
Yes
Yes
No
No
No
33xx Series
Yes
Yes
No
No
No
52xx Series
Yes
Yes
No
No
No
54xx Series
Yes
Yes
No
No
No
74xx Series
Yes
Yes
No
No
No
35xx Series
Yes
Yes
Yes
No
No
55xx Series
Yes
Yes
Yes
No
No
34xx Lynnfield Series
Yes
Yes
Yes
No
No
34xx Clarkdale Series without AES and PCLMULQDQ
Yes
Yes
Yes
No
No
65xx Series
Yes
Yes
Yes
No
No
75xx Series
Yes
Yes
Yes
No
No
i3/i5 Clarkdale Series without AES and PCLMULQDQ
Yes
Yes
Yes
No
No
34xx Clarkdale Series with AES and PCLMULQDQ
Yes
Yes
Yes
Yes
No
28xx Series
Yes
Yes
Yes
Yes
No
36xx Series
Yes
Yes
Yes
Yes
No
48xx Series
Yes
Yes
Yes
Yes
No
56xx Series
Yes
Yes
Yes
Yes
No
88xx Series
Yes
Yes
Yes
Yes
No
i3/i5 Clarkdale Series with AES and PCLMULQDQ
Yes
Yes
Yes
Yes
No
E7-28xx Series
Yes
Yes
Yes
Yes
No
E7-48xx Series
Yes
Yes
Yes
Yes
No
E7-88xx Series
Yes
Yes
Yes
Yes
No
E3-12xx Series
Yes
Yes
Yes
Yes
Yes
21xx Series
Yes
Yes
Yes
Yes
Yes
E5-26xx Series
Yes
Yes
Yes
Yes
Yes

How to backup VMware vCenter Server Virtual Appliance (VCSA) with Veeam

When you use Veeam to backup a vCenter cluster that is running on vSphere 5.x VCSA, there is a chance you will get an error when trying to backup the VCSA it self. This only applies when you have Enable VMware tools quiescence in you backup job. One way to backup the VCSA is to make a separate job for the VCSA and uncheck “Enable VMware tools quiescence” in this job. Another way is to disable it from within the eg. “cluster backup job”.
First Edit the job containing the VCSA in the step called “Guest Processing” click the “Advanced” button.


Howto update VMware vCenter Server Appliance 5.0 Update 1A

In this post I will go thru how to update¬† VMware vCenter Server Appliance (VCSA) to version 5.0 Update 1A. First of all make sure that you have a snapshot or backup of you’re vCenter. Next log in to the webinterface https://vCenterServerIP:5480. Go to the Update tab and click the “Check Updates” Accept the EULA ūüôā and click OK to install the update         Now wait… the installation can take up to 120 minutes.       After the installation has completed you will need to reboot the VCSA. From the System->information tab click reboot   Now you’re VCSA is updated and you are good to go. Pleas have a look at the VMware vCenter Server 5.0 Update 1a Release Notes for known issues and more

VMware vCenter 4 Error ‚ÄúPropertyCollector.RetrieveContents‚ÄĚ

This is acluy an old problem but I ran into it again wehen upgrading a vSphere 4.1 and vCenter 4 to vSphere 5. I got this error when trying to migrate a VM. I remembered that this error chould have something to do with and ISO mounted or CD-ROM drive was connectet, so I tryed to unmount it but could not get access to the edit menu. I tryed to remove the VM from the inventory and add it back in and it worked. I could mirate the VM off the host. Call “PropertyCollector.RetrieveContents” for object “propertyCollector” on vCenter Server “” failed.  

En uge til VMworld 2011 i CPH

S√• er der kun en uge til at jeg skal til VMworld i CPH! Det bliver super fedt.¬†Programmet for ugen er lavet.¬† – What’s New with VMware vSphere 5.0 Licensing and Pricing” – Accelerate Desktop Virtualization Sales” – Selling the Value of the VMware Solution Portfolio to SMBs” – Managing VMware ESXi with VMware vSphere PowerCLI” – Mythbusters Goes Virtual” – Design, Deploy, Optimized SQL Server on VMware ESXi 5″ – VMware vSphere PowerCLI Best Practices” – Storage Tips and Best Practices for VMware View Desktop Deployments” – Design, Deploy, and Optimize Exchange 2010 on vSphere” – Understanding Virtualized Memory Performance Management” – Getting Started with VMware vSphere Design” – VMware Storage vMotion Deep Dive and Best Practices” – Sneak Preview of Next-Generation VMware Hybrid Cloud Solutions” – VMware vSphere 5.0 Storage Features” Vi ses!

vCenter Virtual Appliancefeatures (vCSA) features og fordele

VMware vCenter Server Virtual Appliance giver de samme fordele som central¬†vedligeholdes af sin VMware vSphere infrastruktur. Den store forskel ligge i at det nye vCenter er baseret p√• en SUSE LINUX platform. Konceptet er ikke noget nyt, tilbage i 2009 udgav VMware¬†vCenter Server 2.5 on Linux. Men nu kommer det med i vSphere 5 pakken. Jeg har brugt vCSA flere gange i labs og kan se store fordele i produktet, b√•de fordi det netop ikke kr√¶ver en Windows licens men ogs√• fordi det er forholdsvist hurtig at¬†deploy. Jeg har pr√łvet at liste de fordel og features¬†jeg kan se ved vCSA: Fordel og features:
  • Hurtig installation der ikke tager mere end 20 min.
  • Installeres p√• SUSE Linux Enterprise Server 11 x64.
  • OVF deployed og fylder 15GB + 60GB samt bruger 8GB RAM og 2x vCPU (kan godt k√łrer med mindre).
  • Inkludere en embedded DB2 database der er beregnet til milj√łer med mindre end 5 ESXi hosts eller 50 VM’er (Svarer til Windows vCenter Server med MSSQL Express som DB).
  • Underst√łtter p.t. kun Oracle database til st√łrre installationer.
  • Kan intrigere med Active Directory (AD) og¬†Network Information Services (NIS)¬†autentificering.
  • vSphere Web Client support er bygget ind i vCenter Server Virtual Appliance.
  • Kan bruge NFS store til vCenter Server Virtual Appliance core og log filer.
  • Kan patches direkte i web interface.
  • inkludere en pre-konfigureret Auto Deploy server.
  • Kr√¶ver ingen Windows OS licens.
vCSA supportere ikke:
  • Microsoft SQL som database for vCenter.
  • vCenter Server Linked Mode.
  • vCenter Server Heartbeat.
  • IPv6.
Jeg h√•ber at jeg kan f√• tid til at lave en gennemgang af installation. Men indtil da kan du jo selv pr√łve. Du kan hente vCSA p√• VMware’s hjemmeside. Held og lykke med vCSA

vMotion fejler efter opgradering til vCenter 5

Efter opgradering af vCenter til version 5 har jeg oplevet at nogle VM’er ikke kunne migreres mellem mine hosts. I vCenter kommer denne fejl : Host CPU is incompatible with the virtual machine’s requirements at cupid level 0x1 register’ecx’ Host bits: 0000:0100:0000:1000:0010:0010:0000:0001 Required: 1000:0100:0000:100x:xxx0:0x1x:xxx0:x001 Mismatch detected for these features: *General incompatibilities; refer to KB article 1993 for possible solutions. I mit tilf√¶lde kommer fejlen fordi at mit vCenter er opgraderet fra version 2.5 til 4.0 og derefter til 5.0. hvor gamle CPUmaskings er flytte med over. For at komme dette til livs er det n√łdvendigt at lukke VM’en ned og rette i dens HW konfiguration.
For at få vMotion til at virke korrekt (igen):
  1. Sluk VM’en.
  2. Klik p√•¬†Edit Settings¬†for VM’en.
  3. Klik Options.
  4. Vælge CPUID Mask under Advanced.
  5. Klik Advanced.
  6. Klik Reset All to Default.
  7. Klik OK.
  8. Klik OK igen.
  9. Tænd din VM og migrate.
Se evnt. denne VMware KB som beskriver problemet

vSphere HA fejler efter migrering til vCenter 5.0

Efter opgradering af vCenter til version 5.0, melder cluteret en fejl, der fort√¶ller at den ikke kan finde en vSphere master host. Grunden til dette er at SSL certifikatet ikke er blevet verificeret automatisk ved migreringen fra vCenter 4.   For at komme rette denne fejl skal man, som der st√•r i¬†fejlmedelsdsen, kontrollere at SSL. Dette g√łres fra vCenter -> Administratration -> vCenter Server Settings og under punktet SSL settings vil du kunne se de ESX(i) servere der ikke er blevet “verified”. S√¶t v ved dem der ikke er¬†verificeret¬†og Reconfigure vSphere HA for hver af de servere der fejler i din cluster.  

VMware vCenter server service stopper

Efter installationen af vCenter p√• den embeddet SQL 2005 express er det n√łdvendigt af s√¶tte databasen til simpel recovery mode, man kan ogs√• v√¶lge at tage backup af databasen med et backup software og her v√¶lge at tage transactions log backup. I¬†mindre milj√łer er det dog ikke n√łdvendigt med en fuld SQL server og express er en ok valg. Der vil komme en fejl i event loggen der hedder noget i sil med nedenst√•ende og Eventid‚Äôet er 9002.¬†: The transaction log for database ‚ÄėVIM_VCDB‚Äô is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases For at l√łse problemet kan man downloaded og installere¬†Microsoft SQL Server Management Studio Express¬†og s√¶tte databasen til simpel mode fra bulk-log. Det kan ogs√• v√¶re en god ide at shrike de filer der er skrevet. h√łjre-click VIM_VCDB v√¶lge Tasks ‚Äď> Shrink ‚Äď> Files. Herefter kan vCenter server servicen startes igen.