VMS system monitoring software for HP Openview.

[Gino Castoldi_2]

Hi,

Server: Alpha 4100, VMS 6.2

We are looking for a software product to monitor VMS systems. What we are looking for are ideas on what people are using to perform this function. Whatever the product is it should be able to integrate with HP's Openview/Operations product (ITO/OVO).

We are basically looking for a monitoring solution that can work with HP OVO.

10 points to any good answer or idea.
TIA, Gino

[labadie_1 · Accepted solution]

I am afraid you need Vms 7.1 to have such an agent, see

http://h18004.www1.hp.com/products/quickspecs/10450_div/10450_div.html

[Ian Miller.]

BMC Patrol will run on VMS V6.2 and feed events upwards. It's a bit nasty unix like though.

[Mike Naime]

Gino:

The short answer is "It can't be done"

We have/had the complete HPOV suite installed in our data centers. For monitoring the 200+ OpenVMS alphaservers we use BMC Patrol and Consoleworks.

We also use Consoleworks to monitor the 72 CLI ports on our HSG80 storage controllers.

Why repeat myself. :-)
For an earlier thread on this exact topic, go back to page 15 and look at this thread labeled MANAGING OPENVMS.
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=353508

Mike Naime.

[Wim Van den Wyngaert]

Gino,

I monitored at max about 200 servers and stations using simple DCL (4000 lines).

1 script that barely needs config but that monitored nodes 5.5, 6.2 and 7.x, using decnet 4 and 5, ucx 2.x,3.x,4.x,5.x.

I included a description of what it monitors. Some items are specific to this bank (but the script knows it).

Wim

[Wim Van den Wyngaert]

It didn't follow the internal http link

[Wim Van den Wyngaert]

Mike : what do you monitor via consoleworks ?

We use console manager but the scans are not active. What I'm missing is something that doesn't scan for known things but something that tells me when an unknown thing happens.

E.g. if the message "I don't like this my job. I am going to crash" appears on the console, that it is considered as unknown and thus an alarm must be given.

Wim

[labadie_1]

Wim, in the Report memory shortages of all kinds , I would add the npagedyn pool expansion failure. You can get it in sda, or even simpler:

$ mc agen$feedback
$ sea sys$system:agen$feedback.dat npagedyn_allocafail

The first line is the same as
$ @sys$update:autogen savparams savparams, but is shorter

[Wim Van den Wyngaert]

Labadie,

Thanks for the tip. I give an alarm when 50% of the max is used.

E.g. NPAGDYN 4, NPAGVIR 16 alarm at 8.

This alarm indicates that something is wrong or that the 4 is too low.

And autogen is too heavy for regular usage.

Wim (can't give you a point, sorry)

[labadie_1]

What you do should work nearly always, but I remember some stupid soft, trying to do directly a pool expansion from npagedyn beyond npagevir.