About NSXEdge's LB (Session Time Out)

[networlddsg]

Hello.

Is it possible to change the setting of "Session Time Out" in LB of NSX Edge?

（I also want to know the default value of Session Time Out.)

NSX Version 6.3.2

[bayupw]

If you are looking for NSX Edge TCP keepalive or inactivity timeout, you can modify it via REST API as per release notes below

VMware NSX for vSphere 6.3.2 Release Notes

Issue 1446327: Some TCP-based applications may time out when connecting through NSX Edge
The default TCP established connection inactivity timeout is 3600 seconds. The NSX Edge deletes any connections idle for more than the inactivity timeout and drops those connections.

Workaround:

1. If the application has a relatively long inactivity time, enable TCP keepalives on the hosts with keep_alive_interval set to less than 3600 seconds.
2. Increase the Edge TCP inactivity timeout to greater than 2 hours using the following NSX REST API. For example, to increase the inactivity timeout to 9000 seconds. NSX API URL:
   /api/4.0/edges/{edgeId}/systemcontrol/config PUT Method <systemControl> <property>sysctl.net.netfilter.nf_conntrack_tcp_timeout_established=9000</property> </systemControl>

[networlddsg]

Hello.

I tried and I got an error.

Is there a mistake in the setting method?

POSTMAN error screen

[bayupw]

Hello, the settings looks right, not sure why it's error.

I have used this settings on one of my deployment but that was on NSX 6.2.2.

I'll try this on a lab and let you know the result.

If it is urgent, you can open a case to VMware GSS/Support

[bayupw]

I did a test and yes the result is same, I can't use that sysctl property

I tried other property such as rp_filter and it works

I am wondering if that property is not available anymore or misdocumented.

There is not much documentation on the property on NSX 6.3 REST API doc, but this is documented on NSX 6.2 REST API doc as below

Will need to reach VMware Support/GSS or someone from VMware NSBU to check about this

[networlddsg]

Thank you.

I will check with Vmware.

I will share it if I understand.