R80 migration export rules about.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

R80 migration export rules about.

L1 Bithead

Hello,

 

When I run export commands at the customer, I get an error as follows. Anybody have an idea?

 

mgmt_cli show access-rulebase offset 0 limit 400 name "Internet Security" details-level "full" use-object-dictionary true --format json > RuleSet_0_400.json

 

code: "generic_err_invalid_syntax"
message: "Login request message processing failed"

 

Checkpoint API status

 

API Settings:
---------------------
Accessibility: Require ip 127.0.0.1
Automatic Start: Enabled

Processes:

Name State PID More Information
-------------------------------------------------
API Started 16256
CPM Started 9995 Check Point Security Management Server is running and ready
FWM Started 9031
APACHE Started 10391

Port Details:
-------------------
JETTY Internal Port: 50276
APACHE Gaia Port: 443
Apache port retrieved from: httpd-ssl.conf


--------------------------------------------
Overall API Status: Started
--------------------------------------------

API readiness test SUCCESSFUL. The server is up and ready to receive connections

Notes:
------------
To collect troubleshooting data, please run 'api status -s <comment>'

 

 

Cheers.

Sezo

1 REPLY 1

L5 Sessionator

Try changing the upper limit from 400 to 50. 

 

Ive seen issues with trying to export too many rules upfront.

  • 2258 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!