Lantronix MPS100 EPS Reference Manual - Page 20

Dynamic Host Control Protocol DHCP, Simple Network Management Protocol SNMP

Page 20 highlights

TCP/IP Concepts A unique IP address must be specified on the Server before any of the TCP/IP functionality is available. See your Installation Guide for more information on configuring the IP address. A DHCP server can be used to temporarily assign a leased IP address to the Server. See Dynamic Host Control Protocol (DHCP) on page 12-6 for more information. 2.6.2 Dynamic Host Control Protocol (DHCP) DHCP, an extension to BOOTP, allows network administrators to lease IP addresses to network nodes as needed. Server servers offer two levels of DHCP support: boot and runtime. If your Server has boot mode DHCP support, the Server will attempt to acquire an IP address via DHCP at boot time. If it succeeds, the Server will save the IP address into NVR and continue with the boot process. Once running, the Server's operational code will attempt to acquire the same IP address from the DHCP server. If for some reason the runtime DHCP request fails (for example, if there is no response for 15 seconds), the Server will use the address saved in NVR. If your Server does not support DHCP at the boot level, you can still use DHCP at the operational level. To enable DHCP in the runtime code, enter the Set/Define Server DHCP Enabled command and reboot the server. Note: Enabling DHCP will remove the IP address saved in NVRAM, if there is one. The Server will use BOOTP or RARP to acquire an IP address at boot time, and then it will request an IP address via DHCP once it is running. If the runtime DHCP request fails, the server will use the IP address stored in NVRAM. If the DHCP request succeeds, the Server will use the resulting IP address. It will not save the IP address to NVRAM or overwrite the saved address (the one acquired by BOOTP or RARP). If you enter a new IP address with the Set/Define Server IPaddress command, the Server will assume that you want to use that address in the future, and will disable DHCP. Note: When DHCP is used, the IP address saved in NVRAM will change each time the Server boots, and the List Server Bootparams command (which shows the characteristics that will be in effect the next time the Server boots) may show a different IP address than the one that is currently in use. 2.6.3 Simple Network Management Protocol (SNMP) The Server supports the SNMP network protocol, which allows hosts on the network to query nodes for counters and network statistics and change some parameters on those nodes. The form of these requests is documented by RFC 1098. The list of items that can be queried and/or set and the type of data used, such as integer and string, are both documented in various Management Information Bases (MIBs). MIBs cover a variety of things, such as parallel port status, counters, and IP address resolution tables. The Server supports the following MIBs: MIB-II (RFC 1213) System, Interface, Address Translation, IP, ICMP, TCP, and UDP, but not the EGP group. Parallel MIB (RFC 1660)All parallel devices. Serial MIB (RFC 1659)All Serial devices. 2-6

  • 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
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223

TCP/IP
Concepts
2-
6
A unique IP address must be specified on the Server before any of the TCP/IP functionality is available. See
your
Installation Guide
for more information on configuring the IP address.
A DHCP server can be used to temporarily assign a leased IP address to the Server. See
Dynamic Host
Control Protocol (DHCP)
on page 12-6 for more information.
2.6.2
Dynamic Host Control Protocol (DHCP)
DHCP, an extension to BOOTP, allows network administrators to lease IP addresses to network nodes as
needed. Server servers offer two levels of DHCP support: boot and runtime.
If your Server has boot mode DHCP support, the Server will attempt to acquire an IP address via DHCP at
boot time. If it succeeds, the Server will save the IP address into NVR and continue with the boot process.
Once running, the Server’s operational code will attempt to acquire the same IP address from the DHCP
server. If for some reason the runtime DHCP request fails (for example, if there is no response for 15
seconds), the Server will use the address saved in NVR.
If your Server does not support DHCP at the boot level, you can still use DHCP at the operational level. To
enable DHCP in the runtime code, enter the
Set/Define Server DHCP Enabled
command and reboot the
server.
Note:
Enabling DHCP will remove the IP address saved in NVRAM, if there is one.
The Server will use BOOTP or RARP to acquire an IP address at boot time, and then it will request an IP
address via DHCP once it is running. If the runtime DHCP request fails, the server will use the IP address
stored in NVRAM. If the DHCP request succeeds, the Server will use the resulting IP address. It will
not
save the IP address to NVRAM or overwrite the saved address (the one acquired by BOOTP or RARP).
If you enter a new IP address with the
Set/Define Server IPaddress
command, the Server will assume that
you want to use that address in the future, and will disable DHCP.
Note:
When DHCP is used, the IP address saved in NVRAM will change each time the
Server boots, and the List Server Bootparams command (which shows the
characteristics that will be in effect the next time the Server boots) may show a
different IP address than the one that is currently in use.
2.6.3
Simple Network Management Protocol (SNMP)
The Server supports the SNMP network protocol, which allows hosts on the network to query nodes for
counters and network statistics and change some parameters on those nodes. The form of these requests is
documented by RFC 1098. The list of items that can be queried and/or set and the type of data used, such
as integer and string, are both documented in various Management Information Bases (MIBs). MIBs cover
a variety of things, such as parallel port status, counters, and IP address resolution tables.
The Server supports the following MIBs:
MIB-II (RFC 1213)
System, Interface, Address Translation, IP, ICMP, TCP, and UDP, but not the
EGP group.
Parallel MIB (RFC 1660)
All parallel devices.
Serial MIB (RFC 1659)
All Serial devices.