Ad Widget

Collapse

HP Procurve Switch Config

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • PeteyMcGee
    Junior Member
    • Jun 2008
    • 3

    #1

    HP Procurve Switch Config

    I am having an issue configuring one of our two HP Procurve switches. They are both the same model: J4819A-5308XL and configured identically. SNMP is enabled and I can pick up traffic on both using SNMP tool on the Zabbix server. I am able to monitor one of the switches through Zabbix with no issue. I am using the HP Procurve template and I am wondering if anyone out there may have an updated template that may resolve this issue. Both are also running the latest firmware. Any suggestions are much appreciated.
  • nelsonab
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2006
    • 1233

    #2
    I'm going to make a guess here, check the host configuration, make sure they are setup to point to the right host.

    Are there any errors for the second host?

    The version of the template you have is probably the same one I created and uploaded. There are no updates which I am aware of.

    I'm glad to hear the template was useful for someone else. :-D
    RHCE, author of zbxapi
    Ansible, the missing piece (Zabconf 2017): https://www.youtube.com/watch?v=R5T9NidjjDE
    Zabbix and SNMP on Linux (Zabconf 2015): https://www.youtube.com/watch?v=98PEHpLFVHM

    Comment

    • Niels
      Senior Member
      • May 2007
      • 239

      #3
      Originally posted by nelsonab
      I'm glad to hear the template was useful for someone else. :-D
      I'm using it too -- thanks!

      Comment

      • just2blue4u
        Senior Member
        • Apr 2006
        • 347

        #4
        I've just included it. Thanks for sharing!

        Is there some documentation / Reference guide containing information about the content / meaning of the SNMP OIDs?
        I have the MIBs downloaded from hp.com but i would like to have some more details, as i would like to create some triggers.
        Big ZABBIX is watching you!
        (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

        Comment

        • PeteyMcGee
          Junior Member
          • Jun 2008
          • 3

          #5
          No Errors

          Oddly enough there are no errors. The status of both = monitored and both show up as being available. There are numerous errors under the items configuration : OID [1.3.6.1.2.1.2.2.1.2.10] value #2 has unknow type [81] but they are also showing up for both hosts...

          Comment

          • just2blue4u
            Senior Member
            • Apr 2006
            • 347

            #6
            i found out that the "unknown type" error comes up if zabbix tries to get data of an OID (let's say "traffic on port 88") that doesn't exist for that device (e.g. if the switch doesn't have 88 ports )

            In this case the item becomes "unsupported" in zabbix and is queried if the "refresh unsupported items" timer has expired again.
            Big ZABBIX is watching you!
            (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

            Comment

            • PeteyMcGee
              Junior Member
              • Jun 2008
              • 3

              #7
              That makes perfect sense! Though the models are the same, the one that is not working has additional interfaces. I will have to edit the template to accept the additional interfaces. Thank you for the idea, I will post my results.

              Comment

              • just2blue4u
                Senior Member
                • Apr 2006
                • 347

                #8
                i spent the whole last day in creating an advanced template with the items sortet into applications and some informational stuff being removed. It's not finished, but i'll share it once it is...
                Big ZABBIX is watching you!
                (... and my 48 hosts, 4513 items, 1280 triggers via zabbix v1.6 on CentOS 5.0)

                Comment

                Working...