Month: November 2016

Pure Processor Power!

My wife let me build a new desktop as my Christmas present this year. My intent was to build a sweet rig for things like GNS3, Plex, Handbrake and some A/V editing by dropping a hot CPU, high memory capacity, RAIDing a few NAS HDDs together for storage and mirroring 2 smaller economy SSDs for OS and critical programs. Tie them all together with a strong, but economical, motherboard and I could build a pretty sweet rig for under $800, right? Well, this isn’t Linus Tech Tips so I didn’t get to push together everything at once, but I think I did alright.

The Build

So, notes on the build. I budgeted $100 on the motherboard then I chose based on 3 filters:

  1. Integrated USB 3.1 on type A so I can do things like quickly transfer files on a 3.1 thumb drive, stand up good quality heavier Linux and Windows VMs in VmWare Player, or rapidly charge my phone.
  2. DDR3 dual channel. I love the speeds of DDR4, but I don’t need them. I can max this motherboard (64GB) for much cheaper than I could if I picked a DDR4 board. I need memory so I can have Wireshark, GNS3, and a browser all pumping at the same time. This meets that mark without breaking the wallet.
  3. AM3+ socket. I didn’t want to go on-board for graphics and I definitely didn’t want Intel prices. The AMD FX-8370 was perfect and I caught it when the difference between the chip alone vs with the Wraith Cooler was only three dollars.

The Gigabyte 970-Gaming-SLI fit my needs, was 35 bucks under budget, has M.2, plus it’s lightly ruggedized. Other quick notes: the SSD was a cheap solution to get fast boot (less than a sip of coffee on the Windows 10 logo); the vid card was just a cheap video output, but actually plays New Vegas at around 40FPS on high, not bad for the price; PSU was cheap and has enough spare potential to keep the fan quiet even at the max the PC can draw; ADATA RAM, because cheap and effective; Corsair AF series fans are super quiet and look great; HGST Deskstar NAS 3TB because cheap for the high MTTF and raiding in the additions won’t hurt my feelings/wallet; Enermax Ostrog case, cheap and looks nice (though not the best cable management, my CPU bundle sticks out like a sore thumb). I also had 3 160GB WD Blues Sata III 5400 in the drawer, so I striped them together for kicks.

Results

I’m impressed. For less than $600 I’m getting this result out of handbrake.

capture

Wow. I was doing this before on a Dell I15 ultrabook with the I7 4500-U running Ubuntu 14.04. Now you cannot, in any world, compare the performance of an older ultrabook processor to an 8370. Still, this is cut my encoding time to 1/10 of burden. And sure, there are other factors further boosting that number too, so let’s go to the Prime95 results.

Capture1.PNG

BAM! So, when the test queued the workers, the CPU jumped into Turbo on each core before they settled into throughput-per-core. This capture is thirty minutes into the test and I’m writing this as it continues to run. The Mobo/CPU/Wraith are in perfect harmony. It took about ten minutes to climb to 49C and then the board drew a line in the sand. The Wraith picked up speed, taking the CPU back to a steady 46C and the heat spread through the case for another ten minutes before the two other board fans took more speed, but we’re still at 46.5C. Even better, it’s nearly silent. Fan config is Top/out=2xAF140(molex-to-3pin), Rear/out=1xOstrog120mm; Front/in=unknownspare120mm; bottom/in=2xAF120(molex-to-3pin). I just killed Prime95 and the Wraith took the chip to under 30C in ten seconds and at 20 seconds all temp sensors are at normal 25C (my office is cold). Not bad for AMD.

What’s Next?

I’m not done with this guy. I’m going to swap out the vid card for something in the $200 range eventually for a HTPC setup, add two more of those Adata sticks so I can put a ridiculous number of routers in GNS3 or even open two tabs in Chrome (if you don’t get it, check your RAM usage), pull the 3 WD Blue 160s and raid in 3 more of the 3TB HGST HDDs, add a fan controller and temp probes for for the Corsairs, and add an M.2 stick to put my Steam games on. Speaking of which, I put Skyrim on the 3 striped WD Blues. Skyrim moves between loading screens so quickly that I can’t read the tips. First world problems.

Packet Pushers: A Recap

A couple weeks ago I had the honor of joining the Packet Pushers Podcast for a discussion on networking careers and the more general IT field. First of all, that was Awesome! I’ve been listening to Ethan Banks and Greg Ferro for going on two years and it was a blast to have the ear of these gentlemen when they’ve had mine for so long. Michael Sweikata and Ryan Booth of Moving Ones and Zeroes also joined in the fun. Together, those four engineers have on the order of 70ish years in IT, and I have four years, six if I include tech support. It felt great to have these 4 guys express interest and concern in my opinions. I came prepared with my thoughts and the input of many of my colleagues, who share in common my lack of tenure and wealth of questions about the future. These four packet pros in turn assuaged many fears and reinforced my love of all things IT. On to the Recap!

What’s a young network pro to do?

When I asked these engineers for advice aimed towards someone in my position as he/she considers a networking career Greg summed it up beautifully: “don’t.” He wasn’t being short or fatalist; instead he and the other 3 addressed my fears that networking is dying. In short, yes, it’s dying. Not the career of building the paths on which data travels; data will always need mobility. Instead, the Network is evolving from a sum of a million parts just barely glued together into essentially a giant mainframe, with some exceptions. With Ethernet speeds shaming the rest of the system one would first think “wow, I’ll be able to transfer this file so fast.” but in reality, why would you move the data to a weak host when those time sensitive bits are already sitting in a bare metal beast?  This mentality has driven progress in computing for about the last ten years. Networking, on the other hand, is finally tuning into the speed IT. Most of the networking field is likely to move into either automation. We all wanted a better way to provision a vlan on 200 switches in a moment, right? Well, it’s finally coming. Add in cloud-integrations, server-centric thin-client workstations, and wireless everywhere and there simply are not as many cables being run at businesses.

But like I said, Data still needs to move. Be it in a hypervisor or a controller, networking pros will still have to lay down paths between hosts, instances, and containers. The rise of automation is simplifying that process, but we still have to make all of the interconnections. Are the jobs going to go away? They say, and I say, No. But the amount of time networking pros spend in front of an SSH terminal is going to steadily decrease in exchange for time spent banging out python, tuning your puppet/chef/ansible deployment, or learning the new SDN solution designed to do it all in a distributed manner.

Cisco, certs, and the future of IT learning.

So what does this do to beloved Cisco? Well, they are going to have to get flexible. Cisco has spent many years conforming the industry to itself, but now we have options. Not just Juniper or HPE, but options to make a network from scratch or from the opensource compilations of many other network pros who want to break the vendor bonds.

So if companies are branching out, what does that do to the cert environment? Nothing, as Ethan Banks explained in the podcast. Cisco’s training arm is a profit model which has adapted over the years to the changes in technology. Quite simply, Cisco is likely continue revamping their cert system to reflect the industry while also seeding a Cisco preference into those certified by Cisco.

But obviously Cisco, Juniper, HPE, etc., are not going to write a “OpenStack Associate” certification. The open and whitebox communities instead going to pull a greater variety of skills for network support. Soon, more job listing will include “Python/Java preferred” or “Security Experience” under “CCNA certified.” Computer science and IT sec are re-entering the network and the jobs will follow that trend.

Let there be Gripes!

If you haven’t ready my post about my attempts at ICND2, check them out. I was incredibly relieved to hear Ethan Banks say he would have trouble passing the CCNA. I’m not going to beat that dead horse, as my mind is geared towards passing the revised ICND2 by Valentines day.

There’s a great bit of conversation on the lack of vendor accountability, insight, and integrity and how that’s driving customers away from the traditional vendors. I don’t have the experience to speak on that topic, but the conversation was still fascinating.

That’s it!

This is just a bit of what was pertinent to me, as a lot of the conversation was above my experience and understanding. All in all, this was a great conversation that addressed much of my aspirations and worries. Link below, check it out, and I recommend the Packet Pushers to any IT pros who want a view beyond their own data-center.

http://packetpushers.net/podcast/podcasts/show-311-five-engineers-microphone/

Fixed it!

Fixed the website. Too bad I didn’t get it back up until 3 weeks after the chat with the guys at the Packet Pushers Podcast!

I found the backup file right before I was about to wire a drive and put it in a raid array on my new desktop. Good thing I looked before I lept!