AS/U installation

[Frédéric Devos]

AS/U cannot start after the installation!

Test System details:
L1000,1CPU,512MbRAM
HP-UX 03/2001,QualityPack 03/2001,HW critical patch 03/2001

What I do?
1) Install x25 software
2) Install OTS
3) Install ASU 04.06 --> The problems begin
After the reboot, the "INITIALISE LOADABLE MODULE" give an error :
"WARNING: Out of character major numbers
Couldn't install driver krm
gio_mod_drv_reg: gio_allocate_majors failed
FAIL *"
In /stand/dlkm/mod_register, you read "krm:5:pseudo,25,-1,-1" If I remove this line, there is no boot problems anymore.

Do someone have an Idea of what is wrong?

After that, when I try to start initialize asu (asu_inst), I receive the following message :
"RROR: The Advanced Server for UNIX Systems cannot be started.
Verify the transport is configured correctly and is running."
I then check /etc/opt/lmu/netbios/nbconfig but the datas seem to be correct.

What can I try now?

Thanks

[Rainer von Bongartz]

lots of possibilities for that....

AS/U relies on netbios daemon and netbios on STREAMS.

First check if STREAMS is functional; then check for
netbiosdaemon /opt/lmu/netbios/bin/netdemon

[LB4]

i use CIFS/9000 instead of ASU.
You can download it from software.hp.com
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProducts.pl?group_type=category&group_name=NSM

It's free and it works very well.

[Frédéric Devos]

Thanks for helping me !!!

How can I check if STREAMS is functional?
For Netbios, it starts normally. You can find the the netdemon after starting it.

I have seen something else :
On an operational server, "lsdev | egrep -i 'netbios|netbiosdg|lmxloop'" gives 3 devices.

On the test server, only the 2 following devices netbios|netbiosdg

-----------------------------------------------
For the CIFS product, I know that the very last version can play Domain Controller. We will test it in the next weeks
Thanks
-----------------------------------------------

[Rainer von Bongartz]

STREAMS is initialized at boot up, so look for STREAMS related messages in syslog.log.

You really should have /dev/lmxloop device. If you dont't
have this, look if the lmxloop driver is included in the kernel (use sam).