oddness with protocols.cfg
list Sean Clark
I had this set in the protocols.cfg [bbd] send "ping" expect "xymond" port 1984 I tried this then [bbd] send "ping\r\n" expect "xymond" port 1984 Shows yellow Manually running [sclark at bastion?~]~bb/server/bin/XXX.com "ping" xymond 4.3.7 Works, but doing something like this doesn't -bash-3.2$ telnet localhost 1984 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. ping (hit enter here) ^] (give up after waiting for a while) telnet> quit Debug gives me this 15451 2012-05-14 15:33:39 tcp_got_expected: No data in banner 15451 2012-05-14 15:33:39 Adding to combo msg: status+30 XXXX,com.bbd yellow <!-- [flags:OrdastLe] --> Mon May 14 15:33:34 2012 bbd NOT ok I also tried the 'banner' keyword in protocols.cfg, and didn't get anything What am I doing wrong here? -- Sean Clark Sr. Engineer, Software ATG Network Operations & Planning Integrated Regional OSS<http://www.twcable.com/DepartmentOverview/AdvancedTechnologyGroup/ATG/NOP/OSS/Network.aspx>; user-2db5fbcae9a7@xymon.invalid <mailto:user-2db5fbcae9a7@xymon.invalid> devaudio<aim://devaudio> <mailto:user-2db5fbcae9a7@xymon.invalid> Cell: (XXX) XXX-XXXX This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
list Henrik Størner
▸
On 14-05-2012 21:42, Clark, Sean wrote:
I had this set in the protocols.cfg [bbd] send "ping" expect "xymond" port 1984 I tried this then [bbd] send "ping\r\n" expect "xymond" port 1984 Shows yellow
Yes, well ... let's just say that xymond has some very specific requirements about the TCP/IP protocol. Which the Xymon network tester doesn't fulfill. (Technically, xymond expects the client to send a FIN packet - usually done by calling "shutdown(socket, SHUT_WR)" before it will assume that the entire command has been sent - and only then will it process the request and send a response).
▸
Manually running [sclark at bastion?~]~bb/server/bin/XXX.com "ping" xymond 4.3.7 Works, but doing something like this doesn't -bash-3.2$ telnet localhost 1984 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. ping (hit enter here) ^] (give up after waiting for a while) telnet> quit
Nope, same reason - telnet doesn't shutdown the session the way xymond expects. So you are not doing anything wrong - it's just xymond that behaves oddly. Regards, Henrik
list Sean Clark
SooooŠ no way to test xymond with xymonnet, eh? :-D The issue I had, is I have xymon behind a load balancer, and wanted to be sure "xymon" is up and not just that port 1984 is listening The xymon ping in protocols.cfg looked perfect but commented outŠ. Now I see why -- Sean Clark Sr. Engineer, Software ATG Network Operations & Planning Integrated Regional OSS <http://www.twcable.com/DepartmentOverview/AdvancedTechnologyGroup/ATG/NOP/ OSS/Network.aspx> user-2db5fbcae9a7@xymon.invalid <mailto:user-2db5fbcae9a7@xymon.invalid> devaudio <aim://devaudio> <mailto:user-2db5fbcae9a7@xymon.invalid> Cell: (XXX) XXX-XXXX
▸
On 5/14/12 3:51 PM, "Henrik Størner" <user-ce4a2c883f75@xymon.invalid> wrote:
On 14-05-2012 21:42, Clark, Sean wrote:I had this set in the protocols.cfg [bbd] send "ping" expect "xymond" port 1984 I tried this then [bbd] send "ping\r\n" expect "xymond" port 1984 Shows yellowYes, well ... let's just say that xymond has some very specific requirements about the TCP/IP protocol. Which the Xymon network tester doesn't fulfill. (Technically, xymond expects the client to send a FIN packet - usually done by calling "shutdown(socket, SHUT_WR)" before it will assume that the entire command has been sent - and only then will it process the request and send a response).Manually running [sclark at bastion?~]~bb/server/bin/XXX.com "ping" xymond 4.3.7 Works, but doing something like this doesn't -bash-3.2$ telnet localhost 1984 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. ping (hit enter here) ^] (give up after waiting for a while) telnet> quitNope, same reason - telnet doesn't shutdown the session the way xymond expects. So you are not doing anything wrong - it's just xymond that behaves oddly. Regards, Henrik
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.