Archive

Category Archives for "Networking"

J-AUT Course

Hi ,

I have enrolled for Juniper-JAUT Course and looking forward to it.

Below are the details. Its a 5 Day course and am expecting more out of this course.

https://learningportal.juniper.net/juniper/user_activity_info.aspx?id=5186

My main interest lies in YAML / JSON use cases with Juniper Devices and their interaction. I will let you know how the course goes as the day progresses and over all efficiency of the course.

 

-Rakesh

BrandPost: Where Do you Rank? IDC Lists Top Drivers for SD-WAN Adoption

IDC concluded a worldwide survey in September 2017 to learn and report on the key factors driving SD-WAN deployments for enterprises. I’m pleased to see the alignment in the findings with what I wrote in my previous article, SD-WAN Delivers Real Business Outcomes to Cloud-first Enterprises back in September. The results of the survey identified the following top four drivers for deploying an enterprise SD-WAN solution:To read this article in full, please click here

Worth Reading: Debating Exascale Commodity Hardware

Building the first exascale systems continues to be a high-profile endeavor, with efforts underway worldwide in the United States, the European Union, and Asia – notably China and Japan – that focus on competition between regional powers, the technologies that are going into the architectures, and the promises that these supercomputers hold for everything from research and government to business and commerce. —Jeffery Burt @ The Next Platform

Reaction: Science and Engineering

Are you a scientist, or an engineer? This question does not seem to occur to most engineers, but it does seem science has “taken the lead role” in recent history, with engineers being sometimes (or perhaps often) seen as “the folks who figure out how to make use of what scientists are discovering.” There are few fields where this seems closer to the truth than computing. Peter Denning has written an insightful article over at the ACM on this topic; a few reactions are in order.

Denning separates engineers from scientists by saying:

The first concerns the nature of their work. Engineers design and build technologies that serve useful purposes, whereas scientists search for laws explaining phenomena.

While this does seem like a useful starting point, I’m not at all certain the two fields can be cleanly separated in this way. The reality is there is probably a continuum starting from what might be called “meta-engineers,” those who’s primary goal is to implement a technology designed by someone else by mentally reverse engineering what this “someone else” has done, to the deeply focused “pure scientist,” who really does not care about the practical application, but is rather simply searching Continue reading

AMD scores its first big server win with Azure

AMD built it, and now the OEM has come. In this case, its Epyc server processors have scored their first big public win, with Microsoft announcing Azure instances based on AMD’s Epyc server microprocessors.AMD was first to 64-bit x86 design with Athlon on the desktop and Opteron on the servers. Once Microsoft ported Windows Server to 64 bits, the benefit became immediately apparent. Gone was the 4GB memory limit of 32-bit processors, replaced with 16 exabytes of memory, something we won’t live to see in our lifetimes (famous last words, I know).Also on Network World: Micro-modular data centers set to multiply When Microsoft published a white paper in 2005 detailing how it was able to consolidate 250 32-bit MSN Network servers into 25 64-bit servers thanks to the increase in memory, which meant more connections per machine, that started the ball rolling for AMD. And within a few years, Opteron had 20 percent server market share.To read this article in full, please click here

AMD scores its first big server win with Azure

AMD built it, and now the OEM has come. In this case, its Epyc server processors have scored their first big public win, with Microsoft announcing Azure instances based on AMD’s Epyc server microprocessors.AMD was first to 64-bit x86 design with Athlon on the desktop and Opteron on the servers. Once Microsoft ported Windows Server to 64 bits, the benefit became immediately apparent. Gone was the 4GB memory limit of 32-bit processors, replaced with 16 exabytes of memory, something we won’t live to see in our lifetimes (famous last words, I know).Also on Network World: Micro-modular data centers set to multiply When Microsoft published a white paper in 2005 detailing how it was able to consolidate 250 32-bit MSN Network servers into 25 64-bit servers thanks to the increase in memory, which meant more connections per machine, that started the ball rolling for AMD. And within a few years, Opteron had 20 percent server market share.To read this article in full, please click here

History Of Networking – Alistair Woodman – VoIP

In this episode of History of Networking, Alistair Woodman joins us to discuss the beginnings of commercial VoIP including a look at early protocols, CTI and the early days of ATM versus Frame-Relay versus IP.

Alistair Woodman
Guest
Russ White
Host
Donald Sharp
Host
Phil Gervasi
Host
Jordan Martin
Host

Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post History Of Networking – Alistair Woodman – VoIP appeared first on Network Collective.

History Of Networking – Alistair Woodman – VoIP

In this episode of History of Networking, Alistair Woodman joins us to discuss the beginnings of commercial VoIP including a look at early protocols, CTI and the early days of ATM versus Frame-Relay versus IP.

Alistair Woodman
Guest
Russ White
Host
Donald Sharp
Host
Phil Gervasi
Host
Jordan Martin
Host

Outro Music:
Danger Storm Kevin MacLeod (incompetech.com)
Licensed under Creative Commons: By Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0/

The post History Of Networking – Alistair Woodman – VoIP appeared first on Network Collective.

Worth Reading: The Dead DRM Canary

EFF has been fighting against DRM and the laws behind it for a decade and a half, intervening in the US Broadcast Flag, the UN Broadcasting Treaty, the European DVB CPCM standard, the W3C EME standard and many other skirmishes, battles and even wars over the years. With that long history behind us, there are two things we want you to know about DRM… —Cory Doctorow @ Deep LinksEFF has been fighting against DRM and the laws behind it for a decade and a half, intervening in the US Broadcast Flag, the UN Broadcasting Treaty, the European DVB CPCM standard, the W3C EME standard and many other skirmishes, battles and even wars over the years. With that long history behind us, there are two things we want you to know about DRM… —Cory Doctorow @ Deep Links

IDG Contributor Network: Linux then, and why you should learn it now

The booming popularity of Linux happened around the same time as the rise of the web. The server world, once proprietary, eventually fell in love with Linux just the same way networking did. But for years after it began growing in popularity, it remained in the background. It powered some of the largest servers, but couldn’t find success on personal devices. That all changed with Google’s release of Android in 2008, and just like that, Linux found its way not only onto phones but onto other consumer devices.The same shift from proprietary to open is happening in networking. Specialized hardware that came from one of the “big 3” networking vendors isn’t so necessary anymore. What used to require this specialized hardware can now be done (with horsepower to spare) using off-the-shelf hardware, with Intel CPUs, and with the Linux operating system. Linux unifies the stack, and knowing it is useful for both the network and the rest of the rack. With Linux, networking is far more affordable, more scalable, easier to learn, and more adaptable to the needs of the business.To read this article in full, please click here

1 … 1,565 1,566 1,567 1,568 1,569 … 3,477