Monthly Archives: August 2015

vCenter Server 5.5 fails to start after reboot

VMware VirtualCenter Server service unable to start after vCenter server reboot,

In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file you see  similar logs :
[04928 info ‘[SSO][CreateSsoFacade]’] [CreateUserDirectory] STS URI set to: https://vCenter_Server_FQDN:7444/sts/STSService/vsphere.local
[04928 info ‘[SSO][CreateSsoFacade]’] [CreateUserDirectory] Admin URI set to: https://vCenter_Server_FQDN:7444/sso-adminserver/sdk/vsphere.local
[04928 info ‘[SSO][CreateSsoFacade]’] [CreateUserDirectory] Groupcheck URI set to: https://vCenter_Server_FQDN:7444/sso-adminserver/sdk/vsphere.local
[02396 error ‘[SSO][SsoFactory_CreateFacade]’]
Unable to create SSO facade: Invalid response code: 404 Not Found.
[02396 error ‘vpxdvpxdMain’]
[Vpxd::ServerApp::Init] Init failed:
Vpx::Common::Sso::SsoFactory_CreateFacade(sslContext, ssoFacadeConstPtr)
–> Backtrace:
–> backtrace[00] rip 000000018018cd7a
–> backtrace[01] rip 0000000180106c48
–> backtrace[02] rip 000000018010803e

To work around this issue, restart the VMware Secure Token Service:
Log in as an administrator to the server that is running vCenter Server.

  1. Click Start > Run, type services.msc, and click OK. The Services window opens.
  2. Stop these services:

    VMware Secure Token Service
    VMware Identity Management Service
    VMware Certificate Service
    VMware KDC Service
    VMware Directory Service.

  3. Start these services:

    VMware Identity Management Service
    VMware Certificate Service
    VMware KDC Service
    VMware Directory Service
    VMware Secure Token Service
    VMware VirtualCenter Server

Please follow the KB 2061412 for more info.

 

Advertisements

Unable to connect to the requested VDP appliance

Today I came across a situation where I am unable to connect to my VDP appliance and come up with below error.

vdp-error

 

 

there is no problem connecting to VDP configuration.

  • In the /usr/local/avamar/var/vdr/server_logs/vdr-server.log file, you see an entry similar to:

    YYYY-MM-DD HH:MM:SS,MS ERROR [com.abc.vdr.server.VDRServer$1]-server.VDRServer: VDRServer.getVCenterClient cannot obtain VCenterClient  java.lang.NullPointerException: VCenterClient list is empty

  • Also in the vdr-server.log file, you may see an entry similar to:

    YYYY-MM-DD HH:MM:SS,MS INFO [http-xxxx-exec-x] -impl.X509TrustChainKeySelector: Failed to find trusted path to signing certificate. 

Resolution:

This issue occurs with the date and time doesn’t match with VDP appliance and vCenter server or ESXi host.

Check the ntp settings are configured correctly on your VC and ESXi hosts. To resolve the issue stop the MCS service on the VDP appliance and start it again .
#dpnctl stop mcs

Once stopped start it again

#dpnctl start mcs

Please follow the KB Could not connect to the requested VDP appliance

 

 

 

 

Cisco UCS – CIMC did not detect storage controller error

Virtual Notions

During a recent UCS firmware upgrade I had quite a few blades show up with the error “CIMC did not detect storage”. Within UCSM I could see that the blade had a critical alert. It initially started after I upgraded UCS Manager firmware as documents in a previous post I wrote about UCS Firmware Upgrades. I did some searching around to find what may be causing the issue and the best answer I could find was to from the Cisco community forums to disassociate the blade, decommission and reseat within the chassis. I later spoke to a Cisco engineer and he advised of the same steps but that it was also possible to do without reseating the blade. This also looks like its a problem when upgrading from 2.2(1d) to other versions of UCSM but I haven’t been able to validate if it’s only that version or if it…

View original post 253 more words