Re: PM3 + SNMP (fwd)

Alex (alex@livingston.com)
Fri, 27 Sep 1996 12:11:45 -0700

Duly noted. Thanks for the feedback--and for the explanation. As I've
written to a couple of you--please do give me heads up on any SNMP
requirements, needs, wishes, desires, dreams, fantasies, etc. that you have.
As in this example and others, its particularly helpful to hear *why* you
need something because as we comb through all the requests, the ones that
will come clearest the quickest are the ones that have sort of a
business/technical case behind them--ya kno whut I mean?

At 10:34 AM 9/27/96 -0400, you wrote:
>I would also like to see last connect speed. Can the PM ask the modem for
>the value(s) from some number of S-registers and include this data with the
>stop or start record. It would really help when modems start (or stop)
>acting in a certian way. This would take the SNMP management *almost* to the
>modem level.
>
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>
>>On Thu, 26 Sep 1996, Alex wrote:
>>
>>> How would you want that represented to you? Whats this going to look like
>>> in an ideal world?
>>>
>>> alex
>>
>>I want to see all of the stuff that is sent in radius stop packets
>>included. Things like the the session ID to match the info up with
>>radacct packets; cumulative traffic in/out; cumulative seconds (pmconsole
>>can't give it with that precision); the static/dynamic IP assigned; and so
>>forth.
>>
>>I'm afraid I don't have a strong handle on the limits of SNMP ( I stopped
>>exploring it as soon as I figured out the portmaster's SNMP could not
>>provide this kind of info). But I would think there could be an
>>somewhere.ports.number
>>somewhere.ports.info.#.username
>> .sessionid
>> .time
>> .octetsin
>> .octetsout
>> .user-service
>> .protocol
>> .speed
>> .errorsin
>> .errorsout
>> .portname
>>
>>Basically, each serial interface has certain information that the
>>portmaster already knows about it: physical characteristics,
>>configuration, statistics, state (including current connection). All of
>>this information should be presented with SNMP. A new COMOS version
>>should automatically have a new MIB that includes everything that has been
>>added. (Yes, its a pain for the sysadmins, but I think it would be worth
>>it.)
>>
>>Really, *anything* that the portmaster knows should be made available via
>>SNMP, though that's probably asking a bit much ;-).
>>
>>
>>> At 09:51 AM 9/26/96 -0700, you wrote:
>>> >
>>> >User name would be a HUGE +. If I could get who's logged in via
>>> >SNMP from all my portmasters I'd be very happy.
>>> >
>>> >> We need at least ability to get interface status (user on, user off,
>>> >> logging in), fixed bugs with interface speeds. SNMP traps would be agood
>>> >> thing too, but better concentrate on interface statistics.
>>> >>
>>> >> tia, Paul
>>> >>
>>> >
>>>
>----------------------------------------------------------------------------
>>> >Ryan Mooney Phone (602)265-9188 PCSLink
>>> >ryan@pcslink.com Fax (602)265-9357 Internet Services
>>> >
>>> >The world needs more bitter, twisted souls. It would be a much better
place.
>>>
>>-----------------------------------------------------------------------------
>>> >
>>> >
>>> Alex Henthorn Livingston Enterprises
>>> Senior Technical Product Manager 6920 Koll Center Parkway #220
>>> Product Marketing Engineer Pleasanton, CA 94566
>>> alex@livingston.com Voice 510-485-6787 Fax 510-244-1903
>>>
>>
>>- ----------------------------------------------------------------------------
>>Steven P. Crain scrain@shore.net http://www.shore.net/~scrain
>>Shore.Net Unix Development and Administration
>>
>>-----BEGIN PGP SIGNATURE-----
>>Version: 2.6.2
>>Comment: Finger me for a public key.
>>
>>iQB1AwUBMkvfh40DAXSiDippAQF6zQMAi4rS8shEeTeRgMvZj0rcusIvNsQ9nTca
>>4AQENL8xIxDQJsNdwpZ+qoCnqW+xnkqSLp9VtwtFsdo1uBhSvrqnQsKSYunkUEST
>>0T5HJTUtTaCCxUCVv3HaDCa+fv0NWuSu
>>=v80a
>>-----END PGP SIGNATURE-----
>>
>>
>>
>----------------------------------------------------------
>Dan Struthers
>
>The solution to any problem lies in its proper definition.
>----------------------------------------------------------
>
>
>
Alex Henthorn Livingston Enterprises
Senior Technical Product Manager 6920 Koll Center Parkway #220
Product Marketing Engineer Pleasanton, CA 94566
alex@livingston.com Voice 510-485-6787 Fax 510-244-1903