This morning at approximately 1:30 our peering session with HE reset, I assume for some kind of normal maintenance on their end. This triggered a weird issue on our end. Because of some crufty route policy we were preferring the routes we learned from the MICE route server over the routes we learned directly from HE. And for some reason the routes we were learning from the route server had a different link-local address associated with them than the routes we learned directly. And this address no longer seems to be valid, and this caused traffic to be black holed. From below FE80::224:38FF:FEA7:EA03 - address on routes learned from MICE RS FE80::224:38FF:FEA7:EA36 - address on routes direct from HE I changed my route policy to ignore the routes from HE through the MICE Route Server and things are working again. I'm not sure what changed and why the routes from the MICE Route server have an bogus link-local address. But I though I would warn you all. MTC-GR-01#sh ipv6 ro 2001:470:0:1C2::1 Routing entry for 2001:470::/32 Known via "bgp 57", distance 20, metric 1, type external Route count is 1/1, share count 0 Routing paths: FE80::224:38FF:FEA7:EA03, Vlan300 MPLS label: nolabel MPLS Flags: NSF Last updated 01:43:15 ago MTC-GR-01#sh ipv6 ro 2600:0:2:1239:144:232:26:11 Routing entry for 2600::/29 Known via "bgp 57", distance 20, metric 0, type external Route count is 1/1, share count 0 Routing paths: FE80::224:38FF:FEA7:EA36, Vlan300 MPLS label: nolabel MPLS Flags: NSF Last updated 01:43:52 ago -- ================================================ David Farmer Email: farmer@umn.edu Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 1-612-626-0815 Minneapolis, MN 55414-3029 Cell: 1-612-812-9952 ================================================ ######################################################################## To unsubscribe from the MICE-DISCUSS list, click the following link: http://lists.iphouse.net/cgi-bin/wa?SUBED1=MICE-DISCUSS&A=1