I was fortunate to do my first EMC Unity install today (Unity 300 specifically), and Unity follows the path of the VNXe installation sequence, pretty easy. This blog post is about as short as the Unity install is 🙂
What a week we’ve had, and really I mean Yesterday!
Finally home after a 3rd straight week in NY doing some fun installs for one of our partners. Being home in SC in the summer always feels good. Like being in an oven good.
Then, Microsoft blows our minds with the release of Powershell for MacOS and Linux. I couldn’t download it fast enough!
On to Friday news…
Onto the Logical Router….
In Part 1 of my Deploying NSX series, we covered the prep of NSX in the environment, including deploying the NSX Manager appliance, deploying NSX Controllers and vSphere host preparation. In Part 2 this part of the series, we covered the creation of Logical Switches and our NSX Edge, which consist of our Edge Services Gateway (Providing DHCP, Firewall, VPN, NAT, Routing and Load Balancing capabilities). In our 3rd part in the series, we’ll cover the deployment of the Logical Router, which provides our routing and bridging for the existing networks, as well as configuring routing to get traffic into and out of our new NSX environment.
It’s been over 6 months since I last had NSX working in my home lab, and with a rebuild I decided it was time to wrap up Part 2 of my NSX in a home lab blog post.
In Part 1 of my Deploying NSX series, we covered the prep of NSX in the environment, including deploying the NSX Manager appliance, deploying NSX Controllers and vSphere host preparation. In this part of the series, we’ll cover the creation of Logical Switches and our NSX Edge, which consist of our Edge Services Gateway (Providing DHCP, Firewall, VPN, NAT, Routing and Load Balancing capabilities). Part 3 will cover the deployment of the Logical Router, which provides our routing and bridging for the existing networks, as well as configuring routing to get traffic into and out of our new NSX environment.
So let’s dive right in…
It’s been well over a month since the last post, and while I’ve had many ideas on topics since the last one, nothing has come to fruition!
I wrapped up a busy 2015, with hopes to knock out a few posts during the Christmas break, then the New Year break, and now we’re over halfway thru January and my whiteboard hasn’t changed. I’ve still got my plans for wrapping up my NSX post, especially since I’ve rebuilt my lab for the umpteenth time!
Coming into 2016, I’ve been presented with an awesome opportunity to take over a new role, a challenge, as the Practice Manager for the @eGroup_Inc Data Center Architecture team. It’s a great team, agile, and full of knowledge – and fun.
I’m a big an of the Cisco Fabric Extenders when it comes to getting more ports in a data center topology, I like the easy of management and simple layout for getting connections onto the FEX. However, after speaking with a few coworkers and friends, I came to the conclusion that the supported FEX topologies are still somewhat confusing between the Nexus line, and what is actually supported from a connectivity standpoint on the FEX’s.
I’ve been trying to get the Horizon View EUC Access Point deployed in my home lab for a while now. No matter how I did it, I could just not get the Access Point to work correctly.
I love the idea of the Access Point, being a simple ‘if it breaks, redeploy it’ method, but it really was making me wonder just how ready this was. Turned out, it was all on me…
I’ve been using ManageEngine’s OpUtils product for a few years now for IP Address Management (IPAM). While it has a lot of other great features, I’ve really liked the way they do IPAM. Yes, Microsoft has IPAM now built into Windows, but I’ve never liked the setup of the Windows IPAM configuration, and the lack of a good Web UI for IPAM made me like it even less.
I’m always having to look up power connectors when quoting equipment or reviewing with a customer, to make sure that PDU’s have the appropriate receptacles. I always feel like the information provided by equipment providers doesn’t match up with what’s on the PDU or what the customer states they have.
Got this email today, and it makes me very very sad to see this product go. I’ve been a huge fan of Mint for many years now, and being a Mac user, have loved the Mint Quick View in my Menu bar.
We are writing to inform you that we will be discontinuing support and development for QuickView, the Mint Mac OS desktop app.
We’ve promised to hold ourselves to the highest standard of quality in our products, and strongly believe that shifting our efforts to the Mint Web, iOS and Android applications will help us deliver above and beyond that promise. There’s so much about QuickView that we love – and it’s hard for us to say goodbye to it – but we are confident that this change will help you get even more out of Mint.”
I hate to see a good product go, especially one that was useful. Sure, I can open my browser and see Mint, or get it on my phone, but having Quick View in the menu bar, was great.
Sigh, goodbye Quick View… You’ve been a mainstay in my Mac’s Menu bar for many many years.