Skip to main content

Adding NAT IP Addresses

This page explains the Add NAT IP Address feature in the OCX Portal.

Remarks​

  • For some XaaS Connections, one initially assigned NAT IP address is provided when the resource is created.
  • On the NAT IP Address list page, you can check the number of active sessions for each NAT IP address. This value is updated every 5 minutes.
  • As a guideline, approximately 62,000 sessions are supported per NAT IP address.
  • If the number of sessions increases, consider adding additional NAT IP addresses.

Prerequisites​

Before adding a NAT IP address, please confirm the following:

  • Your User Role is either admin or user.
  • The target XaaS Connection resource is in either the available or attached state.

Procedure for Adding NAT IP Addresses​

  1. Log in to the OCX Portal.

  2. From the left navigation bar, click [XaaS Connections].

  3. From the XaaS Connections list page, click the target XaaS Connection resource.

  4. In the lower half of the OCX Portal screen, click the NAT IP Addresses tab, then click [+] Add NAT IP Address.

  5. The NAT IP address addition screen will be displayed. Configure the following item and click [Add].

    • Quantity
      • Enter the number of NAT IP addresses to add.
      • You can enter an integer between 1 and 4.
        • The maximum number of NAT IP addresses that can be assigned to a single XaaS Connection resource is 5, including the initially assigned NAT IP address that is automatically allocated at creation.
        • NAT IP addresses are automatically assigned by the system and cannot be specified by the customer. You can check the assigned NAT IP addresses after they have been added.

  6. An addition confirmation pop-up will appear. Review the settings and click [Add].

  7. The NAT IP Addresses list page will be displayed, and the newly added NAT IP addresses will appear under NAT IP Addresses.

This completes the addition of NAT IP addresses.

Notes​

  • When adding NAT IP addresses, all existing NAT sessions will be deleted.
  • As a result, communication interruptions will occur on all currently active NAT IP addresses for the target XaaS Connection resource.
  • Please take care if there are applications actively communicating using NAT.
  • The duration of the communication interruption depends on the application behavior when sessions are disconnected and re-established.