SNMP-SMI to IDL Translator

• Abstract
• Systems/Software Requirements

• Download the SNMP-SMI to IDL translator C++ source code
• Installtion instruction for SNMP-SMI to IDL translator source
• Download the SNMP-SMI to IDL translator binary only
• Installtion instruction for SNMP-SMI to IDL translator binary
• SNMP-SMI to IDL online coneversion toolkit is now part of CORBA/SNMP Gateway runtime distribution .
• Installtion instruction for SNMP-SMI to IDL coneversion toolkit
• Description of the WEB-based online SMI to IDL conversion

• Download the Base IDL files for CORBA/SNMP Gateway
• Extraction instruction for base IDL files
• Command Line Usage of the SMI-->IDL translator

• View already converted IDL files in HTML

Abstract

WEB server based SNMP-SMI to CORBA-IDL conversion toolkit is JWS/Servlet based tool to convert an uploaded MIB file to IDL. From now onwards we will call this toolkit as Mib2Idl translator.
An user at a remote site uses a form to upload a MIB file and specify conversion option and the cgi-bin script assciated with this form is invoked to return a set of HTML links to various generated files.

The core of this Mib2Idl conversion toolkit is the ASN.1/SNMP-SMI to CORBA-IDL translator. The smi2idl translator converts SMI based SNMP MIB information module and generates IDL interafces and types based on the JIDM specification translation document. The smi2idl translator can handle MIB infromation modules based on both SNMPv1 and SNMPv2 SMIs.

The smi2idl translator takes SNMP MIB files as input and generates two output files for each input MIB file:
<MIB_MODULE_NAME>.idl and <MIB_MODULE_NAME>.oid,
where MIB_MODULE_NAME is name of the IDL module for the input SNMP information module. The <MIB_MODULE_NAME>.idl contains the IDL interfaces and types generated from the SMI macros and ASN.1 types in the input MIB module. The <MIB_MODULE_NAME>.oid contains the mapping of IDL scoped name of the interfaces/attributes to the corresponding ASN.1 OID. By default both ouput files are generated in the same directory as the MIB file. One use the compiler option to specifiy a different destination diretory for the generated IDL and OID files.

The Mib2Idl toolkit extends the smi2idl translator and provide conversion option to generate HTML files from generated IDL files, update the Interface Repository of the CORBA/SNMP gateway run-time and generate signed jar file of Java stubs generated based on the IDL->Java mapping. The HTML files are generated from the IDL files using the IDL Documentation Generator (idldoc 1.1) developed at Sandia National Laboratories, Livermore, CA. The Mib2Idl toolkit can be used in two ways: command line and web-server based on-line.

The SMI-->IDL translator is compliant with SNMP part of X/Open-NMF sponsored "Inter-Domain Management: Specification Translation" document and supports MIBs defined based on the SNMPv1 and SNMPv2 SMIs.
ASN.1/SMI-->IDL translator is developed by Helena Sarin of Lucent Technologies. For more information or comments about the compiler, please contact Helena Sarin.

(Note:
The smi2idl translator does not support mapping of any arbitrary ASN.1 module to IDL yet. We plan to support full ASN.1-->IDL mapping very soon.
The smi2idl translator does not support GDMO-->IDL mapping and we do not have any plan to do it. )

Systems/Software Requirements:

The smi2idl translator currently works only on SPARC/Solaris 2.5.x or up.

Systems/Software Requirements for the smi2idl conversion toolkit:

• SPARC/Solaris 2.5.x or up
• SUN C++ compiler and Tools.h++ library (for SMI to IDL translator source)
  SUN's Forte workshop for C++ can be downloaded for free trial.
• Any CORBA 2.x compliant IDL compiler
  (Optional, required if you want to update the Interface Repository)

Systems/Software Requirements for the Mib2Idl conversion toolkit:

• SPARC/Solaris 2.5.x or up
• SUN C++ compiler and Tools.h++ library (for SMI to IDL translator source)
  SUN's Forte workshop for C++ can be downloaded for free trial.
• Java Web Server with support for servlet/JSP
• Any CORBA 2.x compliant IDL compiler
  (Optional, required if you want to update the Interface Repository)
• IDL-->HTML converter ( we use idldoc);
• JDK 1.1.6 or up and any CORBA 2.3 compliant IDL-->Java compiler
  (optional; required if you want to package java-stubs as signed jar files).
  

Note: The IDL files generated by the compiler are tested for correctness with Orbix, Visibroker, JavaIDL, and NEO IDL compilers.

If you do not use the default IDL compilers used in the tool-kit, then you have to edit the c-shell scripts supplied with the toolkit to modify the include path, library path etc.

The SMI-->IDL translator has following limitations:

• This smi2idl translator is based on the preliminary version of the JIDM 's "Inter-Domain Management: Specification Translation" document.
  The smi2idl translator does not conform to most recent specification translation used in the CORBA/SNMP interworking specification submitted in response to CORBA/TMN Interworking RFP from OMG. The specification translation mentioned in CORBA/SNMP interworking submission is based on a revised version of the preliminary specification due out very soon from Opengroup.

• it does not understand OID consisting of more than two items;
  The compiler does not understand following syntax for OID:
  org OBJECT IDENTIFIER ::= { iso(1) 3 }
  internet OBJECT IDENTIFIER ::= { iso org(3) dod(6) 1 }
  but it understands
  org OBJECT IDENTIFIER ::= { iso 3 }
  dod OBJECT IDENTIFIER ::= { org 6 }
  internet OBJECT IDENTIFIER ::= { dod 1 }
  

• The compiler cannot handle INTEGER with SIZE clause in the SYNTAX of the OBJECT-TYPE or Textual-Convention macros.

• The compiler can handle texts before and after the BEGIN/END statements of SMI modules. The compiler strips off RFC header/footer if the the standard delimiters are used. If the standard delimiters are not used, the behaviour is unknown.

• In order to convert a specific MIB file to IDL, you have to upload and convert all the imported MIB files in the target MIB file. In a future revision, we will provide option to upload more than one MIB files at a time.

Instructions for Installing Mib2Idl Conversion Toolkit

Installation Instruction for SMI-->IDL Translator C++ Source

• Uncompress and extract the files from smi2idl.tar.Z as follows:
  zcat smi2idl.tar.Z | tar xvf -
  

• extracted code will placed under the directory SMI2IDL
• change directory to .../SMI2IDL/smi
• edit the Makefile to specify the path for C++ compiler
• invoke "make all" to create the smi2idl executable

Installation Instruction for SMI-->IDL Translator Binary Only

Save the downloaded file as smi2idl.Z in a separate directory.

Uncompress the file using "uncompress smi2idl.Z".

Please make sure that the uncompressed smi2idl file is executable.
The smi2idl translator works only on SPARC/Solaris machines.

JIDM Defined Base IDL Files for CORBA/SNMP Gateway

Save the compressed-tar file as CorbaSnmp_IDL.tar.Z.

Uncompress and extract the IDL files in a separate directory using:
"zcat CorbaSnmp_IDL.tar.Z | tar xvf - " command.

You may want to replace the CORBA services related IDL files under COSS directory with the corresponding files of your own ORB. The IDL files under COSS directory are CORBA 2.0 compliant. You have to only modify the include statements in various COS-specific IDL files or replace the files with links to the corresponding ORB specific files.

Command Line Usage of the SMI-->IDL translator

smi2idl [ option ] ... file

the following options may be used:
-I<path> [-I<path> ..] Specifies directories where common Mib files are located
-D     Specifies the directory where output IDL files are placed
-P      Generate pragma ID statement (deprecated)
-N      Output IDL files for every imported module
-U<path> Specifies directory where user Mibs reside,
        including the file for which IDL file will be produced

• smi2idl -I. -D /tmp/IDL RFC1213_MIB
• smi2idl -I. -P RFC1213_MIB

Copyright © 2000 Lucent Technologies. All rights reserved.