Motorola V186 User Manual - Page 121

For MDLC over iDEN, MDLC over Tetra, and MDLC over Standard or Null Modem, Site ID, Link ID

Get Motorola V186 - Cell Phone - GSM PDF manuals and user guides View all Motorola V186 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 121 highlights

Communications 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 Link ID LINE1 LINE2 IP Address or Host name 10.5.1.160 155.9.1.17 The following IP Conversion Table should be loaded to the FEP: Site ID 1 1 2 2 Link ID LINE1 LINE2 LINE1 LINE2 IP Address or Host name 192.5.1.161 155.9.1.18 192.5.1.162 155.9.1.19 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 Link ID LINE1 LINE2 IP Address or Host name FEP1.moto.com FEP2.moto.com 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. 117

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
Communications
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
Link ID
IP Address or Host name
100
LINE1
10.5.1.160
100
LINE2
155.9.1.17
The following IP Conversion Table should be loaded to the FEP:
Site ID
Link ID
IP Address or Host name
1
LINE1
192.5.1.161
1
LINE2
155.9.1.18
2
LINE1
192.5.1.162
2
LINE2
155.9.1.19
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
Link ID
IP Address or Host name
100
LINE1
FEP1.moto.com
100
LINE2
FEP2.moto.com
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.
117