xymon as a drop-in bb replacement
list John Thurston
We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options.
We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition.
Has anyone else recently gone down this path?
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Sean MacGuire
▸
John Thurston wrote:
We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options. We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?
If anyone on here is old enough - they might recognize me as the original author of BB. And, yes Quest End-of-Lifed it earlier this month and I'm taking care of all the support until the EoL. That having been said, I recommend moving to Xymon, and would be happy to help any BBPE users in any way I can. -- Sean MacGuire user-4915795a2617@xymon.invalid Key West +X XXX XXX XXXX The best way to predict the future is to invent it. - Alan Kay
list John Horne
▸
On Mon, 2013-03-18 at 10:55 -0800, John Thurston wrote:
We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options. We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?
Hello, Not too recently, around autumn 2011. I use Xymon to monitor around 20 servers, so obviously not on your scale of things! :-) However, I would suggest installing Xymon on a test server initially, see how it works and what needs configuring, and likewise install it onto a client (and have the server monitor the client). We found that once we had a test server and client running, the actual move to a live Xymon server and clients was very easy. With this setup you should be able to see if Xymon is going to work with your BB configuration files (which for generic BB files, I think Xymon will work out of the box). John. -- John Horne, Plymouth University, UK Tel: +XX (X)XXXX XXXXXX Fax: +XX (X)XXXX XXXXXX
list Sean Clark
I migrated from bb1.9btf to xymon when it first came out (2005?2006?) Transition is seamless You'll want to get to migrating the clients when you find how much more useful the xymon client in than the bb native one was (Sorry Sean)
▸
On 3/18/13 2:55 PM, "John Thurston" <user-ce4d79d99bab@xymon.invalid> wrote:
We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options. We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path? -- Do things because you should, not just because you can. John Thurston XXX-XXX-XXXX user-ce4d79d99bab@xymon.invalid Enterprise Technology Services Department of Administration State of Alaska
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 18-03-2013 19:55, John Thurston wrote:
We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options.
I heard about this from Sean MacGuire. I expect there will be others like yourself in the same situation coming to have a closer look at Xymon now.
▸
We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?
Xymon is designed to be compatible with BB clients, so there is no need to replace the clients - you can swap out the BB server with a Xymon server, and your clients won't know the difference. This is quite intentional - I had 1000+ BB clients when Xymon was designed, and replacing all of them overnight was not possible. As pointed out elsewhere, there are benefits to changing the client - especially for Unix-based clients. But you are free to do it whenever it fits into your overall maintenance, or when there is a specific need for a client replacement. (The actual replacement is fairly simple, since you do all of the configuration on the Xymon server. The client can be rolled out as a pre-packaged file that you just unpack somewhere with a standard config pointing it to your Xymon server - so you can use the same client package on all systems running the same operating system). Regards, Henrik
list John Thurston
▸
On 3/18/2013 11:04 AM, Sean MacGuire wrote:
John Thurston wrote:We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options. We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?If anyone on here is old enough - they might recognize me as the original author of BB.
Yes, Sean. Thank you! We've been running bb since 1998 or 99. Does that make me old?
▸
That having been said, I recommend moving to Xymon, and would be happy to help any BBPE users in any way I can.
Well, it was a little bit of a battle, but I got Xymon built and running on a Solaris zone. This is a thing of beauty. I grabbed my bb-hosts file, pulled my BBDISPLAY lines out, and threw it at the Xymon server. We're rocking and rolling :) A few things I notice are: Our BB configuration pre-dates FQDN support, so my bb-hosts file has only hostnames in it. I'll either need to disable FQDN on Xymon or insert "testip" all over my hosts.cfg. I'll probably do the latter because I think it is finally time to embrace fqdn. I didn't import any of my ext-scripts or customizations and I see Xymon now natively supports a few things I had rolled on my own. I've thrown a BBRELAY line in one of my production BB servers, and it works like a champ. One thing I'm missing, though, is the equivalent of the searchable web-help we have with BBPE. I see all of the help files and I can grep them, but is there a slicker way to find things in them from the web interface?
▸
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska
list Jeremy Laidman
▸
On 20 March 2013 10:49, John Thurston <user-ce4d79d99bab@xymon.invalid> wrote:
One thing I'm missing, though, is the equivalent of the searchable web-help we have with BBPE. I see all of the help files and I can grep them, but is there a slicker way to find things in them from the web interface?
Use the Googles: site:xymon.com inurl:xymon/help "xymonproxy" You can make this a search engine in your browser, by manual configuration. Or, just install the OpenSearch provider here: http://mycroftproject.com/search-engines.html?name=xymon. Set a useful keyword (Firefox and Chrome) such as "xymondocs" and you can search directly from the URL bar. Cheers Jeremy
list Henrik Størner
On Tue, 19 Mar 2013 15:49:03 -0800, John Thurston
▸
<user-ce4d79d99bab@xymon.invalid> wrote:Our BB configuration pre-dates FQDN support, so my bb-hosts file has only hostnames in it. I'll either need to disable FQDN on Xymon or insert "testip" all over my hosts.cfg. I'll probably do the latter because I think it is finally time to embrace fqdn.
You can set FQDN="FALSE" in xymonserver.cfg, and it should work just like your old BB server. A quick way of setting "testip" for all hosts is to add a ".default." at the top of hosts.cfg: 0.0.0.0 .default. # testip If you need to turn it off again somewhere, just define it again, but blank: 0.0.0.0 .default. # But of course, using fqdn's really is the best solution. Regards, Henrik
list Mark Deiss
Nuts - guess that means the Quest/former Deadcat repository of all the BB-based user contributions will be vaporized at some point per BBPE EOL. Maybe Mr. Croteau/Quest can " transfer" the content back under the wings of Mr. MacGuire/somebody? This code base should be all GPL and not hamstrung by any Quest licensing restrictions. Hmm, maybe Mr. Croteau and Mr. MacGuire will get back together again with something like "Big Second-Cousin-Once-Removed's Second-Coming"
▸
-----Original Message-----
From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner
Sent: Tuesday, March 19, 2013 5:20 AM
To: xymon at xymon.com
Subject: Re: [Xymon] xymon as a drop-in bb replacement
On 18-03-2013 19:55, John Thurston wrote:We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options.
I heard about this from Sean MacGuire. I expect there will be others like yourself in the same situation coming to have a closer look at Xymon now.
We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?
Xymon is designed to be compatible with BB clients, so there is no need to replace the clients - you can swap out the BB server with a Xymon server, and your clients won't know the difference. This is quite intentional - I had 1000+ BB clients when Xymon was designed, and replacing all of them overnight was not possible. As pointed out elsewhere, there are benefits to changing the client - especially for Unix-based clients. But you are free to do it whenever it fits into your overall maintenance, or when there is a specific need for a client replacement. (The actual replacement is fairly simple, since you do all of the configuration on the Xymon server. The client can be rolled out as a pre-packaged file that you just unpack somewhere with a standard config pointing it to your Xymon server - so you can use the same client package on all systems running the same operating system). Regards, Henrik
list Scot Kreienkamp
As long as we're laying out wish lists.... I really wish someone would take over development of BBWin again. That is a serious concern for us. Windows will never be totally out of the environment and not having a strong client to monitor both Windows and Linux is a big problem. Scot Kreienkamp | Senior Systems Engineer | La-Z-Boy Incorporated 1284 N. Telegraph Rd. | Monroe, MI 48162 | user-9678697f1438@xymon.invalid | www.la-z-boy.com
-----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Deiss, Mark Sent: Wednesday, March 20, 2013 8:59 AM
▸
To: xymon at xymon.com
Subject: Re: [Xymon] xymon as a drop-in bb replacement
Nuts - guess that means the Quest/former Deadcat repository of all the BB-
based user contributions will be vaporized at some point per BBPE EOL. Maybe
▸
Mr. Croteau/Quest can " transfer" the content back under the wings of Mr. MacGuire/somebody? This code base should be all GPL and not hamstrung by any Quest licensing restrictions. Hmm, maybe Mr. Croteau and Mr. MacGuire will get back together again with something like "Big Second-Cousin-Once-Removed's Second-Coming" -----Original Message----- From: xymon-bounces at xymon.com [mailto:xymon-bounces at xymon.com] On Behalf Of Henrik Størner Sent: Tuesday, March 19, 2013 5:20 AM To: xymon at xymon.com Subject: Re: [Xymon] xymon as a drop-in bb replacement On 18-03-2013 19:55, John Thurston wrote:We ran BB 1.9 for years, then switched to BBPE about three years ago. Earlier this month, Quest announced end-of-life for BBPE so we're looking at our options.I heard about this from Sean MacGuire. I expect there will be others like yourself in the same situation coming to have a closer look at Xymon now.We have fewer than 500 clients reporting into Big Brother. But swapping them out for something else is going to painful and take time. If a xymon server will happily accept bb-client messages, then I could stand up a xymon server and replace clients through attrition. Has anyone else recently gone down this path?Xymon is designed to be compatible with BB clients, so there is no need to replace the clients - you can swap out the BB server with a Xymon server, and your clients won't know the difference. This is quite intentional - I had 1000+ BB clients when Xymon was designed, and replacing all of them overnight was not possible. As pointed out elsewhere, there are benefits to changing the client - especially for Unix-based clients. But you are free to do it whenever it fits into your overall maintenance, or when there is a specific need for a client replacement. (The actual replacement is fairly simple, since you do all of the configuration on the Xymon server. The client can be rolled out as a pre-packaged file that you just unpack somewhere with a standard config pointing it to your Xymon server - so you can use the same client package on all systems running the same operating system). Regards, Henrik
This message is intended only for the individual or entity to which it is addressed. It may contain privileged, confidential information which is exempt from disclosure under applicable laws. If you are not the intended recipient, please note that you are strictly prohibited from disseminating or distributing this information (other than to the intended recipient) or copying this information. If you have received this communication in error, please notify us immediately by e-mail or by telephone at the above number. Thank you.
list Gonzalo Fernandez Ordas
Hi I have generated some scripts which they should send some information back to the Xymon Server. The jobs seem working fairly well, but they failed to give me a full output but a partial one? Is there any limit for the amount of information being sent across? For example ,checking the ports there is a full output, but in my case remotely I am running a "cat <file>" and the Xymon Server does not reflect the whole output but a fragment of it. any idea? Many thanks
list Mike Burger
Gonzalo, Check your logs, and see if there are any mentions of reports being to large. Then, look at your xymonserver.cfg file and modify the appropriate "MAX...." variables to account for the additional size. I've increased "MAXMSG_CLIENT", "MAXMSG_STATUS" and "MAXMSG_DATA" to account for a number of my busier servers. -- Mike Burger http://www.bubbanfriends.org "It's always suicide-mission this, save-the-planet that. No one ever just stops by to say 'hi' anymore." --Colonel Jack O'Neill, SG1
▸
Hi I have generated some scripts which they should send some information back to the Xymon Server. The jobs seem working fairly well, but they failed to give me a full output but a partial one? Is there any limit for the amount of information being sent across? For example ,checking the ports there is a full output, but in my case remotely I am running a "cat <file>" and the Xymon Server does not reflect the whole output but a fragment of it. any idea? Many thanks
list Adam Goryachev
▸
On 20/03/13 23:58, Deiss, Mark wrote:
Nuts - guess that means the Quest/former Deadcat repository of all the BB-based user contributions will be vaporized at some point per BBPE EOL. Maybe Mr. Croteau/Quest can " transfer" the content back under the wings of Mr. MacGuire/somebody? This code base should be all GPL and not hamstrung by any Quest licensing restrictions. Hmm, maybe Mr. Croteau and Mr. MacGuire will get back together again with something like "Big Second-Cousin-Once-Removed's Second-Coming"
As the original person responsible for the deadcat repository, I'll put my hand up, again... though perhaps this is already handled by xymonton? Will likely require some work from some enterprising individual(s) to simply copy the various scripts from the current location and upload to xymonton. If people think it would actually be more useful to have a separate repository, let me know and I'll dig something up.... Regards, Adam -- Adam Goryachev Website Managers Ph: +XX X XXXX XXXX user-eaec2ffb4cbc@xymon.invalid Fax: +XX X XXXX XXXX www.websitemanagers.com.au
list Sean MacGuire
▸
Adam Goryachev wrote:
On 20/03/13 23:58, Deiss, Mark wrote:Nuts - guess that means the Quest/former Deadcat repository of all the BB-based user contributions will be vaporized at some point per BBPE EOL. Maybe Mr. Croteau/Quest can " transfer" the content back under the wings of Mr. MacGuire/somebody? This code base should be all GPL and not hamstrung by any Quest licensing restrictions. Hmm, maybe Mr. Croteau and Mr. MacGuire will get back together again with something like "Big Second-Cousin-Once-Removed's Second-Coming"As the original person responsible for the deadcat repository, I'll put my hand up, again... though perhaps this is already handled by xymonton? Will likely require some work from some enterprising individual(s) to simply copy the various scripts from the current location and upload to xymonton. If people think it would actually be more useful to have a separate repository, let me know and I'll dig something up....
Guys, I've spoken with the nice people at Quest... the plugins will live on and will not be vaporized. Stay tuned.
▸
--
Sean MacGuire user-4915795a2617@xymon.invalid
Key West +X XXX XXX XXXX
The best way to predict the future is to invent it. - Alan Kay
list John Palys
I am having an issue with the fqdn and big brother bb18c version using BBWIN client version 1.1. If I setup servers without the fqdn, they report proeprly to BB showing all indicators. If I try to use FQDN even though it matches in the bb-hosts file, I get noting unless a check is "bad:. When it hits a threshold, then it show up ONLY in the condensed dispaly, not the host display for the particular batch of servers. Any solutions? -- Thank You, ******************************************* John Palys Systems Administrator, Efficient Computing Inc Direct: XXX.XXX.XXXX Main: XXX.XXX.XXXX / XXX-XXX-XXXX, ext XXXX Fax: XXX.XXX.XXXX Email: user-02cee590f224@xymon.invalid *******************************************
list John Thurston
▸
On 6/11/2013 2:58 PM, John Palys wrote:
I am having an issue with the fqdn and big brother bb18c version using BBWIN client version 1.1.
Are you talking about a BBWIN client talking to a BB 1.8c server? As I recall, there was an FQDN flag which needed to be set TRUE in the bb-server config file. However, I don't recall in which version of BB this was added.
Any solutions?
Stand up a xymon server :)
▸
--
Do things because you should, not just because you can.
John Thurston XXX-XXX-XXXX
user-ce4d79d99bab@xymon.invalid
Enterprise Technology Services
Department of Administration
State of Alaska