<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"Préformaté HTML Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Texte de bulles Car";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Arial","sans-serif";
color:windowtext;
font-weight:normal;
font-style:normal;}
span.PrformatHTMLCar
{mso-style-name:"Préformaté HTML Car";
mso-style-priority:99;
mso-style-link:"Préformaté HTML";
font-family:Consolas;
mso-fareast-language:EN-US;}
span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Arial","sans-serif";
color:black;
font-weight:normal;
font-style:normal;}
span.TextedebullesCar
{mso-style-name:"Texte de bulles Car";
mso-style-priority:99;
mso-style-link:"Texte de bulles";
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="FR" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Thanks for the answer, I’m happily surprised to see that we’re still far from xymon’s limit.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I made more checks today, and realized that some tools that I thought were sending their statuses over a few seconds actually send batches of ~200
statuses in 200ms. These burst are definitely far higher than 200msg/s… I had no idea that our traffic was so irregular.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">I guess that, as you pointed out, the next step is to setup xymonproxy and have the few tools that generate so much traffic use them. As the only thing
they know about xymon is the status command, that should be quite easy to set up.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Regarding the history files, it is not an issue as far as performance is concerned, but it definitely is a pain to manage. Moving to database solution
has been in our todo list for some time now.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black;mso-fareast-language:FR">Francois Maillard</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black;mso-fareast-language:FR">
<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:35.4pt"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR">De :</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif";mso-fareast-language:FR"> Clark, Sean
[mailto:sean.clark@twcable.com] <br>
<b>Envoyé :</b> mercredi 17 décembre 2014 19:46<br>
<b>À :</b> MAILLARD Francois Ext DTSI/DSI; xymon@xymon.com<br>
<b>Objet :</b> Re: [Xymon] xymon on a large architecture<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal" style="margin-left:35.4pt"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">So I have a setup where, in total, I monitor about 300,000 hosts.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">It's regionalized though, with the largest site having roughly 34,000 hosts<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">The xymon daemon runs on a VM, with 16 GB of Ram, and 4x2.5 Ghz xeon processors. The virtual NIC is a 1000Mb <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">It currently handles 481 msgs/sec (the hosts.cfg is 1.2 Mb)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">Here are some ideas:<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">(1) Obviously split pollers out into separate machines<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">(2) Change the history daemon (Henrick as some sample daemons in the source code) - I changed it to write stachg and clichg and such are written out to mysql instead
of files, and the textblog is compressed. This helped with managing history<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">(3) Use JC Cleaver's patches <a href="http://terabithia.org/rpms/xymon/">http://terabithia.org/rpms/xymon/</a> -- he has several memory leak fixes, tuning optimizations.
I would just say that if you use clientupdate, you will have to patch his things a little bit<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">(4) An interesting thing you can do, if you have the means via a load balancer is --><o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"> (a) I have 10 pollers for this instance. All of them run xymonproxy on localhost (stuff they poll reports to localhost and gets forwarded up)<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"> (b) Using a load balancer for they xymon IP address, it inspects the first 12 characters of a xymon message – if it's something that can be combo'd in proxy it passes
to a poller in the pool, otherwise, it sends it to the real xymon IP<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">(5) JC has some nanomsg options for channels, and myself, I use AMQP for channels to communicate data outbound. Both of these help if you use xymondata outside of the
stock app<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black">For your setup, rather than running more xymond's on different ports, setup xymonproxy's on different machines, and point your clients to them. Then you won't have to
migrate your history files or anything else. But I would look at changing your history setup, as several million files gets very unwieldy to manage, but millions of rows in databases are much easer to do.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="margin-left:35.4pt"><b><span style="color:black">From:
</span></b><span style="color:black">"<a href="mailto:fmaillard.ext@orange.com">fmaillard.ext@orange.com</a>" <<a href="mailto:fmaillard.ext@orange.com">fmaillard.ext@orange.com</a>><br>
<b>Date: </b>Wednesday, December 17, 2014 at 11:04 AM<br>
<b>To: </b>"<a href="mailto:xymon@xymon.com">xymon@xymon.com</a>" <<a href="mailto:xymon@xymon.com">xymon@xymon.com</a>><br>
<b>Subject: </b>[Xymon] xymon on a large architecture<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black"><o:p> </o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Hello,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">We’re running a quite large xymon setup, and have been dealing with performance issue for quite a while. Here are some stats
to give an idea about the setup:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- We have 2 xymon servers per datacenter, on 3 datacenter (all messages are sent to both servers for a given site)</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- Each xymon server receives on average between 200msg/s and 250msg/s. We’re getting peaks at 400msg/sec.</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">- Each site hosts about 3000 hosts / 30 000 services</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">We’ve been suspecting for a long time that we might be losing messages… and I think I finally tracked it down to xymond
not fetching the messages quickly enough so that the kernel’s buffer fill up and messages get discarded (by the kernel). On one of our servers, even though I have already increased net.ipv4.tcp_rmem and net.ipv4.tcp_wmem I got the following output from “netstat
-s”:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">148909 packets pruned from receive queue because of socket buffer overrun</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">4453143 packets collapsed in receive queue due to low socket buffer</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">And here I come to the question I’m having:</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">1/ Is 250msg/s too much for a single xymond instance? Is anyone running instances with a lot more traffic than that?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">2/ I’m starting to look into running several instances of xymond on the same machine, by binding them to different ports.
Another option is to set up new machines, but that would mean migrating history files (several million files), sorting out the firewalling issues (our xymon interfaces are deeply connected to our information system) so I’d rather like avoiding this option.
Are there any guidelines on how to do this?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">3/ Are there any settings and best practice that could improve performance? For instance, should we move to a massive use
of combo statuses in order to lessen the number of messages received?</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Best regards,</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Francois Maillard</span></b><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span lang="EN-US" style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black"> </span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Pilote des plateformes Supervision, DNS & FTP - Sysadmin Infrastructure</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">Altran Méditerranée</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:black">pour Orange/OF/DTSI/DSI/DFY/HBX<br>
</span><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">Sophia Antipolis</span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.0pt;font-family:"Helvetica","sans-serif";color:black">tél. 04 97 12 87 53<br>
<a href="mailto:fmaillard.ext@orange.com"><span style="color:#FF6600">fmaillard.ext@orange.com</span></a></span><span style="color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="color:black"> <o:p></o:p></span></p>
<pre style="margin-left:35.4pt"><span style="color:black">_________________________________________________________________________________________________________________________<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black"><o:p> </o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black"><o:p> </o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">This message and its attachments may contain confidential or privileged information that may be protected by law;<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">they should not be distributed, used or copied without authorisation.<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">If you have received this email in error, please notify the sender and delete this message and its attachments.<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.<o:p></o:p></span></pre>
<pre style="margin-left:35.4pt"><span style="color:black">Thank you.<o:p></o:p></span></pre>
</div>
</div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:10.5pt;color:black;mso-fareast-language:FR"><o:p> </o:p></span></p>
<div class="MsoNormal" align="center" style="margin-left:35.4pt;text-align:center">
<span style="font-size:10.5pt;color:black;mso-fareast-language:FR">
<hr size="2" width="100%" align="center">
</span></div>
<p class="MsoNormal" style="margin-left:35.4pt"><span style="font-size:7.5pt;font-family:"Arial","sans-serif";color:gray;mso-fareast-language:FR">This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged,
confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination,
distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original
and any copy of this E-mail and any printout.</span><span style="font-size:10.5pt;color:black;mso-fareast-language:FR"><o:p></o:p></span></p>
</div>
<PRE>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</PRE></body>
</html>