VMware Cloud Community
Paulb21
Contributor
Contributor
Jump to solution

Connect-VIServer : No such device or address

When running Connect-VIServer -Server xx.xx.xx.xxx -Protocol https -User domain\username -Password xxxxxxxxx from a UNIX server with PowerShell and VMware-PowerCLI-11.1.0-11289667 installed we get the following error:-

Connect-VIServer : No such device or address

We have tried FQDN / IP address for the vCenter but it makes no difference.

Name resolution works fine and CURL on 443 also works.

We see a successful login for the account within the vCenter logs.

If the same command is used from a Windows VM it works fine.

Reply
0 Kudos
1 Solution

Accepted Solutions
Paulb21
Contributor
Contributor
Jump to solution

The issue has now been resolved.

It was due the Red Hat server being unable to communicate with the VMware Platform Services Controller on port 443!

Many thanks for the suggestions.

For information, we did log a VMware call for this issue but they were unable to resolve it. We worked it out ourselves in the end.

View solution in original post

Reply
0 Kudos
13 Replies
LucD
Leadership
Leadership
Jump to solution

Is that from a supported Linux OS?
See the Release Notes.

Also, have a look at PowerCLI issue on CentOS 7 Linux


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

We are running it on Red Hat Linux 7.4 and have the following modules loaded.

ModuleType Version Name                                ExportedCommands

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

Manifest   6.1.0.0 Microsoft.PowerShell.Management     {Add-Content, Clear-Content, Clear-Item, Clear-I...

Manifest   6.1.0.0 Microsoft.PowerShell.Utility        {Add-Member, Add-Type, Clear-Variable, Compare-O...

Script     1.1.7.2 PackageManagement                   {Find-Package, Find-PackageProvider, Get-Package...

Script     1.6.7 PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Fi...

Script     2.0.0 PSReadLine                          {Get-PSReadLineKeyHandler, Get-PSReadLineOption,...

Script     6.7.0.1... VMware.Vim

Script     11.0.0.... VMware.VimAutomation.Cis.Core       {Connect-CisServer, Disconnect-CisServer, Get-Ci...

Script     11.0.0.... VMware.VimAutomation.Common

Script     11.0.0.... VMware.VimAutomation.Core           {Add-PassthroughDevice, Add-VirtualSwitchPhysica...

Script     11.0.0.... VMware.VimAutomation.Sdk            {Get-ErrorReport, Get-InstallPath, Get-PSVersion}

PowerCLI Version

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

   VMware PowerCLI 11.1.0 build 11289667

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

Component Versions

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

   VMware Cis Core PowerCLI Component PowerCLI Component 11.0 build 10335701

   VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 11.0 build 10336080

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Did it work before?
Did you look at the thread I linked to? Are you using NSX?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

This is new installation of PowerCLI on Linux so it has not worked before.

We have no NSX in use.

The same command works from from a Windows VM on the same network as the Linux VM.

Reply
0 Kudos
sjesse
Leadership
Leadership
Jump to solution

Is the Linux machine in the same subnet as the windows machine that works, could there be a firewall in between?

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Are you running the Connect-VIServer from a SSH connection to the Linux box?
Or from a TTY session?

Are you using the bash shell?


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

The connection is from an SSH session using bash.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Do you get the same error when you connect from a TTY?

Or a SSH with a TTY (most of the time the -t parameter).


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

We get the same error when using TTY. Its an interactive session using putty.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

Unfortunately I don't have a RH 7.4 at hand, so I can't really do any tests.
It works for me on Ubuntu and a few other Linux flavours, so I suspect it could be a distro and/or version issue.

The PowerCLI Compatibility Matrix still only mentions Ubuntu, so I'm not even sure you could open a SR.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

Many thanks for your help LucD

We will perform more testing and open a case with VMware.

Reply
0 Kudos
LucD
Leadership
Leadership
Jump to solution

If you do get an answer, let us know.


Blog: lucd.info  Twitter: @LucD22  Co-author PowerCLI Reference

Reply
0 Kudos
Paulb21
Contributor
Contributor
Jump to solution

The issue has now been resolved.

It was due the Red Hat server being unable to communicate with the VMware Platform Services Controller on port 443!

Many thanks for the suggestions.

For information, we did log a VMware call for this issue but they were unable to resolve it. We worked it out ourselves in the end.

Reply
0 Kudos