Applies To:

Show Versions Show Versions

sol13947: Importing the BIG-IP MIB file 'F5-BIGIP-COMMON-MIB.txt' may result in an error
Known IssueKnown Issue

Original Publication Date: 10/18/2012
Updated Date: 01/23/2013

Description

When importing the F5-BIGIP-COMMON MIB file into an external MIB tool, it may result in an error.

The BIG-IP MIB file named F5-BIGIP-COMMON-MIB.txt contains trailing commas in the IMPORTS section which may prevent some external MIB tools from importing it.

Impact

The import may fail and result in an error on the external MIB tool.

Symptoms

As a result of this issue, you may encounter the following symptoms:

  • The import of the affected MIB file may result in an error and it may not be imported into the external MIB tool.
  • The external MIB tool may display an error message about the parse error for the affected MIB file.

Status

F5 Product Development has assigned ID 392860 to this issue, and has confirmed that this issue exists in the products listed in the Applies To box. For information about releases or hotfixes that resolve this issue, refer to the following table:

Type of Fix
Versions Fixed
Related Articles
Release 11.3.0 SOL2200: Most recent versions of F5 software
Hotfix None None

Workaround

To work around this issue, you can remove the trailing commas at the end of lines in the IMPORTS section of the affected MIB file. To do so, perform the following procedure:

Impact of workaround: None

  1. Download the F5-BIGIP-COMMON-MIB.txt file to your local system.

    Note: You cannot edit the F5-BIGIP-COMMON-MIB.txt file directly on the BIG-IP system as the file is located on a read-only file system.

  2. Access the text editor of your choice to edit the F5-BIGIP-COMMON-MIB.txt file.
  3. Remove the trailing comma (,) from the end of any line in the IMPORTS section of the file.

    For example, before modification, the IMPORTS section may appear as follows:

      IMPORTS
          MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
          enterprises, Integer32
              FROM SNMPv2-SMI

          TEXTUAL-CONVENTION, DisplayString
              FROM SNMPv2-TC
      
          MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP,
               FROM SNMPv2-CONF;

        --================================================================

    After modification, the IMPORTS section may appear as follows:

      IMPORTS
          MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE
          enterprises, Integer32
              FROM SNMPv2-SMI

          TEXTUAL-CONVENTION, DisplayString
              FROM SNMPv2-TC

          MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
              FROM SNMPv2-CONF;

      --================================================================

  4. Save the modification and exit the text editor.
  5. Import the MIB file on the external MIB tool again.

Supplemental Information

Was this resource helpful in solving your issue?




NOTE: Please do not provide personal information.



Incorrect answer. Please try again: Please enter the words to the right: Please enter the numbers you hear:

Additional Comments (optional)