You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

Table of content

Logistics

The meeting is kindly hosted by UNINETT in Trondheim.
The meeting will start Monday at 12:00 CET the 12th of April and end at 13:00 CET the 13th of April.

Recommended hotel

Nova Hotel Kurs og Konferanse.
Cicignons Plass,
NO-7011 Trondheim

Phone: +47 73 80 63 00,
Fax: +47 73 50 20 42
E-mail: booking@nova-trondheim.no

Video conferencing

The video conferencing system (Sony XG 80 HD) is SIP- and H323-capable,
supports H.264 720P and two videosources (H239/"DuoVideo").
The contact details for our videoconferencing solution is:

IP : 158.38.60.244
GDS-number : 004773557891
Phone : +47 7355 7891

Participants

Morten Brekkevold (UNINETT)
Håvard Kusslid (UNINETT)
Jørgen Qvist (NORDUnet)
Vidar Faltinsen (UNINETT)
Juha Oinonen (Funet)
Vegard Vesterheim (UNINETT)
Stefan Liström (NORDUnet)
Jan Ferré (Forskningsnettet)
Tore Kristiansen [UNINETT)

Draft agenda

Monday 12th of April

 

 

Time (in CET)

Topic

Topic lead

12:00-12:45

Lunch (provided by UNINETT)

 

12:45-13:00

Introductions and setting the agenda

NORDUnet

13:00-13:45

OPS forum review

NORDUnet

13:45-14:30

NREN Operational updates

Short presentation from each NREN.

14:30-14:45

Break

 

14:45-15:45

Network Inventory presentations

 

 

NDL

Juha

 

Telemator

Stefan

 

netdb

Jan

15:45-16:30

Discussion about how to proceed
with possible Network Inventory activity

NORDUnet

16:30-17:00

Wrap up of day one

NORDUnet

19:00-

Dinner (provided by NORDUnet)

 

Tuesday 13th of April

 

 

Time (in CET)

Topic

Topic lead

09:00-09:30

Update on TT integration

NORDUnet

09:30-10:00

Update on use of service IDs

NORDUnet

10:00-10:45

NAV demonstration

UNINETT

10:45-11:00

Break

 

11:00-11:20

Pymetric demonstration

UNINETT

11:20-11:40

Multicast beacon discussion

FUNET

11:40-12:00

Wrap up of meeting

NORDUnet

12:00-13:00

Lunch provided by UNINETT

 

Minutes of the meeting

Participants

Håvard Kusslid (UNINETT)
Vidar Faltinsen (UNINETT)
Juha Oinonen (Funet)
Vegard Vesterheim (UNINETT)
Stefan Liström (NORDUnet)
Jan Ferré (Forskningsnettet)
Pekka Savola (FUNET)
Morten Brekkevold (UNINETT)
Tore Kristiansen [UNINETT)
Morten Kuntsen (UNINETT)

OPS forum review

It is good that we have the oportunity to exchange experiences and practice during discussions in this forum. Demos of different tools also help understand how we work and if a certain tool could be useful for others to use.

Not much coordinated development has been done yet, but the concept is still something that would be interesting to do.

It would be good to have more detailed information about tools and procedures. We should try to extend the functions matrix on the wiki.

Traveling to four face to face meetings a year, rotated between the different NRENs can be pressing.

We agreed to hold our meetings in another way. We will still have around four meetings each year, but every second meeting will be on Video conference. One of the face to face meetings each year will be hosted at a central location (i.e. Stockholm or Copenhagen) to make travel as convenient as possible and the second face to face meeting will be rotated among the NORDUnet NRENs.

Something that could be useful to do, would be to try to identify which difficulties we have when cooperating between the different NRENs and try to focus on solving them.

NREN Operational updates

SUNET
SUNET has now finalized the implementation of Telemator as a network inventory.

NORDUnet
NORDUnet has hired a new NOC manager, Fresia Peréz. Stefan Liström will be responsible for Nordic community development, international projects focusing on operations as well as driving key internal NORDUnet strategic and cross-functional projects.
NORDUnet is currently looking into developing their own Network Inventory

UNINETT
Since last meeting there was a large incident in the northern part of Norway. Both a boat and landslide accident affecting the UNINETT network and left the northern part of UNINETT with 155MB connection.
It is very unusual that accidants have this large effect on the network as UNINETT is a robust network. But this also shows that a CBF in the northern part of Norway between UNINETT and SUNET would be a useful backup alternative.
UNINETT is merging their service and network departments.
UNINETT is looking into tailoring RT a little more, the current functionality is not really "good enough".
Some of UNINETT customers are investigating how to use ITIL to help their organizations, UNINETT are observering this effort to see how this would affect them and if there is something they could learn from this effort.
Contractual relationships to RIPE done

FSKnet
FSKnet are upgrading a few of their POPs (optical network) to ROADM.
They are moving to nagios for network monitoring to acheive correlated alarms.

FUNET
Network side been busy planning and setting up the last parts of the north and east optical network.
Installed Juniper MX routers and remove old juniper router.
Upgrading DNS system (services) and implmenting DNSSEC.
The FUNET NOC is now involved in SA2 in GN3.
FUNET is looking into the posibility to reorganize the NOC funtion. To have a dedicated NOC instead of experts on a rotating schedule.

RHnet
RHnet is finaly connected to NORDUnet properly with two 10G connections.
They are upgrading their internal network (backbone) to 10G.
The university of iceland will run the RHnet NOC.

Network Inventory presentations

NDL
NDL did not direct fit into what FUNET currently needs, to make it more useful it needs some developing.

Telemator
Telemator works fairly good for documenting a physical network topology but has limitations when it comes to documenting a logical network topology.

Tore will try to get ahold of the python API for Telemator

netdb
Netsb focus on switches and patchpanels and is very limited when documenting fibers and creating a logical topology.
There was no graphical interface.

Discussion about how to proceed with possible Network Inventory activity

We agreed on create specification about network inventory
What kind of information the system should contain and what kind of functions the system should have.
It was agree that each NREN should write down what kind of information each NREN would like to store in a network inventory and what kind of funtions it should be able to do. Then send that information to Stefan and he will publish it on the operational forum wiki. This should be done before June.
When that is done each NREN can review their specification in regards to what the others have done and create a revised version before July.
The goal of this task is to both learn from each other and also see how similar our requirements for a network inventory are.

Update on TT integration

Stefan will discuss with Eduix and try to make a central reporistory for tickets with an XMPP or IRC feed.
UNINETT is looking into customizing RT more and read the ICS files in the NORDUnet tickets into their calendar system instead of mapping values in the body of the emails.
University of iceland that is going to run the operations of RHnet also use RT.

Update on use of service IDs

The current information we include regarding IDs in the NORDUnet tickets are enough. IDs are currently manually processed by connecting NRENs.

NAV demonstration

Vidar did a presentation of NAV.

Pymetric demonstration

Pymetric is an internal routing visualizing tool that UNINETT use.
It was developed due to the fact that internal routing was dificult to follow, specially 2nd and 3rd paths.
Software can be found at software.uninett.no

Multicast beacon discussion

There is currently no way to monitor multicast within NORDUnet and geant except the multicast beacon.
NORDUnet and FUNET present, UNINETT present with hosts from time to time.
We discussed the posibility to change to D-beacon instead of using the current dast-beacon software. Trond at UNINETT will investigate what needs to be done to make this happen.
FUNET is using Nagios scripts to monitor their beacons.

TF-NOC

There is going to be a preparation meeting for TF-NOC on Monday the 3rd of May. The goal of the meeting is to come up with an proposal regarding what the task force can do.

AOB

During the operational update there was a discussion about organizational diagrams. To get a better understanding of each NRENs organisation we agreed to try to create an organisation diagram for each NREN. This could then be presented at the next meeting and maybe posted or linked to from the operational wiki.

Next meeting

As next meeting will take place during the vacation period Stefan will send out a foodle at the begining of July when most people hopefully know when their vacations will be.

  • No labels