| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2180.1 | root IP icon stays blue | ZUR01::FUEGLISTER | Roland Fueglister, 760-2498 | Tue Jan 28 1997 10:47 | 22 |
| I seemed to run into the same problem as described in .0
I had running the internal kit V4.1C for quite a while; I did an upgrade from
PNV V4.1B.
Today I experienced problems with the NetView database; a new database didn't
solve the problem.
Therefore I did a brand new PNV 4.1C Installation, no errors shown up so far in
the /tmp/update.log and /tmp/pnvinstall.log. All deamons were running fine.
The Problem:
The root icon stays blue, no nodes are discovered. Some Nodes are in the object
database but with only a few fields, the topology database contains zero nodes.
I have now reinstalled PNV4.1B and this version runs perfect.
Is there a known problem with the internal kit V4.1C?
Roland
|
| 2180.2 | | MOLAR::SIEGEL | MS: ZKO1-3/H18 DTN: 381-0035 | Wed Jan 29 1997 10:53 | 15 |
|
Hi Roland,
Brian Thompson reinstalled PNV V4.1C at the customer site on 1/17/97 (or at
least I assume he did...he asked me to be reachable in case he had any
problems).
I haven't heard whether or not the customer's problem still exists. Also,
I have not been able to reproduce the problem on in-house systems.
What else is happening on the system? Have you tried installing the PNV
V4.1C kit from the Con Dist yet?
Joanna
|
| 2180.3 | Con Dist PNV4.1C same problem | ZUR01::FUEGLISTER | Roland Fueglister, 760-2498 | Thu Jan 30 1997 05:51 | 21 |
| Hi Joanna,
Bad News! In the meantime I got the Con Dist with PNV V4.1C kit.
I deinstalled PNV 4.1B without backup and did a fresh PNV4.1C installation. I
have the same misbehaviour as with the internal kit.
Unix Version: Digital UNIX V4.0 (Rev. 386) with CDE
NetView: NetView V4.1C (Rev.55)
Symptoms:
- The root/Subnet/Segment hierarchy is created, neighbor subnets are set to
unmanaged
- There are only blue symbols and brown symbols for the unmanaged adjacent
subnets on the map
- there are no node/interface symbols on the map
- The output of ovobjprint shows node and interface objects, but with only 2
fields (Field ID 10,27 or 10,11)
- The output of ovtopodump -l shows zero hosts
Roland
|
| 2180.4 | Same Problem on Customer System | JULIET::LOLA_JI | | Thu Jan 30 1997 19:10 | 26 |
| One of my clients was having exactly the same problem on one of their
production systems.
We deinstalled Netview V4.1B and did a fresh install of V4.1C. We were
unable to manage anything. We deinstalled NetView V4.1C and reinstalled
NetView V4.1B and we were then able to get things working.
Unix Version : Digital UNIX V4.0A with CDE
NetView : NetView V4.1C (from Jan 97 Layered Products) = Not
Working
NetView V4.1B (from Oct 96 Layered Products) = Working
Last week when we were trying to troubleshoot these problems, a
customer call was placed with the MCS Support Center to report this and
attempt to get help. No return call for five days.
Is this product broken? Is there a patch? If this is broken,
shouldn't an advisory be put out to those customers that have licenses
to NOT to install this product? I know that my clients would
appreciate such advisories.
Could someone from NetView Engineering please comment on this?
Jim Lola
Systems Consultant
Digital NSIS
|
| 2180.5 | | TUXEDO::MINTZ | Erik Mintz | Fri Jan 31 1997 09:59 | 19 |
| Jim-
The V4.1c was tested by engineering and worked correctly. In fact it
is still working correctly here; we have been completely unable to
replicate the problem.
Could you please send a note to MOLAR::SIEGEL with the following information:
- Has PDM ever been installed on the system?
- Are any other network related products running on the system
(ClearVSN, DECnet, ...)
- If you have a system still running V4.1c, what happens if you issue
"TEST->DEMAND POLL" for a system running SNMP?
We need to characterize the problem before we can take effective
correction action, so any help in narrowing down the circumstances
will be greatly appreciated.
-- Erik
|
| 2180.6 | PNV 4.1C upgrade again | SPANKY::THOMPSON | | Fri Jan 31 1997 10:27 | 11 |
| Joanna On the 17th I went back to the customer to just install PNV
4.1C and not PDM like you asked.
The GUI was already down, a ovstatus showed all daemons running except
gtmd. I then did a ovstop, after 15 minutes the daemons still had not
stopped. I then booted the system and got a disk error and eventually
ended up with a bad system disk. I've replaced the disk and installed
Unix and OSI yesterday and will be installing PNV,PDM & Probewatch
wednesday. I'll yet you know how things go.
thanks
brian
|
| 2180.7 | restart inetd as a workaround | MOLAR::SIEGEL | MS: ZKO1-3/H18 DTN: 381-0035 | Wed Mar 05 1997 16:44 | 13 |
|
Restarting the network is a workaround for this problem. Use netsetup
to restart the network (/usr/sbin/rcinet restart) . When you exit the
procedure it will ask you if you wish to restart the network.
Warning---anybody remotely logged in will be disconnected.
I have tested this out on several systems which had this problem and
autodiscovery worked. If this doesn't fix your problem, please let me
know.
Thanks,
Joanna
|