Operating System - OpenVMS
1827885 Members
1517 Online
109969 Solutions
New Discussion

Re: TCPIP Pause At Startup

 
SOLVED
Go to solution
Wim Van den Wyngaert
Honored Contributor

Re: TCPIP Pause At Startup

You can disable smtp and enable it later in the startup but via a submit.

But I'm not going to prevent the hang : I'm not in a hurry to get my node up without network.

Wim
Wim
Dean McGorrill
Valued Contributor

Re: TCPIP Pause At Startup

Wim,
tcpip, like decnet, were pretty good about having dials either through commands or logicals to change stuff like timers. esp one of 10 minutes. I'd be surprized if
there isn't one. if theres someone inside
hp in here, they could ask in the tcpip notes conference (or its equiv) or look
in the tcpip sources.

Dean
Robert Atkinson
Respected Contributor

Re: TCPIP Pause At Startup

Not to say one doesn't exist, but I had a good hunt around at the time and couldn't find it.

By the way, if you want to see if you can reduce the timeout, simply issuing a '$ NSLOOKUP' command will have exactly the same effect as the boot hang, taking a number of minutes to realise the DNS server isn't responding.

We have 3 DNS servers configured, which is probably why our timeout takes 10 minutes.

Rob.
labadie_1
Honored Contributor

Re: TCPIP Pause At Startup

I have done
$ @sys$startup:tcpip$define_commands
$ sysconfig -q inet
$ sysconfig -q socket
$ sysconfig -q net

and I have not found a parameter with a value of 600 or 6000 (if the unit is 1/10 second)

of course this proves nothing, as the unit for this timeout may be any value.

May be it is hard coded and it would need to patch some cell before and after the start of Tcpip (or copy before and after 2 versions of the .exe holding the timeout value).

Wim Van den Wyngaert
Honored Contributor

Re: TCPIP Pause At Startup

set config nam/retry=1/timeout=1
(were both 4, for 2 name servers in /serv)

Startup time of ucx went from 4min27sec to 19 sec. Normal startup takes 12 sec (very old slow as500). So 1 retry takes 8 sec for 2 nodes.

Retry=2 took 27 sec.
retry=3 took 43 sec.
retry=0 took 1min15sec ???

So 4 seconds per retry per node.

The arp timeout is about 4 sec. So it's arp that's to blame. Note that I traced IP in the beginning : this was a fault. Always start with tracing ARP.

And I think ARP timeout is hardcoded in tcpip.

Wim
Wim
Dean McGorrill
Valued Contributor

Re: TCPIP Pause At Startup

Wim,
thats a nice reduction of time.
I thought there'd be a dial. I always
seem to have trouble in general with
tcpip commands (not that ncl is obvious!)

Dean
Jack Trachtman
Super Advisor

Re: TCPIP Pause At Startup

Looks like my original post has regained life!

Re my original post: the hang occurred on test systems that we had physically disconnected from our network.

Resolution: we enabled the Bind/DNS service on the test node so whatever other service was waiting for a response (SMTP, ?) was satisfied.
Jack Trachtman
Super Advisor

Re: TCPIP Pause At Startup

Thanks all