BEGIN:VCALENDAR VERSION:2.0 X-WR-CALNAME:IP Grid Unscheduled Outages PRODID:-//Apple Computer, Inc//iCal 2.0//EN X-WR-RELCALID:9F5CEEB3-53E1-4CDE-9E76-75-unsched_maint X-WR-TIMEZONE:America/Indianapolis CALSCALE:GREGORIAN METHOD:PUBLISH BEGIN:VEVENT SEQUENCE:1 DTSTART:20060628T184001Z SUMMARY: 96 IP Grid Participant Purdue Lambda to Chicago Outage DTEND:20060628T185001Z DESCRIPTION:TICKET NUMBER: 96\nOUTAGE TYPE: Circuit---Other\nAFFECTED: IP Grid Participant Purdue's Lambda to Chicago\n\nSTART TIME: Wednesday, June 28, 2006, 6:40 PM (1840)\nEND TIME: Wednesday, June 28, 2006, 6:50 PM (1850)\nDESCRIPTION: IP Grid Participant Purdue's Lambda to Chicago was unavailable due to non-service affecting maintenance being performed by IP Grid engineers. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=96&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20060801T171901Z SUMMARY: 104 IP Grid Bloomington Force 10 Outage DTEND:20060801T203401Z DESCRIPTION:TICKET NUMBER: 104\nOUTAGE TYPE: Undetermined\nAFFECTED: bf10-2.iu.teragrid.org (Big Red cluster)\nbf10-1.iu.teragrid.org connection to bBR.noc.indiana.edu\nbf10-1.iu.teragrid.org connection to Data Capacitor\n\nSTART TIME: Tuesday, August 1, 2006, 5:19 PM (1719)\nEND TIME: Tuesday, August 1, 2006, 8:34 PM (2034)\nDESCRIPTION: IUB Maintenance URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=104&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20060815T170001Z SUMMARY: 107 IP Grid Indianapolis to Chicago Circuit Available DTEND:20060824T145901Z DESCRIPTION:TICKET NUMBER: 107\nOUTAGE TYPE: Hardware\nAFFECTED: Teragrid Circuit #2 between Indianapolis & Chicago\n\nSTART TIME: Tuesday, August 15, 2006, 5:00 PM (1700)\nEND TIME: Thursday, August 24, 2006, 2:59 PM (1459)\nDESCRIPTION: The Teragrid circuit #2 is now available to the IP Grid community. IP Grid engineers replaced a transponder at the IUPUI node and the circuit is now stable. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=107&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20060827T171601Z SUMMARY: 111 IP Grid Indianapolis to Chicago Circuit Outage Resolved DTEND:20060828T160501Z DESCRIPTION:TICKET NUMBER: 111\nOUTAGE TYPE: Hardware\nAFFECTED: Teragrid Circuit #1 between Indianapolis & Chicago\n\nSTART TIME: Sunday, August 27, 2006, 5:16 PM (1716)\nEND TIME: Monday, August 28, 2006, 4:05 PM (1605)\nDESCRIPTION: Teragrid Circuit #1 was unavailable to the IP Grid Community. IP Grid Engineers replaced a transpoder card and the circuit has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=111&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20061113T174401Z SUMMARY: 126 IP Grid Indianapolis-Chicago Circuit Outage Resolved DTEND:20061113T192401Z DESCRIPTION:TICKET NUMBER: 126\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Teragrid Circuit #1 between Indianapolis & Chicago\nTeragrid Circuit #2 between Indianapolis & Chicago\n\nSTART TIME: Monday, November 13, 2006, 5:44 PM (1744)\nEND TIME: Monday, November 13, 2006, 7:24 PM (1924)\nDESCRIPTION: IP Grid circuits 1 & 2 between Indianapolis & Chicago were unavailable to the IP Grid Community. A fiber connection was accidentally disconnected while troubleshooting an unrelated outage. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=126&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20070422T214001Z SUMMARY: 151 Link to IUPUI_Force10 is unconfigured/Link to Teragrid-10GigE-1 is down DTEND:20070504T201401Z DESCRIPTION:TICKET NUMBER: 151\nOUTAGE TYPE: Undetermined\nAFFECTED: \nSTART TIME: Sunday, April 22, 2007, 9:40 PM (2140)\nEND TIME: Friday, May 4, 2007, 8:14 PM (2014)\nDESCRIPTION: URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=151&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20070123T130501Z SUMMARY: 137 IP Grid Indianapolis E600 Slot 3 Connections Outage Resolved DTEND:20070123T155301Z DESCRIPTION:TICKET NUMBER: 137\nOUTAGE TYPE: Hardware\nAFFECTED: Indianapolis E600 Slot 3 Connections\n\nSTART TIME: Tuesday, January 23, 2007, 1:05 PM (1305)\nEND TIME: Tuesday, January 23, 2007, 3:53 PM (1553)\nDESCRIPTION: All connections to the IP Grid network via the Indianapolis E600 Slot 3 were unavailable. IP Grid engineers moved the connections restoring connectivity. Engineering replaced a failed card and in agreement with the customers, let the connections remain on Slot 1. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=137&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20070215T095301Z SUMMARY: 142 IP Grid Core Node SBR (Indianapolis) Available DTEND:20070215T124001Z DESCRIPTION:TICKET NUMBER: 142\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node: SBR (Indianapolis)\nOne of the backbone circuits to Chicago \n\n\nSTART TIME: Thursday, February 15, 2007, 9:53 AM (0953)\nEND TIME: Thursday, February 15, 2007, 12:40 PM (1240)\nDESCRIPTION: IP Grid Core Node SBR (Indianapolis) was unavailable to the Indiana University IPGrid Community. IP Grid engineers moved the connection to a different port restoring connectivity to IU. However, one of two 10G backbone circuits to Chicago remains unvailable. Connectivity to Chicago is still available, though at a diminished capacity of 10Gbps. IP Grid is expecting to perform maintenance on Friday, February 16 to replace and return all connections restoring all connectivity. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=142&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20070503T150001Z SUMMARY: 156 IP Grid NOC Email Account Outage Resolved DTEND:20070503T191401Z DESCRIPTION:TICKET NUMBER: 156\nOUTAGE TYPE: Undetermined\nAFFECTED: No Network Impact\n\nSTART TIME: Thursday, May 3, 2007, 3:00 PM (1500)\nEND TIME: Thursday, May 3, 2007, 7:14 PM (1914)\nDESCRIPTION: The IP Grid NOC email account was unavailable. System administrators resolved the problem. Please resume contacting the IP Grid NOC via email or phone. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=156&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080409T192401Z SUMMARY: 258 IP Grid sw2.bltn.iu.teragrid.org & sw3.bltn.iu.teragrid.org Outage Resolved DTEND:20080409T192801Z DESCRIPTION:TICKET NUMBER: 258\nOUTAGE TYPE: Software\nAFFECTED: \nSTART TIME: Wednesday, April 9, 2008, 7:24 PM (1924)\nEND TIME: Wednesday, April 9, 2008, 7:28 PM (1928)\nDESCRIPTION: URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=258&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20070625T214301Z SUMMARY: 174 IP Grid Node Indianapolis Force 10-2 (e600) Outage Resolved DTEND:20070626T000301Z DESCRIPTION:TICKET NUMBER: 174\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node: Indianapolis Force 10-2 (e600)\n\nSTART TIME: Monday, June 25, 2007, 9:43 PM (2143)\nEND TIME: Tuesday, June 26, 2007, 12:03 AM (0003)\nDESCRIPTION: IP Grid Node Indianapolis Force 10-2 (e600) is currently available to the IP Grid Community. IP Grid Engineers report the outage was due to a failed card. The card has been replaced and service has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=174&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080419T021901Z SUMMARY: 261 IP Grid Core Node Bloomington Force-10 e600 Brief Outage DTEND:20080419T022001Z DESCRIPTION:TICKET NUMBER: 261\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node Bloomington Force-10 e600\n\nSTART TIME: Saturday, April 19, 2008, 2:19 AM (0219)\nEND TIME: Saturday, April 19, 2008, 2:20 AM (0220)\nDESCRIPTION: IP Grid Core Node Bloomington Force-10 e600 was briefly unavailable to the community due to an RPM failure. The backup RPM took over and service has been restored. IP Grid engineers are currently working with Force10 Support to correct the problem. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=261&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20071210T214601Z SUMMARY: 232 IPGrid Various Core Nodes Reporting Down DTEND:20071210T235001Z DESCRIPTION:TICKET NUMBER: 232\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: IP Grid Fiber Patch\n\nSTART TIME: Monday, December 10, 2007, 9:46 PM (2146)\nEND TIME: Monday, December 10, 2007, 11:50 PM (2350)\nDESCRIPTION: Two fiber patches were inadvertently crimped. Patches were repaired and service restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=232&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20071226T135001Z SUMMARY: 234 IP Grid Computer Science Outage Available DTEND:20071226T154101Z DESCRIPTION:TICKET NUMBER: 234\nOUTAGE TYPE: Undetermined\nAFFECTED: Computer Science\n\nSTART TIME: Wednesday, December 26, 2007, 1:50 PM (1350)\nEND TIME: Wednesday, December 26, 2007, 3:41 PM (1541)\nDESCRIPTION: IP Grid Computer Science is now available to the IP Grid community. IP Grid engineers gave no reason for the outage. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=234&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080311T132101Z SUMMARY: 253 IP Grid Participant Purdue ETF Site Switch Available DTEND:20080311T132801Z DESCRIPTION:TICKET NUMBER: 253\nOUTAGE TYPE: Undetermined\nAFFECTED: Participant Purdue ETF Site Switch #1 (SBR:17:192.5.40.5) \n\nSTART TIME: Tuesday, March 11, 2008, 1:21 PM (1321)\nEND TIME: Tuesday, March 11, 2008, 1:28 PM (1328)\nDESCRIPTION: IP Grid Participant Purdue ETF Site Switch was unavailable to the community. Purdue Engineers had been contacted; however, reason for outage is unavailable. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=253&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080127T070001Z SUMMARY: 240 IP Grid Backbone Circuit bF10-1 to IU-Campus Stable DTEND:20080127T070101Z DESCRIPTION:TICKET NUMBER: 240\nOUTAGE TYPE: Circuit---Damaged-Fiber\nAFFECTED: Backbone Circuit bF10-1 to IU-Campus\n\nSTART TIME: Sunday, January 27, 2008, 7:00 AM (0700)\nEND TIME: Sunday, January 27, 2008, 7:01 AM (0701)\nDESCRIPTION: IP Grid Backbone Circuit bF10-1 to IU-Campus is currently stable. IP Grid engineers identified the problem to a bad fiber. Connectivity has been stabilized. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=240&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:2 DTSTART:20080127T070501Z SUMMARY: 240 IP Grid Backbone Circuit bF10-1 to IU-Campus Stable DTEND:20080127T070601Z DESCRIPTION:TICKET NUMBER: 240\nMAINTENANCE TYPE: \nAFFECTED: Backbone Circuit bF10-1 to IU-Campus\n\nSTART TIME: Sunday, January 27, 2008, 7:05 AM (0705)\nEND TIME: Sunday, January 27, 2008, 7:06 AM (0706)\nDESCRIPTION: IP Grid Backbone Circuit bF10-1 to IU-Campus is currently stable. IP Grid engineers identified the problem to a bad fiber. Connectivity has been stabilized. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=240&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:3 DTSTART:20080127T082601Z SUMMARY: 240 IP Grid Backbone Circuit bF10-1 to IU-Campus Stable DTEND:20080127T082701Z DESCRIPTION:TICKET NUMBER: 240\nMAINTENANCE TYPE: \nAFFECTED: Backbone Circuit bF10-1 to IU-Campus\n\nSTART TIME: Sunday, January 27, 2008, 8:26 AM (0826)\nEND TIME: Sunday, January 27, 2008, 8:27 AM (0827)\nDESCRIPTION: IP Grid Backbone Circuit bF10-1 to IU-Campus is currently stable. IP Grid engineers identified the problem to a bad fiber. Connectivity has been stabilized. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=240&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:4 DTSTART:20080127T113301Z SUMMARY: 240 IP Grid Backbone Circuit bF10-1 to IU-Campus Stable DTEND:20080127T192701Z DESCRIPTION:TICKET NUMBER: 240\nMAINTENANCE TYPE: \nAFFECTED: Backbone Circuit bF10-1 to IU-Campus\n\nSTART TIME: Sunday, January 27, 2008, 11:33 AM (1133)\nEND TIME: Sunday, January 27, 2008, 7:27 PM (1927)\nDESCRIPTION: IP Grid Backbone Circuit bF10-1 to IU-Campus is currently stable. IP Grid engineers identified the problem to a bad fiber. Connectivity has been stabilized. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=240&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080507T171401Z SUMMARY: 268 IPGrid Link to BB - Swain West/Astro is Down DTEND:20080507T183501Z DESCRIPTION:TICKET NUMBER: 268\nOUTAGE TYPE: Power\nAFFECTED: \nSTART TIME: Wednesday, May 7, 2008, 5:14 PM (1714)\nEND TIME: Wednesday, May 7, 2008, 6:35 PM (1835)\nDESCRIPTION: Power restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=268&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080607T162601Z SUMMARY: 274 IP Grid Core Node Bloomington Force-10 E600 Available DTEND:20080610T155601Z DESCRIPTION:TICKET NUMBER: 274\nOUTAGE TYPE: Power\nAFFECTED: Core Node Bloomington Force-10 E600\n\nSTART TIME: Saturday, June 7, 2008, 4:26 PM (1626)\nEND TIME: Tuesday, June 10, 2008, 3:56 PM (1556)\nDESCRIPTION: IP Grid Core Node Bloomington Force-10 E600 was unavailable to the community. The reason for outage is due to a power failure. Power has been restored and the Force-10 E600 has been returned to service. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=274&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080614T192901Z SUMMARY: 278 IP Grid Core Node Bloomington Force-10 E600 Outage Update DTEND:20080616T191601Z DESCRIPTION:TICKET NUMBER: 278\nOUTAGE TYPE: Power\nAFFECTED: Core Node Bloomington Force-10 E600\n\nSTART TIME: Saturday, June 14, 2008, 7:29 PM (1929)\nEND TIME: Monday, June 16, 2008, 7:16 PM (1916)\nDESCRIPTION: IP Grid Core Node Bloomington Force-10 E600 was unavailable to the community due to a power outage. Technicians have restored service. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=278&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080722T055001Z SUMMARY: 287 IP Grid Core Node IUB Force10-2 and IUB Force10-3 Outage Resolved DTEND:20080722T125701Z DESCRIPTION:TICKET NUMBER: 287\nOUTAGE TYPE: Power\nAFFECTED: Core Node IUB Force10-2 and IUB Force10-3\n\nSTART TIME: Tuesday, July 22, 2008, 5:50 AM (0550)\nEND TIME: Tuesday, July 22, 2008, 12:57 PM (1257)\nDESCRIPTION: IP Grid Core Nodes IUB Force10-2 and IUB Force10-3 and all their associated connections were unavailable. Power has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=287&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080802T184301Z SUMMARY: 292 IP Grid Connection Purdue Outages Resolved DTEND:20080802T195901Z DESCRIPTION:TICKET NUMBER: 292\nOUTAGE TYPE: Hardware\nAFFECTED: IP Grid Participant Purdue's Lambda to Chicago\n\nSTART TIME: Saturday, August 2, 2008, 6:43 PM (1843)\nEND TIME: Saturday, August 2, 2008, 7:59 PM (1959)\nDESCRIPTION: Purdue's Lambda to Chicago is unavailable in the IP Grid community. Engineers have been contacted and re-seated a faulty card in Indianapolis, IN. Service has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=292&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:2 DTSTART:20080819T121501Z SUMMARY: 292 IP Grid Connection Purdue Outages Resolved DTEND:20080819T122001Z DESCRIPTION:TICKET NUMBER: 292\nMAINTENANCE TYPE: \nAFFECTED: IP Grid Participant Purdue's Lambda to Chicago\n\nSTART TIME: Tuesday, August 19, 2008, 12:15 PM (1215)\nEND TIME: Tuesday, August 19, 2008, 12:20 PM (1220)\nDESCRIPTION: Purdue's Lambda to Chicago is unavailable in the IP Grid community. Engineers have been contacted and re-seated a faulty card in Indianapolis, IN. Service has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=292&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080729T042001Z SUMMARY: 296 IP Grid Core Node BF10-2 Brief Outage Resolved DTEND:20080729T042401Z DESCRIPTION:TICKET NUMBER: 296\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node BF10-2\n\nSTART TIME: Tuesday, July 29, 2008, 4:20 AM (0420)\nEND TIME: Tuesday, July 29, 2008, 4:24 AM (0424)\nDESCRIPTION: Force10 has told us to upgrade. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=296&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20081211T202801Z SUMMARY: 338 IP Grid Backbone Circuits to Chicago Available DTEND:20081212T135801Z DESCRIPTION:TICKET NUMBER: 338\nOUTAGE TYPE: Undetermined\nAFFECTED: Backbone Circuits to Chicago\n\nSTART TIME: Thursday, December 11, 2008, 8:28 PM (2028)\nEND TIME: Friday, December 12, 2008, 1:58 PM (1358)\nDESCRIPTION: IP Grid Backbone Circuits to Chicago is now available to the community. IP Grid Engineers are currently on site in Chicago and reported the outage was due to bad fiber pair and have move the connections to a new fiber pair. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=338&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080903T174101Z SUMMARY: 311 IP Grid bf10-1 Various Circuits Outage Resolved DTEND:20080903T192001Z DESCRIPTION:TICKET NUMBER: 311\nOUTAGE TYPE: Hardware\nAFFECTED: Teragrid\n\nSTART TIME: Wednesday, September 3, 2008, 5:41 PM (1741)\nEND TIME: Wednesday, September 3, 2008, 7:20 PM (1920)\nDESCRIPTION: bf10-1 is available to the community. IP Grid engineers have isolated a bad line card. IP Grid engineers reseated the card to restore service. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=311&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20080912T125601Z SUMMARY: 313 IP-Grid WCC SW2 and SW3 Switch Outage resolved DTEND:20080912T131101Z DESCRIPTION:TICKET NUMBER: 313\nOUTAGE TYPE: Undetermined\nAFFECTED: sw2.wcc.iu.teragrid.org\nsw3.wcc.iu.teragrid.org\n\nSTART TIME: Friday, September 12, 2008, 12:56 PM (1256)\nEND TIME: Friday, September 12, 2008, 1:11 PM (1311)\nDESCRIPTION: Both switches are fully functional. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=313&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20081018T051601Z SUMMARY: 323 IP Grid Backbone sw4.wcc to bf10-1 Outage DTEND:20081018T055101Z DESCRIPTION:TICKET NUMBER: 323\nOUTAGE TYPE: Undetermined\nAFFECTED: \nSTART TIME: Saturday, October 18, 2008, 5:16 AM (0516)\nEND TIME: Saturday, October 18, 2008, 5:51 AM (0551)\nDESCRIPTION: Switch was down due to power failure URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=323&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:2 DTSTART:20081018T055201Z SUMMARY: 323 IP Grid Backbone sw4.wcc to bf10-1 Outage DTEND:20081018T055901Z DESCRIPTION:TICKET NUMBER: 323\nMAINTENANCE TYPE: \nAFFECTED: \nSTART TIME: Saturday, October 18, 2008, 5:52 AM (0552)\nEND TIME: Saturday, October 18, 2008, 5:59 AM (0559)\nDESCRIPTION: Switch was down due to power failure URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=323&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20081030T223301Z SUMMARY: 328 IP Grid Connectivity to IU Campus Outage DTEND:20081030T223901Z DESCRIPTION:TICKET NUMBER: 328\nOUTAGE TYPE: Undetermined\nAFFECTED: \nSTART TIME: Thursday, October 30, 2008, 10:33 PM (2233)\nEND TIME: Thursday, October 30, 2008, 10:39 PM (2239)\nDESCRIPTION: IPGRID Backbone BF10-1 to IF10-1was unavailable. IPGRID engineers are currently investigating, however no reason for the outage has been determined. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=328&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:2 DTSTART:20081031T033501Z SUMMARY: 328 IP Grid Connectivity to IU Campus Outage DTEND:20081031T033901Z DESCRIPTION:TICKET NUMBER: 328\nMAINTENANCE TYPE: \nAFFECTED: \nSTART TIME: Friday, October 31, 2008, 3:35 AM (0335)\nEND TIME: Friday, October 31, 2008, 3:39 AM (0339)\nDESCRIPTION: IPGRID Backbone BF10-1 to IF10-1was unavailable. IPGRID engineers are currently investigating, however no reason for the outage has been determined. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=328&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090201T131601Z SUMMARY: 351 IP Grid Backbone Circuits Outage Resolved DTEND:20090201T133001Z DESCRIPTION:TICKET NUMBER: 351\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Teragrid 10GigE #1 and #2\n\nSTART TIME: Sunday, February 1, 2009, 1:16 PM (1316)\nEND TIME: Sunday, February 1, 2009, 1:30 PM (1330)\nDESCRIPTION: IP Grid Backbone Circuits #1 and #2 experienced a brief outage. The reason for the outage was due to a circuit maintenance. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=351&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090315T111601Z SUMMARY: 361 IP Grid Core Node bF10-2 Outage Resolved DTEND:20090315T120801Z DESCRIPTION:TICKET NUMBER: 361\nOUTAGE TYPE: Power\nAFFECTED: Core Node bF10-2\n\nSTART TIME: Sunday, March 15, 2009, 11:16 AM (1116)\nEND TIME: Sunday, March 15, 2009, 12:08 PM (1208)\nDESCRIPTION: Core Node bF10-2 is now available. Technicians replaced the failed UPS. The node was switched to utility power, temporarily restoring service until the replacement UPS was installed. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=361&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:2 DTSTART:20090315T150601Z SUMMARY: 361 IP Grid Core Node bF10-2 Outage Resolved DTEND:20090318T000601Z DESCRIPTION:TICKET NUMBER: 361\nMAINTENANCE TYPE: \nAFFECTED: Core Node bF10-2\n\nSTART TIME: Sunday, March 15, 2009, 3:06 PM (1506)\nEND TIME: Wednesday, March 18, 2009, 12:06 AM (0006)\nDESCRIPTION: Core Node bF10-2 is now available. Technicians replaced the failed UPS. The node was switched to utility power, temporarily restoring service until the replacement UPS was installed. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=361&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090319T183601Z SUMMARY: 366 IP Grid Participant Purdue ETF Site Switch #1 Available DTEND:20090325T152101Z DESCRIPTION:TICKET NUMBER: 366\nOUTAGE TYPE: Undetermined\nAFFECTED: Participant Purdue ETF Site Switch #1 \n(SBR:17:192.5.40.5)\n\nSTART TIME: Thursday, March 19, 2009, 6:36 PM (1836)\nEND TIME: Wednesday, March 25, 2009, 3:21 PM (1521)\nDESCRIPTION: IP Grid Participant Purdue ETF Site Switch is available to the community. Purdue Engineers have been contacted; however, reason for outage was due to a damaged strand. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=366&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090505T135501Z SUMMARY: 374 IP Grid Core Node SBR Available DTEND:20090505T180001Z DESCRIPTION:TICKET NUMBER: 374\nOUTAGE TYPE: Hardware\nAFFECTED: Core Node SBR\n\nSTART TIME: Tuesday, May 5, 2009, 1:55 PM (1355)\nEND TIME: Tuesday, May 5, 2009, 6:00 PM (1800)\nDESCRIPTION: IP Grid Core Node SBR is available after IP Grid engineers performed software maintenance. A hard drive failure resulted in a temporary outage. A new hard drive was installed. Teragrid traffic was re-routed during this outage. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=374&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090512T100001Z SUMMARY: 375 IP Grid Various Backbone Circuit Outage Resolved DTEND:20090512T103301Z DESCRIPTION:TICKET NUMBER: 375\nOUTAGE TYPE: Circuit---Other\nAFFECTED: Purdue 10G\nTeraGrid 10G #1 & #2\n\nSTART TIME: Tuesday, May 12, 2009, 10:00 AM (1000)\nEND TIME: Tuesday, May 12, 2009, 10:33 AM (1033)\nDESCRIPTION: The above listed circuits were unavailable to the community following circuit maintenance. IP Grid engineers worked with Cisco Systems to restore service. Further work will be scheduled at a later date to make permanent repairs; however, this maintenance is complete. This is a continuation of maintenance ticket 371:75. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=375&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090611T113601Z SUMMARY: 383 IP Grid opt.wlct.iu.teragrid.org Alarm Available DTEND:20090611T113701Z DESCRIPTION:TICKET NUMBER: 383\nOUTAGE TYPE: Undetermined\nAFFECTED: opt.wlct.iu.teragrid.org\n\nSTART TIME: Thursday, June 11, 2009, 11:36 AM (1136)\nEND TIME: Thursday, June 11, 2009, 11:37 AM (1137)\nDESCRIPTION: URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=383&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090622T120001Z SUMMARY: 385 IPgrid BB link to sw.wcc.iu.teragrid.org Brief Outage - Complete DTEND:20090622T120401Z DESCRIPTION:TICKET NUMBER: 385\nOUTAGE TYPE: Undetermined\nAFFECTED: iDataPlex switch at Wruber (SW/SW4)\n\nSTART TIME: Monday, June 22, 2009, 12:00 PM (1200)\nEND TIME: Monday, June 22, 2009, 12:04 PM (1204)\nDESCRIPTION: UP URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=385&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090722T182201Z SUMMARY: 396 IP Grid opt.star.iu.teragrid.org FAC-1-1-1 &FAC-2-1-1 Carrier Loss On The LAN$ - Complete DTEND:20090722T182801Z DESCRIPTION:TICKET NUMBER: 396\nOUTAGE TYPE: Circuit---Other\nAFFECTED: \nSTART TIME: Wednesday, July 22, 2009, 6:22 PM (1822)\nEND TIME: Wednesday, July 22, 2009, 6:28 PM (1828)\nDESCRIPTION: Engineering investigating URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=396&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090806T170001Z SUMMARY: 402 IP Grid Core Node (WCC) Outage Resolved DTEND:20090806T174501Z DESCRIPTION:TICKET NUMBER: 402\nOUTAGE TYPE: Power\nAFFECTED: Core Node WCC\n\nSTART TIME: Thursday, August 6, 2009, 5:00 PM (1700)\nEND TIME: Thursday, August 6, 2009, 5:45 PM (1745)\nDESCRIPTION: IP Grid Core Node (WCC) was unavailable to the community due to a power outage. Power has been restored to the node. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=402&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090804T163601Z SUMMARY: 400 IP Grid IDataPlex Switch Outage Resolved DTEND:20090804T171101Z DESCRIPTION:TICKET NUMBER: 400\nOUTAGE TYPE: Power\nAFFECTED: sw4.wcc.iu.teragrid.org\n\nSTART TIME: Tuesday, August 4, 2009, 4:36 PM (1636)\nEND TIME: Tuesday, August 4, 2009, 5:11 PM (1711)\nDESCRIPTION: The WCC building has lost power. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=400&proj=75 END:VEVENT BEGIN:VEVENT SEQUENCE:1 DTSTART:20090924T233001Z SUMMARY: 416 IP Grid sw4.wcc.iu.teragrid.org Brief Outage Resolved DTEND:20090924T233301Z DESCRIPTION:TICKET NUMBER: 416\nOUTAGE TYPE: Software\nAFFECTED: sw4.wcc.iu.teragrid.org\n\nSTART TIME: Thursday, September 24, 2009, 11:30 PM (2330)\nEND TIME: Thursday, September 24, 2009, 11:33 PM (2333)\nDESCRIPTION: IP Grid Idataplex switch was briefly unavailable to the community. IP Grid engineers were contacted and the reason for the outage was due to a system crash. All services has been restored. URL;VALUE=URI:http://tick-indy.globalnoc.iu.edu/ticket/view.cgi?tick=416&proj=75 END:VEVENT END:VCALENDAR