Hi all,
having an issue with Connect-NsxtServer cmdlet - it takes almost 2 minutes to connect to the NSX-T manager. Is that normal? If not, any ideas on how to troubleshoot?
PS C:\> Measure-Command { Connect-NsxtServer $server }
Days : 0
Hours : 0
Minutes : 1
Seconds : 53
Milliseconds : 815
Ticks : 1138153958
TotalDays : 0.00131730782175926
TotalHours : 0.0316153877222222
TotalMinutes : 1.89692326333333
TotalSeconds : 113.8153958
TotalMilliseconds : 113815.3958
I have the same question. Doing a REST-API login getting a bearer token is sub second request. So not sure what Connect-NsxtServer is do
I think a hint could be that when I run the connect via vRA in the FaaS container it actually crashed on out-of-memory. I extended memory to 2GB without success. So maybe a memory leak is occuring.
Same issue here.
On Mac and Linux it takes more than 2 minutes whilst in Windows it takes ages...
Notice that CPU and memory consumption for the PowerShell daemon is ridiculously high during the connection request.
Mac:
Days : 0
Hours : 0
Minutes : 2
Seconds : 11
Milliseconds : 178
Ticks : 1311783183
TotalDays : 0.00151826757291667
TotalHours : 0.03643842175
TotalMinutes : 2.186305305
TotalSeconds : 131.1783183
TotalMilliseconds : 131178.3183
PID | COMMAND | %CPU TIME |
31136 | pwsh | 99.3 12:40.99 30/1 |
Windows:
Days | : 0 |
Hours | : 0 |
Minutes | : 9 |
Seconds | : 51 |
Milliseconds | : 325 |
Ticks | : 5913255137 |
TotalDays | : 0.0068440452974537 |
TotalHours | : 0.164257087138889 |
TotalMinutes | : 9.85542522833333 |
TotalSeconds | : 591.3255137 |
TotalMilliseconds : 591325.5137
Anyone ever figure this out? Having same issue.