maksik

Доброго времени суток! Аналогичная проблема с отпаданием ONU (проверяли на Fora EP1001 и на Foxgate NR1001). ==================================================== ZXAN(config)#show epon onu state OnuIndex OnlineStatus OamStatus RegMac -------------------------------------------------------------------- epon-onu_1/2/1:1 Offline idle 0000.0000.0000 ONU Number: 0/1 ZXAN(config)#show epon onu state OnuIndex OnlineStatus OamStatus RegMac -------------------------------------------------------------------- epon-onu_1/2/1:1 Online complete 1c87.7912.7fde ONU Number: 1/1 ==================================================== ZXAN#show card Rack Shelf Slot CfgType RealType Port HardVer SoftVer Status ------------------------------------------------------------------------------- 1 1 1 GTGO GTGOG 8 140600 V1.2.5P3 INSERVICE 1 1 2 ETGO ETGOD 8 091201 V1.2.5P3 INSERVICE 1 1 3 PRAM PRAM 3 V1.01 INSERVICE 1 1 4 SMXA SMXA 3 131201 V1.2.5P3 INSERVICE ==================================================== При этом, соответственно, ping (на тестовом оборудовании) около 5 секунд есть/нет. Заменить карту нет возможности. Нужна помощь. ================================================================================================================================================================= Jan 12 13:56:01 2017 Jan 12 13:55:45 ZTE command-log:An alarm 43015 level cleared occurred at 13:55:45 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 5 #012 on Jan 12 13:56:02 2017 Jan 12 13:55:45 ZTE command-log:An alarm 43015 level critical occurred at 13:55:45 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 0 Probable Cause : FiberCut#012 on Jan 12 13:56:11 2017 Jan 12 13:55:55 ZTE command-log:An alarm 43015 level cleared occurred at 13:55:55 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 5 #012 on Jan 12 13:56:13 2017 Jan 12 13:55:56 ZTE command-log:An alarm 43015 level critical occurred at 13:55:56 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 0 Probable Cause : FiberCut#012 on Jan 12 13:56:21 2017 Jan 12 13:56:05 ZTE command-log:An alarm 43015 level cleared occurred at 13:56:05 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 5 #012 on Jan 12 13:56:21 2017 Jan 12 13:56:05 ZTE command-log:An alarm 43016 level critical occurred at 13:56:05 01/12/2017 kiev sent by MCP Epon alarm OnuOffLine: shelf 1 slot 2 olt 1 onu 2 level 0 #012 on Jan 12 13:56:23 2017 Jan 12 13:56:07 ZTE command-log:An alarm 43016 level critical occurred at 13:56:07 01/12/2017 kiev sent by MCP Epon alarm OnuOffLine: shelf 1 slot 2 olt 1 onu 1 level 0 #012 on Jan 12 13:56:24 2017 Jan 12 13:56:07 ZTE command-log:An alarm 43016 level cleared occurred at 13:56:07 01/12/2017 kiev sent by MCP Epon alarm OnuOffLine: shelf 1 slot 2 olt 1 onu 2 level 5 #012 on Jan 12 13:56:27 2017 Jan 12 13:56:10 ZTE command-log:An alarm 43016 level cleared occurred at 13:56:10 01/12/2017 kiev sent by MCP Epon alarm OnuOffLine: shelf 1 slot 2 olt 1 onu 1 level 5 #012 on Jan 12 13:56:33 2017 Jan 12 13:56:17 ZTE command-log:An alarm 43015 level critical occurred at 13:56:17 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 0 Probable Cause : FiberCut#012 on Jan 12 13:56:42 2017 Jan 12 13:56:25 ZTE command-log:An alarm 43015 level cleared occurred at 13:56:25 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 5 #012 on Jan 12 13:56:44 2017 Jan 12 13:56:27 ZTE command-log:An alarm 43015 level critical occurred at 13:56:27 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 0 Probable Cause : FiberCut#012 on Jan 12 13:56:52 2017 Jan 12 13:56:35 ZTE command-log:An alarm 43015 level cleared occurred at 13:56:35 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 5 #012 on Jan 12 13:56:54 2017 Jan 12 13:56:37 ZTE command-log:An alarm 43015 level critical occurred at 13:56:37 01/12/2017 kiev sent by MCP Epon alarm PonLos: shelf 1 slot 2 olt 1 onu 0 level 0 Probable Cause : FiberCut#012 on =================================================================================================================================================================

Разве никто не работал с эти NetGear'ами?

Доброго времени суток! Требуется oid для снятия статистики загрузки CPU. "Google в помощь" не работает. Может кто сталкивался с подобным. Прошу помочь в данном вопросе.

При изменении в xml файле c walk на get при запросе verbose query oid'ы меняются. При walk Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.35160.1.16.1' + Index found at OID: '1.3.6.1.4.1.35160.1.16ф.1.2.1' value: 'AN1 Temperature' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.2' value: 'AN2 Temperature' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.3' value: '' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.4' value: '' При get + Executing SNMP get for data @ '.1.3.6.1.4.1.35160.1.16.1.2.1.AN1 Temperature' [value=''] + Executing SNMP get for data @ '.1.3.6.1.4.1.35160.1.16.1.2.1.AN2 Temperature' [value=''] + Executing SNMP get for data @ '.1.3.6.1.4.1.35160.1.16.1.2.1.' [value=''] + Executing SNMP get for data @ '.1.3.6.1.4.1.35160.1.16.1.2.1.' [value=''] P.S. Игнор что ли?

Вопросы еще актуальны.

Здравствуйте. Встал вопрос добавления устройства PING3 в cacti (необходимо снимать с устройства температуру...с возможностью в дальнейшем и другие датчики подключать и мониторить). Нашел инструкцию на английском по добавлению устройства в cacti (как раз пример с отображением графика температуры). Добавил в cacti все необходимые данные. Добавил device. Выставляю SNMP версии 2, ответа при нажатии на Verbose Query нет, выставляю SNMP версии 1, ответ есть, но при успешном запросе от Verbose Query вверху страницы все равно выдает сообщение "SNMP Error". Мой пробный вариант xml файла: <interface> <name>Get PING3 Statistics</name> <description>Get SNMP based Temperature Information from the PING3</description> <index_order_type>numeric</index_order_type> <oid_index>.1.3.6.1.4.1.35160.1.16.1</oid_index> <fields> <analogName.1> <name>Name</name> <method>walk</method> <source>value</source> <direction>input</direction> <oid>.1.3.6.1.4.1.35160.1.16.1.2.1</oid> <!--Это OID имени AN1, к которому подключен датчик измерения температуры--> </analogName.1> <analogValue.1> <name>Value</name> <method>walk</method> <source>value</source> <direction>output</direction> <oid>.1.3.6.1.4.1.35160.1.16.1.13.1</oid> <!--Это OID, который выдает значение температуры--> </analogValue.1> </fields> </interface> При нажатии на verbose query (при выставленном SNMP версии 1) в ответ приходит: + Running data query [15]. + Found type = '3' [snmp query]. + Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/ping3.xml' + XML file parsed ok. + Executing SNMP walk for list of indexes @ 'iso.3.6.1.4.1.35160.1.16.1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.1' value: 'AN1 Temperature' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.2' value: '' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.3' value: '' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.2.4' value: '' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.3.1' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.3.2' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.3.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.3.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.4.1' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.4.2' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.4.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.4.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.5.1' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.5.2' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.5.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.5.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.6.1' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.6.2' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.6.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.6.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.7.1' value: '200' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.7.2' value: '200' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.7.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.7.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.8.1' value: '250' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.8.2' value: '250' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.8.3' value: '10230' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.8.4' value: '10230' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.9.1' value: '258' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.9.2' value: '200' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.9.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.9.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.10.1' value: '260' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.10.2' value: '250' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.10.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.10.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.11.1' value: '200' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.11.2' value: '200' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.11.3' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.11.4' value: '0' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.12.1' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.12.2' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.12.3' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.12.4' value: '1' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.13.1' value: '256' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.13.2' value: '359' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.13.3' value: '7100' + Index found at OID: '1.3.6.1.4.1.35160.1.16.1.13.4' value: '7400' + Located input field 'analogName' [walk] + Executing SNMP walk for data @ 'iso.3.6.1.4.1.35160.1.16.1.2.1' + Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/ping3.xml' + Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/ping3.xml' + Found data query XML file at '/usr/share/cacti/site/resource/snmp_queries/ping3.xml' Возможно я неправильно составляю xml файл? И вообще, не зря ли я стараюсь (в смысле, что нужно просто разобраться с snmp trap)? Кто сталкивался с данным устройством, наведите на правильный путь решения данного вопроса

Увы , КТ не позволяет. Кто такой (что такое) КТ?