Avaya Connecting ASN Routers and BNX Platforms to a Network Manual de usuario Pagina 92

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 106
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 91
Connecting ASN Routers and BNX Platforms to a Network
A-12
The sample messages in Table A-1 show the sequence of messages when a
BOOTP exchange is successful.
Verifying the BOOTP Server Setup
Refer to these instructions if the BOOTP server is receiving BOOTP requests but
failing to respond, or failing to forward the kernel, configuration, application, or
string files.
Verify the BOOTP server setup as follows:
1. Make sure that the kernel image and all of the application (.exe) files are
in the same directory.
Table A-1. BOOTP Messages
Message Explanation
hostname:/etc> request from IP addr
192.16.24.12
The UNIX hostname, the path (
/etc
) of the
bootptab
file, and the IP address of the
ASN.
found 192.16.24.12 ASN.Boston The IP address (192.16.24.12) mapped to
the ASN’s hostname, ASN.Boston, in the
bootptab
file.
bootfile2 /$HOME/.builder_dir/
rel900/asn krnl_an.exe
The pathname of the kernel file, as
specified in the
bootptab
file.
couldn't access /$HOME/
.builder_dir/rel900/asn
krnl_asn.exe.ASN.Boston
Disregard this message. The BOOTP
server tries to access the ASN host both by
its name and by its IP address. The
“couldn’t access” message means that the
server tried to access a host named
“ASN.Boston” but failed because the ASN is
not named. The attempt to access the ASN
by its IP address succeeds, as you can infer
by reading the last message.
vendor magic field is 99.130.83.99 Disregard this message.
sending RFC1048-style reply The BOOTP server is sending a BOOTP
response in compliance with RFC 1048.
Vista de pagina 91
1 2 ... 87 88 89 90 91 92 93 94 95 96 97 ... 105 106

Comentarios a estos manuales

Sin comentarios