binding error to new mib file

[terry]

Hello,

I have a question about binding error.

When I binding a new MIB file, I met the bellow error.

..\var\mibs\WS-CC-RF-MIB.txt: ERROR 003: Parser error - syntax error, unexpected
 COMMA_SYM, expecting RIGHT_BRACE_SYM in line 1245

The line 1245 of mib file is as the belows;
      -- 1.3.6.1.4.1.388.14.3.2.1.11.5.1.12
      wsCcRfRadioBasicRates OBJECT-TYPE
        SYNTAX TransmitRate
        MAX-ACCESS read-create
        STATUS current
        DESCRIPTION
            "List of basic rates for the radio."
        DEFVAL { {rate1Mb}, {rate2Mb}, {rate5pt5Mb}, {rate11Mb} }  <== Here is the line 1245
        ::= { wsCcRfRadioEntry 12 }

And, TransmotRate is defined as the belows;

      TransmitRate ::= BITS
        {
        rate1Mb(0),
        rate2Mb(1),
        rate5pt5Mb(2),
        rate6Mb(3),
        rate9Mb(4),
        rate11Mb(5),
        rate12Mb(6),
        rate18Mb(7),
        rate22Mb(,
        rate24Mb(9),
        rate36Mb(10),
        rate48Mb(11),
        rate54Mb(12)
        }

In the RFC1902, the value of the DEFVAL clause can define as the belows;

    ObjectSyntax      DEFVAL clause
    ----------------  ------------
    Integer32          DEFVAL { 1 }
                        -- same for Gauge32, TimeTicks, Unsigned32
    INTEGER            DEFVAL { valid } -- enumerated value
    OCTET STRING      DEFVAL { 'ffffffffffff'H }
    OBJECT IDENTIFIER  DEFVAL { sysDescr }
    BITS              DEFVAL { { primary, secondary } }  <=== Here
                        -- enumerated values that are set
    IpAddress          DEFVAL { 'c0210415'H } -- 192.33.4.21

I want to know what's wrong?

Please help me as soon as possible.
I attach the mib file.

Best Regards,

• Terry

---

WS-CC-RF-MIB.txt

[victor]

Hello!

Looks like a bug in MIB compiler. As a workaround, just comment out or delete entire DEFVAL line - it is not used by compiler anyway.

Best regards,
Victor

[terry]

Thank you very much.

I comment out those related lines.
So, I can bind.

Now, I want to know the schedule to fix the bug.

Best Regards,

• Terry

[victor]

Hello!

It's fixed in 0.2.21.

Best regards,
Victor