diff --git a/pandora_doc/ChangeLog b/pandora_doc/ChangeLog index 4c475257f0..99aa7fd6c5 100644 --- a/pandora_doc/ChangeLog +++ b/pandora_doc/ChangeLog @@ -1,3 +1,8 @@ +2007-04-12 Manuel Arostegui + + * fr/*: Added to reposistory. French translation + by Denis Chupau. Almost done, but not finished yet. + 2007-04-11 Manuel Arostegui * en/pandora_quick_install.xml: Added information about diff --git a/pandora_doc/fr/fdl.xml b/pandora_doc/fr/fdl.xml new file mode 100644 index 0000000000..211fd2720d --- /dev/null +++ b/pandora_doc/fr/fdl.xml @@ -0,0 +1,663 @@ + + + + + Version 1.1, March 2000 + + + 2000Free Software Foundation, Inc. + + + +
Free Software Foundation, Inc. 59 Temple Place, + Suite 330, Boston, MA + 02111-1307 USA
+ Everyone is permitted to copy and distribute verbatim copies of this + license document, but changing it is not allowed. + + + + GNU Free Documentation License + + + 0. PREAMBLE + + The purpose of this License is to make a manual, textbook, or + other written document free in the sense of + freedom: to assure everyone the effective freedom to copy and + redistribute it, with or without modifying it, either + commercially or noncommercially. Secondarily, this License + preserves for the author and publisher a way to get credit for + their work, while not being considered responsible for + modifications made by others. + + + + This License is a kind of copyleft, which means + that derivative works of the document must themselves be free in + the same sense. It complements the GNU General Public License, + which is a copyleft license designed for free software. + + + + We have designed this License in order to use it for manuals for + free software, because free software needs free documentation: a + free program should come with manuals providing the same + freedoms that the software does. But this License is not limited + to software manuals; it can be used for any textual work, + regardless of subject matter or whether it is published as a + printed book. We recommend this License principally for works + whose purpose is instruction or reference. + + + + 1. APPLICABILITY AND DEFINITIONS + + This License applies to any manual or other work that contains a + notice placed by the copyright holder saying it can be + distributed under the terms of this License. The + Document, below, refers to any such manual or + work. Any member of the public is a licensee, and is addressed + as you. + + + + A Modified Version of the Document means any work + containing the Document or a portion of it, either copied + verbatim, or with modifications and/or translated into another + language. + + + + A Secondary Section is a named appendix or a + front-matter section of the Document that deals exclusively + with the relationship of the publishers or authors of the + Document to the Document's overall subject (or to related + matters) and contains nothing that could fall directly within + that overall subject. (For example, if the Document is in part a + textbook of mathematics, a Secondary Section may not explain any + mathematics.) The relationship could be a matter of historical + connection with the subject or with related matters, or of + legal, commercial, philosophical, ethical or political position + regarding them. + + + + The Invariant Sections are certain Secondary Sections whose titles + are designated, as being those of Invariant Sections, in the + notice that says that the Document is released under this + License. + + + + The Cover Texts are certain short passages of + text that are listed, as Front-Cover Texts or Back-Cover Texts, + in the notice that says that the Document is released under this + License. + + + + A Transparent copy of the Document means a machine-readable + copy, represented in a format whose specification is available + to the general public, whose contents can be viewed and edited + directly and straightforwardly with generic text editors or (for + images composed of pixels) generic paint programs or (for + drawings) some widely available drawing editor, and that is + suitable for input to text formatters or for automatic + translation to a variety of formats suitable for input to text + formatters. A copy made in an otherwise Transparent file format + whose markup has been designed to thwart or discourage + subsequent modification by readers is not Transparent. A copy + that is not Transparent is called + Opaque. + + + + Examples of suitable formats for Transparent copies include + plain ASCII without markup, Texinfo input format, LaTeX input + format, SGML or XML using a publicly available DTD, and + standard-conforming simple HTML designed for human + modification. Opaque formats include PostScript, PDF, + proprietary formats that can be read and edited only by + proprietary word processors, SGML or XML for which the DTD + and/or processing tools are not generally available, and the + machine-generated HTML produced by some word processors for + output purposes only. + + + + The Title Page means, for a printed book, the + title page itself, plus such following pages as are needed to + hold, legibly, the material this License requires to appear in + the title page. For works in formats which do not have any title + page as such, Title Page means the text near the + most prominent appearance of the work's title, preceding the + beginning of the body of the text. + + + + + 2. VERBATIM COPYING + + You may copy and distribute the Document in any medium, either + commercially or noncommercially, provided that this License, the + copyright notices, and the license notice saying this License + applies to the Document are reproduced in all copies, and that + you add no other conditions whatsoever to those of this + License. You may not use technical measures to obstruct or + control the reading or further copying of the copies you make or + distribute. However, you may accept compensation in exchange for + copies. If you distribute a large enough number of copies you + must also follow the conditions in section 3. + + + + You may also lend copies, under the same conditions stated + above, and you may publicly display copies. + + + + + 3. COPYING IN QUANTITY + + If you publish printed copies of the Document numbering more than 100, + and the Document's license notice requires Cover Texts, you must enclose + the copies in covers that carry, clearly and legibly, all these + Cover Texts: Front-Cover Texts on the front cover, and + Back-Cover Texts on the back cover. Both covers must also + clearly and legibly identify you as the publisher of these + copies. The front cover must present the full title with all + words of the title equally prominent and visible. You may add + other material on the covers in addition. Copying with changes + limited to the covers, as long as they preserve the title of the + Document and satisfy these + conditions, can be treated as verbatim copying in other + respects. + + + + If the required texts for either cover are too voluminous to fit + legibly, you should put the first ones listed (as many as fit + reasonably) on the actual cover, and continue the rest onto + adjacent pages. + + + + If you publish or distribute Opaque copies of the Document numbering more than 100, + you must either include a machine-readable Transparent copy along with + each Opaque copy, or state in or with each Opaque copy a + publicly-accessible computer-network location containing a + complete Transparent copy of the Document, free of added + material, which the general network-using public has access to + download anonymously at no charge using public-standard network + protocols. If you use the latter option, you must take + reasonably prudent steps, when you begin distribution of Opaque + copies in quantity, to ensure that this Transparent copy will + remain thus accessible at the stated location until at least one + year after the last time you distribute an Opaque copy (directly + or through your agents or retailers) of that edition to the + public. + + + + It is requested, but not required, that you contact the authors + of the Document well before + redistributing any large number of copies, to give them a chance + to provide you with an updated version of the Document. + + + + + 4. MODIFICATIONS + + You may copy and distribute a Modified Version of the Document under the conditions of + sections 2 and 3 above, provided that you release + the Modified Version under precisely this License, with the + Modified Version filling the role of the Document, thus + licensing distribution and modification of the Modified Version + to whoever possesses a copy of it. In addition, you must do + these things in the Modified Version: + + + + + + A + + Use in the Title + Page (and on the covers, if any) a title distinct + from that of the Document, and from those of + previous versions (which should, if there were any, be + listed in the History section of the Document). You may + use the same title as a previous version if the original + publisher of that version gives permission. + + + + + + + B + + List on the Title + Page, as authors, one or more persons or entities + responsible for authorship of the modifications in the + Modified Version, + together with at least five of the principal authors of + the Document (all of + its principal authors, if it has less than five). + + + + + + + C + + State on the Title + Page the name of the publisher of the Modified Version, as the + publisher. + + + + + + + D + + Preserve all the copyright notices of the Document. + + + + + + + E + + Add an appropriate copyright notice for your modifications + adjacent to the other copyright notices. + + + + + + + F + + Include, immediately after the copyright notices, a + license notice giving the public permission to use the + Modified Version under + the terms of this License, in the form shown in the + Addendum below. + + + + + + + G + + Preserve in that license notice the full lists of Invariant Sections and + required Cover + Texts given in the Document's license notice. + + + + + + + H + + Include an unaltered copy of this License. + + + + + + + I + + Preserve the section entitled History, and + its title, and add to it an item stating at least the + title, year, new authors, and publisher of the Modified Version as given on + the Title Page. If + there is no section entitled History in the + Document, create one + stating the title, year, authors, and publisher of the + Document as given on its Title Page, then add an item + describing the Modified Version as stated in the previous + sentence. + + + + + + + J + + Preserve the network location, if any, given in the Document for public access + to a Transparent + copy of the Document, and likewise the network locations + given in the Document for previous versions it was based + on. These may be placed in the History + section. You may omit a network location for a work that + was published at least four years before the Document + itself, or if the original publisher of the version it + refers to gives permission. + + + + + + + K + + In any section entitled Acknowledgements or + Dedications, preserve the section's title, + and preserve in the section all the substance and tone of + each of the contributor acknowledgements and/or + dedications given therein. + + + + + + + L + + Preserve all the Invariant + Sections of the Document, unaltered in their + text and in their titles. Section numbers or the + equivalent are not considered part of the section titles. + + + + + + + M + + Delete any section entitled + Endorsements. Such a section may not be + included in the Modified + Version. + + + + + + + N + + Do not retitle any existing section as + Endorsements or to conflict in title with + any Invariant + Section. + + + + + + + If the Modified Version + includes new front-matter sections or appendices that qualify as + Secondary Sections and + contain no material copied from the Document, you may at your + option designate some or all of these sections as invariant. To + do this, add their titles to the list of Invariant Sections in the + Modified Version's license notice. These titles must be + distinct from any other section titles. + + + + You may add a section entitled Endorsements, + provided it contains nothing but endorsements of your Modified Version by various + parties--for example, statements of peer review or that the text + has been approved by an organization as the authoritative + definition of a standard. + + + + You may add a passage of up to five words as a Front-Cover Text, and a passage + of up to 25 words as a Back-Cover Text, to the end of + the list of Cover Texts + in the Modified Version. + Only one passage of Front-Cover Text and one of Back-Cover Text + may be added by (or through arrangements made by) any one + entity. If the Document + already includes a cover text for the same cover, previously + added by you or by arrangement made by the same entity you are + acting on behalf of, you may not add another; but you may + replace the old one, on explicit permission from the previous + publisher that added the old one. + + + + The author(s) and publisher(s) of the Document do not by this License + give permission to use their names for publicity for or to + assert or imply endorsement of any Modified Version . + + + + + 5. COMBINING DOCUMENTS + + You may combine the Document + with other documents released under this License, under the + terms defined in section 4 + above for modified versions, provided that you include in the + combination all of the Invariant + Sections of all of the original documents, unmodified, + and list them all as Invariant Sections of your combined work in + its license notice. + + + + The combined work need only contain one copy of this License, + and multiple identical Invariant + Sections may be replaced with a single copy. If there are + multiple Invariant Sections with the same name but different + contents, make the title of each such section unique by adding + at the end of it, in parentheses, the name of the original + author or publisher of that section if known, or else a unique + number. Make the same adjustment to the section titles in the + list of Invariant Sections in the license notice of the combined + work. + + + + In the combination, you must combine any sections entitled + History in the various original documents, + forming one section entitled History; likewise + combine any sections entitled Acknowledgements, + and any sections entitled Dedications. You must + delete all sections entitled Endorsements. + + + + + 6. COLLECTIONS OF DOCUMENTS + + You may make a collection consisting of the Document and other documents + released under this License, and replace the individual copies + of this License in the various documents with a single copy that + is included in the collection, provided that you follow the + rules of this License for verbatim copying of each of the + documents in all other respects. + + + + You may extract a single document from such a collection, and + dispbibute it individually under this License, provided you + insert a copy of this License into the extracted document, and + follow this License in all other respects regarding verbatim + copying of that document. + + + + + 7. AGGREGATION WITH INDEPENDENT WORKS + + A compilation of the Document or its derivatives with + other separate and independent documents or works, in or on a + volume of a storage or distribution medium, does not as a whole + count as a Modified Version + of the Document, provided no compilation copyright is claimed + for the compilation. Such a compilation is called an + aggregate, and this License does not apply to the + other self-contained works thus compiled with the Document , on + account of their being thus compiled, if they are not themselves + derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these + copies of the Document, then if the Document is less than one + quarter of the entire aggregate, the Document's Cover Texts may + be placed on covers that surround only the Document within the + aggregate. Otherwise they must appear on covers around the whole + aggregate. + + + + + 8. TRANSLATION + + Translation is considered a kind of modification, so you may + distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with + translations requires special permission from their copyright + holders, but you may include translations of some or all + Invariant Sections in addition to the original versions of these + Invariant Sections. You may include a translation of this + License provided that you also include the original English + version of this License. In case of a disagreement between the + translation and the original English version of this License, + the original English version will prevail. + + + + + 9. TERMINATION + + You may not copy, modify, sublicense, or distribute the Document except as expressly + provided for under this License. Any other attempt to copy, + modify, sublicense or distribute the Document is void, and will + automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this + License will not have their licenses terminated so long as such + parties remain in full compliance. + + + + + 10. FUTURE REVISIONS OF THIS LICENSE + + The Free Software + Foundation may publish new, revised versions of the GNU + Free Documentation License from time to time. Such new versions + will be similar in spirit to the present version, but may differ + in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. + + + + Each version of the License is given a distinguishing version + number. If the Document + specifies that a particular numbered version of this License + or any later version applies to it, you have the + option of following the terms and conditions either of that + specified version or of any later version that has been + published (not as a draft) by the Free Software Foundation. If + the Document does not specify a version number of this License, + you may choose any version ever published (not as a draft) by + the Free Software Foundation. + + + + + Addendum + + To use this License in a document you have written, include a copy of + the License in the document and put the following copyright and + license notices just after the title page: + + +
+ + Copyright © YEAR YOUR NAME. + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the + Free Software Foundation; with the Invariant Sections being LIST + THEIR TITLES, with the Front-Cover Texts being LIST, + and with the Back-Cover + Texts being LIST. A copy of the license is included in + the section entitled GNU Free Documentation + License. + +
+ + + If you have no Invariant + Sections, write with no Invariant Sections + instead of saying which ones are invariant. If you have no + Front-Cover Texts, write + no Front-Cover Texts instead of + Front-Cover Texts being LIST; likewise for Back-Cover Texts. + + + + If your document contains nontrivial examples of program code, + we recommend releasing these examples in parallel under your + choice of free software license, such as the GNU General Public + License, to permit their use in free software. + + + + + + + + + diff --git a/pandora_doc/fr/gpl.xml b/pandora_doc/fr/gpl.xml new file mode 100644 index 0000000000..9652ab21c0 --- /dev/null +++ b/pandora_doc/fr/gpl.xml @@ -0,0 +1,381 @@ + + + + GNU General Public License + Version 2, June 1991 + + 1989, 1991 + Free Software Foundation, Inc. + + + +
Free Software Foundation, Inc. + 51 Franklin Street, Fifth Floor, + Boston, + MA + 02110-1301 + USA +
+ + + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + + Version 2, June 1991 + + GNU General Public License +
+ Preamble + + The licenses for most software are designed to take away your + freedom to share and change it. By contrast, the GNU General + Public License is intended to guarantee your freedom to share + and change free software - to make sure the software is free for + all its users. This General Public License applies to most of + the Free Software Foundation's software and to any other + program whose authors commit to using it. (Some other Free + Software Foundation software is covered by the GNU Library + General Public License instead.) You can apply it to your + programs, too. + + + + When we speak of free software, we are referring to freedom, not + price. Our General Public Licenses are designed to make sure + that you have the freedom to distribute copies of free software + (and charge for this service if you wish), that you receive + source code or can get it if you want it, that you can change + the software or use pieces of it in new free programs; and that + you know you can do these things. + + + + To protect your rights, we need to make restrictions that forbid + anyone to deny you these rights or to ask you to surrender the + rights. These restrictions translate to certain responsibilities + for you if you distribute copies of the software, or if you + modify it. + + + + For example, if you distribute copies of such a program, whether + gratis or for a fee, you must give the recipients all the rights + that you have. You must make sure that they, too, receive or can + get the source code. And you must show them these terms so they + know their rights. + + + We protect your rights with two steps: + + + copyright the software, and + + + offer you this license which gives you legal permission to copy, + distribute and/or modify the software. + + + + + Also, for each author's protection and ours, we want to make certain that + everyone understands that there is no warranty for this free software. If + the software is modified by someone else and passed on, we want its + recipients to know that what they have is not the original, so that any + problems introduced by others will not reflect on the original authors' + reputations. + + Finally, any free program is threatened constantly by software patents. + We wish to avoid the danger that redistributors of a free program will + individually obtain patent licenses, in effect making the program + proprietary. To prevent this, we have made it clear that any patent must be + licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and modification + follow. +
+
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION +
+ Section 0 + This License applies to any program or other work which contains a notice + placed by the copyright holder saying it may be distributed under the terms + of this General Public License. The Program, below, refers to any such + program or work, and a + work based on the Program means either + the Program or any derivative work under copyright law: that is to say, a + work containing the Program or a portion of it, either verbatim or with + modifications and/or translated into another language. (Hereinafter, translation + is included without limitation in the term + modification.) Each licensee is addressed as you. + + Activities other than copying, distribution and modification are not covered by + this License; they are outside its scope. The act of running the Program is not + restricted, and the output from the Program is covered only if its contents + constitute a work based on the Program (independent of having been made by running + the Program). Whether that is true depends on what the Program does. +
+
+ Section 1 + You may copy and distribute verbatim copies of the Program's source code as you + receive it, in any medium, provided that you conspicuously and appropriately + publish on each copy an appropriate copyright notice and disclaimer of warranty; + keep intact all the notices that refer to this License and to the absence of any + warranty; and give any other recipients of the Program a copy of this License + along with the Program. + + You may charge a fee for the physical act of transferring a copy, and you may at + your option offer warranty protection in exchange for a fee. +
+
+ Section 2 + You may modify your copy or copies of the Program or any portion of it, thus + forming a work based on the Program, and copy and distribute such modifications + or work under the terms of + Section 1 above, provided + that you also meet all of these conditions: + + + You must cause the modified files to carry prominent notices stating that + you changed the files and the date of any change. + + + You must cause any work that you distribute or publish, that in whole or + in part contains or is derived from the Program or any part thereof, to be + licensed as a whole at no charge to all third parties under the terms of + this License. + + + If the modified program normally reads commands interactively when run, you + must cause it, when started running for such interactive use in the most + ordinary way, to print or display an announcement including an appropriate + copyright notice and a notice that there is no warranty (or else, saying + that you provide a warranty) and that users may redistribute the program + under these conditions, and telling the user how to view a copy of this + License. (Exception: If the Program itself is interactive but does not + normally print such an announcement, your work based on the Program is not + required to print an announcement.) + + + + + These requirements apply to the modified work as a whole. If identifiable sections + of that work are not derived from the Program, and can be reasonably considered + independent and separate works in themselves, then this License, and its terms, + do not apply to those sections when you distribute them as separate works. But when + you distribute the same sections as part of a whole which is a work based on the + Program, the distribution of the whole must be on the terms of this License, whose + permissions for other licensees extend to the entire whole, and thus to each and + every part regardless of who wrote it. + + Thus, it is not the intent of this section to claim rights or contest your rights + to work written entirely by you; rather, the intent is to exercise the right to control + the distribution of derivative or collective works based on the Program. + + In addition, mere aggregation of another work not based on the Program with the Program + (or with a work based on the Program) on a volume of a storage or distribution medium + does not bring the other work under the scope of this License. +
+
+ Section 3 + You may copy and distribute the Program (or a work based on it, under + Section 2 in object code or executable form under the terms of + Sections 1 and + 2 above provided that you also do one of the following: + + + Accompany it with the complete corresponding machine-readable source code, which + must be distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + + Accompany it with a written offer, valid for at least three years, to give any + third party, for a charge no more than your cost of physically performing source + distribution, a complete machine-readable copy of the corresponding source code, + to be distributed under the terms of Sections 1 and 2 above on a medium customarily + used for software interchange; or, + + + Accompany it with the information you received as to the offer to distribute + corresponding source code. (This alternative is allowed only for noncommercial + distribution and only if you received the program in object code or executable form + with such an offer, in accord with Subsection b above.) + + + + + The source code for a work means the preferred form of the work for making modifications + to it. For an executable work, complete source code means all the source code for all modules + it contains, plus any associated interface definition files, plus the scripts used to control + compilation and installation of the executable. However, as a special exception, the source + code distributed need not include anything that is normally distributed (in either source or + binary form) with the major components (compiler, kernel, and so on) of the operating system + on which the executable runs, unless that component itself accompanies the executable. + + If distribution of executable or object code is made by offering access to copy from a + designated place, then offering equivalent access to copy the source code from the same place + counts as distribution of the source code, even though third parties are not compelled to + copy the source along with the object code. +
+
+ Section 4 + You may not copy, modify, sublicense, or distribute the Program except as expressly provided + under this License. Any attempt otherwise to copy, modify, sublicense or distribute the + Program is void, and will automatically terminate your rights under this License. However, + parties who have received copies, or rights, from you under this License will not have their + licenses terminated so long as such parties remain in full compliance. +
+
+ Section 5 + You are not required to accept this License, since you have not signed it. However, nothing + else grants you permission to modify or distribute the Program or its derivative works. + These actions are prohibited by law if you do not accept this License. Therefore, by modifying + or distributing the Program (or any work based on the Program), you indicate your acceptance + of this License to do so, and all its terms and conditions for copying, distributing or + modifying the Program or works based on it. +
+
+ Section 6 + Each time you redistribute the Program (or any work based on the Program), the recipient + automatically receives a license from the original licensor to copy, distribute or modify + the Program subject to these terms and conditions. You may not impose any further restrictions + on the recipients' exercise of the rights granted herein. You are not responsible for enforcing + compliance by third parties to this License. +
+
+ Section 7 + If, as a consequence of a court judgment or allegation of patent infringement or for any other + reason (not limited to patent issues), conditions are imposed on you (whether by court order, + agreement or otherwise) that contradict the conditions of this License, they do not excuse you + from the conditions of this License. If you cannot distribute so as to satisfy simultaneously + your obligations under this License and any other pertinent obligations, then as a consequence + you may not distribute the Program at all. For example, if a patent license would not permit + royalty-free redistribution of the Program by all those who receive copies directly or + indirectly through you, then the only way you could satisfy both it and this License would be + to refrain entirely from distribution of the Program. + + If any portion of this section is held invalid or unenforceable under any particular circumstance, + the balance of the section is intended to apply and the section as a whole is intended to apply + in other circumstances. + + It is not the purpose of this section to induce you to infringe any patents or other property + right claims or to contest validity of any such claims; this section has the sole purpose of + protecting the integrity of the free software distribution system, which is implemented by public + license practices. Many people have made generous contributions to the wide range of software + distributed through that system in reliance on consistent application of that system; it is up + to the author/donor to decide if he or she is willing to distribute software through any other + system and a licensee cannot impose that choice. + + This section is intended to make thoroughly clear what is believed to be a consequence of the + rest of this License. +
+
+ Section 8 + If the distribution and/or use of the Program is restricted in certain countries either by patents + or by copyrighted interfaces, the original copyright holder who places the Program under this License + may add an explicit geographical distribution limitation excluding those countries, so that + distribution is permitted only in or among countries not thus excluded. In such case, this License + incorporates the limitation as if written in the body of this License. +
+
+ Section 9 + The Free Software Foundation may publish revised and/or new versions of the General Public License + from time to time. Such new versions will be similar in spirit to the present version, but may differ + in detail to address new problems or concerns. + + Each version is given a distinguishing version number. If the Program specifies a version number of + this License which applies to it and any later version, you have the option of following the terms + and conditions either of that version or of any later version published by the Free Software + Foundation. If the Program does not specify a version number of this License, you may choose any + version ever published by the Free Software Foundation. +
+
+ Section 10 + If you wish to incorporate parts of the Program into other free programs whose distribution + conditions are different, write to the author to ask for permission. For software which is copyrighted + by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions + for this. Our decision will be guided by the two goals of preserving the free status of all + derivatives of our free software and of promoting the sharing and reuse of software generally. +
+
+ NO WARRANTY Section 11 + BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT + PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR + OTHER PARTIES PROVIDE THE PROGRAM AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, + INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE + PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. +
+
+ Section 12 + IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR + ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU + FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE + USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED + INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH + ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH + DAMAGES. + + END OF TERMS AND CONDITIONS +
+
+
+ How to Apply These Terms to Your New Programs + If you develop a new program, and you want it to be of the greatest + possible use to the public, the best way to achieve this is to make it + free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest + to attach them to the start of each source file to most effectively + convey the exclusion of warranty; and each file should have at least + the copyright line and a pointer to where the full notice is found. + + <one line to give the program's name and a brief idea of what it does.> + Copyright (C) <year> <name of author> + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License + along with this program; if not, write to the Free Software + Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + + Also add information on how to contact you by electronic and paper mail. + + If the program is interactive, make it output a short notice like this + when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type show w. + This is free software, and you are welcome to redistribute it + under certain conditions; type show c for details. + + The hypothetical commands show w and show c should + show the appropriate parts of the General Public License. Of course, the commands you + use may be called something other than show w and show c; + they could even be mouse-clicks or menu items--whatever suits your program. + + You should also get your employer (if you work as a programmer) or your + school, if any, to sign a copyright disclaimer for the program, if + necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + Gnomovision (which makes passes at compilers) written by James Hacker. + + <signature of Ty Coon>, 1 April 1989 + Ty Coon, President of Vice + + This General Public License does not permit incorporating your program into + proprietary programs. If your program is a subroutine library, you may + consider it more useful to permit linking proprietary applications with the + library. If this is what you want to do, use the GNU Library General + Public License instead of this License. +
+ diff --git a/pandora_doc/fr/images/1.jpg b/pandora_doc/fr/images/1.jpg new file mode 100644 index 0000000000..c8c0a354bd Binary files /dev/null and b/pandora_doc/fr/images/1.jpg differ diff --git a/pandora_doc/fr/images/2.jpg b/pandora_doc/fr/images/2.jpg new file mode 100644 index 0000000000..39535209f7 Binary files /dev/null and b/pandora_doc/fr/images/2.jpg differ diff --git a/pandora_doc/fr/images/3.jpg b/pandora_doc/fr/images/3.jpg new file mode 100644 index 0000000000..d0c243271a Binary files /dev/null and b/pandora_doc/fr/images/3.jpg differ diff --git a/pandora_doc/fr/images/4.jpg b/pandora_doc/fr/images/4.jpg new file mode 100644 index 0000000000..14ef867c25 Binary files /dev/null and b/pandora_doc/fr/images/4.jpg differ diff --git a/pandora_doc/fr/images/5.jpg b/pandora_doc/fr/images/5.jpg new file mode 100644 index 0000000000..d918a4effa Binary files /dev/null and b/pandora_doc/fr/images/5.jpg differ diff --git a/pandora_doc/fr/images/6.jpg b/pandora_doc/fr/images/6.jpg new file mode 100644 index 0000000000..2b6835708b Binary files /dev/null and b/pandora_doc/fr/images/6.jpg differ diff --git a/pandora_doc/fr/images/DBText.png b/pandora_doc/fr/images/DBText.png new file mode 100644 index 0000000000..07924350ec Binary files /dev/null and b/pandora_doc/fr/images/DBText.png differ diff --git a/pandora_doc/fr/images/Pandora_DataServer_Diagram.png b/pandora_doc/fr/images/Pandora_DataServer_Diagram.png new file mode 100755 index 0000000000..bebdf99c0c Binary files /dev/null and b/pandora_doc/fr/images/Pandora_DataServer_Diagram.png differ diff --git a/pandora_doc/fr/images/Pandora_NetworkServer_Diagram.png b/pandora_doc/fr/images/Pandora_NetworkServer_Diagram.png new file mode 100755 index 0000000000..c18ea2748b Binary files /dev/null and b/pandora_doc/fr/images/Pandora_NetworkServer_Diagram.png differ diff --git a/pandora_doc/fr/images/Pandora_SNMP_Diagram.png b/pandora_doc/fr/images/Pandora_SNMP_Diagram.png new file mode 100755 index 0000000000..839777c483 Binary files /dev/null and b/pandora_doc/fr/images/Pandora_SNMP_Diagram.png differ diff --git a/pandora_doc/fr/images/SNMP_alert.png b/pandora_doc/fr/images/SNMP_alert.png new file mode 100644 index 0000000000..3ac2304df4 Binary files /dev/null and b/pandora_doc/fr/images/SNMP_alert.png differ diff --git a/pandora_doc/fr/images/SNMP_alert_create.png b/pandora_doc/fr/images/SNMP_alert_create.png new file mode 100644 index 0000000000..dbfa89c665 Binary files /dev/null and b/pandora_doc/fr/images/SNMP_alert_create.png differ diff --git a/pandora_doc/fr/images/SNMP_alert_create1.png b/pandora_doc/fr/images/SNMP_alert_create1.png new file mode 100644 index 0000000000..762e89b05a Binary files /dev/null and b/pandora_doc/fr/images/SNMP_alert_create1.png differ diff --git a/pandora_doc/fr/images/SNMP_console.png b/pandora_doc/fr/images/SNMP_console.png new file mode 100644 index 0000000000..3c2abca4ba Binary files /dev/null and b/pandora_doc/fr/images/SNMP_console.png differ diff --git a/pandora_doc/fr/images/access_graph_full.jpg b/pandora_doc/fr/images/access_graph_full.jpg new file mode 100644 index 0000000000..cc74407caf Binary files /dev/null and b/pandora_doc/fr/images/access_graph_full.jpg differ diff --git a/pandora_doc/fr/images/access_graph_peak.jpg b/pandora_doc/fr/images/access_graph_peak.jpg new file mode 100644 index 0000000000..2be141f366 Binary files /dev/null and b/pandora_doc/fr/images/access_graph_peak.jpg differ diff --git a/pandora_doc/fr/images/b_blue.png b/pandora_doc/fr/images/b_blue.png new file mode 100644 index 0000000000..98a44fda20 Binary files /dev/null and b/pandora_doc/fr/images/b_blue.png differ diff --git a/pandora_doc/fr/images/b_down.png b/pandora_doc/fr/images/b_down.png new file mode 100644 index 0000000000..bd0dd41edf Binary files /dev/null and b/pandora_doc/fr/images/b_down.png differ diff --git a/pandora_doc/fr/images/b_green.png b/pandora_doc/fr/images/b_green.png new file mode 100644 index 0000000000..9e36b27901 Binary files /dev/null and b/pandora_doc/fr/images/b_green.png differ diff --git a/pandora_doc/fr/images/b_red.png b/pandora_doc/fr/images/b_red.png new file mode 100644 index 0000000000..d73caaaf56 Binary files /dev/null and b/pandora_doc/fr/images/b_red.png differ diff --git a/pandora_doc/fr/images/b_white.png b/pandora_doc/fr/images/b_white.png new file mode 100644 index 0000000000..e188dbdb6f Binary files /dev/null and b/pandora_doc/fr/images/b_white.png differ diff --git a/pandora_doc/fr/images/b_yellow.png b/pandora_doc/fr/images/b_yellow.png new file mode 100644 index 0000000000..94fcec7922 Binary files /dev/null and b/pandora_doc/fr/images/b_yellow.png differ diff --git a/pandora_doc/fr/images/cancel.png b/pandora_doc/fr/images/cancel.png new file mode 100644 index 0000000000..6ab6ca13c4 Binary files /dev/null and b/pandora_doc/fr/images/cancel.png differ diff --git a/pandora_doc/fr/images/config.png b/pandora_doc/fr/images/config.png new file mode 100644 index 0000000000..17ebecec9f Binary files /dev/null and b/pandora_doc/fr/images/config.png differ diff --git a/pandora_doc/fr/images/convert.sh b/pandora_doc/fr/images/convert.sh new file mode 100755 index 0000000000..046f174670 --- /dev/null +++ b/pandora_doc/fr/images/convert.sh @@ -0,0 +1,8 @@ +#!/bin/bash + +for a in `ls *.gif` +do + nombre=`echo $a | cut -f 1 -d "." ` + convert $nombre.gif $nombre.png +done + diff --git a/pandora_doc/fr/images/data_d.png b/pandora_doc/fr/images/data_d.png new file mode 100644 index 0000000000..0a1664e726 Binary files /dev/null and b/pandora_doc/fr/images/data_d.png differ diff --git a/pandora_doc/fr/images/data_m.png b/pandora_doc/fr/images/data_m.png new file mode 100644 index 0000000000..525af801f1 Binary files /dev/null and b/pandora_doc/fr/images/data_m.png differ diff --git a/pandora_doc/fr/images/data_w.png b/pandora_doc/fr/images/data_w.png new file mode 100644 index 0000000000..84e7724e79 Binary files /dev/null and b/pandora_doc/fr/images/data_w.png differ diff --git a/pandora_doc/fr/images/dot_blue.png b/pandora_doc/fr/images/dot_blue.png new file mode 100644 index 0000000000..cf4323374a Binary files /dev/null and b/pandora_doc/fr/images/dot_blue.png differ diff --git a/pandora_doc/fr/images/dot_down.png b/pandora_doc/fr/images/dot_down.png new file mode 100644 index 0000000000..fa10485103 Binary files /dev/null and b/pandora_doc/fr/images/dot_down.png differ diff --git a/pandora_doc/fr/images/dot_green.png b/pandora_doc/fr/images/dot_green.png new file mode 100644 index 0000000000..20ed4ac8a9 Binary files /dev/null and b/pandora_doc/fr/images/dot_green.png differ diff --git a/pandora_doc/fr/images/dot_red.png b/pandora_doc/fr/images/dot_red.png new file mode 100644 index 0000000000..3d2b3ca2d7 Binary files /dev/null and b/pandora_doc/fr/images/dot_red.png differ diff --git a/pandora_doc/fr/images/dot_white.png b/pandora_doc/fr/images/dot_white.png new file mode 100644 index 0000000000..3253384b96 Binary files /dev/null and b/pandora_doc/fr/images/dot_white.png differ diff --git a/pandora_doc/fr/images/dot_yellow.png b/pandora_doc/fr/images/dot_yellow.png new file mode 100644 index 0000000000..99af86d437 Binary files /dev/null and b/pandora_doc/fr/images/dot_yellow.png differ diff --git a/pandora_doc/fr/images/esquema.png b/pandora_doc/fr/images/esquema.png new file mode 100644 index 0000000000..3205328bdd Binary files /dev/null and b/pandora_doc/fr/images/esquema.png differ diff --git a/pandora_doc/fr/images/grafica_d.png b/pandora_doc/fr/images/grafica_d.png new file mode 100644 index 0000000000..c942efc70c Binary files /dev/null and b/pandora_doc/fr/images/grafica_d.png differ diff --git a/pandora_doc/fr/images/grafica_h.png b/pandora_doc/fr/images/grafica_h.png new file mode 100644 index 0000000000..63fc92af99 Binary files /dev/null and b/pandora_doc/fr/images/grafica_h.png differ diff --git a/pandora_doc/fr/images/grafica_m.png b/pandora_doc/fr/images/grafica_m.png new file mode 100644 index 0000000000..3014e29844 Binary files /dev/null and b/pandora_doc/fr/images/grafica_m.png differ diff --git a/pandora_doc/fr/images/grafica_w.png b/pandora_doc/fr/images/grafica_w.png new file mode 100644 index 0000000000..e69fdafd00 Binary files /dev/null and b/pandora_doc/fr/images/grafica_w.png differ diff --git a/pandora_doc/fr/images/groups.png b/pandora_doc/fr/images/groups.png new file mode 100644 index 0000000000..9c1f66ea0d Binary files /dev/null and b/pandora_doc/fr/images/groups.png differ diff --git a/pandora_doc/fr/images/image001.png b/pandora_doc/fr/images/image001.png new file mode 100644 index 0000000000..0a4090aaf6 Binary files /dev/null and b/pandora_doc/fr/images/image001.png differ diff --git a/pandora_doc/fr/images/image002.png b/pandora_doc/fr/images/image002.png new file mode 100644 index 0000000000..e463bd42a6 Binary files /dev/null and b/pandora_doc/fr/images/image002.png differ diff --git a/pandora_doc/fr/images/image003.png b/pandora_doc/fr/images/image003.png new file mode 100644 index 0000000000..701c378c18 Binary files /dev/null and b/pandora_doc/fr/images/image003.png differ diff --git a/pandora_doc/fr/images/image004.png b/pandora_doc/fr/images/image004.png new file mode 100644 index 0000000000..bf7c34be9c Binary files /dev/null and b/pandora_doc/fr/images/image004.png differ diff --git a/pandora_doc/fr/images/image005.png b/pandora_doc/fr/images/image005.png new file mode 100644 index 0000000000..98bad97d99 Binary files /dev/null and b/pandora_doc/fr/images/image005.png differ diff --git a/pandora_doc/fr/images/image006.png b/pandora_doc/fr/images/image006.png new file mode 100644 index 0000000000..fe639eb561 Binary files /dev/null and b/pandora_doc/fr/images/image006.png differ diff --git a/pandora_doc/fr/images/image007.png b/pandora_doc/fr/images/image007.png new file mode 100644 index 0000000000..55252f46d1 Binary files /dev/null and b/pandora_doc/fr/images/image007.png differ diff --git a/pandora_doc/fr/images/image008.png b/pandora_doc/fr/images/image008.png new file mode 100644 index 0000000000..f67e03a163 Binary files /dev/null and b/pandora_doc/fr/images/image008.png differ diff --git a/pandora_doc/fr/images/image009.png b/pandora_doc/fr/images/image009.png new file mode 100644 index 0000000000..3594e75681 Binary files /dev/null and b/pandora_doc/fr/images/image009.png differ diff --git a/pandora_doc/fr/images/image010.png b/pandora_doc/fr/images/image010.png new file mode 100644 index 0000000000..fe9038691b Binary files /dev/null and b/pandora_doc/fr/images/image010.png differ diff --git a/pandora_doc/fr/images/image011.png b/pandora_doc/fr/images/image011.png new file mode 100644 index 0000000000..c788cd8b4f Binary files /dev/null and b/pandora_doc/fr/images/image011.png differ diff --git a/pandora_doc/fr/images/image012.png b/pandora_doc/fr/images/image012.png new file mode 100644 index 0000000000..53dc97adb0 Binary files /dev/null and b/pandora_doc/fr/images/image012.png differ diff --git a/pandora_doc/fr/images/image013.png b/pandora_doc/fr/images/image013.png new file mode 100644 index 0000000000..d73fc7df0d Binary files /dev/null and b/pandora_doc/fr/images/image013.png differ diff --git a/pandora_doc/fr/images/image014.png b/pandora_doc/fr/images/image014.png new file mode 100644 index 0000000000..612d8b113d Binary files /dev/null and b/pandora_doc/fr/images/image014.png differ diff --git a/pandora_doc/fr/images/image015.png b/pandora_doc/fr/images/image015.png new file mode 100644 index 0000000000..b11dfa7269 Binary files /dev/null and b/pandora_doc/fr/images/image015.png differ diff --git a/pandora_doc/fr/images/image016.png b/pandora_doc/fr/images/image016.png new file mode 100644 index 0000000000..655cd52742 Binary files /dev/null and b/pandora_doc/fr/images/image016.png differ diff --git a/pandora_doc/fr/images/image017.png b/pandora_doc/fr/images/image017.png new file mode 100644 index 0000000000..2ad95bc92f Binary files /dev/null and b/pandora_doc/fr/images/image017.png differ diff --git a/pandora_doc/fr/images/image018.png b/pandora_doc/fr/images/image018.png new file mode 100644 index 0000000000..9e39d2a8e4 Binary files /dev/null and b/pandora_doc/fr/images/image018.png differ diff --git a/pandora_doc/fr/images/image019.png b/pandora_doc/fr/images/image019.png new file mode 100644 index 0000000000..c41bdbca32 Binary files /dev/null and b/pandora_doc/fr/images/image019.png differ diff --git a/pandora_doc/fr/images/image020.png b/pandora_doc/fr/images/image020.png new file mode 100644 index 0000000000..6bfb29365a Binary files /dev/null and b/pandora_doc/fr/images/image020.png differ diff --git a/pandora_doc/fr/images/image021.png b/pandora_doc/fr/images/image021.png new file mode 100644 index 0000000000..06fff30759 Binary files /dev/null and b/pandora_doc/fr/images/image021.png differ diff --git a/pandora_doc/fr/images/image022.png b/pandora_doc/fr/images/image022.png new file mode 100644 index 0000000000..1373d692cb Binary files /dev/null and b/pandora_doc/fr/images/image022.png differ diff --git a/pandora_doc/fr/images/image023.png b/pandora_doc/fr/images/image023.png new file mode 100644 index 0000000000..3aaec43685 Binary files /dev/null and b/pandora_doc/fr/images/image023.png differ diff --git a/pandora_doc/fr/images/image025.png b/pandora_doc/fr/images/image025.png new file mode 100644 index 0000000000..87f187dc9f Binary files /dev/null and b/pandora_doc/fr/images/image025.png differ diff --git a/pandora_doc/fr/images/image026.png b/pandora_doc/fr/images/image026.png new file mode 100644 index 0000000000..412b610a2c Binary files /dev/null and b/pandora_doc/fr/images/image026.png differ diff --git a/pandora_doc/fr/images/image027.png b/pandora_doc/fr/images/image027.png new file mode 100644 index 0000000000..998ce6b5ee Binary files /dev/null and b/pandora_doc/fr/images/image027.png differ diff --git a/pandora_doc/fr/images/image028.png b/pandora_doc/fr/images/image028.png new file mode 100644 index 0000000000..9a8fb7ca42 Binary files /dev/null and b/pandora_doc/fr/images/image028.png differ diff --git a/pandora_doc/fr/images/image029.png b/pandora_doc/fr/images/image029.png new file mode 100644 index 0000000000..a785739737 Binary files /dev/null and b/pandora_doc/fr/images/image029.png differ diff --git a/pandora_doc/fr/images/image030.png b/pandora_doc/fr/images/image030.png new file mode 100644 index 0000000000..82977b5690 Binary files /dev/null and b/pandora_doc/fr/images/image030.png differ diff --git a/pandora_doc/fr/images/image031.png b/pandora_doc/fr/images/image031.png new file mode 100644 index 0000000000..b1cf41003b Binary files /dev/null and b/pandora_doc/fr/images/image031.png differ diff --git a/pandora_doc/fr/images/image032.png b/pandora_doc/fr/images/image032.png new file mode 100644 index 0000000000..83a98739d4 Binary files /dev/null and b/pandora_doc/fr/images/image032.png differ diff --git a/pandora_doc/fr/images/image033.png b/pandora_doc/fr/images/image033.png new file mode 100644 index 0000000000..dc934df495 Binary files /dev/null and b/pandora_doc/fr/images/image033.png differ diff --git a/pandora_doc/fr/images/image034.png b/pandora_doc/fr/images/image034.png new file mode 100644 index 0000000000..d709ed9b11 Binary files /dev/null and b/pandora_doc/fr/images/image034.png differ diff --git a/pandora_doc/fr/images/image035.png b/pandora_doc/fr/images/image035.png new file mode 100644 index 0000000000..d0fdaa1761 Binary files /dev/null and b/pandora_doc/fr/images/image035.png differ diff --git a/pandora_doc/fr/images/image036.png b/pandora_doc/fr/images/image036.png new file mode 100644 index 0000000000..861bd8a0a4 Binary files /dev/null and b/pandora_doc/fr/images/image036.png differ diff --git a/pandora_doc/fr/images/image037.png b/pandora_doc/fr/images/image037.png new file mode 100644 index 0000000000..c46eb08005 Binary files /dev/null and b/pandora_doc/fr/images/image037.png differ diff --git a/pandora_doc/fr/images/image038.png b/pandora_doc/fr/images/image038.png new file mode 100644 index 0000000000..b365bbe742 Binary files /dev/null and b/pandora_doc/fr/images/image038.png differ diff --git a/pandora_doc/fr/images/image039.png b/pandora_doc/fr/images/image039.png new file mode 100644 index 0000000000..ea3c52d386 Binary files /dev/null and b/pandora_doc/fr/images/image039.png differ diff --git a/pandora_doc/fr/images/image040.png b/pandora_doc/fr/images/image040.png new file mode 100644 index 0000000000..762c542ae7 Binary files /dev/null and b/pandora_doc/fr/images/image040.png differ diff --git a/pandora_doc/fr/images/image041.png b/pandora_doc/fr/images/image041.png new file mode 100644 index 0000000000..326e13d560 Binary files /dev/null and b/pandora_doc/fr/images/image041.png differ diff --git a/pandora_doc/fr/images/image042.png b/pandora_doc/fr/images/image042.png new file mode 100644 index 0000000000..3dc9d90649 Binary files /dev/null and b/pandora_doc/fr/images/image042.png differ diff --git a/pandora_doc/fr/images/image043.png b/pandora_doc/fr/images/image043.png new file mode 100644 index 0000000000..b4445cd8ca Binary files /dev/null and b/pandora_doc/fr/images/image043.png differ diff --git a/pandora_doc/fr/images/image044.png b/pandora_doc/fr/images/image044.png new file mode 100644 index 0000000000..240a644c86 Binary files /dev/null and b/pandora_doc/fr/images/image044.png differ diff --git a/pandora_doc/fr/images/image045.png b/pandora_doc/fr/images/image045.png new file mode 100644 index 0000000000..e3038c5a3c Binary files /dev/null and b/pandora_doc/fr/images/image045.png differ diff --git a/pandora_doc/fr/images/image046.png b/pandora_doc/fr/images/image046.png new file mode 100644 index 0000000000..9a5010fbb3 Binary files /dev/null and b/pandora_doc/fr/images/image046.png differ diff --git a/pandora_doc/fr/images/image047.png b/pandora_doc/fr/images/image047.png new file mode 100644 index 0000000000..08b1611518 Binary files /dev/null and b/pandora_doc/fr/images/image047.png differ diff --git a/pandora_doc/fr/images/image048.png b/pandora_doc/fr/images/image048.png new file mode 100644 index 0000000000..ca36610000 Binary files /dev/null and b/pandora_doc/fr/images/image048.png differ diff --git a/pandora_doc/fr/images/image049.png b/pandora_doc/fr/images/image049.png new file mode 100644 index 0000000000..1e460497af Binary files /dev/null and b/pandora_doc/fr/images/image049.png differ diff --git a/pandora_doc/fr/images/image050.png b/pandora_doc/fr/images/image050.png new file mode 100644 index 0000000000..12f8cd01f8 Binary files /dev/null and b/pandora_doc/fr/images/image050.png differ diff --git a/pandora_doc/fr/images/image051.png b/pandora_doc/fr/images/image051.png new file mode 100644 index 0000000000..ead01e5072 Binary files /dev/null and b/pandora_doc/fr/images/image051.png differ diff --git a/pandora_doc/fr/images/image052.png b/pandora_doc/fr/images/image052.png new file mode 100644 index 0000000000..7f7f4f44d9 Binary files /dev/null and b/pandora_doc/fr/images/image052.png differ diff --git a/pandora_doc/fr/images/image053.png b/pandora_doc/fr/images/image053.png new file mode 100644 index 0000000000..c36df2d81f Binary files /dev/null and b/pandora_doc/fr/images/image053.png differ diff --git a/pandora_doc/fr/images/image054.png b/pandora_doc/fr/images/image054.png new file mode 100644 index 0000000000..d18a98ade9 Binary files /dev/null and b/pandora_doc/fr/images/image054.png differ diff --git a/pandora_doc/fr/images/image055.png b/pandora_doc/fr/images/image055.png new file mode 100644 index 0000000000..8c6d926677 Binary files /dev/null and b/pandora_doc/fr/images/image055.png differ diff --git a/pandora_doc/fr/images/image056.png b/pandora_doc/fr/images/image056.png new file mode 100644 index 0000000000..7c92637da6 Binary files /dev/null and b/pandora_doc/fr/images/image056.png differ diff --git a/pandora_doc/fr/images/image057.png b/pandora_doc/fr/images/image057.png new file mode 100644 index 0000000000..a52d7b274b Binary files /dev/null and b/pandora_doc/fr/images/image057.png differ diff --git a/pandora_doc/fr/images/image058.png b/pandora_doc/fr/images/image058.png new file mode 100644 index 0000000000..ec3ba5e88d Binary files /dev/null and b/pandora_doc/fr/images/image058.png differ diff --git a/pandora_doc/fr/images/image059.png b/pandora_doc/fr/images/image059.png new file mode 100644 index 0000000000..a5c68bd40b Binary files /dev/null and b/pandora_doc/fr/images/image059.png differ diff --git a/pandora_doc/fr/images/image060.png b/pandora_doc/fr/images/image060.png new file mode 100644 index 0000000000..6d705beddc Binary files /dev/null and b/pandora_doc/fr/images/image060.png differ diff --git a/pandora_doc/fr/images/image061.png b/pandora_doc/fr/images/image061.png new file mode 100644 index 0000000000..342571ece7 Binary files /dev/null and b/pandora_doc/fr/images/image061.png differ diff --git a/pandora_doc/fr/images/image52.png b/pandora_doc/fr/images/image52.png new file mode 100644 index 0000000000..d76c4ce2f0 Binary files /dev/null and b/pandora_doc/fr/images/image52.png differ diff --git a/pandora_doc/fr/images/messages.png b/pandora_doc/fr/images/messages.png new file mode 100644 index 0000000000..b6ac5ff8ad Binary files /dev/null and b/pandora_doc/fr/images/messages.png differ diff --git a/pandora_doc/fr/images/messages1.png b/pandora_doc/fr/images/messages1.png new file mode 100644 index 0000000000..479a27e27e Binary files /dev/null and b/pandora_doc/fr/images/messages1.png differ diff --git a/pandora_doc/fr/images/messages2.png b/pandora_doc/fr/images/messages2.png new file mode 100644 index 0000000000..39312dc384 Binary files /dev/null and b/pandora_doc/fr/images/messages2.png differ diff --git a/pandora_doc/fr/images/mini_pandora_box.jpg b/pandora_doc/fr/images/mini_pandora_box.jpg new file mode 100644 index 0000000000..1d9bf76437 Binary files /dev/null and b/pandora_doc/fr/images/mini_pandora_box.jpg differ diff --git a/pandora_doc/fr/images/module_graph_full.jpg b/pandora_doc/fr/images/module_graph_full.jpg new file mode 100644 index 0000000000..4a2485b330 Binary files /dev/null and b/pandora_doc/fr/images/module_graph_full.jpg differ diff --git a/pandora_doc/fr/images/module_graph_peak.jpg b/pandora_doc/fr/images/module_graph_peak.jpg new file mode 100644 index 0000000000..bd629be655 Binary files /dev/null and b/pandora_doc/fr/images/module_graph_peak.jpg differ diff --git a/pandora_doc/fr/images/ok.png b/pandora_doc/fr/images/ok.png new file mode 100644 index 0000000000..42054dea61 Binary files /dev/null and b/pandora_doc/fr/images/ok.png differ diff --git a/pandora_doc/fr/images/outof.png b/pandora_doc/fr/images/outof.png new file mode 100644 index 0000000000..698fce9e55 Binary files /dev/null and b/pandora_doc/fr/images/outof.png differ diff --git a/pandora_doc/fr/images/pandora-webbanner.jpg b/pandora_doc/fr/images/pandora-webbanner.jpg new file mode 100755 index 0000000000..ca7062c2bb Binary files /dev/null and b/pandora_doc/fr/images/pandora-webbanner.jpg differ diff --git a/pandora_doc/fr/images/pandora_ER.png b/pandora_doc/fr/images/pandora_ER.png new file mode 100644 index 0000000000..321453ffab Binary files /dev/null and b/pandora_doc/fr/images/pandora_ER.png differ diff --git a/pandora_doc/fr/images/pandora_agentbox.jpg b/pandora_doc/fr/images/pandora_agentbox.jpg new file mode 100644 index 0000000000..b3aa698df0 Binary files /dev/null and b/pandora_doc/fr/images/pandora_agentbox.jpg differ diff --git a/pandora_doc/fr/images/pandora_agentscheme1.jpg b/pandora_doc/fr/images/pandora_agentscheme1.jpg new file mode 100644 index 0000000000..cde652138d Binary files /dev/null and b/pandora_doc/fr/images/pandora_agentscheme1.jpg differ diff --git a/pandora_doc/fr/images/pandora_alert.jpg b/pandora_doc/fr/images/pandora_alert.jpg new file mode 100644 index 0000000000..7cc3d586d8 Binary files /dev/null and b/pandora_doc/fr/images/pandora_alert.jpg differ diff --git a/pandora_doc/fr/images/pandora_arch1.jpg b/pandora_doc/fr/images/pandora_arch1.jpg new file mode 100644 index 0000000000..cdc7c5bc8f Binary files /dev/null and b/pandora_doc/fr/images/pandora_arch1.jpg differ diff --git a/pandora_doc/fr/images/pandora_arch2.jpg b/pandora_doc/fr/images/pandora_arch2.jpg new file mode 100644 index 0000000000..6826471045 Binary files /dev/null and b/pandora_doc/fr/images/pandora_arch2.jpg differ diff --git a/pandora_doc/fr/images/pandora_database.jpg b/pandora_doc/fr/images/pandora_database.jpg new file mode 100644 index 0000000000..b753e21e3d Binary files /dev/null and b/pandora_doc/fr/images/pandora_database.jpg differ diff --git a/pandora_doc/fr/images/pandora_login.jpg b/pandora_doc/fr/images/pandora_login.jpg new file mode 100644 index 0000000000..82f30e42a5 Binary files /dev/null and b/pandora_doc/fr/images/pandora_login.jpg differ diff --git a/pandora_doc/fr/images/pandora_logo.jpg b/pandora_doc/fr/images/pandora_logo.jpg new file mode 100644 index 0000000000..c839519845 Binary files /dev/null and b/pandora_doc/fr/images/pandora_logo.jpg differ diff --git a/pandora_doc/fr/images/servers1.png b/pandora_doc/fr/images/servers1.png new file mode 100644 index 0000000000..d2e60a5ee3 Binary files /dev/null and b/pandora_doc/fr/images/servers1.png differ diff --git a/pandora_doc/fr/images/servers2.png b/pandora_doc/fr/images/servers2.png new file mode 100644 index 0000000000..1ba63e1efa Binary files /dev/null and b/pandora_doc/fr/images/servers2.png differ diff --git a/pandora_doc/fr/images/setup.png b/pandora_doc/fr/images/setup.png new file mode 100644 index 0000000000..d941d8c0a2 Binary files /dev/null and b/pandora_doc/fr/images/setup.png differ diff --git a/pandora_doc/fr/images/target.png b/pandora_doc/fr/images/target.png new file mode 100644 index 0000000000..edc180d557 Binary files /dev/null and b/pandora_doc/fr/images/target.png differ diff --git a/pandora_doc/fr/man/pandora b/pandora_doc/fr/man/pandora new file mode 100644 index 0000000000..0ba6c8bc0b --- /dev/null +++ b/pandora_doc/fr/man/pandora @@ -0,0 +1,352 @@ +.TH PandoraFMS + +.SH NAME + +pandorafms - Pandora Free Monitoring System User Guide + +.SH AVAILABILITY + +Linux, AIX, Solaris, Windows... + +.SH DESCRIPTION + +This is the user guide for Pandora FMS. This is not the full version, full version contains images, you will be able to find at www.pandorafms.net + +.SH NOTES + +This is the main Pandora User Guide. If you have this man page also, you are supposed to have also pandora_agent, pandora_network, pandora_server and pandora_console man pages. + +.SH SYPNOSYS + +Pandora FMS is a monitoring application to watch systems and applications. Pandora allows to know the +status of any element of your bussiness systems. Pandora watch for your hardware, your software, your +multilayer system and of course your Operating System. Pandora could detect a network interface down +and the movement of any value of the NASDAQ new technology market. If you want, Pandora could sent +a SMS message when your systems fails... or when Google value low below US$ 330. +Pandora FMS will adjust, like an octopus, to your systems and requirements, because it has been +designed to be open, modular, multiplattform and easy to customize. + +.B Pandora architecture: + +.I Web Console +.br +Pandora’s user interface. The user controls and operates the system with it. Several Web +consoles can be implemented in a single system. The Web console is written in PHP, and it is over a +database and a Web server. It is compatible with any platform - GNU/Linux, Solaris, Win2000, AIX, +etc.T official supported platform is GNU/Linux, though +The console permits the user to control the status of the agents, view statistical information, generate +graphs and data tables, keep a system incident control,moreover it is able to generate reports and +change the alerts, agents, and user profile settings. + +.I Server +.br +In Pandora 1.2 there are three different servers: +The core server is the receptor of the data packages and generates the alerts - it is the brain of the +system. Several servers can work alongside for larger systems. The core server accesses Pandora +database, which is shared with the Web server, and stores the processed data packages. Server executes +as daemon, and processes the packages stored in its file system. Data is generated by the system +agents. Despite the server’s low system resources comsumption and simple installation and operation, +the core server is the most critical element of the system. The core server receives and processes the +produced data, and fires the alerts and the events. +The Network Servers monitorize remote systems using network resources like ICMP, TCP, UDP or +SNMP Queries. Network Servers are acting itself like "Network Agents". This server fires the alerts +and the events for this modules. +The SNMP Server receives and processes the snmp traps, and fires the alerts associated to it. +.I Central Database +.br +At the moment the system only supports MySQL. The central database keeps all +the information Pandora needs to work - agent data, settings, user information, incidents, system +settings, etc. The system can use a MySQL cluster to store the information, or a High Availability +(HA) solution for larger sytems. +This database can work with any of the platform officially supported by MySQL. Pandora can be +implemented with MySQL versions from 3.0 to 5.0, although the latest is recommended. + +.I Pandora Agents +.br +They collect all the system’s data. They are executed in each local system, although +they can also collect remote information by intalling monitoring sytems for the agent in several +different machines - called satellite agents. +They have been developed to work under a specific platform, making use of the specific tools of the +used language: ShellScripting for Unix - which includes GNU/Linux, Solaris, AIX, HP-UX and BSD, +as well as the Nokia’s IPSO. Pandora agents can be developed in virtually any language, given its +simple API and being open source. Windows agent are developed in a free development environment +for C++ and uses the same interface and modularity than Unix agents. +The old agent for Windows plattforms was developed on VBS Scripting language, and is deprecated +with the new Pandora 1.2 windows agent. + +.B What kind of systems/ services can be monitored? + +At present, with Pandora any process or system that through a command returns a value can be +monitored, as well as any value in any Operating System log file or similar. Some examples of already +existing implementations below: +Number of connections (sessions) of Checkpoint FW-1 +Number of NAT sessions of Checkpoint FW-1 +Number of connections of Linux NetFilter / IPTables firewall +Number of FW-1 logged packets +Number of FW-1 dropped packets +Number of FW-1 accepted packets +State of High Availability in FW1 NG +Last policy installed in a Firewall-1 module +Synchronization state of the modules in FW1 NG +CPU of the system: idle, user and system +Number of processes of the system +Temperature of the CPU of a system +Value of a MS Windows registry entry +Queued jobs in a generic dispatcher +Memory of the system: free, swap, kernel Fw-1, cache +Percentage of free space on disc (for different partitions) +Messages processed by a mail gateway +Existence of a string in a text file +IP traffic (filtering based on the connections of the firewall) +Hits of pages in HTTP Servers (Apache, iPlanet, IIS, Netscape) +Percentage of erroneous packets in a Gateway +Connections established in a Remote Access Server (RAS) +Size of a file +Open sessions by a VPN server +MySQL Performance: Threads, queries, sessions... +Snort system state +Reported events by IDS (Snort) up to six levels of priority +Network load +Number of local Connections (TCP, UDP, Unix sockets) +Detected viruses by a Web Antivirus Gateway +ICMP latency time towards a host +Rate of average transference in a file transfer tool +Number of DNS requests attended by a server (including types) +Number of FTP sessions attended by a FTP server +(Generic) State of any active process / service in the system +(Generic) State of any countable parameter of the system + +.B Information gathering with Pandora agents +.br +Pandora agents are based on native languages in every platform: scripts that can be written in any +language. It’s possible to reproduce any agent in any programming language and can be extended +without difficulty the existing ones in order to cover aspects not taken into account up to the moment. +These scripts are formed by modules that each one gathers a "chunk" of information. Thus, every agent +gathers several "chunks" of information; this one is organized in a data set and stored in a single file, +called data file. +The process of transferring the data file from the agent to the server is made regularly at a defined time +interval in the agent configuration file, pandora_agent.conf. It’s possible to modify that parameter in +order to do not fill the database with non-relevant information, either load the network or affect the +system performance. The default interval is 300 (seconds), which is equivalent to five minutes. Minor +values of 100 (seconds) are not recommended since host performance could be affected, besides loading +excessively Database and the Operating System of Pandora Server. Pandora is not a real time system; it’s +an applications and systems general monitoring system in environments that are not critical at real time. +Packets transfers are made via SSH, with DSA authentication (although also RSA can be used). The +process is completely safe since neither any password nor unencrypted confidential information is sent. +Confidentiality, integrity and authentication of the connections between the agent and the server are +ensured. In the Agents and Server Installation and Configuration guides, the process of generation of +keys to do the automatic SCP transfer is detailed. +Also the transfer via FTP or any other file transfer system could be made, although SSH has been chosen +for security and compatibility with most of the systems in the market. +Pandora Agents are thought to be executed from the agent from which they gather information, although +the agents can gather information of accessible machines from the host where they are installed. In this +case those agents are called "Satellite Agents". These Satellite Agents can use Telnet, SNMP or any +other commands to get the information. +We can also have a host with several agents: Some that gather information from the accessible machines +(acting as "satellite agents") and the Standard Agent that monitors the host where it’s running. + +.B XML Data fiFiles +.br +The data file has the following syntax: +hostname.serialnumber.data + +This is an XML file, and its name is the combination of the hostname where the agent runs, a different +serial number for every data package and the extension .data that indicates that it’s a data fifile. +We also have a control fifile for every data fifile: + +.I hostname.serialnumber.checksum +This file has .checksum extension and contains a MD5 hash of the data file. This allows checking that the +information has not been changed before being processed. +The XML data file generated by every agent is the core of Pandora. This file has the information gathered +by the Agent. Its easy structure allows that any user could create its own developments to be processed in +Pandora, or use the included ones. An example of the information included into the data file below: + +.I " +.br +.I +.br +.I SSH Daemon .br +.br +.I generic_proc +.br +.I 1 +.br +.I +.br +.I +.br +.I FTP Daemon +.br +.I generic_proc +.br +.I 0 +.br +.I +.br +.I +.br +.I DiskFree +.br +.I generic_data +.br +.I 5200000 +.br +.I +.br +.I +.br +.I UsersConnected +.br +.I generic_data_inc +.br +.I 119 +.br +.I 1 +.br +.I 250 +.br +.I Users currently connected +.br +.I +.br +.I +.br +.I LastLogin +.br +.I generic_data_string" +.br +.I slerena +.br +.I +.br +.I + +.B Pandora Servers +.br +With Pandora 1.2 version, you have three different types of servers: +.I "Pandora Data Server" +.br +This is a PERL application that that processes the information sent by the +agents. The agents send the XML data file via SSH and the server periodically verifies if it has new +data files waiting to be processed. You can setup different data servers in different systems or in the +same host (that will be different virtual servers). + +.I "Pandora Network Server" +.br +This is a PERL application that execute network tasks like sending pings, +TCP requests, SNMP requests and UDP request. When you assign an agent to a server, you are +assigning to a network server, not a data server, so, this is very important that machines running +network servers have "network visibility" to hosts assigned in network modules. +For example, if you create a module to make a ping check to 192.168.1.1 and assign this agent/module +to a server in a 192.168.2.0/24 network without access to 192.168.1.0/24 module will always report +DOWN. + +.I "Pandora SNMP Server" +.br +This is a PERL application that parse output from standard snmptradp (we +provide one binary for snmptrapd, but it is possible that you need to replace it with a binary that runs +better in your system). This daemon receives SNMP traps, and Pandora SNMP Server stores in +database and fire alerts assigned in Pandora SNMP Console. +Data are extracted from the data file, identifying origin, type and category. Once it’s classified, the data +are inserted into the Database by the same Perl script. +Pandora Server can work in High Availability and/or Load Balancing. In a very big architecture, several + +Pandora Servers can be arranged simultaneously in order to be able to manage big volumes of +information distributed by geographical or functional zones. +Pandora Server is always running (as a daemon) and permanently verifies if some element causes to fire +an alarm. If so, it executes the action defined in the alarm, as to send a SMS, an email, even activates the +execution of a SCRIPT or to send an HTTP form. + +We could have several simultaneous servers, one of them is the Main Server or "Master Server " and the +rest of servers are "Slave Servers". The Master Server is the only one that verifies the alarms if any agent +goes down. The server which receives the data file from the agent always fires the rest of alarms, defined +in the agents’ modules. This is also important if this server changes (due to configurations of high +availability, load balancing or clustering). + + +.B Pandora console +.br +The Web Console is a web application that allows to see graphical reports, state of every agent, also to +access to the information sent by the agent, to see every monitored parameter and to see its evolution +throughout the time, to form the different nodes, groups and users of the system. It is the part that +interacts with the final user, and that will allows you to administer the system. +The Web Console is written in PHP and no plug-in, Flash, Java or ActiveX is needed to access the +console, only a browser that supports HTML and CSS (IE5+ or Mozilla 4+). Pandora Web Console can +run in several servers, the only thing you need is to be allow to access Pandora Database, where Pandora +stores all the information. + +.B Pandora database +.br +Pandora uses a SQL Database to store all the information. Pandora maintains an asynchronous database +with all the received data, making a temporary cohesion of everything it is receives and normalizing all +the information from the different sources. Every Agent data module generates an entry of information +for every data bundle, which implies that a real production system can have of the order of ten million of +data, or information atoms. +This information is managed automatically from Pandora, carrying out a periodic and automatic +maintenance of the database. This means that there is no operator either manager required to run tasks as +database administration ones. This is possible thanks to a periodic purge of the past information over a +date (by default 90 days), as well as a data which is older, by default, 30 days. + +.B Compacting data +.br +Data stored by Pandora are useful to see evolutions through the time, in order to: make statistics, +generate reports and to do capacity planning, as well as other statisticals tasks. To do that it isn’t +necessary to have all the data, but it’s enough to have a representative sample, of smaller resolution, +enough to carry out the task that is needed. +With that philosophy the compaction system has been constructed. For instance, If we have a sample of +9.000 elements, distributed during 90 days, Pandora will take the data of last month, which would be +3.000 elements and will compress it in 300. In the graphs they will practically be equal, and it will be +usful for the reports, statistics and other tasks. This is made thanks to a interpolation in temporary strips, +in a totally automatic and periodic way, there is no user or the administrator needed to do this. + +.HISTORY + +.B Pandora 1.2 new features +.br +Alert system. Now it is possible to define a "minimun" and "maximum" limit to fire an alert, just to delete +"noisy" data that fires false positives. +Network Subsystem. Now it is possible to monitor and analyze data using remote network tools, without +using agents, from the new Pandora Network Server component. All management are made from +Pandora Console, and now you will be able to make ICMP checks (Ping), size network latency, get all +types of SNMP values (including scanning MIB), and makes TCP/UDP connections to check ports, and +test text applications, sending texts and waiting for a specific response. +Module groups.Modules now could be grouped using a new "module groups". +Network data refresh on demand. Could be for each module or using a "global group refresh", forcing +Pandora Network Servers to refresh all network modules inside a group. +Online contextual help, for Pandora WEB Console. +New Pandora server infraestructure. +New SNMP trap console to receive SNMP traps and assigning alerts. +Internal messaging system, to notify events to Pandora users. +Agent detail view autorefresh +New main agent group view +Improved database management system, that allows to manage much more data. + +Pandora is a project initiated and mainly developed by Sancho Lerena, at present other people is working +on it: Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel Arostegui We want to +thank many other people who help us with translation, graphic design, bugs reporting and interesting +ideas. +.br +Pandora is Free Software, and is published under GPL Licence. In order to know the last features, go to +the official web site of the project in http://pandora.sourceforge.net. + +.SH AUTHOR + +Pandora Free Monitoring System is made and copyrighted by Sancho Lerena +Pandora is a project initiated and mainly developed by Sancho Lerena, at present other people is working +on it: Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel Arostegui We want to +thank many other people who help us with translation, graphic design, bugs reporting and interesting +ideas. +.br + + +.SH SEE ALSO + +.B pandora +.br +.B pandora_server +.br +.B pandora_agents +.br +.B pandora_console diff --git a/pandora_doc/fr/man/pandora.1 b/pandora_doc/fr/man/pandora.1 new file mode 100644 index 0000000000..90f22478dd --- /dev/null +++ b/pandora_doc/fr/man/pandora.1 @@ -0,0 +1,342 @@ +PandoraFMS() PandoraFMS() + + + +NNAAMMEE + pandorafms - Pandora Free Monitoring System User Guide + + +AAVVAAIILLAABBIILLIITTYY + Linux, AIX, Solaris, Windows... + + +DDEESSCCRRIIPPTTIIOONN + This is the user guide for Pandora FMS. This is not the full version, + full version contains images, you will be able to find at www.pando- + rafms.net + + +NNOOTTEESS + This is the main Pandora User Guide. If you have this man page also, + you are supposed to have also pandora_agent, pandora_network, pan- + dora_server and pandora_console man pages. + + +SSYYPPNNOOSSYYSS + Pandora FMS is a monitoring application to watch systems and applica- + tions. Pandora allows to know the status of any element of your bussi- + ness systems. Pandora watch for your hardware, your software, your mul- + tilayer system and of course your Operating System. Pandora could + detect a network interface down and the movement of any value of the + NASDAQ new technology market. If you want, Pandora could sent a SMS + message when your systems fails... or when Google value low below US$ + 330. Pandora FMS will adjust, like an octopus, to your systems and + requirements, because it has been designed to be open, modular, multi- + plattform and easy to customize. + + PPaannddoorraa aarrcchhiitteeccttuurree:: + + _W_e_b _C_o_n_s_o_l_e + Pandora’s user interface. The user controls and operates the system + with it. Several Web consoles can be implemented in a single system. + The Web console is written in PHP, and it is over a database and a Web + server. It is compatible with any platform - GNU/Linux, Solaris, + Win2000, AIX, etc.T official supported platform is GNU/Linux, though + The console permits the user to control the status of the agents, view + statistical information, generate graphs and data tables, keep a system + incident control,moreover it is able to generate reports and change the + alerts, agents, and user profile settings. + + _S_e_r_v_e_r + In Pandora 1.2 there are three different servers: The core server is + the receptor of the data packages and generates the alerts - it is the + brain of the system. Several servers can work alongside for larger sys- + tems. The core server accesses Pandora database, which is shared with + the Web server, and stores the processed data packages. Server executes + as daemon, and processes the packages stored in its file system. Data + is generated by the system agents. Despite the server ’s low system + resources comsumption and simple installation and operation, the core + server is the most critical element of the system. The core server + receives and processes the produced data, and fires the alerts and the + events. The Network Servers monitorize remote systems using network + resources like ICMP, TCP, UDP or SNMP Queries. Network Servers are act- + ing itself like "Network Agents". This server fires the alerts and the + events for this modules. The SNMP Server receives and processes the + snmp traps, and fires the alerts associated to it. _C_e_n_t_r_a_l _D_a_t_a_b_a_s_e + At the moment the system only supports MySQL. The central database + keeps all the information Pandora needs to work - agent data, settings, + user information, incidents, system settings, etc. The system can use a + MySQL cluster to store the information, or a High Availability (HA) + solution for larger sytems. This database can work with any of the + platform officially supported by MySQL. Pandora can be implemented with + MySQL versions from 3.0 to 5.0, although the latest is recommended. + + _P_a_n_d_o_r_a _A_g_e_n_t_s + They collect all the system’s data. They are executed in each local + system, although they can also collect remote information by intalling + monitoring sytems for the agent in several different machines - called + satellite agents. They have been developed to work under a specific + platform, making use of the speci fic tools of the used language: + ShellScripting for Unix - which includes GNU/Linux, Solaris, AIX, HP-UX + and BSD, as well as the Nokia’s IPSO. Pandora agents can be developed + in virtually any language, given its simple API and being open source. + Windows agent are developed in a free development environment for C++ + and uses the same interface and modularity than Unix agents. The old + agent for Windows plattforms was developed on VBS Scripting language, + and is deprecated with the new Pandora 1.2 windows agent. + + WWhhaatt kkiinndd ooff ssyysstteemmss// sseerrvviicceess ccaann bbee mmoonniittoorreedd?? + + At present, with Pandora any process or system that through a command + returns a value can be monitored, as well as any value in any Operating + System log file or similar. Some examples of already existing implemen- + tations below: Number of connections (sessions) of Checkpoint FW-1 Num- + ber of NAT sessions of Checkpoint FW-1 Number of connections of Linux + NetFilter / IPTables firewall Number of FW-1 logged packets Number of + FW-1 dropped packets Number of FW-1 accepted packets State of High + Availability in FW1 NG Last policy installed in a Firewall-1 module + Synchronization state of the modules in FW1 NG CPU of the system: idle, + user and system Number of processes of the system Temperature of the + CPU of a system Value of a MS Windows registry entry Queued jobs in a + generic dispatcher Memory of the system: free, swap, kernel Fw-1, cache + Percentage of free space on disc (for different partitions) Messages + processed by a mail gateway Existence of a string in a text file IP + traffic (filtering based on the connections of the firewall) Hits of + pages in HTTP Servers (Apache, iPlanet, IIS, Netscape) Percentage of + erroneous packets in a Gateway Connections established in a Remote + Access Server (RAS) Size of a file Open sessions by a VPN server MySQL + Performance: Threads, queries, sessions... Snort system state Reported + events by IDS (Snort) up to six levels of priority Network load Number + of local Connections (TCP, UDP, Unix sockets) Detected viruses by a Web + Antivirus Gateway ICMP latency time towards a host Rate of average + transference in a file transfer tool Number of DNS requests attended by + a server (including types) Number of FTP sessions attended by a FTP + server (Generic) State of any active process / service in the system + (Generic) State of any countable parameter of the system + + IInnffoorrmmaattiioonn ggaatthheerriinngg wwiitthh PPaannddoorraa aaggeennttss + Pandora agents are based on native languages in every platform: scripts + that can be written in any language. It’s possible to reproduce any + agent in any programming language and can be extended without dif + ficulty the existing ones in order to cover aspects not taken into + account up to the moment. These scripts are formed by modules that + each one gathers a "chunk" of information. Thus, every agent gathers + several "chunks" of information; this one is organized in a data set + and stored in a single file, called data file. The process of trans- + ferring the data file from the agent to the server is made regularly at + a de fined time interval in the agent con figuration file, pan- + dora_agent.conf. It’s possible to modify that parameter in order to do + not fill the database with non-relevant information, either load the + network or affect the system performance. The default interval is 300 + (seconds), which is equivalent to five minutes. Minor values of 100 + (seconds) are not recommended since host performance could be affected, + besides loading excessively Database and the Operating System of Pan- + dora Server. Pandora is not a real time system; it’s an applications + and systems general monitoring system in environments that are not + critical at real time. Packets transfers are made via SSH, with DSA + authentication (although also RSA can be used). The process is com- + pletely safe since neither any password nor unencrypted con fidential + information is sent. Confidentiality, integrity and authentication of + the connections between the agent and the server are ensured. In the + Agents and Server Installation and Configuration guides, the process of + generation of keys to do the automatic SCP transfer is detailed. Also + the transfer via FTP or any other file transfer system could be made, + although SSH has been chosen for security and compatibility with most + of the systems in the market. Pandora Agents are thought to be exe- + cuted from the agent from which they gather information, although the + agents can gather information of accessible machines from the host + where they are installed. In this case those agents are called "Satel- + lite Agents". These Satellite Agents can use Telnet, SNMP or any other + commands to get the information. We can also have a host with several + agents: Some that gather information from the accessible machines (act- + ing as "satellite agents") and the Standard Agent that monitors the + host where it’s running. + + XXMMLL DDaattaa fiFFiilleess + The data file has the following syntax: hostname.serialnumber.data + + This is an XML file, and its name is the combination of the hostname + where the agent runs, a different serial number for every data package + and the extension .data that indicates that it’s a data fifile. We + also have a control fifile for every data fifile: + + _h_o_s_t_n_a_m_e_._s_e_r_i_a_l_n_u_m_b_e_r_._c_h_e_c_k_s_u_m This file has .checksum extension and + contains a MD5 hash of the data file. This allows checking that the + information has not been changed before being processed. The XML data + file generated by every agent is the core of Pandora. This file has the + information gathered by the Agent. Its easy structure allows that any + user could create its own developments to be processed in Pandora, or + use the included ones. An example of the information included into the + data file below: + + _<_a_g_e_n_t _d_a_t_a _o_s___n_a_m_e_= _S_u_n_O_S_" _o_s___v_e_r_s_i_o_n_=_"_5_._8_" _t_i_m_e_s_t_a_m_p_=_"_3_0_0_" + _a_g_e_n_t___n_a_m_e_=_"_p_d_g_e_s_0_1_" _v_e_r_s_i_o_n_=_"_1_._0_"_> + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_S_S_H _D_a_e_m_o_n_<_/_n_a_m_e_> _._b_r + _<_t_y_p_e_>_g_e_n_e_r_i_c___p_r_o_c_<_/_t_y_p_e_> + _<_d_a_t_a_>_1_<_/_d_a_t_a_> + _<_/_m_o_d_u_l_e_> + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_F_T_P _D_a_e_m_o_n_<_/_n_a_m_e_> + _<_t_y_p_e_>_g_e_n_e_r_i_c___p_r_o_c_<_/_t_y_p_e_> + _<_d_a_t_a_>_0_<_/_d_a_t_a_> + _<_/_m_o_d_u_l_e_> + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_D_i_s_k_F_r_e_e_<_/_n_a_m_e_> + _<_t_y_p_e_>_g_e_n_e_r_i_c___d_a_t_a_<_/_t_y_p_e_> + _<_d_a_t_a_>_5_2_0_0_0_0_0_<_/_d_a_t_a_> + _<_/_m_o_d_u_l_e_> + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_U_s_e_r_s_C_o_n_n_e_c_t_e_d_<_/_n_a_m_e_> + _<_t_y_p_e_>_g_e_n_e_r_i_c___d_a_t_a___i_n_c_<_/_t_y_p_e_> + _<_d_a_t_a_>_1_1_9_<_/_d_a_t_a_> + _<_m_i_n_>_1_<_/_m_i_n_> + _<_m_a_x_>_2_5_0_<_/_m_a_x_> + _<_d_e_s_c_r_i_p_t_i_o_n_>_U_s_e_r_s _c_u_r_r_e_n_t_l_y _c_o_n_n_e_c_t_e_d_<_/_d_e_s_c_r_i_p_t_i_o_n_> + _<_/_m_o_d_u_l_e_> + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_L_a_s_t_L_o_g_i_n_<_/_n_a_m_e_> + _<_t_y_p_e_>_g_e_n_e_r_i_c___d_a_t_a___s_t_r_i_n_g_<_/_t_y_p_e_>_" + _<_d_a_t_a_>_s_l_e_r_e_n_a_<_/_d_a_t_a_> + _<_/_m_o_d_u_l_e_> + _<_/_a_g_e_n_t___d_a_t_a_> + + PPaannddoorraa SSeerrvveerrss + With Pandora 1.2 version, you have three different types of servers: + _P_a_n_d_o_r_a _D_a_t_a _S_e_r_v_e_r + This is a PERL application that that processes the information sent by + the agents. The agents send the XML data file via SSH and the server + periodically verifies if it has new data files waiting to be processed. + You can setup different data servers in different systems or in the + same host (that will be different virtual servers). + + _P_a_n_d_o_r_a _N_e_t_w_o_r_k _S_e_r_v_e_r + This is a PERL application that execute network tasks like sending + pings, TCP requests, SNMP requests and UDP request. When you assign an + agent to a server, you are assigning to a network server, not a data + server, so, this is very important that machines running network + servers have "network visibility" to hosts assigned in network modules. + For example, if you create a module to make a ping check to 192.168.1.1 + and assign this agent/module to a server in a 192.168.2.0/24 network + without access to 192.168.1.0/24 module will always report DOWN. + + _P_a_n_d_o_r_a _S_N_M_P _S_e_r_v_e_r + This is a PERL application that parse output from standard snmptradp + (we provide one binary for snmptrapd, but it is possible that you need + to replace it with a binary that runs better in your system). This dae- + mon receives SNMP traps, and Pandora SNMP Server stores in database and + fire alerts assigned in Pandora SNMP Console. Data are extracted from + the data file, identifying origin, type and category. Once it’s classi + fied, the data are inserted into the Database by the same Perl script. + Pandora Server can work in High Availability and/or Load Balancing. In + a very big architecture, several + + Pandora Servers can be arranged simultaneously in order to be able to + manage big volumes of information distributed by geographical or func- + tional zones. Pandora Server is always running (as a daemon) and per- + manently verifies if some element causes to fire an alarm. If so, it + executes the action defined in the alarm, as to send a SMS, an email, + even activates the execution of a SCRIPT or to send an HTTP form. + + We could have several simultaneous servers, one of them is the Main + Server or "Master Server " and the rest of servers are "Slave Servers". + The Master Server is the only one that verifies the alarms if any agent + goes down. The server which receives the data file from the agent + always fires the rest of alarms, defined in the agents’ modules. This + is also important if this server changes (due to configurations of high + availability, load balancing or clustering). + + + PPaannddoorraa ccoonnssoollee + The Web Console is a web application that allows to see graphical + reports, state of every agent, also to access to the information sent + by the agent, to see every monitored parameter and to see its evolution + throughout the time, to form the different nodes, groups and users of + the system. It is the part that interacts with the final user, and that + will allows you to administer the system. The Web Console is written + in PHP and no plug-in, Flash, Java or ActiveX is needed to access the + console, only a browser that supports HTML and CSS (IE5+ or Mozilla + 4+). Pandora Web Console can run in several servers, the only thing you + need is to be allow to access Pandora Database, where Pandora stores + all the information. + + PPaannddoorraa ddaattaabbaassee + Pandora uses a SQL Database to store all the information. Pandora + maintains an asynchronous database with all the received data, making a + temporary cohesion of everything it is receives and normalizing all the + information from the different sources. Every Agent data module gener- + ates an entry of information for every data bundle, which implies that + a real production system can have of the order of ten million of data, + or information atoms. This information is managed automatically from + Pandora, carrying out a periodic and automatic maintenance of the + database. This means that there is no operator either manager required + to run tasks as database administration ones. This is possible thanks + to a periodic purge of the past information over a date (by default 90 + days), as well as a data which is older, by default, 30 days. + + CCoommppaaccttiinngg ddaattaa + Data stored by Pandora are useful to see evolutions through the time, + in order to: make statistics, generate reports and to do capacity plan- + ning, as well as other statisticals tasks. To do that it isn’t neces- + sary to have all the data, but it’s enough to have a representative + sample, of smaller resolution, enough to carry out the task that is + needed. With that philosophy the compaction system has been con- + structed. For instance, If we have a sample of 9.000 elements, dis- + tributed during 90 days, Pandora will take the data of last month, + which would be 3.000 elements and will compress it in 300. In the + graphs they will practically be equal, and it will be usful for the + reports, statistics and other tasks. This is made thanks to a interpo- + lation in temporary strips, in a totally automatic and periodic way, + there is no user or the administrator needed to do this. + + + PPaannddoorraa 11..22 nneeww ffeeaattuurreess + Alert system. Now it is possible to define a "minimun" and "maximum" + limit to fire an alert, just to delete "noisy" data that fires false + positives. Network Subsystem. Now it is possible to monitor and ana- + lyze data using remote network tools, without using agents, from the + new Pandora Network Server component. All management are made from Pan- + dora Console, and now you will be able to make ICMP checks (Ping), size + network latency, get all types of SNMP values (including scanning MIB), + and makes TCP/UDP connections to check ports, and test text applica- + tions, sending texts and waiting for a specific response. Module + groups.Modules now could be grouped using a new "module groups". Net- + work data refresh on demand. Could be for each module or using a + "global group refresh", forcing Pandora Network Servers to refresh all + network modules inside a group. Online contextual help, for Pandora + WEB Console. New Pandora server infraestructure. New SNMP trap con- + sole to receive SNMP traps and assigning alerts. Internal messaging + system, to notify events to Pandora users. Agent detail view autore- + fresh New main agent group view Improved database management system, + that allows to manage much more data. + + Pandora is a project initiated and mainly developed by Sancho Lerena, + at present other people is working on it: Raul Mateos, David Vil- + lanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel + Arostegui We want to thank many other people who help us with transla- + tion, graphic design, bugs reporting and interesting ideas. + Pandora is Free Software, and is published under GPL Licence. In order + to know the last features, go to the official web site of the project + in http://pandora.sourceforge.net. + + +AAUUTTHHOORR + Pandora Free Monitoring System is made and copyrighted by Sancho Lerena + Pandora is a project initiated and mainly + developed by Sancho Lerena, at present other people is working on it: + Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan + Barajas and Manuel Arostegui We want to thank many other people who + help us with translation, graphic design, bugs reporting and interest- + ing ideas. + + + +SSEEEE AALLSSOO + ppaannddoorraa + ppaannddoorraa__sseerrvveerr + ppaannddoorraa__aaggeennttss + ppaannddoorraa__ccoonnssoollee + + + + PandoraFMS() diff --git a/pandora_doc/fr/man/pandora_agents b/pandora_doc/fr/man/pandora_agents new file mode 100644 index 0000000000..25abac18b0 --- /dev/null +++ b/pandora_doc/fr/man/pandora_agents @@ -0,0 +1,674 @@ +.TH Pandora Agents + +.SH NAME + +pandora_agents - Agents for PandoraFMS + +.SH AVAILABILITY + +Linux, AIX, Solaris, Windows... + +.SH DESCRIPTION + +This is the man page for Linux Pandora Agents. + +Pandora FMS agents collect all system’s data. They are executed in each local system, although they can +also collect remote information by installing monitoring systems for the agent in several different +machines - called satellite agents + +They are developed to work under a given platform, making use of the specific tools of the language +being used: VBSCript/Windows Scripting for Microsoft platforms (Win2000, WinXP y Win2003), +ShellScripting for UNIX - which includes Linux, Solaris, AIX, HP-UX and BSD, as well as the Nokia’s +IPSO. Pandora agents can be developed in virtually any language, given its simple API system and being +open source. There are branches of the Pandora project started for the creation of agents in Posix C, Perl +and Java for those systems requiring closed agents. + +Pandora Agents are Free Software, i.e., the way agents collect and sent information is documented. An +agent can be recreated in any programming language, and can be upgraded easily, to improve aspects of +the program not covered so far. + +This man describes the installation of agents in machines running over Linux operating systems. + +.SH SYPNOSIS + +.B Generic role of the agents + +Regardless the platform an agent is running on, this is formed of the following elements: +A script (or binary application in Windows) that collects and sends the data to the server. For UNIX +machines the script is called pandora_agent.sh and is executed directly from the Pandora agent folder. + +One or several configuration fifiles where the values to be collected are defined. The file is called +pandora_agent.conf both for Windows and Unix machines. + +This simple structure makes it easy the customisation of an agent. There is no need to code again the +agent to modify the way it works, as the configuration file holds most of the parameters needed to do so. + +.B Main Script + +The main script is the executable file that collects the data specified in the configuration file. It sends the +data to the server in XML. In Windows machines application is installed as a service and is executed at +the time intervals set in the configuration fifile. In machines running over UNIX the main script is run +through a special script called pandora_agent_daemon, and runs continuously in the machine as a +process. + +.B Configuration File + +The data collection in the host system is the gathering of independent data units, which are defined in the +pandora_agent.conf fifile. The pandora_agent.conf file is divided in two parts: + +.I General parameters + + Configure general options about server location, agent name, interval, and other general options. + +.I Module definitions + +Configure and defined the method of extraction for each piece of information that will be extracted from local host and sent to Pandora Server. + +.B General parameters + +The general parameters of the agent configuration are defined in this section. Some of these parameters +are common for all systems and others specific for Windows or UNIX. The general parameters are: +.I server_path: + +The server path is the full path of the folder where the server stores the data sent by the +agent. It is usually: /opt/pandora/data_in. +.I server_ip: + +The server IP is the IP address or the host name of the Pandora server, where the data will +be stored. The host must be reachable and must be listening to port 22 (SSH). + +.I temporal: + + This is the full path of the folder where the agent stores the data locally, before it is sent to +the server. It must be said that the data packages are deleted once the agent tries to contact Pandora +server, no matter if the communication was successful or not. This is done to avoid over flcoding hard +drive of the host system where the agent runs. The location of the local folder varies with the +architecture of the host system. In Unix systems this is usually /opt/pandora/data_out + +.I interval: + +This is the time interval in seconds in which the agent will collect data from the host system +and send the data packages to the server. The recommended value ranges from 300 (5 minutes) to 600 +(10 minutes). This number could be larger, although it is important to consider the impact of a larger +number on the database. + +.I debug: + +This parameter is used to test the generation of data fifiles, forcing the agent to do not copy data +file to server, so you can check data fifile contents and copy XML data fifile manually. It does not delete +any data when the process is finished, so data fifile will be in temp directory. The activity is written in a +log fifile. The fifile is named pandora_agent.log. This log fifile can be used to test the system and to +investigate potential issues. + +.I agent_name: + +This is an alternative host name. This parameter is optional as if it is not declared the +name is obtained directly from the system. + +.I checksum: + +This parameter can take two values. If the value is 1, the checksums are performed through +MD5. If the value is 0, the checksum is not performed at all. This may be useful for systems where a +MD5 tool cannot be implemented. If the checksum is deactivated in the agent it must be also +disconnected in the server. Otherwise it could create problems. + +An example of the general parameters from a Unix configuration would be. + +.I server_ip Pandora_Server +.br +.I server_path /opt/pandora/data_in +.br +.I temporal /opt/pandora/data_out +.br +.I interval 300 +.br +.I agent_name satellite_agent +.br +.I debug 1 +.br +.I checksum 1 + +.B Module definition + +Each data item that is to be collected must be defined precisely in each module, using the exact syntax. +As many values as necessary can be set to be collected, adding at the end of the general parameters as +many modules as the number of values to collect. Each module is made of several directives. Following +is a descriptive relation of all module marks available for Unix agents. + +.I module_begin + +Defines the beginning of the module. + +.I module_name name + +Name of the module. This is the id for this module, choose a name without blank spaces and not very +long. There is no practical limitation (max of 250 chars) but will be easier to manage if you use short +names. This name CANNOT be duplicated with a similar name in the same agent. This name could be +duplicated with other modules in other agents. + +.I module_type type + +Data type the module will handle. There are four data types for agents: + +.TP + +Numeric (generic_data). + +Simple numeric data, flfloat or integer. If the values are of the float type, they will be truncated to their integer value. + +.TP +Incremental (generic_date_inc). + +Integer numeric data equal to the differential between the actual value and the previous one. When this differential is negative the value is set to 0. +Alphanumeric (generic_string). Text strings up to 255 characters. + +.TP• +Monitors (generic_proc). + +Stores numerically the status of the processes. This data type is called monitor because it assigns 0 to an "Incorrect" status and any value above 0 to any "Correct" status. + +.P +.I module_exec command + +This is the generic "command to execute" directive. Both, for Unix and Windows agents there is only one +directive to obtain data in a generic way, executing a single command (you could use pipes for redirecting execution to anoter command). This directive executes a command and stores the returned value. This method is also available on Windows agents. This is the "general purpose method" for both +kind of agents. + +.I module_min value + +This is the minimum valid value for the data generated in this module. If the module has not yet been +defined in the web console this value will be taken from this directive. This directive is not compulsory. + +This value does not override the value defined in the agent if the module does not exist in the +management console. It is created automatically when working on learning mode. + +.I module_max value + +It is the maximum valid value for the data generated in this module. If the module has not been defined in +the web console this value will be taken from this directive. This directive is not compulsory and is not +supported by the Windows agent. This value does not override the value defined in the agent if the +module does not exist in the management console. This is created automatically when working on +learning mode. + +.I module_description text + +This directive is used to add a comment to the module. This directive is not compulsory. This value does +not override the value defined in the agent if the module does not exist in the management console. This +is created automatically when working on learning mode. + +.I module_interval factor + +Pandora 1.2 introduces this new feature. You can, for each module, setup its own interval. This interval +its calculated as a multiply factor for agent interval. For example, if your agent has interval 300 (5 +minutes), and you want a module only be calculated each 15 minutes, you could add this line: +module_interval 3. So this module will be calculated each 300sec x 3 = 900sec (15 minutes). + +.I module_end + +Ends module definition + +.B Agent types + +It is possible to monitor virtually any system with Pandora. This can be done either with a local agent +collecting data directly from the system to be monitored, using a a satellite agent collecting data from a +system by SNMP or using the new Pandora 1.2 agents, the remote agents, who can chack using remote +network polling (TCP, UCP, ICMP/PING and SNMP) remote services, from the Pandora Network Server. + +The local agents can be either Windows or Unix agents. The satellite agents can be implemented using +any of the agents above. The modules are configured to collect data from the external system by, for +example, an SNMPGET tool. + +.B UNIX agents + +.I Introduction to Unix agents + +The in-built UNIX applications and tools make the agents running on this system be very simple. There +are also agents developed for AIX, Linux, Solaris and BSD platforms, some of them very similar but not +identical. Requirements for the installation of Pandora Agents on UNIX +.I AIX + +MD5 signatures are used to guarantee the integrity of the generated data packages. The MD5 package is +integrated in AIX 5.1 and above. There is a freeware package for AIX 4.3 but it has several issues and +might not work correctly. In the case of having problems with the AIX agents the checksum system used +to validate the integrity of the data can be disabled. + +.I Solaris + +The MD5 package is necessary to execute the Solaris agent correctly. This package is available from +http://sunfreeware.com . It can be also downloaded for Solaris 8 from the following URL: + +ftp://ftp.sunfreeware.com/pub/freeware/sparc/8/md5-6142000-sol8-sparc-local.gz +MD5 Package installation on Solaris + +.I root@stest:/tmp:> gzip -d md5-6142000-sol8-sparc-local.gz +.br +.I root@stest:/tmp:> pkgadd -d ./md5-6142000-sol8-sparc-local +.br +.I The following packages are available: +.br +.I 1 SMCmd5 md5 +.br +.I (sparc) 6142000 +.br +.I Select package(s) you wish to process (or ’all’ to process +.br +.I all packages). (default: all) [?,??,q]: 1 +.br +.I Solaris SSH + +The suggested SSH client is OpenSSH. If any other SSH client is to be used it must be considered that +each piece software may have different ways to generate or manage keys. For example, if F-Secure SSH +is used, the public key must be in OpenSSH format when the keys are generated. The format can be +changed from IETF to OpenSSH with F-Secure SSH, using the following command: + +.I ssh-keygen -i -f file_ietf_pubkey + +.B GNU/Linux + +SSH and MD5 should be installed in Linux by default, but if they are not they can be installed using the +tools available in each distribution. + +.B BSD (IPSO) + +SSH and MD5 should be installed by default. If they are not, it is necessary to install them. + +.B Pandora Unix Agent install + +The software comes in a .tar.gz file. First of all the fifile needs to be extracted into a folder, usually +/opt/pandora_agent, although any other folder may be used. If a different folder is used, the daemon +launcher must be modified by changing route to $PANDORA_HOME. + +There is hardly any difference between AIX, Solaris and Linux, and they all work around the hash MD5 +generation binaries. + +This is the structure of the installation in /opt/pandora_agent/ once the fifiles have been extracted: + +.I /opt/pandora_agent/data_out + +Folder where the data collected by the agents is stored. + +.I /opt/pandora_agent/doc + +Folder with information about the agent and its license. + +.I /opt/pandora_agent/pandora_agent.conf + +File where the data to be collected is defined, along side the command to be executed for the data collection. This is the system core, as it defines the main +data to be collected in any Firewall. + +.I /opt/pandora_agent/pandora_user.conffi + +File where several of the parameters to collect data from the monitored system are defined in more detail. + +.I /opt/pandora_agent/pandora_agent.sh + +This is the actual Pandora agent. This file is a shellscript that collects the data configured in the pandora_agent.conf and pandora_user.conf files. It also transfers +the data packages to the Pandora server. + +.I /opt/pandora_agent/pandora_agent_daemon + +Start and stop script. It makes a call to pandora_agent.sh. It offers two options, start and stop. + +.I /opt/pandora_agent/pandora.log + +Textfifile where the activity of the Pandora agent is saved, when the agent is executed in debugging mode. + +.B Key generation + +The SSH keys generated must be: + + SSH version2 keys +• + Open SSH format keys +• + DiffieHellman (DH) format keys + +• +To generate the keys the command ssh-keygen is executed followed by the specific parameters for our +operating system. Please, create key WITHOUT password. + +The public key must be copied into the /home/.pandora/authorized_keys fifile in the Pandora +server. Before starting the Pandora agent the SSH authentication must be checked. To do this the +following command must be executed on the agent machine: + +.I $ ssh pandora@pandora_server + +The system must connect successfully BEFORE launching the Pandora agent. + +.B First running of the Unix agent + +To start the agent it is only necessary to execute pandora_agent_daemon start from /opt/pandora_client. +Pandora Agent creates a file (/var/run/pandora.pid) with the PID number of the process when it is started. + +For IPSO systems the agent will be started with a nice -10 priority, so it becomes the process with the +lowest priority over the system CPU. It will be executed when no other processes with a higher priority +are waiting in the system CPU queue. + +In BSD systems the maximum priority is +20 and the lowest -20. + +To stop agent, execute pandora_agent_daemon stop from /opt/pandora_agent. + +.B Advanced configuration for Unix Agent + +The real power of Pandora resides in the capability of the agents to run user defined scripts. This could +be used to collect specific data or to perform an operation to return any desired value. This is the purpose +of pandora_user.conf. + +This file is executed every in agent loop. It is a shell-script in which any command can be executed, as +long as the output is in the XML format the agent uses to send data to the server. The XML structure +would be: + +.I +.br +.I NAME +.br +.I TYPE +.br +.I DATA +.br +.I + +Where NAME, TYPE and DATA are the variables already defined in previous sections. The XML must +be built manually, usually using echo commands. + +.SH EXAMPLES + +An example of a Unix module would be: + +.I module_begin +.br +.I module_name cpu_user +.br +.I module_type generic_data +.br +.I module_exec vmstat | tail -1 | awk ’{ print $14 }’ +.br +.I module_min 0 +.br +.I module_max 100 +.br +.I module_description User CPU +.br +.I module_end + +This would be the script a customized agent would use for Checkpoint FW1 in IPSO agents: + +.I #!/bin/sh +.br +.I # Pandora User-Defined acquisition script +.br +.I # This code is under GPL licence +.br +.I # Please refer documentation for more example and a more +.br +.I # depth usage instructions +.br +.I # mbuf clusters usados (%) +.br +.I MBUF_TOTAL=‘netstat -m |grep "mbuf cluster" | tr -s "/" " " |awk ’{ print $2 }’‘ +.br +.I MBUF_USED=‘netstat -m |grep "mbuf cluster" | tr -s "/" " " |awk ’{ print $1 }’‘ +.br +.I MBUF_USED_PER=‘echo $MBUF_TOTAL $MBUF_USED | awk ’{ print $2 / ($1 / 100) } +.br +.I echo "" +.br +.I echo "MBUF_CLUSTER_USED_PER" +.br +.I echo "$MBUF_USED_PER" +.br +.I echo "generic_data" +.br +.I echo "" + +A more complex example could be: + +.I #!/bin/sh +.br +.I # Pandora User-Defined acquisition script +.br +.I # This code is under GPL licence +.br +.I # Please refer documentation for more example and a more +.br +.I # depth usage instructions +.br +.I # Calculating the number of packages generated by ETH2, +.br +.I # if nothing is generated +.br +.I # within 20 seconds an alert is rosen +.br +.I # Perform the calculation between 8 to 23h. Return ok for times +.br +.I # outside this range +.br +.I echo "" +.br +.I echo "Packet_Generator_Check" +.br +.I echo "generic_proc" +.br +.I UNO=‘ifconfig eth2 | grep "TX packets" | cut -f 2 -d ":" | grep -o -e "[0-9]*"‘ +.br +.I sleep 20 +.br +.I DOS=‘ifconfig eth2 | grep "TX packets" | cut -f 2 -d ":" | grep -o -e "[0-9]*"‘ +.br +.I HORA=‘date "+%k"‘ +.br +.I if [ "$HORA" -lt "8" ] && [ "$HORA" -gt "11" ] +.br +.I then +.br +.I # Time out of range, no checking, everything OK +.br +.I # Fuera de hora, no compruebo, esta OK +.br +.I echo "1" +.br +.I else +.br +.I if [ "$UNO" == "$DOS" ] +.br +.I then +.br +.I echo "0" +.br +.I else +.br +.I echo "1" +.br +.I fi +.br +.I fi +.br +.I echo "" + +.B Implementation examples for Unix Agents + +Example #1: calculate the number of HITS of the main page of an Apache Web server: + +.I module_begin +.br +.I module_name WEB_Hits +.br +.I module_type generic_data_inc +.br +.I module_exec cat /var/log/apache/access.log | grep "index" | wc -l +.br +.I module_end + +Example: check if the process of the DNS server (named) is active or fell over: + +.I module_begin +.br +.I module_name DNS_Daemon +.br +.I module_type generic_proc +.br +.I module_exec ps -Af | grep named | grep -v "grep" | wc -l +.br +.I module_end + +Complete example of the configuration of an agent for Linux + # General Parameters + # ================== +.I server_ip 192.168.100.45 +.br +.I server_path /opt/pandora/data_in +.br +.I pandora_path /opt/pandora_ng/ +.br +.I temporal /opt/pandora_ng/data_out +.br +.I interval 300 +.br +.I hostname linuxbox01 +.br +.I debug 0 +.br +.I checksum 1 + +# Module Definition +# ================= +.I module_begin +.br +.I module_name cpu_user +.br +.I module_type generic_data +.br +.I module_exec vmstat 1 2 | tail -1 | awk ’{ print $14 }’ +.br +.I module_end + +.I module_begin +.br +.I module_name cpu_sys +.br +.I module_type generic_data +.br +.I module_exec vmstat 1 2 | tail -1 | awk ’{ print $14 }’ +.br +.I module_end + +.I module_begin +.br +.I module_name disk_root_free +.br +.I module_type generic_data +.br +.I module_exec df -kh / | tail -1 | awk ’{ print 100 - $5 }’ +.br +.I module_end + +.I module_begin +.br +.I module_name disk_store_free +.br +.I module_type generic_data +.br +.I module_exec df -kh /store | tail -1 | awk ’{ print 100 - $5 }’ +.br +.I module_end + +.I module_begin +.br +.I module_name memfree +.br +.I module_type generic_data +.br +.I module_exec cat /proc/meminfo | grep MemFree | cut -c 10-23 +.br +.I module_end + +.I module_begin +.br +.I module_name memused +.br +.I module_type generic_data +.br +.I module_exec cat /proc/meminfo | grep "Active" | cut -c 8- | cut -f 1 -d "k" +.br +.I module_end + +.I module_begin +.br +.I module_name proctotal +.br +.I module_type generic_data +.br +.I module_exec ps -A | wc -l +.br +.I module_end + +.I module_begin +.br +.I module_name sshd +.br +.I module_type generic_proc +.br +.I module_exec ps -Af | grep sshd | grep -v "grep" | wc -l +.br +.I module_end + +.I module_begin +.br +.I module_name WEB_Hits +.br +.I module_type generic_data_inc +.I module_exec cat /var/log/apache/access.log | grep "index.php" | wc -l +.br +.I module_end + +.I module_begin +.br +.I module_name eMails_proc +.br +.I module_type generic_data_inc +.br +.I module_exec cat /var/log/mail/mail.log | grep "message-id" | wc -l +.br +.I module_end + +.I module_begin +.br +.I module_name FTP_sessions +.br +.I module_type generic_data_inc +.br +.I module_exec cat /var/log/syslog | grep "FTP session opened" | wc -l +.br +.I module_end + +.I module_begin +.br +.I module_name eMails_SPAM +.br +.I module_type generic_data_inc +.br +.I module_exec cat /var/log/mail/mail.log | grep "identified spam" | wc -l +.br +.I module_end + +.SH AUTHOR + +Pandora Free Monitoring System is made and copyrighted by Sancho Lerena +Pandora is a project initiated and mainly developed by Sancho Lerena, at present other people is working +on it: Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel Arostegui We want to +thank many other people who help us with translation, graphic design, bugs reporting and interesting +ideas. +.br + + +.SH SEE ALSO + +.B pandora +.br +.B pandora_server +.br +.B pandora_agents +.br +.B pandora_console + + diff --git a/pandora_doc/fr/man/pandora_agents.1 b/pandora_doc/fr/man/pandora_agents.1 new file mode 100644 index 0000000000..20d615e601 --- /dev/null +++ b/pandora_doc/fr/man/pandora_agents.1 @@ -0,0 +1,616 @@ +Pandora(Agents) Pandora(Agents) + + + +NNAAMMEE + pandora_agents - Agents for PandoraFMS + + +AAVVAAIILLAABBIILLIITTYY + Linux, AIX, Solaris, Windows... + + +DDEESSCCRRIIPPTTIIOONN + This is the man page for Linux Pandora Agents. + + Pandora FMS agents collect all system’s data. They are executed in + each local system, although they can also collect remote information by + installing monitoring systems for the agent in several different + machines - called satellite agents + + They are developed to work under a given platform, making use of the + speci fic tools of the language being used: VBSCript/Windows Scripting + for Microsoft platforms (Win2000, WinXP y Win2003), ShellScripting for + UNIX - which includes Linux, Solaris, AIX, HP-UX and BSD, as well as + the Nokia’s IPSO. Pandora agents can be developed in virtually any + language, given its simple API system and being open source. There are + branches of the Pandora project started for the creation of agents in + Posix C, Perl and Java for those systems requiring closed agents. + + Pandora Agents are Free Software, i.e., the way agents collect and sent + information is documented. An agent can be recreated in any programming + language, and can be upgraded easily, to improve aspects of the program + not covered so far. + + This man describes the installation of agents in machines running over + Linux operating systems. + + +SSYYPPNNOOSSIISS + GGeenneerriicc rroollee ooff tthhee aaggeennttss + + Regardless the platform an agent is running on, this is formed of the + following elements: A script (or binary application in Windows) that + collects and sends the data to the server. For UNIX machines the script + is called pandora_agent.sh and is executed directly from the Pandora + agent folder. + + One or several configuration fifiles where the values to be collected + are defined. The file is called pandora_agent.conf both for Windows and + Unix machines. + + This simple structure makes it easy the customisation of an agent. + There is no need to code again the agent to modify the way it works, as + the configuration file holds most of the parameters needed to do so. + + MMaaiinn SSccrriipptt + + The main script is the executable file that collects the data specified + in the configuration file. It sends the data to the server in XML. In + Windows machines application is installed as a service and is executed + at the time intervals set in the configuration fifile. In machines run- + ning over UNIX the main script is run through a special script called + pandora_agent_daemon, and runs continuously in the machine as a pro- + cess. + + CCoonnffiigguurraattiioonn FFiillee + + The data collection in the host system is the gathering of independent + data units, which are defined in the pandora_agent.conf fifile. The + pandora_agent.conf file is divided in two parts: + + _G_e_n_e_r_a_l _p_a_r_a_m_e_t_e_r_s + + Configure general options about server location, agent name, interval, + and other general options. + + _M_o_d_u_l_e _d_e_f_i_n_i_t_i_o_n_s + + Configure and defined the method of extraction for each piece of infor- + mation that will be extracted from local host and sent to Pandora + Server. + + GGeenneerraall ppaarraammeetteerrss + + The general parameters of the agent configuration are defined in this + section. Some of these parameters are common for all systems and others + specific for Windows or UNIX. The general parameters are: _s_e_r_v_e_r___p_a_t_h_: + + The server path is the full path of the folder where the server stores + the data sent by the agent. It is usually: /opt/pandora/data_in. + _s_e_r_v_e_r___i_p_: + + The server IP is the IP address or the host name of the Pandora server, + where the data will be stored. The host must be reachable and must be + listening to port 22 (SSH). + + _t_e_m_p_o_r_a_l_: + + This is the full path of the folder where the agent stores the data + locally, before it is sent to the server. It must be said that the data + packages are deleted once the agent tries to contact Pandora server, no + matter if the communication was successful or not. This is done to + avoid over flcoding hard drive of the host system where the agent runs. + The location of the local folder varies with the architecture of the + host system. In Unix systems this is usually /opt/pandora/data_out + + _i_n_t_e_r_v_a_l_: + + This is the time interval in seconds in which the agent will collect + data from the host system and send the data packages to the server. The + recommended value ranges from 300 (5 minutes) to 600 (10 minutes). This + number could be larger, although it is important to consider the impact + of a larger number on the database. + + _d_e_b_u_g_: + + This parameter is used to test the generation of data fifiles, forcing + the agent to do not copy data file to server, so you can check data + fifile contents and copy XML data fifile manually. It does not delete + any data when the process is finished, so data fifile will be in temp + directory. The activity is written in a log fifile. The fifile is named + pandora_agent.log. This log fifile can be used to test the system and + to investigate potential issues. + + _a_g_e_n_t___n_a_m_e_: + + This is an alternative host name. This parameter is optional as if it + is not declared the name is obtained directly from the system. + + _c_h_e_c_k_s_u_m_: + + This parameter can take two values. If the value is 1, the checksums + are performed through MD5. If the value is 0, the checksum is not per- + formed at all. This may be useful for systems where a MD5 tool cannot + be implemented. If the checksum is deactivated in the agent it must be + also disconnected in the server. Otherwise it could create problems. + + An example of the general parameters from a Unix configuration would + be. + + _s_e_r_v_e_r___i_p _P_a_n_d_o_r_a___S_e_r_v_e_r + _s_e_r_v_e_r___p_a_t_h _/_o_p_t_/_p_a_n_d_o_r_a_/_d_a_t_a___i_n + _t_e_m_p_o_r_a_l _/_o_p_t_/_p_a_n_d_o_r_a_/_d_a_t_a___o_u_t + _i_n_t_e_r_v_a_l _3_0_0 + _a_g_e_n_t___n_a_m_e _s_a_t_e_l_l_i_t_e___a_g_e_n_t + _d_e_b_u_g _1 + _c_h_e_c_k_s_u_m _1 + + MMoodduullee ddeeffiinniittiioonn + + Each data item that is to be collected must be defined precisely in + each module, using the exact syntax. As many values as necessary can + be set to be collected, adding at the end of the general parameters as + many modules as the number of values to collect. Each module is made of + several directives. Following is a descriptive relation of all module + marks available for Unix agents. + + _m_o_d_u_l_e___b_e_g_i_n + + Defines the beginning of the module. + + _m_o_d_u_l_e___n_a_m_e _n_a_m_e + + Name of the module. This is the id for this module, choose a name with- + out blank spaces and not very long. There is no practical limitation + (max of 250 chars) but will be easier to manage if you use short names. + This name CANNOT be duplicated with a similar name in the same agent. + This name could be duplicated with other modules in other agents. + + _m_o_d_u_l_e___t_y_p_e _t_y_p_e + + Data type the module will handle. There are four data types for agents: + + + + Numeric (generic_data). + + Simple numeric data, flfloat or integer. If the values are of + the float type, they will be truncated to their integer value. + + + Incremental (generic_date_inc). + + Integer numeric data equal to the differential between the + actual value and the previous one. When this differential is + negative the value is set to 0. Alphanumeric (generic_string). + Text strings up to 255 characters. + + + Monitors (generic_proc). + + Stores numerically the status of the processes. This data type + is called monitor because it assigns 0 to an "Incorrect" status + and any value above 0 to any "Correct" status. + + + _m_o_d_u_l_e___e_x_e_c _c_o_m_m_a_n_d + + This is the generic "command to execute" directive. Both, for Unix and + Windows agents there is only one directive to obtain data in a generic + way, executing a single command (you could use pipes for redirecting + execution to anoter command). This directive executes a command and + stores the returned value. This method is also available on Windows + agents. This is the "general purpose method" for both kind of agents. + + _m_o_d_u_l_e___m_i_n _v_a_l_u_e + + This is the minimum valid value for the data generated in this module. + If the module has not yet been defined in the web console this value + will be taken from this directive. This directive is not compulsory. + + This value does not override the value defined in the agent if the mod- + ule does not exist in the management console. It is created automati- + cally when working on learning mode. + + _m_o_d_u_l_e___m_a_x _v_a_l_u_e + + It is the maximum valid value for the data generated in this module. If + the module has not been defined in the web console this value will be + taken from this directive. This directive is not compulsory and is not + supported by the Windows agent. This value does not override the value + de fined in the agent if the module does not exist in the management + console. This is created automatically when working on learning mode. + + _m_o_d_u_l_e___d_e_s_c_r_i_p_t_i_o_n _t_e_x_t + + This directive is used to add a comment to the module. This directive + is not compulsory. This value does not override the value defined in + the agent if the module does not exist in the management console. This + is created automatically when working on learning mode. + + _m_o_d_u_l_e___i_n_t_e_r_v_a_l _f_a_c_t_o_r + + Pandora 1.2 introduces this new feature. You can, for each module, + setup its own interval. This interval its calculated as a multiply fac- + tor for agent interval. For example, if your agent has interval 300 (5 + minutes), and you want a module only be calculated each 15 minutes, you + could add this line: module_interval 3. So this module will be calcu- + lated each 300sec x 3 = 900sec (15 minutes). + + _m_o_d_u_l_e___e_n_d + + Ends module definition + + AAggeenntt ttyyppeess + + It is possible to monitor virtually any system with Pandora. This can + be done either with a local agent collecting data directly from the + system to be monitored, using a a satellite agent collecting data from + a system by SNMP or using the new Pandora 1.2 agents, the remote + agents, who can chack using remote network polling (TCP, UCP, ICMP/PING + and SNMP) remote services, from the Pandora Network Server. + + The local agents can be either Windows or Unix agents. The satellite + agents can be implemented using any of the agents above. The modules + are con figured to collect data from the external system by, for exam- + ple, an SNMPGET tool. + + UUNNIIXX aaggeennttss + + _I_n_t_r_o_d_u_c_t_i_o_n _t_o _U_n_i_x _a_g_e_n_t_s + + The in-built UNIX applications and tools make the agents running on + this system be very simple. There are also agents developed for AIX, + Linux, Solaris and BSD platforms, some of them very similar but not + identical. Requirements for the installation of Pandora Agents on UNIX + _A_I_X + + MD5 signatures are used to guarantee the integrity of the generated + data packages. The MD5 package is integrated in AIX 5.1 and above. + There is a freeware package for AIX 4.3 but it has several issues and + might not work correctly. In the case of having problems with the AIX + agents the checksum system used to validate the integrity of the data + can be disabled. + + _S_o_l_a_r_i_s + + The MD5 package is necessary to execute the Solaris agent correctly. + This package is available from http://sunfreeware.com . It can be also + downloaded for Solaris 8 from the following URL: + + ftp://ftp.sunfreeware.com/pub/freeware/sparc/8/md5-6142000-sol8-sparc- + local.gz MD5 Package installation on Solaris + + _r_o_o_t_@_s_t_e_s_t_:_/_t_m_p_:_> _g_z_i_p _-_d _m_d_5_-_6_1_4_2_0_0_0_-_s_o_l_8_-_s_p_a_r_c_-_l_o_c_a_l_._g_z + _r_o_o_t_@_s_t_e_s_t_:_/_t_m_p_:_> _p_k_g_a_d_d _-_d _._/_m_d_5_-_6_1_4_2_0_0_0_-_s_o_l_8_-_s_p_a_r_c_-_l_o_c_a_l + _T_h_e _f_o_l_l_o_w_i_n_g _p_a_c_k_a_g_e_s _a_r_e _a_v_a_i_l_a_b_l_e_: + _1 _S_M_C_m_d_5 _m_d_5 + _(_s_p_a_r_c_) _6_1_4_2_0_0_0 + _S_e_l_e_c_t _p_a_c_k_a_g_e_(_s_) _y_o_u _w_i_s_h _t_o _p_r_o_c_e_s_s _(_o_r ’_a_l_l’ _t_o _p_r_o_c_e_s_s + _a_l_l _p_a_c_k_a_g_e_s_)_. _(_d_e_f_a_u_l_t_: _a_l_l_) _[_?_,_?_?_,_q_]_: _1 + _S_o_l_a_r_i_s _S_S_H + + The suggested SSH client is OpenSSH. If any other SSH client is to be + used it must be considered that each piece software may have different + ways to generate or manage keys. For example, if F-Secure SSH is used, + the public key must be in OpenSSH format when the keys are generated. + The format can be changed from IETF to OpenSSH with F-Secure SSH, using + the following command: + + _s_s_h_-_k_e_y_g_e_n _-_i _-_f _f_i_l_e___i_e_t_f___p_u_b_k_e_y + + GGNNUU//LLiinnuuxx + + SSH and MD5 should be installed in Linux by default, but if they are + not they can be installed using the tools available in each distribu- + tion. + + BBSSDD ((IIPPSSOO)) + + SSH and MD5 should be installed by default. If they are not, it is nec- + essary to install them. + + PPaannddoorraa UUnniixx AAggeenntt iinnssttaallll + + The software comes in a .tar.gz file. First of all the fifile needs to + be extracted into a folder, usually /opt/pandora_agent, although any + other folder may be used. If a different folder is used, the daemon + launcher must be modified by changing route to $PANDORA_HOME. + + There is hardly any difference between AIX, Solaris and Linux, and they + all work around the hash MD5 generation binaries. + + This is the structure of the installation in /opt/pandora_agent/ once + the fifiles have been extracted: + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_d_a_t_a___o_u_t + + Folder where the data collected by the agents is stored. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_d_o_c + + Folder with information about the agent and its license. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_p_a_n_d_o_r_a___a_g_e_n_t_._c_o_n_f + + File where the data to be collected is defined, along side the command + to be executed for the data collection. This is the system core, as it + defines the main data to be collected in any Firewall. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_p_a_n_d_o_r_a___u_s_e_r_._c_o_n_ffi + + File where several of the parameters to collect data from the monitored + system are defined in more detail. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_p_a_n_d_o_r_a___a_g_e_n_t_._s_h + + This is the actual Pandora agent. This file is a shellscript that col- + lects the data con figured in the pandora_agent.conf and pan- + dora_user.conf files. It also transfers the data packages to the Pan- + dora server. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_p_a_n_d_o_r_a___a_g_e_n_t___d_a_e_m_o_n + + Start and stop script. It makes a call to pandora_agent.sh. It offers + two options, start and stop. + + _/_o_p_t_/_p_a_n_d_o_r_a___a_g_e_n_t_/_p_a_n_d_o_r_a_._l_o_g + + Textfifile where the activity of the Pandora agent is saved, when the + agent is executed in debugging mode. + + KKeeyy ggeenneerraattiioonn + + The SSH keys generated must be: + + SSH version2 keys • + Open SSH format keys • + Dif fieHellman (DH) format keys • To generate the keys the command + ssh-keygen is executed followed by the specific parameters for our + operating system. Please, create key WITHOUT password. + + The public key must be copied into the /home/.pandora/authorized_keys + fifile in the Pandora server. Before starting the Pandora agent the SSH + authentication must be checked. To do this the following command must + be executed on the agent machine: + + _$ _s_s_h _p_a_n_d_o_r_a_@_p_a_n_d_o_r_a___s_e_r_v_e_r + + The system must connect successfully BEFORE launching the Pandora + agent. + + FFiirrsstt rruunnnniinngg ooff tthhee UUnniixx aaggeenntt + + To start the agent it is only necessary to execute pandora_agent_daemon + start from /opt/pandora_client. Pandora Agent creates a file + (/var/run/pandora.pid) with the PID number of the process when it is + started. + + For IPSO systems the agent will be started with a nice -10 priority, so + it becomes the process with the lowest priority over the system CPU. It + will be executed when no other processes with a higher priority are + waiting in the system CPU queue. + + In BSD systems the maximum priority is +20 and the lowest -20. + + To stop agent, execute pandora_agent_daemon stop from /opt/pan- + dora_agent. + + AAddvvaanncceedd ccoonnfigguurraattiioonn ffoorr UUnniixx AAggeenntt + + The real power of Pandora resides in the capability of the agents to + run user defined scripts. This could be used to collect specific data + or to perform an operation to return any desired value. This is the + purpose of pandora_user.conf. + + This file is executed every in agent loop. It is a shell-script in + which any command can be executed, as long as the output is in the XML + format the agent uses to send data to the server. The XML structure + would be: + + _<_m_o_d_u_l_e_> + _<_n_a_m_e_>_N_A_M_E_<_/_n_a_m_e_> + _<_t_y_p_e_>_T_Y_P_E_<_/_t_y_p_e_> + _<_d_a_t_a_>_D_A_T_A_<_/_d_a_t_a_> + _<_/_m_o_d_u_l_e_> + + Where NAME, TYPE and DATA are the variables already defined in previous + sections. The XML must be built manually, usually using echo commands. + + +EEXXAAMMPPLLEESS + An example of a Unix module would be: + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _c_p_u___u_s_e_r + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _v_m_s_t_a_t _| _t_a_i_l _-_1 _| _a_w_k ’_{ _p_r_i_n_t _$_1_4 _}’ + _m_o_d_u_l_e___m_i_n _0 + _m_o_d_u_l_e___m_a_x _1_0_0 + _m_o_d_u_l_e___d_e_s_c_r_i_p_t_i_o_n _U_s_e_r _C_P_U + _m_o_d_u_l_e___e_n_d + + This would be the script a customized agent would use for Checkpoint + FW1 in IPSO agents: + + _#_!_/_b_i_n_/_s_h + _# _P_a_n_d_o_r_a _U_s_e_r_-_D_e_f_i_n_e_d _a_c_q_u_i_s_i_t_i_o_n _s_c_r_i_p_t + _# _T_h_i_s _c_o_d_e _i_s _u_n_d_e_r _G_P_L _l_i_c_e_n_c_e + _# _P_l_e_a_s_e _r_e_f_e_r _d_o_c_u_m_e_n_t_a_t_i_o_n _f_o_r _m_o_r_e _e_x_a_m_p_l_e _a_n_d _a _m_o_r_e + _# _d_e_p_t_h _u_s_a_g_e _i_n_s_t_r_u_c_t_i_o_n_s + _# _m_b_u_f _c_l_u_s_t_e_r_s _u_s_a_d_o_s _(_%_) + _M_B_U_F___T_O_T_A_L_= ‘_n_e_t_s_t_a_t _-_m _|_g_r_e_p _m_b_u_f _c_l_u_s_t_e_r _| _t_r _-_s _/ _|_a_w_k ’_{ _p_r_i_n_t + _$_2 _}’‘ + _M_B_U_F___U_S_E_D_=‘_n_e_t_s_t_a_t _-_m _|_g_r_e_p _m_b_u_f _c_l_u_s_t_e_r _| _t_r _-_s _/ _|_a_w_k ’_{ _p_r_i_n_t _$_1 + _}’‘ + _M_B_U_F___U_S_E_D___P_E_R_= ‘_e_c_h_o _$_M_B_U_F___T_O_T_A_L _$_M_B_U_F___U_S_E_D _| _a_w_k ’_{ _p_r_i_n_t _$_2 _/ _(_$_1 _/ + _1_0_0_) _} + _e_c_h_o _<_m_o_d_u_l_e_> + _e_c_h_o _<_n_a_m_e_>_M_B_U_F___C_L_U_S_T_E_R___U_S_E_D___P_E_R_<_/_n_a_m_e_> + _e_c_h_o _<_d_a_t_a_>_$_M_B_U_F___U_S_E_D___P_E_R_<_/_d_a_t_a_> + _e_c_h_o _<_t_y_p_e_>_g_e_n_e_r_i_c___d_a_t_a_<_/_t_y_p_e_> + _e_c_h_o _<_/_m_o_d_u_l_e_> + + A more complex example could be: + + _#_!_/_b_i_n_/_s_h + _# _P_a_n_d_o_r_a _U_s_e_r_-_D_e_f_i_n_e_d _a_c_q_u_i_s_i_t_i_o_n _s_c_r_i_p_t + _# _T_h_i_s _c_o_d_e _i_s _u_n_d_e_r _G_P_L _l_i_c_e_n_c_e + _# _P_l_e_a_s_e _r_e_f_e_r _d_o_c_u_m_e_n_t_a_t_i_o_n _f_o_r _m_o_r_e _e_x_a_m_p_l_e _a_n_d _a _m_o_r_e + _# _d_e_p_t_h _u_s_a_g_e _i_n_s_t_r_u_c_t_i_o_n_s + _# _C_a_l_c_u_l_a_t_i_n_g _t_h_e _n_u_m_b_e_r _o_f _p_a_c_k_a_g_e_s _g_e_n_e_r_a_t_e_d _b_y _E_T_H_2_, + _# _i_f _n_o_t_h_i_n_g _i_s _g_e_n_e_r_a_t_e_d + _# _w_i_t_h_i_n _2_0 _s_e_c_o_n_d_s _a_n _a_l_e_r_t _i_s _r_o_s_e_n + _# _P_e_r_f_o_r_m _t_h_e _c_a_l_c_u_l_a_t_i_o_n _b_e_t_w_e_e_n _8 _t_o _2_3_h_. _R_e_t_u_r_n _o_k _f_o_r _t_i_m_e_s + _# _o_u_t_s_i_d_e _t_h_i_s _r_a_n_g_e + _e_c_h_o _<_m_o_d_u_l_e_> + _e_c_h_o _<_n_a_m_e_>_P_a_c_k_e_t___G_e_n_e_r_a_t_o_r___C_h_e_c_k_<_/_n_a_m_e_> + _e_c_h_o _<_t_y_p_e_>_g_e_n_e_r_i_c___p_r_o_c_<_/_t_y_p_e_> + _U_N_O_=‘_i_f_c_o_n_f_i_g _e_t_h_2 _| _g_r_e_p _T_X _p_a_c_k_e_t_s _| _c_u_t _-_f _2 _-_d _: _| _g_r_e_p _-_o _-_e + _[_0_-_9_]_* ‘ + _s_l_e_e_p _2_0 + _D_O_S_= ‘_i_f_c_o_n_f_i_g _e_t_h_2 _| _g_r_e_p _T_X _p_a_c_k_e_t_s _| _c_u_t _-_f _2 _-_d _: _| _g_r_e_p _-_o _-_e + _[_0_-_9_]_* ‘ + _H_O_R_A_=‘_d_a_t_e _+_%_k ‘ + _i_f _[ _$_H_O_R_A _-_l_t _8 _] _&_& _[ _$_H_O_R_A _-_g_t _1_1 _] + _t_h_e_n + _# _T_i_m_e _o_u_t _o_f _r_a_n_g_e_, _n_o _c_h_e_c_k_i_n_g_, _e_v_e_r_y_t_h_i_n_g _O_K + _# _F_u_e_r_a _d_e _h_o_r_a_, _n_o _c_o_m_p_r_u_e_b_o_, _e_s_t_a _O_K + _e_c_h_o _<_d_a_t_a_>_1_<_/_d_a_t_a_> + _e_l_s_e + _i_f _[ _$_U_N_O _=_= _$_D_O_S _] + _t_h_e_n + _e_c_h_o _<_d_a_t_a_>_0_<_/_d_a_t_a_> + _e_l_s_e + _e_c_h_o _<_d_a_t_a_>_1_<_/_d_a_t_a_> + _f_i + _f_i + _e_c_h_o _<_/_m_o_d_u_l_e_> + + IImmpplleemmeennttaattiioonn eexxaammpplleess ffoorr UUnniixx AAggeennttss + + Example #1: calculate the number of HITS of the main page of an Apache + Web server: + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _W_E_B___H_i_t_s + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a___i_n_c + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_v_a_r_/_l_o_g_/_a_p_a_c_h_e_/_a_c_c_e_s_s_._l_o_g _| _g_r_e_p _i_n_d_e_x _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + Example: check if the process of the DNS server (named) is active or + fell over: + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _D_N_S___D_a_e_m_o_n + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___p_r_o_c + _m_o_d_u_l_e___e_x_e_c _p_s _-_A_f _| _g_r_e_p _n_a_m_e_d _| _g_r_e_p _-_v _g_r_e_p _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + Complete example of the configuration of an agent for Linux + # General Parameters + # ================== _s_e_r_v_e_r___i_p _1_9_2_._1_6_8_._1_0_0_._4_5 + _s_e_r_v_e_r___p_a_t_h _/_o_p_t_/_p_a_n_d_o_r_a_/_d_a_t_a___i_n + _p_a_n_d_o_r_a___p_a_t_h _/_o_p_t_/_p_a_n_d_o_r_a___n_g_/ + _t_e_m_p_o_r_a_l _/_o_p_t_/_p_a_n_d_o_r_a___n_g_/_d_a_t_a___o_u_t + _i_n_t_e_r_v_a_l _3_0_0 + _h_o_s_t_n_a_m_e _l_i_n_u_x_b_o_x_0_1 + _d_e_b_u_g _0 + _c_h_e_c_k_s_u_m _1 + + # Module Definition # ================= _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _c_p_u___u_s_e_r + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _v_m_s_t_a_t _1 _2 _| _t_a_i_l _-_1 _| _a_w_k ’_{ _p_r_i_n_t _$_1_4 _}’ + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _c_p_u___s_y_s + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _v_m_s_t_a_t _1 _2 _| _t_a_i_l _-_1 _| _a_w_k ’_{ _p_r_i_n_t _$_1_4 _}’ + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _d_i_s_k___r_o_o_t___f_r_e_e + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _d_f _-_k_h _/ _| _t_a_i_l _-_1 _| _a_w_k ’_{ _p_r_i_n_t _1_0_0 _- _$_5 _}’ + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _d_i_s_k___s_t_o_r_e___f_r_e_e + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _d_f _-_k_h _/_s_t_o_r_e _| _t_a_i_l _-_1 _| _a_w_k ’_{ _p_r_i_n_t _1_0_0 _- _$_5 _}’ + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _m_e_m_f_r_e_e + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_p_r_o_c_/_m_e_m_i_n_f_o _| _g_r_e_p _M_e_m_F_r_e_e _| _c_u_t _-_c _1_0_-_2_3 + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _m_e_m_u_s_e_d + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_p_r_o_c_/_m_e_m_i_n_f_o _| _g_r_e_p _A_c_t_i_v_e _| _c_u_t _-_c _8_- _| _c_u_t _-_f _1 _-_d _k + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _p_r_o_c_t_o_t_a_l + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a + _m_o_d_u_l_e___e_x_e_c _p_s _-_A _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _s_s_h_d + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___p_r_o_c + _m_o_d_u_l_e___e_x_e_c _p_s _-_A_f _| _g_r_e_p _s_s_h_d _| _g_r_e_p _-_v _g_r_e_p _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _W_E_B___H_i_t_s + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a___i_n_c _m_o_d_u_l_e___e_x_e_c _c_a_t _/_v_a_r_/_l_o_g_/_a_p_a_c_h_e_/_a_c_c_e_s_s_._l_o_g + _| _g_r_e_p _i_n_d_e_x_._p_h_p _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _e_M_a_i_l_s___p_r_o_c + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a___i_n_c + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_v_a_r_/_l_o_g_/_m_a_i_l_/_m_a_i_l_._l_o_g _| _g_r_e_p _m_e_s_s_a_g_e_-_i_d _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _F_T_P___s_e_s_s_i_o_n_s + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a___i_n_c + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_v_a_r_/_l_o_g_/_s_y_s_l_o_g _| _g_r_e_p _F_T_P _s_e_s_s_i_o_n _o_p_e_n_e_d _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + _m_o_d_u_l_e___b_e_g_i_n + _m_o_d_u_l_e___n_a_m_e _e_M_a_i_l_s___S_P_A_M + _m_o_d_u_l_e___t_y_p_e _g_e_n_e_r_i_c___d_a_t_a___i_n_c + _m_o_d_u_l_e___e_x_e_c _c_a_t _/_v_a_r_/_l_o_g_/_m_a_i_l_/_m_a_i_l_._l_o_g _| _g_r_e_p _i_d_e_n_t_i_f_i_e_d _s_p_a_m _| _w_c _-_l + _m_o_d_u_l_e___e_n_d + + +AAUUTTHHOORR + Pandora Free Monitoring System is made and copyrighted by Sancho Lerena + Pandora is a project initiated and mainly + developed by Sancho Lerena, at present other people is working on it: + Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan + Barajas and Manuel Arostegui We want to thank many other people who + help us with translation, graphic design, bugs reporting and interest- + ing ideas. + + + +SSEEEE AALLSSOO + ppaannddoorraa + ppaannddoorraa__sseerrvveerr + ppaannddoorraa__aaggeennttss + ppaannddoorraa__ccoonnssoollee + + + + + + Pandora(Agents) diff --git a/pandora_doc/fr/man/pandora_console b/pandora_doc/fr/man/pandora_console new file mode 100644 index 0000000000..b36fed97c0 --- /dev/null +++ b/pandora_doc/fr/man/pandora_console @@ -0,0 +1,171 @@ +.TH pandora_console + +.SH NAME + +pandora_console - PandoraFMS web application + +.SH AVAILABILITY + +Linux, AIX, Solaris + +.SH DESCRIPTION + +The Web Console is a web application that allows to see graphical reports, state of every agent, also to +access to the information sent by the agent, to see every monitored parameter and to see its evolution +throughout the time, to form the different nodes, groups and users of the system. It is the part that +interacts with the final user, and that will allows you to administer the system. + +The Web Console is written in PHP and no plug-in, Flash, Java or ActiveX is needed to access the +console, only a browser that supports HTML and CSS (IE5+ or Mozilla 4+). Pandora Web Console can +run in several servers, the only thing you need is to be allow to access Pandora Database, where Pandora +stores all the information. + + +.SH SYPNOSIS +.B Pandora Console and Pandora database +.br + +.I Pandora database install + +Please look at MySQL install and management guide (http://dev.mysql.com/doc) to obtain information +about how to create a MySQL database, how to manage mysql users and give him/her privileges to +read/write in Pandora database. Remember that you must write the password of the root user in MySQL +database to enter mysql command line. This user is not the same of the Operating System. The root +password in MySQL is in blank by default (within almost all distributions), you must changed this +password with the MySQL command mysqladmin. Please be careful with this. +You need a database with name "pandora", you could rename it, but you need to reconfigure in server too. +To create the structure of Pandora database in MySQL Server you have the SQL script "pandoradb.sql". +It creates tables and indexes needed to insert information into Pandora database. +You MUST populate database with SQL script "pandoradb_data.sql", +it inserts data needed to run Web Console and default user (login: admin, pass: pandora) to access Pandora Web Console. +First create a database called "pandora", and set an user to be able to access this database: +.I mysql> create database pandora; +.br +Later, execute the next commands using a user with enough privileges to create tables and indexes for +pandora Database into your MySQL Server: +Designed to be open, modular, multiplattform and easy to customize. + +.I cat pandoradb.sql | mysql -D pandora -u root -p + +.I cat pandoradb_data.sql | mysql -D pandora -u root -p + +You can also use the source command, if you are connected to MySQL, from the MySQL prompt: + +.I mysql> use pandora +.br +.I mysql> source path_to_pandora_dbstruct.sql +.br +.I mysql> source path_to_pandora_dbdata.sql + +This example is valid using root user in MySQL +Now we will create an user "pandora" and will be given to it privileges from the localhost: + +.I mysql> grant all on pandora.* to ’pandora’@’localhost’ identified by ’pandora’; + +Keep in mind that users need access from Pandora WEB Console and from Pandora Server, if your +deployment has many subcomponents in different physical machines, you need to setup a MySQL user +with privileges to access from different locations. + +If you get the error "Warning: mysql_connect() [function.mysql-connect]: client does not support +authentication protocol requested by server; consider upgrading" when authenticating Web Console, you +have to change the way the password is stored into the database: + +.I mysql> set password for ’pandora’@’localhost’ = old_password(’pandora’); + +Please note this user will be used by several pandora subcomponents (Pandora Server, Pandora Web +Console) to access database. + +.B Pandora console install + +Prior to install Pandora console, you need the following dependencies and software needed: + +.I Web server. Apache2 is recommended + +.I PHP 4.3.x, or PHP 5.x. Both has been tested for Pandora 1.2 + +.I PHP Modules for MySQL, GD, session management and SNMP. + +.I JpGraph, it is necesary to generate graphics. It has an open source license, you can download it in +http://www.aditus.nu/jpgraph/ + +To install Pandora Console, simply untar in your HTTP server publishing directory and set perms to +www-data or http user. + +To setup Pandora Console, you only need to modify a file, include/config.php, where the following +variables are included in .php code: +.I $dbname="pandora"; // name of database for pandora) +.br +.I $dbuser="pandora"; // mysql user to access db +.br +.I $dbpassword="pandora"; // Password for mysql user +.br +.I $dbhost="pandora"; // Hostname or IP of mySQL server + +If database is define and was correctly installed, you can now access: + +.I http://host:port/installdir/index.php + +The first time you log there is a default admin user "admin" and password "pandora". It’s worth to say +that YOU MUST CHANGE CREDENTIALS BEFORE LOGIN FIRST TIME, change it or create another +account, give it administrator privileges, and disable this one. + +If you cannot see the pandora console login page, it’s possible that you have problems with PHP instalation. When you +installed the Web, please check that PHP engine its running. Fist try to access to the server IP with a +browser. You must see the Welcome Apache page. + +Remember that alter installing the PHP and the PHP module for Apache you must stop and start the +Server Apache. As an example, Ubuntu with Apache2: + +.I /etc/init.d/apache2 stop + +.I /etc/init.d/apache2 start +To verify the PHP and Apache integration you can create the file test.php with the following lines: + +.I TEST"; +.br +.I phpinfo(); +.br +.I ?> + +Now, copy this file in the Apache HTTPDOC directory. This directory depend of the Operating System +or Linux Distribution, for example in Ubuntu this directory is /var/www and in SUSE is +/srv/www/htdocs), RedHat based distributions uses /var/www/html as well. + +To check this integration, please use your browser to open the following URL: +.I http://IP/test.php + +Where IP is IP Address of your Apache server. If the integration is correct you will see in the browser a +text string with big font: “TEST” and a big table with a lot of info about your PHP installation. +2.3.2.1. Graphic reporting instalation + +For correct graphic generation, you need to enter the full path to a TrueType font installed in your +system. By default a free truetype font is distributed with Pandora Console package, and placed in +./reporting/FreeSans.ttf file. Please check that setup directive $config_fontpath is well +configured. +Pandora 1.2 uses JpGraph for viewing graphics. JpGraph is a different project and has no relationship +with Pandora, so you need to install it. You can find at http://www.aditus.nu/jpgraph/. +Download last version (2.x), and place all .php files from src directory into reporting/jpgraph +Pandora Console directory. + +.SH AUTHOR + +Pandora Free Monitoring System is made and copyrighted by Sancho Lerena +Pandora is a project initiated and mainly developed by Sancho Lerena, at present other people is working +on it: Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel Arostegui We want to +thank many other people who help us with translation, graphic design, bugs reporting and interesting +ideas. +.br + + +.SH SEE ALSO + +.B pandora +.br +.B pandora_server +.br +.B pandora_agents +.br +.B pandora_console + diff --git a/pandora_doc/fr/man/pandora_console.1 b/pandora_doc/fr/man/pandora_console.1 new file mode 100644 index 0000000000..f10a27a994 --- /dev/null +++ b/pandora_doc/fr/man/pandora_console.1 @@ -0,0 +1,184 @@ +pandora_console() pandora_console() + + + +NNAAMMEE + pandora_console - PandoraFMS web application + + +AAVVAAIILLAABBIILLIITTYY + Linux, AIX, Solaris + + +DDEESSCCRRIIPPTTIIOONN + The Web Console is a web application that allows to see graphical + reports, state of every agent, also to access to the information sent + by the agent, to see every monitored parameter and to see its evolution + throughout the time, to form the different nodes, groups and users of + the system. It is the part that interacts with the final user, and that + will allows you to administer the system. + + The Web Console is written in PHP and no plug-in, Flash, Java or + ActiveX is needed to access the console, only a browser that supports + HTML and CSS (IE5+ or Mozilla 4+). Pandora Web Console can run in sev- + eral servers, the only thing you need is to be allow to access Pandora + Database, where Pandora stores all the information. + + + +SSYYPPNNOOSSIISS + PPaannddoorraa CCoonnssoollee aanndd PPaannddoorraa ddaattaabbaassee + + _P_a_n_d_o_r_a _d_a_t_a_b_a_s_e _i_n_s_t_a_l_l + + Please look at MySQL install and management guide + (http://dev.mysql.com/doc) to obtain information about how to create a + MySQL database, how to manage mysql users and give him/her privileges + to read/write in Pandora database. Remember that you must write the + password of the root user in MySQL database to enter mysql command + line. This user is not the same of the Operating System. The root pass- + word in MySQL is in blank by default (within almost all distributions), + you must changed this password with the MySQL command mysqladmin. + Please be careful with this. You need a database with name "pandora", + you could rename it, but you need to reconfigure in server too. To + create the structure of Pandora database in MySQL Server you have the + SQL script "pandoradb.sql". It creates tables and indexes needed to + insert information into Pandora database. You MUST populate database + with SQL script "pandoradb_data.sql", it inserts data needed to run Web + Console and default user (login: admin, pass: pandora) to access Pan- + dora Web Console. First create a database called "pandora", and set an + user to be able to access this database: _m_y_s_q_l_> _c_r_e_a_t_e _d_a_t_a_b_a_s_e _p_a_n_- + _d_o_r_a_; + Later, execute the next commands using a user with enough privileges to + create tables and indexes for pandora Database into your MySQL Server: + Designed to be open, modular, multiplattform and easy to customize. + + _c_a_t _p_a_n_d_o_r_a_d_b_._s_q_l _| _m_y_s_q_l _-_D _p_a_n_d_o_r_a _-_u _r_o_o_t _-_p + + _c_a_t _p_a_n_d_o_r_a_d_b___d_a_t_a_._s_q_l _| _m_y_s_q_l _-_D _p_a_n_d_o_r_a _-_u _r_o_o_t _-_p + + You can also use the source command, if you are connected to MySQL, + from the MySQL prompt: + + _m_y_s_q_l_> _u_s_e _p_a_n_d_o_r_a + _m_y_s_q_l_> _s_o_u_r_c_e _p_a_t_h___t_o___p_a_n_d_o_r_a___d_b_s_t_r_u_c_t_._s_q_l + _m_y_s_q_l_> _s_o_u_r_c_e _p_a_t_h___t_o___p_a_n_d_o_r_a___d_b_d_a_t_a_._s_q_l + + This example is valid using root user in MySQL Now we will create an + user "pandora" and will be given to it privileges from the localhost: + + _m_y_s_q_l_> _g_r_a_n_t _a_l_l _o_n _p_a_n_d_o_r_a_._* _t_o ’_p_a_n_d_o_r_a’_@’_l_o_c_a_l_h_o_s_t’ _i_d_e_n_t_i_f_i_e_d + _b_y ’_p_a_n_d_o_r_a’_; + + Keep in mind that users need access from Pandora WEB Console and from + Pandora Server, if your deployment has many subcomponents in different + physical machines, you need to setup a MySQL user with privileges to + access from different locations. + + If you get the error "Warning: mysql_connect() [function.mysql-con- + nect]: client does not support authentication protocol requested by + server; consider upgrading" when authenticating Web Console, you have + to change the way the password is stored into the database: + + _m_y_s_q_l_> _s_e_t _p_a_s_s_w_o_r_d _f_o_r ’_p_a_n_d_o_r_a ’_@ ’_l_o_c_a_l_h_o_s_t ’ _= _o_l_d___p_a_s_s_w_o_r_d_( + ’_p_a_n_d_o_r_a’_)_; + + Please note this user will be used by several pandora subcomponents + (Pandora Server, Pandora Web Console) to access database. + + PPaannddoorraa ccoonnssoollee iinnssttaallll + + Prior to install Pandora console, you need the following dependencies + and software needed: + + _W_e_b _s_e_r_v_e_r_. _A_p_a_c_h_e_2 _i_s _r_e_c_o_m_m_e_n_d_e_d + + _P_H_P _4_._3_._x_, _o_r _P_H_P _5_._x_. _B_o_t_h _h_a_s _b_e_e_n _t_e_s_t_e_d _f_o_r _P_a_n_d_o_r_a _1_._2 + + _P_H_P _M_o_d_u_l_e_s _f_o_r _M_y_S_Q_L_, _G_D_, _s_e_s_s_i_o_n _m_a_n_a_g_e_m_e_n_t _a_n_d _S_N_M_P_. + + _J_p_G_r_a_p_h_, _i_t _i_s _n_e_c_e_s_a_r_y _t_o _g_e_n_e_r_a_t_e _g_r_a_p_h_i_c_s_. _I_t _h_a_s _a_n _o_p_e_n _s_o_u_r_c_e + _l_i_c_e_n_s_e_, _y_o_u _c_a_n _d_o_w_n_l_o_a_d _i_t _i_n http://www.aditus.nu/jpgraph/ + + To install Pandora Console, simply untar in your HTTP server publishing + directory and set perms to www-data or http user. + + To setup Pandora Console, you only need to modify a file, include/con- + fig.php, where the following variables are included in .php code: + _$_d_b_n_a_m_e_=_"_p_a_n_d_o_r_a_"_; _/_/ _n_a_m_e _o_f _d_a_t_a_b_a_s_e _f_o_r _p_a_n_d_o_r_a_) + _$_d_b_u_s_e_r_=_"_p_a_n_d_o_r_a_"_; _/_/ _m_y_s_q_l _u_s_e_r _t_o _a_c_c_e_s_s _d_b + _$_d_b_p_a_s_s_w_o_r_d_=_"_p_a_n_d_o_r_a_"_; _/_/ _P_a_s_s_w_o_r_d _f_o_r _m_y_s_q_l _u_s_e_r + _$_d_b_h_o_s_t_=_"_p_a_n_d_o_r_a_"_; _/_/ _H_o_s_t_n_a_m_e _o_r _I_P _o_f _m_y_S_Q_L _s_e_r_v_e_r + + If database is define and was correctly installed, you can now access: + + _h_t_t_p_:_/_/_h_o_s_t_:_p_o_r_t_/_i_n_s_t_a_l_l_d_i_r_/_i_n_d_e_x_._p_h_p + + The first time you log there is a default admin user "admin" and pass- + word "pandora". It’s worth to say that YOU MUST CHANGE CREDENTIALS + BEFORE LOGIN FIRST TIME, change it or create another account, give it + administrator privileges, and disable this one. + + If you cannot see the pandora console login page, it’s possible that + you have problems with PHP instalation. When you installed the Web, + please check that PHP engine its running. Fist try to access to the + server IP with a browser. You must see the Welcome Apache page. + + Remember that alter installing the PHP and the PHP module for Apache + you must stop and start the Server Apache. As an example, Ubuntu with + Apache2: + + _/_e_t_c_/_i_n_i_t_._d_/_a_p_a_c_h_e_2 _s_t_o_p + + _/_e_t_c_/_i_n_i_t_._d_/_a_p_a_c_h_e_2 _s_t_a_r_t To verify the PHP and Apache integration you + can create the file test.php with the following lines: + + _<_?_P_H_P + _e_c_h_o _<_h_1_>_T_E_S_T_<_/_h_1_> _; + _p_h_p_i_n_f_o_(_)_; + _?_> + + Now, copy this file in the Apache HTTPDOC directory. This directory + depend of the Operating System or Linux Distribution, for example in + Ubuntu this directory is /var/www and in SUSE is /srv/www/htdocs), Red- + Hat based distributions uses /var/www/html as well. + + To check this integration, please use your browser to open the follow- + ing URL: _h_t_t_p_:_/_/_I_P_/_t_e_s_t_._p_h_p + + Where IP is IP Address of your Apache server. If the integration is + correct you will see in the browser a text string with big font: “TEST + ” and a big table with a lot of info about your PHP installation. + 2.3.2.1. Graphic reporting instalation + + For correct graphic generation, you need to enter the full path to a + TrueType font installed in your system. By default a free truetype font + is distributed with Pandora Console package, and placed in configured. + Pandora 1.2 uses JpGraph for viewing graphics. JpGraph is a different + project and has no relationship with Pandora, so you need to install + it. You can find at http://www.aditus.nu/jpgraph/. Download last ver- + sion (2.x), and place all .php files from src directory into report- + ing/jpgraph Pandora Console directory. + + +AAUUTTHHOORR + Pandora Free Monitoring System is made and copyrighted by Sancho Lerena + Pandora is a project initiated and mainly + developed by Sancho Lerena, at present other people is working on it: + Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan + Barajas and Manuel Arostegui We want to thank many other people who + help us with translation, graphic design, bugs reporting and interest- + ing ideas. + + + +SSEEEE AALLSSOO + ppaannddoorraa + ppaannddoorraa__sseerrvveerr + ppaannddoorraa__aaggeennttss + ppaannddoorraa__ccoonnssoollee + + + + + pandora_console() diff --git a/pandora_doc/fr/man/pandora_server b/pandora_doc/fr/man/pandora_server new file mode 100644 index 0000000000..6b0fc5eefb --- /dev/null +++ b/pandora_doc/fr/man/pandora_server @@ -0,0 +1,154 @@ +.TH Pandora Server + +.SH NAME + +pandora_server - PandoraFMS Server + +.SH AVAILABILITY + +Linux, AIX, Solaris. + +.SH DESCRIPTION + +Pandora FMS 1.2 has three kind of servers: Data server, Network Server and SNMP Server/Trap console. +All of them could be installed in the same machine or in different machines, also, you could setup many +of them in a High Availability environment or using it to manage highs loads of data. + +.SH SYPNOSIS + +.B Pandora Data Server + +To build Pandora Data Server you need to have the following perl modules and software installed in your +machine. This packages could be installed using your distribution packaging system or using CPAN. + + • XML::Simple, useful XML functions +.br + • Digest::MD5, MD5 generation +.br + • Time::Local, Date and Time basic manipulation +.br + • DBI, DB interface with MySQL +.br + • Date::Manip, needed to manipulate Date and Time formats of input, output and compare + +You can find them at http://www.cpan.org or install using your default package instalation system. These +packages are in the default distribution of Suse 9.1 and Debian 3.0 GNU/Linux. Also available for +Solaris in CPAN repository. Next, you need to set the TZ (Time Zone) environment variable. + +.B Pandora Network Server + +Requires SSH Server and Perl v5.8 or higher and the next Perl Modules: + + • IO::Socket, manage and manipulation of TCP/UDP sockets +.br + • Time::HiRes, needed for ICMP times +.br + • Time::Local, Date and Time basic manipulation +.br + • SNMP, for SNMP management +.br + • Date::Manip, needed to manipulate Date and Time formats of input, output and compare +.br + • Net::Ping, to calculate latency times (it’s required that the server runs as root user). + +To use SNMP fuctions it’s needed also to have installed the net-snmp package. It’s worth to say that to run modules of GENERIC_ICMP_DATA type (calculate ICMP latency time) Pandora Network Server must run with root privileges. + +.B Pandora SNMP Server + +You need to install the NET-SNMP package which is included in all GNU/Linux distributions. You have to use the snmptrapd binary and copy or link it to $HOME_PANDORA/util, where $HOME_PANDORA is the instalation directory of Pandora. + +This binary gets the SNMP traps, generating a log that is parsed by the Pandora Server. + +.B Installing Pandora Server + +Create the /opt/pandora directory and "gunzip" and "untar" here the pandora_server_1.2.tar.gz file. + +Create an user pandora in OS. Usually you do that in GNU/Linux with commands: + +.I useraddd pandora -d /home/pandora +.br +.I mkdir /home/pandora +.br +.I chown pandora /home/pandora + +This user will be used by the SSH transfers to the server, so this user will need a strong password. + +In the file /home/pandora/.ssh/authorized_keys we will add the public key of each agent which send data to Pandora Server. These keys must be SSH v2, OpenSSH DiffieHellman (DF) or RSA. To convert between keys you can use the ssh-keygen tool. Pandora Server will check and parse XML fifiles sent by Pandora Agents and will insert the datainto the Database. + +Check launch scripts (pandora_network, pandora_server, pandora_snmp) and check for pathnames in the +first two variables in script. roa Server. This usually is /opt/pandora_server + +.B Configuring your new Pandora Server setup + +After install Pandora Server in, you will need to edit the fifile pandora_server.conf, where are defined +the variables of the server configuration. File pandora_server.conf is a text fifile, you could edit with +your prefer text editor, like emacs. This configuration fifile is common to all kinds of Pandora Server (Data +server, SNMP Server, Network server), you also could have different copies of configuration file for each +Pandora Server you have. +Edit configuration fifile of Pandora Server, usually /opt/pandora/conf/pandora_server.conf and +take a look at the lines: + +.I dbuser pandora +.br +.I dbpass pandora +.br +.I dbhost localhost + +Please change them to your own data. For security reasons isn’t recommended use the default values. +These are default values, and all must be existing directory and filename and valid username, password +and hostname. + +Remember: you need to create the directory /opt/pandora/data_in where Pandora Server will read and +write data, sent by remote agents using ssh/scp. This directory must be owned or with permissions to +write for user "pandora". If you don’t have a "pandora" user yet, create it. + +You can run Pandora Server with an user without privilegues, you can use the user "pandora", it only +needs to run /usr/bin/perl and access to /opt/pandora and /opt/pandora/data_in directories. + +This is true with all the components but with Pandora SNMP Console needs root user to open UDP port +161 (this can be solved setting SUID0 to the snmptrapd binary) and running the rest of the Server using +an user without privileges. + +Also Pandora Network Server can be run using an user without privileges, but the +GENERIC_ICMP_DATA type won’t work, as root privileges are required to get ICMP latency times. +Check the MySQL connection with the user and password before running the server + +Pandora Server distribution tarball includes a Posix/System V start/stop script for "daemonize" Pandora +Server. It is possible that you need to customize, but its runs smoothly on GNU/Linux (debian, Suse) and +Solaris 8 systems. It has start|stop|restart parameters to include it in your default init level directory and it +creates a logfifile defined in $log_fifile variable (by default is /opt/pandora/pandora.log): +.I /etc/init.d/pandora_server start + +.B Setting up SSH configuration + +Pandora, uses SSH protocol to copy XML data packets, generated by the agents, to the server. You need to generate a SSH2 key in every agent, and copy the public key in +/home/pandora/.ssh/authorized_keys, so you need to create a user called "pandora" without +privileges. This user will be used by agents to copy data into Pandora Data Server +/opt/pandora/data_in directory. + +Please BE SURE that user "pandora" exists (if not, create with useradd), and +/home/pandora/.ssh/authorized_keys exists and ownership of this file and directory is for +pandora user, and permissions set to 600. + +Please be sure that directory /opt/pandora/data_in exists and pandora user is able to write in. + +.SH AUTHOR + +Pandora Free Monitoring System is made and copyrighted by Sancho Lerena +Pandora is a project initiated and mainly developed by Sancho Lerena, at present other people is working +on it: Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan Barajas and Manuel Arostegui We want to +thank many other people who help us with translation, graphic design, bugs reporting and interesting +ideas. +.br + + +.SH SEE ALSO + +.B pandora +.br +.B pandora_server +.br +.B pandora_agents +.br +.B pandora_console + diff --git a/pandora_doc/fr/man/pandora_server.1 b/pandora_doc/fr/man/pandora_server.1 new file mode 100644 index 0000000000..f67c83ceda --- /dev/null +++ b/pandora_doc/fr/man/pandora_server.1 @@ -0,0 +1,181 @@ +Pandora(Server) Pandora(Server) + + + +NNAAMMEE + pandora_server - PandoraFMS Server + + +AAVVAAIILLAABBIILLIITTYY + Linux, AIX, Solaris. + + +DDEESSCCRRIIPPTTIIOONN + Pandora FMS 1.2 has three kind of servers: Data server, Network Server + and SNMP Server/Trap console. All of them could be installed in the + same machine or in different machines, also, you could setup many of + them in a High Availability environment or using it to manage highs + loads of data. + + +SSYYPPNNOOSSIISS + PPaannddoorraa DDaattaa SSeerrvveerr + + To build Pandora Data Server you need to have the following perl mod- + ules and software installed in your machine. This packages could be + installed using your distribution packaging system or using CPAN. + + • XML::Simple, useful XML functions + • Digest::MD5, MD5 generation + • Time::Local, Date and Time basic manipulation + • DBI, DB interface with MySQL + • Date::Manip, needed to manipulate Date and Time formats of input, + output and compare + + You can find them at http://www.cpan.org or install using your default + package instalation system. These packages are in the default distribu- + tion of Suse 9.1 and Debian 3.0 GNU/Linux. Also available for Solaris + in CPAN repository. Next, you need to set the TZ (Time Zone) environ- + ment variable. + + PPaannddoorraa NNeettwwoorrkk SSeerrvveerr + + Requires SSH Server and Perl v5.8 or higher and the next Perl Modules: + + • IO::Socket, manage and manipulation of TCP/UDP sockets + • Time::HiRes, needed for ICMP times + • Time::Local, Date and Time basic manipulation + • SNMP, for SNMP management + • Date::Manip, needed to manipulate Date and Time formats of input, + output and compare + • Net::Ping, to calculate latency times (it’s required that the + server runs as root user). + + To use SNMP fuctions it’s needed also to have installed the net-snmp + package. It ’s worth to say that to run modules of GENERIC_ICMP_DATA + type (calculate ICMP latency time) Pandora Network Server must run with + root privileges. + + PPaannddoorraa SSNNMMPP SSeerrvveerr + + You need to install the NET-SNMP package which is included in all + GNU/Linux distributions. You have to use the snmptrapd binary and copy + or link it to $HOME_PANDORA/util, where $HOME_PANDORA is the instala- + tion directory of Pandora. + + This binary gets the SNMP traps, generating a log that is parsed by the + Pandora Server. + + IInnssttaalllliinngg PPaannddoorraa SSeerrvveerr + + Create the /opt/pandora directory and "gunzip" and "untar" here the + pandora_server_1.2.tar.gz file. + + Create an user pandora in OS. Usually you do that in GNU/Linux with + commands: + + _u_s_e_r_a_d_d_d _p_a_n_d_o_r_a _-_d _/_h_o_m_e_/_p_a_n_d_o_r_a + _m_k_d_i_r _/_h_o_m_e_/_p_a_n_d_o_r_a + _c_h_o_w_n _p_a_n_d_o_r_a _/_h_o_m_e_/_p_a_n_d_o_r_a + + This user will be used by the SSH transfers to the server, so this user + will need a strong password. + + In the file /home/pandora/.ssh/authorized_keys we will add the public + key of each agent which send data to Pandora Server. These keys must be + SSH v2, OpenSSH DiffieHellman (DF) or RSA. To convert between keys you + can use the ssh-keygen tool. Pandora Server will check and parse XML + fifiles sent by Pandora Agents and will insert the datainto the + Database. + + Check launch scripts (pandora_network, pandora_server, pandora_snmp) + and check for pathnames in the first two variables in script. roa + Server. This usually is /opt/pandora_server + + CCoonnffiigguurriinngg yyoouurr nneeww PPaannddoorraa SSeerrvveerr sseettuupp + + After install Pandora Server in, you will need to edit the fifile pan- + dora_server.conf, where are defined the variables of the server config- + uration. File pandora_server.conf is a text fifile, you could edit with + your prefer text editor, like emacs. This configuration fifile is com- + mon to all kinds of Pandora Server (Data server, SNMP Server, Network + server), you also could have different copies of configuration file for + each Pandora Server you have. Edit configuration fifile of Pandora + Server, usually /opt/pandora/conf/pandora_server.conf and take a look + at the lines: + + _d_b_u_s_e_r _p_a_n_d_o_r_a + _d_b_p_a_s_s _p_a_n_d_o_r_a + _d_b_h_o_s_t _l_o_c_a_l_h_o_s_t + + Please change them to your own data. For security reasons isn’t recom- + mended use the default values. These are default values, and all must + be existing directory and filename and valid username, password and + hostname. + + Remember: you need to create the directory /opt/pandora/data_in where + Pandora Server will read and write data, sent by remote agents using + ssh/scp. This directory must be owned or with permissions to write for + user "pandora". If you don’t have a "pandora" user yet, create it. + + You can run Pandora Server with an user without privilegues, you can + use the user "pandora", it only needs to run /usr/bin/perl and access + to /opt/pandora and /opt/pandora/data_in directories. + + This is true with all the components but with Pandora SNMP Console + needs root user to open UDP port 161 (this can be solved setting SUID0 + to the snmptrapd binary) and running the rest of the Server using an + user without privileges. + + Also Pandora Network Server can be run using an user without privi- + leges, but the GENERIC_ICMP_DATA type won’t work, as root privileges + are required to get ICMP latency times. Check the MySQL connection + with the user and password before running the server + + Pandora Server distribution tarball includes a Posix/System V + start/stop script for "daemonize" Pandora Server. It is possible that + you need to customize, but its runs smoothly on GNU/Linux (debian, + Suse) and Solaris 8 systems. It has start|stop|restart parameters to + include it in your default init level directory and it creates a log + fifile defined in $log_fifile variable (by default is /opt/pandora/pan- + dora.log): _/_e_t_c_/_i_n_i_t_._d_/_p_a_n_d_o_r_a___s_e_r_v_e_r _s_t_a_r_t + + SSeettttiinngg uupp SSSSHH ccoonnfigguurraattiioonn + + Pandora, uses SSH protocol to copy XML data packets, generated by the + agents, to the server. You need to generate a SSH2 key in every agent, + and copy the public key in /home/pandora/.ssh/authorized_keys, so you + need to create a user called "pandora" without privileges. This user + will be used by agents to copy data into Pandora Data Server /opt/pan- + dora/data_in directory. + + Please BE SURE that user "pandora" exists (if not, create with user- + add), and /home/pandora/.ssh/authorized_keys exists and ownership of + this file and directory is for pandora user, and permissions set to + 600. + + Please be sure that directory /opt/pandora/data_in exists and pandora + user is able to write in. + + +AAUUTTHHOORR + Pandora Free Monitoring System is made and copyrighted by Sancho Lerena + Pandora is a project initiated and mainly + developed by Sancho Lerena, at present other people is working on it: + Raul Mateos, David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan + Barajas and Manuel Arostegui We want to thank many other people who + help us with translation, graphic design, bugs reporting and interest- + ing ideas. + + + +SSEEEE AALLSSOO + ppaannddoorraa + ppaannddoorraa__sseerrvveerr + ppaannddoorraa__aaggeennttss + ppaannddoorraa__ccoonnssoollee + + + + + Pandora(Server) diff --git a/pandora_doc/fr/pandora.xml b/pandora_doc/fr/pandora.xml new file mode 100644 index 0000000000..005a2c25cb --- /dev/null +++ b/pandora_doc/fr/pandora.xml @@ -0,0 +1,86 @@ + + +Pandora FMS"> + + + + + + +]> + + + + &pandora; &pandora_version; + Installation Manual + + + 2006 + + Artica Soluciones Tecnologicas S.L, Sancho Lerena, Esteban + Sanchez, David Villanueva, Raul Mateos, Manuel Arostegui and others. + + + 19/11/2006 + &pandora_version; + First Edition(&pandora_version;) + + November 19th, 2006 + + pandora user manual + + + + Permission is granted to copy, distribute and/or modify this + document under the terms of the GNU Free Documentation + License, Version 1.1 or any later version published by the + Free Software Foundation. A copy of the license is included + in the section entitled GNU Free Documentation + License. + + + + + 1.0 + 11 Sept 2006 + Submitted. + + + + 1.1 + 20 Sept 2006 + First draft for review. + + + + 1.2 + 21 Nov 2006 + Last review. + + + + 1.3 + 3 Dec 2006 + Very last review. + + + + 1.3 + 19 Jan 2007 + French Translation. + + + + + + &include_pandora_introduction; + &include_pandora_install; + &include_pandora_migration; + &include_pandora_advanced; + &include_fdl; + &include_gpl; + + diff --git a/pandora_doc/fr/pandora_advanced.xml b/pandora_doc/fr/pandora_advanced.xml new file mode 100644 index 0000000000..4878681d83 --- /dev/null +++ b/pandora_doc/fr/pandora_advanced.xml @@ -0,0 +1,167 @@ + + + Section Pandora FMS avancé + Fonctionnalités Haute Disponibilité (HD) de Pandora FMS + + Vous pouvez paramétrer Pandora pour l'utiliser dans divers scénarii HD: + + + + Cluster de bases de données pour HD. Vous avez besoin de + configurer un cluster MySQL5. Il y a des informations pour mettre cela en oeuvre + dans les forums/wikis de support, vous devez seulement convertir le schéma de la DB + vers des tables compatibles avec un cluster MySQL. Ce scénario a été testé + et fonctionne bien, mais il nécessite d'avoir des connaissances avancées + sur l'administration de clusters MySQL. + + + + + Consoles Pandora Multiples. Très facilement, + paramétrez simplement une autre console. Aucun problème de verrouillage ou + d'incompatibilité n'a été détecté au cours de multiples déploiements. + + + + + Serveurs de données Pandora Multiples Pandora pour la HA + . C'est le scénario le plus complexe, car si vous n'avez + pas besoin de connaître en détail le paramétrage de Pandora Server, + vous aurez besoin d'utiliser d'autres outils pour implémenter la HD + réseau, comme VRRP or Keepalive. Pour le serveur de données Pandora + vous aurez besoin de 2 machines identiques, avec les même clefs publiques + pour tous les agents qui se connectent au serveur (et de dupliquer + la clef hôte du serveur SSH). Puis paramétrer la HD sur le réseau pour + pointer sur l'un d'entre eux. Si l'un d'entre eux vient à faillir, VRRP + ou Keepalive "promeu" l'autre serveur, ainsi les agents Pandora, s'y connecteront + pour envoyer leur prochain paquet de données. Il n'y a rien à changes dans + les serveurs de données Pandora, assurez-vous seulement que le nom des deux + seveurs de données Pandora est le même sur ces deux machines (dans le programme + pandora serveur, pas le nom d'hôte de la machine). + + + + + Serveurs Pandora Network multiples pour HD + . Cela est plus aisé. Vous aurez besoin de paramétrer + plusieurs Pandora Network Servers sur plusieurs machines du réseau + (ou toutes celles dans un même sgment), et assignez-les au + même serveur. Si ce serveur s'arrête, et qu'il y a d'autres + Network Servers actifs, marqués comme serveurs "primaires", + automatiquement, le premier Network Server disponible marqué comme + "primaire", lancera l'interrogation du module réseau. Si vous avez + plusieurs serveurs marqués comme primaire, tous peuvent lancer + des requêtes. + + + + + Pandora Network Server multiples pour la balance de + charge. Vous aurez besoin de paramétrer plusieurs + Pandora Network Servers sur plusieurs machines du réseau + (ou toutes celles dans un même sgment), et assigner les + agents/modules à differents servers, equilibrant la charge entre + tous les serveurs disponibles. + + + + + + Serveurs virtuels Pandora + + Une cas particulier pour obtenir plus de puissance de calcul dans + les serveurs, pourrait d'être d'implémenter des serveurs "virtuels". + Utiliser des serveurs virtuels (une autre instance du même serveur + dans la même machine) est utilisé quand le serveur Pandora ne peut + traiter toutes les informations sans délais trop important. + Pandora 1.2 utilise un nombre limité de therads pour traiter l'information + (cela changera dans les versions futures), vous pouvez donc installer + d'autres instances de Pandora Network ou Pandora Data Server (avec + un autre répertoire data_in !), pour pouvoir traiter plus d'informations + avec la même machine. + + + + Conception de la base de données de Pandora (et modification depuis la 1.1) + + Les premières versions de Pandora, depuis la 0.83 jusqu'à la 1.1 étaient basées + sur une idée simple: une donnée, une insertion en base. Cela était très facile à + développer et autorisait l'implémentation facile des recherches, insertions et autres + operations. + + + Cela eut beaucoup d'avantages mais aussi un sérieux problème: + la capacité à monter en charge. La limite de ce système est + définie par le nombre maximal de modules qu'il peut supporter. + Passé cette limite, la gestion sera trop lente. + + + Les solutions basées sur un cluster MySQL sont difficiles à mettre + en oeuvre et ont posent des problème, de plus, elles n'offrent pas + de solution viable sur le long terme. + + + La compression de données basée sur l'interpolation et la purge de données + génère une base de données plus petite. Cela n'est aps suffisant: + Les systèmes de production ont une limite de 100 agents comprenant + chacun 10 modules. Ce qui n'est pas beaucoup pour les gros réseaux. + + + Ce problème était très important pour le futur de Pandora FMS, la façon + dont Pandora gérait ses données fut donc modifiée. Le nouveau système + de gestion des données stocke les donnée uniquement si la nouvelle valeur + est différente de la précédente. Ce système évite de stocker des données + redondantes. Cela permet de garder une base de données de petite taille. + Cette logique vaut pour tous les types de modules Pandora (texte, numérique, + incrémental et booléen). + + + Cela résout une partie de la problèmatique de la montée en charge + en réduisant considérablement l'utilisation de la base de données, + dans des propprtions de l'ordre de 40 à 70%. Une autre solution au + problème de montée en charge serait: séparer totalement les composants + Pandora et une implémentation intégrée de la Haute Disponibilité dans + les composants Pandora. Autorisant alors plusieurs serveurs Pandora + (réseau, données, SNMP), consoles Pandora, bases de données Pandora + (dans un cluster MySQL5). + + + Ces changements s'accompagnent d'une façon différente de lire les données. + Dans la nouvelle version, si un agent ne peut communiquer avec le serveur + Pandora, et le serveur Pandora ne reçoit pas de données de cet agent, cette + absence de données sera représentée par une ligne horizontale prolongeant + la dernière valeur reçue, matérialisant l'absence de changement depuis lors. + Pandora, représentera donc cette absence de nouvelle valeur comme une absence de + changement depuis le dernier contact. + + + Ce graph, par exemple représente les changements pour chaque donnée reçue toutes + les 180 secondes. + + + + Ci-dessous, le même graph avec une perte de connection de 05:55 à 15:29 approximativement. + + + + + Il a été introduit dans Pandora 1.2, un nouveau graph représentant la connectivité + des agents vers le serveur Pandora. Ce graphe vient donc compléter les autres en + indiquant quand les agents parviennent à envoyer des données au serveur Pandora. + Voici un exemple de ce graph montrant le contact régulier d'un agent à son serveur: + + Si ce graph montre des "trous", cela peut révéler des problèmes, ou être dû à une + connexion lente lorsqu'un agent Pandora contacte le serveur Pandora. + Le graphe suivant reprend le graphe ci-dessus, en montrant ce phénomène: + + + + Le guide du programmeur sur l'architechture Pandora + + + + + + + + diff --git a/pandora_doc/fr/pandora_chapter1.xml b/pandora_doc/fr/pandora_chapter1.xml new file mode 100644 index 0000000000..dc519fab73 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter1.xml @@ -0,0 +1,134 @@ + + + + Introduction + + Qu'est-ce que Pandora FMS? + + + Pandora FMS est un outil de monitoring permettant à un administrateur + système d'analyser de manière graphique l'efficacité et l'état de Sytémes + d'exploitation, serveurs, applications et matériel - comme les pare-feu, + proxies, bases de données, serveurs web, serveurs de tunels, routeurs, + commutateurs ethernet, processus, services, serveurs à accès distant, et + plus encore. Le tout intégré au sein d'une architecture ouverte et + distribuée. + + + Pandora peut fonctionner sur n'importe quel système d'exploitation, grâce + à des agents spécifiques à chaque plateforme. Pandora peut aussi surveiller + n'importe quel matériel TCP/IP, comme les balances de charge, les routeurs, + commutateurs ethernet, imprimantes etc.. + + + + L'architecture de Pandora comprend quatre composants principaux: + + + - Console Web: L'interface utilisateur de Pandora. + C'est au travers celle-ci que l'utilisateur contrôle et pilote le système. + Plusieurs consoles web peuvent être paramétrées sur un même système. + La console web est écrite en PHP, et fonctionne au-dessus d'une base de données + et d'un serveur web. Cette interface web est compatible avec tous les systèmes + d'exploitation - GNU/Linux, Solaris, Win2000, AIX, etc. - même si la plateforme + officielle supportée est GNU/Linux. + + + + La console permet à l'utilisateur de contrôler le status des agents, + consulter des statistiques, générer des graphiques et des tableaux de + données, garder un système de contrôle des incidents, de plus, il peut + générer des rapports, changer les alertes, et les paramètres de profil + d'utilisateur. + + + + - Le noyau Serveur: Le noyau Serveur Pandora + est le récepteur des paquets de données, et gère les alertes + (c'est le cerveau du système). Plusieurs serveurs peuvent fonctionner + de concert pour les gros systèmes. Ce serveur est écrit en PERL et + fonctionne sur toute plateforme, même si la plateforme officielle + supportée est GNU/Linux. + + + + Le noyau Serveur accède à la base de données Pandorapartagée + avec le serveur Web, pour y stocker les données traitées issues + des paquets de données. Le serveur est exécuté comme un "démon", et + traite les paquets de données reçues dans son réterpoire de travail. + Ces paquets de données sont générées par les agents Pandora. + Malgré son fonctionnement et installation simples et sa basse + consommation en ressources, le noyau Serveur est l'élément le plus + critique du système. Ce noyau reçoit et traite les données, + il déclenche aussi les alarmes et les évènements. + + + + - Base de données centrale: Pour le moment, + le système supporte seulement MySQL. La base de données centrale + garde toutes les informations dont Pandora a besoin pour son + fonctionnement (les données de agents, la configuration, les + informations utilisateurs, les incidents, les paramètres systèmes, + etc. Le système peut utiliser un cluster MySQL pour stocker l'information, + ou une solution de Haute Disponibilité pour les plus gros systèmes. + + + + Cette base de données peut fonctionner sur n'importe quel + système d'exploitation supporté par MySQL. Pandora peut + fonctionner avec les versions 3.0 et 4.0 de MySQL, la + dernière est cependant recommandée. + + + + - Agents Pandora: Ils collectent les données + du système monitoré. Ils sont exécutés en local, et peuvent + collecter des données à distance (SNMP). + + + + Ils ont été développés pour fonctionner sur des plateformes spécifiques, + utilisant les outils spécifiques à chaque langage utilisé: + VBSCript/Windows Scripting pour les plateformes Microsoft (Win2000, + WinXP et Win2003) et scripts shell pour Unix - ce qui inclut + GNU/Linux, Solaris, AIX, HP-UX et BSD, et aussi Nokia IPSO. + Les agents Pandora peuvent être développés dans virtuellement + n'importe quel langage, grâce à son API très simple et son caractère Open Source. + + + + Administration Pandora + + La console web est l'outil utilisé pour administrer + Pandora. Elle est écrite en PHP et ne nécessite aucun + logiciel tierce: ni FLASH, ni JAVA, ni ActieX. + La console web peut fonctionner sur n'importe quel + navigateur web supportant HTML et CSS (IE5+ ou Mozilla 4+). + + + + L'administration Pandora est divisée en éléments principaux + comme suit: + + + + Utilisateurs Pandora + + + Agents + + + Alertes + + + Incidents + + + Configuration du serveur + + + Maintenance de la base de données + + + + diff --git a/pandora_doc/fr/pandora_chapter2.xml b/pandora_doc/fr/pandora_chapter2.xml new file mode 100644 index 0000000000..61e101de34 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter2.xml @@ -0,0 +1,168 @@ + + + Utilisateurs + + Un utilisateur est basé sur son activité quotidienne. Chaque utilisateur + se voit attribué un profil d'autorisation d'accès avec une liste d'actions + autorisée/interdites associées. Un ou plusieurs profils peuvent être associés + à un même utilisateur. + + + + Chaque utilisateur se voit attribuer un groupe d'agents auxquels il peut + accéder en complément du profil administratif qu'il aura dans chaque groupe. + Chaque utilisateur peut appartenir à un ou plusieurs groupes, avec pour chaque + groupe un profil assigné. + + + + Un agent ne peut appartenir qu'à un seul et unique groupe, le partageant + avec le autres agents de même caractéristiques. Les groupes contiennent aussi + les incidents. + + + + Résumé: Les profils utilisateur dans Pandora définissent quels utilisateurs + peuvent accéder à Pandora et ce que chacun d'entre eux peut faire. + Les groupes définnissent les éléments en commun parmi les différents utilisateurs. + Chaque utilisateur peut se trouver dans un ou plusieurs groupes à la fois. + A chaque groupe est attaché des profils utilisateur définis. + Un profil est une liste d'actions que l'utilisateur est autorisé à exécuter, + comme consulter les incidents, gérer la base de données et autre. + + + + Gestion des profils + + Le gestionnaire de profils Pandora est utilisé pour assigner des profils + à chaque utilisateur. Une hiérarchie d'utilisateurs est créée, structurée + par les profils utilisateurs au sein de l'entreprise. Grâce à ce système, + différents niveaux de sécurité peuvent être définis: + utilisateurs en lecture seulement, coordinateur de groupe d'agents, ou + administrateurs système. + + + + Un profil est créé depuis l'outil de gestion de profils dans le menu d'administration + Il y a 5 profils prédéfinis: + + + + + Operator (lecture) + + + Operator (écriture) + + + Chief Operator + + + Group coordinator + + + Pandora Administrator + + + + Pour créer un nouveau profil, cliquez sur "Gestion de Profils" > + "Créer un profil" dans le menu Administration + + + + Nimporte lequel des rôles suivants peuvent être assignés à un nouveau profil: + + + + View incidents (IR) + + + Edit incidents (IW) + + + Manage incidents (IM) + + + + View agents (AR). Pour consulter les agents comme les évènements qu'ils génèrent + + + + Edit agents (AW). Pour modifier les modules des agents + + + Edit alerts (LW). Pour modifier les alertes assignées à un agent + + + Manage users (UM). Pour modifier les utilisateurs et leurs rôles + + + + Manage DB (DM). Pour modifier la configuration et les données de la base de donnée (Global) + + + + Manage alerts (LM). Pour définir de nouvelles alertes (Global) + + + Manage Pandora (PM). Pour modifier le paramètres généraux du système + + + + + + Ajout d'un utilisateur + + + Un utilisateur est ajouté en cliquant sur "Gestion d'usagers" > "Créer un usager" + dans le menu Administration + + + + + Pour créer un nouvel utilisateur, il est nécessaire de renseigner au moins l'ID + de l'utilisateur, son mot de passe (deux fois) et le profil Pandora global. + + + + Supprimer un utilisateur + + + Un utilisateur est supprimé en cliquant sur l'icône suppression sur le côté droit de l'utilisateur. La liste des utilisateurs + est accessible par la "Gestion d'usagers" dans le menu administration. + + + + + Statistiques + + Les statistiques concernant l'activité des utilisateurs montrent un graphique + avec l'activité des utilisateurs qui est une représentation des évènements que + l'audit a généré pour chaque utilisateur. Le nombre d'évènements générés par + un utilisateur reflète habituellement son activité. + + + Cliquez sur "Voir usagers" > "Statistiques" dans le menu Opération pour + afficher ce graphique: + + + + + Messages aux usagers + + Dans Pandora 1.2, il a été ajouté la possibilité d'envoyer des messages + aux autres utilisateurs. Pour créer un nouveau message, allez dans la section + "Messages" dans le menu Opération. Vous pouvez aussi lire les messages reçus, + mais les messages envoyés ne sont pas stockés dans votre espace. + + + Messages aux groupes + + Depuis la section "Messages" > "Messages aux groupes" du menu Opération, + vous pouvez envoyer des messages aux groupes d'utilisateurs. Les messages + envoyés ne sont pas stockés dans votre espace. + + + + diff --git a/pandora_doc/fr/pandora_chapter3.xml b/pandora_doc/fr/pandora_chapter3.xml new file mode 100644 index 0000000000..5c1b2dd660 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter3.xml @@ -0,0 +1,1254 @@ + + + + + Les Agents + + + Les agents collectent les informations. Il existe des agents basés sur + un agent logiciel et installés sur le système à surveiller, ainsi que des + agents réseau (network agents), un agent virtuel, sans installation aucune + de logiciel, qui exécute des tâches réseau sur les "Pandora Network servers" + et affichent des informations sur la console. + + + Pour les agent qui nécessitent une installation logicielle sur le système distant, + une copie de la clef publique de la machine (distante) à surveiller doit être présente + sur le serveur de données Pandora afin de collecter les données, comme il est spécifié + en détails dans le Guide d'Installation de Pandora. + + + Les données collectées par les agents sont organisées et stockées par petites + parties appelés "modules". Chaque module stocke un seul type de données. La valeur + prise par un module correspond à la valeur de la variable surveillée. L'agent doit être + activé dans le serveur Pandora et un groupe assigné à l'agent. Les données commencent + alors à être enregistrées et consolidées dans le base et sont accessibles. + + + Un agent réseau DOIT être assigné à un serveur réseau (Network Server) pour exécuter des + des tâches réseau. Si aucun "Network Server" n'est visible, c'est qu'aucun Network Server + n'est lancé. Il vous faut configurer et lancer un serveur réseau avant d'essayer d'assigner + un module réseau à un Agent. + + + Avec la console Pandora, un utilisateur peut: + + + + Voir l'état de l'agent + + + Accéder aux données collectées + + + Accéder aux valeurs surveillées et à leur évolution dans le temps + + + Afficher des rapports graphiques + + + Configurer des Alertes + + + + Configurer les modules. Définir les valeurs maximum et minimum valides + pour chaque module, paramétrer une description compréhensive, ou même + changer le nom du module (notez que le nom du module doit être le même + dans la console que dans la configuration de l'agent). + + + + + Exporter un tables de données en format CSV. + + + + + + Gestionnaire de groupes + + + Les groupes Pandora sont communs aux agents, incidents et profiles. + Les groupes sont ajoués dans "Géstion d'Agents" > "Gestion de groupes" + dans le menu Administration. + + + + + + Il y a plusieurs groupes par défaut définis dans Pandora. Vous pouvez aussi + créer vos propres groupes (utilisez les différentes icônes fournies, ou éditez + et créez les vôtres). Vous pouvez aussi modifier les icônes fournies. + + + + Un groupe est ajouté en cliquant sur "Créer groupe" et lui assignant un nom. + + + Un groupe est supprimé en cliquant sur l'icône de suppression + + dans la partie droite de chaque groupe. + + + + Ajouter un agent + + You can define new agents. Once defined in Pandora console, it is + ready to receive data from a Software agent (old agents, based + on software installed in a remote machine), or from Network + Agents (assined to a Network Server who runs network tasks to + monitor remote systems). You can also mix both types of module + in the same agent. + + + Please remember that a network agent NEEDs to be assigned to a + Network Server to execute network tasks. If you can't see any + Network Servers it's because you don't have any Network Server + running. Please configure and run a Network Server before trying + to assign a network module to an Agent. + + + An agent is added in "Manage Agents" > "Create agent" in the + Administration menu. + + + + + + To add a new agent the following parameters must be configured: + + + + + + Agent Name: Name of the agent. This and + the "agent name" parameter in Pandora's agent.conf file + must have the same value. By default + agent takes hostname of the machine where it's running. + + + + + IP Address: IP address of an agent. An + agent can share its IP address with other agents. It's only + used for informational purposes. In network agents it's useful, + because the Server uses this IP address for all new + network module definition by default. + + + + + Group: Pandora's group the agent + belongs to. In this version of Pandora, an agent only can + belong to a group. + + + + + Interval: Execution interval of an + agent. It is the time elapsed in seconds between two + consecutive agent executions. An agent could have a + defined interval, but could have modules with different + (bigger or smaller) intervals. An agent is considered + "down" (not responding) when Pandora servers (any of them) + has no contact with agent in Interval x 2 seconds. + + + + + OS: The Operating System to be + monitored. The supported Operating Systems are: AIX, BeOS, + BSD, Cisco, HP-UX, Linux, MacOS, Other, Solaris, Windows. + + + + + Description: Brief description of an agent. + + + + + Module definition: There are two state + for a module: + + + + + Learning mode: All the modules sent + by the agent are accepted. If modules are not defined, they + will be automatically defined by the system. It is recommended + to activate the agents in this mode and change it once the + user is familiar with Pandora FMS. + + + + + Normal mode: The modules in this mode + must be configured manually. The self definition of the + modules is not allowed in this mode. + + + + + Disabled: This parameter shows if the + agent is activated and ready to send data or + deactivated. The deactivated agents don't appear in the user + views. + + + + + Assigning modules + + Pandora's agents use the operating system own commands to + monitor a device. Pandora's server will store and process the + output generated by those commands. The commands are called + "modules". + + If the agent had been added in "normal mode", the modules + to be monitored should have been assigned. Those modules must be + configured in the agent configuration file. + + The modules to be processed by Pandora Server are + assigned in the "Manage Agents" option, Administration menu. A + list with all the agents in Pandora will be shown here. + + You'll get a form with all the agent's settings when the + agent name is clicked. In the same screen there is a section to + assign modules. + + + + + To add a module is necessary to fill some of the following fields: + + + Module type: type of module,there are the + following types of modules: + + + + + generic_data: numeric data type. + + + + + generic_data_inc: incremental + numerical data type. It stores data resulting from + difference between last agent data and actual data. + + + + + generic_data_proc: Boolean data type: + 0 means False or "bad values", and 1 means True or "good" + value. Generic Proc types are also called "monitors" + because could say if something is "ok" or is "wrong". They + Are displayed in agent view as little lamps. Red if 0, Green + if 1. + + + + + generic_data_string: Alphanumeric data + type (text string, max. 255 characters). + + + + + + generic_icmp: get network latency in + miliseconds for remote system. + + + + + + generic_icmp_proc: makes a "ping" to + remote system. Report 0 if system is not reachable or not + responding. + + + + + + generic_tcp_proc: makes a "tcp" ping + to remote systems and reports "1" if a listing port is + responding. Optionally, you may pass parameters in "TCP + SEND" (you can use the macro ^M to send carriage returns) + and wait to receive string defined in "TCP RECEIVE". If + Pandora Network Server received TCP RECEIVE string, it + returns 1 (ok), else returns 0 (wrong). + + + + + + generic_tcp_data: generic_tcp_string, + generic_tcp_inc, gets numerical data, string + data or incremental data from TCP open port. If it cannot + connect, no value returned. + + + + + generic_snmp types:: they get + information using SNMP interface. If you enter SNMP + community and IP address, you can walk SNMP MIB from + target using SNMP v1 protocol, and all MIB variables will + be listed to allow you choose one. You can also enter MIB + using numerical OID or human - understandable format. + + + + + generic_ucp_proc: makes a "udp" ping + to remote systems and reports "1" if a listing port is + responding and 0 if are not responding. + + + + + Module Group: It is possible to group + modules in the following groups: General, Networking, + Application, System and Misscellaneous: + + + Module Name: Name of the module. + + + Module Interval: Interval of time in seconds + that the agent waits between two consecutive executions. + + + Target IP: IP of the agent. + + + TCP port: TCP port to monitor, it is possible + to configure UDP port if the module type generic_udp_proc is chosen. + + + SNMP OID: SNMP OID to monitor. If you + configure the MIBs in pandora is possible to get the value. + + + SNMP Community: Community necessary to monitor + a SNMP OID. + + + TCP send: Parameters to send to TCP port. + + + TCP receive: Field to configure the + parameters which we expect to receive in a TCP connection. + + + Maximum:: Upper threshold for the + value in the module. Any value above this threshold will + be taken as invalid and the whole module will be + discarded. + + + Minimum:: Lower threshold for the + value in the module. Any value below this threshold will + be taken as invalid and the whole module will be + discarded. + + + Comments:: Comments added to the + module. + + + All the modules to be monitored by an agent can be reviewed + by accessing the agent in the "Manage Agents" option, + Administration menu. + + + + + + In this screen the modules can be: + + + + + Deleted by clicking + + + + + Edited by clicking + + + + + + However, the type of data of the module can't be modified. + + + + Alerts + + + An alert is Pandora's reaction to an "out of range" module + value. The Alert can consist of sending an e-mail or SMS to + the administrator, sending a SNMP trap, write the incident + into the system syslog or Pandora log file, etc. Basically, + anything that can be triggered by a script configured + in the Operating System where Pandora Servers run. + + + Adding an Alert + + + The existing Alerts are accessed by clicking on the "Manage + Alerts" option, Administration menu. + + There are 6 default types of Alerts: + + + + + eMail. Sends an e-mail from Pandora's Server + + + + + Internal audit. Writes the incident + in Pandora's internal audit system, that is stored in Pandora SQL database. + + + + LogFile.Writes the incident in the log + file. Use this in combination with a customized LogFile alert to generate + logfiles using the format you want. + + + + SMS Text. Sends an SMS to a + given mobile phone, of course, you need to define a alert before to make this possible + and a email/Sms gateway configured and accesible from pandora server. + + + + + SNMP Trap. Sends a SNMP Trap. + + + + Syslog. Sends an alert to the Syslog + + + + + + + + An Alert is deleted by clicking on the delete icon + + placed on the right hand side of the Alert. + A new customised Alert can be created clicking in "Create + Alert". + + + The values "_field1_", "_field2_" and "_field3_" + in the customised Alerts are used to build the command + line that the machine where Pandora resides will execute + - if there were several servers, the one in Master mode. + + + + + + When a new Alert is created the following field must be + filled in: + + + + Alert name: The name of the Alert + + + + + Command: Command the Alert will + trigger + + + + Description: Description of the + Alert + + + + + + In 'Command' data field these variables are used to build + the command line that the machine where Pandora resides will + execute - if there were several servers, the one in Master + mode, replacing at runtime: + + + + + _field1_: + Field #1, usually assigned as username, + e-mail destination or single identification for this event + + + + _field2_: + Field #2, usually assigned as short + description of events, as subject line in e-mail + + + + _field3_: + Field #3, a full text explanation + for the event + + + >_agent_: Agent name + + + _timestamp_: + A standard representation of date and time. + Replaced automatically when the event has been fired + + + + _data_: The data value that + triggered the alert + + + + + + Assigning Alerts + + + The next step after an agent has been added, its + modules have been configurated and the alerts have been + defined, is assign those alerts to the agent. + + + + This is done by clicking on the agent to be configured in the + "Manage Agents" option, Administration menu. + The Alert association form is placed at the bottom of that + page. + + + + + + To assign an alert the next fields must be filled in: + + + + + + Alert type: This can be selected from + the list of alerts that have been previously generated. + + + + + Maximum Value: Defines the maximum + value for a module. Any value above that threshold will + trigger the Alert. + + + + + Minimum Value: Defines the minimum + value for a module. Any value below that will trigger the + Alert. Both maximum and minimum values define "the acceptable" values + that Pandora FMS consider "valid", outside this values, Pandora will consider as + alert candidate. + + + + + Description: Describes the function of + the Alert, and it is useful to identify the Alert amongst + the others in the Alert General View. + + + + + Field #1 (Alias, name): Define the + used value for the "_field1_" variable. + + + + + Field #2 (Single Line): Define the + used value for the "_field2_" variable. + + + + + Field #3 (Full Text): Define the used + value for the "_field3_" variable. + + + + + Time threshold: Minimum duration + between the firing of two consecutive alerts, in seconds. + You can choose between the interval configured or to define + other interval. + + + + + Min number of alerts: Minimum number + of alerts that can be sent consecutively. + + + + + Max number of alerts: Maximum number + of alerts that can be sent consecutively. If you set it to 0 no alerts + will be send. + + + + + Assigned module: + Module to be motitorized by the alert. + + + + + All the alerts of an agent can be seen through "Manage Agents" + in the Adminitration menu and selecting the agent. + You need to use TimeThreshold in cooperation with max. number of alerts. Let's see an example: + + "I want to fire an alert when XXX goes down, and please, dont't disturb me again at least for one hour, then, if this thing continue to be down, fire another alert and wait another hour". + + + You need to setup: Time threshold 3600 (1 Hour), Min. number of alerts = 1, Max. number of alerts = 1 + + + + + Agent module and agent's alert management + It might happen that the user finds that modules and alerts + configured for an agent would be repeated in a new agent. + + In order to simplify the administrator's work Pandora offers + the option of copying modules and alerts defined in an agent to + be assigned to another. + + The screen is accessed through "Manage Agents" > + "Manage Config.", in the Administration menu: + + + + Source Agent menu permits the selection of the agent where the + needed modules and/or alerts reside. The "Get Info" button + shows the modules for that agent in the Modules list box. + + + Copy process is performed to copy the + module and/or alert configuration from the selected source + agents to the selected destination agents. Several agents can + be selected, pressing CTRL and the mouse right button + simultaneously. The two tick boxes at the top of the form + will be used to specify if the configuration to copy is from + modules and/or from alerts. + + + Deletion process is performed to delete + the configuration of the destination agents, in the multiple + selection list box. Several agents can be selected at a time, + and the tick boxes at the top of the form indicate whether it + is the modules or the alerts configuration what is to be + deleted. The application will prompt to confirm the deletion, + as once deletion is performed, the data associated to them + will also be deleted. + + + + Agents group detail + + Once you have configured your groups and agents, you can see + the status of the groups of agents through "View Agents", in + the Operation Menu. + + + If you pass the mouse over any group image, you'll see the + number of agents of that group as well the number of monitors, + organized by status. + + + + By pressing the icon + + at the right of any group image, you will update the info of + that group. + + + + + Agent monitoring + + When the agents begin to send data to the server, and + it is added in the Web console, Pandora processes and inserts + the data in the Database. The data are consolidated and can be + accessed from the Web console, either as row data or as + graphs. + + + Agent view + + All the Agents can be accessed from the Operation menu. + + + You can view the agents in group by clicking "View agents". + From here the status of the agents can be quickly reviewed + thanks to a simple system coloured circles and bulbs that + appear when the user pass the mouse on a group. + + + + To view all the Agents of the group just click in the icon of the group. + + + + The list of agents shows all the relevant the information + in the following columns: + + + Agent: Shows the agent's name. + + SO: Displays an icon that represents the + Operating System. + + + Interval: Shows the time interval (seconds) + in which the agent sends data to the server. + + + Group: This is the group the agent belongs + to. + + + Modules: Under normal circumstances this + field shows the values representing the number of modules and + the number of monitors, both in black. If the status of a + monitor changes to "incorrect", one additional number is + shown: the number of modules, the number of monitors and the + number of monitors with "incorrect" status, all in black save + the last one. + + + Status: Shows the "general" status of the + agent through the following icons: + + + + All the monitors are OK. It's the ideal status. + + + + No defined monitors. Sometimes nothing is monitored + that could be right or wrong, and only numeric or + text data is reported. + + + + At least one of the monitors is failing. Usually we + want to avoid this, and keep our systems in a healthy + green colour. + + + The + agent doesn't have any data. New agents with an empty data + package can have this status. + + + + Colour shifting from green to red. This icon indicates that + the agent has just changed its status, from 'All OK' to'we have + a problem'. + + + When an + agent is down or there is no news from it for 2 times the + Interval value in seconds. Usually it is due to a communication + issue or a crashed remote system. + + + Alerts: Shows if any alerts have been sent + through the following icons: + + + + No alerts have been sent. + + + + Shown when at least one alert has been sent within + the time threshold of the alert. + + + Last contact: Shows date and time of + the last data package sent by the agent, using a progress bar, + according to value of the interval. If you see the image + , + the agent has not send data during the interval. + Passing the mouse over the image will show you the last contact + in date and time format. + + + Note: The icon is only visible if you're + and administrator and it's a link to the "Manage Agents" > + "Update Agent" option in the Administration menu. + + + + Accessing the data of an agent + + When an agent is accessed, by clicking on its name, all the + information related to that agent is displayed. + + + Agent general info + + This shows the data introduced when the agent was created and + the total number a data packages the agent has sent. + + + + + Last data received + + + This is the description of all the agent modules been + monitored. + + + + In this list the module information is showed in the following + columns: + + + + Module name: Name given to the module in + the agent's config file. + + + Module type: Type of module as described + in Asigning Modules section. + + + Description: Description given to the + module in the agent's config file. + + + Data: Last data sent by the agent. + + + Graph: Monthly(M), Weekly(W), Daily(D) + and Hourly(H) graphs are generated with the data sent by the + agent against time. + + + On the left hand side of the graph the newst data is + represent, and on the right had side the oldest. + + + The generated graphs are: + + - Hourly graph + () + covers a 60 minute interval + + + + - Daily graph + () + covers a 24 hour interval + + + + - Weekly graph + () + covers a 7 day interval + + + + - Mothly graph + () + covers a 30 day interval + + + + Raw Data: This is the raw data sent by + the agent + + + - Last + month + + + - Last + week + + + - Last + day + + + + Timestamp: This is the hour when last + contact was made. + + + + Complete list of monitors + + This is the description of all the monitors defined by + the agent + + + + + The list shows the information about the monitors in the + following columns: + + + Agent: Agent where the monitor is + defined. + + + Type: Data type of the monitor. For a + monitor this value is always of the generic_proc type. + + + Module name: Name given to the module + when it was created. + + + Description: Description given to the + modulein the agent's config file. + + + Status: The table shows the agent status + through the following icons: + + + + The monitor is OK + + + + The monitor is failing + + + Last contact: Shows the time and date of + the last data packaged received from the agent + + + + Complete list of alerts + + This is the description of all the alerts defined in the + agent + + + + The arlert information is shown in the list divided in the + following fields: + + + Type: Type of alert. + + + Name: Name given to the alert when it + was created. + + + Description: Description given to the + alert when it was created. + + + Min/Max: The values Mininimun and Maximum + configured in the alert. + + + Time threshold: The time threshold + configured in the alert. + + + Last fired: The last time the alert was + executed. + + + Times Fired: Number of times the alert + was launched. + + + Status: Shows if the alert has been + sent through the following icon: + + + + No alerts have been sent + + + At + least one alert has been sent + + + + + Alert details + + The description of all the alerts defined in the server can be + viewed from the "View Agents" > "Alert Details" option in + Operation menu. + + + + In this list all the alerts appear in a similar way as in the + individual view, but now they are shown all together. This + allows a deeper analisys of each alert. + + + + Monitor details + + The description of all the monitors defined in the server + (a monitor is a module of "proc" type) can + be viewed from the "View Agents" > "Monitor detail" option + in the Operation menu. + + + + In this list all the monitors appear in a similar way as in + the individual view, but now they are shown all together. + This allows a deeper analisys of each monitor. + + + + Export Data + + + The Data Export tool can be found in the "View Agents" > + "Export data" option in the Operation Menu. + + + + Three parameters need to be configured for exporting data: the + agent where data resides, the modules to be exported and the + date interval of the data to be exported: + + + + + The fields in the results of Exporting data are: + + + Module: Module name. + + + Data: Data contained by the module. + + + Timestamp: Date and time of the the package + was sent by the agent. + + + + Selecting the CSV format for the output, a text file with + extension .csv is be created. The data + is qualified by single quotes and the fields separated by + commas: + + + + + Statistics + + Two kinds of graphical statistics are displayed from the + "View Agents" > "Statistics" option, in the Operation + menu: + + + + + A graph with the number of modules configurated for each + agent + + + + + A graph with number of packages sent by each Agent. A + package is the number of values from the modules the agent + sends after each time interval + + + + + + + + + + SNMP Console + + Majority of devices can send SNMP traps when have any problem as + reboot, lost interface, the temperature is very high, CPU crash, + etc. With Traps is possible to know the problem when it happens. + + + In Pandora 1.2 there is a SNMP console to receive SNMP traps. + It is possible configure any device to send SNMP traps to + Pandora FMS, you only need the Pandora IP and Community. + + + From SNMP Console in the Operation menu the users can see + the SNMP traps sent to Pandora Server. + + + + SNMP Alerts + + Just like is possible to generate an alert if there is an out of + range module value. It is possible to generate an alert if an + SNMP trap is received with a anorma value. The Alert can consist of + sending and e-mail or SMS to the administrator, sending an SNMP + trap, write the incident into the system syslog or Pandora log + file, etc. Basically anything that can be triggered by a + script configured in the Operating System when Pandora Servers run. + + + In "SNMP Console" > "SNMP Alerts" from Operation menu, the users + can see the configured SNMP Alerts. + + + - + To create a new alert the administrator must click in + . Then appears the + following screen: + + + + To assign an Alert the next fields must be filled in: + + + + + Alert: This can be selected from + the list of alerts that have been previously generated. + + + + + Alert type: You can chose between + "OID", "Custom OID/value" or "SNNMAgent". + + + + + Description: Describes the + function of the Alert, and it is useful to identify + the Alert amongst the others in the Alert General + View. + + + + + OID: The OID to be motitorized + by the alert. + + + + + Custom value: Custom value to be + motitorized by the alert. + + + + + SNMP Agent IP: IP of the SNMP + agent. + + + + + Field #1 (Alias, name): Define the + used value for the "_field1_" variable. + + + + + Field #2 (Single Line): Define the + used value for the "_field2_" variable. + + + + + Field #3 (Full Text): Define the + used value for the "_field3_" variable. + + + + + Min number of alerts: Minimum + number of alerts that can be sent consecutively. + + + + + Max number of alerts: Maximum + number of alerts that can be sent consecutively. + + + + Time threshold: Minimum + duration between the firing of two consecutive + alerts, in seconds. + + + + + + diff --git a/pandora_doc/fr/pandora_chapter4.xml b/pandora_doc/fr/pandora_chapter4.xml new file mode 100644 index 0000000000..656c126a2d --- /dev/null +++ b/pandora_doc/fr/pandora_chapter4.xml @@ -0,0 +1,308 @@ + + + + Gestion des incidents et messages + + + Le processus de monitoring du système a besoin de suivre les incidents + apparaissant dans le système en même temps que la réception et le traitement + des données à surveiller dans chaque interval de temps. + + + + Pandora utilise un outil appelé le Gestionnaire d'Incidents dans ce but, + pour lequel chaque utilisateur peut ouvrir un incident, dans lequel une + description de ce qui s'est passé sur le réseau est présentée. Cela peut + être complété avec des commentaires et des fichiers quand c'est nécéssaire. + + + + Ce système est destiné au travail en groupe. Les systèmes permettant + différents rôles et une gestion électronique des processus métiers (workflow) + permettant de passer des incidents d'un groupe à un autre. Le système permet + à différents groupes et différents utilisateurs de travailler sur le même + incident, partageant l'information et les fichiers. + + + + En cliquant sur "Gérer les Incidents", dans le menu Opération, une liste + montre tous les incidents ordonnés suivant la date à laquelle ils ont été + mis à jour. Des filtres peuvent être appliqués pour n'afficher que les + incidents intéressants pour l'utilisateur. + + + + + + Les filtres suivants peuvent être appliqués: + + + + + Filtre de status d'incident. + L'utilisateur peu afficher: + - tous les incidents + - les incidents actifs + - les incidents fermés + - les incidents rejetés + - les incidents expirés + + + + Filtre de priorité. + Les incidents peuvent être affichés par: + + - toutes priorités + - priorité informative + - basse priorité + - priorité moyenne + - haute priorité + - très high priorité + - maintenance + + + Filtre de groupe. + Utile pour ne sélectionner que les incidents d'un certain groupe Pandora. + + + + + + La liste d'incidents affiche les informations dans les colonnes suivantes: + + + + ID: ID de l'incident. + + + Etat: L'état de l'incident est représenté par les icones suivantes: + + + Incident actif + Incident actifs avec commentaires + Incident rejeté + Incident fermé + Incident expiré + + Nom de l'incident: Nom donné à l'incident + + Priorité: La priorité assignée à l'incident est représentée par les icones + suivantes: + + + + + + Très haute priorité + + + + Haute priorité + + + + Priorité moyenne + + + + Basse priorité + + + + Informatif + + + + Maintenance + + + Groupe: Le nom du groupe auquel l'incident a + été assigné. Un incident ne peut être assigné qu'à un seul groupe. + + + Mis à jour le: La date à laquel l'incident a été + mis à jour. + + + Source: L'origine de l'incident. L'origine est + sélectionnée à partir d'un liste stockée en base de données. Cette liste + ne peut être modifiée que par l'administrateur de la base. + + + Propriétaire: L'utilisateur auquel a été assigné + l'incident. Il n'y a aucun lien avec le créateur de l'incident, puisque + l'incident peut être passé d'un utilisateur à un autre. Un incident peut + être assigné à un autre utilisateur par son propriétaire, ou par un + utilisateur possédant les droits d'administration sur le groupe auquel + appartient l'incident. + + + Ajout d'un incident + + La création d'un incident s'oppère en cliquant sur "Gérer incidents"> + "Nouvel incident", dans le menu Operation + + + + + + La page "créer un incident" apparaît, présentant les champs nécessaires + à la définition de l'incident. La procédure est terminée par un clic sur + le bouton "Créer". + + + + Suivi des incident + + + Tous les incidents ouverts peuvent être suivis. Ceci en cliquant sur + "Gérer incidents" dans le menu Opération. + + + + L'incident est sélectionné en cliquant sur son nom dans la colonne "Nom de l'incident". + + + + L'écran présente alors les paramètres de configuration de l'incident, ces commentaires et + fichiers attachés. + + + + La première partie de l'écran contient la configuration de l'incident + + + + + Les valeurs suivantes peuvent être mises à jour depuis cette page: + + + Nom de l'incident + + + Propriétaire de l'incident + + + Etat del'incident + + + Origine (source) de l'incident + + + Groupe de l'incident + + + Priorité de l'indicent + + + + L'incident est mis à jour en cliquant sur le bouton "Mise à jour incident". + + + Ajout d'un commentaire à un incident + Des commentaires peuvent être ajoutés à un incident en cliquant sur "Ajouter note". + Cela ouvre une page présentant un cadre d'édition de texte. + + + Les commetaires sont écrits dans ce cadre. + Le commentaire apparaîtra dans la section "Notes attachées à l'incident" après un clic + sur le bouton "Ajouter". + + + Seuls les utilisateurs ayant des droits d'écriture peuvent ajouter un commentaire, + et seuls les propriétaires peuvent les supprimer. + + + + Attacher des fichiers à un incident + Il est parfois nécessaire de lier une image, un fichier de configuration, + ou n'importe quel type de fichier à un incident. + + + Les fichiers sont attachés dans la sections "Attacher un fichier". + Les fichiers peuvent être recherchés sur la machine locale puis attachés lors d'un + clic sur le bouton "Télécharger". + + + Seul un utilisateur avec des droits d'écriture peut attacher un fichier, + et seul le propriétaire de l'incident ou du fichier peut le supprimer. + + + La page de suivi d'incidents affiche tous les fichiers attachés à un incident dans + la section "Fichiers attachés". + + + + + Rechercher un incident + + Un incident spécifique peut être retrouvé en utilisant soit un filtre, + comme expliqué dans la première section de ce chapitre, soit en interrogeant + la base par l'intermédiaire de"Gérer incidents" > "Chercher incident" + du menu Operation. + + + + Toute chaîne de texte incluse dans l'incident peut être recherchée + en utilisant cet outil. Ce moteur de recherche parcourt le titre de + l'incident, ainsi que le texte contenu dans l'incident. Mais il ne + cherchera pas dans les commentaires ni dans les fichiers attachés. + La recherche peut être conduite en complément des filtres sur le + groupe, la priorité ou l'état. + + + + Statistiques + + Les statistiques d'incident sont accessibles par "Gérer incidents" > + "Statistiques" dans le menu Opération. Elles peuvent être de cinq types + différents: + + + + Etat de l'incident + + + Priorité de l'incident + + + User ayant l'incident ouvert + + + Incidents par groupe + + + Origine de l'incident + + + + + + + + Messages + + Dans Pandora 1.2 il est possibles d'envoyer des messages aux autres + utilisateurs. Chaque utilisateur peut voir ses messages dans "Messages" + du menu Operation. + + + + + + Pour envoyer un message à un autre utilisateur, cliquer sur "Messages" > + "Nouveau message" dans le menu Operation. + + + + + Il est possible d'anvoyer un message à un groupe depuis "Messages aux groupes" + > "Nouveau message" dans le menu Operation. + + + + diff --git a/pandora_doc/fr/pandora_chapter5.xml b/pandora_doc/fr/pandora_chapter5.xml new file mode 100644 index 0000000000..9fc69e66fc --- /dev/null +++ b/pandora_doc/fr/pandora_chapter5.xml @@ -0,0 +1,117 @@ + + + + Evènements + + Un évènement dans Pandora correspond à tout changement inhabituel + dans un agent. + + + Un évènement est enregistré quand un agent n'envoie plus de données ou démarre, + quand un moniteur est défaillant ou change d'état, ou quand une alarme + est déclenchée. + + + + Un évènement est d'ordinaire précédé par un soucis sur le système + monitoré. Un système de validation et suppression a été créé afin d'éviter + d'oublier des problèmes non analysés, ces évènements peuvent donc être + facilement validés ou effacés si le problème peut être ignoré ou a + déjà été traité et résolu. + + + + Les évènements apparaissent classés chronologiquement suivant leur ordre + d'apparition sur le système, et peuvent être affichés en cliquant sur + "Voir évènements" dans le menu Opération. les évènements les plus récents + sont placés le plus haut dans le tableau. + + + + + + La liste des évènements montre les données dans les colones suivantes: + + + + Etat: L'état de l'évènement est représenté par + l'icône ci-dessous: + + L'évènement a été + validé + + L'évènement n'a pas été + validé + + + Nom de l'évènement: Nom assigné par Pandora à l'évènement. + + + Nom de l'Agent: Agent dans lequel l'évènement a eu lieu. + + + Nom de groupe: Groupe d'agents où l'évènement a eu lieu. + + + ID usager: Utilisateur qui a validé + l'évènement. + + + Date/heure: Date et heure de l'apparition ou la + validation de l'évènement (s'il a été validé). + + + Action: Actions qui peuvent être éxecutées sur + l'évènement. + + + + Cette icône valide l'évènement, faisant disparaître l'icône. + + + + Cette icône supprime l'évènement. + + + Les évènements peuvent aussi être validés ou supprimés + dans les groupes en cochant les cases de la dernière + colonne de l'évènement, puis en cliquant sur le bouton + "Valider" ou "Effacer" en bas de la liste. + + + Statistiques + + + Trois sortes de représentations graphiques statistiques + peuvent être choisies à partir de "Voir évènements" > + "Statistiques" du menu Operation: + + + + + + Le nombre total d'évènements divisé par le nombre de révisés + et non révisés + + + + + + Nombre total d'évènements divisé par les utilisateurs les ayant validés + + + + + + Nombre total d'évènements divisé par le groupe auquel appartient l'agent qui + les a déclenchés + + + + + + diff --git a/pandora_doc/fr/pandora_chapter6.xml b/pandora_doc/fr/pandora_chapter6.xml new file mode 100644 index 0000000000..f58191fa74 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter6.xml @@ -0,0 +1,84 @@ + + + + Système d'Audit + + + Le système d'Audit de Pandora affiche toutes les actions opérées par chaque + utilisateur, ainsi que les tentatives ratées de login. + + + + Le système d'Audit inclus les actions qui ont tentées de dépasser + le système de sécurité: tentatives de suppression d'un incident par + un utilisateur non autorisé, tentative de changer les profils utilisateur + par un utilisateur non autorisé, etc. Son fonction principale est, + avant tout, de suivre les connexions des utilisateurs (login/logout). + + + + Les logs d'audit peuvent être consultés dans "Audit du système" du menu Administration, + classés chronologiquement. + + + + Des filtres peuvent être appliqués sur ces enregistrements pour ne montrer que + ceux présentant un intérêt pour l'utilisateur, discriminés par leur champ Action. + + + + Les actions sélectionnables sont celles définies et stockées dans la base de données + au moment de la sélection. + + + + + + Les informations d'Audit sont affichées dans les champs suivants: + + + Usager: Utilisateurs qui a déclenché l'évènement (SYSTEM + est l'utilisateur spécial pour le système). + + + + + Action: Action associée à l'évènement. + + + + + Date: Date de l'entrée dans les logs. + + + + + IP d'origine: IP de la machine ou de + l'agent qui a déclenché l'évènement + + + + + Commentaires: Commentaires décrivant l'entrée + + + + + Statistiques + + Il n'y a pas de section spéciale pour afficher les statistiques + des Audits du système. Cependant, il est possible d'utiliser les + graphiques générés dans la section Usagers afin d'évaluer les actions + de chaque utilisateur, car ce graphe représenterait le nombre total + d'entrées d'Audit pour chacun: plus l'utilisateur est actif, plus + il y a d'entrée le concernant. + + + Le graphique montre aussi les entrées d'utilisateurs invalides, + comme les tentatives ratées de connexion (login). + + + + diff --git a/pandora_doc/fr/pandora_chapter7.xml b/pandora_doc/fr/pandora_chapter7.xml new file mode 100644 index 0000000000..ebff5277d7 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter7.xml @@ -0,0 +1,99 @@ + + + Serveur Pandora + + Dans Pandora 1.2 il y a plusieurs types de serveurs: Network Server, + Data Server ou SNMP Server. + + + Il est possible de gérer ces Pandora Servers depuis "Gestion des serveurs" + du menu Administration. + + + + Les champs suivants sont affichés dans la page Gestion des serveurs: + + + + + Nom: Nom du serveur. + + + + + Etat: Etat du serveur (service). Vert OK et + Rouge Echoué. + + + + + Addresse IP: IP du serveur. + + + + + Description: Description du serveur. + + + + + Réseau: Marque pour le Network Server. + + + + + Données: Marque pour le Data Server. + + + + + SNMP: Marque pour le SNMP Server. + + + + + Principal: Marqué quand le serveur est maître et + non marqué quand le maître est un backup. + + + + + Vérifier: + + + + + Lancé le: Date de démarrage du serveur. + + + + + Actualisé le: La date de la dernière mise à jour. + + + + + Action: Icônes servant à modifier les propriétés du serveur + ou supprimer un serveur (seulement dans le menu Administration). + + + + + Depuis "Gestion des serveurs" dans le menu Administration il est possible de configurer + et gérer les serveurs. + + + Il est possible de supprimer in serveur avec l'icône + + + Il est possible de changer les propriétés du serveur en utilisant l'icône + + + + Pour un serveur, il est possible de modifier: le nom, l'adresse IP et la description. + + + diff --git a/pandora_doc/fr/pandora_chapter8.xml b/pandora_doc/fr/pandora_chapter8.xml new file mode 100644 index 0000000000..67e1458af3 --- /dev/null +++ b/pandora_doc/fr/pandora_chapter8.xml @@ -0,0 +1,270 @@ + + + + Maintenance de la base de données + + + Le coeur du système Pandora est sa base de données. Toutes les données + collectées sur les machines monitorées sont stockée dans cette base, + des données de l'administrateur aux évènement, incidents et données d'Audit + générées par le système au cours du temps. + + + + Il est évident que l'efficacité et la fiabilité de ce module est vital + pour le fonctionnement correct de Pandora. Une maintenance régulière + de cette base de données est nécessaire. Pour ce faire, les gérants de + la base peuvent utiliser les commandes standard MySQL. Maintenir la base + en bonne condition est critique pour que Pandora fonctionne correctement. + + + + Comme la taille de la base de données s'accroît linéairement, + les données seront compressées pour réduire leur nombre, sans perdre + d'informations importantes, spécialement les graphiques générés avec + les données traitées. + + + Cliquer sur "Maintenance des bases de données" dans le menu Administration + affiche la configuration de la base de données comme définie dans la partie + "Configuration" du menu Administration concernant le compactage et la suppression + des données. + + + + Information sur la base de données + + Les statistiques de la base de données sont générées par Agent, dans + "Maintenance de la base de données" > "Information base de données" + du menu Administration, et sont représentées dans deux sortes de graphiques: + + + + + Nombre de modules configurés pour chaque agent. + + + + + Nombre de paquets envoyés par chaque agent. Un paquet est le groupe + de données liées au module que l'agent envoie à intervalle régulier. + + + + + + + + Ces graphiques peuvent aussi être affichés depuis "Voir agents" > + "Statistiques" dans le menu Operation. + + + Il est possible de voir les informations de la base en mode texte en cliquant sur + "Appuyez ici pour voir l'information de la Base de Données en format texte" + + + + + Nettoyage manuel de la base de données + + Pandora repose sur des outils d'administration puissants pour nettoyer manuellement + la majorité des données stockées dans la base. Cela inclus les données générées + par les agents et le server lui-même. + + + Nettoyage des données des agents + + Débogage des données sélectionnées d'un module + + L'option de nettoyage de données sélectionnées d'un module est + utilisée pour éliminer les entrées hors limites (incohérence), + quelle que soit la raison de leur présence (panne d'agent, données + hors limites, tests, erreurs de base de données, etc.). + Eliminer les données erronnées ou non nécessaires produit une + représentation graphique plus précise et présente les données + sans pics ou échelles invraissemblables. + + + Depuis "Maintrenance des bases de données" > "Epurer les + bases de données" du menu Administration, toutes les données hors + limites rçues d'un module d'un agent peut être éliminée. + + + + Les paramètres du nettoyage sont: agent, module, limtes maximum et minimum + des données. Toutes les données hors de ces limites seront supprimées. + + + Par exemple, pour un module enregistrant le nombre de processus, si nous + somme intéressés seulement par les valeurs comprises entre 0 et 100, toutes + les valeurs supérieures à 100 seront considérées comme des erreurs, du "bruit" + ou des conditions anormales. Si nous prenons une fourchette entre 0 et 100, + toutes les valeurs supérieures et inférieures (comme -1, 100 ou 100000) seront + définitivement supprimées de la base de données. + + + + Nettoyage de toutes les données des agents + + Toutes les valeurs hors limites reçues par un agent peuvent être + supprimées depuis "Maintenance de bases de données" > "Effacement base de données" du menu + Administration. + + + Les données sont supprimées via les paramètres suivants depuis + l'écran "Effacement base de données": + + + + + Effacer toutes les données + + + + + Effacer les données de plus de 3 mois + + + + + Effacer les données de plus d'un mois + + + + + Effacer les données de plus de deux semaines + + + + + Effacer les données de plus d'une semaine + + + + + Effacer les données de plus de 3 jours + + + + + Effacer les données de plus d'un jour + + + + + + + + Nettoyer les données sytème + + Nettoyer les données d'Audit + + Toutes les données d'Audit générées par le système peuvent être supprimées + depuis "Maintenance des bases de données" > "Base de données Audit" du menu + Administration. + + + Les données à supprimer sont sélectionnées en choisissant les options suivantes + dans l'écran "Epuration de la base de données Audit" + + + + + Effacer toutes les données + + + + + Effacer les données de plus de 3 mois + + + + + Effacer les données de plus d'un mois + + + + + Effacer les données de plus de deux semaines + + + + + Effacer les données de plus d'une semaine + + + + + Effacer les données de plus de 3 jours + + + + + Effacer les données de plus d'un jour + + + + + + + Nettoyage des évènements + + Tous les évènements générés par le système peuvent être supprimés depuis + "Maintenance des bases de données" > "Base de données des évènements" + du menu Administration. + + + Les données à supprimer sont sélectionnées en sélectionnant une des options suivantes + de l'écran "Nettoyer la Base de Données des événements" + + + + + Effacer toutes les données + + + + + Effacer les données de plus de 3 mois + + + + + Effacer les données de plus d'un mois + + + + + Effacer les données de plus de deux semaines + + + + + Effacer les données de plus d'une semaine + + + + + Effacer les données de plus de 3 jours + + + + + Effacer les données de plus d'un jour + + + + + + + + diff --git a/pandora_doc/fr/pandora_chapter9.xml b/pandora_doc/fr/pandora_chapter9.xml new file mode 100644 index 0000000000..d51765fe8f --- /dev/null +++ b/pandora_doc/fr/pandora_chapter9.xml @@ -0,0 +1,87 @@ + + + + Configuration de Pandora + + Tous les paramètres configurables dans Pandora peuvent être définis dans + "Configuration" dans le menu Administration. + + + + Ces paramètres sont les suivants: + + + Langage: Pandora supportera plus de + langues au cours de prochaines version ou révisions. Pour + l'instant, la version 1.2 supporte l'Anglais, l'Espagnol, + l'Espagnol d'amérique latine, le Bable (Espagne, Asturias), + l'Italien, le Français, le Catalan et le Portugais du Brésil. + + + Block size for pagination: Maximum size of + the lists in the event, incident and audit log sections. + + + Max. de jours avant de compacter les données: Ce + paramètre contrôle la compression des données. Le données plus vieilles + que le nombre de jours spécifié sont compactées. Pour les gros volumes + de données, il est recommandé de définir ce paramètre entre 14 et 28; + pour les systèmes avec peu de données, ou les systèmes très puissants, + un nombre entre 30 et 50 sera suffisant. + + + Max. de jours avant d'éliminer les données: Ce paramètre + contrôle le durée de conservation des données avant qu'elles ne soient + définitivement éliminées. La valeur recommandée est 60. pour les système + avec peu de ressources ou les machines chargées, le valeur recommandée est 40 + à 50. + + + Résolution des tableaux (1 bas, 5 haut): Cette + valeur représente la précision du logarithm d'interpolation du + générateur de graphiques. + + + Interpolation du compactage (Heures: 1 fine, 10 medium, 20 + mauvaise): Degré de compression utilisé pour compacter la + base de données, avec 1 pour la plus basse compression et 1 pour la + meilleure compression. Une valeur supérieure à 12 implique une perte + conséquente des données. Il est recommandé d'utiliser une valeur + supérieure à 6 si les données seront représentées sur un graphique + dans un intervalle de temps large. + + + Ordre du tableau: cette valeur représente le sens + dans lequel créer les graphs. les possibilités sont droite à auche ou + gauche à droite. + + + Polices Truetype: Cette valeur active ou + désactive le format de polices truetype. Les valeurs possibles sont + Activé ou Désactivé. + + + Image de base: Cette valeur définit l'image de fond + avec la possibilité de choisir entre de muiltiples fonds d'images. + + + Liens + + Liens vers différents sites internet ou privés peuvent être configurés + dans Pandora: moteurs de recherches, applications, ou intranets + d'netreprise. + + + Les liens configurés dans Pandora peuvent être édités dans "Configuration" > + "Liens" du menu Administration. + + + + Un nouveau lien est créé en cliquant sur "Ajouter". Le lien peut ensuite être édité: + + + + diff --git a/pandora_doc/fr/pandora_install.xml b/pandora_doc/fr/pandora_install.xml new file mode 100644 index 0000000000..a9476c57ae --- /dev/null +++ b/pandora_doc/fr/pandora_install.xml @@ -0,0 +1,1456 @@ + + + &pandora; installation + + Prerequisites + + &pandora; is not only a single app, it is made up by + several shellscript files (Unix/Linux Agents), a WEB application + in PHP (Console), some code in C++ (Windows Agent), some code in + PERL5 (Server) and some structure and data in SQL (Database), + so, to get all this running you need to have some pieces of + software installed in your system. This is a list of packages, + libraries and software you need before install &pandora;. + + + + Pandora Servers + + Pandora FMS 1.2 has three kind of servers: Data server, Network + Server and SNMP Server/Trap console. All of them could be + installed in the same machine or in different machines, also, + you could setup many of them in a High Availability environment + or using it to manage highs loads of data. + + Pandora Data Server + + To build Pandora Data Server you need to + have the following perl modules and software installed in your + machine. This packages could be installed using your + distribution packaging system or using CPAN. +
+ + XML::Simple, useful XML functions + + Digest::MD5, MD5 generation + + Time::Local, Date and Time basic manipulation + + DBI, DB interface with MySQL + + + + Date::Manip, needed to manipulate Date and Time formats + of input, output and compare + + + +
+ + + You can find them at http://www.cpan.org or install using your + default package instalation system. These packages are in the + default distribution of Suse 9.1 and Debian 3.0 GNU/Linux. Also + available for Solaris in CPAN repository. + Next, you need to set the TZ (Time Zone) environment + variable. + + + + Pandora Network Server + + Requires SSH Server and Perl v5.8 or higher and the next Perl Modules: +
+ + + + IO::Socket, manage and manipulation of TCP/UDP sockets + + + + + Time::HiRes, needed for ICMP times + + + + + Time::Local, Date and Time basic manipulation + + + + + SNMP, for SNMP management + + + + + Date::Manip, needed to manipulate Date and Time formats + of input, output and compare + + + + + Net::Ping, to calculate latency times (it's required + that the server runs as root user). + + + +
+ To use SNMP fuctions it's needed also to have installed the + net-snmp package. It's worth to say that to run modules of + GENERIC_ICMP_DATA type (calculate ICMP latency time) Pandora + Network Server must run with root privileges. + + + Pandora SNMP Server + + You need to install the NET-SNMP package which is included in + all GNU/Linux distributions. You have to use the snmptrapd + binary and copy or link it to $HOME_PANDORA/util, where + $HOME_PANDORA is the instalation directory of Pandora. + + + This binary gets the SNMP traps, generating a log that is + parsed by the Pandora Server. + + + + Installing Pandora Server + + Create the /opt/pandora directory and + "gunzip" and "untar" here the + pandora_server_1.2.tar.gz file. + + + Create an user pandora in OS. Usually you do that in GNU/Linux + with commands: + + useraddd pandora -d /home/pandora + mkdir /home/pandora + chown pandora /home/pandora + + This user will be used by the SSH transfers to the server, so + this user will need a strong password. + + + In the file + /home/pandora/.ssh/authorized_keys we will + add the public key of each agent which send data to Pandora + Server. These keys must be SSH v2, OpenSSH DiffieHellman (DF) or + RSA. To convert between keys you can use the ssh-keygen tool. + + + Pandora Server will check and parse XML files sent by Pandora + Agents and will insert the data into the Database. + + + Check launch scripts (pandora_network, pandora_server, + pandora_snmp) and check for pathnames in the first two variables + in script. roa Server. This usually is + /opt/pandora_server + + + + Configuring your new Pandora Server setup + + After install Pandora Server in, you will need to edit the file + pandora_server.conf, where are defined the + variables of the server configuration. File + pandora_server.conf is a text file, you could + edit with your prefer text editor, like emacs. This configuration + file is common to all kinds of Pandora Server (Data server, SNMP + Server, Network server), you also could have different copies of + configuration file for each Pandora Server you have. + + + Edit configuration file of Pandora Server, usually + /opt/pandora/conf/pandora_server.conf and + take a look at the lines: + + dbuser pandora + dbpass pandora + dbhost localhost + + Please change them to your own data. For security reasons isn't + recommended use the default values. + + + These are default values, and all must be existing directory and + filename and valid username, password and hostname. + + + Remember: you need to create the directory /opt/pandora/data_in + where Pandora Server will read and write data, sent by remote + agents using ssh/scp. This directory must be owned or with + permissions to write for user "pandora". If you don't have a + "pandora" user yet, create it. + + + You can run Pandora Server with an user without privilegues, you + can use the user "pandora", it only needs to run /usr/bin/perl and + access to /opt/pandora and + /opt/pandora/data_in directories. + + + This is true with all the components but with Pandora SNMP Console + needs root user to open UDP port 161 (this can be solved setting + SUID0 to the snmptrapd binary) and running the rest of the Server + using an user without privileges. + + + Also Pandora Network Server can be run using an user without + privileges, but the GENERIC_ICMP_DATA type won't work, as root + privileges are required to get ICMP latency times. + + + Check the MySQL connection with the user and password before running the server + + + Pandora Server distribution tarball includes a Posix/System V + start/stop script for "daemonize" Pandora Server. It is possible + that you need to customize, but its runs smoothly on GNU/Linux + (debian, Suse) and Solaris 8 systems. It has start|stop|restart + parameters to include it in your default init level directory and + it creates a logfile defined in $log_file variable (by default is + /opt/pandora/pandora.log): + + /etc/init.d/pandora_server start + + + + Setting up SSH configuration + + Pandora, uses SSH protocol to copy XML data packets, + generated by the agents, to the server. You need to generate a + SSH2 key in every agent, and copy the public key in + /home/pandora/.ssh/authorized_keys, so you + need to create a user called "pandora" without privileges. This + user will be used by agents to copy data into Pandora Data Server + /opt/pandora/data_in directory. + + + Please BE SURE that user "pandora" exists (if not, create with + useradd), and + /home/pandora/.ssh/authorized_keys exists and + ownership of this file and directory is for pandora user, and + permissions set to 600. + + + Please be sure that directory + /opt/pandora/data_in exists and pandora + user is able to write in. + + + + + + Pandora Console and Pandora database + Pandora database install + + Please look at MySQL install and management guide + (http://dev.mysql.com/doc) to obtain information about how to + create a MySQL database, how to manage mysql users and give + him/her privileges to read/write in Pandora database. Remember + that you must write the password of the root user in MySQL + database to enter mysql command line. This user is not the same + of the Operating System. The root password in MySQL is in blank + by default (within almost all distributions), you must changed + this password with the MySQL command + mysqladmin. Please be careful with this. + + + You need a database with name "pandora", you could rename it, but + you need to reconfigure in server too. + + + To create the structure of Pandora database in MySQL Server you + have the SQL script "pandoradb.sql". + + + It creates tables and indexes needed to insert information into + Pandora database. + + + You MUST populate database with SQL script "pandoradb_data.sql", + it inserts data needed to run Web Console and default user + (login: admin, pass: pandora) to access Pandora Web Console. + + + First create a database called "pandora", and set an user to be + able to access this database: + + + mysql> create database pandora; + + + Later, execute the next commands using a user with enough + privileges to create tables and indexes for pandora Database into + your MySQL Server: + + + cat pandoradb.sql | mysql -D pandora -u root -p + cat pandoradb_data.sql | mysql -D pandora -u root -p + + + You can also use the source command, if you are connected to + MySQL, from the MySQL prompt: + + + mysql> use babel + mysql> source path_to_babel_dbstruct.sql + mysql> source path_to_babel_dbdata.sql + + + This example is valid using root user in + MySQL + + + Now we will create an user "pandora" and will be given to it + privileges from the localhost: + + mysql> grant all on pandora.* to 'pandora'@'localhost' + identified by 'pandora'; + + Keep in mind that users need access from Pandora WEB Console and + from Pandora Server, if your deployment has many subcomponents + in different physical machines, you need to setup a MySQL user + with privileges to access from different locations. + + + If you get the error "Warning: mysql_connect() + [function.mysql-connect]: client does not support authentication + protocol requested by server; consider upgrading" when + authenticating Web Console, you have to change the way the + password is stored into the database: + + mysql> set password for 'pandora'@'localhost' = old_password('pandora'); + + Please note this user will be used by several pandora + subcomponents (Pandora Server, Pandora Web Console) to access + database. + + + + + Pandora console install. + Prior to install Pandora console, you need the following + dependencies and software needed: +
+ + + + Web server. Apache2 is recommended. + + + + + PHP 4.3.x, or PHP 5.x. Both has been tested for Pandora 1.2 + + + + + PHP Modules for MySQL, GD, session management and SNMP. + + + + + JpGraph, it is necesary to generate graphics. It has an + open source license, you can download it in + http://www.aditus.nu/jpgraph/ + + + +
+ + + To install Pandora Console, simply untar in your HTTP server + publishing directory and set perms to www-data or http user. + + + To setup Pandora Console, you only need to modify a file, + include/config.php, where the following + variables are included in .php code: + + + $dbname="pandora"; // name of database for pandora) + $dbuser="pandora"; // mysql user to access db + $dbpassword="pandora"; // Password for mysql user + $dbhost="pandora"; // Hostname or IP of mySQL server + + + If database is defined and was correctly installed, you can + now access: + + http://host:port/installdir/index.php + + The first time you log there is a default admin user "admin" + and password "pandora". It's worth to say that YOU + MUST CHANGE CREDENTIALS BEFORE LOGIN FIRST TIME, + change it or create another account, give it administrator + privileges, and disable this one. + + + + If you cannot see a screen like this, it's possible that you + have problems with PHP instalation. When you installed the + Web, please check that PHP engine its running. Fist try to + access to the server IP with a browser. You must see the + Welcome Apache page. + + + Remember that alter installing the PHP and the PHP module for + Apache you must stop and start the Server Apache. As an + example, Ubuntu with Apache2: + + /etc/init.d/apache2 stop + /etc/init.d/apache2 start + + + To verify the PHP and Apache integration you can create the + file test.php with the following lines: + + <?PHP + echo "<h1>TEST</h1>"; + phpinfo(); + ?> + + Now, copy this file in the Apache HTTPDOC directory. This + directory depend of the Operating System or Linux + Distribution, for example in Ubuntu this directory is + /var/www and in SUSE is + /srv/www/htdocs). RedHat based + distributions uses /var/www/html as well + + + To check this integration, please use your browser to open the + following URL: + + http://IP/test.php + + + Where IP is IP Address of your Apache server. If the + integration is correct you will see in the browser a text + string with big font: TEST and a big table with + a lot of info about your PHP installation. + + Graphic reporting instalation + + For correct graphic generation, you need to enter the full + path to a TrueType font installed in your system. By default a + free truetype font is distributed with Pandora Console + package, and placed in + ./reporting/FreeSans.ttf file. Please + check that setup directive + $config_fontpath is well configured. + + + Pandora 1.2 uses JpGraph for viewing graphics. JpGraph is a + different project and has no relationship with Pandora, so you + need to install it. You can find at + http://www.aditus.nu/jpgraph/. Download + last version (2.x), and place all .php + files from src directory into + reporting/jpgraph Pandora Console + directory. + Depending on the jpgraph you downloaded you might be required + to change the includes on the reporting/fgraph.php + adding the correct path, it will looks like: + include ("jpgraph/src/jpgraph.php"); + + + + + + Pandora Agents + Introduction + + &pandora; agents collect all system's data. They are executed in + each local system, although they can also collect remote + information by installing monitoring systems for the agent in + several different machines - called satellite agents. + + + They are developed to work under a given platform, making use of + the specific tools of the language being used: VBSCript/Windows + Scripting for Microsoft platforms (Win2000, WinXP y Win2003), + ShellScripting for UNIX - which includes Linux, Solaris, AIX, HP-UX + and BSD, as well as the Nokia's IPSO. Pandora agents can be + developed in virtually any language, given its simple API system + and being open source. There are branches of the Pandora project + started for the creation of agents in Posix C, Perl and Java for + those systems requiring closed agents. + + + Pandora Agents are Free Software, i.e., the way agents collect and + sent information is documented. An agent can be recreated in any + programming language, and can be upgraded easily, to improve + aspects of the program not covered so far. + + + This document describes the installation of agents in machines + running over Windows and Unix operating systems. + + + + Generic role of the agents + + Regardless the platform an agent is running on, this is formed of + the following elements: + + + + A script (or binary application in Windows) that collects and + sends the data to the server. For UNIX machines the script is + called pandora_agent.sh and is executed directly from the Pandora + agent folder. + + + One or several configuration files where the values to be + collected are defined. The file is called pandora_agent.conf both + for Windows and Unix machines. + + + This simple structure makes it easy the customisation of an + agent. There is no need to code again the agent to modify the + way it works, as the configuration file holds most of the + parameters needed to do so. + + + + Main Script + + The main script is the executable file that collects the data + specified in the configuration file. It sends the data to the + server in XML. In Windows machines application is installed as a + service and is executed at the time intervals set in the + configuration file. In machines running over UNIX the main script + is run through a special script called + pandora_agent_daemon, and + runs continuously in the machine as a process. + + + + Configuration File + + The data collection in the host system is the gathering of + independent data units, which are defined in the + pandora_agent.conf file. The + pandora_agent.conf file is divided in two parts: + + + + General parameters: Configure general + options about server location, agent name, interval, and + other general options. + + + + + Module definitions: Configure and + define the method of extraction for each piece of + information that will be extracted from local host and sent + to Pandora Server. + + + + + General parameters + + The general parameters of the agent configuration are defined in + this section. Some of these parameters are common for all systems + and others specific for Windows or UNIX. The general parameters + are: + + + + + server_path: The server path is the + full path of the folder where the server stores the data + sent by the agent. It is usually + /opt/pandora/data_in. + + + + + server_ip: The server IP is the IP + address or the host name of the Pandora server, where + the data will be stored. The host must be reachable and + must be listening to port 22 (SSH). + + + + + temporal: This is the full path of + the folder where the agent stores the data locally, + before it is sent to the server. It must be said that + the data packages are deleted once the agent tries to + contact Pandora server, no matter if the communication + was successful or not. This is done to avoid over + flooding hard drive of the host system where the agent + runs. The location of the local folder varies with the + architecture of the host system. In Unix systems this is + usually /opt/pandora/data_out, and + in Windows systems + C:\pandora\data_out. + + + + + + interval: This is the time interval + in seconds in which the agent will collect data from the + host system and send the data packages to the + server. The recommended value ranges from 300 (5 + minutes) to 600 (10 minutes). This number could be + larger, although it is important to consider the impact + of a larger number on the database. + + + + + debug: This parameter is used to + test the generation of data files, forcing the agent to + do not copy data file to server, so you can check data + file contents and copy XML data file manually. It does + not delete any data when the process is finished, so + data file will be in temp directory. The activity is + written in a log file. The file is named + pandora_agent.log. This log file can be used to test the + system and to investigate potential issues. + + + + + agent_name: This is an alternative + host name. This parameter is optional as if it is not + declared the name is obtained directly from the system. + + + + + checksum: This parameter can take + two values. If the value is 1, the checksums are + performed through MD5. If the value is 0, the checksum + is not performed at all. This may be useful for systems + where a MD5 tool cannot be implemented. If the checksum + is deactivated in the agent it must be also disconnected + in the server. Otherwise it could create problems. + + + + + An example of the general parameters from a Unix configuration would be. + + server_ip Pandora_Server + server_path /opt/pandora/data_in + temporal /opt/pandora/data_out + interval 300 + agent_name satellite_agent + debug 1 + checksum 1 + + + + Module definition + + Each data item that is to be collected must be defined precisely + in each module, using the exact syntax. As many values as + necessary can be set to be collected, adding at the end of the + general parameters as many modules as the number of values to + collect. Each module is made of several directives. Following is a + descriptive relation of all module marks available for Unix agents + (almost all of them are applicable to Windows Agent too). + + module_begin + + Defines the beginning of the module. + + + module_name name + + Name of the module. This is the id for this module, choose a + name without blank spaces and not very long. There is no + practical limitation (max of 250 chars) but will be more easier to + manage if you use short names. This name CANNOT be duplicated + with a similar name in the same agent. This name could be + duplicated with other modules in other agents. + + + module_type type + + Data type the module will handle. There are four data types for agents: + + + + Numeric (generic_data). Simple numeric data, float or + integer. If the values are of the float type, they will be + truncated to their integer value. + + + + + Incremental (generic_date_inc). Integer numeric data equal to + the differential between the actual value and the previous + one. When this differential is negative the value is set to 0. + + + + + Alphanumeric (generic_string). Text strings up to 255 characters. + + + + + Monitors (generic_proc). Stores numerically the status of the + processes. This data type is called monitor because it assigns + 0 to an "Incorrect" status and any value above 0 to any + "Correct" status. + + + + + + + module_exec command + + This is the generic "command to execute" + directive. Both, for Unix and Windows agents there is only one + directive to obtain data in a generic way, executing a single + command (you could use pipes for redirecting execution to anoter + command). This directive executes a command and stores the + returned value. This method is also available on Windows + agents. This is the "general purpose method" for both kind of + agents. + + + For a Windows agent there are more directives to obtain data, who + are described following this lines. + + + module_service service (Win32 Only) + + Checks if a given service name is running in this host. Remember + to use " " characters if service name contains blank spaces. + + + module_proc process (Win32 Only) + + Checks if a given processname is running in this host. If the + process name contains blank spaces do not + use " ". Also notice that the process name must have the + .exe extension. The module will + return the number of process running with this name. + + + module_freedisk drive_letter: (Win32 Only) + + Checks free disk on drive letter (do not forget ":" after drive + letter. + + + + module_cpuusage cpu id (Win32 Only) + + Returns CPU usage on CPU number cpu. If you only have one cpu, + use 0 as value. + + + + module_freememory (Win32 Only) + + Return free memory in the whole system. + + + module_min value + + This is the minimum valid value for the data generated in this + module. If the module has not yet been defined in the web + console this value will be taken from this directive. This + directive is not compulsory. This value does not override the + value defined in the agent if the module does not exist in the + management console. It is created automatically when working on + learning mode. + + + module_max value + + It is the maximum valid value for the data generated in this + module. If the module has not been defined in the web console + this value will be taken from this directive. This directive is + not compulsory and is not supported by the Windows agent. This + value does not override the value defined in the agent if the + module does not exist in the management console. This is created + automatically when working on learning mode. + + + module_description text + + This directive is used to add a comment to the module. This + directive is not compulsory. This value does not override the + value defined in the agent if the module does not exist in the + management console. This is created automatically when working + on learning mode. + + + module_interval factor + + Pandora 1.2 introduces this new feature. You can, for each + module, setup its own interval. This interval its calculated as + a multiply factor for agent interval. For example, if your agent + has interval 300 (5 minutes), and you want a module only be + calculated each 15 minutes, you could add this line: + module_interval 3. So this module will be + calculated each 300sec x 3 = 900sec (15 minutes). + + + module_end + + Ends module definition + + + Examples + + An example of a Windows module, checking if EventLog service is + alive, would be: + + module_begin + module_name ServicioReg + module_type generic_proc + module_service Eventlog + module_description Eventlog service availability + module_end + + An example of a Unix module would be: + + module_begin + module_name cpu_user + module_type generic_data + module_exec vmstat | tail -1 | awk '{ print $14 }' + module_min 0 + module_max 100 + module_description User CPU + module_end + + + + + + +Agent types + + It is possible to monitor virtually any system with Pandora. This + can be done either with a local agent collecting data directly from + the system to be monitored, using a a satellite agent collecting + data from a system by SNMP or using the new Pandora 1.2 agents, the + remote agents, who can chack using remote network polling (TCP, UCP, + ICMP/PING and SNMP) remote services, from the Pandora Network + Server. + + + The local agents can be either Windows or Unix agents. The satellite + agents can be implemented using any of the agents above. The modules + are configured to collect data from the external system by, for + example, an SNMPGET tool. + + +UNIX agents +Introduction to Unix agents + + The in-built UNIX applications and tools make the agents running on + this system be very simple. There are also agents developed for AIX, + Linux, Solaris and BSD platforms, some of them very similar but not + identical. Requirements for the installation of Pandora Agents on + UNIX + + AIX + + MD5 signatures are used to guarantee the integrity of the + generated data packages. The MD5 package is integrated in AIX 5.1 + and above. There is a freeware package for AIX 4.3 but it has + several issues and might not work correctly. In the case of having + problems with the AIX agents the checksum system used to validate + the integrity of the data can be disabled. + + + Solaris + + The MD5 package is necessary to execute the Solaris agent + correctly. This package is available from http://sunfreeware.com + . It can be also downloaded for Solaris 8 from the following URL: + + + ftp://ftp.sunfreeware.com/pub/freeware/sparc/8/md5-6142000-sol8-sparc-local.gz + + + MD5 Package installation on Solaris + + + + root@stest:/tmp:> gzip -d md5-6142000-sol8-sparc-local.gz + root@stest:/tmp:> pkgadd -d ./md5-6142000-sol8-sparc-local + + The following packages are available: + 1 SMCmd5 md5 + (sparc) 6142000 + + Select package(s) you wish to process (or 'all' to process + all packages). (default: all) [?,??,q]: 1 + + + Solaris SSH + + The suggested SSH client is OpenSSH. If any other SSH client is to + be used it must be considered that each piece software may have + different ways to generate or manage keys. For example, if + F-Secure SSH is used, the public key must be in OpenSSH format + when the keys are generated. The format can be changed from IETF + to OpenSSH with F-Secure SSH, using the following command: + + + + ssh-keygen -i -f file_ietf_pubkey + + + + + GNU/Linux + + SSH and MD5 should be installed in Linux by default, but if they + are not they can be installed using the tools available in each + distribution. + + + BSD (IPSO) + + SSH and MD5 should be installed by default. If they are not, it is + necessary to install them. + + + + + + +Pandora Unix Agent install + + The software comes in a .tar.gz file. First of all the file needs + to be extracted into a folder, usually /opt/pandora_agent, + although any other folder may be used. If a different folder is + used, the daemon launcher must be modified by changing route to + $PANDORA_HOME. + + + There is hardly any difference between AIX, Solaris and Linux, and + they all work around the hash MD5 generation binaries. + + + This is the structure of the installation in /opt/pandora_agent/ + once the files have been extracted: + + + /opt/pandora_agent/data_out, folder where the + data collected by the agents is stored. + + + /opt/pandora_agent/doc, folder with + information about the agent and its license. + + + /opt/pandora_agent/pandora_agent.conf, file + where the data to be collected is defined, along side the command + to be executed for the data collection. This is the system + core, as it defines the main data to be collected in any Firewall. + + + /opt/pandora_agent/pandora_user.conf, file + where several of the parameters to collect data from the monitored + system are defined in more detail. + + + /opt/pandora_agent/pandora_agent.sh, this is + the actual Pandora agent. This file is a shellscript that collects + the data configured in the pandora_agent.conf and + pandora_user.conf files. It also transfers the data packages to + the Pandora server. + + + /opt/pandora_agent/pandora_agent_daemon, + start and stop script. It makes a call to pandora_agent.sh. It + offers two options, start and stop. + + + /opt/pandora_agent/pandora.log, text file + where the activity of the Pandora agent is saved, when the agent + is executed in debugging mode. + + Key generation + + The SSH keys generated must be: + + + + SSSH version2 keys + + + + + Open SSH format keys + + + + + DiffieHellman (DH) format keys + + + + + To generate the keys the command ssh-keygen is executed followed + by the specific parameters for our operating system. Please, + create key WITHOUT password. + + + The public key must be copied into the + /home/.pandora/authorized_keys file in the + Pandora server. Before starting the Pandora agent the SSH + authentication must be checked. To do this the following command + must be executed on the agent machine: + + $ ssh pandora@pandora_server + + + The system must connect successfully BEFORE launching the Pandora agent. + + + First running of the Unix agent + + To start the agent it is only necessary to execute + pandora_agent_daemon start from /opt/pandora_client. Pandora Agent + creates a file (/var/run/pandora.pid) with the PID number of the + process when it is started. + + + For IPSO systems the agent will be started with a nice -10 + priority, so it becomes the process with the lowest priority over + the system CPU. It will be executed when no other processes with a + higher priority are waiting in the system CPU queue. + + + In BSD systems the maximum priority is +20 and the lowest -20. + + + To stop agent, execute pandora_agent_daemon stop from /opt/pandora_agent. + + + + Advanced configuration for Unix Agent + + The real power of Pandora resides in the capability of the agents + to run user defined scripts. This could be used to collect + specific data or to perform an operation to return any desired + value. This is the purpose of pandora_user.conf. + + + This file is executed every in agent loop. It is a shell-script in + which any command can be executed, as long as the output is in the + XML format the agent uses to send data to the server. The XML + structure would be: + + <module> + <name>NAME</name> + <type>TYPE</type> + <data>DATA</data> + </module> + + + Where NAME, TYPE and DATA are the variables already defined in + previous sections. The XML must be built manually, usually using + echo commands. + + + For example, this would be the script a customized agent would use + for Checkpoint FW1 in IPSO agents: + + #!/bin/sh + # Pandora User-Defined acquisition script + # This code is under GPL licence + # Please refer documentation for more example and a more + # depth usage instructions + + # mbuf clusters usados (%) + MBUF_TOTAL=`netstat -m |grep "mbuf cluster" | tr -s "/" " " |awk '{ print $2 }'` + MBUF_USED=`netstat -m |grep "mbuf cluster" | tr -s "/" " " |awk '{ print $1 }'` + MBUF_USED_PER=`echo $MBUF_TOTAL $MBUF_USED | awk '{ print $2 / ($1 / 100) } + + echo "<module>" + echo "<name>MBUF_CLUSTER_USED_PER</name>" + echo "<data>$MBUF_USED_PER</data>" + echo "<type>generic_data</type>" + echo "</module>" + + + + A more complex example could be: + + " + echo "Packet_Generator_Check" + echo "generic_proc" + UNO=`ifconfig eth2 | grep "TX packets" | cut -f 2 -d ":" | grep -o -e "[0-9]*"` + sleep 20 + DOS=`ifconfig eth2 | grep "TX packets" | cut -f 2 -d ":" | grep -o -e "[0-9]*"` + HORA=`date "+%k"` + if [ "$HORA" -lt "8" ] && [ "$HORA" -gt "11" ] + then + # Time out of range, no checking, everything OK + # Fuera de hora, no compruebo, esta OK + echo "1" + else + if [ "$UNO" == "$DOS" ] + then + echo "0" + else + echo "1" + fi + fi + echo "" + ]]> + + + + + Implementation examples for Unix Agents + + Example #1: calculate the number of HITS of the main page of an + Apache Web server: + + module_begin + module_name WEB_Hits + module_type generic_data_inc + module_exec cat /var/log/apache/access.log | grep "index" | wc -l + module_end + + + + Example: check if the process of the DNS server (named) is active + or fell over: + + module_begin + module_name DNS_Daemon + module_type generic_proc + module_exec ps -Af | grep named | grep -v "grep" | wc -l + module_end + + + + Complete example of the configuration of an agent for Linux + + + + + + + + + Pandora FMS Windows Agents + + Build Pandora FMS Windows Agent from sources + + In order to build from sources, you will need the latest + Dev-Cpp IDE version, with the MinGW tools. Download from + http://www.bloodshed.net/devcpp.html + + + Open PandoraService.dev with Dev-Cpp and construct the + project. Everything should compile fine in a default + installation. + + + + Pandora FMS Windows Agent installation (installer) + + Starting with Pandora FMS v1.2.0, Windows version comes with + an automated installer, provided with excelent freesoftware + Install Jammer, so install now is very easy. You only need to + choose a destination path, install and generate manually SSH + keys as described below. For personalized or corporate + deployments, you also can create your own installer (we + provide install jammer sources for creating your own + installable, so you can include a set of SSH keys in your own + installer package). + + + Creating SSH keys with Windows Agents + + Go to .\util of your Pandora FMS agent for + Windows and run puttygen.exe. Choose option + "Generate keys, SSH-2_DSA, 1024". + + Press Generate. Export key to OpenSSH key (Pandora's SSH implementation uses a port of OpenSSH). + + We have no chosen password, so press YES: + + Save it as C:\Program Files\Pandora_Agent\keys\id_dsa + + Now let's copy the public key to clipboard + + and paste it as C:\Program + Files\Pandora_Agent\keys\id_dsa.pub, and also to + /home/pandora/.ssh/authorized_keys file in + server to establish a correct SSH automatic key authentication. + + + + + Manual Pandora FMS Windows Agent installation (without installer) + + Before running or installation of Pandora Windows service, you + must create the configuration directory and extract the + PandoraBin.zip file into it. + + It doesn't matter where it is installled, because Pandora Agent + will adapt to any local directory. In the examples, the + application will be installed in C:\Pandora\ + + + This directory will hold the configuration files, which are: + + c:\Pandora\pandora_agent.conf :: Pandoramain configuration + c:\Pandora\id_dsa :: Private SSH key + c:\Pandora\id_dsa.pub :: Public SSH key + + + + To install manually (without installer) the Pandora FMS Windows Agent execute this sentence in a + Windows command line: + + + PandoraService.exe --install + + + The Agent will be installed into the Windows services + system. You can check it on Control Panel -> Administrative + tools -> Services. + + + To run the Agent open the "Services" dialog (Control Panel -> + Administrative tools-> Services), search the "Pandora Service" + service and run it clicking the play button. To stop the + service, open the "Services" dialog, search the "Pandora + Service" and click the stop button. + + + To uninstall the Pandora Windows Agent, execute this sentence in + a Windows command line: + + PandoraService.exe --uninstall + + + + + Windows Agent testing + + You can check the Pandora Windows Agent output in the + C:\babel\babel-debug.dbg file, that is a + plain text file and includes info about the execution flow of + the Agent. + + + To test that SSH is working correctly, you can use the + --test-ssh parameter in the executable file. This force babel + to conect using internal SSH and copy a file called + "ssh.test". + + + + Windows Agent configuration + + All setup is made in babel_agent.conf. + This file is a list of keys/values pairs. Here is an example + of this file. + + + + + + + + + diff --git a/pandora_doc/fr/pandora_introduction.xml b/pandora_doc/fr/pandora_introduction.xml new file mode 100644 index 0000000000..a32dff2b27 --- /dev/null +++ b/pandora_doc/fr/pandora_introduction.xml @@ -0,0 +1,509 @@ + + + Introduction to Pandora FMS + Pandora. The Free Monitoring System + + Pandora FMS is a monitoring application to watch systems and + applications. Pandora allows to know the status of any element of + your bussiness systems. Pandora watch for your hardware, your + software, your multilayer system and of course your Operating + System. Pandora could detect a network interface down and the + movement of any value of the NASDAQ new technology market. If you + want, Pandora could sent a SMS message when your systems + fails... or when Google value low below US$ 330. + + + Pandora FMS will adjust, like an octopus, to your systems and + requirements, because it has been designed to be open, modular, + multiplattform and easy to customize. + + + + Introducing Pandora FMS. + + &pandora; is a monitoring tool that allows a system + administrator to visually analise the status and efficiency of + Operating Systems, Servers, Applications and Hardware Systems - + such as firewalls, proxies, databases, Web servers, tunnelling + servers, routers, switches, processes, services, remote access + servers, etc. - all integrated into an open and distributed + architecture. Pandora can be implemented over any operating + system, with specific agents for each platform. Pandora can also + monitor any TCP/IP hardware system, as load balancers, + routers, switches, printers, etc. + + Pandora architecture is formed of four main components: + + + + Web Console: Pandora's user + interface. The user controls and operates the system with + it. Several Web consoles can be implemented in a single + system. The Web console is written in PHP, and it is over a + database and a Web server. It is compatible with any + platform - GNU/Linux, Solaris, Win2000, AIX, etc.T + official supported platform is GNU/Linux, though + + + The console permits the user to control the status of the + agents, view statistical information, generate graphs and + data tables, keep a system incident control,moreover it is able + to generate reports and change the alerts, agents, and user + profile settings. + + + + + Server: In Pandora 1.2 there are three + different servers: + + + The core server is the receptor of the data packages and + generates the alerts - it is the brain of the system. + Several servers can work alongside for larger systems. + The core server accesses Pandora database, which is shared + with the Web server, and stores the processed data + packages. Server executes as daemon, and processes the + packages stored in its file system. Data is generated by the + system agents. Despite the server's low system resources + comsumption and simple installation and operation, the core + server is the most critical element of the system. The core + server receives and processes the produced data, and fires + the alerts and the events. + + + The Network Servers monitorize remote systems using + network resources like ICMP, TCP, UDP or SNMP + Queries. Network Servers are acting itself like "Network + Agents". This server fires the alerts and the events for this + modules. + + + The SNMP Server receives and processes the snmp traps, and fires + the alerts associated to it. + + + + + Central Database: At the moment the + system only supports MySQL. The central database keeps all + the information Pandora needs to work - agent data, + settings, user information, incidents, system settings, + etc. The system can use a MySQL cluster to store the + information, or a High Availability (HA) solution for larger + sytems. + + + This database can work with any of the platform officially + supported by MySQL. Pandora can be implemented with MySQL + versions from 3.0 to 5.0, although the latest is recommended. + + + + + Pandora Agents: They collect all the + system's data. They are executed in each local system, + although they can also collect remote information by + intalling monitoring sytems for the agent in several + different machines - called satellite agents. + + + They have been developed to work under a specific platform, + making use of the specific tools of the used language: + ShellScripting for Unix - which includes GNU/Linux, Solaris, + AIX, HP-UX and BSD, as well as the Nokia's IPSO. Pandora + agents can be developed in virtually any language, given its + simple API and being open source. Windows agent are + developed in a free development environment for C++ and uses + the same interface and modularity than Unix agents. + + + The old agent for Windows plattforms was developed on VBS + Scripting language, and is deprecated with the new Pandora + 1.2 windows agent. + + + + + + + What kind of systems/ services can be monitored? + + At present, with Pandora any process or system that through a + command returns a value can be monitored, as well as any value in + any Operating System log file or similar. Some examples of already + existing implementations below: + + Number of connections (sessions) of Checkpoint FW-1 + Number of NAT sessions of Checkpoint FW-1 + Number of connections of Linux NetFilter / IPTables firewall + Number of FW-1 logged packets + Number of FW-1 dropped packets + Number of FW-1 accepted packets + State of High Availability in FW1 NG + Last policy installed in a Firewall-1 module + Synchronization state of the modules in FW1 NG + CPU of the system: idle, user and system + Number of processes of the system + Temperature of the CPU of a system + Value of a MS Windows registry entry + Queued jobs in a generic dispatcher + Memory of the system: free, swap, kernel Fw-1, cache + Percentage of free space on disc (for different partitions) + Messages processed by a mail gateway + Existence of a string in a text file + IP traffic (filtering based on the connections of the firewall) + Hits of pages in HTTP Servers (Apache, iPlanet, IIS, Netscape) + Percentage of erroneous packets in a Gateway + Connections established in a Remote Access Server (RAS) + Size of a file + Open sessions by a VPN server + MySQL Performance: Threads, queries, sessions... + Snort system state + Reported events by IDS (Snort) up to six levels of priority + Network load + Number of local Connections (TCP, UDP, Unix sockets) + Detected viruses by a Web Antivirus Gateway + ICMP latency time towards a host + Rate of average transference in a file transfer tool + Number of DNS requests attended by a server (including types) + Number of FTP sessions attended by a FTP server + (Generic) State of any active process / service in the system + (Generic) State of any countable parameter of the system + + + Global architecture + + Pandora 1.2 has changed many things from 1.1 version, but this + graph representing Pandora architecture is very useful to + understand in a single graph, all components. + + + + + Information gathering with Pandora agents + + Pandora agents are based on native languages in every platform: + scripts that can be written in any language. It's possible to + reproduce any agent in any programming language and can be + extended without difficulty the existing ones in order to cover + aspects not taken into account up to the moment. + + + These scripts are formed by modules that each one gathers a + "chunk" of information. Thus, every agent gathers several "chunks" + of information; this one is organized in a data set and stored in + a single file, called data file. + + + The process of transferring the data file from the agent to the + server is made regularly at a defined time interval in the agent + configuration file, pandora_agent.conf. It's possible to modify + that parameter in order to do not fill the database with non-relevant + information, either load the network or affect the system + performance. The default interval is 300 (seconds), which is + equivalent to five minutes. Minor values of 100 (seconds) are not + recommended since host performance could be affected, besides + loading excessively Database and the Operating System of Pandora + Server. Pandora is not a real time system; it's an applications + and systems general monitoring system in environments that are not + critical at real time. + + + Packets transfers are made via SSH, with DSA authentication + (although also RSA can be used). The process is completely safe + since neither any password nor unencrypted confidential + information is sent. Confidentiality, integrity and authentication + of the connections between the agent and the server are + ensured. In the Agents and Server Installation and Configuration + guides, the process of generation of keys to do the automatic SCP + transfer is detailed. + + + Also the transfer via FTP or any other file transfer system could + be made, although SSH has been chosen for security and + compatibility with most of the systems in the market. + + + Pandora Agents are thought to be executed from the agent from + which they gather information, although the agents can gather + information of accessible machines from the host where they are + installed. In this case those agents are called "Satellite + Agents". These Satellite Agents can use Telnet, SNMP or any other + commands to get the information. + + + We can also have a host with several agents: Some that gather + information from the accessible machines (acting as "satellite + agents") and the Standard Agent that monitors the host where it's + running. + + XML Data files + + The data file has the following syntax: + + hostname.serialnumber.data + + This is an XML file, and its name is the combination of the + hostname where the agent runs, a different serial number for every + data package and the extension .data that indicates that it's a + data file. + + + We also have a control file for every data file: + + hostname.serialnumber.checksum + + This file has .checksum extension and contains a MD5 hash of the + data file. This allows checking that the information has not been + changed before being processed. + + + The XML data file generated by every agent is the core of + Pandora. This file has the information gathered by the Agent. Its + easy structure allows that any user could create its own + developments to be processed in Pandora, or use the included ones. + An example of the information included into the data file below: + + + + SSH Daemon + generic_proc + 1 + + + FTP Daemon + generic_proc + 0 + + + DiskFree + generic_data + 5200000 + + + UsersConnected + generic_data_inc + 119 + 1 + 250 + Users currently connected + + + LastLogin + generic_data_string + slerena + + + ]]> + + + + Pandora servers + + With Pandora 1.2 version, you have three different types of servers: + + + + Pandora Data Server. This is a PERL + application that that processes the information sent by the + agents. The agents send the XML data file via SSH and the + server periodically verifies if it has new data files + waiting to be processed. You can setup different data + servers in different systems or in the same host (that will + be different virtual servers). + + + + + Pandora Network Server. This is a PERL + application that execute network tasks like sending pings, + TCP requests, SNMP requests and UDP request. When you assign + an agent to a server, you are assigning to a network server, + not a data server, so, this is very important that machines + running network servers have "network visibility" to hosts + assigned in network modules. + + + For example, if you create a module to make a ping check to + 192.168.1.1 and assign this agent/module to a server in a + 192.168.2.0/24 network without access to 192.168.1.0/24 + module will always report DOWN. + + + + + Pandora SNMP Server. This is a PERL + application that parse output from standard snmptradp (we + provide one binary for snmptrapd, but it is possible that + you need to replace it with a binary that runs better in your + system). This daemon receives SNMP traps, and Pandora SNMP + Server stores in database and fire alerts assigned in + Pandora SNMP Console. + + + + + + Data are extracted from the data file, identifying origin, type + and category. Once it's classified, the data are inserted into the + Database by the same Perl script. + + + Pandora Server can work in High Availability and/or Load + Balancing. In a very big architecture, several Pandora Servers can + be arranged simultaneously in order to be able to manage big volumes of + information distributed by geographical or functional zones. + + + Pandora Server is always running (as a daemon) and permanently + verifies if some element causes to fire an alarm. If so, it + executes the action defined in the alarm, as to send a SMS, an + email, even activates the execution of a SCRIPT or to send an HTTP + form. + + + We could have several simultaneous servers, one of them is the + Main Server or "Master Server " and the rest of servers are "Slave + Servers". The Master Server is the only one that verifies the + alarms if any agent goes down. The server which receives the data + file from the agent always fires the rest of alarms, defined in + the agents' modules. This is also important if this server changes + (due to configurations of high availability, load balancing or + clustering). + + + + Pandora console + + The Web Console is a web application that allows to see + graphical reports, state of every agent, also to access to the + information sent by the agent, to see every monitored parameter + and to see its evolution throughout the time, to form the + different nodes, groups and users of the system. It is the part + that interacts with the final user, and that will allows you to + administer the system. + + + The Web Console is written in PHP and no plug-in, Flash, Java or + ActiveX is needed to access the console, only a browser that + supports HTML and CSS (IE5+ or Mozilla 4+). Pandora Web Console can + run in several servers, the only thing you need is to be allow to + access Pandora Database, where Pandora stores all the information. + + + + Pandora database + + Pandora uses a SQL Database to store all the information. Pandora + maintains an asynchronous database with all the received data, + making a temporary cohesion of everything it is receives and + normalizing all the information from the different sources. Every + Agent data module generates an entry of information for every data + bundle, which implies that a real production system can have of + the order of ten million of data, or information atoms. + + + This information is managed automatically from Pandora, carrying + out a periodic and automatic maintenance of the database. This means + that there is no operator either manager required to run tasks as database + administration ones. This is possible thanks to a periodic purge of the past + information over a date (by default 90 days), as well as a data + which is older, by default, 30 days. + + + Compacting data + + Data stored by Pandora are useful to see evolutions through + the time, in order to: make statistics, generate reports and to do + capacity planning, as well as other statisticals tasks. + To do that it isn't necessary to have all the data, but it's + enough to have a representative sample, of smaller resolution, + enough to carry out the task that is needed. + + + With that philosophy the compaction system has been + constructed. For instance, If we have a sample of 9.000 elements, + distributed during 90 days, Pandora will take the data of + last month, which would be 3.000 elements and will compress it in 300. + In the graphs they will practically be equal, and it will be useful for the reports, statistics + and other tasks. This is made thanks to a interpolation in temporary + strips, in a totally automatic and periodic way, there is no user + or the administrator needed to do this. + + + + + + Pandora 1.2 new features + + Alert system. Now it is possible to define a + "minimun" and "maximum" limit to fire an alert, just to delete + "noisy" data that fires false positives. + + + Network Subsystem. Now it is possible to + monitor and analyze data using remote network tools, without using + agents, from the new Pandora Network Server component. All + management are made from Pandora Console, and now you will be able + to make ICMP checks (Ping), size network latency, get all types of + SNMP values (including scanning MIB), and makes TCP/UDP + connections to check ports, and test text applications, sending + texts and waiting for a specific response. + + + Module groups.Modules now could be grouped + using a new "module groups". + + + Network data refresh on demand. Could + be for each module or using a "global group refresh", forcing + Pandora Network Servers to refresh all network modules inside a + group. + + + Online contextual help, for Pandora WEB Console. + + + New Pandora server infraestructure. + + + New SNMP trap console to receive SNMP traps + and assigning alerts. + + + Internal messaging system, to notify events + to Pandora users. + + + Agent detail view autorefresh + + + New main agent group view + + + Improved database management system, that + allows to manage much more data. + + + + + About Pandora + + + Pandora is a project initiated and mainly developed by Sancho + Lerena, at present other people is working on it: Raul Mateos, + David Villanueva, Esteban Sanchez, Jose Navarro, Jonathan + Barajas and Manuel Arostegui. We want to thank many other people who help us + with translation, graphic design, bugs reporting and interesting + ideas. + + + Pandora is Free Software, and is published under GPL Licence. In + order to know the last features, go to the official web site of + the project in http://pandora.sourceforge.net. + + + diff --git a/pandora_doc/fr/pandora_migration.xml b/pandora_doc/fr/pandora_migration.xml new file mode 100644 index 0000000000..dfcaec4432 --- /dev/null +++ b/pandora_doc/fr/pandora_migration.xml @@ -0,0 +1,97 @@ + + + Migration depuis Pandora 1.1 + Migrer Pandora 1.1 vers Pandora 1.2 + + Vous aurez besoin du script pandoradb_1.1_to_1.2.sql fourni + avec la console Pandora version 1.2. Migrer de la version 1.1 + à la version 1.2 inclus: + + + + Le remplacement complet du code PHP de la console Pandora + (sauvegardez votre original pour remplacer les valeurs dans + /include/config.php pour votre login, mot de passe, nom d'hôte, + et les paramètres de la base de données. + + + + + Le remplacement complet du code PERL du serveur (sauvegardez + votre original pour remplacer les valeurs dans pandora_server.conf. + Le nouveau pandora_server.conf est situé dans le répertoire /conf. + Il est possible que vous aillez besoin de changer le répertoire de + réception des données et les paramètres dans les scripts du démon. + (lire la documentation de Pandora Serveur 1.2 avant d'essayer de le + démarrer). + + + + + Lisez la documentation au sujet des nouvelles fonctionnalités + de Pandora 1.2. Le processus de migration ne supprime aucune + donnée, aucun agent, ni configuration, ni données d'environnement, + mais veuillez tout de même, s'il vous plaît, lire _attentivement_ + toute la documentation sur le sujet avant d'essayer. + + + + + + Etapes de la Migration + + 0. Stoppez le service Serveur Pandora avant de changer quoi que ce soit + dans la base de données. Notez que vous ne perdrez aucune donnée pendant le + processus de migration puisque les données des agents seront stockées + dans le répertoire de réception des données. Déplacez ce répertoire vers + le nouveau répertoire de réception avant de démarrer le nouveau serveur, + et Pandora traitera les données sans perte. + + + 1. Faites un DUMP de tous les enregistrements tagente_datos vers un lieu sûr, par exemple: + + mysqldump --no-create-info -u root -p pandora \ + tagente_datos > /tmp/pandora.conv.tmp + + + + 2. Exécutez le script SQL de migration, par exemple: + + cat pandoradb_1.1_to_1.2.sql | mysql -u root -p -D pandora + + + NOTEZ que ce script va supprimer (drop) vos tables de données, NE RATEZ PAS + l'étape 1. + + + 3. Réinportez les données sauvées au cours de la première étape, par exemple: + + cat /tmp/pandora.conv.tmp | mysql -u root -p -D pandora + + + + 4. Supprimez les fichiers temporaires, par exemple: + + rm -Rf /tmp/pandora.conv.tmp + + + + Mise à jour du code + + Sauvegardez simplement vos installations Pandora Console et Pandora Serveur + et procédez comme pour une nouvelle installation de Pandora. Utilisez vos + paramètres de configuration existants pour cette nouvelle installation de + Pandora. La migration de la base de données est l'étape la plus critique et + doit être réalisée avant d'utiliser le nouveau code. + + + Etape finale + + Démarrez les nouveaux composants Pandora. Ouvrez la console Web et + vérifiez qu'un nouveau "Network Server" a été créé. Editez chaque + agent pour lui attribuer ce nouveau serveur. Cette étape peut être + automatisée en utilisant SQL, et dne doit être effectuée qu'une fois. + Cela n'a besoin d'être fait que si vous voulez utiliser Network Servers. + + + diff --git a/pandora_doc/fr/pandora_userguide.xml b/pandora_doc/fr/pandora_userguide.xml new file mode 100644 index 0000000000..41945ac3d7 --- /dev/null +++ b/pandora_doc/fr/pandora_userguide.xml @@ -0,0 +1,91 @@ + + +Pandora FMS"> + + + + + + + + + + + +]> + + + + &pandora; &pandora_version; + Guide d'utilisation + + + 2007 + + Artica Soluciones Tecnologicas S.L, Sancho Lerena, Esteban + Sanchez, David Villanueva, Raul Mateos, Manuel Arostegui and others. + Tranquil IT Systems, Denis Chupau. + + + 01/02/2007 + &pandora_version; + First Edition(&pandora_version;) + + November 21st, 2006 + + manuel d'utilisation Pandora + + + + Il est permis de copier, distribuer et/ou modifier ce + document dans les termes de la GNU Free Documentation + License, Version 1.1 ou toute autre version postérieure + publiée par la Free Software Foundation. Une copie de cette + licence est incluse dans la section intituléeGNU Free Documentation + License. + + + + + 1.2 + 24 November 2006 + Submitted. + + + 1.1 + 10 October 2006 + Submitted. + + + 1.0 + 11 September 2006 + Submitted. + + + 0.1 + 11 September 2006 + First draft for review. + + + 0.1.1 + 5 february 2007 + French translation. + + + + + &include_pandora_chapter1; + &include_pandora_chapter2; + &include_pandora_chapter3; + &include_pandora_chapter4; + &include_pandora_chapter5; + &include_pandora_chapter6; + &include_pandora_chapter7; + &include_pandora_chapter8; + &include_pandora_chapter9; + &include_fdl; + &include_gpl; + diff --git a/pandora_doc/fr/schemas.xml b/pandora_doc/fr/schemas.xml new file mode 100644 index 0000000000..0455da351d --- /dev/null +++ b/pandora_doc/fr/schemas.xml @@ -0,0 +1,14 @@ + + + + + + + + + + + + + + \ No newline at end of file