In a previous blog, we discussed medianet performance monitor and how it can provide greater confidence within the network with its ability to analyze voice, video and data traffic and report on loss, latency and jitter.
Plixer International delivers a complementary solution that supports the medianet performance monitor feature through the medianet Cisco Developer Network (CDN) program. CDN for medianet systems management offers application programming interfaces (APIs) and documentation to enable network and application management vendors to support enterprise medianet features that offer customers a range of management and operation solutions.
On March 29, Plixer’s Scrutinizer NetFlow Analyzer version 8.5 successfully completed interoperability testing with Medianet 2.2 (press announcement). Scrutinizer provides detailed reports including the medianet performance monitoring statistics (round trip time, jitter, packet loss, bit/byte and packets, MAC Addresses, IP Addresses, VLANs, Domains, application recognition) to help you monitor and troubleshoot video, voice and data applications. These reports can help the network operator perform fault isolation of network issues affecting rich media applications, as well as track historical performance of various parts of the network.
Yesterday, I blogged about the “good-enough” network. You know, it’s a network that just good enough to send out a quick email or watch a video, but not quite fast or reliable enough to do everything you need.
It may be easier to think of the good-enough network in terms of other areas of your life where good enough just doesn’t cut it.
For instance, a 19-inch tube TV is certainly good enough for watching reruns of “Magnum P.I.,” but not for watching the big game.
Or using SPF 5 sunscreen may be good enough, but SPF 30 is a way better option if you want to avoid a sunburn.
Just imagine if your customers settled for a good-enough network? It may go something like this:
What are the seven myths about the good-enough network? Read More »
We’ve all settled for less in our lives. Maybe you bought a pair of shoes that were a little tight, but the sale price was way too good to pass up. Or perhaps you got a brand-new digital camera that wasn’t exactly the one you wanted, but last year’s model way a much better price.
While everyone loves getting a good deal, sometimes buying the less expensive option means sacrificing quality. You’d pay good money to make those blisters on your feet disappear and when those pictures of your daughter’s graduation don’t come out, you curse yourself for spending less.
When it comes to the network, saving a few dollars up front may sound good, but losing the ability to capitalize on trends such as video, mobility, and cloud just don’t add up. (And may cause headaches down the road.)
In fact, research shows that over the long run, it may not even be the most cost efficient. Building a tactical network based on low-cost point products and services increases the total cost of ownership for most organizations by at least 20 to 35 % over a three-year time frame, according to the white paper “Debunking the Myths of A ‘Good Enough’ Network.”
The white paper findings also indicate that a network is only as reliable as its weakest link. And saving a bit of money on a router may be offset by the cost of an outage – and then some. That’s just one of the seven deadly network sins.
What are the other seven deadly network sins? And what should you know about a multi-vendor approach to building business-critical networks?
Tune into our webcast, hosted by Rob Lloyd (Cisco’s executive vice president of worldwide operations) to find out. The webcast will also feature executives from The Royal Bank of Scotland and Cisco Gold Partner BlueWater Communications Group.
Finally it’s here. Cisco has been working on integrating the Media Services Interface (MSI) into the WebEx Meeting Client.
For those unfamiliar with the MSI, it’s an SDK developed to enable applications to interact with a Cisco Medianet. One of the long standing challenges IT organizations have faced has been to harmonize the needs of applications and endpoints with the network services required to meet those needs. It’s been a case of ships in the night as network administrators have done their best to deliver services while having limited interaction with the endpoints and applications that leverage those services. Asking endpoints and applications to consistently implement all the networking protocols to enable them to leverage the network has often led to mixed results; inconsistent or incomplete protocol stack implementations led to interoperability issues with the burden usually falling on the end customer.