WAAS %WAAS-TFO-4-641016: Entering overload state

[Richard Bradfield]

getting the messages

May 20 08:13:44 CHIWAD01 tcpproxy: %WAAS-TFO-4-641016: Entering overload state d

ue to Max connections (Num. of Entries: 5).

May 20 08:13:44 CHIWAD01 tcpproxy: %WAAS-TFO-4-641014: Entered overload state gl

obally. Total number of entries: 5

May 21 07:13:15 CHIWAD01 tcpproxy: %WAAS-TFO-4-641017: Exited overload due to Ma

x connections. Total number of entries for this reason: 5, time of last entry: T

ue May 20 08:13:44 2008

May 21 07:13:15 CHIWAD01 tcpproxy: %WAAS-TFO-4-641017: Exited overload state glo

bally. Total number of entries: 5, time of last entry: Tue May 20 08:13:44 2008

May 21 09:00:30 CHIWAD01 tcpproxy: %WAAS-TFO-4-641016: Entering overload state d

ue to Max connections (Num. of Entries: 6).

when I look at the connection statistics

I see many entries that have been open for a long time (weeks) with very little data (7 bytes) How do I clear these orphaned connections?

so I dont reach maximum connections

Richard.

[dstolt]

Richard,

What version of code are you using? You may be encountering a DDTS fixed in 4.0.17

Check out CSCsm22514 and CSCsm51361

http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v4015_v4017/release/notes/ws4015_4017rn.html#wp349693

Dan

[Richard Bradfield]

Dan,

I am running 4.0.13

so looks like I will have to upgrade to 4.0.17

thanks

Richard.