Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We have a virtual configured for direct access that we tried to set the idle timer to infinite (0), but about 10 minutes after doing so the CSM-S stopped responding. Is there a problem with setting the timer to infinite on a Cat 6500 w/ CSM-S v. 2.1...
When is this option required for a vserver configuration? Is it required to use with cookie persistence? Can I disable it if I'm not using a policy or making any L7 lb decisions?
Its a 24x7 production environment, so we are not able to test. Currently the ANY protocol vserver is handling all TCP and ICMP connections and we have a very long timeout - 120hrs - configured for it. The UDP vserver is handling all UDP traffic and...
Here is the config that we used - which looks the same as your config. I fully expected it to work like your test. Showing the status and conns of the new TCP vserver after the change showed 0 active conns, but the number of total conns was increas...
We decided to try splitting the vservers, but ran into issues when bringing the new vservers online.We are seeing TCP/UDP/ICMP traffic on the vserver, so we created a new TCP and UDP vserver and made them operational - leaving the current "any" proto...
I found the issue with setting the idle timer to infinite on the vserver. When you set the timer to infinite, you must also set the variable INFINITE_IDLE_TIME_MAXCONNS to a large enough value to handle all the connections. We decided to try this a...
I'm going to adjust the idle timer to a finite value for the forwarding vip that handles incoming traffic. Now, where is the idle timer for outbound connections that are initiated by the real servers on the CSM-S?
