WP4 Activity Plan Romanian Education Network RoEduNet

1
WP4 Activity PlanRomanian Education Network -
RoEduNet

• Eduard Andrei - eandrei_at_roedu.net
• Dan Nae - dann_at_roedu.net
• Octavian RUSU - octavian_at_iasi.roedu.net

2
Description of Work

• Project objectives
• To implement the regional networking
  infrastructure that will connect to the
  pan-European network the regional NRENs
• To maintain the infrastructure in stable
  operation
• Total allocated men-months 4.43
• Project duration 10 months

3
Work Package Participants

• RoEduNet - Lead Contractor - 1.14 men-months
• HUNGARNET - 0.84 men-months
• GRNET - 2.45 men-months

4
WP4 Deliverables and Milestones

• Deliverables
• D12 - Implementation and acceptance tests
• D14 - SEEREN configuration and performance
• Milestones
• M12 - Operation of the regional networking
  infrastructure offering to all NRENs GEANT
  visibility
• M13 - Stable network operation

5
WP4 Activity List

• 4.1 Define acceptance tests
• 4.2 Deliver equipment and connections
• 4.3 Adjust equipment configuration
• 4.4 Technical support in stable operation

6
WP4 Detailed Activity Plan

• Acceptance tests for links and equipment
• Equipment configuration and deployment
• Initial test period
• Transition to production state
• Performance monitoring
• Additional services
• Technical support and problem solving

7
Acceptance tests for links and equipment

• Deployment of links from the contracted service
  provider
• Delivery of equipment from the contracted
  supplier
• Initial carrier tests on BER and link
  availability to pass minimum requirements (99
  availability and 10e-12 BER)
• Initial equipment testing to detect
  software/hardware problems, as well as
  software/hardware compatibility with the network
  design.
• Activity duration 1 month

8
Equipment configuration and deployment

• The configuration should provide the minimum
  requirement all NREN connectivity to GEANT
  (including any future connected NRENs e.g. RENAM)
• The equipment configuration should allow for
  various extended services multicasting, QoS,
  IPv6
• The initial configuration and deployment of the
  equipment may require some travelling for on-site
  installation
• Training of all NRENs personnel on the
  configuration and operation of equipment (online
  or face-to-face) as well as documents on the
  implementation available online
• Activity duration 3 months

9
Equipment configuration and deployment (contd)

• GEANT connectivity should be provided to all
  NRENs
• As stated in the DoW document (Annex 1) the
  additional traffic should not cause problems to
  the existing GEANT connections (an estimated
  total of 17 Mbps, which can be supported by any
  of the existing GEANT links)
• Redundant links (if any) should be taken into
  account for load balancing and rerouting traffic
  in case of a link failure
• If the regional NRENs (the ones already connected
  to GEANT) have direct links connecting them,
  routing policies should be configured to insure
  redundant connectivity to GEANT for all NRENs

10
Equipment configuration and deployment (contd)

• The EGP routing policies should be similar to
  GEANT routing policies (communities,
  import/export policies, etc)
• Additional EGP policies should be considered and
  accepted by all NRENs
• The IGP of choice should be configured on all
  routers (OSPF, IS-IS) to allow for load sharing
  and redundant links.

11
Equipment configuration and deployment (contd)

• Additional services should be delivered to all
  NRENs
• Multicast should be enabled on all routers
• QoS required for sensitive applications and
  congested links. All routers should have at least
  a common DSCP marking policy, and a traffic
  shaping policy to reserve bandwidth for specific
  applications
• VoIP - as telephone costs are very high in SEE,
  VoIP should be provisioned on all routers, for
  basic troubleshooting calls, voice meetings, etc.
• IPv6 for testing

12
Initial test period

• After the deployment of the equipment, a short
  test period will ensure the proper operation of
  all links and equipment
• During the test period additional tests will be
  run to verify the operation of links and
  equipment (ping tests, simulated traffic loads,
  simulated link failures)
• This is an extension of the acceptance tests
• Reports on the test results will be made
  available on-line
• Eventual equipment configuration changes will be
  made
• Necessary phase prior to going into production
  state
• Management and monitoring tools should be in
  place by now
• Activity duration 4 months

13
Transition to production state

• Going from test phase into production state
  shouldnt pose any problems but
• Connectivity should be verified for all NRENs
  (internally and to GEANT)
• Traffic load on all links should be checked
  (congestion gt upgrades?)

14
Additional services

• Additional services (DNS, mail relay, ftp, web,
  LDAP, etc) can be offered by any/all of the
  participating NRENs
• The task of administering the .seeren.org domain,
  along with its public services can be distributed
  among the participating NRENs.

15
Performance monitoring

• The monitoring tools should be installed during
  the initial test phase
• basic SNMP monitoring will be performed on all
  routers for all NRENs
• flow analysis tools (if the routers support it)
  flowscan/cflowd for detailed analysis
• additional monitoring tools if needed
• online reports and graphs should be made
  available for all NRENs

16
Technical support and problem solving

• Each NREN should have at least one person that
  can be contacted in case of an emergency.
• The contact person should be able to solve most
  of the problems that arise
• basic communication tools e-mail, phone, fax, an
  maybe IP phones
• Implementing a trouble ticketing system (with web
  interface and support for mail messages)
• Mailing list for technical issues and problem
  reporting
• Activity duration until the end of the project
  and beyond

17
Problem - loss of connectivity

• Can be tackled with if there are redundant links,
  and the routing policy should provision for this
  situation
• The link failure should be signaled to the
  contracted carrier by any of the link ends
• The links should maintain the 99 availability
  rate

18
Problem - DoS Attacks

• Very common problem in todays networks
• Can be equal to loss of connectivity if you are
  unlucky
• Can be detected using various tools (flow
  analysis, network based sniffers, etc).
• Can be signaled to the upstream NREN using BGP
  communities to be automatically filtered

19
Problem solving

• All other problems must be solved using basic
  communication tools
• e-mail, phone, fax
• mailing list(s) for support questions
• trouble ticketing system