Rev 3 Nov 17
52
4119855
A
A: Basic Configuration Requirements
This information is required for the initial configuration of the ACM so that it can be
installed inside a customer network, boot successfully, and be accessible for further
configuration.
The following items must be configured before the ACM can accept connections.
The enterprise network will have existing default routing rules that specify how traffic
from LAN devices is routed, usually toward the Internet. When an ACM is introduced,
the mobile address space will only be accessible via the ACM. The ACM's
Next Hop
Address
specifies how mobile traffic will reach the enterprise. For enterprise traffic to
reach the mobile network via the VPN, a reverse route must be added at the
intermediate router (between the ACM and an enterprise application).
The ACM is shipped with a default configuration template including an example VPN
connection specification. The example may be modified or a new VPN connection can
be defined. However, for the VPN connection to provide a communication channel
that will pass data beyond itself, the mobile address space and the enterprise address
space must be specified for your particular situation.
Table 1-1: Required ACM Configuration Items
Item
Note
Example
Outside IP address
and netmask
This address must be accessible from the
mobile network. In most cases, this is a
globally routable IP address.
Outside default
gateway
Needed in most cases. To be discussed prior
to shipping if this is not desired.
Public DNS server
Defaulted to opendns.org server
Public NTP server
Defaulted to public NTP pool
server 0.us.pool.ntp.org
Inside IP address
and netmask
This must be compatible with your enterprise
LAN address.
The default settings are
10.99.0.1/24.
Next hop address
Required if you have an intermediate router
between the ACM and your application
servers that are on a different network than
that of the ACM inside address.
10.99.0.2
Table 1-2: Address Space (Mobile and Enterprise) Definitions
Item
Note
Example
Mobile subnetwork(s)
Each AirLink gateway/router has an entire subnetwork. For
small implementations, a class C address can be assigned to
each device.
172.22.0.0/24 …
172.22.255.0/24
Enterprise subnetwork(s) If all mobile traffic must be routed through the VPN (full
tunnel) it needs to be specified as 0.0.0.0/0
If some mobile traffic should be allowed to bypass the tunnel,
then the tunneled traffic must be specified.
10.10.0.0/16
