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

Post a Comment

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 permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot 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...
2 comments
Read more

Issue : Configure Management Network option is Grayed out into ESXi

Last week I got into an issue of one of my client into Vsphere environment where one of its ESXi went done out of the network. Issue was IP address was showing 0.0.0.0 on main Esxi screen and when I tried to change the network configuration, its " Configure Management network option was greyed out.  I tried to gid into it and try to analyis its vmKernal and vmwarning logs. What I found is its VMkernal switch got removed due to unexpected reason. So to resolve the issue I tried to reconfigure its vswitch0 (vmk0) by going into Tech Mode of that Exi. Below are the steps which I followed to resolve the issue. 1) Login to ESXi 2) Press F2, Check if you " Configure Management network " is greyed out or not" if yes,    follow below 3) Press ALT+F1 to move the ESXi screen to tech mode   ( This is command line like dos) 4) login with root account 5) Run the following command into it esxcli network ip interface add --interface-name= vmk0 ...
2 comments
Read more

Collecting Logs from NSX-T Edge nodes using CLI

  This article explains how to extract the logs from NSX-T Edge nodes from CLI. Let's view the steps involved: 1) Login to NSX-T  Edge node using CLI from admin credentials. 2) Use of  " get support-bundle " for Log extraction. get support-bundle command will extract the complete logs from NSX-T manager/Edge nodes. nsx-manager-1> get support-bundle file support-bundle.tgz 3) Last step is to us e of " copy file support-bundle.tgz url " command. copy file will forward your collected logs from the NSX-T manager to the destination(URL) host from where you can download the logs. copy file support.bundle.tgz url scp://root@192.168.11.15/tmp Here, the URL specified is the ESXi host ( 192.168.11.15) under /tmp partition where logs will be copied and from there one can extract it for further log review. Happy Learning.  :)
Post a Comment
Read more