Two things. Second, the message in netmon.trace: This happens under a
couple
of circumsances, one of which is when you run multiple demandpolls and it
runs
out of memory. This is fixed in 5.1.1. The message you were supposed to
find was
not there, probably because netmon died at a bad time, or maybe that was an
old message. With 5.1, lots of interesting information is being reported in
netmon.trace
(in /usr/OV/log). It pays to take a look in there from time to time. (Too
bad there are
no time stamps in it).
And for the first case, check the device. I just saw one today and handed
it over to
the network analyst to investigate. But I did do a Monitor..Network
Configuration...
Addresses, and sure enough, the device is reporting a mask of 0.0.0.0. So
Netview
is reporting that the mask has changed. The message that should have
appeared in
netmon.trace would say about the same thing: the node is in an incorrect
network,
please delete and rediscover it. This is because Netview will not correct
that
sort of placement problem on its own. (Otherwise loadhosts -m would not be
able
to allow you to falsify a network mask).
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Hi, group!
That's what NetView tells me...
Mar 31 09:15:48 10.224.8.80 Network Mask for 10.224.8.80 Changed to
0.0.0.0, see netmon trace for details
That's the netmon.trace file i can find...
[root@NMSSR1:/home/root]> find / -name "netmon.trace" -ls
12451 4 -rw-rw-rw- 1 root bin 66 Feb 20 13:46
/usr/OV/log/netmon.trace
That's the contents of this netmon.trace file...
[root@NMSSR1:/home/root]> cat /usr/OV/log/netmon.trace
Node/Iface or memory allocation error in allocSnmpState - exiting
Ever seen anything like that?
Something to worry about?
Or just something to ignore?
Thanks, Ralph.
iT-AUSTRIA / OE2100 / TK-NET
Tel. +43 1 21717 58948
FAX +43 1 21717 58979
Mobil 0664 1908469
Mailto:Ralph.Schiffinger@erstebank.at
|