PWIP Driver (for DECnet-Plus and PATHWORKS) fails to start

[Petr X]

Hello,
I've installed on our enviroment a TCPIP patch kit v5.4 ECO6 (OVMS ver. 7.3-2). Installation went smooth till I discovered I'm no longer able to get connected via "set host" command. After short investigation I found this issue:

type $1$DGA100:[SYS0.SYSMGR]TCPIP$PWIPACP_SMFT71.LOG

Tue Mar 10 10:50:27 2009: getLocalAddr : getaddrinfo failure: 2

Tue Mar 10 10:50:27 2009: interfaceInit : Could not getLocalAddr!

Tue Mar 10 10:50:27 2009: main : PWIPdriver, PWIPacp interface init failure, aborting PWIP ACP startup...


I've been searching for a solution and found that resolver should be configured, but this is not a option in this case. I need to find a workaround solution for that case.

[Steven Schweda]

I know nothing, but "Could not getLocalAddr!"
sounds to me like a name-to-address look-up
problem, so I'd look at the local HOSTS data
base and/or DNS to see what's there for this
system. (I wouldn't expect a TCPIP ECO to
change anything important in this
neighborhood, but what do I know?)

> [...] TCPIP patch kit v5.4 ECO6 [...]

Why 6? Around here:

alp $ tcpip show version

HP TCP/IP Services for OpenVMS Alpha Version V5.4 - ECO 7
on a COMPAQ Professional Workstation XP1000 running OpenVMS V7.3-2

[Petr X]

Hi Steven,
Thanks a lot for your response.
Regarding my case, I've been looking to some configs and I found this:

1) I execute "MC NCL" and than
NCL>SHOW ALL

....
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV2 , number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
...
[ DNA_IP , 0.0.0.0 ] <-- THIS IS STRANGE
....

The line I've marked with the arrow is different on other systems like in this example:

....
[ DNA_CMIP-MICE ] ,
[ DNA_SessionControlV2 , number = 19 ] ,
[ DNA_OSItransportV1 , 'DEC0'H ] ,
[ DNA_IP , 10.162.210.66 (XXXXXX) ]
....

Which points me to question why is not an IP assigned here for the first case???

Cheers
Petr

[Steven Schweda]

> [...] <-- THIS IS STRANGE

Perhaps for you. Mine looks like that, too.
(But I don't use DECnet-over-IP, or PW, or,
...)

If I were looking for IP info, NCL is not
where I'd go. What does "TCPIP SHOW HOSTS"
say? "TCPIP SHOW INTERFACE"?


> [ DNA_IP , 10.162.210.66 (XXXXXX) ]

If you hide enough details (like "XXXXXX"),
you can make it impossible to puzzle out
what's actually happening. With an address
like 10.x.x.x, how much secrecy do you
believe that you need?

For a good time, I just ran
SYS$MANAGER:TCPIP$CONFIG.COM, and asked it to
"Configure PWIP Driver" (Start and enable).
_Now_, I get this from NCL:
[ DNA_IP , 209.98.249.184 ]
instead of this:
[ DNA_IP , 0.0.0.0 ]
which I was getting. Perhaps you should give
that a try.

[Petr X]

Yes, I did the "@SYS$MANAGER:TCPIP$CONFIG.COM" procedure already before, still the result is presented in this output:

FT71:SYSTEM> ty $1$DGA100:[SYS0.SYSMGR]TCPIP$PWIPACP_SMFT71.LOG
Wed Mar 11 17:20:15 2009: getLocalAddr : getaddrinfo failure: 2
Wed Mar 11 17:20:15 2009: interfaceInit : Could not getLocalAddr!
Wed Mar 11 17:20:15 2009: main : PWIPdriver, PWIPacp interface init failure, aborting PWIP ACP startup...
FT71:SYSTEM>

so we are back to square one :(


Regarding your point "info about IP" I've not been looking for IP in general, but more likely I tried to point out to a strange behaviour regarding first and second case.

[Bill Hall]

Petr,

I would run TCPIP$CONFIG and review or even reconfigure all of the core environment configurations. This may just fix the issue.

I think I agree with Steve, that this is probably a local host file "corruption". Running through the core environment configuration may fix the problem. Then again, you might have to manually set nohost and completely reconfigure this host.

The NCL output is just a red herring, you won't see the correct tcpip address in the DNA_IP tower until you have successful incoming or outgoing DECnet over IP traffic. You can't get any traffic if the PWIP driver doesn't start.

Bill

[Steven Schweda]

> so we are back to square one :(

We might get to square two if we could see
your TCPIP SHOW reports.

> [...] I did the
> "@SYS$MANAGER:TCPIP$CONFIG.COM" procedure
> [...]

And you think that that says enough about
what you did to be useful?

[Volker Halle]

Petr,

what does UCX SHOW HOST SMFT71 report ? It must be a DNS entry in the local host database. Is it ?

Does the IP address match UCX SHOW INT (any of the IP adresses reported) ?

Volker.

[Petr X]

Hi All, thanks a lot for your responses, I appreciate them a lot.

uxc sh ho shows:
...
10.163.201.65 SMFT71, SMFT71_O
...

FT71:SYSTEM> UCX SHOW INT
Packets
Interface IP_Addr Network mask Receive Send MTU

IE0 10.0.1.1 255.255.255.0 0 1 1500
IE2 10.15.15.1 255.255.255.224 1137 59 1500
IE6 10.15.15.33 255.255.255.224 1134 23 1500
LE0 10.163.201.65 255.255.255.192 111818 67 1500
LE1 10.163.201.129 255.255.255.128 2268628 3615614 1500
LO0 127.0.0.1 255.0.0.0 1433218 1433218 4096
WE0 10.0.0.1 255.255.255.0 0 1 1500

There is no DNS service running within the network.

[Robert Atkinson]

Could you try '$ NSLOOKUP SMFT71' ?

Rob.