Dale's new X-station update mechanism is to use
  /afs/alm/ais/servers/xstations/bin/update_xstations

-------------------------------------------------------------------------------
Xstation boot log is at /var/spool/logs/bootpd.log
Config file is /etc/bootptab, which on 4-5-99 at least, is a link to
/afs/alm/rcf/servers/xstations/etc/bootptab


-------------------------------------------------------------------------------
Xstation information (including some of what is below) located in
  /afs/alm/rcf/servers/procedures-xstations

Xstation boot machines are ahab (9.1.24.48 & 9.1.72.48), moby (9.1.8.48),
and laurel (9.1.30.66).  Activity is kept in /var/spool/logs/bootpd.log,
the Xstation data is kept in /etc/bootptab.

The Xstation Network Setup page 2 (for ethernet) or 3 (for token ring) should
have the following fields set (this is stuff on the X-station)

   Gateway Internet Address          9.1.nn.253
   Terminal Internet Address         9.1.nn.nnn       Xstation ipaddress
   Host Internet Address             blank            if on ethernet
                                  or 9.1.24.48 (ahab-24!) if on token ring.
   Disable Bootp                     No
   * this makes it a directed boot request to the specified Host.

-------------------------------------------------------------------------------
On ahab, add the Xstation and use the network interface name that matches the
Xstation network type, model and subnet, e.g. et120-8 or tr130-72, as follows:
  smitty x_config  (fill in the blanks)

      *Xstation Name                 [joesx] * no .almaden.ibm.com

      *Xstation Network TYPE Name    [x_st_mgr.yynnn-zz] * most already defined
                                      yy=tr | et, nnn=130 | 120, zz=8 | 24 | 72

      *Hardware ADDRESS              [000000000000]
      *XDMCP Mode                    [direct]

      *xdmcp HOST                    [moby.almaden.ibm.com]  if subnet 8
                                   or laurel.almaden.ibm.com if subnet 24
                                   or ahab.almaden.ibm.com   if subnet 72

-------------------------------------------------------------------------------
  I wasted a lot of time one day trying to figure out why an X-station wouldn't
boot.  I deleted the X-station definition and re-added it (standard procedure
when this happens) many times, but I never got it to work.  Turns out that
X-station was already defined under a different name.  Checking the MAC
addresses verified that, e.g.
     /usr/lpp/x_st_mgr/bin/x_ls_trm | grep -i 23B9 (the last 4 MAC digits)
I checked and found 2 other sets of duplicately-defined X-stations, just
waiting to bite somebody.

-------------------------------------------------------------------------------
  Another afternoon was wasted one day when X-stations got the infamous,
non-descriptive error message "Could not read configuration file."
Dale finally got Tony to trace I.P. traffic with a sniffer and saw, 
big as life, a tftp request for a particular file, then the tftp response
with the error message (something like) "tftpd:  Disk access violation".

  It seems to me that a software iptrace, filtering between the x-station
server and the x-station itself, would have saw this.

-------------------------------------------------------------------------------

Dale says you can get into X-station diagnostics and see an error log if you
hit Ctrl-Break when the X-station is booting (the BOOTP/TFTP screen).  From
there you can clear or view the error logs.  Dale also says those screens
have never done him any good.