Ad Widget

Collapse

has a problem when monitor Cyberoam Firewall

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • THUHV
    Junior Member
    • Dec 2009
    • 28

    #1

    has a problem when monitor Cyberoam Firewall

    Dear my friends,
    I just installed zabbix 2.2.6 to monitor my company network included Cyberoam CR200i firewalls.

    I used SNMP v2c to monitor. After i created host for cyberoam and added "template SNMP Device".

    After one hour my zabbix detect all of ports and information from my two cyberoam firewalls. It's seem to be work very fine. but it's work fine only about one hour. after that i don't see any new infor update to my zabbix server. please check my attached picture named is "traffic graphs.jpg".

    I also check items. and all of cyberoam items show is..not supported (please see my picture named is "not supported.jpg".

    When i check snmp by snmpwalk from my zabbix server to my cyberoam. it is okay.

    If i unlink and clear this template and add this template again. i see the same result.

    Please help me. it is very important for me.
    I intended to upgrade to zabbix 2.4, does it solve my problem?

    Thanks you!
    Last edited by THUHV; 10-10-2014, 11:28.
  • THUHV
    Junior Member
    • Dec 2009
    • 28

    #2
    I have just check zabbix_server.log and have this. I don't know why i can receive data on zabbix correctly. But after one hour i received this error.

    10884:20140920:170048.742 item "HAN_CYBEROAM:ifAdminStatus[PortD]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifAdminStatus[ipsec5]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[sit0]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[imq1]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[mast0]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[gre0]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[tun0]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifInOctets[PortF_ppp]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifOperStatus[PortA]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifOperStatus[ipsec3]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifOperStatus[PortF_ppp]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.742 item "HAN_CYBEROAM:ifOutErrors[ipsec4]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.743 item "HAN_CYBEROAM:ifOutErrors[gre0]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    10884:20140920:170048.743 item "HAN_CYBEROAM:ifOutOctets[PortB]" became not supported: SNMP error: (noSuchName) There is no such variable name in this MIB.
    Thank so much!

    Comment

    • dart_ua
      Junior Member
      • Jul 2013
      • 4

      #3
      It's registered bug. support team tell- it will be resolve in new version -2.2.7.

      Comment

      • ingus.vilnis
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Mar 2014
        • 908

        #4
        Hi,

        I see this a week old thread already but with no replies so here is one.
        Yes, 2.4 will solve your problem. This is because your devices do not support SNMP bulk requests but you can disable them in 2.4.


        Best Regards,
        Ingus

        Comment

        • THUHV
          Junior Member
          • Dec 2009
          • 28

          #5
          Originally posted by ingus.vilnis
          Hi,

          I see this a week old thread already but with no replies so here is one.
          Yes, 2.4 will solve your problem. This is because your devices do not support SNMP bulk requests but you can disable them in 2.4.


          Best Regards,
          Ingus

          Yes, this is a problem that i have, thanks you so much! just disable bulk request and everything is okay

          Thank Ingus!

          Comment

          Working...