Wednesday, September 2, 2015

vSphere - Failed to deploy ovf package invalid configuration for device ‘6’

While trying to deploy a test VM from Modern.IE I ran into a pesky little error each time I tried to deploy it using the OVF wizard.

Failed to deploy ovf package invalid configuration for device ‘6’

After searching high and low I found two solutions to this problem.  First, make sure your using thin provisioning (which was greyed out until I implemented the second solution) which I found here.

It involves removing the CD/DVD section of the OVF and saving it.

Thanks to Afterbyrner for the solution.  Check out his blog at

Wednesday, March 30, 2011

Never underestimate the fearlessness of Network Geeks

I certainly wouldn't run my routers that way. It definitely takes some courage to run with that config register....

Thursday, February 3, 2011

It's all gone folks

Mark the history calendars, February 3rd, 2011 marks the day IANA handed out the last of the /8's to the Regional Internet Registers (RIR's). The process that had been selected was that the last 5 /8's would be handed out, one to each region to ensure fairness. It should be noted that APNIC triggered the final distribution with the request and receipt of two /8's and is walking away with a total of three. Even with that distribution, they estimate they only will have 3 to 6 months remaining before exhaustion.

Tuesday, November 16, 2010

What Tracert is really used for...

I can't believe that I've had it wrong for all these years. Special thanks to NextGenHacker101 for setting me straight (although keeping a straight face is taking vast amounts of effort).

Tuesday, October 5, 2010

Oh how things change (My position on IPv6)

Almost exactly 2 years ago I wrote an article where I ranted about how IPv6 is still a long way out from widescale adoption. While I still think that we are at least another 5 years away from a point where IPv6 is the dominant protocol, we have to start getting there now. I have now worked for both Internet Service (ISP) and Managed Service (MSP) Providers and while they both have some things in common, they also both have their own unique challenges. While ISP's obviously need IPv6 to overcome the growing shortage of addresses to be able to assign to end users, MSP's require it to be able to effectively manage customer networks that use overlapping RFC1918 address space with common tools.

My personal opinion is that IPv6 is probably not the best answer that the Networking community could have come up with. I think IPv6 introduces its own set of problems and combats the numbering shortage with a nuclear weapon instead of a fly swatter. I say that because while we may have as many IP Addresses in a single subnet as there are atoms in my body, we will never be able to use them (just like we can't use land mass exposed to nuclear weapons).

With that said, the networking vendors have spoken and IPv6 is going to happen and we need to stop fighting it and adopt it. We have very good transition strategy's available with Dual Stack (DS) for the Enterprise and DS w/LSN or DS Lite for the Service providers so there is no reason not to start thinking about how you are going to get your organization ready. The people who start planning today will be leaps and bounds ahead of those who start in 2012 when IANA runs out of IPv4 addresses (hey, maybe the Mayans had it right after all)

Jeff Doyle has a really good article up about how Carrier Grade NAT (CGN) or Large Scale NAT (LSN) will probably not be as useful as we thought and how we really should just do everything we can to get away from any type of NAT and I whole heartedly agree with him. NAT is an abomination and needs to be a thing of distant memory (like 10BT Half Duplex coaxial networks). And before anyone asks about doing NAT with IPv6, here is my comment from that same article:

I think the biggest problem here is that NAT44 became as prevalent as it did and for the wrong reasons. I think that the idea of security through obscurity was a big reason why NAT is as popular as it is today (which I totally disagree with). I think the proof is in when people who are learning about IPv6 almost always ask about NAT66 because of the security concern of every device being addressable directly from the Internet. The answer is as you point out that NAT is a terrible, terrible thing and we have to get away from it as quickly as possible.

Everyone needs to get on board with IPv6 now, not later.

Everyone chant with me. "NO NAT, NO NAT, NO NAT...."

Monday, June 28, 2010

Cisco Live is ON!

Just sat down for my first session of Cisco Live which is FCoE for the IP Engineer. It's amazing how a few years ago I would have never thought I would need to know anything at all about Storage or Virtualization and now we need to understand it all...