This article explains how the same subnet cannot be used as destination-prefix in different NAT rules with different translation types configured. APP is applied for all related NAT rules and commit fails with error.
TP-NAT-1-re0# show | compare [edit services nat rule-set RULE-1-IPv6] rule RULE-NAT464 { ... } + rule RULE-NAT64;
re0# show groups RULE-NAT64-X, the destination-prefix then { translated { destination-prefix 11:ff1a::/96;
The following error is seen:
error: ms-interface does not support usage of same pool () across terms with different translation types error: configuration check-out failed
Create another group: RULE-NAT64-X-new which is to be applied under rule RULE-1-NAT64.
In group RULE-NAT64-X-new , the destination-prefix was changed to another value than 11:ff1a::/96 . After that, RULE-1-NAT64 was able to be applied to rule-set RULE-1-IPv6 which has already applied rule RULE-1-NAT464