Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[MX] Commit is not successful if both NAT rules are being configured under NAT rule-set

0

0

Article ID: KB36361 KB Last Updated: 15 Dec 2020Version: 1.0
Summary:

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;
Symptoms:

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
Solution:

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

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search