[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | DEC TCP/IP Services for OpenVMS |
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
|
| Created: | Thu Nov 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5568 |
| Total number of notes: | 21492 |
5169.0. "BOOTP, UCX 4.1 issues" by CSC32::R_WILLIAMS () Tue Jan 28 1997 16:23
Hi,
I have a customer with a list of concerns/issues with UCX and BOOTP.
This customer is currently evaluating our product and has some valid
concerns. Can anybody help address these concerns?
Thanks,
-Rick
+++++++
I am installing "DEC TCP/IP Services for OPENVMS" (UCX) on a VAX
4300. My environment will (hopefully) include a VAX 4300, a
MicroVAX 3190, two Alpha 2100's, numerous Emulex Print and
Terminal servers, about 10 or 15 NetWare v4.11 fileservers, and
several hundred PCS.
Currently, I am using the VAX 4300, one NetWare v4.1 fileserver,
one Emulex Terminal Server, one Emulex Print Server, and one PC
to demonstrate the feasibility of this installation.
I have installed UCX v4.1, and applied a patch "UCXVAX_E3041". I
have the following questions/suggestions that I hope Digital can
address:
1) I would like to use BootP to assign host (and domain) names,
IP addresses, and default name server addresses. I do not need
to download any software to (most of) my devices. After applying
the "UCXVAX_E3041" patch, I find that the following syntax is
valid:
$ UCX SET BOOTP 191.254.1.145 /HARDWARE=ADDRESS=00-A0-24-12-BE-97
The documentation and help screens claim that /FILE is required,
however I did not (nor do I want to) specify a file. I have not,
however, found any way to specify /NOFILE in the event that a
file has been specified and I want to remove that file
specification. Is there any way, other than removing and
recreating the record, that I can remove the file specification?
2) I already have a list of all of my devices, and their
hardware addresses (in Excel), from which I can create text files
in almost any format. I would like to be able to create a
ETC.BOOTPTAB file, and use UCX CONVERT /VMS BOOTP to populate
UCX's BootP database. I found some documentation on the format
of UNIX's ETC.BOOTPTAB file on the Internet, but UCX does not
seem to understand all of the parameters specified in this
format. Is there any documentation on the format UCX is
expecting for the UCX CONVERT/VMS BOOTP command? Also, since the
format of all of the files used by UNIX seems to not be very
standard, I think it would be very helpful to include a detailed
description of UCX's expectations of all of the text files it
uses (ETC.HOSTS, ETC.BOOTPTAB, domain_name.DB).
I have managed to get some information into UCX with CONVERT/VMS
BOOTP, but I have not found any way to get records added without
a file specification. I have tried ":bf:", ":bf=:", ":bf@:",
":bf=@:", ":hd:", ":hd:=", ":hd:@", and ":hd:=@", none of which
yield the "File: not defined" that I get when I use UCX SET BOOTP
without a /FILE qualifier.
3) Is there any way, other than manually editing the
domain_name.DB files, to specify the address of other BIND/DNS
servers? My VAX 4300 is currently configured as the primary name
server for the domain "Clayton.com", and I need to specify that
another device (191.254.1.230) is the primary name server for the
domain "Corp.Clayton.com".
For your information, I am including the output from "$ ucx show
version /all"
Digital TCP/IP Services for OpenVMS VAX Version V4.1 - ECO Level 3
on a VAX 4000-300 running OpenVMS V6.2
Image name Image ID Link Date Image location
CORE environment:
UCX$ACCESS_SHR;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSLIB]
UCX$BGDRIVER;2 UCX V4.1-12P 27-NOV-1996 SYS$COMMON:[SYS$LDR]
UCX$INETACP;2 UCX V4.1-12P 27-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$INETDRIVER;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYS$LDR]
UCX$INET_ROUTING;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$INTERNET_SERVICES_V6;2 UCX V4.1-12P 27-NOV-1996 SYS$COMMON:[SYS$LDR]
UCX$IPC_SHR;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSLIB]
UCX$MSG;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSMSG]
UCX$PING;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$SDA;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSLIB]
UCX$TRACE;2 UCX V4.1-12G 26-SEP-1996 SYS$COMMON:[SYSEXE]
UCX$UCP;2 UCX V4.1-12A 20-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$VERSIONS;2 UCX V4.1-12 5-DEC-1996 SYS$COMMON:[SYSEXE]
BIND:
UCX$BIND_SERVER;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$BIND_SERVER_XFER;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$BIND_VALIDATE_SETUP;1 UCX V4.1-12 18-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$METRIC;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$METRICVIEW;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$NSLOOKUP;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
MAIL:
UCX$POP_SERVER;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$SMTP_MAILSHR;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSLIB]
UCX$SMTP_PARSESHR;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSLIB]
UCX$SMTP_RECEIVER;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$SMTP_SYMBIONT;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$UUDECODE;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$UUENCODE;2 UCX V4.1-12A 27-NOV-1996 SYS$COMMON:[SYSEXE]
Network File System:
UCX$CFS_SHR;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSLIB]
UCX$DNFSACP_V6;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$DNFSDISMOUNT_V6;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$DNFSDRIVER_V6;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYS$LDR]
UCX$DNFSMOUNT_V6;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$PCNFSD;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$SERVER_NFS;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
Network Management:
UCX$ESNMP_SERVER;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$ESNMP_SHR;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSLIB]
UCX$MIBCOMP;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$MOSY;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$OS_MIBS;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$SNMPI;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$SNMP_REQUEST;1 UCX V4.1-12 23-JUL-1996 SYS$COMMON:[SYSEXE]
Printing Services:
UCX$TELNETSYM;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$LPD_RCV;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$LPD_SHR;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSLIB]
UCX$LPD_SMB;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$LPQ;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$LPRM;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
UCX$LPRSETUP;2 UCX V4.1-12C 25-NOV-1996 SYS$COMMON:[SYSEXE]
PWIP:
PWIP$SDA;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSLIB]
UCX$PWIPACP;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$PWIPDRIVER;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYS$LDR]
UCX$PWIPSHUT;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
Remote Procedure Call:
UCX$PORTMAPPER;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RPCGEN;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RPCINFO;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RPCXDR_SHR;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSLIB]
Services:
UCX$BOOTP;2 UCX V4.1-12A 23-OCT-1996 SYS$COMMON:[SYSEXE]
UCX$FINGER;2 UCX V4.1-12B 18-SEP-1996 SYS$COMMON:[SYSEXE]
UCX$FINGER_SERVER;2 UCX V4.1-12B 18-SEP-1996 SYS$COMMON:[SYSEXE]
UCX$FTP;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$FTPC;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$FTPD;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$NTPD;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RCP;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RLOGIN;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$RSH;1 UCX V4.1-12 16-JUL-1996 SYS$COMMON:[SYSEXE]
UCX$TFTP;2 UCX V4.1-12A 23-OCT-1996 SYS$COMMON:[SYSEXE]
TELNET:
UCX$TELNET;2 UCX V4.1-12C 4-DEC-1996 SYS$COMMON:[SYSEXE]
UCX$TNDRIVER;2 UCX V4.1-12D 5-DEC-1996 SYS$COMMON:[SYS$LDR]
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5169.1 | | UCXAXP::GRADY | Squash that bug! (tm) | Thu Jan 30 1997 14:49 | 15 |
| 1.) and 2.) are actuall UCP issues - it's the UCP that places such
restrictions on the database entries and the bootptab conversion.
The requirement to supply a file name was incorrect and recently
changed in the UCP command interface - hence the change you noted.
I know that the 'tag' items in bootptab aren't supported - those are
bootp user-defined tags for transferring arbitrary data to the client.
I'm not sure of the details of the Unix-ish entries in bootptab -
again, these are UCP questions. It may be that the filename
requirement remains enforced in the CONVERT command - which would be a
low-priority, albeit somewhat troublesome bug.
tim
|