S170 web ui super slow

[keithsauer507]

We have a 1U Cisco S170 WSA appliance that is just super slow to navigate around the web user interface.  It's running AsyncOS Version 9.1.1-074.

Do you think we should upgrade to a newer appliance?  We only have https description on a handful of IP's (network object group in firewall for wccp port 443).  We want to turn it on globally for like 200 devices, so with that being said and the Web UI is painstakingly slow as it is, time for an upgrade?

Also interested in the virtual appliance, but if you lose L4 traffic monitoring, is it possible to keep the physical appliance to do L4 and the virtual to do the rest?  Or have them both load balance or run in tandem for high availability?  Would this mean purchasing 2 sets of all the feature keys every year to keep things updated?

[Ken Stieers]

It may very well be time for an upgrade...

Its possible to keep the appliance.... you pay your license fees based on user count, so just stay honest there... if you have a hardware appliance, you can download and use the VM as part of that license, and you can deploy as big of one, and as many VMs as you like....

You can keep the physical box to do L4TM, and use the VMs for everything else.

You can use them for HA. 

No it means you pay for your seats... when you update, or add features, you have to go to the licensing portal and get a new license for the VMs...   In general, I've always had issues with the portal so I end up opening a ticket to get updated keys.

I know we've been happier with a S100V... but my VMware infrastructure is better hardware than the 170...

[Handy Putra]

S170 running version 9.1.1 slowness can be caused by too many stuck files in the reporting due to slower disk and due to reporting issues from previous version such as 9.0.1. 

These stuck files can be safely removed and will not delete or impact the reporting database.

To do this:

1. Enter the CLI and enter commands diagnostic -> reporting
   
2. Check the number of files that are being in the export queue, and waiting for reporting process to be processed, using DBSTATS command. This will show the count of files that are waiting to be processed by reporting process, as shown in the ouput below:

#New options in: CLI -> DIAGNOSTIC -> REPORTING

Choose the operation you want to perform:
- DELETEDB - Reinitialize the reporting database.
- DISABLE - Disable the reporting system.
- DBSTATS - List DB and Export Files
- DELETEEXPORTDB - Delete Export Files
- DELETEJOURNAL - Delete Journal Files
[]> dbstats

Outstanding DB stats:
Export Files:
        Folders: 2
        Files: 66
Always Onbox:
        Folders: 2
        Files: 4

The reporting system is currently enabled.

In this case, if all the above conditions are met, in order to continue normal WSA S170 operation, administrator should clear those excessive files by following the procedure below:

1. Enter command DISABLE to disable the reporting engine.
2. Enter command DELETEEXPORTDB. 

Note: if there's a lot of backed up data, this command may take a very long time to complete.  If it sits for a long time without making any progress, then the data may need to be removed manually.

  3. Enter command DELETEJOURNALS.

  4. Enter command ENABLE to re-enable the reporting engine.

At this point, reporting should be processing all new data (and will have all the data that was previously in reporting database).