where we used the output from that command to create the graphs we needed (one of the two points you mentioned). Even with API scripting this was not possible as we all know. I hope Check Point takes a good hard look at their C2S/RA reporting capabilities. As with all crises we will learn lessons and grow stronger. I had one customer that has a watch command running and every 10 minutes and he updates a spread sheet from 9 different gateways (every 10 minutes).
I finally figured it out, but it took some time and was not point and click. It was not possible to get easily from Check Point. And it seems to me that that ask was not out of the question. Some of them are rational IMHO and some are not, but those were the two things everyone wanted. I recommended things like cut down the connect time and have them re-authenticate to looking at total number of OM IPs used and in this time of crisis they have very specific wants and needs. They are more concerned with number of users currently on a specific GW and if they need to bounce some and have them connect to another and how long have they been connected. So number of logs and number of sessions, how much data, which blade, etc., are great because that's what you can easily pull in SE, but that's not what the people wanted in this crisis (at least the vast majority of the ones I've dealt with).
How many people are connected right now (and they want updates that range from every 10 minutes to every hour) and they also want to know how long each user is connected.
0 kommentar(er)
