Ad Widget

Collapse

Can't figure out how to monitor SNMP hosts (Cisco switches and routers)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GonEd
    Junior Member
    • Feb 2014
    • 3

    #1

    Can't figure out how to monitor SNMP hosts (Cisco switches and routers)

    Hello everyone,

    I'm new to Zabbix, and currently I have it installed on a Linux (Ubuntu) server. I installed Zabbix 2.0.2 on this server and I'm currently monitoring 3 servers using the agent.

    My issue is getting a SNMP host to monitor. Here's what I've done.

    1. I imported a Cisco 2960 (48 Ports) template. The import process ran flawlessly. I'm trying to monitor Cisco 2960 48-ports switch and Cisco Nexus switch.
    2. I created a SNMP host, using FQDN as its SNMP interface and using DNS as its connect to setting.
    3. In the Templates tab, I added the new Cisco template that I loaded in step 1.
    4. A couple of minutes later and I see a red SNMP icon lit up.

    Troubleshooting I've done.
    Reading the document at: https://www.zabbix.com/documentation...itemtypes/snmp

    1. Command: snmpwalk -v 2c -c MySNMPstring FQDN.MyDomain.com |grep -i ifinoctet
    2. The above command comes back empty.
    3. Ran a slightly different command: snmpwalk -v 2c -c MySNMPstring FQDN.MyDomain.com |grep -i GigabitEthernet
    4. This returns what I think is the proper OID: iso.3.6.1.2.1.2.2.1.2.10101 = STRING: "GigabitEthernet1/0/1"
    5. I created a new item using the OID from step 4, and still no luck

    I checked the logs at /var/log/zabbix-server/ and I did notice a bunch of SNMP failures, but nothing specific that can help me pinpoint the issue(s).

    What am I doing wrong here?
  • pc99096
    Senior Member
    • Oct 2011
    • 193

    #2
    check this:

    Comment

    • GonEd
      Junior Member
      • Feb 2014
      • 3

      #3
      Still nothing...

      Thank you for your reply; I followed the instructions there and I'm still unable to monitor a port on the switch.
      I'm wondering if there's something with the OID I'm using. Basically, this is what I got from snmpwalk:
      iso.3.6.1.2.1.2.2.1.2.10101 = STRING: "GigabitEthernet1/0/1"
      iso.3.6.1.2.1.2.2.1.2.10102 = STRING: "GigabitEthernet1/0/2"
      iso.3.6.1.2.1.2.2.1.2.10103 = STRING: "GigabitEthernet1/0/3"
      iso.3.6.1.2.1.2.2.1.2.10104 = STRING: "GigabitEthernet1/0/4"
      iso.3.6.1.2.1.2.2.1.2.10105 = STRING: "GigabitEthernet1/0/5"
      ...
      ...

      I'm including a screenshot of how the item configuration looks like; I'm hoping this can pinpoint any wrong-doing in my part.
      Attached Files

      Comment

      • aib
        Senior Member
        • Jan 2014
        • 1615

        #4
        As I can see you use the specific community string
        MySNMPstring

        Because of that you have to add the description for macro {$SNMP_COMMUNITY} when you configure host.

        Something like that.
        (Forum Error Message: Too many live links/images found in your post content. Please edit your post or contact the administrator.)

        I thin you have a lot of SNMP failures because of incorrect SNMP community. By default it is "public" community.
        Sincerely yours,
        Aleksey

        Comment

        • GonEd
          Junior Member
          • Feb 2014
          • 3

          #5
          Thanks for your reply Aib.

          I've already set the {$SNMP_COMMUNITY} macro in Administration-General-Macros to my custom SNMP string. However, I was using the actual SNMP string as part of the item configuration. Let me try your suggestion, to use the actual macro in place of the actual snmp string in the item configuration.

          Thanks!


          Originally posted by aib
          As I can see you use the specific community string
          MySNMPstring

          Because of that you have to add the description for macro {$SNMP_COMMUNITY} when you configure host.

          Something like that.
          (Forum Error Message: Too many live links/images found in your post content. Please edit your post or contact the administrator.)

          I thin you have a lot of SNMP failures because of incorrect SNMP community. By default it is "public" community.

          Comment

          Working...