Ad Widget

Collapse

SNMP on Cisco Random OID ?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jcduss59
    Member
    • Jun 2011
    • 33

    #1

    SNMP on Cisco Random OID ?

    Hi all,

    I'm trying to monitor hardware on about 15 switchs Cisco catalyst 2950 using snmp.

    I would like to monitor fans, powersupply, temperature etc

    I get troubles with what I think is "random oid".

    For exemple, on cisco I found this OID to monitor the power supply source :


    When I make an snmpwalk on a first switch :
    snmpwalk -v 1 -c public 10.10.10.1 1.3.6.1.4.1.9.9.13.1.5.1.4
    I'll get this reply :
    iso.3.6.1.4.1.9.9.13.1.5.1.4.1006 = INTEGER: 2


    When I make it on a second switch :
    snmpwalk -v 1 -c public 10.10.10.2 1.3.6.1.4.1.9.9.13.1.5.1.4
    I'll get this reply :
    iso.3.6.1.4.1.9.9.13.1.5.1.4.1003 = INTEGER: 2



    You can note the end of the OID differs. 1003 vs 1006
    As you can note there is only one variable replied for this oid.

    My wish is to create an unique templates to manage all the switch... but it seems not possible??!!

    If I create an Item on zabbix with only oid "iso.3.6.1.4.1.9.9.13.1.5.1.4" or "1.3.6.1.4.1.9.9.13.1.5.1.4"
    I will get this from the server :

    [Switch1:PowerSupply_Source] became not supported: OID [1.3.6.1.4.1.9.9.13.1.5.1.4] value has unknown type [0x81]

    If my item got the full OID with the last digits, item is working.


    What can I do to templates for all of my switch in a unique template ? Is this last digit dynamic and can changes at any time???

    Thank you,
    JC.
    Last edited by jcduss59; 23-04-2012, 12:11.
  • jcduss59
    Member
    • Jun 2011
    • 33

    #2
    Solved !

    I will autoreply my self !

    I found that we can use "Dynamic indexes" at
    http://www.zabbix.com/documentation/.../advanced_snmp

    Should have RTFM first before post, but I hope my answer will help :

    So in my case the OID became :

    1.3.6.1.4.1.9.9.13.1.5.1.4["index","1.3.6.1.4.1.9.9.13.1.5.1.2","Sw1, PS1 Normal, RPS NotExist"]

    and it's working fine !

    Comment

    • jcduss59
      Member
      • Jun 2011
      • 33

      #3
      I continue my investigation.

      I've got troubles with what seems to be a "double dynamic indexe" ex

      My snmpwalk give such information
      iso.3.6.1.4.1.9.9.106.1.2.1.1.2.58.1 = STRING: "HSRP-1"
      iso.3.6.1.4.1.9.9.106.1.2.1.1.2.64.7 = STRING: "HSRP-7"
      iso.3.6.1.4.1.9.9.106.1.2.1.1.2.65.8 = STRING: "HSRP-8"
      iso.3.6.1.4.1.9.9.106.1.2.1.1.2.66.9 = STRING: "HSRP-9"

      which depends on cisco mibs here http://tools.cisco.com/Support/SNMP/...CISCO-HSRP-MIB

      58.1 , 64.7 are here dynamics OID ..

      I would like to monitor cHsrpGrpStandbyState ( http://tools.cisco.com/Support/SNMP/...rpStandbyState) which reply this with snmp walk

      iso.3.6.1.4.1.9.9.106.1.2.1.1.15.58.1 = INTEGER: 1
      iso.3.6.1.4.1.9.9.106.1.2.1.1.15.64.7 = INTEGER: 5
      iso.3.6.1.4.1.9.9.106.1.2.1.1.15.65.8 = INTEGER: 5

      My dynamic OID is written like this :
      1.3.6.1.4.1.9.9.106.1.2.1.1.15["index","1.3.6.1.4.1.9.9.106.1.2.1.1.2","HSRP-1"]

      And Zabbix reports me that the item become not supported :
      3110:20120424:122217.761 item [Switch1:HSRP-1_State] became not supported: OID [1.3.6.1.4.1.9.9.106.1.2.1.1.15.1] value has unknown type [0x81]
      23120:20120424:122222.765 item [Switch1:HSRP-7_State] became not supported: OID [1.3.6.1.4.1.9.9.106.1.2.1.1.15.7] value has unknown type [0x81]
      23110:20120424:122302.974 item [Switch1:HSRP-10_State] became not supported: OID [1.3.6.1.4.1.9.9.106.1.2.1.1.15.10] value has unknown type [0x81]
      23113:20120424:122323.033 item [Switch1:HSRP-8_State] became not supported: OID [1.3.6.1.4.1.9.9.106.1.2.1.1.15.8] value has unknown type [0x81]

      Is "double dynamic indexes" supported?
      Maybe my OID is not written fine?

      Thank you.
      JC

      Comment

      • jcduss59
        Member
        • Jun 2011
        • 33

        #4
        it seems it's not supported yet :



        :/

        Comment

        Working...