| Brendan,
Here is a really old collection of hints and sundry information I wrote
long ago back when we used to use VXT2000s in our shop. Its relevance to
4.x may be iffy, but there might be a few things in here that are worth
something to you.
Of course you'll want to replace the IP addresses and names with your own,
since these are registered.
Standard disclaimers apply. I sorta knew what I was doing but I wouldn't
guarantee complete accuracy. ;-)
Craig
(This file is located at zaxxon in ~craig/public/vxt2000-info.txt)
HINTS ON GETTING VXT2000s TO RUN ON OSF/1 HOSTS
CRAIG PAHIGIAN
DTN 285-3691
craig@nio.dec.com
2/24/94, 3/18/94
Boot flags
----------
b/10000 Boot, look for all possible protocols (MOP first)
b/100 Boot, allow specification of load file
b/101 Boot conversationally using VXTLDR (InfoServer)
b/10100 Boot conversationally looking for all protocols (MOP first)
Boot Bits
---------
0: VXT secondary loader prompt
1: Xdelta
2: Initial breakpoint
3: Used by ROM
8: Bootfile prompt
20: Prompt for LASTport group code
21: reset NVRAM password to VXTNVR
Console commands
----------------
set halt 2 Auto VXTboot
set halt 3 No Auto VXTboot (stop at console prompt after powerfail)
t/util 1 Blow away NVR customizations
On the VXT
----------
In the CUSTOMIZE TCP/IP window, make sure the IP address is set up.
IP address: 16.135.16.70 (for cobra1)
Subnet mask: 255.255.255.0
In the CUSTOMIZE TCP/IP NAME SERVER window, make sure the name server
information is correct.
Primary name server address: 16.135.0.15
Secondary name server address: 16.135.0.19
Determine domain name should be "user specified" as nio.dec.com.
In the CUSTOMIZE TCP/IP ROUTING TABLES, choose dynamic routing and leave
all the boxes blank.
In the CUSTOMIZE FONT PATH window, choose one or all of the following font
paths:
/tftpboot/vxt/fonts/100dpi
/tftpboot/vxt/fonts/75dpi
/tftpboot/vxt/fonts/misc
...or choose them all:
/tftpboot/vxt/fonts/100dpi,/tftpboot/vxt/fonts/75dpi,/tftpboot/vxt/fonts/misc
Various & sundry suggestion for a non-booting VXT
-------------------------------------------------
Make sure you boot the COLOR image for a greyscale terminal. A greyscale
terminal that tries to boot the B&W image will hang.
Make sure xdm is running, i.e. manually run /sbin/init.d/xdm, or put the
following line in /sbin/init.d/xdm so xdm starts on boot:
[ -f /usr/bin/X11/xdm ] && {
/usr/bin/X11/xdm & echo -n ' xdm' >/dev/console
}
Look at /etc/inetd.conf and bootptab. ls /tftpboot/vxt/images and see if the
image pointed to by bootptab is there.
Look at /var/adm/syslog to see if the VXT is trying to boot.
Check if tftp is running in restricted mode while the path in the bootptab
file is the full path.
To force an IP boot, you must boot somehow and modify the terminal manager
for an IP boot. I know of no way to force an IP boot from the console.
Sample files from a good OSF/1 installation
-------------------------------------------
/etc/inetd.conf:
bootps dgram udp wait root /usr/sbin/bootpd bootpd -d
tftp dgram udp wait root /usr/sbin/tftpd tftpd /tftpboot
ls -l /tftpboot/vxt/images
-r--r--r-- 1 root system 4261376 Jul 14 1993 vxt020
-r--r--r-- 1 root system 4261376 Jun 30 1993 vxt020bl19
-r--r--r-- 1 root system 1218560 Jul 14 1993 vxtex020
-r--r--r-- 1 root system 1218560 Jun 30 1993 vxtex020bl19
/etc/services:
ftp 21/tcp
bootps 67/udp
bootpc 68/udp
/etc/bootptab:
vxttec:\
ht=ethernet: ha=08002b296157: ip=16.192.16.162:\
hd=/tftpboot: bf=vxt/images/vxtex020
/var/adm/syslog.dated/26-Jan-09:39/daemon.log:
Jan 26 09:42:33 osftec bootpd[374]: bootpd 2.1a #0: Fri Feb 05 00:32:28
EST 1993
Jan 26 09:42:33 osftec bootpd[374]: reading "/etc/bootptab"
Jan 26 09:42:33 osftec bootpd[374]: read 1 entries from "/etc/bootptab"
Jan 26 09:42:33 osftec bootpd[374]: found: vxttec (08002B296157)
at (16.192.16.162)
Also
----
Read VXT Software on DEC OSF/1 AXP Systems, which contains much of which
you need to do on the host. Notes conference is at ROYALT::VXT, and
pointers to the docs are in that conference.
How to Boot from the GROUP Cluster
----------------------------------
If you modify CUSTOMIZE/BOOT under the Terminal Manager group, and select the
Primary Boot as MOP and select the MOP Boot File as Other and enter VXT020.SYS
in the window, then click on OK, then reboot the terminal, you should be able
to boot from MEMBRx. After that, you should be able to save the Terminal
Manager settings.
|