mosy Command

Purpose

Converts the ASN.1 definitions of Structure and Identification of Management Information (SMI) and Management Information Base (MIB) modules into objects definition files for the snmpinfo command.

Syntax

mosy -o output_defs_file [ -s ] inputfile ...

mosy -x output_desc_file [ -o output_defs_file] [ -s ] inputfile ...

mosy -c output_c_file [ -x output_desc_file] [ -o output_defs_file] [ -s ] inputfile ...

Description

The mosy command reads in the ASN.1 definitions of SMI and MIB modules and produces objects definition files in specific formats. The resulting objects definition files are used by the snmpinfo command.

The inputfile parameter files are required to be in the smi.my or mibII.my format. Sample files are the /usr/samples/snmpd/smi.my and /usr/samples/snmpd/mibII.my files. See the smi.my and the mibII.my files for information on the required format of the file specified by the inputfile parameter.

The mosy -o command is used to create the objects definition file specified by the output_defs_file parameter for the snmpinfo command. This file is normally the /etc/mib.defs file.

The objects definition file can be created with one pass of the mosy compiler if the smi.my and mibII.my files are both specified as inputfile parameters. The smi.my file must precede the mibII.my file on the command line.

The mosy -o command can also be used to create subfiles. If subfiles are created separately from the SMI and MIB modules, you must concatenate the various subfiles before the snmpinfo command can successfully use the resultant mib.defs file. The SMI subfile must be at the top of the final objects definition file.

You can add objects definitions for experimental MIB modules or private-enterprise-specific MIB modules to the /etc/mib.defs file, but you must first obtain the private MIB module from the vendor that supports those MIB variables.

To update the /etc/mib.defs file to incorporate a vendor's private or experimental MIB objects definitions, create a subfile and then concatenate that subfile to the existing MIB II /etc/mib.defs file. See example 3.

Flags

Parameters

Examples

1. To create an objects definition file for use by the snmpinfo command with one pass of the mosy command, enter:

   mosy -o /etc/mib.defs /usr/samples/snmpd/smi.my
   /usr/samples/snmpd/mibII.my

   In this example, /usr/samples/snmpd/smi.my and /usr/samples/snmpd/mibII.my are both specified as input files and the resultant objects definition file is the /etc/mib.defs file.
2. To create objects definition subfiles, enter:

   mosy -o /tmp/smi.obj /usr/samples/snmpd/smi.my
   mosy -o /tmp/mibII.obj /usr/samples/snmpd/mibII.my
   cat /tmp/smi.obj /tmp/mibII.obj > /etc/mib.defs

   In this example, the first command creates an SMI objects file, /tmp/smi.obj, from the /usr/samples/snmpd/smi.my file. The second command creates the MIB objects definition file, /tmp/mibII.obj, from the /usr/samples/snmpd/mibII.my file. The final command concatenates the subfiles, placing the SMI objects definition file first in the resultant /etc/mib.defs file.
3. To add private enterprise specific MIB objects definitions to an existing /etc/mib.defs file for use by the snmpinfo command, enter:

   mosy -o /tmp/private.obj /tmp/private.my
   cat /etc/mib.defs /tmp/private.obj > /tmp/mib.defs
   mv /tmp/mib.defs /etc/mib.defs

   In this example, the first command creates the /tmp/private.obj objects definition file. The second command concatenates the /etc/mib.defs MIB objects definition file with the /tmp/private.obj private MIB file and places the concatenated contents into the /tmp/mib.defs temporary MIB objects definition file. The final command moves the temporary file to the /etc/mib.defs file for use by the snmpinfo command.
4. To create a description file in /tmp/smi.desc, a C code file named /tmp/smi.c, and a Management Information Base (MIB) definition file named /tmp/smi.defs, enter:

    mosy  -x /tmp/smi.desc -c /tmp/smi.c -o /tmp/smi.defs -s smi.my mibII.my

Files