5ain7 ga11 . CH || i7-l3ak5. CH || g07r007.CH

Virtualisierung

Datenträger Quorum in Hyper-v 2012 R2 zügeln ohne downtime

by on Aug.31, 2015, under Hyper-V, Knowledgebase, Server-Plattformen, Virtualisierung, Windows Server 2012 R2

Falls man mal das Datenträgerquorum eines Hyper-V 2012 R2 Clusters zügeln muss, dann geht dies ganz einfach und ohne downtime.

Einfach das gewünschte Volume per ISCSI oder SAS erstellen (normalerweise nimmt der Clustermanager einfach das Kleinste) und bei allen Nodes anbinden. Dann den Printscreens folgen:

 

HVCL1

Rechte Maustaste auf den Cluster, “Weitere Aktionen” => ” Quorumeinstellungen konfigurieren”.

HVCL2

“Erweiterte Quorumkonfiguration” und anschliessend auf “weiter”.

hvcl3

Mein Quorum gilt für alle Nodes, darum “Alle Knoten” wählen und auf “weiter”.

hvcl5

“Datenträgerzeugen konfigurieren ” und “weiter”.

hvcl6

Neuen Speicherzeugen wählen und “weiter. Danach ist das neue Quorum aktiv und das alte kann gelöscht werden.

Leave a Comment more...

ESXi 4.1 Installation hängt bei “multiextent loaded succesfully” bei einem HP DL380 G6+

by on Sep.09, 2011, under ESX(i)-Server, Knowledgebase, Virtualisierung

Ich hatte das Problem, dass die frische Installation des ESXi hängen blieb und zwar beim Punkt:

multiextent loaded succesfully.

ESXi Installation hangs

ESXi Installation hangs

Weder ein Reboot noch langes warte schaffte Abhilfe. Ich musste einfach das RAID neu erstellen, die Installation neu starten und dann klappte es.

 

 

Leave a Comment more...

VMWare Vsphere Client und Windows 7

by on Sep.10, 2009, under Knowledgebase, Virtualisierung, VMWare Clients, Windows 7

Windows 7 steht vor der Tür und viele sind schon drann, es wacker zu testen. Der Versuch den VSphere Client 4.0 auf Windows 7 zu installieren läuft ohne weiteres durch, beim Start der Applikation erscheinen jedoch die ersten Fehlermeldungen. Mit folgender Anleitung kann das .Net Framework für die Client umgangen werden, bis VMWare eine geeignete Version rausbringt:

1. VSphere Client auf Windows 7 installieren, Applikation jedoch nicht starten (WICHTIG!!)

2. Von einem NICHT Windows 7 PC die Datei System.dll kopieren

%SystemRoot%\Microsoft.NET\Framework\v2.0.50727\System.dl

Es handelt sich dabei um die System.dll des .Net 3.5 SP1.

3. Im nächsten Schritt mus ein neuer Ordner “Lib”  im Verzeichnis des VSphere Clients erstellt werden.

Bei 32 bit Betriebssystemen sieht es folgendermassen aus:

%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

Bei 64 bit:

%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

Die System.dll muss in den soeben erstellten Ordner “Lib”  kopiert werden.

4. In einem weiteren Schritt muss die VSphere Config Datei um ein paar Hacks angepasst werden:

32bit oder 64bit:

%ProgramFiles(x86)%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe.config
%ProgramFiles%\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe.config

Folgende Codefragmente hinzufügen:

<runtime>
<developmentMode developerInstallation="true"/>
</runtime>

damit die Datei folgendermassen aussieht:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <system.net>
        <connectionManagement>
            <clear/>
            <add address="*" maxconnection="8" />
        </connectionManagement>
    </system.net>
  <appSettings>
    <add key = "protocolports" value = "https:443"/>
  </appSettings>
<runtime>
<developmentMode developerInstallation="true"/>
</runtime>
</configuration>

5. Anschliessend muss nur noch eine Umgebungsvariabel angepasst werden, damit die System.dll von Windows 7 auch gefunden werden kann.

System Variabel

System Variabel

Der Wert ist:

C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib oder

C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\Lib

6. Windows 7 neu booten und der VSphere Client ist einsatzbereit.

Leave a Comment more...

Unterschied zwischen ESXi- und ESX Server

by on Aug.10, 2009, under ESX(i)-Server, Knowledgebase, Virtualisierung

Von VMWare werden verschiedene Varianten des ESX-Servers vertrieben, darunter auch den gratis ESXi-Server. Hier eine Zusammenstellung, was genau die Unterschiede sind.

Capability

VMware ESX

VMware ESXi

Service Console Service Console is a standard Linux environment through which a user has privileged access to the VMware ESX kernel. This Linux-based privileged access allows you to highly customize your environment by installing agents and drivers and executing scripts and other Linux-environment code. VMware ESXi is designed to make the server a computing appliance. Accordingly, VMware ESXi behaves more like firmware than traditional software. To provide hardware-like security and reliability, VMware ESXi does not support a privileged access environment like the Service Console of VMware ESX. To enable interaction with agents, VMware has provisioned CIM Providers through which monitoring and management tasks – traditionally done through Service Console agents – can be performed. VMware has provisioned RCLI to allow the execution of scripts.
Remote CLI VMware ESX Service Console has a host CLI command through which VMware ESX can be configured. ESX 3.5 Update 2 supports RCLI. VMware ESX Service Console CLI has been ported to a Remote CLI (RCLI) for VMware ESXi. RCLI is a virtual appliance that interacts with VMware ESXi hosts to enable host configuration through scripts or specific commands.

Note:

  • RCLI is limited to read-only access for the free version of VMware ESXi. To enable full functionality of RCLI on a VMware ESXi host, the host must be licensed with VI Foundation, VI Standard, or VI Enterprise.
  • The VMware Infrastructure toolkit for Windows and the Perl toolkit access ESXi through the same API as RCLI. Similarly, these toolkits are limited to read-only access for the free version of VMware ESXi. When the host is upgraded to VI Foundation, VI Standard, or VI Enterprise, these toolkits have write-access and provide a scriptable method for managing ESXi hosts.
  • The following Service Console CLI commands have not been implemented in RCLI:
    • ESXcfg-info
    • ESXcfg-resgrp
    • ESXcfg-swiscsi
Scriptable Installation VMware ESX supports scriptable installations through utilities like KickStart. VMware ESXi Installable does not support scriptable installations in the manner ESX does, at this time. VMware ESXi does provide support for post installation configuration script using RCLI-based configuration scripts.
Boot from SAN VMware ESX supports boot from SAN. Booting from SAN requires one dedicated LUN per server. VMware ESXi may be deployed as an embedded hypervisor or installed on a hard disk.

In most enterprise settings, VMware ESXi is deployed as an embedded hypervisor directly on the server. This operational model does not require any local storage and no SAN booting is required because the hypervisor image is directly on the server.

The installable version of VMware ESXi does not support booting from SAN.

Serial Cable Connectivity VMware ESX supports interaction through direct-attached serial cable to the VMware ESX host. VMware ESXi does not support interaction through direct-attached serial cable to the VMware ESXi host at this time.
SNMP VMware ESX supports SNMP. VMware ESXi supports SNMP when licensed to a VI Foundation, VI Standard, or VI Enterprise edition. The free version of VMware ESXi does not support SNMP.
Active Directory Integration VMware ESX supports Active Directory integration through third-party agents installed on the Service Console. VMware ESXi with a Virtual Infrastructure license and in conjunction with VirtualCenter allows users to be authenticated via Active Directory. In this configuration, users can log in directly to an ESXi host and authenticate using a local username and password.

The free version of VMware ESXi does not support Active Directory integration at this time.

HW Instrumentation Service Console agents provide a range of HW instrumentation on VMware ESX. VMware ESXi provides HW instrumentation through CIM Providers. Standards-based CIM Providers are distributed with all versions of VMware ESXi. VMware partners may inject their own proprietary CIM Providers in customized versions of VMware ESXi. To obtain a customized version of VMware ESXi, you typically have to purchase a server with embedded VMware ESXi through a server vendor.

At this time, HP also offers its customized VMware ESXi Installable on www.vmware.com. Dell, IBM, and FSC will soon offer their customized version of VMware ESXi on www.vmware.com.

Remote console applications like Dell DRAC, HP iLO, IBM RSA, and FSC iRMC S2 are supported with ESXi.

Note: COS agents have a longer lineage than CIM Providers and are therefore more mature. VMware is actively working with its 250+ partners to close the CIM Provider–Service Console agent gap.

Software Patches and Updates VMware ESX software patches and upgrades behave like traditional Linux based patches and upgrades. The installation of a software patch or upgrade may require multiple system boots as the patch or upgrade may have dependencies on previous patches or upgrades. VMware ESXi patches and updates behave like firmware patches and updates. Any given patch or update is all-inclusive of previous patches and updates. That is, installing patch version “n” includes all updates included in patch versions n-1, n-2, and so forth.
VI Web Access VMware ESX supports managing your virtual machines through VI Web Access. You can use the VI Web Access to connect directly to the ESX host or to the VMware Infrastructure Client. VMware ESXi does not support web access at this time.
Licensing VMware ESX hosts can be licensed as part of a VMware Infrastructure 3 Foundation, Standard, or Enterprise suite. VMware ESXi hosts can be individually licensed (for free) or licensed as part of a VMware Infrastructure 3 Foundation, Standard, or Enterprise suite.

Individually licensed ESXi hosts offer a subset of management capabilities (see SNMP and Remote CLI).

ESXi – Free License

(ESX not available without VI)

VI Foundation

(with ESX or ESXi)

VI Standard

(with ESX or ESXi)

VI Enterprise

(with ESX or ESXi)

Core hypervisor functionality

Yes

Yes

Yes

Yes

Virtual SMP

Yes

Yes

Yes

Yes

VMFS

Yes

Yes

Yes

Yes

VirtualCenter Agent

Yes

Yes

Yes

Update Manager

Yes

Yes

Yes

Consolidated Backup

Yes

Yes

Yes

High Availability

Yes

Yes

VMotion

Yes

Storage VMotion

Yes

DRS

Yes

DPM

Yes

Leave a Comment more...

ESXi-Server via SSH verwalten

by on Aug.07, 2009, under ESX(i)-Server, Knowledgebase, Virtualisierung

Standardmässig ist der SSH-Zugang deaktiviert. Um es trotzdem zu verwenden, kann man den SSH Zugang wie folgt aktivieren:

  1. Go to the ESXi console and press alt+F1
  2. Type: unsupported
  3. Enter the root password(No prompt, typing is blindly)
  4. At the prompt type “vi /etc/inetd.conf”
  5. Look for the line that starts with “#ssh” (you can search with pressing “/”)
  6. Remove the “#” (press the “x” if the cursor is on the character)
  7. Save “/etc/inetd.conf” by typing “:wq!”
  8. Restart the management service “/sbin/services.sh restart”

Ich habe zur Zeit noch das Problem, das Watchdog reinfunkt und den Port 22 blockt. Habe noch keine Lösung gefunden, wie man den Port fix öffnet. Ich löse dies temporär immer mit dem Befehl: <services.sh stop watchdog>. Zum Starten das Gleiche, einfach mit start:-)

Leave a Comment more...

Zugriff auf ESXi Konsole

by on Aug.07, 2009, under ESX(i)-Server, Knowledgebase, Virtualisierung

Der Zugriff bei der ESXi Konsole ist ein bisschen versteckt.  Beim VMWare-Hypervisor Standardbildschirm folgendes eingeben:

  • ALT-F1 betätigen
  • beim blinkenden Cursor:  “unsupported” eintippen und anschliessend <ENTER>
  • Passworteingabe erschein, Pwd reinhacken und voila!

Mit <ALT-F2> kommt man wieder auf  den Shell-like Standardbildschirm.

Leave a Comment more...

Blogroll

A few highly recommended websites...