- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-02-2012 05:59 AM
After updating Policy and Nat Rules, I got the follow commit errors:
- Error: Error: Error updating NAT IP pools
- Error: response from cfgpush.s1.dp1.comm.cfg-dp: Error updating NAT IP pools
This error still occurs if i disable (or even delete) the newly added rules. Since i did a commit ~10min before, i am sure, i didn't changed anything else.
So, i am looking for an advanced command which gives me more info (which object causes this error). Hope somebody can help me.
07-02-2012 07:19 AM
Seems the second last commit was failed and a NAT Rule from there was the issue.
Changing the NAT IP pool from x.x.x.0/26 to x.x.x.1 solved the issue (on a new rule from the second last commit). Since i am using "dynamic-ip-and-port", having just one ip is no big deal. But i am still asking me, why I am not able to define a /24 network as IP Pool. I am even more confused if i am looking at other NAT rules which have a /26 network as IP Pool. So, this shouldn't be a problem.
Is there somewhere a limit for IP Pool addresses?
07-02-2012 07:19 AM
Seems the second last commit was failed and a NAT Rule from there was the issue.
Changing the NAT IP pool from x.x.x.0/26 to x.x.x.1 solved the issue (on a new rule from the second last commit). Since i am using "dynamic-ip-and-port", having just one ip is no big deal. But i am still asking me, why I am not able to define a /24 network as IP Pool. I am even more confused if i am looking at other NAT rules which have a /26 network as IP Pool. So, this shouldn't be a problem.
Is there somewhere a limit for IP Pool addresses?
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!