The answer that you get from your vendor is never a __YES__ , or, not directly. This handy guide is the eight levels of vendor acceptance where answers
Was accessing some Juniper documentation today, and found this. It’s a very neat feature that’s let you download all the documentation for JunOS in a single-ish download.
Collection of useful, relevant or inane places on the the Internets for 23 Sep 2011:
One of the problems of working with the PRINCE2 practitioners is that the people tend to get highly focussed on definitions in the Scope of Works. A Scope of Works defines what the deliverables the customer is to received.
The problem with a Scope of Works is that it is usually prepared before the work is started and/or fully understood. maybe you have a Gap Analysis, or a Consulting Reports or a Requirements Document to setup the initial engagement (every company has their own name of the same thing).
It’s obvious #VXLAN was conjured up by a cloudtard. Simple minds devise simple solutions without seeing the complex problems they missed. Here are five things that VXLAN tells us about the networking industry.
OpenFlow has made a big splash after some high profile funding announcements. As we move into the next phase of product development and even early delivery, it’s important to engage with a wider commercial audience to share the vision and the opportunity that OpenFlow presents.
OpenFlow is a standard for exchanging flow rules between a controller and network device and has the potential to impact networking in a big way. In a similar way that the TCP/IP protocol turned local area networks into the global Internet, OpenFlow has potential to change the control plane of modern networks in a whole new way that enables Software Defined Networking.
We’ve invited a wide range vendors and speakers to share their strategies, discuss the possible options and overview the current state of technology. In two sessions, we will cover the technology and the business opportunities of OpenFlow.
Collection of useful, relevant or inane places on the the Internets for 14 Sep 2011:
So, the venerable Catalyst 6500 staved off execution and received another 10 years of life with the recent announcement of the Catalyst 6500 Supervisor 2T. Should we celebrate the extension of life in old assets, or look for a different answer to a Cisco switch upgrade ? In other words, would this Parrot VOOM if you put 30 million volts through it ?
Now that this has established that a Switch Fabric has buffers, I want to flip back into something practical about this application. Lets use an example of four servers connecting to single switch and sharing an Ethernet Storage Array. The array might be using iSCSI or FCoE to delivery SCSI applications to the Servers. The nature of storage traffic is such that it has transient spikes in traffic that must maintain low latency and should not be dropped.