Ewan MacKellar & Mario Tevanian Office 365 Network Performance Troubleshooting Ewan MacKellar & Mario Tevanian PRD323

Who broke my Outlook?

So what does bad really look like? Has anything changed that would have made things go bad? Which applications are slow and what is the behaviour? Where are the problems located and do they cluster? What is the network topology and available bandwidth? Who are the users and can they reproduce the behaviour?

How fast is your TCP/IP?

Round trip latency

Network trace shows round trip time 10:14:22 PM 01/11/2015 4.5362951 OUTLOOK.EXE Client1 outlook.office365.com TLS TLS:TLS Rec Layer-1 HandShake: Client Hello. {TLS:215, SSLVersionSelector:214, TCP:205, IPv4:204} 10:14:22 PM 01/11/2015 4.5833673 OUTLOOK.EXE outlook.office365.com Client1 TLS TLS:TLS Rec Layer-1 HandShake: Server Hello.; TLS Rec Layer-2 HandShake: Certificate. {TLS:215, SSLVersionSelector:214, TCP:205, IPv4:204}

Using PsPing.exe to show latency C:\>psping.exe -n 10 outlook.office365.com:443 TCP connect to 132.245.164.34:443: 11 iterations (warmup 1) connecting test: Connecting to 132.245.164.34:443 (warmup): 51.31ms Connecting to 132.245.164.34:443: 47.12ms …… Connecting to 132.245.164.34:443: 46.01ms TCP connect statistics for 132.245.164.34:443: Sent = 10, Received = 10, Lost = 0 (0% loss), Minimum = 41.83ms, Maximum = 101.71ms, Average = 53.20ms

Demo

Window scaling affects bandwidth

Segment size and selective acknowledgements - MaxSegmentSize: 1 type: Maximum Segment Size. 2(0x2) OptionLength: 4 (0x4) MaxSegmentSize: 1460 (0x5B4) - SACKPermitted: type: SACK permitted. 4(0x4) OptionLength: 2 (0x2

Demo

What about the network devices?

Check internal and external routing C:\>tracert outlook.office365.com Tracing route to outlook-au.office365.com [132.245.164.34] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 192.168.1.1 2 28 ms 28 ms 28 ms lns20.bne4.on.ii.net [150.101.180.143] 3 26 ms 52 ms 67 ms xe-0-2-0.cr1.bne4.on.ii.net [150.101.33.134] 4 57 ms 49 ms 57 ms ae6.br1.syd7.on.ii.net [150.101.33.76] 5 88 ms 70 ms 52 ms ae0.br1.syd4.on.ii.net [150.101.33.14] 6 42 ms 50 ms 47 ms as12076.nsw.ix.asn.au [218.100.52.4] 7 42 ms 60 ms 66 ms ae1-0.syd03-96cbe-1b.ntwk.msn.net [204.152.140.113] 8 55 ms 41 ms 42 ms ae0-0.syd03-96cbe-1a.ntwk.msn.net [191.234.80.96] 11 43 ms 41 ms 47 ms 132.245.164.34 Trace complete.

Demo

Proxy authentication 10:04:21 AM 27.1073427 OUTLOOK.EXE Client1  proxy.contoso.com HTTP:Request, CONNECT outlook.office365.com:443 10:04:22 AM 27.4692940 OUTLOOK.EXE proxy.contoso.com  Client1 HTTP:Response, HTTP/1.1, Status: Proxy authentication required 10:04:22 AM 27.6456812 OUTLOOK.EXE Client1  proxy.contoso.com HTTP:Request, CONNECT outlook.office365.com:443 , Using NTLM 10:04:22 AM 28.0071196 OUTLOOK.EXE proxy.contoso.com  Client1 HTTP:Response, HTTP/1.1, Status: Proxy authentication required 10:04:22 AM 28.0086832 OUTLOOK.EXE Client1  proxy.contoso.com HTTP:Request, CONNECT outlook.office365.com:443 , Using NTLM 10:04:23 AM 28.2324475 OUTLOOK.EXE proxy.contoso.com  Client1 HTTP:Response, HTTP/1.1, Status: Ok, URL: outlook.office365.com:443

When idle devices make Outlook fail Disconnect pop ups in Outlook Unexpected authentication prompts Hangs when switching between mailboxes or calendars Performance problems Mail stuck in outbox

Egress scalability SaaS means more outgoing connections NAT’ing outbound Maximum of 65k ports per IP, but may be lower in practice Multiple connections per client, per service ~6000 clients per public IP address (use 4000 for caution)

Packet loss Investigate over 1% Filter for Property.TCPRetransmit == 1 Check for FastRetransmit and DupACKs

Name Resolution

Geo DNS gets Outlook there faster

Testing Geo DNS for clients C:\>ping outlook.office365.com Pinging outlook-au.office365.com [132.245.164.34] with 32 bytes of data: Reply from 132.245.164.34: bytes=32 time=45ms TTL=246 Reply from 132.245.164.34: bytes=32 time=58ms TTL=246 Reply from 132.245.164.34: bytes=32 time=131ms TTL=246 Reply from 132.245.164.34: bytes=32 time=64ms TTL=246 Ping statistics for 132.245.164.34: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 45ms, Maximum = 131ms, Average = 74ms

Demo

Application specific steps

Application specific tests Office Configuration Analyzer Tool finds configuration issues Office 365 Client Performance Analyzer tests Outlook and SharePoint Office 365 Fast Track Network Analysis tests Lync/SfB Outlook connection status shows round trip latency to mailbox Internet Explorer F12 Developer Tools for SharePoint latency

So where is the top ten list? It’s right here.

Complete your session evaluation on My Ignite for your chance to win one of many daily prizes.

Continue your Ignite learning path Microsoft Ignite 2015 11/11/2018 11:39 PM Continue your Ignite learning path Visit Microsoft Virtual Academy for free online training visit https://www.microsoftvirtualacademy.com Visit Channel 9 to access a wide range of Microsoft training and event recordings https://channel9.msdn.com/ Head to the TechNet Eval Centre to download trials of the latest Microsoft products http://Microsoft.com/en-us/evalcenter/ © 2015 Microsoft Corporation. All rights reserved. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.