Archive

Category Archives for "Networking"

Dell EMC Expands Server Capabilities for Software-defined, Edge and High-Performance Computing

Dell EMC Expands Server Capabilities for Software-defined, Edge and High-Performance Computing Launches highly capable enterprise-class single- and dual-socket servers Breaks down the cost barrier for deployment of emerging workloads Offers up to 20% better TCO per four-node cluster for vSAN deployments at the edge and are now available as vSAN Ready Nodes Dell EMC announced three new servers designed for software-defined environments, edge and high-performance computing... Read more →

Tune Into Our CCIE SPv4.1 Advanced Technologies Course This Wednesday and Thursday!

Join 5 time CCIE Rohit Pardasani for our new online live sessions, CCIE Service Provider v4.1 Advanced Technologies. These live sessions are available to All Access Pass members via our live classroom interface, which you can access through your members account. For those who are not All Access Pass members, you can view and purchase AAP packages here. Read on to learn more about this online live class.

When: Wednesday, February 7th & Thursday, February 8th at 8 am PDT

Why You Should Watch: This SPv4.1 class will complete the SPv4.1 courses and bring us current for the Cisco Service Provider Blueprints.

Instructor info: Rohit Pardasani, CCIE #21282, CCSI #34999

About the Instructor:

Rohit has been in the networking industry for more than 17 years, with a focus on Cisco networking for the past 15 years. Rohit not only brings his years of teaching experience to the classroom, but also years of real-world enterprise and service provider experience. Rohit has assisted hundreds of engineers in obtaining their CCIE certification, and has been conducting CCIE RS, CCIE SEC, CCIE SP and CCIE Collaboration for Cisco Systems worldwide. Rohit currently holds 5xCCIE’s (Routing Switching, Service Provider, Security, Voice and Continue reading

Cisco says almost all workloads will be cloud based within 3 years

In its latest Cisco Global Cloud Index (2016-2021), the networking giant predicts that by 2021, 94 percent of all workloads will run in some form of cloud environment and that dedicated servers will be a distinct minority.That 94 percent covers both public and private cloud scenarios, which means even in an on-premises scenario, almost all workloads are going to be run in a virtualized environment. The days where a server is dedicated to one workload are rapidly drawing to a close.“We use the definition of one workload or instance with one physical server,” said Thomas Barnett, director, Cisco Service Provider forecast and trends. “In virtual scenarios, we’re seeing one workload with multiple virtual machines and containers. Based on growth in public cloud, we’ve overcome some of the barriers of adoption, such as cost and security and simplicity of deploying of these services.”To read this article in full, please click here

Cisco says almost all workloads will be cloud based within 3 years

In its latest Cisco Global Cloud Index (2016-2021), the networking giant predicts that by 2021, 94 percent of all workloads will run in some form of cloud environment and that dedicated servers will be a distinct minority.That 94 percent covers both public and private cloud scenarios, which means even in an on-premises scenario, almost all workloads are going to be run in a virtualized environment. The days where a server is dedicated to one workload are rapidly drawing to a close.“We use the definition of one workload or instance with one physical server,” said Thomas Barnett, director, Cisco Service Provider forecast and trends. “In virtual scenarios, we’re seeing one workload with multiple virtual machines and containers. Based on growth in public cloud, we’ve overcome some of the barriers of adoption, such as cost and security and simplicity of deploying of these services.”To read this article in full, please click here

IDG Contributor Network: How to overcome infrastructure firefighting and other distractions

As an IT professional, you were hired for a certain, specialized job. But why can’t you seem to get it done? Maybe you’ve been busy “fighting fires.” For anyone responsible for network infrastructure, that’s a leading culprit. But there are others.On the theory that to solve a problem first you need to identify it, we’ve listed a number of obstacles that may be keeping you and your team from the mission-critical parts of your jobs. Taking note of these distractions can be a first step toward fashioning solutions that lead to better outcomes for you and your organization.Infrastructure firefighting When things don’t go according to plan and you have to trade your strategic IT roadmap for tactical reactionary decisions - that’s infrastructure firefighting. The network may not be working as intended; capacity planning may be off mark; production issues could be causing outages, requiring in-depth explanation and research to mitigate repeat outages in the future. Outages may require special actions, as we discuss in this article. You may not have signed on to extinguish unwanted fires, but like it or not, that has become part of your job.To read this article in full, please click here

IDG Contributor Network: How to overcome infrastructure firefighting and other distractions

As an IT professional, you were hired for a certain, specialized job. But why can’t you seem to get it done? Maybe you’ve been busy “fighting fires.” For anyone responsible for network infrastructure, that’s a leading culprit. But there are others.On the theory that to solve a problem first you need to identify it, we’ve listed a number of obstacles that may be keeping you and your team from the mission-critical parts of your jobs. Taking note of these distractions can be a first step toward fashioning solutions that lead to better outcomes for you and your organization.Infrastructure firefighting When things don’t go according to plan and you have to trade your strategic IT roadmap for tactical reactionary decisions - that’s infrastructure firefighting. The network may not be working as intended; capacity planning may be off mark; production issues could be causing outages, requiring in-depth explanation and research to mitigate repeat outages in the future. Outages may require special actions, as we discuss in this article. You may not have signed on to extinguish unwanted fires, but like it or not, that has become part of your job.To read this article in full, please click here

Response: The Need For Stretched VLANs (@ioshints)

A recent post from Ivan Pepelnjak entitled Revisited: The Need For Stretched VLANs made me smile rather bitterly as Ivan dug into the apparent continued desire for stretched layer 2 networks and the reasons people give for the solution’s requirement and validity. I love a good bit of snark as much as the next nerd, so as you can imagine, I’m all over that post.

John Herbert, Expressing Extreme Disbelief At The Horror He Is Reading

However, I confess I did wince slightly – in the way one might do when an old wound is poked with a sharp stick – as Ivan made a passing sarcastic reference to Microsoft’s amazing Network Load Balancing technology:

ipspace.net: Revisited: The Need For Stretched VLANs

My mind was thrown back to the heady days of 2009 when I stumbled across another post from Mr Pepelnjak, this time entitled Turn a switch into a hub … the Microsoft Way which bemoaned the unadulterated stupidity of Microsoft’s attempt to use layer 2 network flooding to accomplish clustering. I had discovered the nature of this behavior at a previous client and had my mind blown by the very stupid and non-standards-compliant way in which this had been implemented.

The reason my mind went to that post, however, is because if I recall correctly it’s Continue reading

Some Market Thoughts on the Broadcom SDKLT

Broadcom, to much fanfare, has announced a new open source API that can be used to program and manage their Tomahawk set of chips. As a general refresher, the Tomahawk chip series is the small buffer, moderate forwarding table size hardware network switching platform on which a wide array of 1RU (and some chassis) routers (often called switches, but this is just a bad habit of the networking world) used in large scale data centers. In fact, I cannot think of a single large scale data center operating today that does not somehow involve some version of the Tomahawk chip set.

What does this all mean? While I will probably end up running a number of posts on SDKLT over time, I want to start with just some general observations about the meaning of this move on the part of Broadcom for the overall network engineering world.

This is a strong validation of a bifurcation in the market between disaggregation and hyperconvergence in the networking world. Back when the CCDE was designed and developed, there was a strong sense among the folks working on the certification that design and operations were splitting. This trend is still ongoing, probably ultimately resulting Continue reading

IDG Contributor Network: Mean time to innocence – using AI to uncover the truth behind perceived WiFi issues

Mean Time to Repair (MTTR) is a common term in IT that represents the average time required to repair a failed component or device. In networking, MTTR is often longer than desired because there are many interdependencies, whereby an issue in one part of the network may cause a problem much farther downstream. Furthermore, a configuration change might appear to create a new issue, when in fact it just exposed something that was there all along but hidden. It takes quite a bit of forensics to get to the root cause of a network problem. In the meantime (pun intended), there is plenty of blame to go around. The Wi-Fi network seems to be at the top of the list when the accusations fly – more so than any other section of the network. Why is that?To read this article in full, please click here

IDG Contributor Network: Mean time to innocence – using AI to uncover the truth behind perceived WiFi issues

Mean Time to Repair (MTTR) is a common term in IT that represents the average time required to repair a failed component or device. In networking, MTTR is often longer than desired because there are many interdependencies, whereby an issue in one part of the network may cause a problem much farther downstream. Furthermore, a configuration change might appear to create a new issue, when in fact it just exposed something that was there all along but hidden. It takes quite a bit of forensics to get to the root cause of a network problem. In the meantime (pun intended), there is plenty of blame to go around. The Wi-Fi network seems to be at the top of the list when the accusations fly – more so than any other section of the network. Why is that?To read this article in full, please click here

1 … 1,508 1,509 1,510 1,511 1,512 … 3,477