Work item C: NOC tools, interworking/interfacing issues, and automation
Goal:
- A NOC uses a wide variety of tools to manage different types of information. The goal of this work item is to investigate what tools are used and how they have been integrated into the NOC environment, focusing on the research and education community.
Topic |
Priority |
Subtopic |
Suggested deliverable |
---|---|---|---|
Survey of tools |
1 |
|
|
|
|
Collect information about which tools are used by the NOCs participating in TF-NOC |
Survey |
|
|
|
Report and statistics with the survey results |
|
|
Make a comparison of the above tools and what NOC functions they can support. |
Mapping between tools and functions |
|
|
Create a taxonomy for tools including information relevant for NOCs (e.g. technology, environment, benefits and goal.) |
Taxonomy for NOC tools |
Monitoring tools |
2 |
|
|
|
|
Collect information about which monitoring tools are used by the community |
Report and statistics with the survey results |
|
|
Investigate how the monitoring tools are deployed and for what purpose (e.g. faultfinding, alarming, statistics) they are used in different NOCs. |
Summary of the deployment of monitoring tools and their purpose |
|
|
Discuss and collect information about how monitoring tools can and are used to help keep track of SLAs. |
Summary of how monitoring tools are used for SLA |
Reporting and statistics tools |
3 |
|
|
|
|
Collect information about which reporting and statistics tools or systems are used by the community. |
Report and statistics with the survey results |
|
|
Identify what information is collected by reporting and statistics tools and who (e.g. management, boards or customers) use that information. |
Report of the collected information and the role of the people that collects it |
|
|
Discuss what information is seen as sensitive information and how do NOCs deal with the distribution of this information. |
Report on how NOCs deal with sensitive information |
Performance management |
4 |
|
|
|
|
Collect information about which performance management tools or systems are used by the community. |
Report and statistics with the survey results |
|
|
Discuss what performance values for the network and services are important for NOCs. |
List of important performance values |
Ticketing systems |
5 |
|
|
|
|
Collect information about which ticket systems are used by the community. |
Report and statistics with the survey results |
|
|
Discuss and investigate what can be done to harmonize ticket systems and make them work together. |
Summary of recommendations to harmonize ticket systems |
Knowledge management |
6 |
|
|
|
|
Collect information about which knowledge management tools or systems are used by the community. |
Report and statistics with the survey results |
|
|
Discuss and identify what information can and is useful to share between NOCs. |
Summary and recommendations about what information is useful to share |
Tool development |
7 |
|
|
|
|
Investigate the interest and possibility of open-source development (if appropriate) in TF-NOC. |
Report on the interest of open-source development and possible volunteers |
|
|
Investigate the possibility of sharing tools or specifications of tools produced by participants of TF-NOC. |
Report of the survey for ad-hoc tools |
|
|
Collect and share experiences about developing vs acquiring tools. |
Survey of ad-hoc tools & integration with DB |
|
|
|
Report and compilation of experiences |
|
|
Collect and share information about tool integration to databases. |
Report with the different approaches to the integration of databases and other network management tools |
T1. A first skeleton of the survey for the TF-NOC participants would be:
What tools does your organization currently use?
- Monitoring tools:
- Network Monitoring platforms (HP Openview, Pandora,...)
- General monitoring (MRTG, Cacti, Nagios, ... with or without plugins)
- Weather maps
- Thresholds and alarms
- Infrastructure monitoring (Nagios, Ganglia, Zabbix,...)
- Diagnostic tools (ping, traceroute, mtr,..)
- Flow monitoring (Netflow, cflow, sflow,... )
- Syslog (logfile scanner, JFFNMS,...)
- Routing: route servers (zebra,...), BGPmon, looking-glass, ...
- Multicast monitoring tools: (dBeacon,...)
- Out-of-band access tools
- Network security
- Sniffing & analyzing (tcpdump, wireshark,...)
- Topology documentation (Visio,...)
- Changes in network configurations (rancid,...)
- Control of configuration files (subversion, ...)
- Multidomain tools
- Do you use any special tool for the monitoring of multidomain networks? Which one?
- Do you use any tool for the automatic configuration of end-to-end circuits accross different networks? Which one?
- Reporting and statistics tools (Nagios, Zabbix,..)
- Who uses them?
- Ticketing tools (RT, Trac, Buzilla,...)
- Who uses them?
- Do the users have access to the tickets?
- Are the tickets publicly available?
- Performance management
- Performance testing (IPerf, NDT,...)
- Traffic generators (Bulk, Mgen,...)
- Chat/communication/coordination tools: IM, mailing lists, skype,...
- Databases: (Mysql, exchange,...)
- What information do you store on them?
- How do you connect them to your management tools?
- Knowledge management/documentation: (Plone, Wiki, ...)
- What kind of information do you store?
- How do you structure it?
The aim is to have information about advantages or disadvantages of the tools that have been already tested by the community.