one of the dependent router conn fail but ping success
list Asif Iqbal
$ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 shows conn/ping failure for 192.168.65.254 status+30 192,168,65,254.conn red <!-- [flags:ordAstLe] --> Tue Dec 4 14:40:30 2012 conn NOT ok Service conn on 192.168.65.254 is not OK : Host does not respond to ping System unreachable for 774 poll periods (232704 seconds) &red 192.168.65.254 is unreachable But success with just 192.168.65.254 as the host $ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 192.168.65.254 11079 2012-12-04 15:02:14 Adding to combo msg: status+30 192,168,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok 11079 2012-12-04 15:02:14 Flushing combo message combo status+30 216,111,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok Service conn on 192.168.65.254 is OK (up) &green 192.168.65.254 is alive (51.2 ms) $ fping 192.168.65.254 192.168.65.254 is alive What gives? -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
list Asif Iqbal
▸
On Tue, Dec 4, 2012 at 3:06 PM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:
$ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 shows conn/ping failure for 192.168.65.254 status+30 192,168,65,254.conn red <!-- [flags:ordAstLe] --> Tue Dec 4 14:40:30 2012 conn NOT ok Service conn on 192.168.65.254 is not OK : Host does not respond to ping System unreachable for 774 poll periods (232704 seconds) &red 192.168.65.254 is unreachable But success with just 192.168.65.254 as the host $ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 192.168.65.254 11079 2012-12-04 15:02:14 Adding to combo msg: status+30 192,168,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok 11079 2012-12-04 15:02:14 Flushing combo message combo status+30 216,111,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok Service conn on 192.168.65.254 is OK (up) &green 192.168.65.254 is alive (51.2 ms) $ fping 192.168.65.254 192.168.65.254 is alive What gives?
running xymon latest $ xymon --version Xymon version 4.3.10
▸
--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
list Asif Iqbal
▸
On Tue, Dec 4, 2012 at 3:08 PM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:
On Tue, Dec 4, 2012 at 3:06 PM, Asif Iqbal <user-6f4b51ac2a40@xymon.invalid> wrote:$ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 shows conn/ping failure for 192.168.65.254 status+30 192,168,65,254.conn red <!-- [flags:ordAstLe] --> Tue Dec 4 14:40:30 2012 conn NOT ok Service conn on 192.168.65.254 is not OK : Host does not respond to ping System unreachable for 774 poll periods (232704 seconds) &red 192.168.65.254 is unreachable But success with just 192.168.65.254 as the host $ xymoncmd xymonnet --no-update --debug --ping --trace --checkresponse --timeout=30 --concurrency=50 192.168.65.254 11079 2012-12-04 15:02:14 Adding to combo msg: status+30 192,168,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok 11079 2012-12-04 15:02:14 Flushing combo message combo status+30 216,111,65,254.conn green <!-- [flags:OrdAstLe] --> Tue Dec 4 15:02:14 2012 conn ok Service conn on 192.168.65.254 is OK (up) &green 192.168.65.254 is alive (51.2 ms) $ fping 192.168.65.254 192.168.65.254 is alive What gives?
still need help troubleshooting this. I wonder if I should the number of concurrent tests from 50 to 30
▸
running xymon latest $ xymon --version Xymon version 4.3.10 -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
-- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?