
Connecting ASN Routers and BNX Platforms to a Network
A-6
Do the following:
1. Make sure that you have at least one interface configured, after booting,
through which the file server that supplied the kernel image can be
reached.
2. Make sure that all the application files (files with .exe filename extensions)
reside in the same directory as the kernel image.
3. Use Site Manager to make sure that IP is enabled and TFTP is created in
the ASN’s configuration file.
Refer to “Verifying the BOOTP Server Setup” later in this appendix.
4. Use Technician Interface commands to verify or correct the status of the
synchronous or Ethernet connectors used for network booting.
• Make sure that the appropriate drivers are running.
• If the ASN is Netbooting with a synchronous connector, make sure that
clocking is set properly for your site (internal or external).
Refer to Using Technician Interface Software for instructions.
Identifying Remote Connectivity Problems
The sections that follow provide guidelines for isolating a router addressing
problem or a Netboot problem, either of which can lead to a startup or
connectivity failure.
Displaying Messages from the ASN
If you cannot connect to the ASN using Site Manager, we recommend that you
connect the ASN to a modem or console.
If you cable the ASN to a modem, you can dial in and connect to the ASN
remotely. This setup provides the same capabilities as an on-site console
connection. Modem communications, however, are slower.
Viewing an ASN error message and entering commands through a modem
connection may simplify troubleshooting if you are not at the ASN site. As an
alternative, you can ask the person at the ASN site to read the console messages to
you and then you can enter the commands you want.
Comentarios a estos manuales