1752341 Members
5897 Online
108787 Solutions
New Discussion юеВ

Re: UCX license strange

 
Alex Chupahin
Super Advisor

Re: UCX license strange

>In which startup procedure are you starting >TCPIP ? Are the licenses already loaded at >that time ?

I commented any TCPIP$STARTUP lines at the SYS$MANAGER:SYSTARTUP_VMS.COM
and reboot.
No success, the all same:

After "OpenVMS startup begun at ...
FAST FD mode set by console
TCPIP-E-SERVERROR cannot process service request
TCPIP-E-NOCLILIC TCPIP-IP-CLIENT PAK IS NOT ENABLED

Then system boots.

I'm really do not understand whats happened





Does TCPIP SHOW INT show an interface ?

yes
we0 and we1 with proper IP address/mask
received 0 sent 63

Does SHOW DEV E show a LAN interface ?
yes, EWA* all online, errors 0
John Gillings
Honored Contributor

Re: UCX license strange

Alex,

> "OpenVMS startup begun at ...
>FAST FD mode set by console
>TCPIP-E-SERVERROR cannot process service request
>TCPIP-E-NOCLILIC TCPIP-IP-CLIENT PAK IS NOT ENABLED

That looks like it's fairly early in the startup. Are you starting some piece of TCPIP before the license data base is loaded?

Put some trace lines in SYLOGICALS.COM and SYSTARTUP_VMS.COM or use a verbose boot to see the exact sequence.
A crucible of informative mistakes
Alex Chupahin
Super Advisor

Re: UCX license strange

boot with verbose:

FAST FD mode set by console
LOADER-I-INIT initializing SYS$YSDRIVER
LOADER-I-INIT initializing SYS$DVDDRIVER
LOADER-I-INIT initializing SYS$IIDRIVER
TCPIP-E-SERVERROR cannot process service request
TCPIP-E-NOCLILIC TCPIP-IP-CLIENT PAK IS NOT ENABLED


> That looks like it's fairly early in the
>startup. Are you starting some piece of TCPIP
>before the license data base is loaded?

Yes VERY early. Before SYSTARTUP_VMS.COM has been started.
So

>Put some trace lines in SYLOGICALS.COM and
>SYSTARTUP_VMS.COM

is not useful.
Alex Chupahin
Super Advisor

Re: UCX license strange

Nobody can help?
Oswald Knoppers_1
Valued Contributor

Re: UCX license strange

>Yes VERY early. Before SYSTARTUP_VMS.COM has been started.

So why don't you move the tcpip$startup to systartup_vms.com? Apparently the licence info is not yet available at the moment you are starting TCPIP.

Oswald
Volker Halle
Honored Contributor

Re: UCX license strange

Alex,

this is not E8.4 and you're trying to run Cluster-over-IP, is it ?

You must start TCPIP$STARTUP.COM in SYSTARTUP_VMS.COM and not earlier.

Add a SHOW LIC UCX* immediately BEFORE you invoke @SYS$STARTUP:TCPIP$STARTUP.COM

Volker.
John Gillings
Honored Contributor

Re: UCX license strange

Alex,

There are a few startup procedures that run before SYLOGICALS.COM, see SYSMAN for a complete list of procedures:

SYSMAN> STARTUP SET DATABASE STARTUP$STARTUP_VMS
SYSMAN> STARTUP SHOW FILE

Have a look inside them to see what they call out. For example SYCONFIG.COM, SYSECURITY.COM and SYPAGSWPFILES.COM. Perhaps some TCPIP stuff has found its way into one of those procedures?

A crucible of informative mistakes
Shruthi K Prakashan
New Member

Re: UCX license strange

Alex,

You could also add the following command before you invoke TCPIP$STARTUP.COM :

$ license list ucx*/full

The command reads license information from the License database, so you would know if license information is accessible at that instance and if the PAK is enabled/disabled.

-Shruthi
John Gillings
Honored Contributor

Re: UCX license strange

re: Shruthi, >$ license list ucx*/full

I'd say you'd be better off with:

$ SHOW LICENSE UCX*,NET-APP*

or, better, (as already suggested)

$ TCPIP CHECK LICENSE
$ SHOW SYMBOL TCPIP$LICENSE*


LICENSE LIST only tells you what's in the LDB, it says nothing about what will actually happen if you attempt to use the product on the current node. Furthermore, if the error is prior to executing SYLOGICALS.COM, LICENSE LIST may not even look in the correct place, because LMF$LICENSE isn't yet defined. Even then, looking for UCX* doesn't cover all the possibilities of PAKs which enable TCPIP services. See SYS$UPDATE:VMSINSTAL_LMFGROUPS.COM. It's different again for Itanium, which is why TCPIP CHECK LICENSE should be the preferred mechansim.

At issue here is that something, somewhere is attempting to use a UCX PAK before licensing has been started (which LOADs the appropriate PAK).

First objective is to find what and where.

Once you know that, you can decide if the problem is that whatever it is is misplaced (in which case it should be removed and TCPIP$STARTUP moved back to its "normal" place in SYSTARTUP_VMS.COM), or it is necessary, in which case it's possible the warning can be ignored, or HP should update the software to not issue a message (like shadowing a system disk, which happens before a shadowing license can be known).
A crucible of informative mistakes
Alex Chupahin
Super Advisor

Re: UCX license strange

Thank you for all had tried to help me
This is report of the solved problem.

1. I remove TCPIP services
And get undefined command TCPIP call when booting. Good.

2. I tried (thanks to John Gillings) to
find call any TCPIP from the list from
SYSMAN> STARTUP SHOW FILE
but no any call.
VERY INTERESTING.
well, go next.

3. I searched any TCPIP keywords from sys$startup:
and find a one file from samba package.
Interesting, I've removed samba previously.
And samba procedures should starts much later...
I've removed this file
reboot
and get network
:)
still do not understand why samba procedure starts so early, but I'll decide it later then.