1 / 12

Operations in HEAnet

HEAnet's NOC, managed by Brian Nisbet, leverages a team of over 30 technical staff, with 75% involved in NOC duty, serving 60+ clients. The operational framework includes a robust Layer 2 network, Bluenet, equipped with integrated provisioning tools that enable automated link provision, monitoring, and alerting. The Layer 3 core features Cisco CRS-1 routers and employs BGP for client connectivity. Expanding services and automation are key focus areas, driving improvements in service delivery and operational efficiency across HEAnet's extensive network infrastructure.

gilles
Download Presentation

Operations in HEAnet

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Operations in HEAnet Brian Nisbet NOC Manager

  2. Operational Overview • 30+ Technical Staff. • 75% of whom participate in NOC Duty. • 60+ Clients. • Expanding Services Catalogue. • 400+ L2 P2P circuits. • 120+ iBGPpeerings, across 80+ physical circuits.

  3. What’s a service? • Everything is a service! • General Internet Service is the core HEAnet offering. • Many, many services on top of the network, more user interaction. • Increasing size has lead to increased need for automation across all services.

  4. Layer 2 Network • Layer 2 network (called Bluenet) was built with with an integrated provisioning tool. • Automatic provision of links, monitoring & alerting. • Complete database of all links. • Basic config put on switch, topology tool uses CDP to find switch, then allows for automatic provision. • Some early issues, but none for many years.

  5. Layer 3 Network - Core • 2 core routers (Cisco CRS-1s), 2 route reflectors (Cisco 7301s). • CPE devices are a mixture of Cisco & Juniper devices. • Not all CPE controlled by HEAnet. • IGP running on CRSes & 7301s. • OSPF for IPv4 • IS-IS for IPv6 • Soon to be IS-IS for all • eBPG to external peers.

  6. Layer 3 Network - Clients • 2 x iBGPpeerings per client. • One to each Core router. • Private ASes used in nearly all situations. • Default network sent to clients. • Client routes: • Advertised by network statements • Controlled by prefix-lists on both CPE & Core. • BGP config mandated by HEAnet.

  7. Layer 3 General Internet Templates • Two links per client, different local prefs, different MEDs. • Link addresses pulled from predefined pool. • Templates used where possible (and by now, it’s possible everywhere). • https://wiki.heanet.ie/BGP_Design,_Customer • Conformity/mandating the BGP config has improved things greatly.

  8. Other Layer 3 Services • Not just one network on the network. • Other services still follow template model where possible. • Large amount of work, both operational & political goes into keeping this sane.

  9. Equipment • Over 80% of CPE supplied by HEAnet. • Unlikely to ever reach 100%. • Client needs, exceptional circumstances etc. • Templates need to be adaptable to major vendor code. • So far only IOS, IOS-XR & JUNOS.

  10. Wish List • Ultimate aim would be to make L3 network more like L2. • Several different models: • Tool creates config, manually applied. • Automatic config, applied in staging area. • Virtual CPE, whole config automatic. • Initial config manual, basic connectivity, links automatic. • Config templates always useful.

  11. L3 Provisioning Tool • Pool of link addresses & private ASes. • Grab the next /30 & /64 • Client networks – access to routing registry? • Multiple types of link. • General Internet – Pool A • Special Network – Pool B • Temporary Network – Pool C • Short term virtual routers. • L2 port becomes entry point to new network.

  12. L3 Provisioning Tool • DNS • Monitoring • Graphing, alerting, configuration • Management • Access control, ACL applications & updates etc. • Mapping

More Related