ARNES Joe Hanc Arnes, Ljubljana, Slovenija joze.hanc@arnes.si - - PowerPoint PPT Presentation

▶
arnes
SMART_READER_LITE
LIVE PREVIEW

ARNES Joe Hanc Arnes, Ljubljana, Slovenija joze.hanc@arnes.si - - PowerPoint PPT Presentation

Sep 26, 2023 453 likes •659 views

TF-NOC flash presentation TF-NOC flash presentation ARNES Joe Hanc Arnes, Ljubljana, Slovenija joze.hanc@arnes.si TF-NOC meeting, Ljubljana 15. 2. 2011 Network Infrastructure - Backbone Optical backbone Optical backbone

slide-1
SLIDE 1

TF-NOC flash presentation TF-NOC flash presentation

ARNES

Jože Hanc Arnes, Ljubljana, Slovenija joze.hanc@arnes.si

TF-NOC meeting, Ljubljana

  • 15. 2. 2011
slide-2
SLIDE 2

Network Infrastructure - Backbone

  • Optical backbone
  • Optical backbone
  • leased dark fibre
  • 53 PoPs in 30 towns
  • L3 equipment (IPv4/IPv6)
  • Cisco
  • Juniper
  • Optical transport
  • Juniper
  • Optical transport
  • active DWDM: Adva
  • passive CWDM

2

slide-3
SLIDE 3

Network Infrastructure - Backbone

3

slide-4
SLIDE 4

Network Infrastructure - Access

  • 1300 customer’s LANs with L3 connections
  • 1300 customer’s LANs with L3 connections
  • Cisco routers
  • uplinks hired by customers
  • Technology
  • dark or lit fiber to PoPs
  • VPN over FTTH, xDSL and CATV, via service

provider’s networks to main PoP in Ljubljana

  • VPN over FTTH, xDSL and CATV, via service

provider’s networks to main PoP in Ljubljana

4

slide-5
SLIDE 5

Network Services

  • L3 connectivity (IPv4, IPv6)
  • L3 connectivity (IPv4, IPv6)
  • QoS and IP SLA
  • IP filtering (Access Control Lists - ACL)
  • Point-to-Point circuits
  • L2
  • MPLS pseudo wire
  • L2
  • MPLS pseudo wire
  • EPL (Ethernet Private Line)
  • L1
  • DWDM/CWDM lambdas

5

slide-6
SLIDE 6

Management/Monitoring tools

  • Cacti – graphing
  • Cacti – graphing
  • Smokeping – active monitoring
  • Icinga – passive monitoring
  • Syslog – passive monitoring
  • Rancid – configuration repository
  • NDT, iperf – on-demand active monitoring
  • in-house scripts:
  • in-house scripts:
  • routing control
  • multiple equal path detection
  • default route monitoring
  • Observium – passive monitoring, in test phase

6

slide-7
SLIDE 7

NOC structure

  • Three level NOC
  • Three level NOC
  • 1st level – helpdesk
  • 2nd level – network consultants
  • 3rd level – backbone experts
  • non dedicated personnel
  • NOC hats are on when needed
  • NOC hats are on when needed

7

slide-8
SLIDE 8

NOC structure - Backbone NOC

  • One expert available 24/7
  • 3rd level support mainly for backbone and
  • 3rd level support mainly for backbone and

big customers (Uni-LJ, Uni-MB, IJS, GOV)

  • Expertise:
  • intra and inter domain IP routing
  • switching
  • MPLS
  • MPLS
  • optical transmission systems
  • QoS
  • performance issues (PERT)

8

slide-9
SLIDE 9

NOC structure – Access NOC

  • 1st level NOC – helpdesk
  • 5 operators – weekdays 8:00 – 20:00
  • 5 operators – weekdays 8:00 – 20:00
  • 2nd level NOC
  • 3 operators – weekdays 8:00 – 16:00
  • Expertise:
  • intra-domain IP routing
  • switching
  • switching
  • IPsec VPN
  • access technologies
  • xDSL, cable, FTTH, wireless

9

slide-10
SLIDE 10

NOC structure – Joint activities

  • PERT
  • PERT
  • Performance Enhancement and Response Team
  • Backbone and Access NOC involved in:
  • operational procedures
  • net-admin procedures
  • maintenance
  • provisioning
  • provisioning

10

slide-11
SLIDE 11

NOC tools

  • All the monitoring

tools tools

  • Vi
  • Big question:
  • tool integration
  • Goal:

creating a common network information network information base and API for management and monitoring aplications

11

slide-12
SLIDE 12

Front End – Users

Number of connected customers – log scale

53 822 189 14

Research Institutes Secondary, primary schools and preschool education Public libraries , museums and other cultural institutions Government departments

  • estimated 200.000 end users

12

24 1 10 100 1000

Universities and high-schools

slide-13
SLIDE 13

Front End – SLAs and agreements

  • No SLA agreements
  • No SLA agreements
  • monitoring IP SLA parameters on some links
  • We are very much interested in what is

the role of other NOCs between access providers and organizations in term of SLA providers and organizations in term of SLA

13

slide-14
SLIDE 14

Front End – Communication

  • Communication:
  • Communication:
  • e-mail
  • phone
  • Keeping track:
  • Trouble Ticket – proprietary tool
  • OTRS
  • Question:
  • OTRS
  • Question:
  • skilled contact person on customer’s side?
  • education, workshops?

14

slide-15
SLIDE 15

Inter-NOC Communication

  • Inside
  • Inside
  • OTRS, email, IM chat, phone
  • shouting to the nearest colleague ☺
  • Outside
  • email, phone
  • email, phone
  • Inter-NOC
  • email, OTRS

15

slide-16
SLIDE 16

Documentation – What, Tools

  • Network documentation
  • Network documentation
  • organization's data (address, contacts,

equipment, network information)

  • equipment configuration files
  • access provider’s contact information
  • Tools:
  • Tools:
  • Proprietary information system (ARIS)
  • Wiki

16

slide-17
SLIDE 17

Documentation – Best practice

  • Mostly checklists
  • Mostly checklists
  • some were done for transfer of activities to

1st level support helpdesk

  • Bunch of documents, but not structured

(yet!).

  • Short answer
  • Not enough
  • Difficult to keep up-to-date

17

slide-18
SLIDE 18

NREN – NOC questions

  • How to integrate NOC into an NREN?
  • How to integrate NOC into an NREN?
  • Dilemma
  • designated operators for NOC or not?

18