- CheckMates
- :
- Products
- :
- CloudMates Products
- :
- Cloud Network Security
- :
- Discussion
- :
- autoprovision on domain with already existing gate...
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Are you a member of CheckMates?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
autoprovision on domain with already existing gateways
Trying to enable autoprovision on one domain, but this domain is having already some gateways in it. I've configured it and all is failing on API calls like this:
File "/opt/CPsuite-R80.20/fw1/scripts/autoprovision/monitor.py", line 1888, in __call__
2019-05-24 07:27:14,130 MONITOR INFO raise Exception('failed API call: %s%s' % (command, msg))
2019-05-24 07:27:14,131 MONITOR INFO Exception: failed API call: show-simple-gateway: Requested object [xxx] not found
I didn't found any documentation, that this cannot be done..also waiting on TAC response..
@Javier_Hijas any insight on this?
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does the gateway showing in the error message actually exist?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes, this gateway is normal gateway object.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Martin,
There could be two problems that may be resulting in this failure.
1. Rest API is not running properly on the MDS. If you can api status ensure there are no errors.
2. The MGMT API may be trying to make a call to the CPM database. If there are any failures this error could result in this failure.
Recommendations moving forward:
- Reboot the MDS. This will clear out all possible API connections and may also resolve the CPM issue if any.
- After reboot the issue continues capture and review the following debugs files.
$MDS_FWDIR/scripts/cpm_debug.sh -t crud -s debug
Replicate the issue
$MDS_FWDIR/scripts/cpm_debug.sh -t crud -s info
$MDS_FWDIR/scripts/cpm_debug.sh -r
Also highly recommend to ensure you are always at the latest autoprov-cfg version.
Thank you,
Dan Morris, Technology Leader, Ottawa Technical Assistance Center
There could be two problems that may be resulting in this failure.
1. Rest API is not running properly on the MDS. If you can api status ensure there are no errors.
2. The MGMT API may be trying to make a call to the CPM database. If there are any failures this error could result in this failure.
Recommendations moving forward:
- Reboot the MDS. This will clear out all possible API connections and may also resolve the CPM issue if any.
- After reboot the issue continues capture and review the following debugs files.
$MDS_FWDIR/scripts/cpm_debug.sh -t crud -s debug
Replicate the issue
$MDS_FWDIR/scripts/cpm_debug.sh -t crud -s info
$MDS_FWDIR/scripts/cpm_debug.sh -r
Also highly recommend to ensure you are always at the latest autoprov-cfg version.
Thank you,
Dan Morris, Technology Leader, Ottawa Technical Assistance Center
![](/skins/images/BFDD56B372A07FDFABDEF003EE622D96/responsive_peak/images/icon_anonymous_message.png)