<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>If you cannot resolve the underlying cause and these are filling up your logs, you can use:</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>no logging buffered warnings</div></blockquote><div><br></div><div>However, keep in mind that does knock out some other messages that you may not want to sacrifice logging. In one of our instances, the tradeoff was worth it to implement the command. </div><div><br></div><div>Regards,</div><div>Mike</div><div><br></div><br><div><div>On Oct 13, 2014, at 4:34 AM, Clement Cavadore <<a href="mailto:clement@cavadore.net">clement@cavadore.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hi,<br><br>After upgrading to 5.6 (CER devices), we keep having the following<br>messages:<br><br>Oct 13 12:46:03:W:IP/ARP: IP address 194.68.129.xxx MAC movement detected, changed from MAC 0022.83d4.1ff0 / port 1/3 to MAC 0022.8354.1ff0 / port 1/3<br>Oct 13 12:46:02:W:IP/ARP: IP address 194.68.129.xxx MAC movement detected, changed from MAC 0022.8354.1ff0 / port 1/3 to MAC 0022.83d4.1ff0 / port 1/3<br>Oct 13 12:44:13:W:IP/ARP: IP address 194.68.129.xxx MAC movement detected, changed from MAC 0022.83d4.1ff0 / port 1/3 to MAC 0022.8354.1ff0 / port 1/3<br>Oct 13 12:44:09:W:IP/ARP: IP address 194.68.129.xxx MAC movement detected, changed from MAC 0022.8354.1ff0 / port 1/3 to MAC 0022.83d4.1ff0 / port 1/3<br>Oct 13 12:40:14:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:40:14:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br>Oct 13 12:37:40:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:37:40:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br>Oct 13 12:16:50:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:16:50:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br>Oct 13 12:12:02:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:12:02:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br>Oct 13 12:11:44:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:11:44:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br>Oct 13 12:10:16:W:IP/ARP: IP address 80.249.208.zzz MAC movement detected, changed from MAC 0025.900a.0c17 / port 1/38 to MAC 000e.d6b5.7c00 / port 1/38<br>Oct 13 12:09:33:W:IP/ARP: IP address 80.249.208.zzz MAC movement detected, changed from MAC 000e.d6b5.7c00 / port 1/38 to MAC 0025.900a.0c17 / port 1/38<br>Oct 13 12:06:18:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 009b.0de4.41c0 / port 1/3 to MAC 001b.0de4.41c0 / port 1/3<br>Oct 13 12:06:18:W:IP/ARP: IP address 194.68.129.yyy MAC movement detected, changed from MAC 001b.0de4.41c0 / port 1/3 to MAC 009b.0de4.41c0 / port 1/3<br><br>I am pretty sure that the MACs are not really changing, as it is on IXPs<br>where strict mac filtering is enabled. This happens on various devices,<br>from various networks I manage. There is no operational problem, apart<br>from fulfilling my log buffer<br><br>Anyone aware of any kind of bug with that ?<br><br>Thanks,<br><br>-- <br>Clément Cavadore<br><br><br>_______________________________________________<br>foundry-nsp mailing list<br><a href="mailto:foundry-nsp@puck.nether.net">foundry-nsp@puck.nether.net</a><br>http://puck.nether.net/mailman/listinfo/foundry-nsp</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>