Navigation
Supported Platforms
Example: Configuring Static Source Translation on AMS Infrastructure
This example shows a static source translation configured on an AMS interface. The flows will be load balanced across member interfaces with this example.
Configure the AMS interface ams0 with load balancing options.
[edit interfaces ams0]
load-balancing-options {
member-interface mams-5/0/0;
member-interface mams-5/1/0;
}
unit 1 {
family inet;
}
unit 2 {
family inet;
}Configure hashing for the service set for both ingress and egress traffic.
[edit services service-set ss1]
interface-service {
service-interface ams0.1;
load-balancing-options {
hash-keys {
ingress-key destination-ip;
egress-key source-ip;
}
}
} | Note: Hashing is determined based on whether the service set is applied on the ingress or egress interface. |
Configure two NAT pools because you have configured two member interfaces for the AMS interface.
[edit services]
nat {
pool p1 {
address-range low 20.1.1.80 high 20.1.1.80;
}
pool p2 {
address 20.1.1.81/32;
}
}Configure the NAT rule and translation.
[edit services]
nat {
rule r1 {
match-direction input;
term t1 {
from {
source-address {
20.1.1.2/32;
}
}
then {
translated {
source-pool p1;
translation-type {
basic-nat44;
}
}
}
term t1 {
from {
source-address {
40.1.1.2/32;
}
}
then {
translated {
source-pool p2;
translation-type {
basic-nat44;
}
}
}
}
} | Note: A similar configuration can be applied for translation types dynamic-nat44 and napt-44. Twice NAT cannot run on AMS infrastructure at this time. |
