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

[Charles_Kim]

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?

[Charles_Kim]

@PhoneBoy  Any advice here? 🙂

[PhoneBoy]

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).

[Charles_Kim]

Sorry 😉 Thanks for the info!

[Martin_Valenta]

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

[kobil]

Generally fw commands executed from expert shell is running on the local SGM only, asg commands are special commands that usually aggregates info from all members (depends on the command)

you can add g_ to commands such as fw (g_fw..) and it will run on all SGMs