Network 'Wizard' Office Hours

Internet2's End-to-End Performance Initiative (E2Epi) worked with the University of Michigan to host the NSF-funded Bridging the Gap Workshop in August, 2005. One outcome of this Workshop was the development of Network 'Wizard' Office Hours, where attendees with long-standing, complex, end-to-end performance problems could bring them to a group of experts who would brainstorm possible solutions.

Prerequisites:

• The problem must be long-standing, preferably one that has foiled repeated attempts to solve. Ideally, the problem is one that spans more than one campus and has existed for more than 3 months. It can be interrmittant.
  
  
• The problem submitter must line up various campus IT staff to help implement the solutions, in real-time, as they are suggested by experts. This allows the experts to validate or eliminate solution paths. Campus IT support staff must be willing participants in the process.
     
• The problem should be submitted at least 2 weeks before the session, preferably 1-1.5 months in advance. The details that should be included in the submission include the name and telephone number of the researcher involved; the name and telephone number of their departmental IT support staff; the name and telephone number of a campus networking engineer (preferably one that has been consulted on this problem; and the details about how the problem presents itself. Also, a list of all (or as many as can be recalled) of the potential solutions that have been attempted would be extremely helpful.
  
  Because the time for this process is limited (usually 1.5 hours at a time, 4 times each year), problems that might have an affect on a wide audience are given priority. (However, interesting problems are always sought!) In the event that your problem is not selected for an upcoming meeting, suggestions for solution via email will be provided.
  
  
• The problem submitter accepts that a description of the problem and eventual solution will be posted (possibly as a case study), anonymizing distinguishing characteristics but making the problem and solution available to everyone.
  

Outcomes:
Problem(s) presented at each session will be followed through to solution; if a solution cannot be determined during the session, the problem will be discussed via email by interested experts until a solution is found. A case study of the problem may be created; however, at the very least, the problem will be documented and posted, minus distinguishing details as to the researcher name and campus. Positive feedback by those involved will generate interest by others; new problems will be submitted and, over time, many problems that are troubling wide audiences will be addressed and documented.

Participation Details:
The problem should be submitted to Susan Evett, Performance Architecture and Technologies, Internet2 at least 2 weeks before the scheduled meeting (1-1.5 months in advance is ideal). A confirmation email will be sent out and additional detail collected, where appropriate. If the problem is selected for work at the upcoming Network Engineer Office Hours session, a representative of the problem community must be present (registered) at the Internet2 meeting and present at the session; in addition, at least 1 member of the campus IT support team must be available, via phone, during the session to implement suggestions and provide additional detais on what has already been attempted.

Next Sessions:

1. Winter 2006 Joint Techs -- February 7, 2006 -- Albuquerque, New Mexico
2. Internet2 Spring Member Meeting 2006 -- April 23, 2006 -- Arlington, Virginia