"In fact, I was talking with someone the other day," said Jim Metzler. "I don't need to be dramatic, but he said to me, 'Jim, I look at Web 2.0 the way I look at global warming. We're just beginning to realize how serious global warming is and take some steps now. We're not there yet on Web 2.0, but it will have a dramatic impact."

We talked a little bit about how broadband is causing end-users to expect more from the Web apps that they use for work, but here's a basic recap: If a user is used to waiting less than 5 seconds for a YouTube video, they may not be as willing to wait 30 seconds for a database. Things are getting faster, and as such there should be a new emphasis on providing performance.

We are used to information in real-time. Our growth of interconnectedness - indeed, the growth of community - has driven us to new expectations.

So we talked to Jim Metzler about whether Web 2.0 is creating new requirements in network performance.

"I think they will once they get more broadly deployed. I actually think that things like SOA and Web Services, Web 2.0, are going to significantly rachet up the need for a more dicisplined performance management, but I don't think people realize it yet…. I think we're still kind of kicking the phrases around. People are saying, 'Oh, Web 2.0, that's all marketing hype, no one knows what that means, yadda yadda yadda' So I think we're still in the denial stage. But I think that, over time, it will have a significant impact on the need for performance management and how we do performance management."

So, what can companies do about Web 2.0?

"I think where's there's SOA Web services, the bottom line is, for starters, we can't chart a course to improve, if we don't know where we're going. It's as simple as that on one level. So we need to continue to educate ourselves as to what exactly Web 2.0 is. And you're not going to be able to get a very precise definition, but you begin to read and see some commonality. 'Is my company heading in that direction? If not Web 2.0, how about these SOA Web services?'"

"I think that on the infrastructure side, to understand the evolving application disciplines, architectures, whatever you want to call it, not, so to speak, just in general but as their company is evolving to it, to figure out what that means for them - Initially it just comes down to guessing at the high level picture and then coming down closer to the ground. As you have some of the monitoring tools that people are deploying, they begin to place more emphasis to understanding the flow of data in an application."

"Becoming more application aware today, not just what applications are running on the network, (that's a good starting point,) but how do they actually transfer data and where are the performance roadblocks? So, it's kind of getting a handle on today while beginning to understand where we're going to evolve to over the next one to five years."

When asked if there was anything else he wanted to mention, Jim Metzler said: "Let's hope the Red Sox can beat the Indians."

By Brian Boyko
Editor, Network Performance Daily

We were supposed to have the video of Dr. Steve Fulton we put up on Thursday night up by Wednesday afternoon. That didn't happen.

By coincidence, we also saw this opinion piece by John Dvorak, and linked to it the day before we needed the video to go up. The article, entitled "Don't trust the servers," talks about problems with Windows Genuine Advantage and how it illustrates the problems with SaaS solutions - that you're eternally dependent on a third party to continue to provide service.

In our case, we rely on Google Video to provide the bandwidth and hosting for the videos in our Whiteboard series. Now, you can say what you want about "getting what you pay for" and the like, but when we couldn't upload our video to Google, I realized how dependent I had gotten on their SaaS video hosting solution.

I couldn't log-in to upload the videos. At first I thought the problem was at my end - perhaps Symantec Anti-Virus had caused some sort of conflict or had firewalled off the ports that Google's video uploader needed. That wasn't it. Maybe it was something with our in-house network. That wasn't it either, as I found out when I took a copy of the video home and tried to upload it from both my Windows XP and my Linux partition. Nada. Zip. Zilch.

Despite the fact that Google's help files had a ready - and wrong - answer to every problem I came across, the problem was entirely Google's. And there was nothing I could do about it until they finally fixed whatever the problem was the next day.

See, while there are a number of video hosting solutions out there, Google Video and Veoh were the only ones that allowed me to upload clips more than 10 minutes long - and Veoh's playback was poor. Even if I could re-code the entire video at a lower resolution to lower the filesize, that didn't matter. Ten minutes was the hard limit on YouTube (also owned by Google) and other sites. My 25 minute video needed Google Video.

Eventually I was able to get the video uploaded, and though it took a while to process, it went up last night.

This isn't the first problem we've had with SaaS. Expensable.com often goes down for a few hours and we can't log expense reports. I use Gmail for my personal e-mail and while it's generally reliable, it does have some problems.

All in all, if you're looking at it from a productivity or a network performance view, moving your apps from the local network to a third party service - well, yes, it will absolutely save bandwidth and may make the network run faster for your other apps. But having a faster network doesn't mean anything if the end-user is waiting for a third-party service as long or longer as they used to wait for their slow-loading WAN apps. Or, in other words, you're not solving the problem of slow performance from the perspective of the end-user. You're just shifting blame.

This is not to rag on SaaS. I haven't lost an e-mail since I started using Gmail in 2004. My Flickr account saved pictures of my deceased friend John when my hard drive stopped working one day. And if it wasn't for YouTube, I'd never be able to show my parents in Virginia anything about my life in Texas.

But these experiences are a bit of a wake-up call that SaaS isn't going to solve every problem. Ultimately, the end goal of enterprise network performance is not to keep the network running as fast as possible, or to free up as much bandwidth. It's about finding the solutions which make the end-users more productive and enabling the company to do more as a result.

This phenomenon isn't limited to the Gummi Bears. There were protests in Mexico over the rising price of corn tortillas. German beers are feeling the pinch as farmers trade in hops and barley for the more lucrative rapeseed and corn. Jolly Time Popcorn isn't feeling so jolly after corn prices went up 70 percent. Between the double whammy of increased cost of corn and increased cost of every other crop because farmers are switching to growing corn instead, it's gotten to the point where it's cheaper to feed livestock, such as pigs, human snack food, according to the Wall Street Journal.

Back to network performance. Consider for the moment, that the path of the food we eat, from raw ingredients to our supermarket shelves consists of a "network" of sorts, this is a classic case of a sudden, unanticipated spike in demand from another endpoint in the network that is wreaking havoc on the network itself. Or, farmers switching to corn at the expense of other crops seems like a classic case of over provisioning one "application" on the network at the expense of all others.

These changes may have seemed insignificant at the time. Many disruptive changes do, which is why you need to have good visibility into your network - whether it's an enterprise network or a food distribution network.

Even a slight increase, for example, in network demand has a number of ancillary costs that many people don't look at. Greater demand of resources doesn't just require more bandwidth. It may necessitate greater processing power, which necessitates more hardware, which necessitates more power and more cooling.

I mean, when even the cost of alternative fuels are going up, many more people are going to be telecommuting from their homes instead of driving or flying in for business. If you're not prepared for a change like that by being aware of how your network is being used, and what changes are coming down the pipe, your network is in just as much trouble as the Gummi Bears are.

The big problem with WAN Optimization and Application Performance Monitoring was that there simply wasn't a WAN Optimization solution on the market that preserved end-to-end performance data, nor a monitoring solution that would work in an optimized WAN.

This problem has been solved.

At Cisco Networkers in Anaheim, NetQoS gave a presentation to hundreds of attendees to make the announcement that we've been working with Cisco to develop a management interface for accurate end-to-end application response time measurement that works on optimized networks. (In addition to the people mobbing our booth, John Chambers, CEO of Cisco Systems, stopped by for a chat and review of what we do.)

Through integrated software on Cisco Wide Area Application Services devices (WAAS), TCP header information is exported to NetQoS SuperAgent (an end-to-end application performance monitoring module) before optimization occurs - preserving that information. Finally, IT organizations can accurately validate the results of WAN Optimization deployments.

(Continued…)

Continue reading "Tracking The Optimized WAN: NetQoS Integrates with Cisco WAAS to Deliver End-to-End Application Response Time Reporting for WAN Optimization" »

By John Mao, Product Manager at NetQoS

Cisco's NetFlow technology provides flow statistics from IOS-enabled routers capable of characterizing traffic on a network. Information provided by NetFlow includes network protocols, ports, IP addresses, and much more.

Five years ago, NetFlow was a new buzzword floating around various companies' networking groups. Some immediately saw the management benefits it could provide while others continued to use the network probes they knew best. However, fast forward to today, and a large majority of engineers are intimately familiar with the benefits and uses of NetFlow.

Although initially implemented by Cisco, NetFlow is emerging as an IETF standard: Internet Protocol Flow Information eXport (IPFIX). Based on the NetFlow Version 9 implementation, IPFIX is going to be the industry standard in the very near future. Network infrastructure vendors, including Nortel and others, are already adding IPFIX support to their enterprise switches and routers.

Thousands of IT enterprises worldwide have embraced NetFlow technology which is capable of providing them the same flow information traditional probes provide. Because of the lower cost to deploy and maintain NetFlow, it is easy to see why so many have made the switch.

The router's memory can retain the vast amounts of in-depth statistics only for a short time. NetFlow/IPFIX Management products (like NetQoS's own ReporterAnalyzer) export the NetFlow data periodically, store and parse the data.

That said, here are six tips for improving network visibility and performance using the NetFlow data that you're probably already getting from your routers. These tips work best with ReporterAnalyzer (hey, it's our company blog and if we didn't think our products were the best, we wouldn't be making them), but should be helpful even to those using more basic tools.

(Continued...)

Continue reading "NetFlow Monitoring: Six Tips for Improving Network Visibility and Performance Using Cisco IOS NetFlow Data" »

By Brian Boyko

Fingerpointing - it's a frustrating and lingering problem for IT organizations. Whenever, application performance degrades, all of a sudden application, server, and networking teams start pointing the finger at one another in an attempt to pass the blame. But isn't that why we have network monitoring tools in the first place - to tell you where the problem is, so that you can fix it faster.

Theoretically, yes. Unfortunately, network teams may be suffering from an undeserved "credibility gap" that prevents companies from taking timely action when problems arise.

For so very long, problems with network performance have often been laid at the feet of the networking team because, quite frankly, to the end user, an application problem, a server problem, and a network link problem all look like the same thing. "The network is slow." So even when it's not the network, the network team often gets the blame.

(Continued...)

Continue reading "Fingerpointing, Frustrated Network Engineers, and the Application Performance Blame Game" »

Ben Erwin, product manager at NetQoS, quickly explains the impact of WAN Optimization on TCP-based Applications in a short video, kicking off our "Whiteboard Series."

If you have questions about the video, please leave a comment below and we'll do our best to answer them.
--------------
More information:

On WAN Optimization:
- NetQoS and Cisco Webinar: Evaluating WAN Optimization Options and Quantifying the Results

Also in our Whiteboard Series:
- The impact of WAN Optimization on NetFlow/IPFIX measurements

With Ben Erwin:
- Third Party Integration and UI in the Enterprise

WAN Optimization solutions are designed to do a couple of things: increase the performance of applications running over the WAN by reducing latency and help companies achieve efficiencies in bandwidth usage. This can help avoid costly infrastructure upgrades and reduce the downtime and lost revenue associated with poor network performance.

For most companies, a big value proposition of WAN optimization is data center consolidation. If you can make your WAN performance rival that of your LAN, you can do away with remote data centers and repurpose or liquidate the expensive hardware in each branch office.

It also simplifies making backups in preparation for disaster recovery because much less data needs to travel across the link in order to get a full backup of the branch office to the home office. It becomes feasible to back up key data remotely on a regular basis. (The alternatives are to saturate the link with a scheduled backup, hire on-site staff simply to do the backup, or trust that the end-users will back up their data locally - which isn't much of a guarantee.) Keeping your data backed up and in one central location also means that it will be easier to verify compliance with government regulation.

There is also a "green effect" as it may also cut down on power requirements too - similar jobs done by separate servers in each branch office can now be handled via a single server at the home office, running virtualized server environments. While that one server requires more CPU cycles, chances are the tradeoff will result in lowered electricity needs. And of course, it eliminates maintenance costs for all that hardware, and the ability to keep your IT staff in your home office rather than sending them on planes to the four corners of the earth when something goes wrong.

There are numerous trends driving the demand for WAN optimization. So, how do you know where you can get the biggest improvements from your investment? Which applications will benefit the most? And, what about the pitfalls? One of the downsides to WAN optimization is that is obscures end-to-end performance monitoring for TCP applications because it breaks the connection between client and server into three separate segments. Most WAN appliances also obscure Netflow data which is used for security and traffic analysis purposes. Traffic prioritization via QoS can also be interrupted. Some WAN optimization solutions address these concerns. Others do not.

-----------------------

Network Performance Daily will address these questions in a series of upcoming posts on WAN Optimization. Subscribe to our RSS feed to get weekly updates. Also, chime in with your thoughts on what you hope to get from deploying WAN Optimization in your organization. Feel free to leave comments below.

Julie Bort interviewed George Kurian at Cisco in Network World, where they talk about WAN optimization.

The interview talks about how Cisco's optimization and acceleration products are distinguished from competitors' and (of course, considering that George Kurian works for Cisco) promoted as superior because of their transparent placement in the network. This means they can be shared among several servers and applications, as well as integrated with Cisco's existing products, and QoS and security policies do not have to be migrated or disrupted. One item only barely touched upon is the idea of using a single appliance in the branch office - the Integrated Service Router - to handle WAN optimization, security, and routing - and how having one appliance to handle all these tasks helps cut down on server room clutter and complexity.

To be sure, these appear to be advantages to Cisco's solution. But the dirty little secret is that all WAN optimization solutions on the market, including Cisco's, obscure end-to-end performance metrics. This is a major issue, of course, and makes the current state of choosing whether or not to deploy a WAN optimization solution a Monty Hall problem - do you opt to retain visibility into your network performance and the ability to solve problems faster, or you deploy a WAN optimization device and hope that whatever's behind curtain number two (the resulting performance gain) is better than what you've traded for?

Maintaining transparency of response time and latency metrics is critical in our view and any WAN optimization vendor that provides a solution to this problem will have a serious competitive advantage.

*Update on Wafaa Bilal and Recreational Network Traffic

The Brain Behind Paintball Artist Bilal: ‘Domestic Tension’ Sysadmin Jason Potkanski talks about how he helped keep the paintball-via-webcam site running.

Jason Potkanski, who works at the Citizendium Foundation, read the Chicago Tribune Daywatch, to find Wafaa Bilal’s site, Domestic Tension. He looked at the site and saw that it was getting swamped over a DSL link. He sent Ben Chang, lead software programmer of the project, an e-mail offering help, and got an answer back the next day. He visited the project site at the Flatfile Galleries on the 11th – a day when the gun was down most of the day due to the strain that the Internet was placing on the connection – the DSL line and commercial-grade router they used were taking a beating from the Slashdot-like effect of a small pipe.

He immediately offered some performance optimization techniques, such as setting keepalives to 3, and installing eAcellerator to speed up the PHP script, replacing the memory inefficient tail function for the chat. And of course, he told Bilal that he would need a dedicated line to the Internet, and by the next day, they got an OC3-quality connection to Steadfast, at Equinex in Chicago. Immediately he saw an improvement.

He also mounted the webcam image and chatlog/shooter log via NFS, remoted in to do the mounts and copy the application over to the Steadfast connection.

Another problem was the use of XML requests, which wasn’t viable on all browsers, and the fact that the original configuration kept three separate requests open for the chat, the shooter log, and the web cam.

If he had the system to design all over again, he’d design it to use a backend database for the logging features, combine the shooter log and chat so that the application requires only two keepalive connections, not three.

(Continued...)

Continue reading "The Brain Behind Paintball Artist Bilal: ‘Domestic Tension’ Sysadmin Jason Potkanski talks about how he helped keep the paintball-via-webcam site running and Recreational Network Traffic." »