Original content from Roger's CCIE Blog Tracking the journey towards getting the ultimate Cisco Certification. The Routing & Switching Lab Exam
The post describes the process of how to upgrade the IOS / Software on a Cisco 4500X switch. I will not be covering how to do a hitless upgrade using ISSU with 2 switches in a VSS pair. This process is performed on two switches which are not in production. So to perform the upgrade... [Read More]
Post taken from CCIE Blog
Original post How to Upgrade IOS on Cisco 4500X Switch
In this post, I dive deep into 802.11 medium contention to understand how it works as a precursor to the final blog post in this series where I’ll detail the two main sources of medium contention, identify Wi-Fi's breaking point (that'll be fun, stay tuned) and how this affects proper WLAN design in order to optimize wireless networks to prevent medium contention from killing your WLAN performance.
Read the full blog post over on the Aruba Networks Tech Blog...
This is the third blog post in a series about WLAN capacity planning. Be sure to read the first and second posts.
Cheers,
Andrew
This post is just a quick response to a comment by Turing Machinæ on Show 227 – OpenStack Neutron Overview with Kyle Mestery, which was “I’ve learnt absolutely NOTHING about openstack from this podcast.” Whilst I don’t agree I have some empathy; time and time again I’ve found myself hitting a brick wall recently when […]
The post OpenStack Neutron – The Dirty Network Detail appeared first on Packet Pushers Continue reading
Centec enters the 10G age with its newest switch chip.
Here's a small Go gotcha that it's easy to fall into when using goroutines and closures. Here's a simple program that prints out the numbers 0 to 9:
(You can play with this in the Go Playground here)
package main
import "fmt"
func main() {
for i := 0; i < 10; i++ {
fmt.Printf("%d ", i)
}
}
It's output is easy to predict:
0 1 2 3 4 5 6 7 8 9
If you decided that it would be nice to run those fmt.Printf
s concurrently using goroutines you might be surprised by the result. Here's a version of the code that runs each fmt.Printf
in its own goroutine and uses a sync.WaitGroup
to wait for the goroutines to terminate.
package main
import (
"fmt"
"runtime"
"sync"
)
func main() {
runtime.GOMAXPROCS(runtime.NumCPU())
var wg sync.WaitGroup
for i := 0; i < 10; i++ {
wg.Add(1)
go func() {
fmt.Printf("%d ", i)
wg.Done()
}()
}
wg.Wait()
}
(This code is in the Go Playground here). If you're thinking concurrently then you'll likely predict that the output will be the numbers 0 to 9 in some Continue reading
I hate getting into lengthy discussions regarding open networking (or bare-metal) pricing as there are benefits other than price. However, with so many people trying to understand the industry transition, I feel compelled to jump in when I see confusing information.
Forrester analyst Andre Kindness recently published a report called The Myth of White-Box Network Switches which is causing a pretty interesting debate. The discourse forms, as Andre puts it, “I think there is misunderstanding/reading my research. I’m not saying one solution is cheaper. It highlights the cost”; however, the title of the report necessarily creates bias. Luckily, we had a chance to speak with Andre to better understand his perspective and intentions as well as relay our observations.
For the hardcore, we’ve gone through some of the market basics in prior blog posts; most notably Democratizing Capacity and Death of the Multipler Effect. Some of the absolute numbers in those analyses have changed; however, these hold true and directly relate to both the points that Andre was trying to make as well as the gaps in his analysis.
The report makes two observations that we completely agree with. One is that, most of Continue reading
Cabling up a 100G link for a customer test we discovered we needed to buy a couple of 100G cables. The interfaces involved were multimode, and use parallel optical paths – i.e. 10 parallel fibres each carrying 10Gbps within a single cable.
It turns out the world of such cables is a bit confusing in its terminology. Some people call these cables MTP, and others call them MPO. After a bit of digging, it turns out that they’re basically the same, but MTP is a brand name for a connector that complies with the MPO standard. The brand is owned by a company called USConec. Confusion over…
There’s quite a nice photo close-up of this connector type available on Completeconnect’s website – here. You can see the parallel fibres in the end of the interface. The cable has 24 fibres in, but only 20 are used – 10 in each direction giving full duplex connectivity at 100Gbps.
The male-ness and female-ness of these types of connector is quite difficult to determine. If you see a pair of pins protruding from the connector at either end of the two rows of fibres, Continue reading
This white paper created for F5 Networks, will focus on useful tips and pitfalls to avoid during NFV implementation.
Most financial service firms, which includes banking and insurance companies, are engaged in a big data project to increase the pace of innovation and uncover game-changing business outcomes. The pressing challenge now is how to drive more continuous value and unearth opportunities more rapidly.
No matter where you might be in your big data journey, the following three-step approach to integrating big data into an analytics strategy can lead to success:
To drive continuous and transformational improvements through big data-driven analytics projects, business units – IT, marketing, risk, compliance or finance, for example – should agree on and outline a mutually beneficial business objective. For instance, driving a better customer experience or improving customer value management. While developing the common objective, financial services firms should also determine the aligned and desired outcomes, such as decreasing fraud and offering more personalized services to customers in real-time.
To read this article in full or to leave a comment, please click here