--0-131859962-1242930530=:27567
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Hi all,=0A=0AExcuse me for polluting the list with a few questions that pro=
bably will seem odd for most readers. So, first a short intro to our system=
.=0A=0A=3D=3D=3D Introduction =3D=3D=3D=0AWhile most of you manage huge ins=
tallations and are facing problems when scaling Nagios to really large netw=
orks, we are running in the opposite direction. We are currently helping a =
customer developing a small network appliance. It will be used in small iso=
lated networks, typically only about 20-30 nodes and ~100 services, maximum=
of say 200 nodes and maybe 1000 services. Typical nodes are Windows server=
s, switches, and PLC:s in an industrial automation environment. Since we ar=
e talking many (>100) small isolated networks with occational call-ins (~ o=
nce a month) and harsh environment we decided to go embedded in order to mi=
nimize administration. Think of it as a HW based spy. Install, get out and =
forget.=0A=0AThe current base implementation is about 30MB of disk space. I=
dle RAM is around 30MB but typically vary in the range 80-200MB depending o=
n configuration. It runs very well on solid-state Soekris boxes (433-500MHz=
, 256-512MB, 2GB CF). The rest of the 2GB CF is used for data storage. Cons=
equently, there are a few areas where our system design probably differs fr=
om most Nagios users. Our major concern for the future is the footprint (bo=
th RAM and disk). This far performance does not seem to be a problem.=0A=0A=
I think you get the picture, but here are some more details:=0A* BusyBox ba=
sed environment. 500kB for most of the OS utilities, including a bourne she=
ll, is really geat. Add 2MB for the Linux kernel including its modules and =
you have the base for our system.=0A* Just basic plain perl, no CPAN stuff.=
(looking at microperl, compatibility?)=0A* Currently apache2, mainly becau=
se lack of time. Investigating alternatives (BB httpd seems snug).=0A* Main=
software include Nagios, PNP, rrdtool, nmap and tcpdump. Trying to move aw=
ay from PHP though.=0A* No databases. This has implications on gui and conf=
iguration.=0A* All wrapped up in a SquashFS file with UnionFS for the data =
storage.=0A* No additional intalls on the target nodes. No plugins, just pl=
ain SNMP and network sniffs for now. IPMI is in the pipeline and WMI is bei=
ng investigated.=0A=0AA first pilot installation will take place next week =
and the main roll out is planned for the end of this year.=0A=0A=3D=3D=3D Q=
uestions =3D=3D=3D=0ANow some inquiries:=0A=0A* What about the future of Na=
gios? I am thinking about the need for database support, perl, PHP and othe=
r heavy weight stuff.=0A* Anyone knows about a SQLite based management for =
Nagios (config and GUI)? The advantage of database support is obvious, but =
the footprint and administration of ordinary DBs are too much for this pupp=
y.=0A* Does Nagios embedded perl play with microperl? I know about the modu=
le limitations with microperl, but we try to avoid them anyway.=0A* Future =
path for our plugins? Currently we use basic perl, shell and C. What are th=
e implications of skipping perl and just go for plain C and shell?=0A* Comm=
ents and thoughts from anyone with experience of similar setups whould be m=
uch appreciated.=0A=0APlease feel free to comment on anything. (I aleady kn=
ow about the lack of sanity, but apart from that
____________________________________=0ASven-G=F6ran Bergh=0ASystemasis AB=
=0A______________________________________________=0A=0A=0A=0A ________=
__________________________________________________=0AL=E5na pengar utan s=
=E4kerhet. J=E4mf=F6r vilkor online hos Kelkoo.=0Ahttp://www.kelkoo.se/c-10=
0390123-lan-utan-sakerhet.html?partnerId=3D96915014
--0-131859962-1242930530=:27567
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
<div style=3D"font-family
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]