No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


SingleCLOUD-VDI-wrong DNS setting lead to all VMs can not login

Publication Date:  2015-04-29 Views:  63 Downloads:  0
Issue Description
All client (think client, web interface) can connect to the virtual machines.When click VM icon, message “VDI its currently unavailable .Try reconnect.......” will appear.
Alarm Information
1 Desktop studio can not be open
2 SQL database status is ‘in recovery’
3 OMS Portal Alarm
Handling Process
1 Change internet DNS IP to internal local DNS ip.

2 Login local DNS server, add internal DNS IP as forwarder.
3 Refer to GPI document > Fault and Alarm > Vdesktop6000 Alarm > Vdesktop6000 component alarm > 16.1000003, Restore DB relationship.
Root Cause
Wrong DNS configuration lead to main DB, slave DB and witness DB cannot communicate with each other(external DNS willanalysis them as in different domain) .
They cannot build mirrored relationship, so they generate a large number of database logs which fully occupy the DB server disk. The DDC cannot
query the actual registration status of the Virtual Desktop Agent (VDA) from the MSSQL2008. The VDA registration status displayed on the DDC is
not registered. Therefore, users cannot log in to the newly connected or reconnected VMs from software clients or thin clients due to the unregistered VDA. Moreover, VMs cannot be created on the ITA.
Internet DNS IP can’t be configued as VDI infrusturcture server DNS IP. In order to access to internet, this DNS IP should be set as DNS forwarder.