Create a Post
cancel
Showing results for 
Search instead for 
Did you mean: 
This widget could not be displayed.
1 Solution

Accepted Solutions
This widget could not be displayed.
5 Replies

Hi everyone,

I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:

 

1. Does purging previous revisions affect our current database/policy?

2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?

3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?

 

Thank you.

Regards

Jump to solution

Does purging previous revisions affect the current database/policy?

Jump to solution

Does purging previous revisions affect the current database/policy?

Jump to solution

Does purging previous revisions affect the current database/policy?

Hi everyone,

I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:

 

1. Does purging previous revisions affect our current database/policy?

2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?

3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?

 

Thank you.

Regards

Hi everyone,

I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:

 

1. Does purging previous revisions affect our current database/policy?

2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?

3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?

 

Thank you.

Regards

Hi everyone,

I had a high CPU utilization issue and tac suggested me to follow [https://support.checkpoint.com/results/sk/sk170059]. Just want to be 100% sure and try my best to avoid mistake or accident:

 

1. Does purging previous revisions affect our current database/policy?

2. Does the SK also do the same as attached screenshot, but just making it automatic/periodically?

3. My management server isn't an MDS, can I still use the command from SK170059 which says "for MDS"?

 

Thank you.

Regards

0 Kudos
0 Kudos
0 Kudos
the_rock
MVP Diamond
MVP Diamond
the_rock
MVP Diamond
MVP Diamond
the_rock
MVP Diamond
MVP Diamond

Im not so sure purging bunch of revisions will do anything for CPU. Has anyone actually determined what process is causing cpu issue?

Andy

Best,
Andy
"Have a great day and if its not, change it"

Im not so sure purging bunch of revisions will do anything for CPU. Has anyone actually determined what process is causing cpu issue?

Andy

Best,
Andy
"Have a great day and if its not, change it"

Im not so sure purging bunch of revisions will do anything for CPU. Has anyone actually determined what process is causing cpu issue?

Andy

Best,
Andy
"Have a great day and if its not, change it"
0 Kudos
0 Kudos
0 Kudos
rochim
Participant
rochim
Participant
rochim
Participant

there are few things has been done with tac so far & still going on:

view cpu processes, cpmdoc, clearing objects without worksession (based on cpmdoc), healthcheck, hw diag, cpinfo, migrate export for tac's lab & after generating cpmdoc report (again), tac suggested to purge old revisions. 

No exact conclusion yet. I assume it might be spec issue. But the customer will need a clear statement from tac, at least.

there are few things has been done with tac so far & still going on:

view cpu processes, cpmdoc, clearing objects without worksession (based on cpmdoc), healthcheck, hw diag, cpinfo, migrate export for tac's lab & after generating cpmdoc report (again), tac suggested to purge old revisions. 

No exact conclusion yet. I assume it might be spec issue. But the customer will need a clear statement from tac, at least.

there are few things has been done with tac so far & still going on:

view cpu processes, cpmdoc, clearing objects without worksession (based on cpmdoc), healthcheck, hw diag, cpinfo, migrate export for tac's lab & after generating cpmdoc report (again), tac suggested to purge old revisions. 

No exact conclusion yet. I assume it might be spec issue. But the customer will need a clear statement from tac, at least.

0 Kudos
0 Kudos
0 Kudos
the_rock
MVP Diamond
MVP Diamond
the_rock
MVP Diamond
MVP Diamond
the_rock
MVP Diamond
MVP Diamond

Personally, just my view, I dont see how purging old revisions would do anything in this case. Maybe if say mgmg server was lagging a bit or dashboard was slow. What process is consuming most cpu?

Andy

Best,
Andy
"Have a great day and if its not, change it"

Personally, just my view, I dont see how purging old revisions would do anything in this case. Maybe if say mgmg server was lagging a bit or dashboard was slow. What process is consuming most cpu?

Andy

Best,
Andy
"Have a great day and if its not, change it"

Personally, just my view, I dont see how purging old revisions would do anything in this case. Maybe if say mgmg server was lagging a bit or dashboard was slow. What process is consuming most cpu?

Andy

Best,
Andy
"Have a great day and if its not, change it"
0 Kudos
0 Kudos
0 Kudos
staboi
Participant
staboi
Participant
staboi
Participant

Something about java cpsead logindexer etc. (if I'm not mistaken bcs no access to customer's environment currently). 

& doctor log shows sizing error as the appliance can only support 300 logging/s, while the current average is 2000+ logs/s.

Something about java cpsead logindexer etc. (if I'm not mistaken bcs no access to customer's environment currently). 

& doctor log shows sizing error as the appliance can only support 300 logging/s, while the current average is 2000+ logs/s.

Something about java cpsead logindexer etc. (if I'm not mistaken bcs no access to customer's environment currently). 

& doctor log shows sizing error as the appliance can only support 300 logging/s, while the current average is 2000+ logs/s.

0 Kudos
0 Kudos
0 Kudos