Introduction
The workshop gathered several NRENs to discuss common challenges and opportunities in monitoring, network operations, NAC, and IoT. There was strong interest in shared solutions and practical collaboration, especially around Argus, NAV, NOC practices, and iotroam.
Key outcomes
Monitoring (Argus / NAV)
- Strong interest in Argus for log aggregation.
- Requests for demos and better setup documentation.
- Need for better support for “glue services”, especially event correlation across systems (e.g. Mist, NAV, Aruba UXI).
- Surf noted that SNMP for stats polling does not scale for some use cases and recommended streaming telemetry. A number of open source telemetry collectors already exist, so it would likely make more sense to integrate an existing one with NAV, than to implement another collector from scratch.
NOC
- Large differences in NOC models across NRENs.
- Key success factors:
- Good documentation
- Standardization
- Automation
- Effective monitoring
- Low alarm noise
- Linking procedures directly from alarms
- Surf’s Network Dashboard (multi-source KPI view) raised strong interest.
NAC
- Clear need for NAC across several NRENs.
- Large variation in the use of NAC at different NRENs.
- Challenges:
- High cost of ClearPass and ISE
- Weak usability of FreeRADIUS
- Important with a way for users to register their devices themselves.
- Interest in cooperation on RADIUS as a Service (RaaS) and best practices
IoT / iotroam
- Very strong interest.
- CSC is in process with Surf for a pilot
- Sikt has been contacted by several Norwegian customers to know more about iotroam.
- Seen as a potential national service.
- Business model not yet clear
- As a part of the cost for the CNaaS service?
- As a part of the cost for eduroam?
- As a standalone subscription?
- Interest in pilots and VM-based deployment.
- OpenSAML / federated login support coming soon.
- Costs mainly for extended functionality.
Overall
- High engagement and constructive discussions.
- Clear value in joint development and shared services (Argus, iotroam).
- Collaboration requires prioritization and concrete commitments.
Way forward
Planned actions
- Argus / NAV: joint demos and alignment between Sikt and Surf. Owner: Sikt
- IoT / iotroam: demo and discussion of deployment model and pilots. Owner: Surf
- NOC: session on organization, tools and best practices. Owner: Sunet
Concrete objective
The shared goal is to achieve tangible, practical collaboration results (e.g. pilots, shared tooling, or joint processes) that can be presented at the TNC BOF meeting in June.
This requires clear ownership, allocation of time and resources, and a commitment to move from discussion to implementation.
Action points / Next steps
Description: Technical demo of Argus, including architecture, main use cases, and operational experience.
Owner: Sikt
Participants: Interested NRENs
Proposed timeframe: 3.march 10-12 CET
To join the demo please use the link below.
Meeting ID: 350 567 442 049 39
Passcode: Vi2HN2f4
Description:
Owner: Sikt / Surf (joint)
Proposed timeframe: Week 11–12
Description:
Owner: Surf
Participants: Sikt, CSC, other interested NRENs
Proposed timeframe: 10.march 14-16 CET
To join the demo please use the link below.
https://teams.microsoft.com/meet/36830957692876?p=vA5UpBxl8dusTO1fMZ
Meeting ID: 368 309 576 928 76
Passcode: 9CG3TN3n
Description: Experience sharing on:
Owner: Sunet
Proposed timeframe: Week 15–16
Description:
Owner: SIG-CNaaS coordination / Sikt
Proposed timeframe: Week 18–19