TFTP Netbooting with UNIX UPDATED: August 31, 1999 SUMMARY: Lucent remote access  products support netbooting over tftp which is booting off an image file located on another host using tftp (trivial file transfer protocol) to actually move the file from the host to the Lucent box. This technote details how to netboot using a UNIX host.  QUICK STEPS:   Download a netboot image Setup TFTP on UNIX host Turn off the PortMaster Raise dipswitches 1 and 2 Connect PortMaster (TM) to a console via a null modem cable Power on the PortMaster Press 'ESC' to get prompt and give PortMaster an ip address '> address xxx.xxx.xxx.xxx' TFTP the image from UNIX host '> tftp yyy.yyy.yyy.yyy' The y's being the ip address of the UNIX host. BEFORE YOU START:   An ethernet connection between the UNIX host and the PortMaster   An binary image file to boot with from Lucent's ftp site: ftp.ra.lucent.com/pub/le/netboot PREPARING THE UNIX HOST FOR NETBOOT: Make a directory to tftp from. umask 22 mkdir /tftpboot ln -s . tftpboot From Lucent's FTP site download a generic image as a binary file. For best results be sure to double check the byte count between the downloaded file and the file on the ftp site. ftp.ra.lucent.com/pub/le/netboot   Place the GENERIC file into the tftpboot directory.   mv GENERIC.PM2 /tftpboot/GENERIC.PM2 Uncomment the tftpd from the /etc/inetd.conf file and save the file. #tftp dgram udp wait nobody /usr/libexec/tcpd tftpd Restart the inetd daemon. % ps -aux | grep inet root  295 0.0 0.2 148 188 ?? Is 4:49PM 0:00.27 inetd % kill -HUP 295   # 295 is the Process Id  of the inetd program PREPARING A CONSOLE FOR NETBOOT:   In order to netboot you must issue at least two commands from a console connected to S0.  Turn off the PortMaster Set dipswitches 1 and 2 on/up. The bank of 5 dipswitches is found on the back of the Lucent next to a single green LED and are numbered from left to right. (1) Set dip switch 1 on or up.   - This forces port S0 into 9600,8,N,1 which will allow you to connect to S0 over the null modem cable to issue commands to the PortMaster. (2) Set dip switch 2 on or up - This forces the Lucent box to boot in Netboot mode.   Connect the PortMaster's S0 port to a serial port or COM port on the machine being used as a console with a NULL modem cable. On the Machine being used as a console configure a terminal program to 9600,8,N,1. Example: Setting Hyper Terminal that comes with MS-Windows 95 and MS-Windows NT 4.x - Click on the "Start" Button - Select "Programs" then "Accessories" then "Hyper Terminal" from the menus. - Once Hyper Terminal is running you see a window labeled "Connection Description". Here pick a name and icon of your choice. - After clicking "OK" you'll have a window labeled "Phone Number". At the bottom from the option labeled "Connect Using" select "Direct to Com x" and click "OK". - The next window "COM Properties" configure to the following and the click "OK". Bits per second - 9600 Data bits - 8 Parity - None Stop bits - 1 Flow Control - Hardware Example: Setting MS-Windows 3.x Terminal program found under the "Accessories" group. - Start the Terminal program - Select "Settings" from the menu-bar and then "Communications" from the sub-menu. - Select the COM port you have connected the NULL modem to on your PC. - Change the speed from 1200 (default) to 9600 - Click "OK", all other settings should work with their default settings. NETBOOTING:   With console connect boot up the PortMaster which will look similar to the following. Livingston Enterprises, Inc. Boot Prom Rev M   Testing Low Memory.... Testing System Clock.... Testing System Memory.... 1024K Checking Boot Rom.... Calibrating.... 33MHz Starting Net Boot..... When you see the RARP's (Reverse Arps) press the 'Esc' key and you will be given a prompt.  Sending RARP request for 0:c0:5:1:61:a7 Sending RARP request for 0:c0:5:1:61:a7 Sending RARP request for 0:c0:5:1:61:a7 From the prompt you can set gateway, netmask and ip address (syntax below) but you only need to give the portmaster an ip address if you are doing the netboot from the same ethernet segment.  > address [ip address for the PortMaster] > netmask [netmask in dotted decimal] > gateway [ip address of gateway router] Next transfer the image from your Windows 95 host.  > tftp [ip address of UNIX] The PortMaster will first look for a filename using its ip address translated into hex. If that is not found it will then look for GENERIC.PM2. Upon successfully netbooting the PortMaster will automatically reboot itself.  > address 10.0.0.9               # assigned the portmaster an ip off 10.0.0.9 OK > tftp 10.0.0.10                 # net booting of Win95 host found at 10.0.0.10 Starting tftp... Requesting tftp of A000009.PM2 from server a00000a Request failed - 1   File not found Requesting tftp of GENERIC.PM2 from server a00000a Loading Image at 0fff0000 336496 tftp complete Verifying Load Module Checksum... Starting Load Module ... Sizing Physical Memory ... 1Mb Testing High Memory ... . 1024K Found 11 ports.... Running ComOS...     PortMaster Console login: CLEANUP: * In most cases after netbooting you will want to upgrade the PortMaster using PMConsole (TM) or PMInstall (TM) to have a more permanent version of the ComOS. * Be sure to put dipswitch 2 back down so you don't go into netboot mode each time the unit is powered up. TROUBLESHOOTING: * PORTMASTER DOES NOT REBOOT AFTER NETBOOT - Wait it can take a few minutes sometimes. - Verify the byte count of the image file vs. the file on the ftp site. - Download it again as a binary file. * SOLID LED ON OR OFF. IF the green LED next to the dip switches not flash off once every 5 seconds call Lucent technical support and keep your phillips screwdriver handy. * NOTHING SEEN ON THE CONSOLE - Make sure the PortMaster  is on, plugged in with the Null modem firmly attached to S0 and chances are its the cable. * GETTING GARBAGE ON THE CONSOLE - DTE speed mismatch. Make sure that your terminal is set to 9600 baud. - IRQ mismatch. If you have another device that is using the IRQ of your COM port you'll see garbage from the other device. - Use a different COM port. - Swap NULL modem cable. - Try another hardware device for your terminal. * ERROR MESSAGE ON BOOT UP, "PANIC WATCHDOG ERROR" - Call Lucent Technical Support. Have your console ready on S0. This may be a problem with the NVRAM. * ERROR MESSAGE ON BOOT UP, "SHARED MEMORY ERROR" - Call Lucent Technical Support. Have your console ready on S0.