topic Setting PDU thresholds using TELNET? in Operating System - OpenVMS

Setting PDU thresholds using TELNET?

Willem Grooters — Thu, 06 May 2010 09:09:19 GMT

This is probably not the right place to put the question (it's not an openVMS question) but I couldn't find another forum to ask....

I'm investigating usage of the HP S132 monitoring PDU; we've installed the management module since we want network access to it.
It's no problem to configure the basics: IP data, SNMP trap receiver en SNMP server (for accessing the data of the unit) over the serial connection - and probably over the netwerk connction, once that's enabled.

The unit can be accessed using a web interface, which allows read-write access to some of the data, and read-only to all.
But our environment lacks a web browser; some information is (potentially) adjustable, but setting thresholds is not covered in the menu. And this is must be possible over the network connection.

Does anyone have an idea how to do that?
(Sending SNMP-updates to the unit excluded - this is hardly acceptable)

Willem

Re: Setting PDU thresholds using TELNET?

Hein van den Heuvel — Thu, 06 May 2010 10:38:50 GMT

>> But our environment lacks a web browser

Maybe the infinite wisdom of the management that put this restriction in place should be challenged.

It's not web-browser that pick up virusses or glance at porn, it is people.

Put an item on the budget called 'PDU control unit' Make it expensive.. it's a a thin client, running Linux from stick with a web browser installed.

How elaborate is the control? Javascript? Flash? Sounds like basic HTML coult be all that is needed.

For basic OpenVMS, just use LYNX, or just 'talk' web with telnet or any other tool willing to read/write from a network port.
It's not all that hard to 'talk' HTML.
Several programming libraries are out there to help. Perl?

Good luck!
groetjes,
Hein

Re: Setting PDU thresholds using TELNET?

Hoff — Thu, 06 May 2010 14:19:46 GMT

Traverse the management stack until a management instantiation is reached that recognizes and processes the relative inapplicability of generic rules involved here and that then generates a corresponding exception condition, otherwise continue with the stack traversal and the next management stack frame.

Should a management stack underflow condition arise while seeking the exception handler, the last-chance employment handler underflow trap should trigger a parallel request to prepare a resume and to issue a vfork() and exec() request to the job controller.

The most explicable triggers for the prohibition of certain common tools would all tend to involve off-site access, and both can typically be filtered at the server network perimeter.

Or instantiate Grace Hopper and instantiate Lynx or cURL or a library, and get on with your job. If that usage later triggers an exception, you have to ask if farming tulips somewhere might be a better choice.