Specifications

VS-1200-S Data Acccess Switch82
© 2011 Datacom Systems Inc
secure (for example by using IPsec), even then, there is no control as to who on the secure
network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB
module.
It is RECOMMENDED that implementers consider the security features as provided by the
SNMPv3 framework (see [RFC3410], section 8), including full support for the SNMPv3
cryptographic mechanisms (for authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED.
Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is
then a customer/operator responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to the objects only to those
principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.
8. References
8.1 Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP
14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S.
Waldbusser, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578,
April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S.
Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S.
Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.
[DSI-SMI] Datacom Systems, Inc., "The Datacom Structure of Management Information
(SMI), July 2010.
8.2 Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability
Statements for Internet-Standard Network Management Framework", RFC 3410, December,
2002.
9. Change Log
Changes introduced in revision "201007015000Z", 15 July 2010 - initial version