The Expiration date for the CachePulse service on your ProxySG is showing as expired, or soon to expire, even though a valid subscription renewal has been purchased and is visible in Network Protection Licensing Portal. In the ProxySG sysinfo file, this may appear as follows:
Stat: CachePulse Expiration Current State : WARNING Last Transition : Wed, 20 Jan 2016 14:09:17 UTC Current Value : 2 Unit of Measurement : days left Warning Threshold : 30 Warning Interval : 0 Critical Threshold : 0 Critical Interval : 0 Notification Method : log
The root-cause of this issue is a minor bug in the SGOS CachePulse component.
BlueCoat advise to perform the following steps outside of production hours wherever possible, or at a time of relatively low traffic-load on the proxy.
To resolve this issue, simply disable and then re-enable the CachePulse service on the proxy. This can be done in the GUI or from the CLI.
Using the GUI:
Using the CLI:
After applying either the GUI or CLI fix above, the new expiration date should now be visible in the ProxySG GUI or in its sysinfo.