1. 1 Kyung Hee University Prof. Choong Seon HONG SNMPv2 MIBs and Conformance SNMPv3 Architecture and Applications

2. 2 Kyung Hee University Introduction  Describing SNMPv2 MIB  Specifying conformance requirements for standardized MIBs  Enabling vendors to document the scope of their implementation.  Looking at the interfaces GROUP

3. 3 Kyung Hee University 13.1 SNMPv2 Management Information Base  Describes objects that describe the behavior of an SNMPv2 entity  Consisting of three groups : System group : an expansion of the original MIB-II system group to include a collection of objects allowing an SNMPv2 entity acting in an agent role to describe its dynamically configurable object resources. SNMP group : a refinement to the original MIB-II snmp group, consisting of objects providing basic instrumentation of protocol entity MIB objects group : a collection of objects that deal with SNMPv2- Trap PDUs and that allow several cooperating SNMPv2 entities, all acting in a manager role, to coordinate their use of the SNMPv2 set operation

4. 4 Kyung Hee University 13.1.1 System Group  New objects have names beginning with the prefix sysOR  Related to system resources and are used by an SNMPv2 entity acting in an agent role to describing those resources that it controls that are subject to dynamic configuration by a manager.

5. 5 Kyung Hee University System Group (cont’d)  Revised system group Describing object resources that the agent controls that are subject to dynamic configuration by a manger

6. 6 Kyung Hee University System Group (cont’d)

7. 7 Kyung Hee University 13.1.2 SNMP Group  Contains some basic traffic information of some of the original objects

8. 8 Kyung Hee University SNMP Group (cont’d)  All but one of the objects are 32-bit read-only counters in Table 13.2  The remaining object, SnmpEnableAuthenTraps is a read-write enumerated integer, with the values enbled(1) and diasabled(2) that indicates whether the SNMPv2 entity is permitted to generate authenticationFailure traps  A comparison with the original MIB II snmp group (Figure 7.7) shows that the revised group (Figure 13.2) has far fewer parameters.

9. 9 Kyung Hee University 13.1.3 MIB Objects Group  Contains additional objects pertinent to the control of MIB object

10. 10 Kyung Hee University 13.2 Conformance Statements  The purpose of the conformance statement is to define a notation to be used to specify acceptable lower bounds of implementation, along with the actual level of implementation achieved. OBJECT-GROUP : indicates those objects in a MIB module that are part of a conformance group l OBJECT-GROUP macro provides a systematic means for a vendor to describes its degree of conformance by indicating which groups are implemented. NOTIFICATION-GROUP : identifies a collection of notifications l used to define a collection of notifications for conformance purpose MODULE-COMPLICANCE : defines compliance requirement for an agent with respect to MIB modules and objects l specifying a minimum set of requirements with respect to the implementation of one or more MIB modules. AGENTS-CAPABILITIES : defines the capabilities provided by a particular agent implementation