Search results for query: *

The above post sounds good, if I want to delete then readd a node (NNM6.4 W2k) I do this: ovstop netmon ovtopofix -a ovstart netmon then use the loadhost command: loadhost 255.255.255.0 ip.ip.ip.ip hostname the node should pop up in a holding tank on in the correct location on the map. - I...

I am certainly no expert but here are some guesses based on the little experience I have. We have a similar situation, and here is what we did: 1) we wrote our own proxy agents in C++ and they run as NT services at remote computers, collecting sensor status from a serial controlled device. (We...

You could try a loadhost to load one of the PCs into NNM then do a demand poll to it to see the results. &quot;loadhosts -m <subnetmask> <ip address> <host name>&quot; Checking the readonly community string is first step (as mentioned above). Also, is autodiscover turned on, if not turn it on...

W2k NNM 6.3 We are running NNM on a server in the &quot;back room&quot;. We do not keep an open, active window on this server. In the &quot;front room&quot; we have several workstations running NNM client (connected to NNM on the server). I have noticed that when objects change severity, the...

NNM collects events in its private database. The problem is, there is a limit to the number of events it keeps, and once full, it will purge the old ones. Which is to say, unless you periodically export to a data wharehouse, you may not be able to look back 2-3 months. I believe the best way...

FYI, windows 2000 allows you to configure your services to restart if the fail/stop. This does not solve your monitoring problem, but may help if things go &quot;waco&quot; (which I have never seen happen on those services). Also, Dell servers have a more sophisiticated managment interface...

When doing auto layout, you can do it on individual submaps instead of all maps. This way, you can drill down into you state submap and autolayout that without affecting any other maps. Open a submap then, &quot;Map | submap | properties&quot; then [view] tab and &quot;autolayout&quot; radio...

We had the same problem (on Win2k), it was absolutely a DNS problem. Try this command (if available on unix) &quot;checkdns.ovpl&quot; located in the \openview\support directory (on Win2k). It will do a DNS lookup on all devices OV knows about and will indicate which are not translating fast...

Your Frenchie response sounds like a memory access violation (although I speak no French). Maybe that is what is killing your Netmon. Try this too, from the command window: &quot;ovstatus -v netmon&quot; gives a verbose status of the netmon process and will tell you if it behind in polling...

We have written our own SNMP Sensor agents to monitor those items. We used SNMP Research's Emanate to create our MIBs and proxy agent template structures (written in VisualC++). We designed our agents to talk to a legacy &quot;box&quot; via serial interface. The legacy &quot;box&quot; is an...

Maybe you need to install CIM components on the client workstations. Maybe when the users click on the web-enabled icon, it is looking at the local workstation and not the server hosting NNM??

We just did the same thing and had a consultant in to help, he strongly suggested we keep them on separate machines. (We happen to be on NT machines).

There are two ways to license NNM on Windows - by IP or by machine ID - most people probably use IP. HP can get you a new license in a day - just go to web-site or call your support number.

Also note that there is a setting that tells NNM to remove unreachable nodes from map after a settable period of time. This may be why your ATM nodes are disappearing - you can disable this. See: Options | Network Polling Configuration | Setting tab.

You may wish to try the book &quot;Professional NT Services&quot; by Kevin Miller. It will show you how to do the service right and tell you tips and tricks you won't get from using the ATL wizard - a definite must have resource however you do your service.

We are running HPOV 6.1 NNM on an NT network. The people that monitor the system do so on workstations that use the remote client into NNM to see the map. We want an audible alert to go off anytime status changes. The alert should be heard on any workstation that has a client open. I know...