MIB

The MIB module files that ship with TCP/IP, or are available for the OSA Direct SNMP subagent, are files that may need to be copied to certain locations depending on the network management application being used. Normally, the network management applications only need these files if they provide a MIB browser. The MIB browser reads in the MIB module source and parses the definitions. By doing so the MIB browser is able to understand all the data by name, OID, and type. Some browsers then display the MIB objects by name and allow customers to execute SNMP requests against them. For instance, using a MIB browser, the OSA port number is normally displayed as 1.3.6.1.4.1.2.6.188.1.1.1.1.nn = 0x40. However, when using the MIB with the MIB browser, the OSA port number is displayed as ibmOSAExpChannelNumber.nn = 0x40.

If you require the OSA Direct Express MIB, the one that matches your servers MCL can be installed by either:
  • Selecting Advanced Functions on the HMC
  • Downloading from the Resource Link home page.
    • After logging in, select Library
    • Under "Library shortcuts" on the right side of the screen, select Open System Adapter (OSA) Library
    • Select "OSA-Express SNMP Direct MIB Module" for a description, or click on "TXT" for the module
    • Save the MIB file to the location required by your network management application

See your network application product information for management commands and procedures.

Only the OSA MIBS.DATA file is used by the z/OS UNIX snmp command. This performs a similar function that the MIB browser provides with the OSA MIB. It enables the user of the z/OS UNIX command to use the names of the MIB objects with the z/OS command, instead of just using their Object Identifier values (OID values). For more information, see the SNMP chapters of the z/OS Communications Server: IP Configuration Guide and z/OS Communications Server: IP Configuration Reference for more information on how to use this file to configure SNMP support.