Motorola V186 - Cell Phone - GSM System Planner Manual page 121

In the example above, two sets of IP conversion tables should be created and the FEP's
Table should be assigned to the RTUs:
The following IP Conversion Table should be loaded to the RTUs:
Site ID
100
100
The following IP Conversion Table should be loaded to the FEP:
Site ID
1
1
2
2
As another example the IP conversion table can be set with names rather than numeric
IPv4 addresses. In this case make sure these names are the full host names set by your
network administrator. Make sure the DNS Servers are either learned (DHCP or PPP) or
set them manually in port configuration (Static LAN).
In this example assume the operator has assigned two names for the FEP:
• FEP1.moto.com for port LINE1
• FEP2.moto.com for port LINE2.
The following IP Conversion Table should be loaded to the RTUs:
Site ID
100
100
In this example, LINE2 is Static LAN so the user needs to set the DNS servers of LINE2
network in the LINE2 port configuration of RTU #1 and RTU #2. LINE1 is PPP, so there
is no need to set these servers – they are learned from the network automatically.
In principle it is recommended to create two sets of IP conversion tables – one that will
be assigned to an FEP/IP Gateway on the LAN, and one to all other RTUs which are
connected with the ASTRO IV&D radios. The first will include the above information
concerning each RTU, and the second will have only the FEP/IP Gateway.
For MDLC over iDEN, MDLC over Tetra, and MDLC over Standard or Null Modem,
consult the system provider for the infrastructure relating to the IP addresses.
Link ID
LINE1
LINE2
Link ID
LINE1
LINE2
LINE1
LINE2
Link ID
LINE1
LINE2
117
Communications
IP Address or Host name
10.5.1.160
155.9.1.17
IP Address or Host name
192.5.1.161
155.9.1.18
192.5.1.162
155.9.1.19
IP Address or Host name
FEP1.moto.com
FEP2.moto.com