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

Started by Mikhail V. Platonov, November 20, 2007, 01:59:20 PM

Previous topic - Next topic

Mikhail V. Platonov

День добрый.
Собираюсь использовать 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'ам?

weec

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

Mikhail V. Platonov

#2
К сожалению, нет. У них на протяжение многих версий один и тот же 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

weec

#3
для вывода более подробных логов при проверке синтаксиса думаю стоит попробовать это (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

weec

хм, зашел на сайт проекта, глянул журнал изменений
нашел вот это
Quotehttp://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

Mikhail V. Platonov

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