PLNOG15: VidMon - monitoring video signal quality in Service Provider IP network - Krzysztof Mazepa, Piotr Najduk

Vidmon
monitorowanie jakości sygnału video
w sieci IP operatora
Krzysztof Mazepa
Piotr Najduk
CISCO SYSTEMS POLAND
VECTRA

Agenda
1. Wprowadzenie
2. Wyzwania związane z transmisją
Video w sieci IP
3. Praktyczne podejście do usuwania
usterek
4. Szczegóły techniczne
5. Zalety wprowadzeniaVidmon’a do
sieciVectry, dalsze plany...

Jak wygląda transmisja sygnału video
w sieci operatora kablowego?

Wyzwania z jakimi styka się dział obsługi
sieci IP związane z transmisją sygnału
Video
 ○ QOS
 ○ Monitoring
 ○ Lokalizacja usterki

Usuwanie usterek w wersji manualnej
 ○ Ustalenie zgrubne miejsca wystąpienia usterki
 ○ Analiza monitoringu, statystyk interfejsów
 ○ Diagnostyka i pomiary

Vidmon – Duże wsparcie dla działu IP
 ○ Historyczne doświadczenia
 ○ Nowa wersja związana z architekturąTyphoon
 ○ Nowa jakość obsługi zgłoszeń dot. video

Aktywne alerty
 RP/0/RSP0/CPU0:ASR9010#show performance traffic alerts interface
TenGigE0/0/1/0 input
 Wed Sep 23 15:03:18.393 MET

 Interface: TenGigE0/0/1/0 Direction: input

 GROUP Alerts
 Class: class_ts_all
 Num Flows: 212
 Num Grouped Alerts: 1
 Highest Alert Severity: Alert
 React ID Severity Metric
 -------- -------- ------
 1 Alert Flow Count

 FLOW Alerts

Przykładowy log
 LC/0/1/CPU0:Sep 24 07:35:20.472 : afmon_ea[111]: %SERVICES-
PERF_TRAFFIC_ALERT-0-ALM_EMERG : TenGigE0/1/0/3: SET|Input|ID
102275|React 9 mpeg-loss-pkts|Src_IP 192.168.150.74, Src_Port 5000,
Dst_IP 232.10.3.7, Dst_Port 6001
 LC/0/1/CPU0:Sep 24 07:35:50.472 : afmon_ea[111]: %SERVICES-
PERF_TRAFFIC_ALERT-0-ALM_EMERG : TenGigE0/1/0/3: CLEAR|Input|ID
102275|React 9 mpeg-loss-pkts|Src_IP 192.168.150.74, Src_Port 5000,
Dst_IP 232.10.3.7, Dst_Port 6001

 react 9 mpeg-loss-pkts
 threshold type immediate
 threshold value ge 1
 action syslog
 action snmp
 alarm severity emergency
 alarm type discrete

Przykładowy log - analiza
 RP/0/RSP0/CPU0:ASR9010#show policy-map type performance-traffic interface TenGigE0/1/0/3
cumulative detail match ipv4 source 192.168.150.74/32 destination 232.10.3.7/32
 Thu Sep 24 12:59:43.807 MET
 -----------------------------------------------------------------------------------
 Interface: TenGigE0/1/0/3 Direction: input
 Service-Policy: vidmon
 -----------------------------------------------------------------------------------
 Total Num Flows: 259
 Flow:97426 Key:192.168.150.74:5000 -> 232.10.3.7:6001 UDP
 Flow Start: Wed Sep 16 11:52:24 2015 Uptime: 8d 01:06:30
 Metric type : IP-CBR
 MRV : 0.001 %
 Avg Packet Rate : 4806.04 pps
 Total Packets : 3341117294
 Avg Bit Rate : 52520 kbps
 Total Bytes : 4563966223604
 Avg Packet Len : 1366.00 B
 -----------------------------------------------------------------------------------
 Num Flows Displayed: 10
 -----------------------------------------------------------------------------------

Przykładowy log – analiza c.d.
 Flow:102275 Key:192.168.150.74:5000->232.10.3.7:6001 MDI-MPEG PID:241
 Flow Start: Wed Sep 23 01:59:14 2015 Uptime: 1d 11:36:30
 Metric type : MDI-MPEG
 MPEG MLR : 0.000 pps
 MPEG Lost Packets : 15
 MPEG MDC : 1
 Error Seconds : 0.00 s
 Transport Availability : 100.00 %
 Avg MPEG Packet Rate : 5332.21 pps
 Total MPEG Packets : 683536137
 Avg MPEG Bit Rate : 8019 kbps

ASR9k Inline Video Monitoring
Technical Overview
Technical Overview
ASR9k Vidmon Solution

© 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidentialasr9k-vidmon-javed 12
How ASR9k Measures MPEG MDI Metrics?
ASR9k
15 1213
13
14 11 1016
MPEG Video Stream
1. Supported on any port of Typhoon LCs
2. Inline DPI of all MPEG video at line rate
3. No buffering of MPEG video during DPI
• No jitter induced
• No latency induced
4. Parse all MPEG Frames in MPEG TS
5. Compute MDI: MLR, DF, MDC metrics per interval
6. Report MDI metrics to CLI and MIBs
7. NMS updates screen after SNMP poll
HW/SW Requirements
1. RSPs all versions
2. Typhoon LCs all versions
3. SW: XR 4.3.0 or above

ASR9k Video Monitoring
Video Metrics Support
Video Monitoring Metric Supported
MPEG-MDI – RFC4445 Yes
RTP-MMR for Microsoft Media Room Yes
RTP-Voice Yes
RTP-JPEG2k Yes
RTP-Custom Yes
Video Availability SCTE-168 report (error’ed
seconds)
Yes
Video Jitter Yes
Media Stop Event Yes
IP-CBR Yes
MPLS Yes

Vidmon on Video Payload Encapsulations

MPEG-MDI Vidmon
 Operates on MPEG2-TS headers (inline DPI on a per-packet
basis)
 Video Payload Independent
Any video encoding: MPEG2, MPEG4, AVC, etc.
Video payload may be encrypted
 Loss metrics computed using the CC field from the MPEG header
 Support for both RTP and non-RTP encapsulated packets
 Up to 7 MPEG2-TS Packets per IP packet supported
 Can filter out control PIDs and low rate PIDs
 When used in conjunction with RTP Vidmon, provides ability to
differentiate source vs network impairments

MPEG2-TS Header
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
0 sync_byte = 0x47 TE PS TP PID scram afctl cc
Bits Field Name Description
31:24 sync_byte Always contains the value 0x47
23 TE (transport error) Transport error indication
22 PS (payload start) Indicates start of elementary stream payload
21 TP (transport priority) Transport stream priority (1 = high priority)
20:8 PID Elementary stream program ID.
7:6 scram Transport Stream scrambling control
5:4 afctl Adaptation Field Control
0x0 = Reserved
0x1 = Payload present
0x2 = Adaptation field present
0x3 = Both Adaptation field and Payload present
3:0 cc Continuity Counter – 4 bit sequence number for this
elementary stream.
Reference slide

Video Monitoring Levels
• When MDI Vidmon enabled, 2 Levels Active
• L3 Vidmon
•IP packet level monitoring (IPCBR or RTP)
•Jitter/DF
• MDI Vidmon
•DPI of MPEG2-TS Packet headers in packet payload
•Detects loss without packet level sequence numbers
• Allows user to differentiate network vs source induced problems
•For example:
• PID level loss with L3 loss: likely network problem
• PID level loss without L3 loss: likely source problem
IP
UDP
MPEG2
MPEG2
MPEG2
MPEG2
MPEG2
MPEG2
MPEG2

Wireline IPTV Use Case – PIM SSM/ASM
MPEG MDI Video Monitoring Points – ASR9k XR4.3
Access and Aggregation
Network
Network
Core IP/MPLS
Network
Home
Network
ASR9k PoP
Super Head End (SHE)
MPEG Video
Video Service
Office (VSO)
DCM
EncoderSource
MSE
MSE
Video Hub
Video Service
Office (VSO)
Video Hub
Encoder
Source
DCM
DCM / VQE
Encoder
Source
Video Hub Office(VHO) /
Regional Head-end (RHE)
P
P
Headend Aquisition
Domain Core Transport
Domain
Domains
MDI
(0:0:12)
ASR9k
ASR9k POP
Ingress MPEG MDI
Monitoring Point
MDI
(0:0:22)
MDI
(0:0:32)
MDI
(12:3:32) MDI
(12:3:42)
MDI
(12:3:27)
Problem
Domain
(i.e. Egress Port)
Egress MPEG MDI
Monitoring Point
PIM-SM/SSM
ASR9k
Video
Distribution
2
MPEG-TS
MSFT Media Room
ABR
JPEG2k
MPEG-MDI
ABR-MDI
RTP-MMR
J2k-MDI

Show Policy-map: MPEG-TS Metric Summary
show policy-map type performance-traffic interface tenGigE 0/2/0/10
-----------------------------------------------------------------------------------
Interface: TenGigE0/2/0/10 Direction: input
Service-Policy: ipcbr-mdi
-----------------------------------------------------------------------------------
Total Num Flows: 3
Metric Flow Key MPEG PID MPEG MPEG MPEG Error
Type SrcAddr:SrcPort -> Pkts Lost Pkts MDC Sec(s)
DstAddr:DstPort
MDI-MPEG 10.0.0.2:1024 -> 51 3510 0 0 0.00
20.0.0.2:1024
MDI-MPEG 10.0.0.2:1024 -> 52 3510 0 0 0.00
20.0.0.2:1024
-----------------------------------------------------------------------------------
Class Name Num-Flows
---------- ---------
ucast 3
mcast 0
-----------------------------------------------------------------------------------
Header Rows
Per-Flow Summary
Metrics

Show Policy-map: MPEG-TS Metric Detail
-----------------------------------------------------------------------------------
Interface: TenGigE0/2/0/10 Direction: input
Service-Policy: ipcbr-mdi
-----------------------------------------------------------------------------------
Total Num Flows: 3
Flow:291 Key:10.0.0.2:1024->20.0.0.2:1024 MDI-MPEG PID:51
Class: ucast Total Intvls: 1
Intvl# 1, Updated at: Sat Oct 20 12:39:41 2012, Duration: 10 s
Metric type : MDI-MPEG
MPEG MLR : 0.000 pps
MPEG Lost Packets : 0
MPEG MDC : 0
IP Jitter : 3.084 ms
Avg MPEG Packet Rate : 351.00 pps
Total MPEG Packets : 3510
Avg MPEG Bit Rate : 527 kbps
Error Seconds : 0.00 s
Transport Availability : 100.00 %
...
Flow:290 Key:10.0.0.2:1024 -> 20.0.0.2:1024 UDP
Class: ucast Total Intvls: 1
Intvl# 1, Updated at: Sat Oct 20 12:39:47 2012, Duration: 10 s
Metric type : IP-CBR
MRV : 0.000 %
DF : 3.084 ms
Avg Packet Rate : 351.00 pps
Total Packets : 3510
Avg Bit Rate : 3824 kbps
Total Bytes : 4780620
Avg Packet Len : 1362.00 B
IPv4 TTL : 255
L3 (IP Level) Flow
Metrics
MPEG Flow Level
Metrics

Zalety wprowadzenia Vidmon’a do sieciVectry
- Większe zadowolenie klientówVectry z jakości
świadczonej usługi
- Proaktywny monitoring
- Szybka lokalizacja usterki
- Dokładne okreslienie natury problemu
- Oszczędności (capex / opex)
- Mozliwość znalezienia problemów nie tylko
ilościowych (błędy) ale również czasowych (jitter)
- Always on, historia jakości transmisji sygnału
- Widoczność utraty jakości sygnału na łączach
„obcych”
Plany na przyszłość

PLNOG15: VidMon - monitoring video signal quality in Service Provider IP network - Krzysztof Mazepa, Piotr Najduk

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

En vedette

En vedette (20)

Similaire à PLNOG15: VidMon - monitoring video signal quality in Service Provider IP network - Krzysztof Mazepa, Piotr Najduk

Similaire à PLNOG15: VidMon - monitoring video signal quality in Service Provider IP network - Krzysztof Mazepa, Piotr Najduk (20)

Dernier

Dernier (20)

PLNOG15: VidMon - monitoring video signal quality in Service Provider IP network - Krzysztof Mazepa, Piotr Najduk