Sophos Anti-Virus feature key status in Dormant

[spisipati]

We have a Virtual IronPort server, and Sophos Anti-Virus feature was Expired.

Recently we got this FeatureKey from Cisco. When we Installed it though CLI, we accepted the Agreement too.

But the FeatureKey was in Dormant status. Please help how to Activate it.

[Ken Stieers]

You just have to go enable/reconfigure it under Security Services/Antimaware.(?) 

[Robert Sherwin]

Dormant keys just need to have the EULA reaccepted once a new license PAK, VLN has been updated on an appliance.

How can I determine the licensed features that are enabled on my Cisco Content Security appliance?

... A Dormant key indicates that the feature itself has an End User License Agreement (EULA) that must be accepted, or that the feature must be configured and enabled. Once completed, the feature moves to Active, and the expiration timer begins. 

Cheers,

Robert

[spisipati]

We tried below actions,

• Security > Sophos Anti-Virus -- Disable and Enable, but no luck.
• Security > Sophos Anti-Virus -- Setup Rule to Server Level, and again Disable and Enable, but no luck. 
• Security > Sophos Anti-Virus -- Setup Rule to Cluster Level, and again Disable and Enable, but no luck. 

Hence CISCO recommended ad below,

• Remove the effected server from Cluster. 
• Disable and Enable Sophos Anti-Virus. 
• Now verified, that Sophos Anti-Virus feature was Active.
• Add this server back to Cluster. 

[Libin Varghese]

Yes, for feature keys newly applied the EULA needs to be accepted at the machine level since the licenses are machine specific.

So in such cases would need to remove the machine from the cluster, disable and re-enable the feature to accept the EULA and then add the machine back to the cluster.

If that does not work a reboot may be required.

 - Libin V

[dmccabej]

Hello,

Some other less intrusive steps to try would be the following (Not sure if you did this specifically in your 2nd 'Security --> Sophos' step) :

1) Move Anti-Virus level settings to machine-level

2) Go to edit machine-level Anti-Virus settings

3) EULA should popup for acceptance

4) Accept EULA and then delete machine-level settings

5) Rinse and repeat for each ESA within the cluster

NOTE: Should not need to commit the above steps

Personally, that has probably fixed 9/10 cases I've run into with this issue. Other times, you may need to resolve by performing some of the more complex tasks that have been stated. 

Thanks!

-Dennis M.