Hüseyin Göksin Blog

Bilgi paylaştıkça çoğalır….

Host currently has no management network redundancy

When admitting a host to a HA cluster, or enabling HA on an existing cluster you may receive the “Host currently has no management network redundancy” warning message.

 

This happens due to requirements in a HA cluster where the management network (that is the service console or VMkernel port for management) is required to have two physical NICs.

If this requirement is not met the above error message is displayed. While I recommend you always, always ensure the management network has two pNICs and is redudant (including via seperate physical switches), it might not be possible in a demo/test environment.
In which case you may want to disable this warning message.

This can be done as follows…

1. Go to “Edit” the cluster settings

2. Click “VMware HA”

3. Click “Advanced Options”

 

4. Add “das.ignoreRedundantNetWarning” and set the value to “True”, Click Ok

5. If there error still shows you need to select the host and click “Reconfigure for HA”

Filed under: Esx Ailesi

Sanal windows sunucuda ses kartı ihtiyacınız mı var? Do you need sound driver on virtual machine?

ESX üzerinde ki bir makineye stream server, mp3 player ya da windows media server kurdunuz fakat doğası gereği bu tip uygulamalar fiziksel ses kartı / driveri görmek isterler.

VMware ile sanallaştırılmış bir fiziksel makineye ses kartı tanıtabilsek dahi rdp bağlantı yapacağımızdan bu driveri uzak masaüstü bağlantısı ile kullanamayız.

Aşağıdaki local policy ayarları ile rdp conneciton yaptığınız makine için ses driverını kullanabilirsiniz.

(Windows Tuşu)+R
mmc
File
Add/Remove Snap İn
Group Policy Object

esx-seskarti1

 

Local Computer Policy / Computer Configuration / Administrative Templates / Windows Components / Remote Desktop Services / Remote Dekstop Session Host / Device and Resource Redirection

altından;

esx-seskarti2

Allow audio and video playback redirection Enabled
Allow audio recording redirection Enabled

konumuna getirmeniz gerekmektedir.

Alıntıdır: http://www.erhanatalar.com/sanal-windows-sunucuda-ses-karti-ihtiyaciniz-mi-var/

Filed under: Esx Ailesi

Configuration issue : No vmkcore disk partition

Untitled

# esxcli system coredump network set –interface-name vmk0 –server-ipv4 10xx.xx.xx.xx –server-port 6500

“xxx.xxx.xxx.xxx – esx’in ip adresini yazınız”

Enable the new setting:

# esxcli system coredump network set --enable true

 

bu işlemden sonra hata gidecektir, SSH’ı kapatmayı unutmayınız.

Filed under: Esx Ailesi

Recreating a missing virtual machine disk (VMDK) descriptor file

Sanal sunucumuzun bulunduğu ESXi sunucumuza ssh ile bağlanmamız gerekecek. Bunun için Vcenter bağlantısı yapıp ESXi sunucumuzu SSH servisini etkinleştiriyoruz.

1

Ardından SSH ile ESXi sunucumuza bağlanıp sanal makinemizin bulunduğu dizine geçiyoruz.

1
~ # cd /vmfs/volumes/CloudDataStore001/FATIHSSO

Mevcut vmdk dosyalarını listemek için aşağıdaki komutu çalıştırıyoruz.

1
2
3
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# ls -ltr *.vmdk
-rw-------    1 root     root     28270762000 Jun  4 11:11 FATIHSSO-flat.vmdk
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO#

Descriptor file için gerekli olan bilgileri almak için aşağıdaki komutları çalıştırıyoruz. İlk komut ile sanal sunucuya ait kofigürasyon dosyasında disk tipine bakıyoruz. İkincisi ile diskin boyutunu byte olarak öğreniyoruz.

1
2
3
4
5
6
7
8
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# less *.vmx | grep -i virtualdev
 
scsi0.virtualDev  = "lsilogic"
 
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# ls -l *-flat.vmdk
 
-rw-------    1 root     root     19338682368 Jun  4 11:30 FATIHSSO-flat.vmdk
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO#

Şimdi geçici dosyamızı oluşturabiliriz.

1
2
3
4
5
6
7
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# vmkfstools -c 19338682368 -a lsilogic -d thin temp.vmdk
 
Create: 100% done.
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# ls -ltr *.vmdk
-rw-------    1 root     root     19338682368 Jun  4 11:11 FATIHSSO-flat.vmdk
-rw-------    1 root     root           491 Jun  4 11:37 temp.vmdk
-rw-------    1 root     root     19338682368 Jun  4 11:37 temp-flat.vmdk

Geçici olarak oluşturduğumuz temp.vmdk dosyasının adını kayıp yada bozuk olan FATIHSSO.vmdk olarak değiştiriyoruz

1
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# mv temp.vmdk FATIHSSO.vmdk

temp.vmdk descriptor file olarak temp-flat.vmdk dosyasını göstermekte bunun için burada değişiklik yapacağız. # Extent description kısmında doğru flat dosyasının adını yazıyoruz.  dd.thinProvisioned = “1″ kısmını ise siliyoruz.

1
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO# vi FATIHSSO.vmdk
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
# Disk DescriptorFile
version=1
CID=4d0d9dee
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"
 
# Extent description
RW 19338682368 VMFS "temp-flat.vmdk"
 
# The Disk Data Base
#DDB
 
ddb.longContentID = "df8d170ab490cae4cf2a24674d0d9dee"
ddb.encoding = "UTF-8"
ddb.virtualHWVersion = "4"
ddb.uuid = "60 00 C2 9b 23 9d 1e 1b-0a 47 30 60 c9 cb f7 2b"
ddb.geometry.cylinders = "4179"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"
ddb.toolsVersion = "8300"
dd.thinProvisioned = "1"

Tüm işlemler tamamlandıktan sonra temp-flat.vmdk dosyasını silebiliriz.

1
/vmfs/volumes/511518f4-8dc29ca1-47c7-a4badb4f2ae1/FATIHSSO#rm temp-flat.vmdk

Artık sunucumuzu başlatabilriz 🙂

 

“Bu link alıntıdır

http://www.fatihbayram.com/recreating-a-missing-virtual-machine-disk-vmdk-descriptor-file/”

 

Filed under: Esx Ailesi

No vmcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved

One of the nice features of ESXi 5.x is the possibility to run  a diskless system by using Auto Deploy.

When first booting the created image you’ll notice some errors which can be easily resolved.

‘No vmcore disk partition is available and no network coredump server has been configured. Host core dumps cannot be saved.’  &
‘System logs on host xxxx are stored on non-persistant storage.’

Quite a mouthful and even though we wouldn’t want to see an actual coredump we do need to fix this warning.
vCenter 5.1 now comes with a coredump & syslog server which integrates with vCenter (optional) and makes this a breeze.

On your vCenter server open the installer and install both options. Using the default options will work fine, for convenience I used the integrate into vCenter option on both.

Install

 

 

 

 

 

 

 

 

Once installed you have to activate them on your ESXi host. Make sure you do these steps before creating your Host Profile (or update it) so all host deployed later will get these settings on boot.
Open the configuration tab and select Security Profile. Click on Firewall Properties and check the syslog check box.

syslog

 

 

 

 

 

 

This will open ESXi firewall for outgoing traffic to the syslog server. Click OK and open Configuration – Software – Advanced Settings and scroll down to Syslog. Find Syslog.global.logHost and enter your syslogserver like: udp://your.syslogserver:514
Click OK and if all went fine, you’ll see you have one less warning in your host summary.

Fixing the second warning can be done in the actual Host Profile but I prefer to fix this before. We do need SSH access so click Configuration – Security Profile and select the Properties of the Security Profile. Select SSH and start it. If you want SSH access to remain after reboots select Start and stop with host.
This will add a new warning to the Summary which we’ll solve later on.

SSH

 

 

 

 

 

 

 

Now open up PuTTY connect your host, login as root and run the commands:
# esxcli system coredump network set --interface-name vmk0 --server-ipv4 10xx.xx.xx.xx --server-port 6500
replacing 10xx.xx.xx.xx with your core dump server.
Enable the new setting:
# esxcli system coredump network set --enable true

That’s it, no more warning on your host and when creating a Host Profile for deployment of more hosts these settings will be inherited.

To get rid of the SSH warning you could either stop the service or if you want to be able to connect to your host(s) with SSH simply open Configuration – Software – Advanced Settings and open UserVars. Scroll down to the bottom and at UserVars.SuppressShellWarning enter 1.

UserVars

Filed under: Esx Ailesi

Esx 5x’de usbarbitrator error hakkında…

Shell den esx e bağlanılır

 

chkconfig –list | grep -i usb komutu ile durum görülür, dah asonra chkconfig usbarbitrator off yapılarak server reboot edilir

Filed under: Esx Ailesi

ESXI 5.5 static mac address “conflicts with VMware reserved MACs”

esxi-error-5-mc-chang

You may see above error in ESXI 5.5 after changing dynamically generated MAC address to STATIC mac address dueto application MAC bind restriction.

In new ESXI 5.5 ,  new policies have been added where the statically assigned MAC addresses can only be in the range 00:50:56:xx:xx:xx series, If you try to change it to something else and then power on the guest machine, you may see above error.

Few days before, a friend of mine upgraded his ESXI from ver 5.0 to 5.5. One of his guest application was binded with the MAC address and the new esxi 5.5 doesn’t allow to use that specific series mac address. So I googled and found following solution that worked (at least for me 😉 )

To RESOLVE this issue, follow this.

1- Enable SSH in ESXI Server Configuration

2- Turn off the target guest machine and change the mac address as per your requirements for the required interface.

3- Turn off the V-Sphere ESXI client.

3- Login to ESXI server via SSH using any ssh client like PUTTY

4- Goto your data store / guest machine folder and open the VMX file.

.

For example I have guest machine with ‘123‘ name. So I used following

~ # cd /vmfs/volumes/
/vmfs/volumes # ls

52a18cdd-49376389-86aa-000c29d1de32  61031d71-0233e8da-be74-f942274c16c3
52a18ce5-9d0863e6-e50b-000c29d1de32  8901537a-ad66db83-fd1f-38ac926cce01
52a18ce7-bd9d6e2a-dacf-000c29d1de32  datastore1
/vmfs/volumes #

/vmfs/volumes # cd datastore1/
/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32 # ls
123

/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32 # cd 123
/vmfs/volumes/52a18ce5-9d0863e6-e50b-000c29d1de32/123 # ls

123-flat.vmdk               vmware-14.log
123.nvram                     123.vmxf                      vmware-15.log
123.vmdk                      vmware-11.log                 vmware-16.log
123.vmsd                      vmware-12.log                 vmware.log
123.vmx                       vmware-13.log

As showed in the image below . . .

3-putty-ssh

Now open the VMX file of the guest machine.

for example

1
vi 123.vmx

now press I and add this line anywhere.

1
ethernet0.checkMACAddress = "false"

(Change the ethernet0 to match your local ethernet number)

Now save and exit it by pressing :wq

Now start V-Sphere ESXI client and start the machine as you normally do 🙂

Congrats you are UP with new MAC address activated 😀

SAMPLE .VMX FILE FOR STATIC MAC address

Following is an sample of working .vmx file for static mac address.

1
2
3
4
5
ethernet0.networkName = "LAN"
ethernet0.addressType = "static"
ethernet0.present = "TRUE"
ethernet0.checkMACAddress = "false"
ethernet0.address = "00:0C:29:Ha:Ha:Ho"

Filed under: Esx Ailesi

Esx vcenter portları

80 : HTTP isteklerine cevap vermesi için 80 port’ unun açık olması gerekmektedir.

389 : LDAP port’udur.vCenter makinanız domain’ e dahil ise zaten açık olmak zorundadır.

443 : HTTPS isteklerine cevap vermesi için 443 port’unun açık olması gerekmektedir.

636 : vCenter Linked mode olarak çalışacak ise bu port açık olmak zorundadır.

902 : vCenter Server ‘ın default portudur.Dataların host’lara gönderilmesi için gereklidir.

903 : Eğer bu port engelli ise vSphere Client ile host’lara bağlanmada sorun yaşarsınız hatta bağlanamazsınız.

8080 : HTTP Web servisidir.Vmware VirtualCenter Management Web servisi bu port’u kullanmaktadır.

8443 : HTTPS Web servisidir.Vmware VirtualCenter Management Web servisi bu port’u kullanmaktadır.

60099 : Web Service değiştiğinde uyaran port’dur.

6501 : Auto Deploy servisi.

6502 : Auto Deploy yönetimi.

7005 : vCenter Single Sign On

7009 : vCenter Single Sign On

7080 : vCenter Single Sign On

7444 : vCenter Single Sign On HTTPS

9443 : vCenter Web Client HTTPS

9090 : vSphere Web Client HTTP

10080 : vCenter Inventory Service HTTP

10443 : vCenter Inventory Service HTTPS

10111 : vCenter Inventory Service Management

10109 : vCenter Inventory Service Linked Mode

Filed under: Esx Ailesi