Forum Discussion
about new virtual server and new pool on F5 LTM 1600 load balancer
Thanks Patrik for the reply !
May you please help give some advice on the statements below ?
10.0.0.3 is the F5 BIG-IP 1600's virtual server IP
10.0.0.1 is the IP of Server A, 10.0.0.2 is the IP of Server B.
Both Server A & Server B belong to the same pool while Server A has higher proirity than Server B.
The timeout value of the persistence profile = 604800 seconds
This persistence profile is used by the virtual server
When we telnet 10.0.0.3 with some TCP port(s), the telnet session can be kept as "connected" status for around 8 minutes. Afterwards, the telnet session will be broken down suddenly.
The telnet session to 10.0.0.3 is telnet to exactly 10.0.0.1 at the background.
However, the telnet session can be kept always connected when we directly telnet to 10.0.0.1
Why the telnet session to F5's virtual server IP is suddenly broken down ?
Is it related to timeout value ?
Thanks very much !
Roc
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com