# ip nat range-list limitations in L3 partition

**URL:** <https://community.a10networks.com/t/ip-nat-range-list-limitations-in-l3-partition/166>\
**Category:** System\
**Created:** [September 23, 2012, 8:51am UTC](https://community.a10networks.com/t/ip-nat-range-list-limitations-in-l3-partition/166 "2012-09-23T08:51:49Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dbanares](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@dbanares](https://community.a10networks.com/u/dbanares)\
**Post date:** [September 23, 2012, 8:51am UTC](https://community.a10networks.com/t/ip-nat-range-list-limitations-in-l3-partition/166/1 "2012-09-23T08:51:49Z")

</div>

Hi,

I have a deployment that requires the feature of range list in SLB to statically mapping of subnets.  
here’s the scenario:

```auto
I created two partitions in AX, and configure a range list in 1st parition "ip nat range-list 10.10.10.0 /24 192.168.0.0 /24 count 254.
I also want to configure the same 10.10.10.0 /24 and map to other nat ip in the second partition: "ip nat range-list 10.10.10.0 /24 172.16.0.0 /24 count 254" but the system won't allow me due to the limitations.

```

I’m thinking if aFlex scripting can do this, could you help me how to do it in aFlex scripting?

Thanks,

---

<div class="post-metadata">

**Author:** ![dbanares](https://avatars.discourse-cdn.com/v4/letter/d/ecccb3/32.png) [@dbanares](https://community.a10networks.com/u/dbanares)\
**Post date:** [October 2, 2012, 8:13am UTC](https://community.a10networks.com/t/ip-nat-range-list-limitations-in-l3-partition/166/2 "2012-10-02T08:13:31Z")

</div>

Hi,

Any help on this?

Thanks