isp.sad.de

notes on virtualization

  • Last Posts

  • Categories

  • Who writes

  • Archive

  • Meta

  • Statistics

    • StatistikenStatistiken
    • Besucher Heute 25
    • Besucher Gestern 45
    • Max. pro Tag 56
    • Gerade Online 3
    • Besucher Gesamt 3.161

  • Tags

  • RSS RTFM

  • RSS yellow bricks

  • RSS Scott Lowe

  • RSS vmLIVE

  • RSS Caschy

  • Abonnieren

KBdigest vCenter: New articles published for week ending 7/17/2010

Erstellt von Adam Fleischmann am Sonntag 25. Juli 2010

VMware vCenter Server
vCenter Server 4.1 fails to install or upgrade with the error: This installation package is not supported by this processor type (1019144)
Date Published: 7/12/2010
Guided Consolidation analysis pauses and cannot be restarted (1019242)
Date Published: 7/12/2010
VMkernel fails to set MTU on vNetwork Distributed Switch (1020617)
Date Published: 7/12/2010
Maximum number of supported devices reached (1020653)
Date Published: 7/12/2010
ESX host is unable to connect to NFS server (1020705)
Date Published: 7/12/2010
vCenter Server does not start when connecting to an Oracle database (1021194)
Date Published: 7/12/2010
vCenter Server fails to populate performance charts and displays an error message when you use custom JDBC SQL port (1021202)
Date Published: 7/12/2010
vCenter Server installation with Oracle database fails after previous failure or shutdown (1021240)
Date Published: 7/12/2010
Accented and composite characters are not displayed in the index for French-language online Help (1021569)
Date Published: 7/12/2010
Some events cannot trigger alarms (1021613)
Date Published: 7/12/2010
vSphere Client displays incorrect characters when vCenter Server is not configured to support the language locale of the vSphere client (1021614)
Date Published: 7/12/2010
Migrating to the vCenter Server 4.1 database (1021635)
Date Published: 7/12/2010
vCenter Server 4.1 network port requirements (1022256)
Date Published: 7/12/2010
Error Message When Trying to Migrate Virtual Machine with USB Devices Attached (1022359)
Date Published: 7/12/2010
A missing database index slows vCenter Server (1023977)
Date Published: 7/12/2010
Virtual machine MAC address conflicts (1024025)
Date Published: 7/12/2010
Supported vCenter Server high availability options (1024051)
Date Published: 7/16/2010
Using the Data Migration Tool to upgrade from vCenter Server 4.0 to vCenter Server 4.1 fails (1024380)
Date Published: 7/16/2010
VMware vCenter Server 4.0.x
Manually enable vSphere solutions (1021265)
Date Published: 7/12/2010
iSCSI adapters cannot establish a connection to an NetApp iSCSI storage array (1021267)
Date Published: 7/12/2010
InvalidException Error Occurs When Virtual Machine and Host Do Not Belong to the Same Distributed Virtual Switch (1021318)
Date Published: 7/12/2010
Storage device path redundancy restored (1020456)
Date Published: 7/12/2010
Frequent PowerOn Reset Unit Attentions occur on device (1020702)
Date Published: 7/12/2010
Transient failure recovery due to watchdog timeout (1020706)
Date Published: 7/12/2010
Changes to Fault Tolerance in vSphere 4.1 (1022844)
Date Published: 7/12/2010
Login to vCenter Server 4.0 Update 1 using vSphere Client 4.1 fails in Linked Mode environments when vCenter Server Update 1 and vCenter Server 4.1 use a different HttpsProxyPort (1024120)
Date Published: 7/12/2010

 

via VMwareKBdigest

Abgelegt unter kb, top kb, vsphere | Keine Kommentare »

vSphere 4.1 HA feature, totally unsupported but too cool » Yellow Bricks

Erstellt von Adam Fleischmann am Sonntag 18. Juli 2010

Early 2009 I wrote an article on the impact of Primary Nodes and Secondary Nodes on your design. This was primarily focussed on Blade environments and basically it discussed how to avoid having all your primary nodes in a single chassis. If that single chassis would fail, no VMs would be restarted as one of the primary nodes is the “failover coordinator” and without a primary node to assign this role to a failover can’t be initiated.

With vSphere 4.1 a new advanced setting has been introduced. This setting is not even experimental, it is unsupported. I don’t recommend anyone using this in a production environment, if you do want to play around with it use your test environment. Here it is:

das.preferredPrimaries = hostname1 hostname2 hostname3
or
das.preferredPrimaries = 192.168.1.1,192.168.1.2,192.168.1.3

The list of hosts that are preferred as primary can either be space or comma separated. You don’t need to specify 5 hosts, you can specify any number of hosts. If you specify 5 and all 5 are available they will be the primary nodes in your cluster. If you specify more than 5, the first 5 of your list will become primary.

Please note that I haven’t personally tried it and I can’t guarantee it will work.

via yellow-bricks.com

Posted via email from ISP.SAD.DE

Abgelegt unter vmware | Keine Kommentare »

VMware KB: Installing ESX 4.1 and vCenter Server 4.1 best practices

Erstellt von Adam Fleischmann am Freitag 16. Juli 2010

This article provides a quick reference to the information needed for a trouble-free installation or upgrade of ESX 4.1 and vCenter Server 4.1.

Note: Because each environment is different, many installation decisions require knowledge and understanding beyond the scope of this article. For more detailed information about your installation, see the vSphere 4.1 documentation. 

via kb.vmware.com

Posted via email from ISP.SAD.DE

Abgelegt unter kb, vmware | Keine Kommentare »

Update Manager 4.1 patch repository features

Erstellt von Adam Fleischmann am Freitag 16. Juli 2010

Purpose

Update Manager can download patches and extensions either from www.vmware.com or from a shared repository.

 

This article provides steps to manually add patches to the Update Manager 4.1 repository.

Resolution

Update Manager 4.1 allows you to import both VMware and third-party patches manually from a ZIP file, called an offline bundle.
You download these patches from the Internet or copy them from a media drive, then save them as offline bundle ZIP file on a local drive.

To import a patch:

  1. From vCenter Server, click Home > Update Manager.
  2. Click the Configuration tab and click Patch Download Settings.
  3. Click the Import Patches link at the bottom of the Patch Download Sources pane to upload to the Update Manager Repository.

Posted via email from Biking Web

Abgelegt unter vmware | Keine Kommentare »

Upgrade auf vsphere 4.1

Erstellt von Adam Fleischmann am Freitag 16. Juli 2010

Migrating to the vCenter Server 4.1 database

Purpose

vCenter Server 4.1 is supported only on 64 bit operating systems. As such, there is no in-place upgrade path for vCenter Server installs on 32 bit operating systems. If your vCenter Server is installed on a 32 bit operating system, you need to switch to a new 64 bit machine where vCenter Server 4.1 can be installed.

 

This article provides an overview of the database migration procedure using the vCenter Server 4.1 migration tools.

Resolution

To backup the database:

  1. Open the folder datamigration on the vCenter Server 4.1 installation media.
  2. Copy the datamigration.zip file and extract it to the root of your C: drive.
  3. Stop these services:

4.    

  • Open a command prompt and change to the c:\datamigration folder.
  • Run this command to backup the vSphere 4.0 configuration:

    backup.bat

    • To restore the database:

    1. Copy the C:\datamigration folder to your Windows 64 bit C: drive.
    2. Have the vSphere 4.1 installation media on your local CD-ROM drive.

      Note: Close the autorun menu if it opens.

    3. Open a command prompt and change to the c:\datamigration folder.
    4. Run this command to install and restore the vSphere 4.0 configuration:

      install.bat

      Note: This script asks you for vCenter Server installation media path.
       

    5. Follow the installation wizard.

    Posted via email from Biking Web

    Abgelegt unter vmware | Keine Kommentare »

     

    © 2010 isp.sad.de All Rights Reserved