ITEM: AE0871L
Netview/6000 support-ref: P8155
Response:
E: Netview v2.1 with U434057 just applied.
D: customer is receiving events for nodes that are not in any maps. He has
about 9000 nodes in the topology db but only 2000 in the maps. There is
only one map. He has run ovmapcount -vu and ovtopofix -a and the objects
that are still managed but in no maps do not get deleted.
D: customer ran the ovtopofix and got some messages:
>\<200.1.1.Segment1 (266) -- not in any maps, updating times.
>\< Updating 200.1.1.Segment1 (objid = 266)
AFter some discussion, it was discoverd that the nodes that he was getting the
alerts from were on the same network as the netview machine. He had some
unmanaged nodes in his maps and was not getting any events for them. Only
for the nodes that were not in any maps.
128.192.1.187 is the netview machine with netmask 255.255.0.0
128.192.15.66 is an example of a machine that is having events reported for
it that are unwanted.
The problem is that Netview will monitor all nodes on its local network.
The customer has deleted these nodes so they are not in any maps. This is
what is causing the events to be reported because netview does not know
what the status of the object is.
The solution is one of the following:
1) Turn autodiscovery back on, rediscover the nodes that are missing,
unmanage them, and put them into an unmanaged map. This way Netview
"knows" about them and can turn off the incoming events, status polling,
etc because the status is unmanaged.
2) set up filters to filter out the events that are coming from those machines
and have the filter either exclude the machines from which you do not want the
events, or filter out that event from all machines.
3) delete the maps and topology database, turn off autodiscovery and then
use a seed file to only rediscover the nodes that you wish to manage.
Of the above solutions, customer is going to implement the 1st one.
Support Line: Netview/6000 support-ref: P8155 ITEM: AE0871L
Dated: January 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:29
Comments or suggestions?
Contact us