Virtual Machine Grey Out

Virtual Machine Grey Out and Can’t control on vcenter level / host level you can check with this command

Do this Step as below :
1. ssh session to host which vm have error / direct to console and cli to host
2. Do this command cli as below :
vim-cmd vmsvc/getallvms

show any message with this :
Skipping invalid VM ’22’
Vmid

(this virtual machine vmx id 22 grey out already) so we have solve this with next step

3. You have reload the inventory id,
vim-cmd vmsvc/reload inventory-vmx-id

example command line :

vim-cmd vmsvc/reload 22

note : inventory id = 22

If you have many vm’s happen you just ssh to your each host then do

vim-cmd vmsvc/getallvms
**check any invalid VM vmx id
vim-cmd vmsvc/reload inventory-vmx-id

I hope my blog can help solve your problem

The VMware vCenter Site Recovery Manager Server service on Local Computer started and then stopped. Some services Stop automatically if they are not use by other services or program

This Error happen after change password database on your DB SRM, Please do this step as below :

Please check event viewer :

Is it show this message : “DBManager error: Could not initialize Vdb connection: ODBC error: (28000) – [Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user ‘your db user name’. ”

Then Make Sure your setting in odbc connectivity to the VMware vCenter Site Recovery Manager database:

  1. Verify if the system DSN is configured to connect to the right SQL instance and that it points to the SRM database.
  2. Ensure that the ODBC connection is 32-bit.
    • On a 32 bit machine, click Start > Programs > Administrative Tools > Data Sources (ODBC).
    • On a 64 bit machine, browse to %systemroot%\sysWOW64\ and click odbcad32.exe.
  3. Ensure the appropriate credentials are used to access the database.
  4. The SRM database can reside either on the same machine where the SRM is installed or on a remote host. If the database is hosted remotely, SQL authentication must be used.
  5. Test if ODBC connectivity is successful.Note: There is an option to test connectivity to the database when you edit the DSN or reconfigure.
  6. we do with tools of SRM, open CMD, cd \ C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin>
  7. Do Command on above CMD –>  installcreds.exe -key db:new_SRM_DSN -u Admin_user
  8. Start service on SRM server

How Setup Syslog on Host ESXI

Prequsition action :

* Activate ssh on each host and do ssh access to each host

* Prepare for syslog server on this case syslog server with ip 192.168.1.220

KB install vsphere syslog collector :

https://pubs.vmware.com/vsphere-50/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc_50%2FGUID-471EFE67-9035-473E-8217-6B67E493A518.html

On Each Host do this step as below :

  1. Before change any setting as below :
    ~ # esxcli system syslog config get
    Default Rotation Size: 1024
    Default Rotations: 8
    Log Output: /scratch/log
    Log To Unique Subdirectory: false
    Remote Host:
  2. esxcli system syslog config set –loghost=’udp://192.168.1.220:514′
  3. esxcli system syslog config set –logdir-unique true
  4. check configuration after change config as below :
    ~ # esxcli system syslog config get
    Default Rotation Size: 1024
    Default Rotations: 8
    Log Output: /scratch/log
    Log To Unique Subdirectory: true
    Remote Host: udp://192.168.1.220:514
  5. esxcli system syslog reload
  6. nc -z 192.168.1.220 514
    if work will show this –> Connection to 192.168.1.220 514 port [tcp/shell] succeeded!
  7. Testing initiate test syslog
    esxcli system syslog mark –message ” SYSLOG TESTING VMWARE `date` “
  8. Show configuration as below :
    esxcli system syslog config get
    Default Rotation Size: 1024
    Default Rotations: 8
    Log Output: /scratch/log
    Log To Unique Subdirectory: true
    Remote Host: tcp://192.168.1.220:514
  9. After do all task as above now to enable on firewall
    From esxi client console –> Host –> Configuration –> Security Profile –> Firewall –> Enable on syslog (port udp/tcp:514) just check on that settings.

Reference KB :

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2003322

Thanks

Purwandi

A general system error occurred: Missing datatstore for backing file ds:///vmfs

This Error appear when we do vmotion on vcenter from host A to host B

Completely error “A general system error occurred: Missing datatstore for backing file ds:///vmfs
/volumes/datastore-name/vm-name(id-vmname)/vm-name
(id-vmname).vmdk

Symtoms :

•Changes are not recognized in vCenter Server when you edit a virtual machine’s .vmx file.
•If you use the Remove from Inventory option to remove the virtual machine, you must re-add it manually with the datastore browser which generates a new Inventory ID

Cause :

The virtual machine’s .vmx configuration file can be reloaded from the command line. This operation does not generate a new Inventory ID (Vmid) for the virtual machine and allows it to stay in the same resource pool.

You can do migrate without powering off the vm’s.

Do this Step as below :
1. ssh session to host which vm have error / direct to console and cli to host
2. Do this command cli as below :
vim-cmd vmsvc/getallvms | grep -i name-of-vm
3. You can see which vm that you grep like this “shown the number of inventory id inventory-vmx-id
inventory-vmx-id vm-name(id-vmname)[datastore-name] vm-name (id-vmname)/vm-name id-vmname).vmx Operating System Guest vmx-08

4. You have reload the inventory id,
vim-cmd vmsvc/reload inventory-vmx-id

example command line :

vm name have error : avenger007(10a96b15-a18d-4ca7-a460-9f1c0ddbc919)

~ # vim-cmd vmsvc/getallvms |grep -i avenger007
339      avenger007(10a96b15-a18d-4ca7-a460-9f1c0ddbc919)[DATASTORE01] avenger007 (10a96b15-a18d-4ca7-a460-9f1c0ddbc919)/Windows-WINSRV-R2-2008-ENT-64bit(10a96b15-a18d-4ca7-a460-9f1c0ddbc919).vmx windows7Server64Guest vmx-08
~ # vim-cmd vmsvc/reload 339

note : inventory id = 339

If you have many vm’s happen you just ssh to your each host then do

vim-cmd vmsvc/getallvms | grep -i name-of-vm
vim-cmd vmsvc/reload inventory-vmx-id

I hope my blog can help solve your problem

KB Link “http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026043”

Thanks

Purwandi

An I/O error occurred while saving the checkpoint: 0 (Resource temporarily unavailable) Failed to write checkpoint data (offset 42876928, size 16384): Failed to resume VM. Module Migrate power on failed. vMotion migration failed. The checkpoint data length (16384 bytes) or the offset (41943040 bytes) exceeds the maximum checkpoint data length (41943040 byte)

This error appear when we do vmotion on host.
This case happen on esxi 5.0 but solve on 5.0 update 1. You should do this action as below :

This issue has been resolved in ESXi 5.0 Update 1.

To work around this issue on ESXi 5.0, use one of these options:

• Change the resolution to a single screen of 1280 x 1024 or smaller before using vMotion for migration.
• Do not upgrade to Virtual Machine Hardware version 8.
• Increase the base checkpoint cache size. Doubling this value from its default of 8 MB to 16 MB (16777216 bytes) should be enough for any display resolution. If you are using two displays at 1600 x 1200 each, increase the setting to 20 MB (20971520 bytes).

To increase the base checkpoint cache size:
1. Power off the virtual machine.
2. Click the virtual machine in the Inventory.
3. On the Summary tab for that virtual machine, click Edit Settings.
4. In the virtual machine Properties dialog box, click the Options tab.
5. Under Advanced, select General and click Configuration Parameters.
6. Click Add Row.
7. In the new row, add migrate.baseCptCacheSize to the name column and add 16777216 to the value column.
8. Click OK to save the change.

Note: If you don’t want to power off your virtual machine to change the resolution, you can also append migrate.baseCptCacheSize = 16777216 to the /etc/vmware/config file on the target host. This adds the option to every VMX process that is spawning on this host, which happens when vMotion is starting a virtual machine on the server.
• Set mks.enable3d = TRUE for the virtual machine:
1. Power off the virtual machine.
2. Click the virtual machine in the Inventory.
3. On the Summary tab for that virtual machine, click Edit Settings.
4. In the virtual machine Properties dialog box, click the Options tab.
5. Under Advanced, select General and click Configuration Parameters.
6. Click Add Row.
7. In the new row, add mks.enable3d to the name column and add True to the value column.
8. Click OK to save the change.

Caution: This workaround increases the overhead memory reservation by 256 MB. As such, it may have a negative impact on HA Clusters with strict Admission Control. However, this memory is only used if the 3D application is active. If, for example, Aero Basic and not Aero Glass is used as a window theme, most of the reservation is not used and the memory could be kept available for the ESXi host. The reservation still affects HA Admission Control if large multi-monitor setups are used for the virtual machine and if the CPU is older than a Nehalem processor and does not have the SSE 4.1 instruction set. In this case, VMware does not recommend using 3D. The maximum recommended resolution for using 3D, regardless of CPU type and SSE 4.1 support, is 1920 x 1200 with dual screens.

Reference :

KB vmware

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2005741

Hopely this help your problem.

Mailbox Stopped, zmmailboxdctl is not running

This error i found with our zimbra :

I found in services, with su zimbra

zmcontrol status

antispam Running
antivirus Running
ldap Running
logger Running
mailbox Stopped
zmmailboxdctl is not running.
mta Running
opendkim Running
spell Running
stats Running
zmconfigd Running

 

Log ini /var/log/zimbra.log

bash# tail -f /var/log/zimbra.log
Oct 19 16:33:27 mail zmmailboxdmgr[31797]: assuming no other instance is running
Oct 19 16:33:27 mail zmmailboxdmgr[31797]: did not find a number in /opt/zimbra/log/zmmailboxd.pid
Oct 19 16:33:27 mail zmmailboxdmgr[31797]: assuming no other instance is running
Oct 19 16:33:27 mail zmmailboxdmgr[31797]: no manager process is running
Oct 19 16:33:27 mail zmconfigd[15249]: Executed: /opt/zimbra/bin/zmmailboxdctl status norewrite returned 1 (25 – 13) (0.02 sec)
Oct 19 16:33:27 mail zmconfigd[15249]: Tracking service mailboxd
Oct 19 16:33:28 mail zmconfigd[15249]: Watchdog: service antivirus status is OK.
Oct 19 16:33:28 mail zmconfigd[15249]: All rewrite threads completed in 0.00 sec
Oct 19 16:33:28 mail zmconfigd[15249]: All restarts completed in 0.00 sec

then i check port with netstat -ntlp | grep LISTEN

bash# netstat -ntlp | grep LISTEN

tcp 0 0 0.0.0.0:32771 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 39095/java
tcp 0 0 127.0.0.1:7171 0.0.0.0:* LISTEN 37914/java
tcp 0 0 0.0.0.0:32772 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:7780 0.0.0.0:* LISTEN 39596/httpd
tcp 0 0 0.0.0.0:40421 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:32773 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 118.91.130.35:389 0.0.0.0:* LISTEN 37765/slapd
tcp 0 0 0.0.0.0:32774 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 127.0.0.1:10663 0.0.0.0:* LISTEN 39033/zmlogger: zmr
tcp 0 0 0.0.0.0:1991 0.0.0.0:* LISTEN 870/sshd
tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN 39266/amavisd (mast
tcp 0 0 0.0.0.0:31337 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 39873/master
tcp 0 0 127.0.0.1:10026 0.0.0.0:* LISTEN 39266/amavisd (mast
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN 39021/mysqld
tcp 0 0 0.0.0.0:6667 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:11 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 127.0.0.1:10027 0.0.0.0:* LISTEN 39873/master
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 39873/master
tcp 0 0 127.0.0.1:10028 0.0.0.0:* LISTEN 39873/master
tcp 0 0 127.0.0.1:10029 0.0.0.0:* LISTEN 39873/master
tcp 0 0 0.0.0.0:5742 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 127.0.0.1:10030 0.0.0.0:* LISTEN 39873/master
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:79 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:15 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:54320 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:2000 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 39266/amavisd (mast
tcp 0 0 127.0.0.1:80 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:27665 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 1886/smtpd
tcp 0 0 127.0.0.1:8465 0.0.0.0:* LISTEN 39429/opendkim
tcp 0 0 0.0.0.0:7025 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:1524 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 118.91.130.35:53 0.0.0.0:* LISTEN 1004/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 1004/named
tcp 0 0 0.0.0.0:119 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:1080 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:12345 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 3293/smtpd
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 1004/named
tcp 0 0 0.0.0.0:12346 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:635 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:49724 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:540 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:7071 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:7072 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:1 0.0.0.0:* LISTEN 48293/portsentry
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 39095/java
tcp 0 0 0.0.0.0:20034 0.0.0.0:* LISTEN 48293/portsentry
tcp6 0 0 :::1991 :::* LISTEN 870/sshd
tcp6 0 0 :::53 :::* LISTEN 1004/named
tcp6 0 0 ::1:953 :::* LISTEN 1004/named

 

i assume portsentry is block zimbra mailbox up service than i do stop services

bash# /etc/init.d/portsentry stop

than i do restrat service zimbra , with su zimbra command zmcontrol restrart

than i check zmcontrol status of mailbox

zmcontrol status
Host xxx.xxx.net
antispam Running
antivirus Running
ldap Running
logger Running
mailbox Running
mta Running
opendkim Running
snmp Running
spell Running
stats Running
zmconfigd Running

so our mailbox up again because of portsentry services. My Suggest is if you use portsentry let all services zimbra up first and than you up again portsentry services.

Thanks

I hope my blog help you thanks

Betapa Praktisnya Membangun Server Development di Cloud

Tidak bisa dipungkiri lagi bahwasanya ketika kita membutuhkan testing pada aplikasi development tentunya kita harus menyiapkan server dalam bentuk fisik ataupun virtual.

Nah, ketika kita menyiapkan dalam bentuk fisik kita mesti perhitungkan secara matang mulai dari request,purchase dan implementasi paling cepat umumnya lebih dari 2 minggu.

Katakanlah hardwarenya masih indent bisa jadi waktu yang dibutuhkan lebih dari 2 bulan bahkan bisa 3 bulan.

Begitu pula ketika akan membangun infrastruktur virtualisasi pun kita harus menyiapkan server,storage,network,device dan lain-lain. Waktu yang dibutuhkan cukup panjang.

Kenapa server development harus dibuat di cloud? Apa pertimbangan anda? Coba kita tanya sama Mr. IC buat hal ini.

Mr.IC menjawab, Anda tidak usah pusing memutuskan terkait test development, dalam hitungan menit bahkan detik untuk menyiapkan server yang anda butuhkan dengan fitur dan spesifikasi sesuai yang anda kehendaki.

Wow hitungan menit bahkan detik. Apa alasannya?

Berikut ini alasannya:

Cloud Provider sudah menyiapkan resources capacity server yang anda minta meliputi : RAM, CPU, Harddisk, Network, Security dan Disaster Recovery.

Anda bisa memakai server anda sesuai dengan yang anda butuhkan bahkan anda bisa naik-turunkan kapasitas RAM, CPU (Prosesor) dan harddisk (red: tergantung operating system) kebutuhan anda dalam hitungan menit bahkan detik, sekali lagi anda tidak pusing memikirkan hardwarenya.

Anda lebih cepat dan mudah memutuskan apakah aplikasi layak untuk dikembangkan atau tidak.

Anda akan bisa membuat perencanaan produksi di cloud juga. Tentunya ketika anda sudah mendapatkan banyak benefit pada saat menggunakan server development di cloud.

Anda tidak perlu memikirkan kondisi kinerja server seperti apa karena cloud provider sudah memiliki monitoring tools yang intelligent (pintar) dalam memonitor kinerja server anda.

Billingnya pun akan sesuai dengan kapasitas yang anda gunakan. Investasi di level hardware jika perhitungan tidak matang akan menyebabkan ketidaksesuaian dengan ekspektasi anda, developmentpun penggunaannya tidaklah lama sehingga akan terjadi over budget.

Nah, alasan tadi bukanlah mengada-ada akan tetapi sudah menjadi layanan yang sudah pasti disediakan secara totalitas dan menyeluruh.

Jadi alasan apa untuk tidak menggunakan cloud sebagai server development anda?

Space ruangan kantor anda lebih efesien karena server anda ada di cloud, pengeluaran listrik anda tidak membengkak karena server anda di cloud,anda bisa menekan budget untuk tenaga IT professional anda karena server anda di cloud, bahkan budget pengadaan hardwarepun tidak diperlukan lagi ketika anda menggunakan cloud.

Anda tidak perlu memusingkan kendala hardware,performance,network dan segudang persiapan anda dalam membangun infrastruktur baru sementara waktu pemakaian hanya sementara (ketika tahap server development sudah OK, akan berlanjut ke server production, tergantung dari penilaian dan kelayakan).

Selamat buat anda yang telah membaca blog ini, semoga menambah referensi dalam mengambil keputusan. Sebenarnya yang bisa dibuat di cloud tidak hanya server development saja yang bisa dibangun, tetapi server productionpun bisa dibangun di cloud. Setahu saya layanan cloud itu tidak murah akan tetapi sesuai dengan kontinuitas bisnis anda yang nyaris tanpa berhenti

Saya bisa tahu hal ini karena Mr. IC yang banyak memberikan pandangan kepada saya tentang Cloud Computing.

Motto untuk Postingan blog kali ini : “Ketika anda berencana membangun server development, pakailah cloud lalu perhatikan apa yang terjadi”.