BigIP-3600 rebooted itself

Sign in as root and look in /var/log. The log file from that date should already be gzipped--so look for ltm.3.gz, or something close. Also, look in /var/core to see if a core file was generated at that time.

Well, I don't see the log files created for that day (Mar 4th).

-rw-------. 1 root root 1010559 2018-03-13 03:34 ltm.10 -rw-------. 1 root root 29513 2018-03-14 03:49 ltm.9.gz -rw-------. 1 root root 45933 2018-03-15 03:33 ltm.8.gz -rw-------. 1 root root 87616 2018-03-16 04:46 ltm.7.gz -rw-------. 1 root root 80223 2018-03-17 03:22 ltm.6.gz -rw-------. 1 root root 53015 2018-03-18 03:34 ltm.5.gz -rw-------. 1 root root 765 2018-03-19 03:08 ltm.4.gz -rw-------. 1 root root 1052 2018-03-20 04:18 ltm.3.gz -rw-------. 1 root root 3178022 2018-03-21 02:52 ltm.1 -rw-------. 1 root root 57647 2018-03-21 03:29 ltm.2.gz -rw-------. 1 root root 1826809 2018-03-21 12:04 ltm

last command output: reboot system boot 2.6.32-431.56.1. Sun Mar 4 11:18 - 12:07 (16+23:48)

I would propose to generate a QKVIEW Support File and Upload this to iHealth. You could look through the Diagnostic Screen to check if some issues look related to your Problem. Also the Log Search in iHealth is a good way to filter the logs to Error Messages and above.

If you don't find any hints related to your problem open up a Support Case. You can Link the QKVIEW to the Support Case so the Support Engineer has a good view on your System.

Besides the Reboot Issue you should think about updating the System(s) to 12.1.2 HF2. This is the most actual release your Hardware Plattform supports (3600 is already EoSD)

I would propose to generate a QKVIEW Support File and Upload this to iHealth. You could look through the Diagnostic Screen to check if some issues look related to your Problem. Also the Log Search in iHealth is a good way to filter the logs to Error Messages and above.

If you don't find any hints related to your problem open up a Support Case. You can Link the QKVIEW to the Support Case so the Support Engineer has a good view on your System.

Besides the Reboot Issue you should think about updating the System(s) to 12.1.2 HF2. This is the most actual release your Hardware Plattform supports (3600 is already EoSD)

The ltm logs are rotated and zipped up daily, and by default only the last 10 or so are kept. If your ltm writes out to a remote syslog server you might be able to find the entries there, but if not then your only hope will be if there's something in /var/core that you can upload to support.

unfortunately /var/core is also empty. This is centos 6.6

open a case with tech support