Re: [TCPIP V5.4] DHCP client problem/observation
From: Bart Zorn (Bart.Zorn_at_xs4all.nl)
Date: 02/11/04
- Next message: Rob Young: "Re: It is almost certain now, INTEL will have 64bit x86 !!"
- Previous message: Denny Rich: "Re: page- and swap-files, autogen, modparams.dat, file-naming etc"
- In reply to: Matt Muggeridge: "Re: [TCPIP V5.4] DHCP client problem/observation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 11 Feb 2004 06:32:21 -0800
Hi Matt,
While we are at this, can you maybe explain why constructs like:
f$edit("sys$common:[sysmgr]tcpip$dhcp_setupcommands.com","upcase")
are used in almost all TCPIP command files? They seem rather redundant
to me. OpenVMS system managers will NEVER enable case sensitive file
names on system disks.
Regards,
Bart Zorn
"Matt Muggeridge" <Matt.Muggeridge@hp.com> wrote in message news:<P4iWb.51285$Wa.9904@news-server.bigpond.net.au>...
> Thanks Peter,
>
> We'll get that one fixed.
>
> Matt.
>
> --
> -------------------------------------------------------------
> OpenVMS TCP/IP Engineering
> Enterprise Computing Group
> Hewlett-Packard Company
> Gold Coast, AUSTRALIA
> -------------------------------------------------------------
>
>
> "Peter 'EPLAN' LANGSTOEGER" <peter@langstoeger.at> wrote in message
> news:dC2Sb.358959$Tz1.11946@news.chello.at...
> > 1) In SYS$STARTUP:TCPIP$DEFINE_COMMANDS.COM there used to be a command
> sequence
> > like
> >
> > $! DHCP Utilities
> > $!
> > $ if f$search("sys$common:[sysmgr]tcpip$dhcp_setupcommands.com") .nes.
> "" -
> > then @sys$common:[sysmgr]tcpip$dhcp_setupcommands.com
> >
> > which got replaced (probably with ODS-5 in mind) with
> >
> > $ ! dhcp utilities
> > $ !
> > $ dhcp_proc =
> f$edit("sys$common:[sysmgr]tcpip$dhcp_setupcommands.com","upcase")
> > $ if f$search(dhcp_proc)
> > $ then
> > $ @'dhcp_proc'
> > $ endif
> >
> > and this obviously doesn't work.
> > At least there should be a ' .NES. ""' and the end of the 'IF'
> >
> > This has happened at or near V5.3 (ECO2) already. So better check
> yourself.
> > (it seems to depend with which version you first configured your DHCP
> client)
> >
> >
> >
> > 2) If I have a DHCP server (and I currently have) which unfortunately
> doesn't
> > send client hostnames (type 12 "ho and
> "SYS$SYSDEVICE:[TCPIP$DHCP]CLIENT.PCY"
> > contains "request hostname" of course) the DHCP client writes something
> like
> >
> > The DHCP server did not pass a host name for this host to use
> > Using the requested hostname <hostname> instead
> >
> > and there it goes and all works. It seems that this happens only if there
> > is a file "SYS$SYSDEVICE:[TCPIP$DHCP]HOSTNAME." but not the file
> > "SYS$SYSDEVICE:[TCPIP$DHCP]interface.DHC" - as it is with the first boot.
> >
> > With the second boot, the "SYS$SYSDEVICE:[TCPIP$DHCP]interface.DHC" exists
> > and doesn't contain a hostname (because the DHCP server didn't send it and
> > nobody else did it add), and then, the msg "Using the requested..." no
> longer
> > appears and the client names itself "unknown" (till I delete *.DHC and
> reboot).
> >
> > Can anyone confirm this behaviour (I see it as a bug in DHCP client,
> triggered
> > by a bug in the DHCP server) in TCPIP V5.4 (and in V5.3, at least in ECO2)
> > and maybe even make a formal support call ?
> >
> > Many TIA
> >
> > --
> > Peter "EPLAN" LANGSTOEGER
> > Network and OpenVMS system specialist
> > E-mail peter@langstoeger.at
> > A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
- Next message: Rob Young: "Re: It is almost certain now, INTEL will have 64bit x86 !!"
- Previous message: Denny Rich: "Re: page- and swap-files, autogen, modparams.dat, file-naming etc"
- In reply to: Matt Muggeridge: "Re: [TCPIP V5.4] DHCP client problem/observation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
