Realtime Application QOS Monitoring (RAQMON) Dan Romascanu dromasca@avaya.com 1
RAQMON Context Setting MG PDA Applications RTP / FTP/ HTTP TCP/UDP S ignaling control plane (e.g. RS VP, NS IS) Streaming Media, Transaction, Bulk data transfer etc Various packet level priority ( TOS, DiffServ etc.) Applications RTP / FTP/ HTTP TCP/UDP IP M AC IEEE 802.3 IP MAC 802.3 IP Network IP MAC 802.3 IP M AC IEEE 802.3 PHYSICAL PHYSICAL IP End Points Router Domain 1 Domain 2. Domain N PHYSICAL Router Domain N+1 PHYSICAL IP End Points Multiple Equipment vendors, Multiple geographic locations, Multiple xsps Control multiple Administrative and Provisioning domain 2
Functional RAQMON Architecture IP End Device Communication Network IP PSTN Cellular Optical APPLICATIO N 1. Context-sensitive Framework VoIP vs. Instant Messaging 2. Transport Network Condition Specific Metrics Jitter 3. Network Policy Specific RSVP Failed, Diffsrv = EF 4. Communication Session Related QoS Session Setup Delay/Duration 5. Device Sate Specific Metrics CPU Usage RAQM ON Data Source (RDS) Variable M etrics list Updated using RAQMON PDU Transport Protocol Agnostic RAQM ON Report Collector (RRC) # 1 (IP Address, port) RAQMON MIB SNMP Network Alarm Manager Management Application 3
RAQMON Framework Definition Scope of the Framework Communication Data Forwarding Path RAQMON PDU is Out of Communication Data Forwarding Path End Device RDS X 1 End Device RDS 2 RRC UNDERLYING TRANSPORT (TCP, SNMP) RAQMON MIB SNMP 1 2 Communication Data Forwarding Path RDS/RRC RAQMON PDU Path (e.g. RTP, RTCP, HTTP, FTP, TLS, SIP, H.323) 4
RAQMON Architecture Overview A set of RAQMON Application level PDUs to have common formats for reporting statistics Between a RAQMON Data Source (RDS) and a RAQMON Report Collector (RRC) Session specific metrics Device status RAQMON PDUs will be transported over existing protocols TCP SNMP Notifications RDS and RRC as Peer-to-Peer entities RDS reports what IT feels to be appropriate for the application context RRC consumes what IT feels to be appropriate for the application context No setup transaction to tell the collector which metrics the data source will be sending later on. RTCP BYE and TIME OUTS are used to terminate reporting between RDS and RRC 5
Parameters pushed by the RDS to RRC 6
RAQMON PDU Overview V PDT = 1 B T P I RC Length DSRC SMI Enterprise Code = 0 Report Type... SMI Enterprise Code = VENDOR Report Type... RMON Reserved Vendor Extension Static parameters static notifications - once per session, and - when sub-sessions start or end Dynamic parameters dynamic notifications 7
RAQMON Extensibility RAQMON PDUs is extensible for future a. SMI Enterprise Code (16 bit) 0 Reserved for RMON WG Vendor IDs are allowed for extension»http://www.iana.org/assignments/enterprise-numbers b. Report Type (8 bit) Allows Additional Parameters/Profiles to be added WG can add new Report Type for SMI Enterprise ID = 0 Other Standards Development Organizations or Vendors can add Any Report Type for Vendor Specific SMI Enterprise ID 8
RAQMON MIB raqmonmib raqmonsession raqmonexception raqmonconfig raqmonparticipant Table raqmonqostable raqmonparticpant AddressTable 9
RAQMON at a Glance Part of the RMON family of protocols Application view Support for multiple concurrent applications Not related to a specific application transport Scalable Extensible Endpoint oriented Works well with encrypted payload and signaling 10
Internet-Drafts Framework http://www.ietf.cnri.reston.va.us/internet-drafts/draftietf-rmonmib-raqmon-framework-11.txt RAQMON PDU http://www.ietf.cnri.reston.va.us/internet-drafts/draftietf-rmonmib-raqmon-pdu-10.txt RAQMON MIB http://www.ietf.cnri.reston.va.us/internet-drafts/draftietf-rmonmib-raqmon-mib-08.txt 11