June 2008 - Outages - Outages Lists

Outages Mailing List Update.
by virendra rode // 03 Jul '08

03 Jul '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello All, First off I would like to thank everyone for their patience during the transition period of isotf.org over to Jared's host (puck) and his willingness to even help after repeatedly nagging and trying his patience primarily by me. As Jared mentioned there are still a couple more things that needs to be hashed out (behind the scenes) while outages mailing list function to operate normally. We will give outages mailing list a few more weeks to operate under isotf.org after which we will be looking at making one final transition (in parallel) to outages.org domain as mentioned in my earlier e-mail. Along w/ its new identity we will be looking at setting WIKI for documentation purposes as discussed earlier. Once again, we will be counting on the network operator community for help in order to make outages wiki resourceful and meaningful so everyone can benefit from the outcome. We will be communicating more on this in the weeks to come. Like always, I'm open for suggestions / feedback. Many thanks to Jared Mauch, Gadi Evron and Randy Vaughn for their relentless help during this migration. regards, /virendra -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIYCPLpbZvCIJx1bcRAvntAJ4uHcxL10hjxHlhwyVgNODdj3LrXgCePCPt vvWgVS0zQqhiOT7wUlZ0J2E= =kXxk -----END PGP SIGNATURE-----

8 10

FW: Level 3 Service Affecting Maintenance - GCR# 201002 - SCHEDULED MAINTENANCE ADVISEMENT, CWIE, LLC
by Raman Sud 27 Jun '08

27 Jun '08

Raman Sud Director, Network Engineering and Operations CWIE Holding Company 2353 West University Drive Tempe AZ 85281 Fax: 480.682.3236 http://www.cavecreek.net/ PGP Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBB765DA2 NOTICE: This message is intended only for the use of the individual or entity to which it is addressed. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the sender of this E-Mail or by telephone. ________________________________ From: maint_advisory(a)level3.com [mailto:maint_advisory@level3.com] Sent: Friday, June 27, 2008 12:48 PM To: todd(a)bandcon.com; steve.cordova(a)level3.com; Networking; helpdesk(a)bandcon.com; Networking Subject: Level 3 Service Affecting Maintenance - GCR# 201002 - SCHEDULED MAINTENANCE ADVISEMENT, CWIE, LLC Importance: High Level 3 Communications - Network Change Control (NCC) ***Scheduled Maintenance Advisement*** Level 3 Service Affecting Maintenance - GCR# 201002 - Scheduled We have scheduled this Scheduled Network Maintenance Period for: CWIE, LLC GCR# 201002 Start Date & Time: Sunday, July 13, 2008 00:00 CT (7/13/2008 05:00 GMT) End Date & Time: Sunday, July 13, 2008 06:00 CT (7/13/2008 11:00 GMT) Reason for Maintenance: Level 3 adding traffic back to ipcolo-sw1.chi1 4/2 to metro-sw1-chcgilcp80w.chi1 1/2. During this process, there is a possible spanning tree loop issue that would effect traffic. If after this maintenance is completed and you have circuit problems, please phone 877-453-8353 opt. 2, opt. 2 and open a ticket, so that we can correct the problem. Location(s): Chicago IL, Services Impacted: Service Impacted Expected Impact Duration IP - Non-Redundant None N/A IP - Redundant None N/A Circuits Impacted: Circuit ID Service Type Order Number Impact BBBL01704 metro-sw1-chcgilco80 3/6 1000-LX/LH FYI: possible spanning tree loop Comments: Clarify Case#: 2638427 Contact Information: Business Hours: Monday-Friday 7AM-5PM CT Phone: 800-850-4095 opt 2 After Hours: Phone: 877-453-8353 Outside the US: Phone: 1-720-888-0229 E-mail: <mailto:maint_advisory@level3.com> maint_advisory(a)level3.com Special Notes Concerning Service Impact: Level 3 Communications will make every effort to minimize the impact, however, unforeseen circumstances could cause a larger impact. Thank You, The Maintenance Advisory Team

1 0

List comment
by Christian Blair 25 Jun '08

25 Jun '08

We can keep this list usable if used sparingly. We don't need everyone's traceroute. Hardly useful for others anyway unless they're your roommate. Post your outage. Move on with your day. Leave the traceroutes for off list interchange.

16 16

back to business please..
by Gadi Evron 24 Jun '08

24 Jun '08

I realize it takes time for folks to read such "stop" emails, but now that we all had time to share our take on the subject, members are requested to take meta-discussion off-list. I believe we have partial concensus that we prefer to hear about actual outages, and that discussion should not be "outlawed" quite yet, but self-moderation is encouraged. We know this model works from the past few months, now that the list is kindly hosted by Jared on puck, things should return to normal, and we will see how things go from here. Gadi.

1 0

Re: [outages] List comment
by Scott Weeks 24 Jun '08

24 Jun '08

---------- dyork(a)lodestar2.com wrote: -------------- >> We don't need everyone's traceroute. >> Hardly useful for others anyway unless they're your roommate. I don't have a great solution to offer... I think the "community" here is probably too new to split into separate "alerts" and "discussion" lists. I also personally don't care which type of list it is. But I would suggest this difference in expectations is perhaps at the route of the original comment and others that have been on the list. --------------------------------------------------------- When a subject becomes uninteresting to a person, all he/she has to do is select based on the subject line and mass delete the thread. It's not too hard. I don't think the list has enough momentum to fragment it already. It would be nice, though, if folks could clean up the traceroutes a bit before posting. For example, remove the delay times when just showing there's connectivity to a particular destination. Many traceroutes are a hard to read mess. scott -----------------------------

2 1

Re: [outages] List comment
by Brandon Butterworth 24 Jun '08

24 Jun '08

> I think the question really is - is this list designed for *reporting* > and confirming outages? Or is it designed for *diagnosing*/discussing/ > troubleshooting outages? I understood the former. It's called outages I want my outages pure and simple and not cut with possible outages "is teh interwebs broken, btw I can't print either" :) There's enough noise and html already I was considering giving up but the move to puck gave me hope it'll evolve into something useful to me. If it doesn't then no problem it's probably useful to someone else. regards brandon

6 5

Re: [outages] List comment
by Scott Weeks 24 Jun '08

24 Jun '08

------- virendra.rode(a)gmail.com wrote: ------------ Now if providers could be little more forthcoming and start reporting their maintenance and outages then sure I can see those alerts being filtered into something like 'outages-alerts' but until that happens I think we may need to feel the list further. --------------------------------------------------- I wouldn't hold my breath for that. You might turn awfully blue... ;-) scott -----------------------------

1 0

Notice/discussion
by Diggs, Lois 24 Jun '08

24 Jun '08

>From my perspective, both the initial reporting and the subsequent discussion of an outage are useful. Lois M. Diggs, Lt Col, VTANG 229 IOS/CC (802) 485-1975 DSN 636-4975

1 0

routing loop in cogent?
by Josh Fiske 23 Jun '08

23 Jun '08

Is anyone else seeing some routing loops in Cogent's network? ala: ... 18 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.475 ms 36.336 ms 34.087 ms 19 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.286 ms 38.188 ms 37.530 ms 20 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 33.148 ms 37.066 ms 35.823 ms 21 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.403 ms 37.534 ms 22 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.051 ms 33.120 ms 34.209 ms 23 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.112 ms * * 24 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.603 ms 34.994 ms 34.119 ms 25 * uslec.iad01.atlas.cogentco.com (154.54.11.214) 36.929 ms 38.443 ms 26 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 34.784 ms 35.317 ms 33.839 ms 27 uslec.iad01.atlas.cogentco.com (154.54.11.214) 37.185 ms 38.327 ms 39.863 ms 28 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.362 ms 36.451 ms 34.788 ms 29 uslec.iad01.atlas.cogentco.com (154.54.11.214) 38.600 ms 39.782 ms 40.031 ms 30 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 38.156 ms 39.726 ms 35.726 ms 31 uslec.iad01.atlas.cogentco.com (154.54.11.214) 47.281 ms 37.617 ms 49.460 ms 32 gi9-16.mpd01.iad01.atlas.cogentco.com (154.54.11.213) 35.389 ms 35.988 ms 35.609 ms 33 uslec.iad01.atlas.cogentco.com (154.54.11.214) 39.162 ms 121.744 ms^C - - - - Joshua Fiske '03, '04 Network and Security Engineer Clarkson University, Office of Information Technology (315) 268-6722 -- Fax: (315) 268-6570 GPG Key: http://clarkson.edu/~jfiske/jfiske_pub.asc jfiske(a)clarkson.edu CONFIDENTIALITY: This e-mail (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this e-mail in error, please notify the sender and delete this e-mail from your system.

9 9

Re: [outages] [Outages] Fisher Plaza Power Outage
by Sean Donelan 23 Jun '08

23 Jun '08

On Sun, 22 Jun 2008, Alex Rubenstein wrote: >> I like Sean's version better, though: >> >> http://www.donelan.com/design/general.html > > With all due respect for Sean, his version does not address specifically > the systems analysis need that should be used to install a datacenter to > meet a given criteria. > > After looking at Sean's thing more closely, that is not a guide of > design, but instead a description of goal to reach. You'll noticed that particular page is labeled "general." That page is as you describe, the general goals to reach. But having a "general" page may also imply there are other pages which identify specific system design elements and choices you may make ranging from siting, architectural, civil, electrical, mechanical, piping, operations and maintance, fire and safety and so on. You would probably end up with a book a couple of hundred pages long. My purpose with publically posting the "general" page was to respond to the question people used to ask me. How do you design a data center, and my answer was "What's you goal for the datacenter." There isn't one goal for a data center, so there also isn't one data center design. People kept getting hung up on whether a data center was N-2+3^0 redundant; and not spending the time figuring out their actual goals. Depending on your goals, one super data center may be appropriate for you, or a few cheap data centers in different cities may be appropriate for you, or something completely different may be appropriate for you. But in any case, start the discussion about what you are trying to achieve.

1 0