RE: the future of SNMP
Bruce Shaw <[email protected]> Wed, 26 Feb 2003 17:30:25 -0700
| Newsgroups | gmane.ietf.eos |
|---|---|
| Message-ID | <[email protected]> |
[ post by non-subscriber. with the massive amount of spam, it is easy to miss and therefore delete posts by non-subscribers. if you wish to regularly post from an address that is not subscribed to this mailing list, send a message to <listname>[email protected] and ask to have the alternate address added to the list of addresses from which submissions are automatically accepted. ] Yes. My primary concern was that I don't want SNMP to fall by the wayside - some of us still want to use it. -----Original Message----- From: Wijnen, Bert (Bert) [mailto:[email protected]] Sent: Wednesday, February 26, 2003 5:22 PM To: Bruce Shaw; '[email protected]' Subject: RE: the future of SNMP > -----Original Message----- > From: Bruce Shaw [mailto:[email protected]] > Sent: woensdag 26 februari 2003 21:01 > To: '[email protected]' > Subject: the future of SNMP > > I certainly intend to continue SNMP into the future. Given > that systems administrators are being asked to monitor more > servers, especially rack-mounted server farms, we really > aren't left any choice in the matter. > > As SNMP is cross-platform, a vendor specific methodology is > not going to work. > > I would like to see expansion of existing MIBS. I am current > working on HOST-RESOURCES-MIB. > Thanks for your input. Sofar, that does not seem to warrant or support extra effort to extend SNMP protocol (which is what EOS was intended for) but rather to focus on more MIB objects for more/better monitoring. Is my interpretation of your statement correct? Bert This communication is intended for the use of the recipient to which it is addressed, and may contain confidential, personal and or privileged information. Please contact us immediately if you are not the intended recipient of this communication, and do not copy, distribute, or take action relying on it. Any communication received in error, or subsequent reply, should be deleted or destroyed.