Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Flatly)
  • No Skin
Collapse
Brand Logo

NetXMS Forum

  1. Home
  2. Support (Russian)
  3. Компиляция mib-файлов

Компиляция mib-файлов

Scheduled Pinned Locked Moved Support (Russian)
7 Posts 2 Posters 25.4k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I
    I
    Mikhail V. Platonov
    wrote on last edited by
    #1

    День добрый.
    Собираюсь использовать NetXMS для сбора статистики с нашего почтового сервера. На машине крутится CommuniGatePro, у него есть mib-файл (приложил). Команда nxmibc -d . -z в директории mib'ов выдает:

    ./CGatePro-MIB.txt: ERROR 003: Parser error - syntax error, unexpected MODULE_IDENTITY_SYM, expecting OBJECT_TYPE_SYM in line 13"
    

    Я сравнивал построение mib-файлов, никаких особенных различий не увидел, синтаксис везде одинаковый.
    Скажите, в чем может быть проблема? В самом mib'е, в компиляторе nxmibc? Может есть какая-нибудь документация толковая по mib'ам?


    CGatePro-MIB.txt

    1 Reply Last reply
    0
    • W
      W
      weec
      wrote on last edited by
      #2

      есть ли другие версии MIB для CommuniGatePro?

      1 Reply Last reply
      0
      • I
        I
        Mikhail V. Platonov
        wrote on last edited by
        #3

        К сожалению, нет. У них на протяжение многих версий один и тот же mib.
        Я уже пробовал пересобрать nxmibc (https://www.netxms.org/forum/index.php/topic,121.0.html), но не помогло. Теперь пишет только проще…

        ./CGatePro-MIB.txt: ERROR 003: Parser error - syntax error in line 13
        
        1 Reply Last reply
        0
        • W
          W
          weec
          wrote on last edited by
          #4

          для вывода более подробных логов при проверке синтаксиса думаю стоит попробовать это (snmp mib syntax checker)
          http://www.ops.ietf.org/mib-review-tools.html
          http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/

          вот лог проверки синтаксиса Вашего файла:

          mibs/CGatePro-MIB:13: [2] {bad-identifier-case} `StalkerMIB' should start with a lower case letter
          mibs/CGatePro-MIB:13: [1] {internal-other} syntax error, unexpected MODULE_IDENTITY, expecting OBJECT
          mibs/CGatePro-MIB:32: [5] {internal-flushing} warning: flushing recent incorrect declaration, see previous error(s)
          mibs/CGatePro-MIB:35: [2] {bad-identifier-case} `CommuniGatePro' should start with a lower case letter
          mibs/CGatePro-MIB:36: [2] {bad-identifier-case} `StalkerMIB' should start with a lower case letter
          mibs/CGatePro-MIB:39: [2] {bad-identifier-case} `CGateProObject' should start with a lower case letter
          mibs/CGatePro-MIB:40: [2] {bad-identifier-case} `CommuniGatePro' should start with a lower case letter
          mibs/CGatePro-MIB:43: [2] {bad-identifier-case} `CGateProModule' should start with a lower case letter
          mibs/CGatePro-MIB:44: [2] {bad-identifier-case} `CGateProObject' should start with a lower case letter
          mibs/CGatePro-MIB:48: [2] {bad-identifier-case} `CGateProModule' should start with a lower case letter
          mibs/CGatePro-MIB:57: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2
          mibs/CGatePro-MIB:57: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:65: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2
          mibs/CGatePro-MIB:65: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:73: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:81: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:89: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:97: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:105: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:113: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:121: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:129: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:137: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:145: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:153: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:161: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:173: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2
          mibs/CGatePro-MIB:173: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:181: [5] {integer-misuse} warning: use Integer32 instead of INTEGER in SMIv2
          mibs/CGatePro-MIB:181: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
          mibs/CGatePro-MIB:189: [2] {access-in-smiv2} ACCESS is SMIv1 style, use MAX-ACCESS in SMIv2 MIBs instead
                                                ***
          

          после такого, стоит отписать в службу тех.поддержки CGatePro

          1 Reply Last reply
          0
          • W
            W
            weec
            wrote on last edited by
            #5

            хм, зашел на сайт проекта, глянул журнал изменений
            нашел вот это

            http://lists.communigate.com/Lists/CGatePro/Message/93043.html
            History:

            5.2c1 23-Oct-07 5.2c1 23-Oct-2007 Valid Core License Keys: issued after 01-Sep-2006.

            * ROUTER: all records are "NORELAY" by default now.
             PLEASE CHECK YOUR EXISTING Router Records!.
            * MAILBOX: Synchronization snapshots are implemented.
            * AIRSYNC: the Windows Mobile Email/Calendaring/Contacts "ActiveSync"
             synchronization protocol is implemented.
            * XIMSS: HTTP binding is implemented.
            * Parlay: the Parlay X "Third Party Call Control" and "Call Handling"
             interfaces are implemented.
            * WebApp: CG/PL Web Applications are supported now.
            * MEDIA: inband DTMF detection is implemented.
            * MEDIA: "play position" operations are implemented.
            * Admin: the Account Type Licensing concept is implemented.
            * Admin: the Class of Service mechanism is implemented for Account Settings.
            * Admin: the AirSync Service setting is implemented.
            * Admin: the Temp Blocked Addresses setting is moved from the SMTP Settings
             to Network->Blacklisted Settings.
            * Admin: the Alt RADIUS Password and Alt SIP Password Account settings
             become standard ones.
            * Admin: the Client IP Addresses Domain-level settings are implemented.
            * Admin: the CanControlCluster Monitor admin right is implemented.
            * Foundation: now XML parser supports complex DOCTYPEs, non-UTF-8 charsets,
             and processes ENTITY data.
            * Foundation: the SHA256 digest algorithm is implemented.
            * XIMSS, XMPP: message delivery failure is reported back to the client now.
            * SNMP: MIB elements renamed (they start with lowercase letters) to confirm
             to SNMP naming recommendations.

            попробуйте обновить CGatePro

            1 Reply Last reply
            0
            • I
              I
              Mikhail V. Platonov
              wrote on last edited by
              #6

              Спасибо за разъяснения, буду править mib вручную, обновиться так просто не получится, у нас лицензии на это не хватит 😉
              Большое спасибо.

              1 Reply Last reply
              0
              • W
                W
                weec
                wrote on last edited by
                #7

                попробуйте Community Edition http://www.communigate.com/community/default.html
                http://www.communigate.com/pub/CGatePro/5.2/

                1 Reply Last reply
                0

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                Powered by NodeBB Contributors
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • Users
                • Groups