cancel
Showing results for 
Search instead for 
Did you mean: 
Post a Question
Highlighted

Tracking Connection Count/limit (asg perf or vsx stat)

Hi Checkmates,

I have been stuck determining whether there is a difference in the connection count values (and kernel tables in general).

 

If you run asg perf -vv, you can fetch the concurrent connection of each VS. The output aggregates the connections found across all the blades for that VS

 

If you run "fw vsx stat -l", you can fetch both the connection count and limit.

 

Is fw vsx stat also aggregating all the blades? The values look identical. Is the limit from "fw vsx stat -l" also aggregating the limit of all the blades associated with the VS?

0 Kudos
4 Replies

Re: Tracking Connection Count/limit (asg perf or vsx stat)

@PhoneBoy  Any advice here? 🙂

0 Kudos
Admin
Admin

Re: Tracking Connection Count/limit (asg perf or vsx stat)

No need to tag me, I usually see everything, especially stuff that doesn't get answered. 😬
However, I will admit I am less familiar with the Scalable Platforms, so bear with me.

As far as I know, all of these commands should be aggregating from all the blades.
Note that a given VS has a global limit (across all VSes).
0 Kudos

Re: Tracking Connection Count/limit (asg perf or vsx stat)

Sorry 😉 Thanks for the info!
0 Kudos

Re: Tracking Connection Count/limit (asg perf or vsx stat)

I do use snmp to monitor connections current value and limit of each VS...

0 Kudos