Oki ML591 Users' Guide for the OkiLAN 6010e - Page 153

RARP or BOOTP, UNIX BOOTP, might not have reread the new

Page 153 highlights

Section IV - TCP/IP RARP or BOOTP If you are using a BOOTP or RARP server and the OkiLAN 6010e is not getting an IP address, check the following: • Verify the BOOTP/RARP configuration files are correctly set up ("/etc/ethers" and "/etc/hosts" for RARP and "/etc/bootptab" for BOOTP). Verify the files have the correct hardware address of the OkiLAN 6010e. If using RARP, check that the hostnames are the same between the "/etc/ethers" and "/etc/hosts" files. UNIX BOOTP If you are running UNIX, try the following methods with the BOOTP server (check the documentation for your particular UNIX flavor). • Verify the BOOTP server has reread the "/etc/bootptab" file when the new entry was added. If the BOOTP server was running when you added the new entries, the server might not have reread the new bootptab file. Try sending the SIGHUP signal to the running BOOTP server. For example, kill -HUP tells it to reread "/etc/bootptab". Most BOOTP servers support this option. Check your local BOOTP documentation. If this does not work, restart the BOOTP server (kill and restart the process). OKI OkiLAN 6010e User's Guide IV - 63 TCP/IP

  • 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
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230

TCP/IP
IV - 63
Section IV - TCP/IP
OKI OkiLAN 6010e User’s Guide
RARP or BOOTP
If you are using a BOOTP or RARP server and the
OkiLAN 6010e is not getting an IP address, check the
following:
Verify the BOOTP/RARP configuration files
are correctly set up (“/etc/ethers” and
“/etc/hosts” for RARP and “/etc/bootptab”
for BOOTP). Verify the files have the correct
hardware address of the OkiLAN 6010e. If
using RARP, check that the hostnames are
the same between the “/etc/ethers” and
“/etc/hosts” files.
UNIX BOOTP
If you are running UNIX, try the following methods
with the BOOTP server (check the documentation for
your particular UNIX flavor).
Verify the BOOTP server has reread the
“/etc/bootptab” file when the new entry was
added. If the BOOTP server was running
when you added the new entries, the server
might not have reread the new
bootptab
file.
Try sending the SIGHUP signal to the
running BOOTP server. For example,
kill
HUP
<
process id of bootpd
> tells it to
reread “/etc/bootptab”. Most BOOTP servers
support this option. Check your local
BOOTP documentation. If this does not
work, restart the BOOTP server (kill and
restart the process).