Forum Discussion
Chris_Pollard_1
Nimbostratus
Nimbostratusshow ltm pool detail question
Hi,
Just looking at an issue and happened to do a "show ltm pool detail poolname" and I see the output below. What does "Current Sessions" relate to? Obviously this is a very high number. If I look at other pools then I get a sensible number.
user@(F5)(Active)(/Common)(tmos) show ltm pool detail poolname
---------------------------------------------------------------------
Ltm::Pool: poolname
---------------------------------------------------------------------
Status
Availability : available
State : enabled
Reason : The pool is available
Monitor : http
Minimum Active Members : 0
Current Active Members : 3
Total Requests : 0
Current Sessions : 18446744073709551605
Traffic ServerSide
Bits In 192.8M
Bits Out 2.4G
Packets In 121.1K
Packets Out 220.7K
Current Connections 137
Maximum Connections 238
Total Connections 1.6K
Connection Queue Pool Pool and members
Number of connections queued now 0 0
Number of connections serviced 0 0
Queue head entry age (ms) 0 0
Maximum queue entry age ever (ms) 0 0
Maximum queue entry age recently (ms) 0 0
Average queue entry age (ms) 0 0
Thanks!
7 Replies
SamuelBChris, Did you ever receive an answer to your question? I am seeing something similar and have the same question.
Nick_T1I also see this behavior on 11.6. Interesting that it is very, very close to 2^64. I'm guessing bug. 18446744073709551527 - bigip current sessions number for me, slightly different than yours 18446744073709551616 - 2^64
Chris_GrantEmployee
Current Sessions is just what it sounds like, the current number of sessions active on that pool. Having said that the number you are seeing is nothing short of ridiculous. Please open a ticket so support can investigate and hopefully resolve this.
Chris_Pollard_1Thanks Chris, I will log a call at some point, I suspect it is a bug of some sort.
- Nick_T1I think this may just be a maximum count of all connections that have been made against that pool. I've got a relatively new pool that has a much smaller number while the number I posted here is one of the longest lived on our F5s.
brad_11480But then, how does it count something as a 'current session'. I reset-stats-- that value does not zero but stays about the same value as before the reset, but it never seems to goes down. Trying to understand the concept of a 'session' on a transaction-based pool (web traffic). In my case the virtual servers using the pool have session cookie persistence, so the Big-IP won't know how many cookies are out there in browsers that are still in an active session. I'd ignore this number, but I know it is going to be a question as some of the server and application people are looking to see when the traffic had 'drained' and wonder why 'current sessions' doesn't go to zero. Thanks..- Chris_GrantCurrent sessions should zero out after there are no longer any connection in the connection table. Resetting the statistics won't reset the connections, just the stats related to those connections. To zero out your connections you would need to either disable the pool members and wait for the last persistence profile to expire, or force them offline and wait for the last active connection to finish. Lets say they are short lived HTTP connections. If you forced all the pool members offline, withing a few minutes you should see your current sessions start to drain. On the other hand, if you had a long lived connection with long lived persistence and you simply disabled them, you may never see your sessions drain fully.
