INT-In-Band Network Telemetry

19 Pages·2017·9.7 MB·English

I n - B a n d N e t w o r k T e l e m e t r y - A
P o w e r f u l A n a l y t i c s F r a m e w o r k
f o r y o u r D a t a C e n t e r
Roberto Mari
Dir. Product Management
Barefoot Networks
Barefoot Solutions and SONiC
Growing Open Ecosystem
+
Barefoot Advanced Apps
(Network Analytics and more)
Deep Insight™ Analytics
+
+
Barefoot SDE/Compiler
Capilano™ SDE
+
6.5 T 3.3 T 2.5 T 1.9 T
Barefoot Hardware
Tofino™ ASIC
Production Ready ODM/OEM Systems
Copyright ©2018 - Barefoot Networks
3
New P4 App WG & Open Community initiatives
Charter
• Data-Plane Telemetry (e.g. INT)
API App
• Security: Heavy-hitter Detection
WG WG
• Services Offload: (e.g. Layer-4 LB)
• In-Network Cache for distributed services
.org
• In-Network Consensus protocol
Language
Initial Accomplishments
Architect.
Design
• 30+ Active Customers: OEM and Technology vendors
WG
WG
• Open Sourced INT and Telemetry Report Specs
OVS Orbit PODcast on P4 INT (B. Pfaff, C. Kim): https://ovsorbit.org/#e46
How INT works, upcoming OVS support for INT and SDN vendors involvement
IETF 100 – Barefoot delivers first ever hardware-based (Tofino) In-situ OAM implementation:
Barefoot Networks Demonstrates In-situ Operations, Administration and Management (IOAM)
Showcasing the Power of Programmable Forwarding Plane Technology
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
Today’s Network Monitoring ...
e
d
i
Expensive and Inefficient Can’t capture microbursts No Visibility = No Control
l
S
Service Issue

Switch OS
d
100s ns – 10s usec
Microburst
e Ping SNMP
Traceroute Sflow
t
Must be the
a
Network
m 10s ms – 10s sec
Network Ops Admin
i
n
A
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
5
“I visited Switch 1 @780ns,
1
“Which path did my packet take?”
Switch 9 @1.3µs, Switch 12 @2.4µs”
# Rule
1
2
“In Switch 1, I followed rules 75 and 250. In
2 “Which rules did my packet follow?”
3
Switch 9, I followed rules 3 and 80. ”
…
75 192.168.0/24
…
6
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
3
“How long did my packet queue at each switch?”
“Delay: 100ns, 200ns, 19740ns”
Queue
4
“Who did my packet share the queue with?”
Time
7
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
3
“How long did my packet queue at each switch?”
“Delay: 100ns, 200ns, 19740ns”
Aggressor flow!
Queue
4
“Who did my packet share the queue with?”
Time
8
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
The network should answer these questions
“Which path did my packet take?”
1
“Which rules did my packet follow?”
2
“How long did it queue at each switch?”
3
“Who did it share the queues with?”
4
Tofino + Deep Insight can answer all four questions.
For the first time. At full line rate.
Without generating any additional packets!
9
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss
How it works and how we use the data
Leverages In-Band Network Telemetry (INT)
https://github.com/p4lang/p4-applications/tree/master/telemetry/specs
Add: SwitchID, Arrival Time,
Queue Delay, Matched Rules, …
Original Packet
10
CCooppyyrriigghhtt ©©22001188 -- BBaarreeffoooott NNeettwwoorrkkss