Archive for June, 2013


Experiencing this issue first thing in the morning while provisioning some VD in an existing pool . Then also tried to create a new pool and issue remains the same . Tried the following KB from vmware but doing some mistake at the end while editing pae_moid attribute . Please note you need to put vm-<MOID> to get it work . I need to log call with vmware support for this .

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

In View Administrator a View desktop has a status of “Provisioned (Missing)”

Symptoms

  • In View Administrator, a View desktop has a status of Provisioned (Missing).
  • In vCenter, the View desktop is present and is fully functional.
  • You cannot log in into the View desktop.

Cause

A common cause for this issue is if a vSphere/vCenter administrator had previously removed a View VM from inventory and later added it back into inventory. This can cause the View VM to get a different MOID (Managed Object¬†ID) within vCenter. The VM’s MOID now differs between the vCenter database and VMware View’s ADAM database.

Resolution

To resolve this issue, you must make the VM’s MOID in the ADAM database match the vCenter MOID. To make the MOIDs match:

Note: The MOID in vCenter is in the form of a number. In the ADAM database, the number is preceded by vm-.

  1. Determine the VM’s MOID within the vCenter Database:
    1. Connect to the vCenter Database.
    2. Execute this query:

      Select id from vpx_entity where name='<Name of the VM>'

      This returns the VM’s MOID as seen by vCenter.

  2. Determine the VM’s MOID in the ADAM database on the View Connection Server:
    1. Log in to the machine hosting your VMware View Connection Server through the VMware Infrastructure Client or Microsoft RDP.
    2. Open the ADAM Active Directory Service Interfaces Editor:
      • Windows 2003: Go to Start > Programs > ADAM > ADAM ADSI Edit.
      • Windows 2008: Go to Start > All Programs >Administrator Tools > ADSI Edit.
    3. Right-click ADAM ADSI Edit and click Connect to.
    4. Ensure that Select or type a domain or server is selected and that Destination points to localhost.
    5. Select Distinguished Name (DN) or naming context
    6. Type dc=vdi, dc=vmware, dc=int.
    7. Run a query against OU=Servers, DC=vdi, DC=vmware, DC=int with this string:

      (&(objectClass=pae-VM)(pae-displayname=<Virtual Machine name>))

      Note: The <Virtual Machine Name> can use * or ? as a wildcard to match multiple desktops.

    8. Double-click the CN record for the VM you want to edit.
    9. Scroll down until you see the pae-MOID attribute.
    10. Double-click pae-MOID
    11. Change the pae-MOID to match the VM’s MOID as seen in vCenter.
    12. Restart the Connection Server service for the changes to take effect.
Advertisements

1 – Allow the vlan to the physical interface on Cisco core switch ( Find out what ports and port channel are use for uplink from Blade switch ) ( eg gi3/45,gi4/45,gi5/45 )

– switchport trunk allowed vlan add XXX

-Add it to the port-channel that the interface is in (same command as above)

2 – Create the VLAN on blade switch ( if not already exists ). Exam ple below to add vlan 110 :

– (AUGS-PCHAS02-SW07)#conf

(AUGS-PCHAS02-SW07)(Config)#vlan dat

(AUGS-PCHAS02-SW07)(Vlan)#vlan 110

(AUGS-PCHAS02-SW07)(Vlan)#vlan name 110 User110

(AUGS-PCHAS02-SW07)(Vlan)#exit

3 РAllow the VLAN  on interface range

-(AUGS-PCHAS02-SW07)(Config)#int range 0/1 – 0/48
(AUGS-PCHAS02-SW07)(if-range)#sw allowed vlan add 110
(AUGS-PCHAS02-SW07)(if-range)#sw tagg 110
(AUGS-PCHAS02-SW07)(if-range)#exit

 

4 – Allow and tag the vlan on port channel .

(AUGS-PCHAS02-SW07)(Config)#int 1/1

(AUGS-PCHAS02-SW07)(Interface AUGS-PCHAS02-SW07/1/1)#sw allowed vlan add 110

(AUGS-PCHAS02-SW07)(Interface AUGS-PCHAS02-SW07/1/1)#sw tagg 110

(AUGS-PCHAS02-SW07)(Interface AUGS-PCHAS02-SW07/1/1)#exit

(AUGS-PCHAS02-SW07)(Config)#exit

5- Copy the config


(AUGS-PCHAS02-SW07)#copy run start
Configuration Saved!