Very Computer

by **Paul Wefe** » Mon, 24 Feb 1997 04:00:00

Here is a strange problem I encountered the other day. We have a Sparc
10 Model 40 which is used as a network management station. I recently
had to do a fresh re-install of everything (long story).
I installed Solaris 2.5 and the Recommended 2.5 patch cluster. After
verifying that everything was working ok I installed Sunnet Manager
2.2.3. The install went fine with no errors. However, after setting up
an account to run SNM (adding the path environment) and actually trying
to execute it I get a number of errors all relating to the fact that SNM
can't resolve variables it has placed in inetd.conf, snm.conf, etc..

It is almost like there is a section of the install that didn't
complete. I have racked my brain for a solution and have come up
blank. Back when I originally installed SNM everything went fine and it
worked OK. The only difference I can see is that now I have applied the
patch cluster before SNM. I also added another disk to the system but
I doubt that is causing the problems.

Anyone experience anything like this before?

Thanks,

Paul Wefel

by **Konstantinos Agour** » Tue, 25 Feb 1997 04:00:00

>Here is a strange problem I encountered the other day. We have a Sparc
>10 Model 40 which is used as a network management station. I recently
>had to do a fresh re-install of everything (long story).
>I installed Solaris 2.5 and the Recommended 2.5 patch cluster. After
>verifying that everything was working ok I installed Sunnet Manager
>2.2.3. The install went fine with no errors. However, after setting up
>an account to run SNM (adding the path environment) and actually trying
>to execute it I get a number of errors all relating to the fact that SNM
>can't resolve variables it has placed in inetd.conf, snm.conf, etc..

Yes I experienced this. You will find stuff like AGENTDIR or SNMDIR in these
files. Is it possible that you used csh as root to install it or just su'ed
instead of logging in as root. I think the install-script has en error in it
that needs root running /bin/sh with a clean environment to work. You can fix
it by substituting the stuff in capital letter with the actual paths you want
to use. If you have a standard installation AGENTDIR should be /opt/SUNWconn/
snm/agents, SNMDIR should be the same without agents at the end and
you should have something like DATADIR (I don't remember at the moment, how
it is called exactly) that should be pointing to /var/opt/SUNWconn/snm or
whereever you want to keep your datafiles. For the correct paths, names and
the files in which you have to exchange them, send me an email.

Hope that helps,

Konstantin

--

Otkerstr. 28, 81547 Muenchen, Germany. Tel +49 89 69370185
----------------------------------------------------------------------------
"Captain, this ship will not sustain the forming of the cosmos." Belana Torres

Very Computer

Solaris 2.5 and Sunnet Manager 2.2.3 Install problems - Advice wanted

Solaris 2.5 and Sunnet Manager 2.2.3 Install problems - Advice wanted

Solaris 2.5 and Sunnet Manager 2.2.3 Install problems - Advice wanted