Network and Services Management Jean Walrand EECS

Outline Objectives SNMP RMON NETFLOW MPLS & GMPLS DiffServ End-to-End Overlay Tools For Smart Networks

Objectives Box Management Network Management Services Management Fault Management Performance Management Network Management Network Planning Traffic Engineering Services Management Resource Allocation/Pricing

SNMP Simple Network Management Protocol

SNMP Protocol: GetRequest/GetNextRequest/GetResponse/SetRequest/Traps (protected) Management Information Base (MIB): OID Standardized Custom Examples: Number of interfaces Number of bytes & packets /port PER Tutorial

NetFlow (Cisco) Link Flow: (SIP, STCP, DIP, DTCP, ToS) Functions: Provide detailed data collection with minimal impact on router performance and Efficiently process access lists for packet filtering and security services Applications: Accounting/Billing Network Planning and Analysis--- Network Monitoring Application Monitoring and Profiling User Monitoring and Profiling NetFlow Data Warehousing and Mining

NetFlow (Cisco) (cd) Architecture:

RMON Remote Monitoring RFC 1757 Statistics: about subnet or network History: Sample statistics at separate intervals Alarms: When and how alarms are to be used Hosts: Statistics about activity host <-> subnet Hosts Top N: Statistics about the N highest hosts Traffic Matrix: Traffic and error information Filters: Specify packets or packet types to capture. Packet Capture: How to get data from and about network history. Events: List of all the events, or activities, created by the monitor.

Multi-Protocol Label Swtching Part 2 MPLS & GMPLS Key Ideas: Set up paths – Label Switching Advantages: Faster switching (initial idea) Control routing; Traffic Engineering; QoS Multi-Protocol Label Swtching Part 2

DiffServ Key Ideas: CoS – Per Hop Behavior (e.g., VoIP) Hose Model (as opposed to pipe model) Worst-Case + Overbooking

DiffServ Goal: Solution: CoS without per-connection state No route-pinning Planning and operations based on aggregate statistics and worst-case routing Peer-to-peer SLAs that specify total rate but not traffic destination

DiffServ – Worst Case CAC Ingress 3 Ingress 3 Ingress 1 Ingress 1 Bottleneck Link Ingress 2 Ingress 2 Typical Case Worst Case Terribly wasteful!

DiffServ – Measurement Based CAC New Capacity Mean + 2.4s Gap Admit if peak(new) < Gap at all times

End-to-End Key Ideas: Advantages: Main Issues: Measure QoS with a few test packets Abort if QoS is not acceptable If all users do this, should be OK Advantages: Connections are protected No need for CAC infrastructure Main Issues: Can one measure reliably end-to-end? Assumes all users are honest Fairness

Overlay Networks

Overlay Networks (cd) Tunnel with CoS Control CAC Transport

Tools for Smart Networks Admission Controller Network Measurement Router Configuration Public Internet Access Gateway Switch (control) Performance Monitoring Traffic Generation Sinks Source Switch (source) Switch (sink)

Tools for Smart Networks… Measurement-Based Worst Case EF from S1 to D3 1000s Measurement-Based Admission Control and Provisioning for DiffServ

Tools for Smart Networks … SNT