KAREN wiki

KIWI ADVANCED RESEARCH AND EDUCATION NETWORK

National Education Network Phase 2

From KAREN wiki

Jump to: navigation, search

Contents

Background

Phase 2 of the NEN trail expanded the NEN from a concept to a reality. During this phase, REANNZ connected a number of schools and content and service providers to KAREN, to test the architecture developed in Phase 1 and explore some of the pedagogical benefits of high speed broadband. Phase 2 included a number of stages:

  • 2A - connection of initial schools and content and services partners, July - December 2008
  • 2B - extension of connectivity for initial schools and content and service partners, and expansion to a few new schools, December 2008 - June 2009
  • 2C - extension of connectivity for all participants, July - December 2009

National Education Network Phase 2 Objectives

The objectives of the NEN trial Phase 2 are to:

  • Connect to KAREN a range of educational entities such as Schools, Institutes of Technology and Polytechnics (ITP), Wananga, through Aggregators.
  • Connect and trial a range of educational services, from MoE defined Service Providers, to these education entities.
  • Demonstrate the proposed NEN architecture can be delivered to schools and the NEN architecture, as proposed during Phase I, functions as envisaged.

The outcomes of this project are:

  • Validate and learn the about the NEN architecture
  • Deliver educational services over KAREN
  • Learn issues –technical/commercial/ governance/ support arising from the NEN trial that can be applied as future learning points
  • Demonstrate and prove benefits of the NEN
  • Validate the integrity of the architecture and services through test cases and rigid testing
  • Document the results.

This proof of concept began mid July 2008 and ended December 2009.

Participating schools / services

NEN phase IIB schools

  1. Appleby School
  2. Christ's College
  3. College Street Normal School
  4. Collingwood Area School
  5. Hunterville Consolidated School
  6. Kristin School
  7. Mangamaire School
  8. Nayland College
  9. Nelson College for Girls
  10. Palmerston North Boys' High School
  11. Palmerston North Girls' High School
  12. Pt England School
  13. Southwell School
  14. St Mary's College
  15. The Correspondence School
  16. Wellington College
  17. Wellington East Girls' College
  18. Wellington Girls College
  19. Wellington High School

NEN phase IIC additional schools

  1. Mangatainoka School
  2. Pahiatua School
  3. Taihape Area School
  4. Tararua College

The Ministry accepted, as offered in NEN PIIB, four licences for Content and Service partners (CASP) for the duration of PIIB.

The nominated CASP’s are:

  1. Ministry of Education
  2. e-cast
  3. LERN
  4. Edtech

The existing Content partners i.e. TelstraClear, Te Papa, National Library, Christ College, KAREN Video Conferencing Service etc will remain in place.

Teaching and Learning Outcomes

At the same time as we achieve NEN outcomes, we are taking the chance to test and hopefully prove the value of certain teaching and learning outcomes across the ITPs and the Schools. TEC and MinEdu have driven these outcomes.

School outcomes

CORE Education has been contracted by the Ministry of Education and REANNZ to undertake a small-scale evaluation project to demonstrate the pedagogical benefits of being linked to the advanced network (KAREN), delivering the National Education Network (NEN). The following outcomes are identified for the proposed programme: A new proof of concept (PoC) school, after being connected, is able to articulate the 
 benefits of being connected. 
 A new PoC school can point to one or more specific activities that have been made possible by being connected. 
 It is expected that the evaluation will be used to encourage and promote a deeper understanding of the role that ICT and advanced network technologies can play in the provision of 21st Century teaching and learning programmes as provided for within the NZ curriculum. CORE has engaged Suzi Gould to coordinate the evaluation, and she will work with Derek Wenmoth and Allan Sylvester to engage with the teachers and schools who are a part of the NEN trial during the first part of term four. In designing the evaluation process emphasis will be given to the following:

  • Identifying and understanding the pedagogical intent and implementation of the various uses being made of the network
  • Activities that are intended to promote collaboration among learners and/or teachers
  • Examples of use of ICTs to support teaching and learning
  • Outcomes of the existing projects and initiatives that have been planned as part of the NEN trial.

A key focus of the evaluation project will be the gathering of evidence and artifacts that will endure beyond the time-frame of the project, and remain available to inform future projects. These will include:

  • video interviews with students, staff and principals which will be made available online through EdTalks
  • online artefacts (illustrating student work) made available via an online repository
  • participating teacher and student blogs providing the story of the project in each context

The evaluation work will occur in a variety of ways, including face-to-face meetings and audio and video conferences with participating teachers. These interviews should not be too time consuming, and will focus on work that has already occurred as well as projects that are still running in term four. Teachers in participating schools will be contacted early in the new term to arrange times for visits or linking by audio or video conference. Key contacts: [derek@core-ed.net] or [suzi.gould@learn-it.co.nz]

ITP outcomes

Test the value in the following three areas that in turn support Tertiary Education Strategy:

  • ITP teaching resources sharing / shared course development and delivery
  • ITP back-office support sharing
  • ITP-to-school integration

Project learnings

Service turn-up

Connecting up Schools, Service and Content providers and aggregators for the National Education Network trial has demonstrated that this connection process is a bespoke, sequential and relatively complicated. The internal REANNZ process for completing a “single site connection” request is initiated when the connection information is received in accordance with [connections@reannz.co.nz]

REANNZ requests that the “single site connection” form needs to be completed in full. Missing detail has resulted in site connection delays and, potentially,non-compliance with KAREN standards.

The following information is requested for every connection.

  • Physical and logical design diagram of existing network.
  • Physical and logical design diagram of proposed network.
  • The single site connection information is completed.

Most fields in the “single site connection” request form need to be made mandatory before the connection process will commence. An update to that form has been drafted. This may assist the current process but may not solve the root core problem. A number of issues within the connection process are apparent at this early stage and all need assessment.

The connection process has inherent delays because of not only REANNZ Service Level Agreements (SLA) and in addition the SLA’s of the outsourced third party equipment also adds to the timeline and coordination requirements. As an example any physical or logical MAC update to the KAREN core has a 10 and 5 day lead time requirement with TCL. The cumulative effect of the SLA’s involved in any one connection makes for unacceptable time frames when considering the overall time to connect up a NEN entity.

Most of the new NEN trial customers have experienced connection difficulties. Due to…

  • Lack of technical knowledge required to provide the information sought as required by the current connection process.
  • Lack of understanding of who is responsible for what and what equipment is being supported by whom, makes for a very confused environment. This seems to be worse when services are outsourced.

In summary. The NEN connection process must be improved and simplified and not assume detailed technical knowledge is necessarily available for all NEN educational participants. This area needs a careful holistic analysis and a relevant solution.

Service Provider Issues

  • Existing hardware has been found to be at full capacity requiring upgrades or new hardware to be purchased, this has often come as a surprise and has delayed NEN trial users from connecting.
  • Delays in loan hardware being sourced installed and configured have added to timeframes.
  • Lack of understanding of BGP and multicast has often delayed connections.

MultiCast=

Work is progressing on providing DW German TV over KAREN for the NEN trial. It is planned to distribute this content as multi cast stream originating from Christ College in Christchurch. The provisioning of this content along with the ability to receive DW TV has raised a number of multi cast issues. Some comments arising follow:

Some equipment connected / connecting to the NEN appear not to adhere to the KAREN multicast standards and specs. The requirements are.

  • MUST support MBGP on the edge router
  • MUST support PIM-SM on at least the edge router
  • MAY require support of MSDP on the edge router

There seems to be a lack of technical understanding around multicast. Possibly because multicast has not been widely used commercially in New Zealand. Some of the loan and new hardware being connected to KAREN as a compliant edge device appear not comply with KAREN BGP and multicast standards.

Equipment Configurations

It is intended to build up a repository of technical information, initially router configurations, that have been deployed by organisations connecting to the National Education Network.

The Technical Centre at the KAREN website contains details and standards of the technical requirements for connecting to KAREN and the National Education Network (NEN).

It is necessary to meet these standards to be considered a compliant connection. Organisations considering connecting to the NEN should clearly understand their technical requirements and obligations. If you are in any doubt please seek professional assistance.

Please note:

  • REANNZ does not recommend nor approve any technical devices or their configurations
  • The posting of this information on the REANNZ NEN Wiki site does not imply any form of endorsement by REANNZ
  • REANNZ accepts no liability in respect of any direct or indirect loss or damage from the use and application of the information contained on this wiki site or otherwise

Nelson Loop connection recommendations

Connecting to KAREN – Technical notes for schools

  • DNS

Ensure you have access to your External DNS provider / self service portal If using an ISP you can schedule the DNS record changes to be enabled at a certain time to allow you to perform the cutover to KAREN out of hours Allow up to 24 Hrs for world wide DNS to converge / update. Employ an intermediate DNS server to allow redirection of non reachable websites / resources on KAREN back to the common internet addresses.

  • Routing

Avoid asymmetrical routing. This can be caused by firewalls and / or multiple gateways. Symptoms of this problem are strange communication errors between certain types of mail server and FTP sites losing their connection.

  • Mail delivery

If your mail server supports it you can make use of the MXCACHE file to temporarily deliver mail where DNS is incorrect. Remove RDNS antispam methods until you have time to monitor mail queues and fine tune antispam again. Add a temporary secondary mail server on the ‘old’ public network as a relay to deliver mail which is undeliverable via the KAREN network. This will allow you to keep mail flowing normally overnight when unmonitored and reduce administrator pressure. Ensure your RBL lists are contactable via the KAREN network otherwise mail could be lost depending on you antispam settings.

A strategy for a pilot connection to KAREN

  • Email

Setup a mail server with a verbose console (Ex: Mdaemon trial) on a machine connected to the Karen network. Setup this machine to use KAREN DNS and allow it to relay mail from your existing mail server IP only. Set your existing mail to temporarily relay outgoing mail via the Mail relay and monitor delivery queues. Ensure you have registered a RDNS record for your mail relay. Test and monitor email delivery. Remove the mail forwarding if undeliverable queues build faster than you can troubleshoot them.

  • Web Access

Setup a proxy server with a KAREN public IP / DNS and direct a proportion of users to use this for web access. Test and monitor.

Nelson Loop specific problems

Management events and recommendations

This is a sequential log of problems and the solutions encountered when joining KAREN whereas the technical paper is a set of recommendations.

  • Problem: Schools still do not know what is on KAREN. Very difficult to get the schools to understand what is happening. Principals will not approve expenditure when the advantages cannot be displayed clearly. Suggest: A web page on what KAREN is and what is there so Principals and techs can be educated. This has been implemented by KAREN and been a great success.
  • Problem: There is confusion over what is commercial and non commercial as far as KAEREN is concerned. This confuses the commercial suppliers of services to schools. If the venders are confused then schools also get confused. Suggest: KAREN defines these services with examples.
  • Problem: IAM: -A real concern. The techs are worried that when schools join all users will have access to the likes of EVO. Schools currently do NOT have external IAM systems and cannot regulate access to such sites as EVO easily and quickly, NLS etc. Schools have signed an AUP but they are unaware they cannot enforce it without assistance.
  • Problem: Documentation: We had for send copies to KAREN several times. Suggest a web page when schools can sign on a progress record kept so everyone knows.
  • Problem: Had to change external DNS & MX records. Some schools did not have passwords to their hosting agents. Suggest: That a checklist be made available to schools joining KAREN (See technical recommendations)
  • Problem: Techs became confused when several people (KAREN) tried to communicate with them. Suggest: A technical liaison person be assigned to each school/aggregator so that there is no mixed messages. This has been implemented by KAREN and been a great success.
  • Problem: When a school changes their external IP address then there a number of agencies that needs to be informed. Suggest: That a checklist of these agencies be made up and published on one of the above sites (SCID, ASSNET, Watchdog, E-cast, Users of remote access, VPN and emails, School ICT support etc). This is really a school management not a KAREN issue.
  • Problem: School are not sure if they are on KAREN. Suggest: Need a easy web site that test connectivity, DNS and connection speed on KAREN - sort of a connection weathermap. The test utility supplied by KAREN is ideal. It would be even better if it could detect if the ‘presence’ of KAREN on the test and come up with the appropriate page if the user is not on KAREN. Currently it just doesn’t work if the school is not on KAREN leaving the user in the dark as to their KAREN status.
  • Problem: Routing to Google: The Loop found the routes to Google did not work and it found afterwards that there was a problem here. Suggestion: That this type of problem be noted on one of the above web pages so we all know.
  • Problem: Routing to Microsoft: The Loop found the routes to Microsoft did not work and it found afterwards that there was a dead route there Suggestion: That this type of problem be noted on one of the above web pages so we all know. KAREN is now sending informative email to the Loop management. The Loop management posts this onto the Loop Intranet. An ideal solution- all sorted
  • Loop problem: The Loop does not have a KAREN firewall that passes multicast traffic. KAREN records did not show this and confusion resulted at times. Suggest: The above web page (see 4) holds this information so all parties are aware of the problems and restrictions. The Loop is becoming very aware of the potential benefits of multicasting especially in the relation to its existing internal video archiving service.
  • Insist on doing schools all at once rather than a number of steps. This makes life confusing. Subnet management would be much easier if we shifted the whole Loop at once.
  • DNS suggestions: Suggest: That the Loop encourages everyone to shift their MX and DNS records to the Loop. Suggest: We make a self editing DNS script where schools can change the external DNS themselves. The Loop is encouraging this to happen so when the rest of the schools do join KAREN then it will be much more manageable. Progressing well.

NEN Phase 2 Findings

The National Education Network Proof of Concept (PoC) Phase 2 came to a conclusion at the end of December 2008. The NEN PoC PII culminated with a video conference (vc) that involved a number of participants including Appleby School, Mangamaire School, Wellington College, Wellington GHS, Christ College, Kristin School, ARNET,Pt England School, National Library and REANNZ. This celebratory session was managed by Core Ed as part of their contract with REANNZ. The objective of the celebration was to bring a number of parties together to share their experiences of being connected to the NEN. This vc took place on the 11th December and was considered a success based on the feedback received.

A prior vc occurred on the 10th December with Mangamaire School, REANNZ, the Taraura District Council and local people, InspireNet and with invited personnel from TUANZ. Mangamaire School is a primary School with 44 students and has recently been connected onto an InspireNet fibre. Mangamaire School participated in this vc using a PC, Mirial licence and a low cost web cam. The vc demonstrated that low end and low cost equipment can provide a meaningful vc experience when the upstream bandwidth is not constrained i.e. on the NEN.

Outcomes

The NEN PII has delivered a number of strategic outcomes. In summary:

  • The designed NEN architecture has been proven to be appropriate, with some minor elements for improvement identified
  • A detailed insight into the nature of supplier and member capabilities has been gained, which will inform some of the design parameters for the scale-up of a full NEN deployment
  • The viability of centrally provided and nationally available services over an NEN has been proven
  • Participants have been enabled to collaborate, achieve efficiencies and explore new teaching and learning practices that were previously not possible.
  • The Ministry of Education has authorised a NEN PIIB. This allocates a limited amount of money to maintain the gains achieved with NEN PII. In summary the REANNZ fees of the following Schools will be paid by the Ministry of Education until July 2009.

NEN trial reports

National Education Network Phase II report - January 2009

National Education Network - 21st Century Learning Challenge report - January 2009

NEN Evaluation website: CORE Education