Network Monitoring System with Scheduler

Transcription

1 Network Monitoring System with Scheduler Takatoshi Ikeda APAN-JP NOC, KDDI R&D Labs

2 Outline Background and Motivation Goal Outline of the System Specification of the Developed Environment Demonstration Issue List Roadmap

3 Background and Motivation Lessons Learned from SC2004 Traffic pattern in Bandwidth Challenge A lot of demonstration that filled in almost all bandwidth of a link were conducted in very short term. (tens of minutes) Illinois UNIV. Tokyo UNIV. JGN2 circuit, Japan-US, OC-192c(10Gbps)

4 Background and Motivation (cont.) Lessons Learned Schedule The schedule of actual demos were under control, but preliminary experiments had to been arranged by applicant. In addition, these schedules ware not opened to an online, such as web. Unexpected traffic An unexpected traffic might be generated during the allocated time slot. However, we couldn t identify the source of this traffic and couldn t detect it either. No expected traffic Although the demo slot was allocated, the traffic was not generated at all. The allocated slot should be well used by applicants. We need tool that can manage the schedule of the demonstration and monitor the traffic along the schedule

5 Goal Efficiency of managing the schedule The user and a operator can manage the schedule of demo through web, that makes the schedule management more efficient Management of a resource By managing the bandwidth of an international link, overbooking by multiple demos can be avoided. Monitoring along the schedule By monitoring the traffic on the international link along the schedule, unexpected or abused traffic will be alerted and the unused slot will be detected, too.

6 Outline of the System

7 Outline of the Operation (example: detection a unexpected traffic) Unexpected user Network congestion Unexpected user user 1, register the schedule - start time, end time - required bandwidth - Src IP, Dst IP - etc 2, generate the huge traffic for experiment Network Monitoring System with Scheduler Scheduler Manage the schedule Observatory data Get the network data Alert Monitoring tool Monitor the traffic Check Alert to the unexpected schedule user detect user Notification manage the schedule Check the schedule schedule operator

8 Outline of the Function Scheduling The system has web page for registering a demo. The user or operator can register information of demo into the system, such as start time, end time, bandwidth and the contact point. The system decide whether the demo can be accepted or not, based on the availability of the link. Monitoring The system monitors the traffic along the schedule on the link in full-time, and detects both unscheduled traffic and unused slot; the system alerts the contact point, if detected.

9 System Architecture User Access Layer Web Interface (for Management) Request Handler Schedule Management Layer Demo scheduling manager Resource manager Monitoring Layer monitoring Alert sender Service register For multi domain (Plan)

10 User Access Layer UAL SML MML Network Monitoring system With Scheduler This Layer provides a web interface for management to a user and operator, and handle the request that through the web interface Component Web interface Request Handler Management information User information Demo information (start and end time, requested link and bandwidth,,,,etc)

11 Schedule Management Layer UAL SML MML Network Monitoring system With Scheduler This Layer manages the schedule of demo and a resource of link, and process the request about the schedule from UAL and MML. Component Demo Scheduling Manager Resource Manager Management information Demo information (start and end time, requested link and bandwidth,,,,etc) Link information (bandwidth, terminated router and interface,,,,etc) Link reservation (start and end time, bandwidth)

12 Monitoring Layer UAL SML MML Network Monitoring system With Scheduler This Layer collects the traffic data from observatory which is the system that disclose the valuable network data. By using that data and schedule data, it monitor whether the traffic are generated along the schedule. If the traffic is not along the schedule, it give notice to appropriate contact and operator. Component Monitoring Alert sender Management information Usage data of link Flow data

13 Specification of the Developed Environment

14 Specification Hardware for development Supermicro 8013P+8 CPU : Dual Intel Xeon 3.2GHz Memory : DDR-226 2GB HDD : SCSI Ultra GB Software for development OS Redhat Fedora core 3 Kernel _smp Language Perl (Version 5.8.5) Free software Apache web server) rrdtool store the interface usage data) Flow-tools (netflow collector & analyst tool) NFS (sync the measurement data)

15 Specification (cont.) Traffic Data Usage Data Usage data of router interface for international link. This data is gotten by SNMP every 10 seconds and stored into rrd file. The system fetch the data through NFS. Flow Data Netflow data which is exported by a router. The router which terminated target link exports it. The data is stored into file which is flow-tool format every one minute. The system fetch the data by replication function of flow-tools on Observatory server. NFS nms2 nms4 nmdb1 SNMP Observatory Router (Juniper,Cisco,,,) replication NFS Netflow Network Monitoring System With Scheduler

16 Demonstration

17 Outline of the Demonstration 1. register the demonstration Register the demo information on the system (done beforehand) 2. Generate the demo traffic Generate the traffic from Tokyo to Los Angeles 3. Show the graph Show the graph of demo traffic

18 Network configuration for the demo nms1 iperf TCP Stream Gbps) Tokyo to LA nms2 nms4 nmdb1 Observatory operator Monitoring Data Transfer Registration of schedule Network Monitoring System with Scheduler Tokyo, Japan TransPAC2 US-JAPAN Link OC-192(10Gbps) nms1 Observatory Los Angeles, US

19 Issue List Algorithm design for detection In the current phase, the system can grasp the traffic on the link. For the next phase, the algorithm that detects unscheduled traffic or unused slot will be implemented. Assessment of the performance The CPU load of the router will be checked, and the performance of server will be estimated in the real environments.

20 Issue List (cont.) User profile Manage the user login and prepare for the user and the operator s web pages. Security The security of communication between layers will be implemented. Other flow format Switch or router has adapted the other flow technology such as sflow. Its format will be supported.

21 Road map 2005/8-9 Algorithm for the detection will be implemented. Also, some parameters for detection are adjusted by using real-world data. 2005/9 use the system experimentally for igrid /11 use the system for SC2005.

22 Reference Lessoned Learned from Abilene Observatory Observatory at Tokyo XP UCLP(User Controlled Light Path) Software University of Waterloo s UCLP software University of Ottawa & Communications Research Centre s UCLP software

23 Thanks