![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Hi - > Message-ID: <38E30E75.3E514AE7 at wipro.com> > Date: Thu, 30 Mar 2000 13:51:09 +0530 > From: "Abhishek Bagchi" <abhishek.bagchi at wipro.com> > To: ietf at ietf.org > Subject: More error-status codes on SNMPv1? ... > Is there any other way we can add more error-status codes without > violating v1 > compliance? At the level of the protocol, no. > We don't want to move over to SNMPv2 ,but, still want to add more > error-status codes? > Can we add more error-status codes? If so, how? ... I would suggest using SNMPv3. ------------------------------------------------------------------------ Randy Presuhn randy_presuhn at bmc.com http://www.bmc.com/ Voice: +1 408 546-1006 BMC Software, Inc. 1-3141 2141 N. First Street Fax: +1 408 965-0359 San Jose, California 95131 USA ------------------------------------------------------------------------ Any relationship between my opinions and BMC's should be coincidental. ------------------------------------------------------------------------
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.