topic Re: Tracking Connection Count/limit (asg perf or vsx stat) in Hyperscale Firewall (Maestro)

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

Charles_Kim — Tue, 14 May 2019 16:58:54 GMT

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?

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

Charles_Kim — Tue, 14 May 2019 17:50:24 GMT

@PhoneBoy Any advice here? 🙂

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

PhoneBoy — Tue, 14 May 2019 21:35:06 GMT

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

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

Charles_Kim — Wed, 15 May 2019 15:45:40 GMT

Sorry 😉 Thanks for the info!

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

Martin_Valenta — Thu, 16 May 2019 07:11:06 GMT

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

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

kobil — Sun, 21 Jul 2019 16:08:58 GMT

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