Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

Configuring Inline Static Destination NAT for Next Gen Services

date_range 06-Dec-23

Configuring the Destination Pool for Inline Static Destination NAT

To configure the destination pool for inline static destination NAT:

  1. Create a destination pool.
    content_copy zoom_out_map
    user@host# edit services nat destination pool nat-pool-name
    
  2. Define the addresses or subnets to which destination addresses are translated.
    content_copy zoom_out_map
    [edit services nat destination pool nat-pool-name]
    user@host# set address address-prefix
    
  3. To allow the IP addresses of a NAT destination pool to overlap with IP addresses in pools used in other service sets, configure allow-overlapping-pools.
    content_copy zoom_out_map
    [edit services nat]
    user@host# set allow-overlapping-pools
    

Configuring the NAT Rule for Inline Static Destination NAT

To configure the NAT destination for static destination NAT:

  1. Configure the NAT rule name.
    content_copy zoom_out_map
     [edit services destination source]
    user@host# set rule-set rule-set-name rule rule-name
    
  2. Specify the traffic direction to which the NAT rule set applies.
    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name]
    user@host# set match-direction (in | out)
    
  3. Specify the source addresses of traffic that the NAT rule applies to.

    To specify one address or prefix value:

    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set match source-address address
    

    To specify a range of addresses, configure an address book global address with the desired address range, and assign the global address to the NAT rule:

    content_copy zoom_out_map
     [edit services address-book global]
    user@host# set address address-name range-address lower-limit to upper-limit
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set match source-address-name address-name
    
  4. Specify the destination addresses that the NAT rule applies to.
    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set match destination-address address
    

    To specify a range of addresses, configure an address book global address with the desired address range, and assign the global address to the NAT rule:

    content_copy zoom_out_map
     [edit services address-book global]
    user@host# set address address-name range-address lower-limit to upper-limit
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set match destination-address-name address-name
    

    To specify any unicast address:

    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set match destination-address any-unicast
    
  5. Specify the NAT pool that contains the destination addresses for translated traffic.
    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name rule rule-name]
    user@host# set then destination-nat pool nat-pool-name
    
  6. Configure the generation of a syslog when traffic matches the destination NAT rule match conditions.
    content_copy zoom_out_map
     [edit services nat destination rule-set rule-set-name rule rule-name then]
    user@host# set syslog
    

Configuring the Service Set for Inline Static Destination NAT

To configure the service set for inline static destination NAT:

  1. Define the service set.
    content_copy zoom_out_map
     [edit services]
    user@host# edit service-set service-set-name
    
  2. Configure either an interface service set, which requires a single service interface, or a next-hop service set, which requires an inside and outside service interface.
    • To configure an interface service set:

      content_copy zoom_out_map
       [edit services service-set service-set-name]
      user@host# set interface-service service-interface si-slot-number/pic-number/0.logical-unit-number
      
    • To configure a next-hop service set:

      content_copy zoom_out_map
       [edit services service-set service-set-name]
       [edit services service-set service-set-name]
      user@host# set next-hop-service inside-service-interface si-slot-number/pic-number/0.logical-unit-number outside-service-interface si-slot-number/pic-number/0.logical-unit-number
      
  3. Specify the NAT rule sets to be used with the service set.
    content_copy zoom_out_map
     [edit services service-set service-set-name]
    user@host# set nat-rule-sets rule-set-name
    

Configuring Inline Services and an Inline Services Interface

To enable inline services and an inline services interface:

  1. Enable inline services for the FPC and PIC slot, and define the amount of bandwidth to dedicate to inline services.
    content_copy zoom_out_map
    [edit chassis si-fpc slot-number pic number port number]
    user@host# set inline-services bandwidth (1g | 10g | 20g | 30g | 40g | 100g)
    
  2. Configure the inline services logical interface or interfaces.
    • If you are using an interface service set, configure one logical unit:

      content_copy zoom_out_map
      [edit interfaces si-slot-number/pic-number/0
      user@host# set unit logical-unit-number family family
      
    • If you are using a next-hop service set, configure two logical units and define the inside and outside interfaces:

      content_copy zoom_out_map
      [edit interfaces si-slot-number/pic-number/0
      user@host# set unit logical-unit-number family family
      user@host# set unit logical-unit-number service-domain inside
      user@host# set unit logical-unit-number family family
      user@host# set unit logical-unit-number service-domain outside
      
footer-navigation