LanGuardian Boot PROM


Console Configuration

The LanGuardian console port should be configured as described in this document.

Boot Message

When a LanGuardian is powered on, the following message should be printed to the console port. If this doesn't happen, either the machine is dead or the serial connection to your terminal is not correct.

Copyright (C) 1992-1993 by RTMX, Inc.  All rights reserved.
LG-2 ROM Rev: 09/29/95 PCB Rev: A 
System Serial #: 77

*** Power-on Self Test:
DRAM       ........: PASSED
FPGA       ........: PASSED
ETHERNET 0 ........: PASSED
ETHERNET 1 ........: PASSED
HD64570    ........: PASSED
SCSI       ........: PASSED
FDC765     ........: PASSED

RTMX Auto-boot - hit ^C to abort
 10 seconds to auto-boot

Entering the PROM monitor.

A LanGuardian has a default boot method stored in the non-volatile storage on the machine (an EEPROM). The machine will attempt to boot from this default after a short (normally 10 second) timeout, during which time the machine may be interrupted by a control-C character presented on the console port.

As one would expect with any reasonably modern machine, there is a functional monitor program present in the onboard PROM. This monitor program has a builtin command menu, accessible via the help command.

The help menu:

>> help
help                                      Display command help
cache       [Data][Instruction][None]     Set/show cache mode[s]
radix       [hex/dec]                     Set/show default input radix
size         [byte/word/long]             Set/show default access size
bf          [/bwl] <start> <end> <value>  Fill memory with pattern
bt          [/bwl] <start> <end> <value>  Test memory for pattern
bm          [/bwl] <start> <end> <dest>   Copy block of memory
md          [/bwl] <start> [<end>]        Dump memory
mm          [/bwl] <addr>                 Modify memory
rd                                        Show registers
rm          [<reg>]                       Modify [one or more] register[s]
di          <start> [<end>]               Disassemble instructions
br          [/c] [<addr>]                 Set/Show/Clear breakpoints
env         [/d]                          Default/Show/Modify Environment
rom_env     [/d]                          Default/Show/Modify Environment
probe_scsi                                Initialize SCSI Subsystem
nb          [/h] [le0/le1] [<args>]       Boot (load/execute) a program via le?
bo          [/h] [fd0/sd0] [[<]<file>]    Boot (load/execute) program from disk
sense                                     Show/Modify pseudo Sense Switch
diag                                      Run built-in diagnostics
clock_off                                 Save time of day battery

PROM environmental variables

The PROM on the LanGuardian has the concept of an environment -- similar to that of a Sun3 or SparcStation, but more limited in scope. The current contents of the environment can be accessed via the env command. Note: If you run this command, you must continue to hit enter repeatedly, for each line of output. Or, you can change the value and then hit enter.

>> env
   DRAM SIMM Size: 4M 
   Ethernet port 0 = 00:C0:87:00:00:9A
   Ethernet port 1 = 00:C0:87:00:00:9B
   Auto boot = Y 
   Auto boot timeout = 10 
   Boot Device = fd0 
   Boot Spec =  
   Power-on Self Test = Y 
   Secure [Encrypted] Network Load = N 
   Network Boot Mode: TFTP 
   Ethernet Port 0 IP Address = 192.168.215.32
   Ethernet Port 0 SERVER Address = 192.168.215.21
   Ethernet Port 1 IP Address = 0.0.0.0
   Ethernet Port 1 SERVER Address = 0.0.0.0
   Configuration File = /tftpboot/lg2.boot 

Update NVRAM (y/n)? n

Default Boot Method

Using the env command, one can set the default boot method to be network. To enable this, one must set the IP address for the LanGuardian and the server machine that it is boot from in the boot environment, and then power cycle the machine.

The LanGuardian does NOT use rarp or dhcp to automatically determine its initial IP address while netbooting. If your security device will believe any answer given to it over the network, it isn't going to be very secure. (This is why there is an encrypted network boot mode!)

Last Updated: $Date: 2003/01/13 18:02:00 $