Black Box LEV2525A - Supported Mibs and Rfcs

MNS-BB Software User Guide
-41-
privacy---An encrypted state of the contents of an SNMP packet where they are prevented from
being disclosed on a network. Encryption is performed with an algorithm called CBC-DES (DES-56).
read view---A view name (not to exceed 64 characters) for each group that defines the list of object
identifiers (OIDs) that are accessible for reading by users belonging to the group.
security level---A type of security algorithm performed on each SNMP packet. The three levels are:
noauth, auth, and priv. noauth authenticates a packet by a string match of the user name. auth
authenticates a packet by using either the HMAC MD5 algorithms. priv authenticates a packet by
using either the HMAC MD5 algorithms and encrypts the packet using the CBC-DES (DES-56)
algorithm.
security model---The security strategy used by the SNMP agent. Currently, MNS-BB supports three
security models: SNMPv1, SNMPv2c, and SNMPv3.
Simple Network Management Protocol (SNMP)---A network management protocol that provides a
means to monitor and control network devices, and to manage configurations, statistics collection,
performance, and security.
Simple Network Management Protocol Version 2c (SNMPv2c)---The second version of SNMP, it
supports centralized and distributed network management strategies, and includes improvements in
the Structure of Management Information (SMI), protocol operations, management architecture, and
security.
SNMP engine---A copy of SNMP that can either reside on the local or remote device.
SNMP group---A collection of SNMP users that belong to a common SNMP list that defines an
access policy, in which object identification numbers (OIDs) are both read-accessible and write-
accessible. Users belonging to a particular SNMP group inherit all of these attributes defined by the
group.
SNMP user---A person for which an SNMP management operation is performed. For informs, the
user is the person on a remote SNMP engine who receives the informs.
SNMP view---A mapping between SNMP objects and the access rights available for those objects.
An object can have different access rights in each view. Access rights indicate whether the object is
accessible by either a community string or a user.
write view---A view name (not to exceed 64 characters) for each group that defines the list of object
identifiers (OIDs) that are able to be created or modified by users of the group.
8.9.3 Supported MIBs and RFCs
This feature supports the following RFCs:
RFC 1901-1908 – SNMPv2
RFC 2271-2275 – SNMPv3
• RFC 1901, Introduction to Community-Based SNMPv2. SNMPv2 Working Group.
• RFC 1902, Structure of Management Information for Version 2 of the Simple Network Management
Protocol (SNMPv2). SNMPv2 Working Group.
• RFC 1903, Textual Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2). SNMPv2 Working Group.
• RFC 1904, Conformance Statements for Version 2 of the Simple Network Management Protocol
(SNMPv2). SNMPv2 Working Group.
• RFC 1905, Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2). SNMPv2 Working Group.
• RFC 1906, Transport Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2).
• RFC 1907, Management Information Base for Version 2 of the Simple Network Management
Protocol (SNMPv2). SNMPv2 Working Group.