Weiya,
this is our suggestion. Start the install over again. We got the de install
and reinstall instructions from the Tivoli team. If u follow the
instructions to the - t - u will have a successful install. But mind u
there is a lot of pain involved......
Instructions::::::: THIS IS ON A AIX SYSTEM:: I am not sure about
installing on a SUN system..
The Deinstallation Notes for Framework is FYI. You generally do not have
to deinstall Framework when deinstalling NetView.
=======================================================================
Deinstalling NetView 5.0 and 5.1:
----------------------------------------------------------------------
PROCEDURE TO DE-INSTALL NETVIEW VERSION 5
----------------------------------------------------------------------
1) If the NetView GUI is up, take it down.
2) Stop the netview daemons
ovstop
ovstop nvsecd
ovstop OVsPMD
3A) If the NetView icon (the one with 3 balloons) EXISTS
in the policy region, use instructions on pages 2-13
and 2-14 of the NetView Install Guide to deinstall the
product. This will remove odm entries for NetView,
and /etc/services entries.
3B) If the NetView icon (the one with 3 balloons) DOES NOT EXIST
in the policy region, do the following:
- Source the Tivoli environment. Run your version of
/etc/Tivoli/setup_env.sh script
- To deinstall NetView run
/usr/OV/bin/nv6000_smit zap_proc 'leave deps'
(if there are dependency products installed)
or
/usr/OV/bin/nv6000_smit zap_proc
or
/usr/OV/bin/nv6000_smit deinstallclient
(to deinstall the client)
If /usr/OV/bin does not exist, run
/usr/lpp/nv6000/NV_deinstall
4) After deinstalling, ensure that the /usr/OV directory
does not exist. To remove it:
rm -rf /usr/OV/*
rmdir /usr/OV
5) After deinstalling, ensure that the odm entries do not remain:
'lslpp -L nv6000.*.*' should show NetView is not installed
6) If the NetView icon remains, select the icon, and then
use the menubar option Edit->Delete to remove it.
7) Remove /tmp/.NV* files, if they exist
8) Remove the following files which indicate either the
NetView server of client are installed.
rm $DBDIR/.installed/NVS_50_ALIDB
rm $DBDIR/.installed/NVC_*
rm $BINDIR/.installed/NVS_50_BIN
rm $BINDIR/.installed/NVS_50_NVFBIN
rm $BINDIR/.installed/NVC_*
rm /usr/lib/objrepos/* (for Solaris only)
9) If you backed up your Tivoli Databases before installing
the NetView-Specific Framework patch, (step 5, page 2-3,
NetView Installation Guide)
Issue
wbkupdb -r -d /var/spool/Tivoli/backups/<dbname> <netview_hostname>
NOTE
After restoring the Tivoli databases, you can proceed to try
to re-install the framework specific patch for NetView,
followed by creating the managed node, and then installing
NetView from the managed node,
or proceed to de-install Framework.
NOTE
The Framework databases contain knowledge that the patch was
installed.
Prior to re-installing NetView, you do not have to restore them
to the backup that was taken before the NetView-specific
framework patch was installed. In that case, you will just
want to start the reinstall of NetView by creating the NetView
server managed node.
**Note: If you have the 5.1 media, use the cleanup script found under
MUSTSEE to make sure you have deinstalled everything you needed to.
HOW TO DEINSTALL THE TME10 FRAMEWORK
-------------------------------------
NOTE: If NetView V5 is still installed, de-install it before
starting the framework de-install.
NOTE: If the Framework must be re-installed, and if the machine
is AIX operating system, you may want to take a system backup
(mksysb) after the Framework has been installed, but before
installing NetView.
1. If you have installed any managed nodes, use the
$BINDIR/bin/wrmnode command to remove them. Please
see the appropriate documentation for more information.
$BINDIR/bin/wrmnode <managed_node_hostname>
2. Ensure that the oserv is stopped on the TMR Server.
odadmin shutdown all
3. Execute the following commands on all machines where you have
installed TME:
rm -rf /usr/local/Tivoli/* (or where you have installed)
rm -rf /var/spool/Tivoli/* (or where you have installed)
rm -rf /etc/Tivoli/*
rmdir /etc/Tivoli
4. Remove the objcall entries from your /etc/services file. They
should look like the following:
objcall 94/tcp # Tivoli daemon
objcall 94/udp # Tivoli daemon
5. Remove the following entry from your /etc/inetd.conf file:
objcall dgram udp wait root /etc/Tivoli/oserv/rc
/etc/Tivoli/oserv.rc
---------------------------------------------------
HINTS FOR A SUCCESSFUL NETVIEW V5.1 INSTALLATION
----------------------------------------------------
NOTES on FRAMEWORK INSTALL:
If you have not installed the Framework, the
Framework documentation can be found in:
Framework 3.2 Planning and Installation Guide,
Chapter 5, Section: Installing a TMR Server Unix, Page 5-20
or
Framework 3.6 Planning and Installation Guide,
Chapter 6, Section: Installing a TMR Server Unix, Page 6-20
- On the last page of this chapter, follow the instructions
to update the .profile file of users who bring up NetView.
This will automatically set/source the Tivoli environment,
which NetView is dependent on.
- Framework Installation information can also be found
in the NetView V5.1 Release Notes, pages 20-21
----------------------------------------------------
WARNINGS: Do NOT attempt to install the NetView client on the
same machine as the NetView server. They were meant
to run on unique machines.
-----------------------------------------------------
1) To de-install NetView, and migrate data from that level of
NetView to the latest level,
See NetView V5.1 Release Notes, pages 17-20.
Step '3' of the Release Notes De-Installation information
refers to de-installing the smconfig part of the old
Systems Monitor product. This is ESSENTIAL.
Step '7' of the Release Notes De-Installation information
refers to saving data for migration by running scripts.
Another alternative to save the data is to use the smit
panels, See Installation & Configuration Guide, page 2-13
for info.
2) Verify Software prereqs-
See NetView V5 Install Guide, Pages 1-6 through 1-8
3) Issue the 'echo $LANG' to see the language setting.
LANG setting varies by operating system. Check NetView V5
Install Guide, page 1-15 to get the proper LANG variable
setting for your operating system.
4) Setting the locale - AIX only
Setting the locale (cultural convention) on the machine
involves 2 steps, installing the locale (if necessary)
and setting it as the primary locale on the machine.
4a) Verify whether the En_US locale is installed.
Issue 'locale -a'. You should have results similar to the
following:
# locale -a
C
POSIX
en_US
en_US.ISO8859-1
En_US
En_US.IBM-850
If you do not have En_US installed, install it from the
AIX install media (probably the 2nd CD of the set)
as follows:
To add the locale:
SMIT -> System Environments
-> Manage Language Environments
-> Add Additional Language Environments
Back out of smit, when finished
Issue 'locale -a again to verify that the locale has been
installed.
4b) Set the primary locale for the machine.
Issue the 'locale' command to see the locale settings.
Locale settings must all be 'En_US'.
To set the primary locale:
SMIT -> System Environments
-> Manage Language Environments
-> Change/Show Primary Language Environments
-> Change/Show Cultural Convention, Language, Keyboard
Set the values for Primary Language tranlation to
En_US
Set the values for Primary Cultural convention to
En_US
Back out of smit, when finished
Issue the 'locale' command to see the language and locale
again. If they are not set, and you think the smit change was
good, then set them manually. They are environment variables.
To change them, issued the following commands:
export LANG=En_US
export LC_ALL=En_US
locale -a (to ensure that the locale is installed)
locale (to ensure that the env vars are
correct)
5) Check your memory and paging space and disk space.
Guidelines are on the following pages in the NetView V5
Install & Config Guide.
Memory 1-2
Disk Space 1-3
Paging 1-3
Additional information is in Appendix A (Memory and Paging Space
Considerations) in the same book if you want to pursue
this further.
6) If you are running the TME 10 Event Console (T/EC) in your
Tivoli Managed Region, you may have installed tecad_snmp. You
must stop the tecad_snmp daemon on the Managed Node that will
become your NetView Server to free the SNMP Trap port, 162,
before the NetView installation can run correctly. In order
to prevent the tecad_snmp daemon from restarting on the next
reboot,
BO=`objcall 0.0.0 self`
OSERV=`objcall $BO getattr oserv`
objcall $OSERV boot_method list -(this shows that
it is set to
start)
objcall $OSERV boot_method delete <xyz>
(where xyz is the name for tecad_snmp from the list
displayed by the first objcall command)
7) It is VITAL that you follow the install directions CAREFULLY
since some of the steps are not intuitive.
For installation instructions,
See page 21, NetView 5.1 Release Notes.
Step '2' of the Release Notes Install Information refers to
the Installation of the NetView-specific Framework patches.
Additional information about the patches and the 3.2
Super Patch, can be found on pages 26-27 of the release notes.
(Framework 3.6 includes the 3.2 Super Patch)
The NetView icon with the 3 balloons will pop up on the
policy region about 1/3 way through the install.
8) To reduce problems with ipmap, add the ulimit entries to your
/etc/rc.nfs file. See Release Notes, Page 9 for specifics.
This is for AIX only
For additional System Configuration, and System Environment
information listed for ALL operating system, see the
Release Notes, Table of Contents, Chapter 3 information.
9) Installing the DATABASES part. (optional)
This will allow communication between NetView and a relational
database.
If you intend to install the databases part of NetView,
you should install the NetView product first.
To install the databases:
Go the policy region
Select the NetView server icon (the one with the 3 balloons)
Use menubar option Create -> NetView Server
Set the media to point to the NetView CD
From the 'Select Product to Install' list,
select the TME10 NetView Database, then install
See page 23,(step 6) NetView 5.1 Release Notes.
10) Installing the SOFTCOPY BOOKS and DYNATEXT BROWSER (optional)
If you intend to install the softcopy books for NetView,
you should install the Dynatext Browser first, then the books.
On the Tivoli desktop, go the policy region
Select the NetView server icon (the one with the 3 balloons)
Use menubar option Create -> TME10 NetView Server
Set the media to point to the NetView CD
From the 'Select Product to Install' list,
select the Dynatext Online Browser, then install
See page 23-24 (steps 7-8) NetView 5.1 Release Notes.
Repeat the same to install the NetView Books.
11) Installing the MLM (Mid Level Manager) (optional)
The MLM is NOT installed from the Policy Region or from
the Desktop->Install menubar option.
Both the CFG (configuration) part and the MLM (mid level
manager) part are installed from SMIT. See Chapter 3,
Mid-Level Manager User's Guide shipped with NetView. The
software to be installed is on the NetView CD.
Chapter 3 covers how to install on various operating systems.
See page 24 (step 9) NetView 5.1 Release Notes.
Ziyad Choudhury
B 010 / 2D-03
522 South Rd.
Poughkeepsie, NY 12601
IBM Global Services
Certified Netware Engineer
E-Mail:: ZIYAD@US.IBM.COM
Phone: ( 914) -433-1124
Pager: 1-800-759-8352 Pin 1772452
http://www.Skytel.com/Paging/pageme.cgi?pin=1772452,2
Weiya Cai <weiya_cai@compuware.com> on 03/17/99 11:48:05 PM
Please respond to Weiya Cai <weiya_cai@compuware.com>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Ziyad A Choudhury/Southbury/IBM)
Subject: Re: ovstart fails to find /usr/OV/conf/ovsuf
Greg,
Did you get it work, what is the fix? I had the same problem on AIX
installation
and double checked the UDP/TCP ports usage. However, I couldn't
make it work. I am going to install NV 5.1 on solaris tomorrow.
Thanks.
Weiya
> Hop-Count: 1
> Date: Wed, 10 Mar 1999 16:54:38 -0500
> From: James Shanks <James_Shanks@TIVOLI.COM>
> Subject: Re: ovstart fails to find /usr/OV/conf/ovsuf
> To: NV-L@UCSBVM.ucsb.edu
> X-Comment: UCSBVM.ucsb.edu: Mail was sent by corp.tivoli.com
> X-Lotus-Fromdomain: TIVOLI SYSTEMS
> Content-Disposition: inline
> MIME-Version: 1.0
> Content-Disposition: inline
>
> Yes, Greg, I would start over. Who knows what else is missing. But
there
> should be an lrf for every NetView daemon.
> Or did you install the client?
>
> With the problems you have had, I would suggest a call to Support
> (1-800-TIVOLI-8) and see if one of our install specialists can help.
Then
> you can discuss what s in the error logs and such and perhaps get around
> some of these stumbling blocks.
>
> James Shanks
> Tivoli (NetView for UNIX) L3 Support
>
>
>
> Gregory Adams <gadams@US.IBM.COM> on 03/10/99 04:37:06 PM
>
> Please respond to Discussion of IBM NetView and POLYCENTER Manager on
> NetView <NV-L@UCSBVM.UCSB.EDU>
>
> To: NV-L@UCSBVM.UCSB.EDU
> cc: (bcc: James Shanks)
> Subject: Re: ovstart fails to find /usr/OV/conf/ovsuf
>
>
>
>
>
> James,
> This is a new install, although it is really the second iteration
of
> a new install. We had problems the first time around when the framework
> object for NetViewServer was not properly defined and the ICON for
NetView
> was not created. We tried to use the wln xxxxxxxxxxxxxx and then the
> wrefresh xxxxxxxxxxx commands as suggested in the release notes. This
did
> not help us so we decided to try to install the Server code again. Before
> reinstalling I ran the cleanup script in the MUSTSEE directory of the
CD.
> Maybe that was a mistake ? Anyway I went into the /usr/OV/lrf directory
and
> found only one .lrf file it was nvwebd.lrf. I added it using the
ovaddobj
> command so atleast the /usr/OV/conf/ovsuf file exists now . There are
> obviously missing lrf files. Would it be advisable to just deinstall
> NetView and start over ?
>
> Thankyou
> Greg Adams
>
|