On 6/3/11 22:43 CDT, Justin Krejci wrote:

Getting 2 less prefixes from 2607:FE10:FFFF::2 than from 2607:FE10:FFFF::1 for CDW/Brebee.

*> 2607:FEE0::/32 2607:FE10:FFFF::26 0 3599 i *> 2607:FEE0:8000::/40 2607:FE10:FFFF::26 0 3599 ?

Looks like the /40 is just a subset of the /32 prefix

IPv4 prefix counts are identical on the route servers.

There is no contact on the MICE Participants page for them. Anyone have an idea or a good contact for them?

Actually CDW/Berbee AS 3599 is only peering with the one of route servers, for IPv4 and IPv6. The reason that you see the same number of routes in IPv4 is that Genesis Wireless/RevNetData AS 30032 isn't properly filtering their BGP announcements and reflecting them back to the Route Server. Since the route servers AS isn't in the announcement, normal BGP loop detection doesn't block it. This is one of the dangers of running route server mode. So, 1. CDW/Berbee AS 3599 and Compudyne AS 47096 should both peer with both route servers. 2. Genesis Wireless/RevNetData AS 30032 should filter their route announcements with a prefix-list. Or, should set a BGP community on the routes they learn from the MICE route servers or any direct peers and not announce any routes with that BGP Community back to MICE. Since they don't have to many prefixes and are not serving other ASes, I would suggest the prefix-list option would be the easiest. 3. The route servers should iBGP peer with each other. This would prevent future similar problems. And, would be handy if Peer A looses connectivity to Route Server 1 and Peer B looses connectivity to Route Server 2, then the two peers can still talk to each other. Yes, that would be a bizarre failure mode, but weird sh!% happens. :) -------- An edited "show bgp ipv4 unicast regexp _3599_" Network Next Hop Metric LocPrf Weight Path * 64.73.0.0/17 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 64.73.112.0/20 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 64.73.128.0/18 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 91.220.15.0/24 69.147.218.26 180 0 30032 3599 51818 i *> 69.147.218.26 180 0 3599 51818 i * 173.240.64.0/20 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 192.135.80.0 69.147.218.26 180 0 30032 3599 ? *> 69.147.218.26 180 0 3599 ? * 199.36.37.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 199.36.47.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 204.17.145.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 204.86.231.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 205.173.176.0/21 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 205.173.180.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 205.173.181.0 69.147.218.26 180 0 30032 3599 i *> 69.147.218.26 180 0 3599 i * 207.126.176.0/20 69.147.218.26 180 0 30032 3599 46814 46814 i *> 69.147.218.26 180 0 3599 46814 46814 i ------- An edited "show bgp ipv4 unicast regexp _30032_" Network Next Hop Metric LocPrf Weight Path * 63.171.43.0/24 69.147.218.103 180 0 30032 i *> 69.147.218.103 180 0 30032 i * 64.73.0.0/17 69.147.218.26 180 0 30032 3599 i * 64.73.112.0/20 69.147.218.26 180 0 30032 3599 i * 64.73.128.0/18 69.147.218.26 180 0 30032 3599 i * 65.165.20.0/23 69.147.218.103 180 0 30032 i *> 69.147.218.103 180 0 30032 i r 69.147.218.0/24 69.147.218.103 180 0 30032 ? r> 69.147.218.103 180 0 30032 ? * 74.117.240.0/21 69.147.218.103 180 0 30032 i *> 69.147.218.103 180 0 30032 i * 91.220.15.0/24 69.147.218.26 180 0 30032 3599 51818 i * 173.240.64.0/20 69.147.218.26 180 0 30032 3599 i * 192.135.80.0 69.147.218.26 180 0 30032 3599 ? * 199.21.240.0/21 69.147.218.101 180 0 30032 47096 i * 199.36.37.0 69.147.218.26 180 0 30032 3599 i * 199.36.47.0 69.147.218.26 180 0 30032 3599 i * 204.17.145.0 69.147.218.26 180 0 30032 3599 i * 204.86.231.0 69.147.218.26 180 0 30032 3599 i * 204.120.16.0/20 69.147.218.103 180 0 30032 i *> 69.147.218.103 180 0 30032 i * 205.173.176.0/21 69.147.218.26 180 0 30032 3599 i * 205.173.180.0 69.147.218.26 180 0 30032 3599 i * 205.173.181.0 69.147.218.26 180 0 30032 3599 i * 206.51.193.0 69.147.218.101 180 0 30032 47096 i * 207.126.176.0/20 69.147.218.26 180 0 30032 3599 46814 46814 i * 216.70.9.0 69.147.218.101 180 0 30032 47096 i * 216.70.13.0 69.147.218.101 180 0 30032 47096 i * 216.70.17.0 69.147.218.101 180 0 30032 47096 i * 216.70.22.0 69.147.218.101 180 0 30032 47096 i * 216.70.26.0 69.147.218.101 180 0 30032 47096 i * 216.70.27.0 69.147.218.101 180 0 30032 47096 i * 216.70.28.0 69.147.218.101 180 0 30032 47096 i * 216.70.29.0 69.147.218.101 180 0 30032 47096 i -- =============================================== David Farmer Email:farmer@umn.edu Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 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