Ad Widget

Collapse

Timeout while connecting to [:161]

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • masterj
    Junior Member
    • Oct 2009
    • 4

    #1

    Timeout while connecting to [:161]

    Hi, i am new to Zabbix and have just started evaluating the application.

    Installed Zabbix Server on Ubuntu from the repository and on FreeBSD from the ports tree, yet each time i get the following error when monitoring the cisco switches - Timeout while connecting to [:161]

    I have gone though the formus, installation documentation and have ensure that i installed --with-net-snmp where i compiled the lastest version.

    I have check that the correct community string, O.I.D and other other detail are connect. I am able to get the snmp values from the command line using snmpwalk or snmpget.

    I must be missing something simple, could somebody point me in the right direction, from what i have read, this is supposed to work out of the box, configure host with IP, apply template and correct community string.
  • masterj
    Junior Member
    • Oct 2009
    • 4

    #2
    This message is repeated over and over. Is there not supposed to be [switches IP:161]

    4392:20091027:121710 Starting zabbix_server. ZABBIX 1.4.6.
    4392:20091027:121710 **** Enabled features ****
    4392:20091027:121710 SNMP monitoring: YES
    4392:20091027:121710 WEB monitoring: YES
    4392:20091027:121710 Jabber notifications: YES
    4392:20091027:121710 IPv6 support: NO
    4392:20091027:121710 **************************
    ...
    ...
    4507:20091027:122326 Parameter [Uptime] will be checked after 300 seconds on host [CISCO-SW1]
    4509:20091027:122326 Timeout while connecting to [:161]

    Comment

    • NOB
      Senior Member
      Zabbix Certified Specialist
      • Mar 2007
      • 469

      #3
      Hi

      how does the configuration of your Cisco switch host looks like ?

      It seems the IP address is not or not correctly set.
      This is a wild guess, though.

      Can you post a screenshot or a "text dump" of the fields.

      Regards

      Norbert.

      Comment

      • masterj
        Junior Member
        • Oct 2009
        • 4

        #4
        Hey Norbert

        I doubt the problem is the Cisco switch as i am able to snampwalk and snmpget from the command line of the zabbix server. However, anything is possible.

        We used the following command on the router -
        snmp-server community csw1-snmp RO

        Here is an except from the hosts table:
        select * from hosts where host like'switche%';

        | hostid | proxy_hostid | host | dns | useip | ip | port | status | disable_until | error | available | errors_from | lastaccess | inbytes | outbytes | useipmi | ipmi_port | ipmi_authtype | ipmi_privilege | ipmi_username | ipmi_password | ipmi_disable_until | ipmi_available | snmp_disable_until | snmp_available |
        +--------+--------------+---------------------------+-----+-------+---------------+-------+--------+---------------+------------------------------------+-----------+-------------+------------+---------+----------+---------+-----------+---------------+----------------+---------------+---------------+--------------------+----------------+--------------------+----------------+
        | 10050 | 0 | switch-SW1 | | 0 | 192.168.9.10 | 10050 | 0 | 1256634402 | Timeout while connecting to [:161] | 2 | 1256576355 | 0 | 0 | 0 | 0 | 623 | -1 | 2 | | | 0 | 0 | 0 | 0

        Comment

        • MrKen
          Senior Member
          • Oct 2008
          • 652

          #5
          Wow, I think I need a new 'wide-screen' monitor!

          In your 2nd post you have [CISCO-SW1]
          In your last post you have switch-SW1

          My guess is that you changed 'switch' to 'CISCO' just for this post, so it is probably irrelevant.

          My other guess is that in your Zabbix configuration --> Hosts, for this switch, you have 'Connect to = dns name' instead of IP address.

          MrKen
          Disclaimer: All of the above is pure speculation.

          Comment

          • masterj
            Junior Member
            • Oct 2009
            • 4

            #6
            MrKe is dead right.... it is always the simple stuff...
            I was using connect to DNS instead of IP Address. Many Thanks.

            Comment

            • changzonghui
              Junior Member
              • Nov 2013
              • 7

              #7
              the same error,different reason.

              i got the same error. time out to connect ip:161 , i'm sure i have no problem with the configuration.
              i don't know why,maybe my server hardware is too high.
              here is my server infomation:
              memory: 128G
              cpu: intel,48core


              any other answer ? help,

              Comment

              Working...