Guten Tag Paolo Lucente, am Donnerstag, 3. Mai 2007 um 00:58 schrieben Sie:
> Hi Daniel, > Which network device are you getting the sFlow datagrams from? > Any chance i can have a look to these samples? If yes, can you > please post me privately some full-datagrams captured in > libpcap/tcpdump format? do u remeber this issue? Foundry told us that there isnt any problem with sFlow version 5 and the problem must be in your tool. Foundry exactly wrotes: Thanks for your email, the escalation engineer that I discussed this with was not aware of any problems and has not heard of this problem from other customers either. It seems unusual that you are reporting this on two completely different families of switches so it seems likely that the sFlow collector is the problem. I know that you offered to put us in contact with the developer of the sFlow collector, but from my perspective it would be more helpful if the developer would just look at the traces that you captured and identify what the specific problem is with the format. It would be particularly helpful if they could identify some packets in the trace with format errors and give a detailed explanation of problem with the format. I could then escalate this to engineering and ask them to verify whether our switch is conforming to the correct standard. Are u able to help me in this case? You said that SNMontools and pmacct see the same error :( greetz daniel _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
