Skip navigation
2233 Views 3 Replies Latest reply: Jun 12, 2012 4:01 PM by fdupere RSS
fdupere Newbie 5 posts since
May 12, 2010
Currently Being Moderated

Jun 12, 2012 11:00 AM

Zenoss 4.1.1 - All device show down

Hi,

 

I added multiple devices to our fresh Zenoss 4.1.1 install and they are all showing down. If i run ping command from the menu, the device is reachable. I can snmpwalk my device without any problem. Zenmodeler did discover the interfaces of my device.

 

Logs from ping from the command menu:

==== 192.168.25.4 ====

dcsh --collector=localhost -n "ping -c2 192.168.25.4"

Collector StdOut/Stderr

-----------------------------------------------------------------

localhost PING 192.168.25.4 (192.168.25.4) 56(84) bytes of data.

64 bytes from 192.168.25.4: icmp_seq=1 ttl=62 time=17.8 ms

64 bytes from 192.168.25.4: icmp_seq=2 ttl=62 time=18.6 ms

--- 192.168.25.4 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1000ms

rtt min/avg/max/mdev = 17.869/18.259/18.650/0.413 ms

-----------------------------------------------------------------

 

 

I turned on debug for zenping. NmapPingTask says my device is down.

 

2012-06-12 11:20:32,875 INFO zen: Setting logging level to DEBUG

2012-06-12 11:21:25,968 DEBUG zen.collector.scheduler: Task NmapPingTask changing state from IDLE to QUEUED

2012-06-12 11:21:25,968 DEBUG zen.collector.scheduler: Task NmapPingTask changing state from QUEUED to RUNNING

2012-06-12 11:21:25,969 DEBUG zen.NmapPingTask: ---- BatchPingDevices ----

2012-06-12 11:21:25,969 DEBUG zen.zenping: Queued event (total of 1) {'eventseverity': 0, 'manager': 'labmssp-zenoss', 'eventGroup': 'Ping', 'eventKey': 'nmap_suid', 'device': 'zenping', 'eventClass': '/Status/Ping', 'monitor': 'localhost', 'agent': 'zenping', 'summary': 'nmap is set SUID'}

2012-06-12 11:21:32,776 DEBUG zen.NmapPingTask: 192.168.25.4 is down

2012-06-12 11:21:32,778 DEBUG zen.zenping: Queued event (total of 1) {'manager': 'labmssp-zenoss', 'eventGroup': 'Ping', 'severity': 5, 'device': '192.168.25.4', 'component': '', 'eventClass': '/Status/Ping', 'ipAddress': '192.168.25.4', 'monitor': 'localhost', 'agent': 'zenping', 'summary': '192.168.25.4 is DOWN!'}

2012-06-12 11:21:32,779 DEBUG zen.zenping: Queued event (total of 2) {'eventseverity': 0, 'manager': 'labmssp-zenoss', 'eventGroup': 'Ping', 'eventKey': 'nmap_execution', 'device': 'zenping', 'eventClass': '/Status/Ping', 'monitor': 'localhost', 'agent': 'zenping', 'summary': 'nmap executed correctly'}

2012-06-12 11:21:32,780 DEBUG zen.collector.scheduler: Task NmapPingTask finished, result: None

2012-06-12 11:21:32,780 DEBUG zen.collector.scheduler: Task NmapPingTask changing state from RUNNING to IDLE

 

From Zenoss terminal:

ping -c2 192.168.25.4

>PING 192.168.25.4 (192.168.25.4) 56(84) bytes of data.

64 bytes from 192.168.25.4: icmp_seq=1 ttl=62 time=20.9 ms

64 bytes from 192.168.25.4: icmp_seq=2 ttl=62 time=21.2 ms

--- 192.168.25.4 ping statistics ---

2 packets transmitted, 2 received, 0% packet loss, time 1001msrtt min/avg/max/mdev = 20.986/21.124/21.263/0.200 ms

 

 

Anybody else running in the same problem?

Thanks

Francis

  • dgarcia Rank: White Belt 7 posts since
    Apr 28, 2010
    Currently Being Moderated
    2. Jun 12, 2012 2:29 PM (in response to fdupere)
    Re: Zenoss 4.1.1 - All device show down

    Francis,

     

    Are those devices on the same network segment as your Zenoss instance? Zenoss is using nmap to batch ping those devices. It would be helpful to ping the devices as the same manner as Zenoss does. The relavent code is found in $ZENHOME/Products/ZenStatus/nmap/NmapPingTask.py Line 256. Run the following as the zenoss user.

     

    nmap [YOUR_TARGET_IP]  -sn -PE -n --privileged --send-ip --initial-rtt-timeout=1.5 --min-rtt-timeout=1.5 --traceroute -oX -

     

    Post the results of this command, please.

     

    Regards,
    Daniel Garcia

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points