<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class=""><br class=""></div><div class=""><div style="font-family: arial; font-size: 14px;" class=""><div fr-original-style="" style="box-sizing: border-box;" class="">The biggest problem from our point of view is the migration of members. As soon as the first member will change their setting to use new IPs (RouteServers, Collectors, etc) they will not be able to exchange traffic with other members and the traffic of this member will be gone from IXP till the rest will do changes. Otherwise, they must keep sessions with old RouteServers till all members will migrate to the new IPs.</div></div></div></blockquote><br class=""></div><div>Run with both IP ranges on the same VLAN for a set period of time. We had to do a similar migration and this is how we did it. Be very clear on the date the route-servers will change and give lots of time and notices.</div><div><br class=""></div><br class=""></body></html>