check for the CPU utilisation of the PIX . use the command "sh cpu usage" and see if the CPU is normal. Also check for errors on the pix, switch port... Are you able to ping the inside interface without any problems when the PIX does not respond ???
It failed again. Messages stopped going to syslog. Console port did not respond. Inside did not ping. Last few syslog messages were warning level - no errors. Power off/on got it going again. CPU Usage in first few minutes after reboot was about 15%. Any thoughts? Thanks in advance, Greg
which OS are u using in PIX ?? Which series of PIX ??Need to check for the caveats in the OS. try using a sniffer on the inside and SPAN the traffic.. See if there are any abnormal traffic when the problem occurs.... or else, raise a tac and replace the hardware, as a last resort....
Just an FYI. This issue appears to have been caused by an attack on my system originating from the ripe.net controlled segments. It has been a while since my PIX has crashed (it's bad when 36 hours seems like a long time). My syslog has been showing greatly reduced traffic. Lesson - keep a working syslog server so you can tell what is normal traffic levels and what isn't. I still think that the firewall should have handled the connection attempts so I may have hardware problems.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...