27 Oct 2011

What my first iCloud backup did to my Internet link

I'd just finished reading the piece by Joanie Wexler "iCloud to test Wi-Fi Performance Mettle" when my iCloud invitation arrived. I was keen to see how much bandwidth it used for my first backup. Here's the result.

Icloud-backup-util
The red stuff is the traffic from my iPhone up to iCloud. So, not unexpectedly, it took all the available uplink bandwidth I had, near enough 1 Meg. If there is a silver lining, it's that the traffic is SSL, so while my link may have been completely congested, it was secure. Here's what happened to the link's round trip time.

Rtt
You can identify the backup traffic by its SSL certificate common name which is *.icloud.com so if you have some form of traffic management it should be fairly simple to throttle the backups. Let me know if you need a hand with that.

So there it is, just me with a lightly used iPhone, taking my link to capacity for the best part of an hour. What happens when dozens, hundreds, of iPhones hit your Internet link for the first time?

Addition: In response to some questions; the top graph is from a PacketShaper, the RTT graph is from PathView Cloud. For more information about controlling iCloud traffic with  PacketShaper see https://bto.bluecoat.com/packetguide/8.6/info/application-criteria.htm#ssl or ask me - I'm wonderfully cost-effective.

Cheers, Cliff.

19 Oct 2011

There is no such thing as proactive

Contentious? Semantics? I don't think so. If reactive means taking action after an event it's just optimistic nonsense to use proactive in the sense of taking action before an event. What about predictive? Sounds a bit like standing in your data centre waiting for your twig to twitch or something from the Kaiser Chiefs.  Maybe anticipate? Expecting and planing for (but not stopping) potential future events? How does that help?

Surely what we call proactive just means plain old reactive, but reacting in response to indicative signs giving high confidence that "By the pricking of my thumbs, something wicked this way comes".

If we want advance warning of something undesirable we have to accept the best we can achieve is to get low intensity signs that unambiguously foretell the coming storm. 

From a network infrastructure perspective, these warning signs are increases in latency, round trip time, packet loss and a whole heap of identifiable permanent or transient media issues. Chicken and egg often links these to reduced available bandwidth caused either by increased utilisation or reduced total bandwidth due to incorrect QOS configs, contended lines or any manner of plausibly deniable Telco statements.

For 'apparently' proactive management of network performance take a look at PathView from AppNeta. You'll get advance warning signs for every conceivable network condition and automatically triggered diagnostics to pinpoint what went wrong and how to avoid it in the future.

So if you're still convinced you can be truly proactive go for the lottery or the horses. If you're a pragmatic reactive go for pathview.

Cheers, Cliff.

 

8 Sep 2011

Lack of tools for network performance or just tools found lacking?

I wonder what questions were asked to get the responses published at  IT executives say they lack the tools to manage network performance. We're drowning in a sea of tools from freeware to Rolls Royce but apparently still not enough?

Or, do the respondents have plenty of tools which just don't deliver on their marketing promise. Or, they've bought the tools that should be able to deliver but not deployed them as they're too complicated, or output is difficult to interpret, or didn't budget for the training to get them working?

I think some of the reasons are nicely articulated in Is Your Network Monitoring Equipment Still Working for You?

Me? I'm real happy with my select little set of application performance management tools with pride of place going to PathView to keep the IT foundations running like a dream. If the infrastructure is shakey all else will wobble. 

Network and Application Performance Monitoring Demo

Slow Network? Application performance problems? Watch this short demo to see how PathView Cloud can quickly and affordably help you to pre-assess, continuously monitor and troubleshoot critical applications such as VoIP, Video, Virtualization and any...

Enter your email below if you'd like to get our newsletter for practical performance news tips and tricks.

12 Aug 2011

TryPathView

Slow networks. Some people wonder if there's any other type, often because they simply can't confidently verify the problem is, or is not, the network. Here's a great solution that couldn't involve less risk or pain to try.

With 10 years of impeccable credentials in the US, AppNeta's PathView Cloud hit the UK just last year. It continuously monitors all the vital signs of your network infrastructure (see below) by invisibly exercising it and experiencing the same conditions as your applications. But, where applications and users just groan and get slower, PathView's reaction to declining conditions is to roll up it's sleeves and get stuck in with deep diagnostics to pinpoint where and what's happened.

Sqd
You get continuous monitoring of total capacity, utilised capacity (congestion), available capacity, loss, latency, RTT and Jitter. If its a voice connection you also get MOS reported continuously.

It's described as having "instant value" and in my experience that's entirely accurate. A small download, a 2 minute installation and you're away monitoring and diagnosing to your hearts content. Many evaluations have accurately diagnosed long-standing network problems within minutes. If a download is not for you try a free evaluation using the microAppliance below.

Micro_web2
Don't believe me? Why should you? So get your existing IT supplier to call and grill me. Then if they like it, and think you'd like it, I'll work with them so that you can continue with your trusted supplier through the evaluation stage and beyond. That's why there's no pain for you. Just get someone else you know and trust to recommend taking a look or not. Surely that's about as little risk or pain as you could possibly endure to get started with this great new and unique solution.

Call me, Cliff Chapman, on 023 9265 8344 or 07887 506009 or email cliff.chapman@linkstatus.co.uk and see how PathView Cloud will help you or your customers solve network performance problems.

19 Jul 2011

Road Rage and other Network Problems

Pit a UDP packet against a puny TCP packet and you'll soon see sparks fly. UDP packets veer unpredictably between murderous and suicidal. If TCP packets don't back down quick enough, UDP will either ram them clean off the road or die trying. There's no arguing with UDP. It rampages through the network like bulls in a Spanish street with TCP people scattering in front of them.

When squaring up to UDP, TCP appears conciliatory but quietly seethes waiting its chance to dominate. When UDP bullies are safely ensconced in the pub TCP gloves come off. They turn nasty on each other vying for bandwidth. 

Imagine the race commentary - FTP is gaining ground, fouling Citrix and Exchange to take the lead. A late run from Telnet and Web into the bend and over the fence, but no, FTP is still ahead and somewhere in the melee Telnet and Web have disappeared. Stewards enquiry? Not likely, it's just the cruel Law of the Network. FTP leaves the field victorious with erstwhile competitors strewn the track. TCP stragglers gradually reform and push towards the finish - but what's that sound behind? More FTP - no, worse - UDP is back. Equestrian carnage is only three fences away!

Over time, UDP brute force is eventually overcome by TCP. Creeping, insidious, it has one advantage that UDP cannot match - unlimited reinforcements. Think Lord of the Rings. However, TCP is no quitter, eventually completing but often too late. It's belatedly punching the air but you've already left work, sharing a beer with UDP. 

What's my point?

We all know (or should) that 'visibility' is the first step in any strategy to manage traffic in the way we want it done, not left to the vagaries of protocol and application animosity. Conventional visibility means watching what is going on. But that view is already distorted and influenced by conditions and problems of the entire network infrastructure. You're seeing things how they are, not how they should or could be. You're also seeing them from a single or small number of fixed points looking perpendicular to the network.

Consider taking the view through the network instead. Ride an end to end packet's eye view of your network paths using AppNeta's PathView Cloud. This unique view shows you clearly simply and quickly how well your network is supporting application performance. PathView invisibly tests the underlying infrastructure with detailed layer 3 diagnostics. It also tests network paths with real UDP and TCP traffic to establish what's possible before you consider traffic engineering overlays. Optimization, acceleration, QoS and other techniques all have their place but only when the foundations have already been secured.

Remember this. In a far seeing but overlooked technical paper written by Antonio Sant'ELia in 1944 we find the phrase "All packets are equal but some packets are more equal than others". Clearly an inspiration for George Orwell's allegorical novel about corporate networks published just one year later*.

I suggest you find a Gullible PathView Partner (me, for example) and pretend you want to evaluate the system. The GPP will then provide this system and his help free of charge for around 2 weeks. You use this period to find and fix all the problems in your network then send back the PathView system to the GPP saying it didn't work this time, but you'd like to try it again in a couple of weeks. That's the thing about GPP's - they're so G.

Cheers, Cliff.

*This is not true. Animal Farm was actually inspired by the 1943 Pilot for the BBC cult TV series, Animal Magic. Also, it has been suggested to me that the English translation from Antonio's original paper in Italian may be flawed.
28 Mar 2011

How well will this app work over my WAN?

Logo_tiny_blue
You want confidence that your shiny new app is actually going to work over your WAN. If you're strapped for cash and plenty of time try this. A better solution comes later.

You need to know the smallest capacity bandwidth in the direction of the server to the client and the shortest round trip time for the end to end path between them. Ping is good enough for RTT but measuring bandwidth could be tricky. Failing all else you'll have to trust your telco contract (the better answer comes later). These will help you estimate the best possible performance that network path will support. Be warned - Best Possible Performance will never be achieved in reality.

How to (very) roughly estimate BPP for free? Run the application on a LAN. Download a free copy of wireshark and follow instructions to get a packet capture that contains an example transaction of your new app.  Don't worry what else is captured, we'll filter that out next. From the 'Statistics' menu, select Conversation List > TCP. 

You'll get a pop up screen showing all the conversations that have been captured (so make sure your not also browsing any web sites you wouldn't want your mum to see). Highlight the one you want by identifying the app server address and make a note of the number of packets and bytes transferred in the server-to-client direction. 

Now you know these things. For the network path; bandwidth and minimum round trip time. For the application; how many bytes were transferred and how many packets it took to transfer them. Oh, and remember I said this would be a rough estimate.

Let's say bandwidth is 1M, minimum RTT is 100 milliseconds, the transferred volume is 500Kbytes and the number of packets is 400.

Ignoring overheads a 1M line can transfer 125Kbytes per second so 500Kbytes would take 4 seconds. But RTT is 100 msecs and it is encountered 400 times. This adds 40 seconds to the overall transaction time giving 44 seconds in all. Let's compare that with a LAN.

The transfer rate of a 100M LAN is 12.5Mbytes per second so the raw transfer is 100 x faster at 40 milliseconds. Let's assume LAN RTT is 100 microseconds. 400 round trips therefore adds 40 milliseconds extra delay. Total transaction time is 80 milliseconds.

Now picture yourself thinking "what if I try more bandwidth?". Here's why that doesn't work. Lets say you take your bandwidth 1M to 100M but cannot improve RTT. The raw data transfer reduces from 4 seconds to 40 milliseconds but we still have to add 400 round trips at 100 milliseconds - which is still 40 seconds. The 100M upgrade has just improved the performance from 44 seconds right down to 40.04 seconds!

Also remember that we've just estimated the BPP and that will never be achieved. There will always be other apps on the network consuming bandwidth leaving less for your new app. As bandwidth is consumed the RTT gets worse and you may have packet loss and other such nastiness on your network.

A better way to assess the likely performance of a new app is by

1) Using PathView Cloud to continuously monitor the network paths over which the application is to be run to get realistic values for available bandwidth (i.e the difference between total bandwidth and utilisation) and the RTT. This will also expose previously hidden network problems that will further erode performance.

2) Use those values to set up a WAN emulator, through which you operate the application on a LAN.

You will then directly experience application performance as if you were working from that branch. Testing in this way also allows you to evaluate possible fixes where the performance is unacceptable. Bandwidth and RTT parameters can be adjusted to discover what type of WAN technology is most suitable or WAN optimisation can be tested directly across the emulated WAN so you can see the degree to which performance can be improved. All in the comfort of your own office.

If you have a little bit of money and don't have all the time in the world we can do all this for you. Our Application Readiness service will deploy PathView to gather vital network stats, then bring WAN emulation to your site so that you can experience the branch's eye view of application performance. We can advise about different optimisation techniques that could improve performance and we can actually deploy optimisation in the emulated environment so before and after improvements can be experienced.

The Application Readiness testing is normally performed in a single day. We bring everything required to you. You just supply a workstation and an operator familiar with the application to be tested. Drop me a line if you're interested in understanding how your new app will work over the WAN before finding out the hard (and expensive) way.

Cheers, Cliff.

 

8 Mar 2011

Why NIC Duplex Conflicts Kill Application Performance

Logo_tiny_blue
Networks are created by connecting device NICs (Network Interface Cards) together using Ethernet cables. When two NICs are connected together they must operate at the same speed and duplex. On managed devices you can usually choose fixed settings or a setting called autonegotiate for each NIC. Unmanaged devices always have their NICs set to autonegotiate.

The main cause of NIC duplex conflicts is when one NIC has fixed settings (say 100M full duplex) and its partner is set to autonegotiate. So far, that doesn't sound like a problem does it. Surely the autonegotiating NIC will simply realize its partner is 100M and full duplex and set itself to match. If only! The clue is in the name. If a NIC has fixed settings it cannot 'negotiate' with another NIC so when the autonegotiating NIC tries to 'negotiate' the other end simply doesn't respond. In this situation, an autonegotiating NIC nearly always sets itself to half duplex. 

Why is that crucial to application performance?

Imagine Mary and Fred are two partner NICs. Mary, has fixed settings of 100M and full duplex so can talk and listen at the same time. Fred, ever the diplomat, is set to autonegotiate. Because her settings are fixed, Mary cannot participate in the autonegotiation process so Fred sets himself to half duplex and can therefore only be talking or listening. Sadly, both Mary and Fred operate under the assumption that their partners are set the same as themselves and that's were the trouble starts.

Fred starts talking to Mary but Mary also starts talking to Fred. As Fred beat Mary to start the conversation he cannot hear what Mary is saying and all of Mary's eloquence is wasted (i.e Fred drops all incoming packets from Mary). Mary, assuming that Fred can talk and listen at the same time, continues talking while Fred is talking - more packets dropped.

Now Fred has stopped talking and can listen to Mary but, depending how long Fred was talking for, dozens, hundreds, thousands of Mary's packets have already been dropped and as Mary operates at layer 2 there is no immediate awareness they've been dropped - that comes later. Mary is still talking and now Fred is listening, but can no longer talk, so his transmit buffer begins to overflow with conversations queuing up behind him - more packets evaporate.

By now an unknown number of packets have been dropped in both directions. TCP's job is to recover this situation, recognise packets have been dropped and retransmit them. Things go from bad to worse. First, TCP assumes that packet loss means congestion so it slows down all the flows with the lost packets - a performance killer in it's own right. Second the whole process repeats resulting in a cycle of more packet loss, retransmissions and TCP continuing the ramp down in flow rates because of the perceived but non-existant congestion. 

Imagine now that Mary and Fred are the NICs between a data centre's switch and WAN router and that every conversation for the entire business passes between them. Get the picture? When Mary is talking the entire organisation's users cannot receive anything. When Fred is talking user requests are being simply dropped from the network before they get to the application servers.

That's why duplex conflicts cause unpredictable application performance problems with severities ranging from periodic & mild to complete collapse. 

Duplex conflicts can be detected by inspecting the NIC counters on devices looking for incrementing error or collision counts. That's OK (if very tedious) for devices you own and manage but what about those you don't?

The best way by far, in fact the only reliable way I know, is to use PathView Cloud to test end to end network Paths. PathView let's you see the performance of your entire network from a single screen. PathView's diagnostics include tests to identify and locate NIC duplex conflicts no matter who owns the network devices in the Path.

You can read a much more technically expansive White Paper about the problem here.

Got a long term performance problem that you just can't pinpoint? Sign up to try PathView free. You'll know what's wrong and how to fix it in minutes.
21 Feb 2011

CloudSmart

Our Cloudsmart service is the fastest and most affordable way to fix existing network problems and keep your network fit and healthy. It includes an initial baselining assessment of network health and performance, ongoing continuous performance monitoring, monthly performance reporting and proactive troubleshooting. See the press release.

Today’s leading applications are becoming increasingly performance sensitive. Performance-reliant applications such as VoIP / UC, IP Storage (back-up and disaster recovery), Collaboration, Application & Desktop Virtualization, and SaaS / Cloud services are highly dependent on specific performance parameters such as capacity, latency, jitter and loss.

Organizations often underestimate the task of network assurance prior to deploying a performance sensitive application such as VoIP, VDI, video conferencing to remote locations. Often, this is because the task seems too difficult to perform within constraints of time, resource and budget. The Cloudsmart service, based around the PathView Cloud suite lets you accurately measure how reliable your network will be. It is quick and easy to deploy and includes clear reports that show the condition of the network and actionable recommendations for improvement

PathView Cloud provides businesses with an inexpensive, easy to use means for continuously measuring performance parameters without impacting end user experience. When a problem is detected, PathView Cloud automatically tests each hop in the application delivery path to pinpoint the issue. A mature knowledge base provides detailed information about any highlighted issue, its potential affect on application performance and how to fix it.

Join our mailing list to get your free information pack showing how to keep your entire network tuned for performance. Joining the mailing list is also the first step to free registration for our remote packet capture service.

Email Newsletter icon, E-mail Newsletter icon, Email List icon, E-mail List icon Sign up for our Email Newsletter
For Email Marketing you can trust
4 Feb 2011

Information technology goes global: Tanks in the cloud | The Economist

Media_httpmediaeconom_ecity

"Everyone's gone to the Cloud" tra laa. Except they haven't. Everyone remains forever tethered to the ground by that slim fragile thread called their Internet connection. If this isn't operating at maximum effectiveness and efficiency how can anything else?

But how do you know?

For those that are content to believe their provider's stats and reassurances read no further.

Although the Cloud sounds like a single destination it's clearly (or cloudily) not so surely the best option would be to monitor and diagnose the performance of your link from the end you actually own and control.

That's exactly what PathView Cloud does for you. Get continuous monitoring of capacity, utilisation, latency, round trip time, packet loss, etc. Sounds good? There's more. Hop by hop diagnostics trigger whenever the link falls below the thresholds you've set for any of those parameters. This is pretty cool when you think that none of the Internet devices actually belongs to you. Get clear documented evidence that router IP this is dropping packets or router IP that has a capacity restriction or the link suddenly has massively extended round trip times - as just a few examples.

Find out more at http://bit.ly/aNmECq 

Once you know that your Internet link is whizzing along flawlessly take a look at the the latest developments for Bluecoat's PacketShaper. I used to be PacketShapers greatest fan but the first couple of years of Blue Coat product handling were dissappointing.

But wow, I was at a meeting with them yesterday where I saw the latest and greatest and what's to come. Massive Internet-oriented enhancements. I doubt that even Carlsberg could do it better.

What an exciting time - Yippee

18 Jan 2011

Visualizing Network Performance

How would you like to visualize the performance of your entire network from one screen? That's LAN and WAN - Gigabit to skinny. I really mean performance not just availability or whether a device is responding. PathView Cloud can group, sort and present a live matrix of network path performance, colour coded to show compliance with user-defined thresholds of Capacity, Utilisation, Data Loss, Latency, Jitter and many more essential path characteristics.

Viz-screenshot
For me, Visualization and Deep Diagnostics are the bookends of the spectrum delivered by PathView Cloud, with bags of goodies in between. Take a look at this Prezi about the Visualization features of PathView Cloud from Apparent Networks. You can step through at your own speed.

Watch a little Prezi about it and use the 'More' > Full Screen option so you can zoom in on the screenshots.

I'll follow up soon with another Prezi for Path Diagnostics.

Go easy on me, I'm new to blogging! Hope you enjoy...

Cheers, Cliff.

Contributors

Cliff Chapman