boom FAQ
Q: What is the default login/password?
The default user/password for the boom Client is: admin/admin
Q: I added a new Agent to the server and it is displayed as
 (X) host.domain.net?
What does the "(X)" mean?
This Agent is disabled. This will happen if you reached the maximum number of licensed Agents on the boom
Server or if this Agent has been disabled manually from the boom UI by an administrator.
Q: How can I extend the number of licensed Agents/Hosts/Users?
Please contact our Sales team.
Q: How can I add a license to the boom Server?
Please read the documentation page: Licensing
Q: What is the difference between Free Edition and Enterprise Edition?
The differences are only the limitations off the number of Agents and Users that can concurrently connect to the
boom Server and the number of monitored Hosts that can be processed. Some add-on modules like the HP Operations Manager/Unix
Integration Module (b2om) are not available for the Free Edition.
Q: How I can set log levels for the server or agent?
Please see remote actions in the boom Client.
 Actions -> BOOM_AGENT -> "Set Agent Log Level"
 Actions -> BOOM_SERVER -> "Set Server Log Level"
The log level changes take effect immediately.
Q: How to move a boom agent(s) to another boom server?
Please see remote action in the boom Client.
Actions -> BOOM_AGENT -> "Move to a new Server"
The selected Agent(s) will switch their data flow to the specified hostname. The old owner of the
Agents will have the possibility to assign the Agent(s) back in case of problems.
Q: I have several systems placed in different locations/offices that are connected by an Internet provider
using one proxy/router. How can I manage this without installing satellite boom servers in all locations?
For any kind of NAT environment the boom Agents must have the SHARED_IP=true parameter configured in the
<boom_agent_install_dir>/conf/agent.conf
Setting this parameter enables the boom Server to differentiate the boom Agents that are sending data using
one external IP. The boom Server recognizes such Agents as firewalled.
To enable outbound communication (e.g. server to agents) the proxy/router must be configured
with port-forwarding for each boom Agent that uses this proxy/router.
On the boom Server side the configuration of the according Agents must be changed to use
the NAT IP with the defined forward ports.
Q: Can I modify the statistic page? Or add links there to my company's internal wiki?
Of course. The html source of main page that is displayed in the Statistics view are placed in the:
<boom_server_install_dir>/srv/html/status.html
Feel free to modify this page as you need. There are no restrictions
for adding/removing/linking or changing the content. Just be aware that this page might be overwritten
if you re-install or upgrade the boom server.
Q: Why do I get the message "Monitor does not submit a value during the last polling interval"
Any Policy that is regularly triggered by the Agent expects that at least one monitor value gets submitted.
This message indicates that an executable, script or other type of trigger used in the "Call" parameter
of the Policy does not submit any monitor value to the boom Agent within last polling interval.
In other words: If you have a Policy named "MyMonitor", the Agent waits for at least one value like
MyMonitor=<doubleValue>
printed to the STDOUT or submitted by using the boommon executable/script supplied with the
boom Agent before the next polling interval is reached.
You will see this message also if you are using our VMWare boom Image and just paused the Image for
some time or if you have an Agent on a Notebook which hybernates. After continuing the system the
polling interval for some monitors has passed, so the Agent will complain that it did not receive
the expected values in time.
Q: Part of my Agents don't have access to the boom server due to the firewall rules.
But I see in the logfile and on the firewall that they keep trying to connect...
Can I put these boom Agents into silent mode?
Yes. You can put any Agent into the silent mode by setting MODE=7 in the
Agent's configuration file:
<boom_agent_install_dir>/conf/agent.conf
MODE=7 will force the Agent to silently wait for the boom Server to handle the communication and poll data.
NOTE: Before change any parameter in Agent's configuration file, please ensure that Agent is stopped.
Q: Can I create/copy a Binary Package with my scripts directly on the file system without GUI?
Yes. You can create/copy any folder under the directory:
<boom_server_install_dir>/srv/packages/
Each folder there represents a Binary Package in the boom Client UI. You don't need to restart the boom server
after such changes, just refresh the Binary tree in the UI.
Q: What databases are supported by boom?
MySQL or Oracle.
Q: Does boom have WEB UI?
The boom Server has the embedded nano-HTTP Server used for statistical views, deployments, downloads
and remote viewing of active indications. The full-featured UI is the Java UI.
Q: How do the boom components handle DB outages?
If the backend database is going down, the boom Server creates an indication ("Server lost connection with DB")
and starts trying to re-connect to the database.
All boom Agents start to buffer indications. The default buffer size on every Agent
is 3000 indications and 3000 monitor values. If the limit is reached, the Agent starts dropping oldest
indications.
The Clients will remain connected and operational, but some of the operations that require database
updates (e.g. closing/archiving indications) will be ignored by the boom server.
Q: Is it possible to run the boom Server on a cluster?
The boom server can run on Failover HA Cluster Systems. Some sample
configuration based on the Linux-HA/Pacemaker cluster installation
will be published as Whitepaper soon.
Load Balancing strategies can be realized with boom server hierarchies.
Our consulting team can work out the detailed strategy and best scenario based on
your particular environment and needs.
|
