It looks like you have a bad DNS entry. Try adding 'testip' to the printer lines in bb-hosts. This will cause Xymon to use the provided IP address rather than doing a DNS lookup based on the name.
Thanks, Larry Barber
On Tue, Mar 2, 2010 at 8:49 AM, <d.tom.schmitt at l-3com.com> wrote:
I watch multiple printers and all are on the same subnet .
I added a 128.170.70.88 called Printer088.
From the command line and my PC I can ping the device:
[root at monitor1 ~]# ping 128.170.70.88PING 128.170.70.88 (128.170.70.88) 56(84) bytes of data.
64 bytes from 128.170.70.88: icmp_seq=1 ttl=59 time=1.67 ms
64 bytes from 128.170.70.88: icmp_seq=2 ttl=59 time=1.71 ms
64 bytes from 128.170.70.88: icmp_seq=3 ttl=59 time=1.46 ms
--- 128.170.70.88 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 1.467/1.617/1.713/0.112 ms
[root at monitor1 ~]#
I added the device yesterday afternoon to Xymon (running CentOS with 4.3.0-0.beta2).
bb-hosts entry:
group-compress <h4>Building R</h4>128.170.70.227 Printer227 # conn
128.170.70.228 Printer228 # conn
128.170.70.88 Printer088 # conn
The ICON is RED for the device:
*Tue Mar 2 07:46:07 2010 conn NOT ok *
Service conn on Printer088 is not OK : Host does not respond to ping
System unreachable for 201 poll periods (60424 seconds)
[image: red] 128.170.35.103 is unreachable
Status unchanged in 16 hours, 47 minutes Status message received from 128.170.1.151
[image: hobbitgraph tcp:conn]<http://monitor1.csw.l-3com.com/xymon-cgi/hobbitgraph.sh?host=Printer088&service=tcp:conn&graph_width=576&graph_height=120&disp=Printer088&nostale&color=red&graph_start=1267368435&graph_end=1267541235&action=menu>
The IP address that it says in “unreachable” does not have anything device associated with it either in the bb-hosts or DNS.
Why would this address be part of the test and not the actual IP address????
I have not special characters in the line other than a TAB between the IP and the device name just like all the other ones?
Firewall rules should not play a part as all are on the same subnet and I am able to ping the device from the command line.
BTW: I have three systems doing monitoring of this device and all are the same Xymon release on CentOS 5.3 or 5.4.
All of them show the exact same type of report.Could there be some corruption somewhere? What can I do to troubleshoot Xymon?
*Thanks,*
*Tom Schmitt*
*Senior IT Staff - R&D*
L-3 Communication Systems West
640 North 2200 West
P.O. Box 16850
Salt Lake City, UT 84116
Phone (801) *594-3030*
Cell (801) 231-7230
eFax (413) *480-6873*
*D.Tom.Schmitt at L-3Com.com*
**\\\\||////*****\ ~ ~ / *****| @ @ | ****--oOo---(_)---oOo--***