Today’s Secret Sunday is a shout out to the excellent Jeff Fry, aka @FryGuy_PA on Twitter. Jeff blogs at FryGuy.net where among other things he has previously broken the news on upcoming Cisco products a couple of times by close … Continue reading
If you liked this post, please do click through to the source at Secret Sunday – Jeff Fry and give me a share/like. Thank you!
If you’re just starting out working with ‘Enterprise’ products, you may not have come across Support Lifecycles. It’s important to know what these are, and how it affects you. They can have both a positive & a negative impact on when and why you choose to upgrade systems.
Developers would like to only support the latest version. But customers can’t/won’t always run the latest version. They need to know that they can expect a certain level of support for the version they’re running. As a compromise, software vendors will publish a support lifecycle policy. This will outline the levels of support a product gets, from new product introduction, through to being superceded, and finally moved to end of support. Typical phases include:
This stuff still totally blows my mind. I was at a restaurant for lunch recently with some colleagues. Service was slow, and as a result I was going to be late back to the office, and I had to join a … Continue reading
If you liked this post, please do click through to the source at Lync – This Still Blows My Mind and give me a share/like. Thank you!
Continuing our regular look at the news in Networking and Cloud.
The post Network Break 19 appeared first on Packet Pushers Podcast and was written by Greg Ferro.
Shellshock was released a little over a month ago, to wide predictions of doom & gloom. But somehow the Internet survived, and we lurch on towards the next crisis. I recently gave a talk about Shellshock, the fallout, and some thoughts on wider implications and the future. The talk wasn’t recorded, so here’s a summary of what was discussed.
Attend enough meetings, and sooner or later you’ll be called upon to present. I was ‘volunteered’ to speak on Shellshock, about a month after the exploit was made public. I didn’t talk about the technical aspects of the exploit itself – instead I explored some of the wider implications, and industry trends. I felt the talk went well, mainly because it wasn’t just me talking: everyone got involved and contributed to the discussion. It would be a bit Continue reading
.JPG)
package main
import ("fmt")
func HelloWorld() {
fmt.Println("Welcome to my blogn")
}
We are getting into the Halloween spirit here at Plexxi—check out this Plexxi pumpkin carved by our talented marketing manager, Khoa Ma!
Jack-o-lanterns aside, we know the thought of navigating trends like the Internet of Things and Big Data can be frightening, especially if you are unsure of how to approach them. As these trends gain popularity and deployments increase, IT architects often worry about increased activity on already taxed infrastructures. Our own Mike Bushong is our resident expert on this topic and he penned an interesting blog post this week on networking’s atomic unit and “going small to scale up.” Creating smaller units of capacity makes the network easier to manage, and most importantly, scale. It’s definitely worth a read before heading out to trick-or-treat.
In this week’s PlexxiTube of the week, Dan Backman explains failure scenarios in case of hardware or software outages in a Plexxi pod design.
Network architect Brian Heder contributed an article to Network World this week on the importance and challenges of simplicity in computer network design. While I think Heder’s list is solid, I would add an additional obstacle to network simplicity: customization. Avoid making your network environment Continue reading
The rise of software licensing in networking changes some of my assumptions about the 5 year cost of ownership of products. Roughly, lets assume that you are buying virtual appliances like firewalls, DNS/DHCP, IDS/IPS, proxy servers and load balancers and that you pay some type of yearly license to use the product. Capital Upfront The legacy […]
The post Musing: Subscription License Economics appeared first on EtherealMind.
Burst sizes need to be calculated if you are implementing policers or shapers on Junos devices so that the policer or shaper can control the flow of traffic appropriately. Too small a burst size and TCP applications will have terrible throughput. Too large a burst size and the policer won’t be very effective – the bursts are so large they cancel out the effect of the policing because as one burst ends another one is just about to begin.
The situation is described reasonably well on the Juniper site here, and also in O’Reilly’s excellent MX book. But in both places the mathematics of the calculation is hidden in a paragraph of text – not written out properly and showing the workings. That makes for confusion in my mind.
It’s actually a fairly easy calculation, but isn’t presented well. I finally sat down to work out what it meant.
The easy way to calculate burst size for low bandwidth (i.e. T1/E1 etc) interfaces is 10 times the MTU of the interface. The problem with this is (as you see in figure 3 in the Juniper link above) that on 1500-byte Ethernet this Continue reading
I have a list of things I mean to blog about, and the Junos Apply-Path feature has been on there for way too long without being actions. As I said when I kicked off the “30 Blogs in 30 Days” … Continue reading
If you liked this post, please do click through to the source at Junos Apply-Path – A Step Closer To Heaven and give me a share/like. Thank you!
“Now, as you look through this document you’ll see that I’ve underlined all the major decisions I ever made to make them stand out. They’re all indexed and cross-referenced. See? All I can suggest is that if you take decisions that are exactly opposite to the sort of decisions that I’ve taken, then maybe you […]
The post Halloween Career Advice from the Damned appeared first on Packet Pushers Podcast and was written by Glen Kemp.
Smart Televisions are tracking everything you do and sending that data to unknown services: The amount of data this thing collects is staggering. It logs where, when, how, and for how long you use the TV. It sets tracking cookies and beacons designed to detect “when you have viewed particular content or a particular email […]
The post Response: I’m Terrified of My New TV appeared first on EtherealMind.
It was a dark and stormy Halloween night and a networking engineer was stuck in a data center facing a Mission Impossible project: replace a failing Cat6500 with a brand-new Nexus 7000. Shouldn’t have been a problem, if only the cables were labeled.
Read more ..."After all, what's the best part of Halloween?" Jimmy pleaded over the phone. He was trying yet again to convince Tom to skip work for the night and head over to the party he was throwing. Tom and Jimmy were good friends, but he already knew how the conversation was going to end.
"I dunno, the candy?" Tom played dumb.
"No, the eye candy! I'm telling you bro, you don't want to miss it. Rachel will be there." Jimmy sang the last bit tauntingly.
"I told you," Tom countered. "I've got work." It was around 6pm now, and he was just pulling into the parking lot outside the data center where he planned to spend the night recabling several racks of equipment. The scariest part of his Halloween would be picking through years' worth of undressed patch cabling.
"I don't get why you have to do that shit at night anyway. Why can't you do it during the day when you're stuck at work anyway?" Jimmy prodded.
Tom parked across from the building's entrance and turned off his car. Other than a couple vehicle belonging to the operations staff, the parking lot was deserted. He Continue reading
