Netflow cc agenda 20051125

From GEANT2-JRA1 Wiki

JRA1 D3.4 Flow Monitoring - conference call agenda & minutes

1 Info
2 Agenda
3 Minutes
4 Conference call details

[edit]

Info

Date/time: 25th November 2005, 14:00 CET

Expected time of conference call: 1 hour

[edit]

Agenda

netflow servers installation plan (OS, additional services and tools)
netflow enabled network equipment (list of routers/switches, flow export parameters, ...)
First draft of an action plan (list of tool candidates, first set of testing goals, first draft of a time plan

[edit]

Minutes

Attendees: Hans Trompert (HT), Luuk Oostenbrink (LO), Alessandro Inzerilli (AI), Mauro Campanella (MC), Andreas Solberg (AO), Jon Kare Hellen (JH), Maurizio Molina (MM), Nicolas Simar (NS), Igor Velimirovic (IV)

Shipment: all three netflow testing boxes are delivered (GARR, Surfnet, CARNet)
Installation: boxes will be installed next week, before 05.12.2005.
OS: GARR will install Fedora Core 3 (kernel 2.6), Surfnet Fedora Core 4 (kernel 2.6), CARNet Debian (kernel 2.6). AI pointed that there were some problems with installation of a 64-bit OS and a flow-tools implementation; MM will check similar experience from DANTE and forward patches list to the AI. For now we will go with a 32-bit operating system. NS will check with perSONAR architects if there are any constraints regarding OS.
Access to boxes: machine will be accessed only by hosting NREN. If needed, ssh access will be enabled to the other partners, to be requested at least one week before needed.
Netflow export versions and modes: for now, work in parallel with netflow v.5 and v.9. There is a need to follow new developments within IPFIX wg; MM will forward to the mailing list a e-mail from Nevil Brownlee explaining differences between netflow v.9 and ipfix format. Considering sampling, for now many devices can only provide sampled exports.
Netflow tool requirements: the list of requirements is ok. However, since we decided to support v.5, IPv6 is not a obligatory requirement any more, but will be listed.
Network equipment: for a start, netflow wil be exported from a routers within each NREN. Not a problem to export from GEANT devices, but there is a privacy issue, and a NDA will be needed (MM). It might take a few weeks to arrange it.
Tool candidates: AS described four basic functionalities that netflow tool can provide: capturing, reporting, aggregation, presentation. Each of the tool provides one or more functionalities, and therefore tools can be compared for a specific task only. We shortened list to a four tools with a capturing and reporting function (flow-tools, NERD, nfsen/nfdump, Ipflow) and one for a aggregation and presentation (STAGER). Those five tools will be tested. We need a test evaluation form.
perfSONAR architecture: there is a need for a coordination with a prototype design, in order to prevent problem latter on. NS suggested to prepare description of request/reply procedures before January on order to discuss it with Martin Swany and other people from prototype group. NS proposed two solutions: to integrate netflow measurement points fully in a architecture and therefore provide all data to a measurement archives, or to provide only basic info to MAs and provide more detailed info directly to the users.

Actions

SURFNET; GARR, CARNet to install OS on a boxes before 05.12.2005.
IV to update wiki page: shortened list of a tools, requirements, etc. Also, start work on a coordination with perfSONAR team (DONE!)
MM to forward info about netflow v.9 vs. ipfix format (DONE!)
NS to check with perSONAR team if there are any OS constraints (DONE!)
IV to propose test evaluation form (DONE!)

Next meeting 5th of December 2005, 14:00 CET

[edit]