<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lab on Matt Allford</title><link>https://www.mattallford.com/tags/lab/</link><description>Recent content in Lab on Matt Allford</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 18 May 2018 10:26:59 +0000</lastBuildDate><atom:link href="https://www.mattallford.com/tags/lab/index.xml" rel="self" type="application/rss+xml"/><item><title>Redeploying NSX Edges To a New Cluster After Manager Restoration</title><link>https://www.mattallford.com/redeploying-nsx-edges-to-a-new-cluster-after-manager-restoration/</link><pubDate>Fri, 18 May 2018 10:26:59 +0000</pubDate><guid>https://www.mattallford.com/redeploying-nsx-edges-to-a-new-cluster-after-manager-restoration/</guid><description>&lt;p&gt;That title is a bit of a mouthful, but it&amp;rsquo;s Friday night and that&amp;rsquo;s the best I&amp;rsquo;ve got!&lt;/p&gt;
&lt;p&gt;I was recently working through some recovery scenarios for NSX in the lab, as I was interested to understand what the process was for various scenarios such as:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Losing NSX Manager and restoring&lt;/li&gt;
&lt;li&gt;Losing NSX Manager, DLR and ESG&amp;rsquo;s and restoring&lt;/li&gt;
&lt;li&gt;Losing the entire cluster (including ESXi hosts) and restoring NSX manager in to a new cluster&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The third scenario is reasonably obscure, and I&amp;rsquo;m not sure if you would follow a different restore process than what I did if this did actually happen. But this is what labs are for, right?&lt;/p&gt;</description></item><item><title>PowerCLI Script to Power On or Off vSphere Lab</title><link>https://www.mattallford.com/powercli-script-to-power-on-or-off-vsphere-lab/</link><pubDate>Fri, 09 Jun 2017 10:37:22 +0000</pubDate><guid>https://www.mattallford.com/powercli-script-to-power-on-or-off-vsphere-lab/</guid><description>&lt;p&gt;I was recently chatting to a few guys regarding powering on and off VMs within a vSphere lab and using a script to do so in some sort of controlled manner (or force power off everything if desired). A few of us had a quick search, and couldn&amp;rsquo;t see anything that met the requirements of being able to power on and power off the lab, as well as place VMs into some sort of priority group.&lt;/p&gt;</description></item><item><title>Additions To vGhetto Automated vSphere Lab Deployment</title><link>https://www.mattallford.com/additions-to-vghetto-automated-vsphere-lab-deployment/</link><pubDate>Fri, 07 Apr 2017 12:04:57 +0000</pubDate><guid>https://www.mattallford.com/additions-to-vghetto-automated-vsphere-lab-deployment/</guid><description>&lt;p&gt;So last week I received a new lab server that is going to be housed at home. It is a Dell T430 with 128GB ram, which is exactly what I was after as I want to get right back into the lab work, but I didn&amp;rsquo;t want a heap of gear and network requirements. NestedESXi has worked reasonably well in the past few vSphere releases and there&amp;rsquo;s not much that can&amp;rsquo;t be simulated within a nested environment for the purposes of learning or testing.&lt;/p&gt;</description></item></channel></rss>