Elie,
For the clock alarm it is recommended that you go to that WAE CLI, remove any ntp server configuration (if present), then manually set the clock (e.g. clock set 20:23:30 January 15 2011) as close as possible to the clock on the CM (check with the show clock command on the CM CLI). Once the clock on this WAE is set to the CM time, point the WAE to the CM for ntp. This is actually recommended for all WAEs in your WAAS network to ensure statistics are reported accurately, and features like prepositioning can function properly. Then after 1 or 2 cms poling cycles (5 - 10 minutes) this alarm should clear.
The TFO accelerator alarm indicates that the WAE has reached it's connection limit, and all new TCP connections will be placed into pass through. This condition will clear once enough clients or servers close their TCP connections that are being optimized, and the number of concurrent optimized sessions drops below the effective limit of the WAE. Once this condition is cleared new TCP connections will be flagged for optimization as per the policy engine.
For more information on overload conditions see the troubleshooting wiki here:
http://docwiki.cisco.com/wiki/Cisco_WAAS_Troubleshooting_Guide_for_Release_4.1.3_and_Later_--_Troubleshooting_Overload_Conditions
Regards,
Mike Korenbaum
Cisco WAAS PDI Help Desk
http://www.cisco.com/go/pdihelpdesk
