SNMP is a UDP-based protocol developed to give devices connected on a network a consistent and reliable way to share information. HCC provides a high quality SNMPv2 and SNMPv3 implementation to provide embedded devices with secure and reliable network management capability. Using SNMP IT managers can monitor device operation, usage, detect network faults or inappropriate access and configure remote devices. SNMP is designed to be robust and can be used on a large number of network devices with minimal impact on the managed nodes. It has low transport overheads and keeps working even when other applications fail.

MIB Compiler

This translates ASN.1 MIB specifications into C language MIB definitions, stub method templates, header declarations and OID/name documentation files. After including the MIB Compiler’s output in your own project, all that is left to do is instrument the low-level “stub functions” with your device specific details. HCC’s SNMP does the rest, ensuring that only valid commands (GET, SET, etc) reach your system, and only as authorized by the MIB. The MIB Compiler also parses and validates the MIB for erroneous conditions (duplicate values, overlapping ranges, improper OID hierarchy) and can generate validation information, which is then used by the SNMP Engine to validate objects at run time.

Features
  • Conforms to the HCC Advanced Embedded Framework.
  • Complies with HCC’s MISRA-compliant TCP/IP stack.
  • Designed for integration with both RTOS and non-RTOS based systems.
  • Can be integrated with HCC’s network stack using standard UDP interface
  • SNMP agent fully supporting v1, v2c, v3
  • SNMP manager capability to query remote agents
  • SNMP implementation (RFC 1157) supports SNMPv2c (RFC 1901) and SNMPv3 (RFC 3410).
  • A MIB compiler is included. The MIB implementation is compliant with RFC 3413 and RFC 3418.
  • View-based Access Control Model (VACM) and the VACM Management Information Base (MIB) are compliant with RFC 3415.
  • User-based Security Model (USM) is compliant with RFC 3414.
  • Authentication using Message Digest 5 (MD5) and the Secure Hash Algorithm 1 (SHA-1).
  • Data encryption using the Triple Data Encryption Standard (3DES).