These updates are provided in anticipation of the 77th IETF meeting to be held in Anaheim, California, USA, March 21-26, 2010

YANG modules are to NETCONF as MIB modules are to SNMP. YANG modules are defined within the relevant working group and reviewed by a small cadre of IETF YANG experts prior to publication as an RFC. The following provides a brief outline of and links to the current works-in-progress.

Note that Internet-Drafts are works-in-progress and expire when a subsequent revision is available, or six months after initial publication, whichever occurs first.

I am happy to discuss the usefulness and applicability of the below works-in-progress to your project. Just contact me with your project requirements and ideas.

Operations and Management Area:

• IP Flow Information Export (ipfix)
  • Configuration Data Model for IPFIX and PSAMP
    draft-ietf-ipfix-configuration-model-05” – 8-Mar-10

• Network Configuration Working Group (netconf)
  • Guidelines for Authors and Reviewers of YANG Data Model Documents
    draft-ietf-netmod-yang-usage-03 – 14-Jan-10
  • YANG Module for NETCONF Monitoring
    draft-ietf-netconf-monitoring-12” – 23-Feb-10

I recently evaluated the SNMPv3 Advanced SNMP Agent SDK offered by DMH Software.   A product profile and evaluation synopsis follow.

Product Profile

DMH Software sells a software developers kit consisting of an SMIv2 MIB compiler and their portable, SNMPv3 capable Advanced SNMP Agent runtime libraries.

NetBurner sells a single board device running uc/OS on a Freescale Coldfire 68K processor that served as the embedded target environment.

Evaluation Approach

For this evaluation, the ALARM-MIB (RFC 3877) was implemented using the DMH Software SDK for the NetBurner embedded environment.  The ALARM-MIB was selected for reasons that include:

• the OBJECT-TYPE definitions include every possible SMIv2 sytnax type.
• the tables have multiple index components using OCTET STRING and INTEGER syntax types.
• the two NOTIFICATION-TYPE definitions, alarmActiveState and alarmClearState, enable evaluation of APIs for sending notifications.
• the design of the alarmActiveVariableTable allows each row to contain one of the variable bindings sent in a notification. As such, the alarmActiveVariableTable is a ’sparse’ table containing rows with only three accessible object instances out of ten accessible OBJECT TYPE definitions.

To implement the ALARM-MIB, the following steps were taken:

• the host environment was set up on a Windows XP laptop with the NetBurner supplied Eclipse based IDE and cross compiler, linker and debug utilities.  A NetBurner model 5234 board was used as the target environment.
• the DMH Software SMIv2 MIB compiler was used to generate code from the ALARM-MIB.
• custom code was added to the generated code to complete the functional implementation.
• the NetBurner SDK was used to compile the generated and custom code and to link it with the DMH Software SNMPv3 agent and NetBurner runtime libraries.
• the resulting executable was flashed onto the NetBurner board and tested using the Net-SNMP command line tools.

Evaluation Results – MIB compiler

The DMH Software SMIv2 MIB compiler is based upon and extends utilities that are part of the well known open-source libsmi distribution.  Thus, I experienced a familiar and comfortable feel with the DMH MIB compiler utilities.  Version 1.4.5.0.5 of the SMIv2 MIB compiler was used in the evaluation.

The code generated for the ALARM-MIB consisted of three source files, alarm-mib.c, alarm-mib.h and alarm-mib-sys.c.  The generated source code was modular, of good quality and well annotated with information from the ALARM-MIB as well as comments that clearly indicated where custom code was required to complete a functional implementation.

During the evaluation I encountered several minor issues with the source code generated from the DMH Software MIB compiler:

• generated code contained erroneous range checking for the SMIv2 BITS construct.  NOTE: this issue was resolved within three days of reporting it to DMH Software.
• some code was not generated for the alarmActiveDateAndTime nor alarmClearDateAndTime index components.  NOTE:  this issue was resolved within three days of reporting it to DMH Software.
• generated code for enumerated values would be a welcome addition.
• generated code could do a better job handling SMIv2 Textual-Conventions.  Most of the generated code and comments accurately reflect the underlying base syntax type, rather than the restrictions placed upon the base syntax by the Textual-Convention.  NOTE: support for the RowStatus and StorageType Textual-Conventions are built into the SNMPv3 SDK APIs.

Evaluation Results – SNMPv3 SDK

The DMH Software Advanced SNMP Agent was designed to produce a small executable with embedded and real-time applications in mind.  From tests run, I was pleased to find excellent support for version 3 of the SNMP that included the set of SNMPv3 MIBs for USM, VACM, and Notification targets.  Version 5.0.1.12-2 of the SNMPv3 SDK was used in the evaluation.

The provided developers’ documentation consisted of an integrated set of html pages.  It took a little time to get used to navigating the frames and tabs of the documentation to find the information I needed.  In a handful of instances I found information not available in the documentation by searching through the SNMPv3 SDK include files.

The provided API consisted of a small, concise and well thought out set of functions. From my perspective, a small and concise set of functions is beneficial, serving well the target audience of developers creating management applications.  In general, I found the API provided with the DMH SNMPv3 SDK easy to understand and use.

During the evaluation I encountered a couple of minor issues with the DMH SNMPv3 Agent API:

• the agent cited an error when passed a variable binding tagged with a syntax of Opaque.  NOTE:  This issue was resolved within three days of reporting it to DMH Software.
• while there are two API functions for sending notifications, neither provided a mechanism for the caller to provide the value for sysUpTime.0 for an outgoing notification.  While perceived as a hindrance upon implementing the ALARM-MIB for this evaluation, DMH did offer to resolve this issue in a future release.

Evaluation Results – Summary and Conclusion

Overall, I was pleased with the functionality, features and support offered by DMH Software in their Advanced SNMP Agent SDK product.

Additionaly, I am pleased to report that the SMIv2 MIB compiler generated modular code of good quality and that DMH Software’s response time on technical issues was superb.

If your software development project involves the NetBurner embedded target environment and has a need for an SNMPv3 agent then I recommend you consider using the DHM Software Advanced SNMP Agent for your software development project.

Please contact me if you need to identify applicable IETF published MIB modules. need to design a private enterprise MIB module, or require a quick and sure start with the DMH SDK.  Find out how easily my expertise and skills can support your development team and contribute to a successful design and realization of your software project.

In a world of commercial and open source software toolkits, how can we best identify and select the option lowering the cost of developing SNMP Agent and SNMP Manager applications?

The goal in selecting an SNMP developers’ toolkit is to find the most cost effective means to accelerate development and realize successful project completion.

During the process of SNMP toolkit evaluation, we need to consider factors from both the technical perspective and business perspective.

Some examples of business factors:

• What are the terms and obligations of the distribution license?
• What level of engineering expertise do we need on staff to effectively use the toolkit?
• What is the initial cost for the toolkit?
• Are there annual maintenance and support costs?
• Do we need to track and pay royalties on derivative works?

Some examples of technical factors:

• Does the toolkit include fully compliant implementations of SNMPv1, SNMPv2c and SNMPv3?
• How well does the toolkit scale when handling a heavy volume of encrypted SNMPv3 messages?
• Is the toolkit easily portable to a variety of hardware platforms and operating systems?
• What useful MIB implementations and utilities are included with the toolkit?
• How helpful is the developers documentation?
• Is the SNMP toolkit API concise or bloated?
• Is the SNMP and MIB terminology used in the toolkit consistent with IETF published RFCs?

• What level of technical support exists? Is there an active developer and user community?
• Does the SNMP toolkit integrate well with other technologies (e.g. Corba, WBEM, Syslog, XML, JMX, TL1)?

Based upon the relative significance of each factor we can identify and select the SNMP developers’ toolkit offering the best value and most cost effective means to accelerate development and realize successful project completion. The right SNMP developers’ toolkit is not necessarily the least expensive. Rather, the right SNMP developers’ toolkit is the one that is capable of providing substantial engineering efficiencies during development and facilitates the delivery of a less encumbered, more profitable product.

Open-source SNMP software was initially created as a reference implementation for interoperability testing with proprietary implementations of the SNMP protocol. Over time, the quality of open-source SNMP developers’ toolkits has improved to a point where there is a suitable match for a variety of OEM development efforts.

Commercial SNMP software often provide a much richer feature set than open-source developers’ toolkits. Also, commercial SNMP software offerings have adjusted to low-end market realities of quality open-source software to a point where there is a low cost or no cost binary commercial version that is often competitive with open-source alternatives.

In either case, open-source or commercial, it is important to have sufficient development expertise with SNMP and MIB technologies to make effective use of the selected SNMP developers’ toolkit. This is the core value provided to your project by the right choice of SNMP consultant.

The next step to gaining a better understanding of the alternatives and trade-offs when identifying and selecting the best choice of commercial or open-source SNMP developers’ toolkit is to contact me with your project requirements and questions.

I am often asked, “What MIB modules are IETF working groups developing?”. MIB modules are defined within the relevant working group and reviewed by a small cadre of IETF MIB doctors prior to publication as an RFC. The following provides a brief outline of and links to the current works-in-progress.

Note that Internet-Drafts are works-in-progress and expire when a subsequent revision is available, or six months after initial publication, whichever occurs first.

I am happy to discuss the usefulness and applicability of the below works-in-progress to your project. Just contact me with your project requirements and ideas.

Operations and Management Area:

• Control And Provisioning of Wireless Access Points (capwap)
  • CAPWAP Protocol Base MIB
    draft-ietf-capwap-base-mib-09 – 10-Feb-10
  • CAPWAP Protocol Binding MIB for IEEE 802.11
    draft-ietf-capwap-802dot11-mib-06 – 2-Jan-10

• Diameter Maintenance and Extensions (dime)
  • Diameter Base Protocol MIB
    draft-ietf-dime-diameter-base-protocol-mib-04 – 14-Jan-10
  • Diameter Credit Control Application MIB
    draft-ietf-dime-diameter-cc-appl-mib-03 – 14-Jan-10

• IP Flow Information Export (ipfix)
  • Definitions of Managed Objects for IP Flow Information Export
    draft-ietf-ipfix-mib-10 – 12-Jan-10
  • Definitions of Managed Objects for Packet Sampling
    draft-ietf-ipfix-psamp-mib-00 – 1-Mar-10

Internet Area:

• Layer 2 Virtual Private Networks (l2vpn)
  • Virtual Private Lan Services (VPLS) Management Information Base
    draft-ietf-l2vpn-vpls-mib-03 – 8-Mar-10

• Network-based Localized Mobility Management (netlmm)
  Proxy Mobile IPv6 Management Information Base
  draft-ietf-netlmm-pmipv6-mib-02 – 22-Jan-10

• Network Time Protocol (ntp)
  • Definitions of Managed Objects for Network Time Protocol Version 4 (NTPv4)
    draft-ietf-ntp-ntpv4-mib-07 – 5-Mar-10

• Pseudowire Emulation Edge to Edge (pwe3)
  • SONET/SDH Circuit Emulation Service Over Packet (CEP) Management Information Base (MIB) Using SMIv2
    draft-ietf-pwe3-cep-mib-12 – 9-Jan-08

• Transparent Interconnection of Lots of Links (trill)
  • Definitions of Managed Objects for RBridges
    draft-ietf-trill-rbridge-mib-00 – 1-Mar-10

Routing Area:

• Bidirectional Forwarding Detection (bfd)
  • BFD Management Information Base
    draft-ietf-bfd-mib-09 – 8-Mar-10

• Common Control and Measurement Plane (ccamp)
  • Traffic Engineering Database Management Information Base in support of MPLS-TE/GMPLS
    draft-ietf-ccamp-gmpls-ted-mib-06 – 26-Oct-09

• Forwarding and Control Element Separation (forces)
  • ForCES MIB
    draft-ietf-forces-mib-10 – 10-Sep-08

• Inter-Domain Routing (idr)
  • Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version
    draft-ietf-idr-bgp4-mibv2-10 – 1-Feb-10
  • Definitions of Textual Conventions for the Management of the Fourth Version of Border Gateway Protocol (BGP-4)
    draft-ietf-idr-bgp4-mibv2-tc-mib-01 – 1-Feb-10

• Mobile Ad-hoc Networks (manet)
  • Definition of Managed Objects for the DYMO Manet Routing Protocol
    draft-ietf-manet-dymo-mib-03 – 25-Oct-09
  • Definition of Managed Objects for the Manet Simplified Multicast Framework Relay Set Process
    draft-ietf-manet-smf-mib-01 – 26-Oct-09
  • Definition of Managed Objects for the Neighborhood Discovery Protocol
    draft-ietf-manet-nhdp-mib-03 – 8-Mar-10
  • Definition of Managed Objects for the MANET Optimized Link State Routing Protocol version 2
    draft-ietf-manet-olsrv2-mib-01 – 8-Nov-09

• Open Shortest Path First IGP (ospf)
  • OSPF Version 2 MIB for Multi-Topology (MT) Routing
    draft-ietf-ospf-mt-mib-04 – 15-Dec-09

• Path Computation Element (pce)
  • Definitions of Managed Objects for Path Computation Element Discovery
    draft-ietf-pce-disc-mib-04 – 26-Oct-09
  • Definitions of Textual Conventions for Path Computation Element
    draft-ietf-pce-tc-mib-05 – 26-Oct-09
  • PCE communication protocol(PCEP) Management Information Base
    draft-ietf-pce-pcep-mib-01 – 8-Mar-10

• Virtual Router Redundancy Protocol (vrrp)
  • Definitions of Managed Objects for the VRRP over IPv4 and IPv6
    draft-ietf-vrrp-unified-mib-07 – 2-Feb-10

Individual Submissions:

• various working groups
  • The SatLabs Group DVB-RCS MIB
    draft-combes-ipdvb-mib-rcs-08 – 22-Oct-09
  • SNMP Context Mapping MIB
    draft-kkoushik-snmp-context-map-mib-02 – 8-Mar-10
  • Definitions of Managed Objects for lock via network management protocols
    draft-meng-fan-lock-mib-02 – 24-Oct-09
  • 6LoWPAN Management Information Base
    draft-daniel-6lowpan-mib-01 – 26-Oct-09
  • Definition of Managed Objects for Performance Reporting
    draft-cole-manet-report-mib-02 – 2-Mar-10
  • Backup and Restore MIBs
    draft-shimin-opsawg-snmp-backuprestore-mib-01 – 7-Oct-09
  • Power Consumption MIB for IP forwarding devices
    draft-teraoka-powerconsumption-mib-01 – 16-Feb-10
  • MIB for Energy, Efficiency, Throughput and Carbon Emission
    draft-sreek-powerconsumption-mib-01 – 29-Jan-10
  • Energy Monitoring MIB
    draft-claise-energy-monitoring-mib-02 – 8-Mar-10
  • Definiton of Managed Objects for Energy Management
    draft-quittek-power-mib-00 – 3-Feb-10
  • ANCP MIB module for NAS
    draft-rohit-ancp-nas-mib-00 – 25-Feb-10
  • Management Information Base for the Group Domain of Interpretation
    draft-kamarthy-gdoi-mib-00 – 26-Feb-10

Recently Published RFCs:

• Definitions of Managed Objects for Mapping SYSLOG Messages to Simple Network Management Protocol (SNMP) Notifications
  RFC5676 – October 2009
• Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
  RFC5675 – October 2009
• Alarms in Syslog
  RFC5674 – October 2009
• Textual Conventions for Syslog Management
  RFC5427 – March 2009
• Transmission of Syslog Messages over UDP
  RFC5426 – March 2009
• Transport Layer Security (TLS) Transport Mapping for Syslog
  RFC5425 – March 2009
• The Syslog Protocol
  RFC5424 – March 2009
• Ethernet Pseudowire (PW) Management Information Base (MIB)
  RFC5603 – July 2009
• Management Information Base for OSPFv3
  RFC5643 – August 2009

I am often asked, “What Internet-Drafts on network and services management are IETF working groups developing?”. The following provides a brief outline of and links to the current works-in-progress.

Note that Internet-Drafts are works-in-progress and expire when a subsequent revision is available, or six months after initial publication, whichever occurs first.

I am happy to discuss the usefulness and applicability of the below works-in-progress to your project. Just contact me with your project requirements and ideas.

Within the Security Area:

• Integrated Security Model for SNMP Working Group (isms)
  
  The goal of the ISMS working group is developing a new security model for SNMP that integrates with widely deployed user and key management systems, as a supplement to the USM security model. Current Internet-Drafts include:
  • Transport Layer Security (TLS) Transport Model for SNMP
    draft-ietf-isms-dtls-tm-09 – 6-Mar-10
  • Extensions to the View-based Access Control Model for use with RADIUS
    draft-ietf-isms-radius-vacm-05 – 6-Mar-10

Within the Operations and Management Area:

• Network Configuration Working Group (netconf)
  
  The NETCONF Working Group is chartered to produce a protocol suitable for network configuration. The NETCONF protocol is using XML for data encoding purposes, because XML is a widely deployed standard which is supported by a large number of applications. Current Internet-Drafts include:
  • With-defaults capability for NETCONF
    draft-ietf-netconf-with-defaults-05 – 5-Mar-10
  • Network Configuration Protocol (NETCONF)
    draft-ietf-netconf-4741bis-02 – 4-Feb-10
  • Using the NETCONF Configuration Protocol over Secure Shell (SSH)
    draft-ietf-netconf-rfc4742bis-00 – 28-Dec-09

  Current RFCs include:

  • Partial Lock Remote Procedure Call (RPC) for NETCONF
    RFC5717 – December 2009
  • NETCONF over Transport Layer Security (TLS)
    RFC5539 – May 2009
  • Experience of Implementing NETCONF over SOAP
    RFC5381 – October 2008
  • NETCONF Event Notifications
    RFC5277 – July 2008
  • Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)
    RFC4744 – December 2006
  • Using NETCONF over the Simple Object Access Protocol (SOAP)
    RFC4743 – December 2006
  • Using the NETCONF Configuration Protocol over Secure Shell (SSH)
    RFC4742 – December 2006
  • NETCONF Configuration Protocol
    RFC4741 – December 2006

• NETCONF Data Modeling Language Working Group (netmod)
  
  The NETMOD Working Group will define a “human-friendly” modeling language defining the semantics of operational data, configuration data, notifications, and operations. Current Internet-Drafts include:
  • YANG – A data modeling language for NETCONF
    draft-ietf-netmod-yang-11 – 24-Feb-10
  • Mapping YANG to Document Schema Definition Languages and Validating NETCONF Content
    draft-ietf-netmod-dsdl-map-05 – 2-Mar-10
  • An NETCONF- and NETMOD-based Architecture for Network Management
    draft-ietf-netmod-arch-04 – 8-Mar-10
  • Common YANG Data Types
    draft-ietf-netmod-yang-types-07 – 24-Feb-10
  • Guidelines for Authors and Reviewers of YANG Data Model Documents
    draft-ietf-netmod-yang-usage-03 – 14-Jan-10

• Operations and Management Area Working Group (opsawg)
  
  The Operations and Management Area receives occasional proposals for the development and publication of RFCs dealing with operational and management topics that are not in scope of an existing working group and do not justify the formation of a new working group. Current Internet-Drafts include:
  • Expressing SNMP SMI Datatypes in XML Schema Definition Language
    draft-ietf-opsawg-smi-datatypes-in-xsd-06 – 1-Mar-10
  • “The OAM Acronym Soup”
    draft-ietf-opsawg-mpls-tp-oam-def-03” – 11-Feb-10
  • An Overview of Operations, Administration, and Maintenance (OAM) Mechanisms
    draft-ietf-opsawg-oam-overview-00” – 17-Jan-10

  Current RFCs include:

  • Mapping Simple Network Management Protocol (SNMP) Notifications to SYSLOG Messages
    RFC5675 – October 2009
  • Alarms in Syslog
    RFC5674 – October 2009
  • Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions
    RFC5706 – November 2009
  • Simple Network Management Protocol (SNMP) Traffic Measurements and Trace Exchange Formats
    RFC5345 – October 2008
  • Simple Network Management Protocol (SNMP) Context EngineID Discovery
    RFC5343 – September 2008 (Updates RFC3411 )

Individual Submissions:

• various working groups
  • Robust Configuration Management within NETCONF
    draft-cole-netconf-robust-config-02 – 2-Mar-10
  • SNMP optimizations for 6LoWPAN
    draft-hamid-6lowpan-snmp-optimizations-02 – 20-Oct-09
  • Conversion of MIB to XSD for NETCONF
    draft-xiao-conversion-dm-02 – 11-Sep-09
  • Guidelines for Authors and Reviewers of MIB Documents
    draft-presuhn-opsawg-rfc4181bis-03 – 29-Sep-09
  • Network Configuration Protocol Access Control Model
    draft-bierman-netconf-access-control-01 – 25-Feb-10
  • Extending YANG with Language Abstractions
    draft-linowski-netmod-yang-abstract-02 – 8-Mar-10
  • Virtual Network Management Information Model
    draft-okita-ops-vnetmodel-02 – 8-Mar-10

 
Management Information Base (MIB) modules are designed within the applicable protocol working group and is the topic of another article.

I am happy to discuss the usefulness and applicability of the above works-in-progress to your project. Just contact me with your project parameters and ideas.

Versions of the SNMP prior to third version (SNMPv3) did not include adequate security. Any sufficiently motivated individual with physical access to a shared network link and a protocol sniffer had the ability to capture clear text messages exchanged between a manager application and its agents. Once captured, it was simply a matter of extracting community strings and agent addresses of interest in order to usurp the role of the manager application, possibly hijacking and re-configuring network devices along the way.

The design of SNMPv3 included authentication and privacy (encryption) mechanisms for the protocol. By incorporating these mechanisms, SNMPv3 became self sufficient with no need of any other network services for the secure transmission of SNMP messages. After all, network operators need their network management protocol to be functional even when major portions of the network and its services are impaired.

Three security levels are defined for SNMPv3, in increasing degree of security as follow:

• noAuthNoPriv – essentially clear text messages providing backwards compatibility with earlier versions of the SNMP
• authNoPriv – authenticated messages (SHA1 or MD5 hash), but messages are still transmitted in clear text
• authPriv – authenticated messages with the scoped PDU portion of message encrypted (DES or AES)

For manager applications that only require their agents to verify the authenticity of SNMP message exchanges, the authNoPriv security level is sufficient. This security level offers adequate protection for SNMP message exchanges that do not include sensitive data.

For manager applications that require their agents to both verify the authenticity of SNMP message exchanges and to provide privacy (encryption) of sensitive data contained within the scoped PDU portion of the SNMP message, the authPriv security level must be used. Since the DES encryption cipher is considered cracked, an AES encryption cipher of sufficient length should be used.

However, it is important to avoid using weak authentication or privacy pass phrases. Even when an SNMP manager application uses the authPriv security level with the AES cipher, you can jeopardize secure SNMPv3 message transmissions. In better deployments, the SNMP configuration and applications work together with the proper ciphers and strong pass phrases to ensure secure SNMPv3 message transmission and I am happy to show you just how easy it is to get this right.

In highly secure environments snmpEngineID values should also be protected by using a discovery mechanism together with a security model that avoids exchanging cleartext SNMP messages on network links.

The next step towards using SNMPv3 for secure transmission of SNMP messages is to contact me with your project requirements and questions.

When a software project involves the design of Enterprise MIB modules, there is a tried and true approach to reducing associated cost and risk factors. This valuable design approach leverages the practical wisdom and lessons-learned from the development of more than 250 IETF standards-track MIB modules.

The IETF Operations And Management (OAM) Area directorate collected and posted helpful information related to MIB design on the following topics:

• A boilerplate for MIB documents
• Suggested guidelines for MIB security sections
• A list of generic and common textual conventions
• Readily available MIB review and validation tools

These topics and others are published as a “Best Current Practice” in RFC 4181, “Guidelines for MIB Documents”. RFC 4181 describe a better approach towards the design of MIB modules, but does not address the single largest cause of rework and redesign. This critical step, is the creation of an Information Model, as cited by the Network Management Research Group (NMRG).

Within each IETF standards-track MIB module there exists a tacit, de-facto Information Model. This NMRG view describes how Information Models can represent different abstraction levels and provides a set of reverse-engineered Information models for IETF published MIB modules. This NMRG point of view is described in RFC 3444, “On the Difference between Information Models and Data Models”. Since publication of RFC 3444, IETF working groups now define an Information Model before designing their MIB modules.

My consulting clients who choose to first define an Information Model regard this initial step as a great value for reasons that include the following:

• Efficient knowledge transfer from domain subject experts
• Easy to understand graphic format
• Identifies major system components, their relationships and multiplicity
• Effectively specifies the SNMP INDEX for each system component
• Provides a means to express and analysis use cases

And the best value yielded by the small amount of time and effort spent on first defining an Information Model is the significant reduction in latter development stage risk involving re-design of portions of their Enterprise MIB modules.

It is simply easier to identify and correct logic on a single page or screen image than it is to modify definitions and descriptive text across the hundreds of pages comprising a set of enterprise MIB modules. The simple fact that the need for re-design is often first detected during the latter phases of implementing MIB modules in an SNMP Agent or SNMP Manager application serves to compound the value provided by the initial definition of an Information Model.

Certainly the design approach of information modeling before Enterprise MIB design reduces cost and reduces risk that can adversely impact project budget and schedule.

The next step in taking advantage of this valuable design approach is to contact me with your project requirements and questions.