CIX-ANS path fully CIDR capable
Hello, With the completion of the CIX-West router upgrade this Tuesday morning, the CIX is now speaking BGP4 with ANS (enss187.) Since enss187 is also speaking BGP4 with the ANSNET backbone, this entire path is now CIDR capable. At the moment, enss187 is hearing a number of aggregate routes from the CIX, but none from the ANSNET backbone. Those CIX-member regionals using ANS CO+RE as transit to the CIX may now pass aggregates on to the ANSNET backbone, and thereon to the CIX through enss187, if they require this. I do not see that any of these regionals, which include NEARNet, SURANet, WestNet and NorthWestNet, have begun announcing aggregates to ANSNET yet. In case this is of any importance, the current set of aggregates enss187 is hearing from the CIX numbers 31 routes, and is as follows: Network Next Hop Metric LocPrf Weight Path *> 192.36.32.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 192.121.64.0/23 149.20.5.1 0 1280 701 1729 ? *> 192.135.240.0/21 149.20.5.1 0 1280 200 109 i *> 192.150.56.0/21 149.20.5.1 0 1280 701 1729 ? *> 192.150.64.0/20 149.20.5.1 0 1280 701 1729 ? *> 192.150.80.0/21 149.20.5.1 0 1280 701 1729 ? *> 192.165.148.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 192.212.0.0/16 149.20.5.1 0 1280 1740 i *> 192.216.0.0/16 149.20.5.1 0 1280 200 i *> 192.244.176.0/20 149.20.5.1 0 1280 701 2509 2497 i *> 193.10.16.0/21 149.20.5.1 0 1280 701 1729 2865 i *> 193.10.24.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 193.44.0.0/16 149.20.5.1 0 1280 701 1729 ? *> 193.44.76.0/22 149.20.5.1 0 1280 701 1729 2865 i *> 193.128.40.0/21 149.20.5.1 0 1280 701 1849 i *> 198.30.0.0/16 149.20.5.1 0 1280 1239 600 i *> 198.31.0.0/16 149.20.5.1 0 1280 200 i *> 198.84.4.0/22 149.20.5.1 0 1280 701 ? *> 198.92.0.0/17 149.20.5.1 0 1280 1740 109 i *> 198.93.160.0/19 149.20.5.1 0 1280 1740 109 i *> 198.234.0.0/16 149.20.5.1 0 1280 1239 600 i *> 199.0.0.0/16 149.20.5.1 0 1280 1239 i *> 199.1.0.0/16 149.20.5.1 0 1280 1239 i *> 199.2.0.0/16 149.20.5.1 0 1280 1239 i *> 199.3.0.0/16 149.20.5.1 0 1280 1239 i *> 199.18.0.0/16 149.20.5.1 0 1280 1239 600 i *> 199.108.0.0/16 149.20.5.1 0 1280 1740 i *> 199.182.0.0/16 149.20.5.1 0 1280 2551 i *> 202.24.208.0/20 149.20.5.1 0 1280 701 2509 2497 i *> 202.26.0.0/18 149.20.5.1 0 1280 701 2509 2497 i *> 202.32.0.0/16 149.20.5.1 0 1280 701 2509 2497 i I checked this yesterday as well, at which time the following additional 38 aggregates were being learned from CIX-West. I'm not sure where they disappeared to... Network Next Hop Metric LocPrf Weight Path *> 192.64.100.0/22 149.20.5.1 0 1280 701 286 1891 ? *> 192.78.186.0/23 149.20.5.1 0 1280 701 286 1891 ? *> 192.92.130.0/23 149.20.5.1 0 1280 701 286 1891 i *> 192.122.216.0/23 149.20.5.1 0 1280 701 286 2110 i *> 192.122.220.0/22 149.20.5.1 0 1280 701 286 2110 i *> 192.250.24.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.67.128.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.71.32.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.71.104.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.71.160.0/21 149.20.5.1 0 1280 701 286 2116 i *> 193.72.0.0/16 149.20.5.1 0 1280 701 286 1836 ? *> 193.74.160.0/20 149.20.5.1 0 1280 701 286 1891 ? *> 193.74.176.0/23 149.20.5.1 0 1280 701 286 1891 ? *> 193.74.192.0/22 149.20.5.1 0 1280 701 286 1891 i *> 193.74.200.0/23 149.20.5.1 0 1280 701 286 1891 i *> 193.74.232.0/21 149.20.5.1 0 1280 701 286 1891 i *> 193.74.240.0/20 149.20.5.1 0 1280 701 286 1891 ? *> 193.78.32.0/21 149.20.5.1 0 1280 701 286 1890 i *> 193.78.72.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.78.104.0/22 149.20.5.1 0 1280 701 286 1890 i *> 193.78.120.0/23 149.20.5.1 0 1280 701 286 1890 i *> 193.78.120.0/21 149.20.5.1 0 1280 701 286 1890 i *> 193.80.224.0/22 149.20.5.1 0 1280 701 286 1901 i *> 193.85.0.0/21 149.20.5.1 0 1280 701 286 2819 i *> 193.85.8.0/23 149.20.5.1 0 1280 701 286 2819 i *> 193.85.80.0/23 149.20.5.1 0 1280 701 286 2819 i *> 193.85.104.0/21 149.20.5.1 0 1280 701 286 2819 i *> 193.85.112.0/20 149.20.5.1 0 1280 701 286 2819 i *> 193.85.128.0/20 149.20.5.1 0 1280 701 286 2819 i *> 193.120.16.0/20 149.20.5.1 0 1280 701 286 2110 i *> 193.120.32.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.120.208.0/22 149.20.5.1 0 1280 701 286 2110 i *> 193.120.212.0/22 149.20.5.1 0 1280 701 286 2110 i *> 193.120.216.0/23 149.20.5.1 0 1280 701 286 2110 i *> 193.120.232.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.120.240.0/21 149.20.5.1 0 1280 701 286 2110 i *> 193.242.80.0/21 149.20.5.1 0 1280 701 286 i *> 199.0.192.0/20 149.20.5.1 0 1280 1239 ? - John
From: "John J. Hedderman (ANS Install Eng)" <jjh@ans.net> Subject: CIX-ANS path fully CIDR capable Date: Thu, 7 Apr 94 10:10:13 EDT
At the moment, enss187 is hearing a number of aggregate routes from the CIX, but none from the ANSNET backbone. Those CIX-member regionals using ANS CO+RE as transit to the CIX may now pass aggregates on to the ANSNET backbone, and thereon to the CIX through enss187, if they require this. I do not see that any of these regionals, which include NEARNet, SURANet, WestNet and NorthWestNet, have begun announcing aggregates to ANSNET yet.
This is very good news! I am trying to get a NACR in for Noon for the block 192.32/16. This will only save about 53 routes currently, but if this is determined a success we will add more aggregates on Tuesday. (I need to double check on the AUP stuff, and next hop; since our assigned blocks try to, but do not necessarily follow AUP boundaries.) I don't think it is suprising that ANSNET has not heard aggregates. We certainly were not willing to send them while you couldn't pass them to the CIX, and blackhole our customers traffic. Tuesday was when this was corrected, and Friday is the next configuration window after that-- you should see some aggregates tomorrow. Perhaps since gated does dynamic configs, ANS/MERIT could offer special windows for block additions until the ball gets rolling. Sean
participants (2)
-
John J. Hedderman (ANS Install Eng) -
L. Sean Kennedy