Deutsch de

Project meeting at DB Systel in Frankfurt

19.07.2017

This was our first project meeting at Deutsche Bahn Systel GmbH in Frankfurt. As first  agenda item, we visited the Network Operations Center (NOC) and got an overview of service provider operations and tooling world at Deutsche Bahn.

Although we have been a smaller group this time, we got additional input and had discussions with on-site experts at DB. At the first day we have been invited to visit DB's innovation center Skydeck and put the railway context of the meeting also into our group foto.

Our brainstorming and planning sessions continued at the second day. We covered topic such as

  • Evaluation of TCP timestamps and sampling approaches for delay monitoring
  • Traffic prediction algorithms
  • Anomaly detection for MTU issues
  • Active measurements of middlebox effects


AutoMon at IETF 99 NMRG

17.07.2017

We presented the AutoMon project and our current topic on passive TCP delay analysis at the Network Management Research Group (NMRG) "workshop on measurement-based network management", which was part of the IETF 99 Meeting in Prague. The slides of our talk are available as pdf for download.

The NMRG workshop was on Monday morning, so it was a perfect timing to chat to other IETFers on Sunday evening, on Monday and leave in the afternoon to our AutoMon meeting in Frankfurt. Nevertheless, it was quite a short IETF visit as there were really interesting things going on and time to chat to others was scarce.

Visit of IBM Watson Center Munich

17.05.2017
The AutoMon project and some of our guest visited the IBM Watson Center and got insight into awesome demonstrations in the lab. Afterwards, we continued the AutoMon project meeting in a meeting room in the same building with a stunning view over Munich.

Project meeting/status seminar at IsarNet

16.05.2017
The AutoMon project met with some guests at IsarNet for a status meeting after almost one year of project duration. We presented the current state of our work in the morning to an interested audience including guests from CIT-Jena and Controlware. In the afternoon, we continued the meeting with several workshop sessions on currently ongoing working items.

Project meeting at TUM

21.03.2017

We met at TUM on 21. and 22. of March. The first day Andreas Gilberg from Postbank joined us an interested guest. He got insight in the current work in AutoMon and gave valuable feedback. Also on the first day we visited the nuclear fusion/plasma physics research center (IPP) close to TUM. There we got a physics update and insight into a completely different domain of research. 


At both days we had lively and fruitful brainstormings on the following topics:

  • Related research work at TUM regarding DNS, IP-siblings detection and topology detection/modeling
  • Current developments in network monitoring
  • Update on the state of exply and research on advanced ticket data use cases
  • Visualization approaches and ideas for network monitoring data that in future could enhance the user experience of IsarFlow
  • Network and application timing and anomaly detection
  • ...and far more

Cisco Live 2017 in Berlin

21.02.2017

AutoMon participants from Deutsche Bahn, IBM and IsarNet attended at Cisco Live in Berlin. There were lots of opportunities for dicussing networking topics as well as for getting input on new technologies and network monitoring concepts. Especially, we had several sessions and talks with Cisco engineers about interfaces for obtaining network monitoring data and device configuration. 


We presented AutoMon at the IsarNet booth in the world of solutions. There, we discussed the AutoMon ideas with customers and interested participants.  Furthermore, a demonstrator of AutoMon functionality was presented at the booth and we got valuable feedback.


Unfortunately there is no picture with all AutoMon participants, as we all had a couple of very busy days.

Project meeting Dresden

25.01.2017

The project partners met on 24. and 25. of January in Dresden to talk about the current state of the project and the next steps.

We focused on:

  • discussion on various network topology topics
  • continued planning and refinement of research and application use cases
  • planning of the continued collaboration; including setup of a test site at the partners
  • a team retrospective

... And of course, we again had time to talk about lots of interesting networking topics and challenges we are currently working on; brainstorming and discussing our current challenges.

Project meeting at TUM (Garching)

22.11.2016

The AutoMon project met at Technical University Munich in Garching for a two day meeting. We had a productive time and took a break for visiting

the SuperMUC super computer at the Leibniz super computing center.


Main topics of this meeting included

  • Adaptive NetFlow/IPFIX collection and processing
  • Results from prototypes for selecte use cases
  • Automon architecture concepts

AutoMon at KMU-Innovativ meeting

10.10.2016
Automon presented a Poster at the KMU-Innovativ meeting in Hannover (KMU Innovativ Fachtagung). We had interesting discussions with other projects and got valuable input from panel discussions and science dating activities.

Project meeting at IBM in Kelsterbach

20.09.2016

Our first project meeting after the kickoff took place at IBM-AIS in Kelterbach, close to Frankfurt Airport. As you can see, we hat lots of fun in the fancy lab of IBM Multinetwork WAN Services. At this meeting we

  • discussed AutoMon use cases and refined them considerably
  • evaluated our research activities on the current implementation state of RestConf/NetConf and SDN controller support for today's networking gear for flexible network monitoring configuration
  • had a WebEx with the product manager and development of Cisco APIC-EM SDN controller

Project kickoff at IsarNet

01.06.2016

The AutoMon project started in June and we met right at the first day in June for our kickoff meeting at IsarNet in Hallbergmoos. Unfortunately, we did not take a picture, but nevertheless had fun and a productive time. Besides introding the partners and revisiting the working areas of all partners, we started our first work packages on requirements, use cases and the general architecture.