ip nat range-list limitations in L3 partition
Hi,
I have a deployment that requires the feature of range list in SLB to statically mapping of subnets.
here's the scenario:
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,
I have a deployment that requires the feature of range list in SLB to statically mapping of subnets.
here's the scenario:
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,
0
Comments
Any help on this?
Thanks