---------- Forwarded message ---------- From: Nathan Beard <nbeard@stellarllc.net> Date: Wed, Jun 1, 2016 at 8:25 AM Subject: Route Server #1 - IPv6 To: peering@micemn.net Is there a particular reason why the IPv6 address for route server #1 is no longer reachable following the upgrades that were completed on the night of the 22nd? My IPv6 peering session to the first route server has been stuck in 'Active' state since right around that time and the IPv6 address is also not directly reachable (while route server #2 works fine): // BGP state for route server #1 session // 2001:504:27::d1af:0:1 0 53679 1675496 328107 0 0 0 1w2d Active // Ping to route server #1 // RP/0/RSP0/CPU0:STELLAR-511-ASR9006#ping ipv6 2001:504:27::d1af:0:1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:504:27::d1af:0:1, timeout is 2 seconds: ..... Success rate is 0 percent (0/5) // Ping to route server #2 // RP/0/RSP0/CPU0:STELLAR-511-ASR9006#ping ipv6 2001:504:27::d1af:0:2 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:504:27::d1af:0:2, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms Please let me know when you have an update. Thanks! -- Nathan Beard Network Engineer nbeard@stellarllc.net (218) 820-7636 -- Jay Hanke CTO Neutral Path Communications 3 Civic Center Plaza, Suite 204 Mankato, MN 56001 (507) 327-2398 mobile jayhanke@neutralpath.net www.neutralpath.net