
B-1
Appendix B
Implementation Notes
This appendix contains implementation hints, reminders, and a few important
notes you might have missed earlier in this guide.
Notes
• Bay Networks currently supports BOOTP service on UNIX workstations, but
not on PCs. To use Netboot when your Site Manager workstation is a PC,
transfer the image and configuration files from the PC to a UNIX workstation
that is configured as a BOOTP server.
• You cannot use EZ-Install or Netboot directly from an ASN Token Ring or
FDDI interface.
• You need Version 8.10 (BNX Version 5.00) or later to perform Directed
Netboot.
• If you have a LAN protocol analyzer available, you may want to use it to
troubleshoot BOOTP server communication errors. (Appendix A provides
guidelines for using Packet Capture and an analyzer to isolate these errors.)
• Versions earlier than 7.80 (BNX Version 5.00) do not include the Technician
Interface Packet Capture utility.
Note: You can change the name of the asn.exe file in the local file system —
even if the
bconfig command is
boot image=network.
If you change the
name of the software image file, you must use the form
<new_name>.exe
.
When you boot with a renamed image, you are performing a “named boot.”
However, this does not affect the pathname of the image retrieved from the
network. The “
-
” (no volume) symbol allows a named boot or configuration if
at least one of the two
bconfig settings is local.
Comentarios a estos manuales