Direkt zum Hauptbereich

Beliebte Posts aus diesem Blog

change esx host ip adress

Changing the IP address of service console in ESX 3.x Damian Murdoch comes through again, this time, helping us change the IP address of the service console in VMware's ESX Server 3.x. If you want to change the IP address of the service console in ESX 3.x you can using a command in the service console. To change the IP address of the ESX 3.x host, you need to change the configuration of the vswif. By default this is vswif0 and this is assumed in this document. Login to the service console with root permissions, either by using root or doing a su - to get the permissions. Once in the service console runt the command "esxcfg-vswif -d vswif0". This command deletes the existing vswif0. Don't worry if you get a message about nothing to flush. Then you need to run the command to change the ip address, subnet mask and broadcast address. They are also specified in that order when the command is given. An example command is below. "esxcfg-vswif -a vswif0 -p Service\ Conso...

SSH Connect für root auf VMWare ESX

SSH Security SSH is a commonly used UNIX and Linux command shell that lets you remotely log in to the service console and perform certain management and configuration tasks for ESX Server 3. SSH is used for secure logins and data transfers because it offers stronger protection than other command shells. In this ESX Server 3 release, the SSH configuration is enhanced to provide a higher security level. Key features of this enhancement include: Version 1 SSH protocol disabled – VMware no longer supports Version 1 SSH protocol and uses Version 2 protocol exclusively. Version 2 eliminates certain security issues present in Version 1 and provides you with a safer communications interface to the service console. Improved cipher strength – SSH now supports only 256‐bit and 128‐bit AES ciphers for your connections. Limits on remote logins as root – You can no longer remotely log in as root. Instead, you log in as an identifiable user and either use the sudo command to execute specific opera...

OPManager MSP: Probe findet Central Server nicht

die Probe des opmanager msp edition konnte den zentralen Server nicht finden. Das Problem war, dass im automatisch generierten ZIP File der ServerName des Central Servers hinterlegt ist. Dieser ist aber meist nicht verwendebar, da der zentrale Server beim Service Provider steht. Das File .\AdventNet\ME\probe\conf\NOCServerDetails.xml muss wie unter beschrieben angepasst werden, dann funktioniert die Verbindung. (Vorausgesetzt sind natürlich auch entsprechend offere Ports) NOCServerName=" SERVERNAME.DOMAIN.CH" NOCServerPort="443" DMSID="RICHTIGEID"