Errorlog from EVA to OpenVMS system

[Henri van Veldhuisen]

We changed the the storage solution on OpenVMS cluster from a MA8000 (HSG80) configuration to a EVA3000 configuration. When using the MA8000 all errors on the MA8000 where reported to OpenVMS errorlog. Now all reports about the EVA3000 are logged by the Management appliance.

Because of system management and the solution that was build for error reporting using OpenVMS errorlog we would like to use OpenVMS errorlog also for reporting errors about the EVA3000. Is there someone who has don this already. Now a workaround is used by sending messages from the managagement appliance to the OpenVMS system

[Tom O'Toole]

heh! Good luck!!! Your best bet would be to install webes on the sanapp, and have it mail out error messages. We have spent a lot of time trying to get anything out of the 'hp SOM' notification facility. It's convoluted, overengineered, buggy as hell, and a major waste of time. Webes notifications are much easier to configure, more reliable, and more informative.

Of course, this is still a far from ideal situation, and a situation of HPs making.
It's unfortunate that simple, proven methods (the errorlog, the serial console from the hsg80s) are being abandoned by HP, in favor of inserting as many bathgatesOS boxes as possible into customer sites by force. We are supposed to administer our enterprise systems with these virus magnets.

Because there were so many complaints about the sanapp, the future direction was to be to eliminate it. Now, it turns out that the HP definition of 'elimination' is allowing the customer to use a 'standard' MS pc, instead of a custom MS pc.

GEEEEEEEEEEAAAAAAAAAAZZZZZZZZZEEEEEEEEE!

[Cass Witkowski]

Tom,

Why don't you tell us how you really feel. :)

Cass

[Jan van den Ende]

Re

"Why don't you tell us how you really feel."

because the he (like me) would be blocked from further access to this site for foul-mouthing!

Personally, I have a special relation to billyboxes: I hate them so much that they feel it, and therefor refuse me even what service they are able to give others.
Under my eyes and fingers they have a widely-above-average chance of crashing, dumping, blue-screening, hanging, etc.

HP ---REALLY--- should make available decent means ( = PC-free ) control over the entire config... :-(


Proost.

Have one on me.

Jan

[Ian Miller.]

sounds like another good topic for discussion with HP at the bootcamp - I wonder who they will send from HP management.

[Uwe Zessin]

It won't happen.

[Tom O'Toole]

I agree with Uwe, it won't happen, but it's one of the worst things about dealing with HP in particular, as a vendor, and most vendors in general. It's funny, there was one of those 'polls' at computerworld.com (these trade rags are really just the 'access hollywood' of the IT world - a publicity cycle for vendors to create churn. Note how they always quote 'industry analysts' like 'the gartner group' instead of end users, who love to label everything but the flavor of the week as 'legacy' ), asking if customers were in control of their vendors, or the other way around, and the majority of customers actually said they were in control. What planet are they from?? I offer the 'SAN Appliance' (and all other bathgatesOS 'management agents') as instant proof to the contrary.

[Willem Grooters]

Back to the topic, guys.

WEBES is a solution, and it does NOT require a PC. For what I know, it offers facilities - with some extra software - for communication, even directly to HP for logging and escalation, and e-mails to anyone you wish.

Another possibility is to look for alternatives, I think Cockpit Manager (previously HP, now with Emulators Int. (http://www.emulatorsinternational.com/en/cockpit.htm) would be a possibility. For the purists: It's a genuine VMS-only application.

[Uwe Zessin]

Correct me if I'm wrong, but:

- the EVA doesn't do direct eventing to OpenVMS hosts. How is a VMS-based WEBES going to help?

- you cannot manage the EVA through the serial port - there is no CLI. It is only for low-level diagnostics and maintenance.

Please, don't touch the port! If you're unlucky, you can force a 'hard-stop' on both controllers.

[Ian Miller.]

Willem, Cockpit Manager is still developed by HP but is sold via Emulators International.

I don't know if WEBES will communicate with the EVA3000.

[Tom O'Toole]

Using WEBES for EVA event management certainly does require a PC. The sanapp is where the events are logged.