RE: Some REALLY serious ramifications of the SNMP deal ? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: RE: Some REALLY serious ramifications of the SNMP deal ?
From: "Fritz Hayes" <fhayes@xxxxxxxxxxxxx>
Date: 20 Feb 2002 09:13:22 -0800
Importance: Normal
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/cgi-bin/listinfo/midrange-l>,<mailto:midrange-l-request@midrange.com?subject=unsubscribe>
Organization: Atwater Associates

Did you test the SNMP with something like a MIB Browser (check out
SolarWinds product) to confirm it is a SNMP problem vs code?

Best Regards

Fritz Hayes
Atwater Associates
<snip>
>
|
|I was trying to use snmpGet(). Maybe bad VooDoo.
|It did work the first time, meaning that I got all the
|issues with what has to in ASCII and what has to
|be in EBCDIC correct.
|

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

SNMP sample code , Leif Svalgaard

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.