Skip to main content

Creating a Virtual Mobile Gateway

This page explains how to create a Virtual Mobile Gateway resource using the OCX Portal.

Preparation​

Please confirm the following before creating a Virtual Mobile Gateway resource:

  • Your User Role is either admin or user.

Remarks​

A Virtual Mobile Gateway is provided in a two-instance configuration for hardware redundancy. Each instance acts as a physical gateway to the mobile line. As these are designed to connect with an OCX-Router(v1) using BGP, please complete your network design in advance.

The following AS Numbers are reserved by RFC and cannot be used:

  • 0
  • 23456
  • 65535
  • 4294967295

When Direct Device Communication is turned on, devices with SIMs belonging to the same Virtual Mobile Gateway can communicate with each other using the IPv4 addresses assigned to the SIMs.

  • Traffic between SIMs is turned around within the Virtual Mobile Gateway and does not pass through equipment on the OCX network side (such as firewalls on the OCX-Router(v1) or on-premises equipment (CPE)). If you need to restrict traffic between SIMs, keep this setting off.
  • When turned off, traffic between SIMs is not delivered. However, traffic to an IPv4 prefix registered with a SIM Target Route is delivered to the target SIM regardless of this setting.
  • Only IPv4 traffic is supported.
  • Traffic is not delivered while the destination SIM is not connected to the mobile network.
  • This setting can be changed after creation. Changing it does not disconnect SIM communication.

Procedure for Creating a Virtual Mobile Gateway Resource​

  1. Log in to the OCX Portal.
  2. Click [Access Lines] from the left navigation bar.
  3. When the [Access Lines] sub-menu appears, click [Virtual Mobile Gateways (VMGs)].
  4. From the Virtual Mobile Gateways page, click [+ Create] in the upper right corner.
  5. The screen will switch to the Virtual Mobile Gateway resource creation steps. Configure the following items and click [Create].
    • Virtual Mobile Gateway
      • Name

        • Enter an arbitrary name. A recognizable name makes management easier.
        • Maximum length is 40 characters.
        • Leading and trailing whitespaces are automatically removed.
      • Maximum SIM Registration Limit

        • Select the maximum number of SIMs that can be registered to the Virtual Mobile Gateway from the drop-down menu.
        • This can be changed after creation.
        Maximum SIM Registration Limit
        100 SIMs
        1,000 SIMs
        10,000 SIMs
      • Local ASN

        • Enter the AS Number to be used by the Virtual Mobile Gateway. 4-byte ASNs are supported.
          *See the [Remarks] section for unusable AS Numbers.
      • Remote ASN

        • Enter the AS Number used by the destination OCX-Router(v1). 4-byte ASNs are supported.
          *See the [Remarks] section for unusable AS Numbers.
      • Direct Device Communication

        • Turn this on to allow communication between SIMs belonging to the same Virtual Mobile Gateway. It is off by default.
          *See the [Remarks] section for details.
    • Instance 1 / Instance 2
      • Local Address
        • Enter the IPv4 address for the instance in CIDR (IPv4/mask) format. (e.g., 169.254.0.1/30)
      • Remote Address
        • Enter the IPv4 address for the destination OCX-Router(v1). (e.g., 169.254.0.2)
      • MD5 Authentication Key
        • This is an optional parameter. If left blank, MD5 authentication will not be performed.
        • For MD5 authentication, you can set an alphanumeric string (A-Z, a-z, 0-9) between 6 and 80 characters.
  6. A confirmation pop-up will appear. Review the costs associated with creation and click [Create].
  7. Confirm that the created resource appears in the list with the status activated.
    *You can update the status by clicking [Refresh] in the upper right corner.

This completes the creation of the Virtual Mobile Gateway resource.

Once the Virtual Mobile Gateway resource is created, you can proceed to Create an Address Pool. For more details, please refer to the respective operation pages.