One of my last tasks for 2014 was integrating a new Nimble Storage array into our environment. As this is the first of these I’ve encountered and I haven’t been able to take the free one day Nimble Installation and Operation Professional (NIOP) course they provide I was left to feeling my way through it with great help from their documentation and only ended up calling support to resolve a bug related to upgrading from 2.14 of the Nimble OS. On the network side our datacenter is powered by Cisco Nexus 3000 series switches, also a new addition for us recently. These allowed us to use our existing Cat6 copper infrastructure while increasing our bandwidth to 10 GbE. In this post I’m going to document some of the setup required to meet the best practices outlined in Nimble’s Networking Best Practices Guide when setting up your system with redundant NX-OS switches. Continue reading Configuring Networking for Nimble-vSphere iSCSI
Let me start by saying I feel very dirty for even writing this. My basic rule in life is if the file is bigger than 2 MB, it isn’t to be sent as an attachment to an e-mail. That said, many do not share my opinion on that and here at the office we recently had an occasion where a 200 MB file absolutely had to be e-mailed, it could be sent no other way. A couple of years ago I wrote a post on 4sysops about how to change this in Exchange, so I thought that was an easy fix. Instead the user continued to see this:
After some Googling I found a forum post saying that not only was a hard limit of 50 MB a feature of Outlook 2010 and above, but that this feature had been added to Outlook 2007 with Service Pack 2. The good news/ bad news is that this feature can be over ridden by registry hack. Below is the code that you can copy into a .reg file and execute to insert the required registry key. Know that this is version specific the “12.0” portion below corresponds to Office 2007, you will need to be changed based on your version of Microsoft Office. For reference 2010 will be 14.0 and 2013 is 15.0.
[reghack]Windows Registry Editor Version 5.00
I’ll be the first to admit that I know far less about Linux than is necessary to be good at it and more than necessary to be dangerous at it. That said, if nothing else, I do try to learn more about it. I find that in general I’ve basically committed to CentOS as my flavor of choice with it being the underpinnings of every non-appliance installation I’ve got. Alot of this has to do with the fact that my first experiences were with RedHat and the subsequent RHEL, so with CentOS being the server side, open source derivative of RHEL it makes sense that that’s where I’d go. In the vSphere world as you get further down the rabbit hold of monitor systems for your infrastructure you’ll find that for most things to even begin to operate effectively you’ve got to have VMware tools installed. While there are various instruction sets out there floating around for how to get these on both, through the “Install VMware Tools” GUI and via yum (the RHEL package installation system) I’ve found that your mileage may vary greatly.
Below is a list of commands that I’ve finally got happy with to get these installed and allow for complete control over the VM much like you do with your Windows VMs via the VI client. With the exception of a couple of modifications regarding your revisions of vSphere and CentOS you can pretty much copy and paste this into your elevated prompt (root) on your linux box and get all the information and monitoring you need.
1. Add the VMware GPG keys
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-DSA-KEY.pub
rpm --import http://packages.vmware.com/tools/keys/VMWARE-PACKAGING-GPG-RSA-KEY.pub
2. Copy the following to create a yum repository with all of the relevant information. You will need to change the ESXi version (red) and CentOS base (blue) to match what you run:
echo "[vmware-tools]" >> /etc/yum.repos.d/vmware-tools.repo
echo "name=VMware Tools" >> /etc/yum.repos.d/vmware-tools.repo
echo "baseurl=http://packages.vmware.com/tools/esx/5.0/rhel6/$basearch" >> /etc/yum.repos.d/vmware-tools.repo
echo "enabled=1" >> /etc/yum.repos.d/vmware-tools.repo
echo "gpgcheck=1" >> /etc/yum.repos.d/vmware-tools.repo
3. Install all portions of the VMware Tools:
yum -y install vmware-tools*
And that’s pretty much it. Once done you’ll probably immediately notice that it shows as you are running a 3rd Party version of the tools, but now you’ll see the IP address of the box in the VM summary screen. Further you’ll now be able to monitor heartbeat and view performance data for your VMs, which is very nice to have. In my environment I immediately began getting issue notifications via Veeam ONE letting me know about issues I didn’t even know I had.
A lot of the other guides on how to do this have you use the command
yum install vmware-tools-core, but I find that to be pretty incomplete as there are various plugins that allow for greater management and utilities such as auto update abilities. You can see a whole list of what’s possible and cherry pick if you like by running the command
yum search vmware-tools* once you’ve added your repository (step 2).