You might want to consider putting the old name back into effect, at least
from the
point of view of that box. For instance, you can use that name first in
/etc/hosts, and
have hosts override dns (/etc/netsvc.conf containing 'hosts=local,bind').
The rest of
the world can use the new name first, for all you care. (Her name was
McGill, but she
called herself Lill..) That's assuming this is a standalone TMR server, and
not a
Managed Node in a larger Tivoli environment.
You have Netview happy now with the new name, and you could do a few
things
documented in the back of the V6 release notes that will make the Framework
look
like it is happy, but you will probably not be able to do things down the
road such
as install patches and products successfully. The right people to tell you
how to
thoroughly change the name of a Tivoli Managed Node and TMR Server are in
Tivoli Support, the Framework group. I've tried this a few times, and if I
were in
your situation, I would either go back, or reinstall using the migration
instructions.
You don't have to do it now, but you will probably have to do it
eventually.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit.
James_Shanks@TIVOLI.COM@tkg.com on 08/08/2000 11:31:22 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: Re: [NV-L] my NV 6.0 dislikes the webserver - reset_ci fixed the
problem
Offhand, I cannot say if this is a problem or not. The error actually
comes
not from snmpCollect but from code that was added to check your Tivoli
Framework
oserv. If you can start the Tivoli desktop after sourcing the Tivoli
environment, (run
" . /etc/Tivoli/setup_env.sh " and then type " tivoli ") then there
is
nothing to worry about. If you can't then you will have to pursue fixing
that. That is harder to do. The Framework books have big discussion on
this.
If you cannot start the desktop, then I would see if oserv is running, ( "
ps
-ef | grep oserv " ) and if not try starting it (again you must have the
Tivoli
environment sourced first) and then try " oserv -k $DBDIR -N ali ". If it
is
still running you must stop it before you try to restart it, by issuing "
odadmin shutdown all ". If that doesn't work, you may have to kill the
oserv
process. If you cannot restart it, then I recommend you call Support. The
Framework is not simple to get going again once it has been messed up.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
"Werner Nixdorf" <werner.nixdorf@datev.de> on 08/08/2000 11:04:52 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "IBM NetView Discussion" <nv-l@tkg.com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: [NV-L] my NV 6.0 dislikes the webserver - reset_ci fixed the
problem
Hi,
thanks for your help, the reset_ci solved my problem. It was a changed
IP-name -
during the installation I was running az etc/hosts and afterwards I changed
to
the dns with a different IP-name (the old name as alias already).
There is one little question left. When running reset_ci, everything seems
to
look fine until
Restarting netmon...
Restarting snmpCollect...
query: o_errs:0022 insufficient autihorisation
{ SYSTEM_EXCEPTION StExcep::NO_PERMISSION { 42 NO }}
reset_ci finished
I know I have some problems with my snmp-collector, trying to check systems
behind firewalls, but I'm on my way to fix them. My question is: Is this
something to worry about?
thanks
kannix
(See attached file: att1.htm)
Hi,
thanks for your help, the reset_ci solved my
problem. It was a changed IP-name - during the installation I was running az
etc/hosts and afterwards I changed to the dns with a different IP-name (the old
name as alias already).
There is one little question left. When running
reset_ci, everything seems to look fine until
Restarting netmon...
Restarting snmpCollect...
query: o_errs:0022 insufficient
autihorisation
{ SYSTEM_EXCEPTION StExcep::NO_PERMISSION { 42 NO
}}
reset_ci finished
I know I have some problems with my snmp-collector,
trying to check systems behind firewalls, but I'm on my way to fix them. My
question is: Is this something to worry about?
thanks
kannix
|
|