25 second launch delay

Answered

October 16, 2020 10:34

Problem:

Launching NX Client and connecting to the servers VLAN IP results in a 25+ second launch delay.

Configuration:

Running NX Witness Server on 4.1.0.31398 (Debian 10). Server has a primary (10.0.0.106) and a VLAN IP (10.0.31.250). The VLAN is for NX and the cameras. In System Administration > Routing Management, I've disabled all but the VLAN IP and hostname (nx.cams.xyz.com).

Client Observations:

Connecting to the primary IP is instantaneous.
Connecting to the VLAN IP results in a 25+ second loading delay.
No entries observed during launch in the server log.

Questions:

Is it possible to bind the server to only the VLAN IP?
Under Server Settings, what determines the "IP Address"?
Any ideas on what might be causing the delay when connecting to the VLAN IP?
How can this issue be debugged further (extended logging in client and server)?

Thank you very much.

Comments

3 comments

Hamb Anet

October 17, 2020 02:34 Edited

Additional information:

Noticed some client debug log entries that might be relevant to the issue:

2020-10-17 08:22:06.791 4e50 DEBUG nx::vms::discovery::ModuleConnector::Module(0x1be022e7bd0, 16741124-0d9e-3623-a657-650970f458b1): Could not connect to nx.cams.xyz.com:7001: HTTP request has failed: [A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ], http code [0]
2020-10-17 08:22:07.625 4e50 DEBUG nx::network::http::AsyncClient(0x1be0cbdde78): Failed to establish tcp connection to http://10.0.0.105:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. 
2020-10-17 08:22:07.625 4e50 DEBUG nx::vms::discovery::ModuleConnector::Module(0x1be022e7360, 0d359ff8-ef53-3ba8-5c2e-dc4ce0ed44af): Could not connect to 10.0.0.105:7001: HTTP request has failed: [A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. ], http code [0]
2020-10-17 08:22:07.627 4e50 DEBUG nx::network::http::AsyncClient(0x1be0cbde308): Error reading (state receivingResponse) http response from http://10.0.31.251:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

Client debug logs:

Quick connect (10.0.0.107 LAN)

25+ second connect delay (10.0.31.250 VLAN)

Theories & Testing:

Manually tested these URLs:

https://x.x.x.x:7001/api/moduleInformation?showAddresses=false&keepConnectionOpen&updateStream=10

When connecting to the LAN IP (10.0.0.107/cx.fleet.xyz.com), it replies immediately.
When connecting to the VLAN IP (10.0.31.250/nx.cams.xyz.com) there is a 20+ second delay.

Thought it might be a DNS issue related to the server hostnames (cx, cams). But, from the servers, manual DNS tests were OK.

With this additional information, it's clear that connecting to the API endpoint using the VLAN IP introduces a substantial delay.

Will do further debugging server-side.

Question:

During NX Client startup, I also noticed an endpoint that I do not have configured anymore. 10.0.0.105 is from a prior server. In the Connect to Server... dialog, I have 2 saved sessions (LAN and VLAN IP) and there are 2 auto-discovered servers (2 LAN IPs as I have 2 servers).

2020-10-17 09:03:04.869   1f00   DEBUG nx::vms::discovery::ModuleConnector::Module(0x280cb879760, 740a381d-e460-6ed0-0984-cec3cd7ea5a0): Save endpoint 10.0.31.250:7001 to 3
2020-10-17 09:03:04.869   1f00   DEBUG nx::vms::discovery::ModuleConnector::Module(0x280cb879910, 0d359ff8-ef53-3ba8-5c2e-dc4ce0ed44af): Created with RetryPolicy(4294967295, 5s, 2, 1m, 0.2)
2020-10-17 09:03:04.869   1f00   DEBUG nx::vms::discovery::ModuleConnector::Module(0x280cb879910, 0d359ff8-ef53-3ba8-5c2e-dc4ce0ed44af): Save endpoint 10.0.0.105:7001 to 3
2020-10-17 09:03:04.869   1f00   DEBUG nx::vms::discovery::ModuleConnector::Module(0x280cb87ad50, 16741124-0d9e-3623-a657-650970f458b1): Created with RetryPolicy(4294967295, 5s, 2, 1m, 0.2)
2020-10-17 09:03:04.869   1f00   DEBUG nx::vms::discovery::ModuleConnector::Module(0x280cb87ad50, 16741124-0d9e-3623-a657-650970f458b1): Save endpoint nx.cams.hambanet.com:7001 to 1

Given I don't have 10.0.0.105 saved, where is it coming from?

Norman

Network Optix team

October 27, 2020 12:56
Hi Hamb Anet,

Are you connecting through the Nx Cloud and if so, can you tell me what kind of connection is made, NAT or Proxy.
I assume the fast one makes a NAT connection and the slow one a Proxy connection.

You can see this in the icon on the Bottom Left of the camera image when you view it.

Click on the Information icon or right-click on any selected item to open the context menu, and choose Show Info (Alt+I) to display the following item information:
- Resolution of the stream in pixels
- Frames per second (FPS) of the stream
- Bit rate of the stream. The letter after the bit rate value is the video traffic delivery method indicator – Direct Connect, NAT traversal (N) and Proxy (P).
- Codec (e.g., H.265, H.264, or MJPEG)
- Stream in use – Hi-Res or Lo-Res
My assumption would be that the VLAN prohibits the NAT connections and the Proxy can be slower, although 20+ is quite slow. Where is the system based? Will the connection remain smooth after the connection has been made?
0
Norman

Network Optix team

November 05, 2020 13:41
Hi Hamb Anet,

We have not heard back from you in a while, so we are going to assume your question has been answered and set this topic to 'Answered'.
0

Please sign in to leave a comment.

25 second launch delay

Comments

Didn't find what you were looking for?