model restarts logged for Thu 17/Apr/2014
2014_04_17 00:10 h1fw1
2014_04_17 00:14 h1fw1
2014_04_17 00:22 h1fw1
2014_04_17 03:03 h1fw1
2014_04_17 03:12 h1fw1
2014_04_17 03:23 h1fw1
2014_04_17 05:19 h1fw1
2014_04_17 05:25 h1fw1
2014_04_17 07:19 h1fw1
2014_04_17 07:24 h1fw1
2014_04_17 08:12 h1fw1
2014_04_17 08:23 h1fw1
2014_04_17 09:21 h1fw1
2014_04_17 10:05 h1isiham6
2014_04_17 10:07 h1isietmx
2014_04_17 10:27 h1fw1
2014_04_17 10:45 h1isietmy
2014_04_17 10:45 h1isiitmx
2014_04_17 10:47 h1isibs
2014_04_17 10:47 h1isiitmy
2014_04_17 10:49 h1isiham2
2014_04_17 10:49 h1isiham3
2014_04_17 10:49 h1isiham4
2014_04_17 10:49 h1isiham5
2014_04_17 10:51 h1isiham6
2014_04_17 11:09 h1broadcast0
2014_04_17 11:09 h1dc0
2014_04_17 11:09 h1fw0
2014_04_17 11:09 h1fw1
2014_04_17 11:09 h1nds0
2014_04_17 11:09 h1nds1
2014_04_17 12:22 h1fw1
2014_04_17 12:26 h1fw1
2014_04_17 12:55 h1fw1

unexpected restarts in red, daq restart in blue. Looks like the reboot of h1ldasgw1 has cleared the h1fw1 problem.