First and foremost is to verify bandwidth utilisation on ISP. Internet link . And futher look for any packet drop in your entire end to end infrastructure or any congestion in network and even verify CPU ,RAM and disk resource utilisation in network devices like firewall, routers and switches connected in your topology .
I checked the /var/log/httpd.log log and I found the required interface (not the one I thought to):
httpd: 0: GET IFNAME WORKED st0.6
httpd: 0: GET ALLOWED FAILED st0.6
now I can reach the Web Gui.
Thanks to all.
There isn't a show command that shows this information. Invalidated sessions are sessions that are due for cleanup/deletion, holding them in memory so that they could be viewed may present other issues. The behavior can change slightly depending on some configuration settings (i.e. set security flow tcp-session rst-invalidate-session).
If your issue is a ...
Connecting directly into the switch, use the wired network to see if the problem is still there. If not, it's the wireless network - interference, thick walls, long range, overload, ...
If the problem persists directly on the switch, check the switch's interface counters for errors. FCS, giants, runts indicate cabling problems on that port. If any port ...
You probably need one or two more PEMs. This Juniper document is a good planning resource for SRX3600 power budgeting.
All the PEMs in the SRX3600 load-share so the problem isn't which slots are occupied by PEMs but rather the total available power supply. There are no zones or similar complications like there are in some other Juniper chassis.