cpsizeme on SMS server

[NorthernNetGuy]

Is it possible to use the cpsizeme utility on the SMS server? It errors out saying it will only run if the unit has SecureXL turned on, which my Smart-1 405 does not support (can only be used on an enforcement module).

Is there a different tool to run on the SMS server?

I'm trying to gather more evidence to show we need to upgrade our unit, or atleast the ram. We've dipped about 1.3GiB into swap, which you would think is enough evidence.

[_Val_ · Accepted solution]

No, the utility is for Security gateways. You cannot use it to size  SmartCenter Server.

[NorthernNetGuy]

Thats makes sense. Is there any sizing utilities at all for the smartCenter Server?

[the_rock]

I personally never heard of one myself. But, you could run cpview from expert mode, that should give you enough.

[Chris_Atkinson]

cpstat (sk120341) and CPLogInvestigator are the places to start gathering sizing metrics.

[Denis_VINCENT]

Same error message running on a gateway R81.10 HF take 66.
SecureXL is enabled.

[_Val_]

@Denis_VINCENT what is the exact error you get?

[NorthernNetGuy]

Not sure if helpful but if @Denis_VINCENT is having the same issue of finding out of sizing, and seeing same errors as me ("The connection wit hthe server was lost. Any unsaved changes will be preserved")

We opened a TAC and ran the CP Doctor and found the following in the detailed_diag_report, which seems to indicate that we're overutilizing our server:

Daily Average Logging Rates:
Yesterday Avg Logs/sec: 450.14285714285717
Yesterday Avg Index/sec: 224
--------------------------------------------------------------------Yesterday Hourly Average Index/sec--------------------------------------------------------------------
| Domain | Mode |0-1 |1-2 |2-3 |3-4 |4-5 |5-6 |6-7 |7-8 |8-9 |9-10 |10-11 |11-12 |12-13 |13-14 |14-15 |15-16 |16-17 |17-18 |18-19 |19-20 |20-21 |21-22 |22-23 |23-24 |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|System Data |Files |213 |159 |142 |170 |176 |178 |186 |270 |319 |330 |386 |483 |349 |278 |245 |215 |175 |152 |143 |137 |130 |128 |121 |121 |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Indexing Status:
219900 logs in last 10 minutes in solr
366 logs per second in solr

Query Solr Logs by Product:
Hint : Extended logging has been detected
-------------------Today's Logs-------------------
| Product | Num Of Logs |
--------------------------------------------------
|HTTPS Inspection |11898787 (44.65%) |
|Firewall |11142006 (41.81%) |
|VPN |3162759 (11.87%) |
|Application Control |122469 (0.46%) |
|URL Filtering |117503 (0.44%) |
|Anti-Virus |105833 (0.40%) |
|Identity Awareness |96431 (0.36%) |
|Threat Emulation |5443 (0.02%) |
|CloudGuard IaaS |2843 (0.01%) |
|Mobile Access |2208 (0.01%) |
|Anti-Spam and Email Security |2085 (0.01%) |
|IPS |319 (0.00%) |
|System Monitor |198 (0.00%) |
|SmartConsole |149 (0.00%) |
|WEB_API |24 (0.00%) |
|ESOD |16 (0.00%) |
|Threat Extraction |4 (0.00%) |
|SmartEvent Client |4 (0.00%) |
|SmartDashboard |2 (0.00%) |
|Scheduled system update |1 (0.00%) |
--------------------------------------------------

Sizing status:
ERROR : In '405' machine (RAM:16 CPU: 4), the average Logging rate is 450 logs per second, while supported logging rate per machine size is 200 logs per second.