RestPy:Getting a session handle for windows platform

[openixia]

RestPy:Getting a session handle for windows platform

[hubertgee]

For regular Windows api server, the session ID is always 1 because it only support one session.

For windows connection manager, it supports up to 10 sessions like the Linux api server:
platform='connection_manager'

  # Change 8021 to the session ID that you want to connect to.
  session = testPlatform.Sessions.find(Id=8021)

[muthvar1]

Hi Hubert,
This was reported by another engineer and as you can see in the output he provided above, he did use session id 1.. but the call seemed to hang. It is possible there is something we are missing from our side, but can you confirm (from your tests) using session id 1 works for Windows and it does give a handle to the session object?

[hubertgee]

I connect to an existing Windows session quite often by the way how you showed it and I have not experienced any hanging. Does it hang if doing a testPlatform.Sessions.add() ?

[muthvar1]

Yeah.. looks like even an add does hang. Is something not set correctly on our Windows api server?
JFYI, because of the proxy settings on our windows VM.. we couldn't open up the api browser either on the the windows client. Trying to fix that too. Hoping that's not the cause for this issue?

[hubertgee]

We have other customers who configures proxy server in their Windows and that caused connection problems. As soon as the proxy server was disabled, connection works fine. Try disabling the proxy server temporary to see if that fixes the problem and go from there.

[muthvar1]

Yeah tried that too for localhosts and now it just hangs.. so looks like there is some problem in accessing the api browser itself on the client.. Not sure what the problem is.
All of us seem to be seeing the same issue. Should we open a support ticket to get this resolved?

[therkong]

Varghese, Yes, please open a support case. I can take a look. Regards, Theresa Kong Senior Tech Support Engineer Keysight Technologies From: varghese muthalaly <[email protected]> Sent: Tuesday, April 9, 2019 1:37 PM To: OpenIxia/IxNetwork <[email protected]> Cc: Subscribed <[email protected]> Subject: Re: [OpenIxia/IxNetwork] RestPy:Getting a session handle for windows platform (#52) [EXTERNAL] Yeah tried that too for localhosts and now it just hangs.. so looks like there is some problem in accessing the api browser itself on the client.. Not sure what the problem is. All of us seem to be seeing the same issue. Should we open a support ticket to get this resolved? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOpenIxia%2FIxNetwork%2Fissues%2F52%23issuecomment-481425582&data=02%7C01%7C%7C828b24dc6e254b38ca8708d6bd2b26f9%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636904390365634292&sdata=3bjYsFj0GdxAYo%2FmoBsyOObOOEuWISppvi0kV096HZU%3D&reserved=0>, or mute the thread<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAiMaUd4kU5iXCdlvzQTB1Uk4U7yCv8L5ks5vfPn6gaJpZM4clMsR&data=02%7C01%7C%7C828b24dc6e254b38ca8708d6bd2b26f9%7C63545f2732324d74a44dcdd457063402%7C1%7C0%7C636904390365634292&sdata=xB50kDrUdruBeGklvgV66GZm8w5WZsUpsRO7YK7H4h4%3D&reserved=0>.

[muthvar1]

This needs a change in how we start the IxNetwork client in Windows. Theresa from support group helped us on this. Closing this issue with resolution below.

From: Theresa Kong [email protected]
Date: Tuesday, April 9, 2019 at 3:03 PM
To: Sameer Patel [email protected], "Varghese Muthalaly (vamuthal)" [email protected], Hubert Gee [email protected]
Subject: RE: cannot connect to session on windows IxNetwork API server

I started my ixNet API Server with -restInsecure mode. In this mode, http is used instead of https.
And yes, I can connect.

If you started ixNet API Server without -restInsecure, it uses https. There are few things that can go wrong in this mode.
If you check the Windows Events log, there might be errors that may indicate the issue.

• Error 11001 is permission issue. Make sure you have
  read/write permission in "c:/program data/microsoft/crypto/rsa/machinekeys" folder for the uid that started ixNet API Server

• Error 40 is the tls 1.2 issue.
  need to add a regkey below and restart the PC
  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Server] "Enabled"=dword:00000000
  Note: there was SSL key but not TLS 1.2 key
  Restart of the PC is required after adding the regkey

Or you can restart your ixNet API Server with -resetInsecure option. This can be done in the Property window of the ixNet API Sever shortcut.