new1234.jpg

Archive

Posts Tagged ‘vCenter 5.5’

VMware: There is a problem authentication into the legacy vCenter Server using credentials provided by the user

May 16th, 2015 1 comment

During upgrade VMware vCenter Server 5.5.0 (based on Windows 2012R2) to 6.0.0 I received a warning message:

Error: There is a problem authenticating into the legacy vCenter Server using the credentials provided by the user.

Resolution: Check if vCenter Server is up and running. Double check provided vCenter Server credentials

 
VMpros.nl

 
Some troubleshooting:

  • All VMware vCenter Server Services are started
  • No warnings/errors in Microsoft Event Logs during setup
  • I can logon at the vSphere webinterface with credentials administrator@vsphere.local
  • When configure wrong SSO password in setup the setup says "The vCenter Single Sign-On credentials are not valid. Check the username and password and try again"
  • I can ping domain controller VMpros.local
  • I canceled the setup and generated a support file, at the time I received the warning message this setup log was generated, so far, nothing special:

MSI (c) (40:88) [17:15:28:813]: Invoking remote custom action. DLL: C:\Users\ADMINI~1.VMP\AppData\Local\Temp\MSI7329.tmp, Entrypoint: LaunchUpgradeRunnerPreUpgradePhase
MSI (c) (40!C8) [08:23:44:055]: PROPERTY CHANGE: Modifying PreUpgradeComplete property. Its current value is ‘0’. Its new value: ‘1’.
MSI (c) (40:D0) [08:23:47:186]: PROPERTY CHANGE: Modifying SSO_PASSWORD property. Its current value is ‘**********’. Its new value: ‘**********’.
MSI (c) (40:D0) [08:23:47:267]: PROPERTY CHANGE: Modifying VC_5X_PASSWORD property. Its current value is ‘**********’. Its new value: ‘**********’.
MSI (c) (40:D0) [08:23:47:288]: PROPERTY CHANGE: Modifying PreUpgradeComplete property. Its current value is ‘1’. Its new value: ‘0’.
MSI (c) (40:D0) [08:23:47:305]: Doing action: VM_LaunchUpgradeRunnerPreUpgradePhaseAsync

 

Solution

Reboot the vCenter Server… I restarted the setup and the installation can continue.. weird!

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Upgrade vCenter Server 5.5 to 6.0

March 29th, 2015 5 comments

Last week I upgraded VMware vCenter 5.5 server (based Windows 2012R2) at the company environment I work for, the upgrade was very simple.

Pre-install: Please check article “Minimum requirements for the VMware vCenter Server 6.x Appliance (2106572)

 
Installation process

clip_image002

– Select: Install

Read more…

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Host IPMI System Event Log Status alarm is triggered repeatedly in VMware vCenter Server

January 22nd, 2015 2 comments

image

 

Solution

To resolve this issue, stop the alarm from triggering repeatedly and clear the IPMI System Event.log file and reset the sensors.

To clear the IPMI System Event.log file and reset the sensors:

  1. Open vCenter Server using vSphere Client.
  2. In the vCenter Inventory, select the ESXi/ESX host.
  3. Click the Hardware Status tab.
  4. Click System Event log under View.
  5. Click Reset Event Log. The red alert is removed from the System Event log.
  6. Click Reset Sensors to reset the host sensors.

Introduced in ESXi 5.1 Update 2 (Build Number: 1483097) and ESXi 5.5 Patch 1 (Build Number:  1474528), there is a new localcli command line to clear the IPMI SEL logs:

localcli hardware ipmi sel clear

To run localcli command on the ESXi 5.1 or 5.5 host:

  1. Connect to the ESXi host via SSH. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
  2. Run this command:
  3. localcli hardware ipmi sel clear

image   
More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Manual set static IP-address to vCenter Appliance (VCSA)

January 19th, 2015 1 comment

When deploying the VMware vCenter Server Appliance (VCSA) it will default look for a DHCP address. When there is no DHCP server available the following error is displayed:

image

NO NETWORKING DETECTED, PLEASE LOGIN AND RUN THE COMMAND /opt/vmware/share/vami/vami_config_net TO CONFIGURE THE NETWORK

 

Solution

1. Press F2 to login

2. Enter default username: root

3. Enter default password: vmware

4. Run command: /opt/vmware/share/vami/vami_config_net

5. Press 6 to setup eth0

image

6. After allocate a static IP Address to the VCSA the post configuration can be done by using the following URL: 

https://static-ip-address:5480

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Nesting Hyper-V 2012 R2 on vSphere ESXi 5.5

August 28th, 2014 3 comments

In my test environment I configured tree Hyper-V 2012R2 servers nested on vSphere 5.5,  the configuration was very easy, here some details:

1. Deploy a Windows 2012R2 server, use GuestOS Windows 2012 (64-bit)

2. Upgrade hardware level to version 10

3. Remove the virtual machine from the vCenter inventory

4. Download and edit the .vmx file, add the following lines:

vhv.enable = “TRUE”
hypervisor.cpuid.v0 = “FALSE”
mce.enable = “TRUE”

 image

5. Upload and re-add the .vmx file to the vCenter inventory

6. Edit the virtual machine hardware > CPU > Hardware virtualization> select: Expose hardware assisted virtualization to the guest OS

*Note: you need to upgrade to HW level 10, otherwise the hardware virtualization tab is grayed out.

 image

7. Power on the virtual machine

8. Now you are able to select the Hyper-V role, finish the setup

image

 

Ejoy!

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Cannot remove a License Key from VMware vCenter Server

August 23rd, 2014 5 comments

Last week I upgraded a vCenter Server from version 5.1 to 5.5, I also added a 4th hosts to the cluster, so I need to upgrade the host license keys. But after upgrade I couldn’t remove the license files in vCenter Licensing section:

image

 

Solution:

To connect to the ADAM database:

  1. Log in to the vCenter Server.
  2. To open ADSI Edit, click Start > Run, type adsiedit.msc, and press Enter.
  3. Right-click ADSI Edit and click Connect to.
  4. In the Connection point section, click Select or type a Distinguished Name or Naming Context.
  5. Enter dc=virtualcenter, dc=vmware, dc=int
  6. In the Computer section, click Select or type a domain or server: (Server | Domain [:port]).
  7. Enter localhost
  8. Click OK.
  9. Drill down to DC=virtualcenter,DC=vmware,DC=int, OU=Licensing, OU=LicenseEntities.You see the CN="license key" containers.
  10. Right-click the container that shows the the serial number of the key that is negative within the vCenter Server Licensing page.
  11. Click Delete.

image

 

Result:

When you restart he vSphere client and navigate to the Licensing page the old license keys are removed and you can re-assign license keys to the hosts

image

 

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Update vCenter Server appliance

January 24th, 2014 No comments

Last week I updated my vCenter Server Appliance in my homelab, this was too easy:

– Browser: http://vcentername:5480
– Login with root / admin (if AD integrated) credentials
– Tab: Update, click: Check updates
– Available updates: appliance version: 5.5.0.5201 build 1476389 (current: 5.5.0.5100 build 1312297)

image

– Click: Install updates

 

image

– Installing updates..

 

image

– Appliance update is completed, reboot the appliance

 

Status:

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Configure vSphere hosts to VMware Syslog Collector with PowerCLI

December 18th, 2013 2 comments

PowerCLI script:

 

#====================================================================#
#   SCRIPT:        PowerCLI_configure_syslog_settings_host.ps1       #
#   FUNCTION:      Add remote syslog server, settings and  open      #
#                  firewall ports in cluster                         #
#   OWNER:         Sander Daems                                      #
#   VSPHERE:       5.5 build 1331820                                 #
#   CREATED:       18/12/2013                                        #
#   MODIFIED:      18/12/2013                                        #
#   VERSION:       v.1.0                                             #
#====================================================================#
#   CHANGELOG:                                                       #
#                                                                    #
#    v.1.0                                                           #
#    - Script created;                                               #
#                                                                    #
#====================================================================#
# CUSTOM DEFINITIONS                                                 #
#====================================================================#
$vCenterServer = Read-Host "Enter vCenter Hostname / IP"
$vmhost = Get-VMHost
#====================================================================#
# HOST - Specify host and connect                                    #
#====================================================================#
Connect-VIServer $vCenterServer
#====================================================================#
# SCRIPT - SYSLOG - Update Syslog settings                           #
#====================================================================#
$vmhost | Set-VMHostAdvancedConfiguration -NameValue @{'Config.HostAgent.log.level'='info';'Vpx.Vpxa.config.log.level'='info';'Syslog.global.logHost'='udp://10.180.200.18:514'}
#====================================================================#
# SCRIPT - FIREWALL - Open ESXi firewall port                        #
#====================================================================#
$vmhost | Get-VMHostFirewallException -VMhost $vmhost -name syslog | Set-VMHostFirewallException -Enabled $true
#====================================================================#

 

vCenter Syslog Collector settings:

 

image


Script result:

image

image

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn

VMware: Quick stats on “hostname” is not up-to-date

December 18th, 2013 No comments

Today I received some warnings at my new installed vSphere 5.5 hosts, the warning message:

Configuration issues. "Quick stats on hostname is not up-to-date"

VMpros

 

Solution:

This is a known issue in vCenter Server 5.5.

To work around this issue, add these quickStats parameters to the Advanced Settings of the vCenter Server:

  • vpxd.quickStats.HostStatsCheck
  • vpxd.quickStats.ConfigIssues

image

 

Note: Adding these parameters to the vCenter Server will not affect future upgrades.

To add the quickStats parameters to the Advanced Settings of the vCenter Server:

  1. In the vSphere Web Client, navigate to the vCenter Server instance.
  2. Select the Manage tab.
  3. Select Settings > Advanced Settings.
  4. Click Edit.
  5. In the Key field, enter this key: vpxd.quickStats.HostStatsCheck
  6. In the Value field, enter: False
  7. Click Add.
  8. In the Key field, enter this key: vpxd.quickStats.ConfigIssues
  9. In the Value field, enter: False
  10. . Click Add.
  11. . Click OK.
  12. . Restart the vCenter Server service.

More information: VMware

sanderdaems

Sander Daems is founder and author of this blog and working as a Sr. Infrastructure Consultant by IT-Value. Sander has over 10 years experience in IT, primary focus: virtualization, storage and SBC

More Posts - Website

Follow Me:
TwitterLinkedIn