1. The evolution of monitoring services : RNP Case
Emmanuel Gomes Sanches Paulo Maurício da Conceição Júnior Rede Nacional de Ensino e Pesquisa (RNP) Brazilian NREN Engineering and Operations Directory

2. Agenda Introduction Scenary and objective Strategy and roadmap
Monitoring arquitecture evolution
Monitoring scope evolution
Impact on NOC’s demand
Benefits and conclusion

3. 1. Introduction – RNP: Brazilian NREN
Ipê Network
RNP National backbone
Network connections
Situation on August 2016
Composed by 27 PoPs
(Points of Presence)
Aggregated capacity 325 Gbps
International capacity 116 Gbps

4. 1. Introduction – Network extension
Total size : 8,516,000 km2 Europe excluding Russia = 6,900,000 km2
Australia
Europe
USA

5. 1. Introduction – NOC
Network Operation Center – 24x7 monitoring service NOC team alert technical teams contacting each 10 minutes

6. 2. Scenary and objective Difficulties
Reactive action in some failure situations
Lack of visibility in identifying affected services
No statistics of services availability
Dependence of PoP team’s reporting to follow connectivity health
Lack of monitoring information during connection failure events
Action plan
“Promote the evolution of monitoring to improve the quality of management, inserting new tools and expanding the scope”

7. 3. Strategy and roadmap Strategy of evolution
Provide better monitoring tools (2015)
Expand monitoring scope (2016)
Include customers connectivity (in progress)
Roadmap for Scope expansion
Availability monitoring
Conectivity monitoring (already done)
IT infrastructure monitoring (already done)
Corporate services monitoring (2016)
Advanced services monitoring (2017)
Performance monitoring (2018)
Quality monitoring (2019)

8. 4. Monitoring solution – Initial
Centralized architecture
Single point of failure
Ipê
Network

9. 4. Monitoring solution – Nowadays
Distributed architecture
No single point of failure
Better reliability
Open source solution
Based on Nagios code
Load distribution
Ipê
Network

10. 4. Monitoring solution – Nowadays
RNP implementation
27 poller servers installed (one in each PoP)
Monitoring 1,037 hosts with 3,012 elements until the moment
High resilience in case of failure
Ipê
Network

11. 5. Monitoring scope evolution
Previously
RNP use to monitoring only his own infrastructure
Nowadays
RNP decided to expand its monitoring scope including :
Advanced services monitoring
Customer connections monitoring

12. 5. Monitoring scope evolution
Previous scope : Network and IT Infrastructure (based on SNMP)
RNP NOC

13. 5. Monitoring scope evolution
New scope : Add customer connectivity and RNP services (functional tests)

14. 5. Monitoring scope evolution
Inclusion of 16 Advanced Services
CAFe (federation)
Web Conference
eduroam
FIX
(VoIP)
ICPEdu (CA)
IDC (colocation)
Telepresence system
TV Signal Transmission
Live Video Transmission
Videoconference
Video on Demand
Edudrive (cloud storage)
Compute (IaaS)

15. Network layers monitoring history
5. Monitoring scope evolution
Inclusion of customers Connectivity
Network layers monitoring history
CORE Layer:
Ipê Network backbone
monitored since 2007
DISTRIBUTION Layer:
27 Points of Presence
10 PoPs monitored since 2016
ACCESS Layer:
1,237 customers with
3.5 million users
497 customers monitored
since 2016

16. 6. Impact on NOC’s demand
Tickets per month Average increase of 256% in 1 year

17. 7. Benefits and conclusion
Results already perceived of efforts done during last 2 years :
Adoption of a new monitoring tool
Better availability of monitoring service
Load distribution through remote monitoring agents (pollers)
Monitoring resilience in case of connection failure
Possibility of services monitoring through functional tests
Inclusion of services monitoring view
Quicker failure identification
NOC operators contact appropriate technical teams
Smaller resolution time
Better service management and support
Expansion of network monitoring scope
Proactive action on customers’ connectivity failure
Better customer satisfaction
Better network management and planning

18. Emmanuel Sanches – IT Manager
Paulo Júnior – IT Specialist