This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
- Signaling (Time to establish session?) - Media (how did it sound?) - Host (limited by Host CPU)
RMON MIBRRC MIB RMON MIB
Communication Data Forwarding Path
4
RAQMON Framework Overview Instant Messaging
Secure Text Relay
Proxy (SIP) AIM
XMPPSignaling
over TLS TLS
UDP or DCCP
1
2
RRCRRC
RAQMON PDU (RTCP OR
SNMP)
RAQMON PDU
1 Task (Instant
Messaging)
1 Task (Instant
Messaging)
RRC MIB RMON MIBRRC MIB RMON MIB
Communication Data Forwarding Pathanwarsanwars
Does Instant Messaging and WebEX cares about Jitter?
5
RAQMON Framework Definition
RRC
Scope of the Framework
SNMP
RAQMON MIB
RDS RDS
X End DeviceEnd Device
RAQMON PDU is Out of Communication Data Forwarding Path
12
UNDERLYING TRANSPORT
(RTCP, SNMP)
1
2
Communication Data Forwarding Path
RDS/RRC RAQMON PDU Path
(e.g. RTCP, HTTP, FTP, TLS, SIP, H.323)
Communication Data Forwarding Path
6
Functional RAQMON Architecture
Communication NetworkIP
PSTNCellularOptical
RAQMON Report Collector
(RRC) # 1RAQMON MIB
(IP Address, port)
1. Context-sensitive Framework VoIP vs. Instant Messaging vs. XXXX 2. Transport Network Condition Specific Metrics Jitter3. Network Policy Specific RSVP Failed, Diffsrv = EF 4. Communication Session Related QoS Session Setup Delay/Duration5. Device Sate Specific Metrics CPU Usage
Variable Metrics list Updated using RAQMON PDU
SNMP
Management Application
IP End Device
RAQMON Data Source (RDS)
APPLICATION
Transport Protocol Agnostic
Extensible/Programmable Data Model
7
RAQMON PDU Overview
One RAQMON Application level PDUs to have “common formats” for reporting statistics
RAQMON PDUs will be transported over existing protocols– RTCP (APP PT = 204 from RFC 1889 or XR Report)– SNMP (NOTIFICATION)
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”
RDS RRC communication is “stateless” – RTCP BYE (if using RTCP between RDS/RRC) – TIMER (if using RTCP and SNMP based RRC) – Issue: MANDATORY for compliance?
RAQMON PDU may run over lossy transport – No Error correction or Recovery at RAQMON level– Complementary to IPFIX charter– RDS/RRC Sessions could be engineered to be lossless
8
Suggested RAQMON Use Case Examples Based on Application Type
RAQMON PDU for VoIP- Data Source Name (DN) - Receiver Name (RN)- Data Source Address (DA) - Receiver Address (RA) - Data Source Device Port used - Receiver Device Port used - Session Setup Date/Time - Session Setup delay - Session duration- Session Setup Status - End-to-End Delay (Round Trip)- End-to-End Delay (One Way)- Inter Arrival Jitter - Total number of Packets Received - Total number of Packets Sent- Total number of Octets Received- Total number of Octets Sent - Cumulative Packet Loss - Packet Loss in Fraction (in %)- Source Payload Type - Receiver Payload Type - Source Layer 2 Priority - Destination Layer 2 Priority - Source Layer 3 Priority - Destination Layer 3 Priority - CPU utilization in Fraction (in %)- Memory utilization in Fraction (in %)
- Application Name/version
RAQMON PDU for Instant Messaging
- Data Source Name (DN) - Receiver Name (RN)- Data Source Address (DA) - Receiver Address (RA) - Data Source Device Port used - Receiver Device Port used - Session Setup Date/Time - Session Setup delay - Session duration- Session Setup Status - Total number of Packets
Received - Total number of Packets Sent- Cumulative Packet Loss - Source Layer 3 Priority - Destination Layer 3 Priority - CPU utilization in Fraction (in
%)- Memory utilization in Fraction
(in %) - Application Name/version
RAQMON PDU for Pagers- Data Source Name (DN) - Receiver Name (RN)- Data Source Address (DA) - Receiver Address (RA) - Data Source Device Port used - Receiver Device Port used - Session Setup Date/Time - Session duration- Session Setup Status - Total number of Packets Sent- Application Name/version
9
RAQMON PDU Size - over time
1st PDU for VoIP- Data Source Name (DN) - Receiver Name (RN)- Data Source Address (DA) - Receiver Address (RA) - Data Source Device Port used - Receiver Device Port used - Session Setup Date/Time - Session Setup delay - Session Setup Status - End-to-End Delay (Round Trip)- Inter Arrival Jitter - Total number of Packets
Received - Total number of Packets Sent- Packet Loss in Fraction (in %)- Source Payload Type - Receiver Payload Type - Source Layer 2 Priority - Destination Layer 2 Priority - Source Layer 3 Priority - Destination Layer 3 Priority - CPU utilization in Fraction (in
%)- Memory utilization in Fraction
(in %) - Application Name/version
2nd PDU for VoIP- Data Source Name (DN) - Receiver Name (RN)- End-to-End Delay (Round Trip)- Inter Arrival Jitter - Total number of Packets
Received - Total number of Packets Sent- Cumulative Packet Loss - Packet Loss in Fraction (in %)- CPU utilization in Fraction (in %)- Memory utilization in Fraction (in
%)
………………..
Nth PDU for VoIP- Data Source Name (DN) - Receiver Name (RN)- Session Setup Duration- End-to-End Delay (Round Trip)- Inter Arrival Jitter - Total number of Packets
Received - Total number of Packets Sent- Cumulative Packet Loss - Packet Loss in Fraction (in %)- CPU utilization in Fraction (in
– Other objects in raqmonDsNotificationEntry may be added
13
Congestion Safety - changes in draft-02
Use TCP as Transport when possible– Scalability of RRCs may be reduced!
If TCP cannot be used following modes of operation are recommended
a. Constant Transmission Rate– 1 RAQMON PDU every 2 minutes (as good as TCP)– End of communication Session– “Engineered” Constant Rate e.g. 1 PDU every 5 sec
b. Retransmission timers with back offs – Ping/Pongs e.g. Process SNMP INFORMS from RRC
c. By restricting transmission to MTU Size
No more than 10% network bandwidth be used for RAQMON
14
RAQMON Extensibility changes in draft-02
RAQMON PDUs is extensible for future
a. SMI Enterprise Code (16 bit)• 0 Reserved for RMON WG• Vendor IDs are allowed for extension
b. Report Type (16 bit)• Allows Additional Parameters/Profiles to be added• WG can add new Report Type for SMI Enterprise ID = 0• Vendors can add Any Report Type for Vendor Specific SMI Enterprise ID
Update with PDU structure as defined in the framework draft Removed all data source specific stuff
– Now in the RAQMON-RDS-MIB– Conformance clauses
Clean-up – According to comments in the SF bar-review– Improved definition, DESCRIPTION clauses
16
Backgrounder
17
RAQMON Context Setting
IP Network
Applications
RTP / FTP/ HTTP
TCP/UDP
MAC IEEE 802.3
PHYSICAL
IP
MAC 802.3
IP
IP End Points Router
PHYSICAL
MAC 802.3
IP
Router
PHYSICAL
Applications
RTP / FTP/ HTTP
TCP/UDP
MAC IEEE 802.3
PHYSICAL
IP
IP End Points
PDAMG
Streaming Media, Transaction, Bulk data transfer etc
Application level priority (e.g. RSVP for S1, but no RSVP for S2)
Various packet level priority ( TOS, DiffServ etc.)
Domain 1
Domain 2 …….
Domain N+1
Multiple Equipment vendors, Multiple geographic locations, Multiple xSPs Control multiple Administrative and Provisioning domain
Domain N
18
RAQMON Network Configuration
Telephone
Laptop computer
Telephone
IP Network
Video/IP/IM/Voice
Voice over IP
Router
Media GatewayFax
Wireless Gateway
Regional Report Collector (Periodic Packets to populate MIB)
LAN/VPN INTRANET
Laptop computer
Corporate Network
Application Administrator
Monitoring Applications via
SNMP
PDANetwork /
Application Service Provider
SNMP
SNMP
SNMP
SNMP
Statistics Reported
Telephone
PDABluetooth
19
- Data Source Name (DN) - Receiver Name (RN)- Data Source Address (DA) - Receiver Address (RA) - Data Source Device Port used - Receiver Device Port used - Session Setup Date/Time - Session Setup delay - Session duration- Session Setup Status - End-to-End Delay (Round Trip)- End-to-End Delay (One Way)- Inter Arrival Jitter - Total number of Packets Received - Total number of Packets Sent
- Total number of Octets Received- Total number of Octets Sent - Cumulative Packet Loss - Packet Loss in Fraction (in %)- Source Payload Type - Receiver Payload Type - Source Layer 2 Priority - Destination Layer 2 Priority - Source Layer 3 Priority - Destination Layer 3 Priority - CPU utilization in Fraction (in %)- Memory utilization in Fraction (in %)
- Application Name/version
Current set of suggested metrics …..
Parameters “pushed” from RDS to RRC
Framework Accommodates addition of new parameters to the list …..