Skip to main content

Issue: Connect-VIserver Could not connect using the requested protocol.

 

Some time back I had an issue while I tried to connect my Vcenter from powercli but unable to connect and getting below error


 ##################################################
Connect-VIServer :  6/08/2015 3:31:27 AM        Connect-VIserver          Could not connect using the requested protocol.
At line:1 char:1
+ Connect-VIServer itvc001.age.com
+
        + CategoryInfo               : ObjectNotFound: (:) [Connect-VIserver], ViServerConnectionException
        + FullyQualifiedErrorId : Client20_ConnectivityServiceImpl_Reconnect_ProtocolError, VMware.VimAutomation.ViCore.Cmd
    lets.Commands.ConnectVIServer
##################################################

This is all because, there are proxy setting configured into your explorer or into your system from where you are trying to connect the vcenter from powercli.

 To resolve this Issue pls follow below KB articile. 2011395

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

To resolve this, check the proxy settings using the PowerCLI and set the proxy to No Proxy.

To set the proxy setting to No Proxy:

 1.Run this command to find the current proxy settings:

    Get-PowerCLIConfiguration

    You see an output similar to:

    C:\PS>Get-PowerCLIConfiguration

   Proxy Policy Default            Server Mode

   -------------------------       ---------------

   UseSystemProxy                  Single

    Note: This output indicates that the PowerCLI is using the System Proxy.

 2.To change this setting, run this command:

    Set-PowerCLIConfiguration -ProxyPolicy NoProxy -Confirm

    You see an output similar to:

  C:\PS>Set-PowerCLIConfiguration -ProxyPolicy NoProxy -Confirm

    Perform operation?

  Performing operation 'Update vSphere PowerCLI configuration.'?

  [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"): y

  Proxy Policy Default       ServerMode

  ------------               ---------------

  NoProxy                    Single

 

 

After changing above proxy settings you would be able to make connection with vCenter via Powercli. :)

Source (http://vxpresss.blogspot.in/)

Happy Sharing..  :)


 

Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x
You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out.
Now the option left is from the command line of VCSA appliance.
Below steps will make it possible to change the FQDN of the VCSA from the command line.
Access the VCSA from console or from Putty session.Login with root permissionUse above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_netOpt for option 3 (Hostname)Change the hostname to new nameReboot the VCSA appliance.After reboot you will be successfully manage to change the FQDN of the VCSA .

Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client.

If you are using self-signed certificate, you can regenerate the certificate with the help of below KB 2112283 article.



Happy Sharin…

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment.
Somewhere during security auditing we require to provide several information to security team to get successful audit.
One of them is the compliance of Virtual machine auditing of creation date and time.
Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi.
To get the details we will use VMware Powercli to extract the details.
By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date.
Below is the function which needed to be copy and paste into the Powercli.
=======================================================================
function Get-VMCreationTime { $vms = get-vm $vmevts = @() $vmevt = new-object PSObject foreach ($vm in $vms) { #Progress bar: $foundString = "       Found: "+$v…

Could not connect to one or more vCenter Server systems: https://FQDN:443/sdk

Recently I got a case where vCenter 6.0 where the webclient was not showing inventory while loading. Issue occur when the customer was performing migration activity of virtual machine.
We verified that the vpxd services of vCenter, which is VCSA (Appliance), went into stopped stated just after starting means its crashing.
On VCSA Shell: service-control --status vmware-vpxd shows "stopped" service-control --start vmware-vpxd starts the service starts for a couple of seconds and stops again
VCSA 6.0 is linked with extrnal PSC 6.0. Verified the services of PSC and found all looks into good state.
Tried to power off both the VCSA and PSC and Power on in sequence where we started first PSC and later VCSA. After restarting the VCSA, status of the VPXD services was same as it was getting stopped after couple of seconds.
Checked the VPXD logs and found that the heartbeat between ESXi and VCSA was getting timed out for more than 1032 ms or more.
VCSA has generated the core dump at /var/core. …