September 2005 - Test - lists.nanog.org

Weekly Routing Table Report
by Routing Table Analysis 16 Sep '05

16 Sep '05

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to bgp-stats(a)lists.apnic.net If you have any comments please contact Philip Smith <pfs(a)cisco.com>. Routing Table Report 04:00 +10GMT Sat 17 Sep, 2005 Analysis Summary ---------------- BGP routing table entries examined: 170386 Prefixes after maximum aggregation: 97174 Unique aggregates announced to Internet: 81546 Total ASes present in the Internet Routing Table: 20513 Origin-only ASes present in the Internet Routing Table: 17842 Origin ASes announcing only one prefix: 8441 Transit ASes present in the Internet Routing Table: 2671 Transit-only ASes present in the Internet Routing Table: 71 Average AS path length visible in the Internet Routing Table: 4.5 Max AS path length visible: 26 Prefixes from unregistered ASNs in the Routing Table: 26 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 12 Number of addresses announced to Internet: 1424234304 Equivalent to 84 /8s, 228 /16s and 23 /24s Percentage of available address space announced: 38.4 Percentage of allocated address space announced: 57.9 Percentage of available address space allocated: 66.4 Total number of prefixes smaller than registry allocations: 81067 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 35251 Total APNIC prefixes after maximum aggregation: 15514 Prefixes being announced from the APNIC address blocks: 33121 Unique aggregates announced from the APNIC address blocks: 15669 APNIC Region origin ASes present in the Internet Routing Table: 2360 APNIC Region origin ASes announcing only one prefix: 696 APNIC Region transit ASes present in the Internet Routing Table: 360 Average APNIC Region AS path length visible: 4.5 Max APNIC Region AS path length visible: 18 Number of APNIC addresses announced to Internet: 199764992 Equivalent to 11 /8s, 232 /16s and 44 /24s Percentage of available APNIC address space announced: 74.1 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 124/7, 126/8, 202/7, 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 90936 Total ARIN prefixes after maximum aggregation: 55234 Prefixes being announced from the ARIN address blocks: 71100 Unique aggregates announced from the ARIN address blocks: 26179 ARIN Region origin ASes present in the Internet Routing Table: 10223 ARIN Region origin ASes announcing only one prefix: 3772 ARIN Region transit ASes present in the Internet Routing Table: 955 Average ARIN Region AS path length visible: 4.3 Max ARIN Region AS path length visible: 16 Number of ARIN addresses announced to Internet: 268101888 Equivalent to 15 /8s, 250 /16s and 233 /24s Percentage of available ARIN address space announced: 66.6 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863 ARIN Address Blocks 24/8, 63/8, 64/6, 68/7, 70/6, 74/7, 76/8, 198/7, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 32911 Total RIPE prefixes after maximum aggregation: 22417 Prefixes being announced from the RIPE address blocks: 29968 Unique aggregates announced from the RIPE address blocks: 20184 RIPE Region origin ASes present in the Internet Routing Table: 7092 RIPE Region origin ASes announcing only one prefix: 3732 RIPE Region transit ASes present in the Internet Routing Table: 1184 Average RIPE Region AS path length visible: 5.1 Max RIPE Region AS path length visible: 26 Number of RIPE addresses announced to Internet: 217836160 Equivalent to 12 /8s, 251 /16s and 234 /24s Percentage of available RIPE address space announced: 64.9 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 RIPE Address Blocks 62/8, 80/5, 88/6, 188/8, 193/8, 194/7, 212/7 and 217/8 LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 9520 Total LACNIC prefixes after maximum aggregation: 3197 Prefixes being announced from the LACNIC address blocks: 7876 Unique aggregates announced from the LACNIC address blocks: 4588 LACNIC Region origin ASes present in the Internet Routing Table: 636 LACNIC Region origin ASes announcing only one prefix: 199 LACNIC Region transit ASes present in the Internet Routing Table: 121 Average LACNIC Region AS path length visible: 5.2 Max LACNIC Region AS path length visible: 25 Number of LACNIC addresses announced to Internet: 22039808 Equivalent to 1 /8s, 80 /16s and 77 /24s Percentage of available LACNIC address space announced: 32.8 LACNIC AS Blocks 26592-26623, 27648-28671, plus ERX transfers LACNIC Address Blocks 189/8, 190/8, 200/7 AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 1738 Total AfriNIC prefixes after maximum aggregation: 812 Prefixes being announced from the AfriNIC address blocks: 1056 Unique aggregates announced from the AfriNIC address blocks: 799 AfriNIC Region origin ASes present in the Internet Routing Table: 139 AfriNIC Region origin ASes announcing only one prefix: 42 AfriNIC Region transit ASes present in the Internet Routing Table: 18 Average AfriNIC Region AS path length visible: 4.5 Max AfriNIC Region AS path length visible: 12 Number of AfriNIC addresses announced to Internet: 2660608 Equivalent to 0 /8s, 40 /16s and 153 /24s Percentage of available AfriNIC address space announced: 7.9 AfriNIC AS Blocks 36864-37887 & ERX transfers AfriNIC Address Blocks 41/8, 196/8 APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4134 965 5948 201 CHINANET-BACKBONE 9583 788 77 14 Sify Limited 1221 745 1328 514 Telstra Pty Ltd 4755 713 259 63 Videsh Sanchar Nigam Ltd. Aut 4766 608 3927 287 Korea Telecom (KIX) 7545 516 108 73 TPG Internet Pty Ltd 17676 468 6787 101 Softbank BB Corp. 9443 386 84 79 Primus Telecommunications 9498 337 147 59 BHARTI BT INTERNET LTD. 9929 335 224 46 China Netcom Corp. 2907 332 1756 309 SINET Japan 17557 328 23 156 Pakistan Telecom 17488 320 19 8 Hathway IP Over Cable Interne 7474 314 257 217 SingTel Optus Pty Ltd 4802 301 60 152 Wantree Development 18302 294 109 154 SK Global co., Ltd 9837 278 80 179 Powertel Ltd 17974 272 65 14 PT TELEKOMUNIKASI INDONESIA 703 254 263 206 UUNET - Commercial IP service 9800 251 394 66 CHINA UNICOM ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 7018 1500 6374 981 AT&T WorldNet Services 4323 1173 706 229 Time Warner Telecom 721 1083 21922 310 DLA Systems Automation Center 174 1082 5851 1014 Cogent Communications 701 999 8120 841 UUNET Technologies, Inc. 6197 940 389 480 BellSouth Network Solutions, 2386 915 515 677 AT&T Data Communications Serv 1239 867 2852 611 Sprint 18566 848 225 23 Covad Communications 20115 647 509 327 Charter Communications 209 628 3441 494 Qwest 3356 576 10661 445 Level 3 Communications, LLC 3602 557 131 110 Sprint Canada, Inc. 27364 554 44 18 Armstrong Cable Services 3561 541 2409 421 Savvis 22773 529 1352 28 Cox Communications, Inc. 5668 495 115 23 CenturyTel Internet Holdings, 6198 472 417 228 BellSouth Network Solutions, 7132 462 4949 395 SBC Internet Services 19262 453 1374 121 Verizon Global Networks RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 702 593 1994 480 UUNET - Commercial IP service 3301 300 1081 286 TeliaNet Sweden 3320 291 3230 241 Deutsche Telekom AG 8220 266 474 261 COLT Telecommunications 680 244 2040 240 DFN-IP service G-WiN 8708 236 262 216 Romania Data Systems S.A. 3246 229 476 222 Song Networks 9121 200 292 40 TTnet Autonomous System 1257 195 712 173 SWIPnet Swedish IP Network 6746 184 50 160 Dynamic Network Technologies, 5515 181 778 127 Sonera Solution Autonomous Sy 3269 176 1606 69 TELECOM ITALIA 786 174 1795 174 The JANET IP Service 5400 168 289 141 BT Ignite European Backbone 8866 167 37 9 Bulgarian Telecommunication C 6830 157 669 33 UPC Distribution Services 3300 156 185 91 AUCS Communications Services 25186 143 145 100 France Telecom Transpac's Tra 24863 138 37 6 LINKdotNET AS number 3215 136 1165 80 France Telecom Transpac LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 8151 397 650 168 UniNet S.A. de C.V. 16814 298 18 7 NSS, S.A. 11172 248 83 60 Servicios Alestra S.A de C.V 6147 191 118 21 Telefonica Del Peru 11664 191 20 24 Keytech SA 19632 183 14 5 Metropolis Intercom S.A. 22047 172 128 7 VTR PUNTO NET S.A. 14117 153 10 5 Telefonica del Sur S.A. 7303 148 70 13 Telecom Argentina Stet-France 11556 129 64 2 Cable-Wireless Panama 6505 121 89 85 Global One Communicaoes Ltda 10481 120 48 8 Prima S.A. 19169 120 8 28 Telconet 13999 116 52 9 Mega Cable S.A. de C.V. 6503 114 148 75 AVANTEL, S.A. 18822 111 7 15 TELEFONICA MANQUEHUE 21826 104 13 15 INTERCABLE 5639 103 12 9 Telecommunications Services o 11311 97 8 14 Sinectis S.A. 23216 96 24 19 RAMtelecom Telecomunicaciones AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 3741 266 708 223 The Internet Solution 5536 123 8 12 Internet Egypt Network 8452 106 32 7 TEDATA 2018 96 295 87 Tertiary Education Network 15475 92 84 4 Nile Online 2905 77 210 69 The Internetworking Company o 20928 59 16 2 Noor Advanced Technologies AS 24835 58 34 7 RAYA Telecom - Egypt 6713 51 54 8 Itissalat Al-MAGHRIB 5713 38 149 33 Telkom SA Ltd 12455 36 6 3 Jambonet Autonomous system 15706 31 8 3 Sudatel Internet Exchange Aut 33774 30 4 20 AS Number for Telecom Algeria 8524 24 1 4 AUCEGYPT Autonomous System 23889 23 5 9 MAURITIUS TELECOM 16637 22 10 19 Johnnic e-Ventures 21280 22 4 5 Swift Global Kenya Ltd.Is an 10798 21 1 12 Standard Bank of South Africa 12258 17 3 11 Vodacom Internet Company 15808 17 2 2 Communication Solutions Ltd i Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4323 1173 944 Time Warner Telecom 18566 848 825 Covad Communications 9583 788 774 Sify Limited 721 1083 773 DLA Systems Automation Center 4134 965 764 CHINANET-BACKBONE 4755 713 650 Videsh Sanchar Nigam Ltd. Aut 27364 554 536 Armstrong Cable Services 22773 529 501 Cox Communications, Inc. 5668 495 472 CenturyTel Internet Holdings, 6197 940 460 BellSouth Network Solutions, 3602 557 447 Sprint Canada, Inc. 7545 516 443 TPG Internet Pty Ltd 17676 468 367 Softbank BB Corp. 6467 399 349 E.Spire Communications, Inc. 19262 453 332 Verizon Global Networks 11492 335 327 Cable One 4766 608 321 Korea Telecom (KIX) 20115 647 320 Charter Communications 17488 320 312 Hathway IP Over Cable Interne 15270 337 310 PaeTec.net -a division of Pae List of Unregistered ASNs (Global) ---------------------------------- Bad AS Designation Network Transit AS Description 65506 PRIVATE 64.151.117.0/24 26228 ServePath, LLC 64826 PRIVATE 64.200.250.0/23 7911 Williams Communicati 65511 PRIVATE 65.77.145.0/24 16605 Aaro Broadband Wirel 65205 PRIVATE 152.163.5.0/24 2056 America Online 65111 PRIVATE 194.165.131.0/24 8697 Jordan Telecommunica 65430 PRIVATE 196.44.128.0/19 20459 Telecom Namibia 65004 PRIVATE 200.0.113.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.0.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.1.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.2.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.3.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.4.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.5.0/24 28477 Universidad Autonoma 65004 PRIVATE 200.4.6.0/24 28477 Universidad Autonoma 24413 UNALLOCATED 202.46.32.0/19 17623 China Netcom Corp. 65500 PRIVATE 202.93.233.0/24 4795 INDOSATNET-ASN 65500 PRIVATE 202.93.234.0/24 4795 INDOSATNET-ASN 65500 PRIVATE 202.93.235.0/24 4795 INDOSATNET-ASN 65500 PRIVATE 202.93.236.0/24 4795 INDOSATNET-ASN 65500 PRIVATE 202.93.237.0/24 4795 INDOSATNET-ASN 65500 PRIVATE 202.93.238.0/24 4795 INDOSATNET-ASN 18428 UNALLOCATED 203.91.0.0/24 9505 Taiwan Internet Gate 65005 PRIVATE 203.200.197.0/24 4755 Videsh Sanchar Nigam 65500 PRIVATE 211.158.36.0/22 23851 Chongqing Broadband 65500 PRIVATE 211.158.40.0/22 23851 Chongqing Broadband 65500 PRIVATE 211.158.44.0/22 23851 Chongqing Broadband Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 132.0.0.0/10 721 DLA Systems Automation Center 137.0.0.0/13 721 DLA Systems Automation Center 158.0.0.0/13 721 DLA Systems Automation Center 192.43.230.0/24 7575 Australian Academic and Rease 192.44.0.0/24 5501 Fraunhofer Gesellschaft 192.44.0.0/19 702 UUNET - Commercial IP service 192.70.164.0/24 25689 National Research Council of 192.84.205.0/24 719 LANLINK autonomous system 192.119.135.0/24 270 NASA 192.135.50.0/24 7018 AT&T WorldNet Services 192.172.0.0/19 721 DLA Systems Automation Center 192.200.100.0/24 7018 AT&T WorldNet Services Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:18 /9:5 /10:8 /11:17 /12:80 /13:175 /14:323 /15:627 /16:8522 /17:2742 /18:4675 /19:10744 /20:11804 /21:9854 /22:13211 /23:14085 /24:92579 /25:325 /26:271 /27:169 /28:45 /29:14 /30:60 /31:3 /32:30 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 18566 833 848 Covad Communications 6197 769 940 BellSouth Network Solutions, 7018 710 1500 AT&T WorldNet Services 2386 626 915 AT&T Data Communications Serv 9583 611 788 Sify Limited 4323 561 1173 Time Warner Telecom 27364 545 554 Armstrong Cable Services 4766 425 608 Korea Telecom (KIX) 5668 403 495 CenturyTel Internet Holdings, 702 369 593 UUNET - Commercial IP service 1239 369 867 Sprint 7011 368 423 Citizens Utilities 19916 363 369 OLM LLC 6198 345 472 BellSouth Network Solutions, 11492 327 335 Cable One 6517 310 336 Yipes Communications, Inc. 15270 307 337 PaeTec.net -a division of Pae 701 285 999 UUNET Technologies, Inc. 18302 279 294 SK Global co., Ltd 20115 270 647 Charter Communications Number of /24s announced per /8 block (Global) ---------------------------------------------- 4:4 8:23 12:1589 13:1 15:10 16:2 17:3 18:3 20:21 24:1070 30:3 32:61 38:149 40:55 44:4 47:2 52:4 55:1 56:3 57:23 58:156 59:68 60:122 61:726 62:759 63:1890 64:2875 65:2076 66:2910 67:614 68:612 69:1225 70:185 71:17 72:382 80:602 81:552 82:469 83:307 84:245 85:306 86:110 87:16 125:1 128:158 129:167 130:94 131:293 132:36 133:1 134:145 135:43 136:151 137:66 138:164 139:62 140:429 141:105 142:145 143:141 144:217 145:34 146:295 147:118 148:302 149:182 150:107 151:71 152:112 153:93 154:5 155:147 156:80 157:112 158:164 159:170 160:85 161:73 162:231 163:135 164:183 165:183 166:155 167:243 168:438 169:142 170:320 171:8 190:1 192:5709 193:3295 194:2402 195:1552 196:677 198:3881 199:3296 200:4179 201:327 202:6102 203:6384 204:3797 205:2069 206:2451 207:2821 208:2040 209:3355 210:1655 211:794 212:1214 213:1357 214:296 215:36 216:3669 217:1120 218:220 219:138 220:479 221:276 222:126 End of report

1 0

[removal of service on OLD ip address for "B"]
by bmanning＠vacation.karoshi.com 16 Sep '05

16 Sep '05

good afternoon, back on 14 january 2004, we provided notification that the "B" root server address was being renumbered. this renumbering occured 28 january 2004. we have continued to run root service on the old address since then to ease transition for those who might have needed more time to make the change. please ensure that you have a current "root.hints" or "cache.db" file. The Current version may be downloaded from: http://www.internic.net/zones/named.root we have requested and received permission to terminate root service on the old IP address for the "B" root server and plan to do so on 01 january 2006. if there are concerns or questions, please let us know. --bill manning for <hostmaster(a)b.root-servers.net>

1 0

commonly blocked ISP ports
by Luke Parrish 15 Sep '05

15 Sep '05

Everyone, Does anyone have a reference point for commonly blocked ports? We have a list, some reactive and some proactive, however we need to remove ports that are no longer a threat and add new ones as they are published. Thanks luke

10 10

RE: Computer systems blamed for feeble hurricane response?
by Hannigan, Martin 15 Sep '05

15 Sep '05

> > http://www.fema.gov/staff/extended.jsp > > Lists an "IT Services Division" that has ~250 possible points of > contact. > > Surely one of them has some clue... :-/ I think this sort of > problem > shows the endemic disease currently in place at FEMA. It's not just > an "IT gaffe" or firewall mistake. It's a failure much more > serious, > sadly. ObOp: Email is NOT a reliable form of communication. DHS shouldn't start to think so either. NANOG shouldn't worry about if someones email is working as a byproduct, but sure worry if the store and forward function of an ISP is. ' Anything below that is the individual SP's problem, IMO. Perhaps there are reasons some corporate or volunteer mail service is not working i.e. blocked, disallowed on port, etc. ObNotOp: Anyone who needs to contact FEMA, already knows how. If they are using a web page address, they probably shouldn't be contacting FEMA directly, but working through their own government hierarchy.

15 26

SANOG7: Call for Papers
by Gaurab Raj Upadhaya 15 Sep '05

15 Sep '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SANOG 7 16-24 January 2006, Mumbai, India Call for Papers http://www.sanog.org/sanog7/cfp.htm Deadline for proposals : 1 December, 2005 Acceptance Notification: 15 December, 2005 Paper Confirmation : 1 January, 2006 Please submit Online at https://submission.sanog.org/paper/ The following is an open call for papers/presentations for the two- day conference at the 7th South Asian Network Operators Group (SANOG) Meeting. Presentations are expected to be 20-30 minutes long with technical content. Marketing and sales content in presentations is against the spirit of the SANOG and is strictly prohibited. Please respond to this call for papers/presentations by making submissions online at https://submission.sanog.org/paper/ The conference will be comprised of 6 session in two days, including the plenary. The tracks are for general ideas, and feel free to propose talks that you think are relevant to the operational and Internet research community. The topics given below are not exclusive. Track 1: Network operations In this session we invite papers, reports and presentations from network operators, equipment vendors and academic institutions conducting network research on operational issues. Possible topics for this track are: - - Prevention and mitigation of Denial of Service attacks including intrusion - - Routing policies and architecture for scalable IP and broadband networks - - Technology updates and trends in security and routing - - MPLS and QoS implementation experiences - - Traffic management and measurement - - Network migration issues (IPv4 to v6, Layer 2 to IP etc.) Track 2: Applications and Services This track will discuss various services that can be enabled on packet networks. Papers and presentations are invited from developers, operators, equipment vendors and research organizations on the following and related topics - - Voice and Multimedia over IP - - Managed network services including Security and VPNs - - Mail servers, SPAM prevention, - - Wireless Technology and Applications Track 3: Peering and IXP This is a new track at SANOG. This is to cater to the growing demand on the newly established Internet Exchange Points in the region. As local ISPs are going international, we would like to invite both regional and international experts to share their ideas and experience on these topics. - - Internet Exchange Points Operations - - Peering Techniques and Policies - - BGP Multihoming Techniques Track 4: Regional updates This track is fairly broad, and will include updates from ISPs, regional Internet exchanges, APNIC, routing table updates and such information that would be useful to the SANOG community. You are also welcome to submit proposals for BoFs, tutorials and other tracks. On behalf of Ananth Nagarajan, Program Chair - SANOG Sumon Ahmed Sabir, Program Co-Chair - SANOG and the SANOG Programme Committee -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFDKaaeSo7fU26F3X0RAipsAKDlvKAKH16cI6fphhKEF4HADidRTwCcDcAl K5sn/F/ipeWsvrNjXIOeR0g= =jkeN -----END PGP SIGNATURE-----

1 0

FWD: Explanation for the recent major downtime
by jc dill 15 Sep '05

15 Sep '05

My personal website is hosted with DreamHost. They sent this out to their customers today. Of interest to NANOG is the bit about the N+1 redundant genset system having 2 generators quickly fail, and in doing so having the UPS fail and the entire data center go dark. Something to consider in your data center design... jc DreamHost Announcement Team wrote: > On Monday, September 12 the greater Los Angeles area experienced a major power outage > affecting large sections of the city, including our main data center. The power outage began > shortly before 1pm PST and continued until about 4:30pm PST. Our data center is equipped > with a redundant backup power system with both battery UPS systems and diesel generators, > but the backup failed and our entire data center was powered down. > > We have previously covered much of this information on our official weblog (http:// > blog.dreamhost.com/) but many of you have not seen that information so we will summarize > the events here. > > When the grid power to our building was cut, the UPS system kicked in and kept everything in > the building up and running. The five generators also fired up and began providing power. > The building needs four generators to operate at full power so the system is designed to > tolerate a single failure. Unfortunately, two of the five generators failed within minutes of each > other. We receive our power from the building housing our data center and they also manage > the redundant power system. We do not know the exact reason for the generator failures at > this time. We have received some vague explanations that we have not found to be satisfactory. > Regardless, the remaining three generators were not sufficient to meet the building's power > needs and that caused the emergency electrical systems to transfer into a “load shedding > mode” and the building’s UPS system to turn itself off, thus preventing permanent UPS and > related equipment damage. That shut everything down, including emergency lighting, and the > building was evacuated. > > About 15 minutes later, one of the generators was started up to power emergency lighting and > a couple of our senior technicians made their way into the (still evacuated) building and down > to our data center to assess the damage. Since the backup power had failed, our own data > center power remained off until the main grid power came back. We then proceeded to slowly > power up our equipment. Servers (and all computers) consume significantly more power when > booting up than when up and running so there is some risk of overloading the power circuits if > too many of them are flipped on at once. Keeping that in mind, we powered everything on as > quickly as possible. At that time the majority of our services were fully back up and running > but some services were still down and we began the process of systematically verifying all > services and making any necessary repairs and adjustments. Whenever a large number of > servers suddenly loses power a certain small percentage of them will not come back up properly > and when you have several hundred servers it takes awhile to verify all of them. > > Once our own access to our servers was restored our staff continued working into the night to > restore as much service as possible and to respond to as many of your support cases as > possible. Some of our staff continued working all the way through the night and we were able > to restore almost everything that first night. > > Tuesday (September 13) started off early with all of us addressing the residual issues. At > around noon that day one of our core routers experienced an internal failure stemming from > damage previously sustained during the power outage. Our routers handle all of the Internet > traffic coming in and out of our network and they are set up in a redundant way to minimize > network disruption when a failure does occur. In this case, the main cpu of the router (called > the 'supervisor') died and the secondary one took over. Everything continued working almost as > it should have, but there is a remaining router issue that we are still working with Cisco support > on. That issue is responsible for the slower than normal performance of our network and it will > be resolved absolutely as soon as possible. > > During this outage, our off-network Emergency Status Page (http://status.dreamhost.com/) > proved to be an invaluable resource for disseminating information among our customers. That > status page remained up throughout the power outage and was updated regularly as we > received new information. Unfortunately, not everyone knows about it and we will be working > to improve that situation in the coming days. Those bloggers among you that did know to > check the status page were extra helpful in passing along the information to other > dreamhosters who were still in the dark. Thank you to everyone who helped out with that! > > This announcement will be followed by another explaining what went wrong with our processes > and what we plan to do to address them. That will come in the next few days. > > We will be continuing to provide more detailed information on our official weblog found here: > http://blog.dreamhost.com/ > > Also, everyone who has not bookmarked our Emergency Status Page should do so now. That > page is found here: > http://status.dreamhost.com/ > > We will be improving on the basic page we have there to provide as useful of an avenue of > information as possible. > > If you have any additional questions about this outage, please let us know. We will be happy to > address all of your questions or concerns. > > > The Un-Happy DreamHost Powerless Team > > > > > > > > >

2 1

Re: 12/8 problems? (fwd)
by Manish Karir 15 Sep '05

15 Sep '05

---------- Forwarded message ---------- Date: Wed, 14 Sep 2005 16:39:54 -0400 (EDT) From: Manish Karir <mkarir(a)merit.edu> To: nanog(a)merit.edu Subject: Re: 12/8 problems? I'm sorry I'm a bit late on this thread but wanted to point out that you can view some of the relevant information on this, as seen from routeviews at: http://bgpinspect.merit.edu - At the bottom half of the page, select routeviews peer, e.g. sprint - select "Prefix-Exact" as query type - Enter prefix into the Query box: "12.0.0.0/8" (without the quotes) - Select start date as Aug 25, select end date as Sept 14 - Click submit-query. Alternately you can just get the pdf files of the results page from the above queries from the following 2 links: http://bgpinspect.merit.edu/reports/glx-12-8.pdf http://bgpinspect.merit.edu/reports/sprint-12-8.pdf After a few more cleanups and changes, we will be re-announcing the bgp-inspect project hopefully before the next nanog mtg. as a generally available service. thanks manish ---- Date: Mon, 12 Sep 2005 18:02:29 -0400 From: Richard A Steenbergen <ras(a)e-gerbil.net> Subject: Re: 12/8 problems? On Sat, Sep 10, 2005 at 06:15:38AM -0700, Eric Louie wrote: > > FYI, happened again this morning for (at least) 12/8 > duration approx 30 minutes > starting at 5:45 AM PDT. Notice that AT&T is no longer taking chances, and is announcing 2 /9s. - -- Richard A Steenbergen <ras(a)e-gerbil.net> http://www.e-gerbil.net/ras GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC) ----------

1 0

The return of the wildcard domain...
by Jim McBurnett 15 Sep '05

15 Sep '05

All, I saw this evening that CentralNic had added *.uk.com to point to itself. I thought this was of operational interest considering the effect Verisign sitefinder had. (Sorry Martin, no offence intended) So I guess the question to us all is: how will this affect our networks as a whole? Or will it at all? Or is it already? I tried this with the almost funny domain www.idunno.uk.com It does a redirect to http://www.uk.com/results/idunno?src=idunno And came back with a "The domain name "idunno.uk.com" is available for registration. Would you like to buy it" So will ICANN act on this? CentralNIC also runs the uk.com, us.com, eu.com and de.com domains. For a "news" reference: http://www.theregister.co.uk/2005/09/14/centralnic_wildcard/ Anyway, I thought I would start a new topic.. Hopefully this does not add too much to the overall S:N...... Later, Jim McBurnett

5 4

re: commonly blocked ports (but not on backbones)
by brett watson 14 Sep '05

14 Sep '05

> seems to me this is the wrong question... a default security > "posture" (network or system, isp or enterprise or any type of > entity) should be: "if it's not explicitly allowed, it's denied." apologies, i see the original poster was talking about a *backbone*... my mind was on campus/edge/customer networks. this policy, of course, does not apply to backbones (unless you want an avalanche of customer calls). -b

1 0

CAT5 surge/lightning strike protection recommendations?
by R.P. Aditya 14 Sep '05

14 Sep '05

I have a bunch of cat5 buried about 1 ft below the surface connecting multiple buildings on a campus (short runs) and lightning strikes nearby have caused surges along one or more of the cables and burnt out switch ports. I would like to protect the switch ports -- there seem to be lots of products on the market. Anyone have recommendations (tested/practical is best :-)? The APC Protectnet PNET1 and PRM24 seem quite nice and not too expensive -- if they work....pros? cons? Thanks, Adi

13 17