My last 6.0 patch upgrade had an interesting phenomenon. Staging of three of the patches worked without a hitch. Before I could install the next patch, however, I had to cold-reboot the nodes. A soft reboot caused a red message to the console complaining about a module that would not load: a module I did not recognize, and now cannot remember. However, when this happened I did a cold reboot, and everything looks like it worked.
My infrastructure recently underwent a catastrophic failure from which recovery was more tedious than difficult. An iSCSI server running from a KVM server using Open vSwitch decided to go south. Why? I am still trying to figure that out. The long and short of it is that Open vSwitch running within a CentOS 7 KVM has a pretty major performance glitch. I hope to fix that soon. So, what happened?
I have recently been trying to tie my Polycom SoundPoint IP 550 phones to a FortiVoice-VM (FVM) Voice over IP (VoIP) system. This is an attempt to upgrade from our TalkSwitch PSTN to VoIP gateway system. Our goal is to move everything we can into our virtual environment. Currently, our phone system is the last system to migrate into our virtual environment. However, it is just not as easy as expected. Continue reading Upgrading Polycom Soundpoint IP 550 Phones
I recently rebooted my KVM server. When I do this, I often have to run a script to update Open vSwitch by removing unused ports, but this reboot messed up my entire iSCSI bond and vSwitch configuration. It looks like some of the control files for when you reboot the node were broken and needed to be repaired. Now, I am still not sure why these steps are required, but they do fix the problem for me.
To keep vSphere installs secure, it is often necessary to patch or upgrade them in a specific order, as outlined in KB 2109760, which has been our guide for the last few parts of our upgrade saga. However, patching vCenter 6.0 vCSA is not as easy as it looks. The instructions in the online manuals are only apropos for upgrading from vCenter 5.1 or 5.5. For vCenter 6.0, they contain information only valid once you have Update 1 involved. So, how do we proceed? Continue reading vSphere Upgrade Saga: Upgrading to vSphere 6.0 U1
In my Foray into Jenkins, Puppet, Docker, and Photon article, I discussed how to set up Photon, Jenkins, and Docker and how I was able to use Jenkins to deploy a Photon template. However, this template was a simple template with just Docker set up within it: a template that could become anything required, run any Docker container. The next step was to deploy a container within Photon. For this, I chose NGINX. Continue reading Foray into Jenkins, Puppet, Docker, and Photon: Part 2