<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>HI Clement, </div><div><br><blockquote type="cite">Sure, but in an IXP context (especially AMS-IX :)), that would also<br>remove the warning limit for the No. of prefix received from BGP<br>peers... So I think I'd prefer having those, but still seeing the<br>warning messages :)<br></blockquote></div><div><br></div><div>Caveat emptor. We chose not to implement it on other devices for different reasons. It knocks out a range of warnings. </div><div><br></div><div><blockquote type="cite">Hopefully someone else can open a ticket, then. I know that HE has Brocade's ear.<br></blockquote></div><div><br></div><div>We didn't notice the warnings being issued incorrectly, we just weren’t able to resolve them in the affected devices environment. Since we didn’t see a situation where the warnings were actually in error, we are unable to open a bug report. We did notice that they began when we moved up to 5.6. We mentioned it to Brocade and they said it was a new and intentional warning. </div><div><br></div><div>I also asked them for the ability to silence those specific warnings but were presented with the aforementioned solution. I know some Brocade folks are on the list too, so they may be able to push a feature req for more fine grained logging filters. I’ll have to check if we actually put that in officially or just lamented to our rep. :) </div><div><br></div><div>Regards,</div><div>Mike</div><br><div><div>On Oct 13, 2014, at 10:19 AM, Clement Cavadore <<a href="mailto:clement@cavadore.net">clement@cavadore.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi Mike,<br><br>Sure, but in an IXP context (especially AMS-IX :)), that would also<br>remove the warning limit for the No. of prefix received from BGP<br>peers... So I think I'd prefer having those, but still seeing the<br>warning messages :)<br><br>Btw, I hope that it's a known bug !<br><br>Regards,<br><br>-- <br>Clément<br><br>On Mon, 2014-10-13 at 10:12 -0700, Mike Tindle wrote:<br><blockquote type="cite">If you cannot resolve the underlying cause and these are filling up<br>your logs, you can use:<br><br><br> no logging buffered warnings<br><br><br>However, keep in mind that does knock out some other messages that you<br>may not want to sacrifice logging. In one of our instances, the<br>tradeoff was worth it to implement the command. <br><br><br>Regards,<br>Mike<br><br><br><br></blockquote></blockquote></div><br><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">*----------- H U R R I C A N E - E L E C T R I C ---------->><br>| Mike Tindle | Senior Network Engineer | <a href="mailto:mtindle@he.net">mtindle@he.net</a><br>| ASN 6939 | <a href="http://www.he.net">http://www.he.net</a> | 510-580-4126<br>*--------------------------------------------------->></div></span></div></span>
</div>
<br></body></html>