<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Matthew Erbacher on Medium]]></title>
        <description><![CDATA[Stories by Matthew Erbacher on Medium]]></description>
        <link>https://medium.com/@matthew_38680?source=rss-b016305a98e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nC6s8ufKw1WANXkT.</url>
            <title>Stories by Matthew Erbacher on Medium</title>
            <link>https://medium.com/@matthew_38680?source=rss-b016305a98e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:04:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@matthew_38680/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Getting Virtual Machines Production Ready]]></title>
            <link>https://medium.com/beyond-the-helpdesk/getting-virtual-machines-production-ready-97e8a8ef23f5?source=rss-b016305a98e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/97e8a8ef23f5</guid>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[s2ds]]></category>
            <category><![CDATA[hyper-v]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <category><![CDATA[hyperconverged]]></category>
            <dc:creator><![CDATA[Matthew Erbacher]]></dc:creator>
            <pubDate>Wed, 06 Dec 2017 23:22:42 GMT</pubDate>
            <atom:updated>2017-12-06T23:22:42.764Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oMA-h5sdcZ5FOgHampJ4rA.jpeg" /></figure><h4>How to move Virtual Machines from development to production in two easy steps using Hyper-V</h4><p>We have just implemented a new hyper-converged virtual hosting solution using Storage Spaces Direct and Hyper-V (Click <a href="https://medium.com/beyond-the-helpdesk/setting-up-and-configuring-storage-spaces-direct-in-windows-server-2016-4d2be85a8f7d">here</a> to see how we implemented S2D). Its been a rocky road in migrating and maintaining our Virtual Environment within Storage Spaces Direct, but have overcome most challenges that were present.</p><p>Since moving to Hyper-V on S2D, our production environment has become the wild west for virtual machines. We currently have a team of techs creating virtual machines for a variety of different use cases, which shouldn&#39;t be running in a production enviroment</p><p>Previously with our ESXI implementation (Click <a href="https://medium.com/beyond-the-helpdesk/why-storage-spaces-direct-won-out-over-6-alternatives-7f9c3bcd44b5">here</a> to see why we chose Hyper-V), We could structure virtual machines into Testing, Production and other categories that would enable you to see clearly what purpose it served.</p><p>Now under Failover Cluster Manager, you just get a single list of all Virtual machines running in your cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/0*3LnmAWTgXfScsTlf." /></figure><p>This creates an administrative headache to determine what’s currently being tested and what’s actually a production machine. Especially when you have a team of people constantly moving/changing/deleting VM’s.</p><h4>What we did about it.</h4><p>We’ve decided we need to have a staging Hyper-V host, so our team could run up new virtual machines, make the necessary changes then push to production. Once a production VM is no longer needed, it can also be de-staged back onto the staging server.This will be completely separate from our production environment.</p><h4>The on-boarding process</h4><p>Once a VM has been made production ready, there are two main steps to complete to add to our Highly-Available cluster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/0*9jcU44QcYnCYV5ep." /></figure><p>On our staging Hyper-V host, right click the VM and click Move. This will begin a wizard, We want to <strong>Move the virtual Machine </strong>to one of our production Hyper-V hosts, and we want to <strong>Move the virtual machine’s data to a single location</strong>, that location being the storage spaces direct data store (<strong>C:\ClusterStorage\volume1\Hyper-V</strong>). The data storage location is important as it will effect the second step.</p><p>Once the migration is complete, we want to add this VM to our production Cluster. Connect to the Failover Cluster, right click on Roles &gt; Configure Role then select Virtual Machine, select the Virtual Machine you have just moved then click next and you’re done! Now the VM is running on our HA production environment.</p><h4>The off-boarding process</h4><p>To remove a VM from production and move it back onto the staging Hyper-V host, you first have to remove the VM from the cluster first by right clicking on a VM &gt; Remove. This removes the VM from the cluster, but keeps the VM running locally on the host.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/382/0*gGKG_cUbJVmcVQlk." /></figure><p>Open the Hyper-V manager on the host the VM was last running on in the clustered environment, then follow the exact same steps to on-board the VM, as you are now on boarding the VM to the staging Hyper-V host.</p><p>The above on and off-boarding process is all done while the VM is on and running, with only a brief interruption to the VM as the saved state is migrated from one host to another.</p><p>That’s it! Got a better way to manage Hyper-V hosts? I would love to hear your thoughts.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97e8a8ef23f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/getting-virtual-machines-production-ready-97e8a8ef23f5">Getting Virtual Machines Production Ready</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting up and configuring Storage Spaces Direct in Windows Server 2016]]></title>
            <link>https://medium.com/beyond-the-helpdesk/setting-up-and-configuring-storage-spaces-direct-in-windows-server-2016-4d2be85a8f7d?source=rss-b016305a98e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d2be85a8f7d</guid>
            <category><![CDATA[education]]></category>
            <category><![CDATA[edtech]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[schools]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Matthew Erbacher]]></dc:creator>
            <pubDate>Thu, 11 May 2017 04:15:01 GMT</pubDate>
            <atom:updated>2017-05-11T04:15:01.349Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cczmIHo7gAPOqg55M7-7kg.jpeg" /></figure><p>In our previous article (read it <a href="https://medium.com/beyond-the-helpdesk/why-storage-spaces-direct-won-out-over-6-alternatives-7f9c3bcd44b5">here</a>) we went through multiple ways we could deliver a highly available and cost effective virtualisation and storage solution. We decided on implementing a 4 node Hyper-Converged solution using Storage Spaces Direct in Server 2016.</p><h3>Networking</h3><p>Before we can set up our Storage Spaces Direct Cluster, we need to ensure our network configuration is correct. Our 4 nodes will have to have two networks. One network will only be for host failover in our failover cluster, and the other will only be used to access the hosts and guest virtual machines. We will not be using a switch for our failover network, each host will be directly connected via a 40Gb fibre connection.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*F-LMA4_LiDxNAXRu." /></figure><p>On our failover network, we will be utilizing Remote Direct Memory Access (RDMA) on the Mellanox ConnectX-3 Pro adapters. RDMA is able to directly access the memory to read and write on a remote machine. The advantages of RDMA on our hosts is the ability to directly bypass any CPU involvement and bypassing the TCP/IP network stack, thus increasing performance.</p><p>To verify RDMA is enabled our on failover nics, you can run the following powershell command:</p><blockquote><em>Get-NetAdapterRDMA</em></blockquote><h3>Configuring Storage Spaces Direct</h3><h3>Creating the cluster</h3><p>After installing both the Hyper V role and Failover clustering feature within Server 2016, we can now create our Cluster.</p><p>Before creating the cluster, it’s wise to run the cluster validation tool to ensure the hardware selected and IP addressing schemes are compatible for a clustered environment.</p><p>To run a cluster validation, use the following powershell command:</p><blockquote><em>Test-Cluster –Node &lt;MachineName1, MachineName2, MachineName3, MachineName4&gt; –Include “Storage Spaces Direct”, “Inventory”, “Network”, “System Configuration”</em></blockquote><p>Once the validation tests are successful, we are now ready to create our cluster!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*punMu7Ot_DxJRIdz." /></figure><p>To create a cluster in Server 2016, we will use the following powershell command.</p><blockquote><em>New-Cluster –Name &lt;ClusterName&gt; –Node &lt;MachineName1,MachineName2,MachineName3,MachineName4&gt; –NoStorage</em></blockquote><p>It’s important to include the -NoStorage parameter as we do not want the cluster to automatically add all available disks, we will configure this later.</p><h3>Cluster Witness</h3><p>With 4 nodes in our cluster, we want to be able to withstand the worst case scenario if our machines do go offline. By configuring a cluster witness, we will be able to withstand two nodes being completely offline without any services being impacted.</p><p>The cluster witness will act as a quorum vote in the event the cluster nodes lose connection with each other, and only one set of nodes will be active, thus preventing a split-brain situation.</p><p>For our deployment, we will be using a File share witness which is a separate backup server outside of our clustered environment.</p><p>To set a cluster file share witness, use the following powershell command:</p><blockquote><em>Set-ClusterQuorum -FileShareWitness &lt;File Share Witness Path&gt;</em></blockquote><h3>Preparing disks for Storage Spaces Direct</h3><p>Before we configure Storage Spaces Direct, we need to ensure the disks we are using are free of all partitions, otherwise they will not be included in the Storage Spaces Direct pool. As I have been testing and using these 4 nodes in pre-deployment, they all have stale partition data that needs to be erased. Upon re-installing Server 2016, I used the diskpart tool to clean all existing hard drives to ensure no partition data was left of any of the drives.</p><h3>Enabling Storage Spaces Direct</h3><p>Now that we have our 4 nodes in a cluster, all with empty unpartitioned disks we can configure Storage Spaces Direct. The powershell command we will use to enable Storage Spaces Direct in a Cluster:</p><blockquote><em>Enable-ClusterStorageSpacesDirect</em></blockquote><p>Once we run this command, a few things will happen. The storage system will be put into Storage Spaces Direct mode, then the following will happen:</p><p>One big storage pool will be created with the name “S2D on Cluster1” using all disks available to each host. If your storage array consists of more than one type of drive (SSD, NVMe) it will automatically assign this drive to be a read and write cache.</p><p>Two tiers will also be created, one called Capacity and one called Performance. Storage Spaces Direct will automatically configure each tier with different types of redundancy. Performance will use 3-way mirror and capacity will use Parity.</p><p>I also want to note here, that this command takes while to complete. I was stuck at “Waiting until SBL disks are surfaced” for about 30 minutes.. All the disks will disappear from Disk management/ File and Storage services and once completed be added to a storage pool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7oT8wLgxsTz16crv." /></figure><h3>Creating A Disk</h3><p>Now that we have our storage pool, we will need to create virtual disks on top of the pool.</p><p>There are multiple ways to create a new disk/volume on our storage pool, such as within Failover Cluster Manager and also within File and Storage Services, and of course powershell.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UXim1fuatPShHWSW." /></figure><p>To create a new virtual disk, open up Failover Cluster Manager, navigate to Storage &gt; Pools, right click the newly created pool and select “New Virtual Disk”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2WHO9e1GRdDD6tJK." /></figure><p>After you have selected your storage pool, you can see the two different performance tiers. In our setup, we have a mix of HDD and SDD media types. The capacity tier (parity) is only made up of our HDD’s, and our performance tier (3 way mirror) will utilize the SSD’s. This is a massive over simplification of how it actually works, this article from cdemi.io has a great explanation of how it works, <a href="https://blog.cdemi.io/caching-and-storage-tiering-in-storage-spaces-direct/">https://blog.cdemi.io/caching-and-storage-tiering-in-storage-spaces-direct/</a></p><p>Through the GUI you are forced to select a mix of Performance and Capacity tier for your virtual disk, but I only wanted to create a virtual disk on the performance tier. You can do this in powershell.</p><p>The following powershell command enabled me to create a virtual disk using 3 way mirror resiliency:</p><blockquote><em>New-Volume -FriendlyName “vDisk01” -FileSystem CSVFS_ReFS -StoragePoolFriendlyName S2D* -Size 10TB -ResiliencySettingName Mirror</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B5FxmL0hvqZYeByI." /></figure><p>Once we have created a virtual disk, we want to more it highly available across all the nodes. Navigate to Storage &gt; Disks &gt; Add to Cluster Shared Volumes. This will then create a central storage point across all nodes at C:\ClusterStorage\Volume1.</p><p>And there you have it, you can now start deploying highly available roles (such as Hyper V virtual Machines).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d2be85a8f7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/setting-up-and-configuring-storage-spaces-direct-in-windows-server-2016-4d2be85a8f7d">Setting up and configuring Storage Spaces Direct in Windows Server 2016</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quickly improve your VLAN security with VACL’s]]></title>
            <link>https://medium.com/beyond-the-helpdesk/quickly-improve-your-vlan-security-with-vacls-57e4bdafa6a7?source=rss-b016305a98e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/57e4bdafa6a7</guid>
            <category><![CDATA[switch]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[security]]></category>
            <dc:creator><![CDATA[Matthew Erbacher]]></dc:creator>
            <pubDate>Tue, 28 Feb 2017 22:41:45 GMT</pubDate>
            <atom:updated>2017-02-28T23:00:05.513Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XwOMOQgDaG0bAAZ9wtumnw.png" /></figure><p>VLANS (Virtual Local Area Network) are used to segment traffic on a switched network. This has a range of benefits.</p><ul><li>Added security for devices on different VLANs as they can’t be discovered (using multicast traffic) they can only be accessed directly if the client knows the destination device’s IP address</li><li>Isolated broadcast domains each with their own subnet and addressing scheme</li><li>Control over resources available of particular ports and who connects to them</li></ul><p>The negatives are that for any VLAN that is tagged on a port, users can send traffic from the VLAN that they’re assigned to another VLAN if they know the IP address.</p><p>Our setup is similar to below, where each physical interface is configured to act as a trunk port. VLAN’s are added to each port. In this scenario traffic from one VLAN can cross to another VLAN allowing any device to access another device on a different VLAN.</p><p>Each physical port on the switch is enabled to allow traffic from VLAN 100, 200 and 300 to communicate between VLANS.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/523/0*EdIleI6DKYat-SQU." /></figure><h3>Blocking access between VLAN’s</h3><p>But what if we don’t want one VLAN to access another VLAN? VACLs (Virtual Access Control Lists) are an effective way to control groups. How this is setup and applied is different depending on your switch vendor, however the concept is generally the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/376/0*r5fEVKzIEe_Ez2w0." /></figure><h3>Example configuration</h3><p>For this example, we are using a DLink DGS 6600 Chassis-Based switch. <br>The command “ip access-list <em>NAME</em>” will create a list, then we can enter some rules.</p><p>For this example we have the following:</p><ul><li>We have VLAN 100 (Admin VLAN) with IP range: 192.168.100.0/24</li><li>We have VLAN 200 (Desktop VLAN) with IP range: 192.168.200.0/24</li><li>We have VLAN 300 (Printer VLAN) with IP range: 192.168.300.0/24</li><li>We want to DENY any traffic going from Desktop VLAN (200) to Server VLAN (100), and allow Printer VLAN (300) traffic to access VLAN Admin (100) and Desktop (200).</li><li>We want to apply this rule for any traffic going OUT of the VLAN then INBOUND to the interface.</li></ul><p><em>DGS-6600:2&gt;enable</em></p><p><em>DGS-6600:15#configure terminal</em></p><p><em>DGS-6600:15(config)#ip access-list deny_vlan</em></p><p><em>The maximum available of IP access-list is 255</em></p><p><em>DGS-6600:15(config-ip-acl)#deny 192.168.200.0 255.255.255.0 192.168.100.0 255.255.255.0</em></p><p><em>DGS-6600:15(config-ip-acl)#permit 192.168.300.0 255.255.255.0 192.168.100.0 255.255.255.0</em></p><p><em>DGS-6600:15(config-ip-acl)#permit 192.168.300.0 255.255.255.0 192.168.200.0 255.255.255.0</em></p><p><em>DGS-6600:15(config-ip-acl)#end</em></p><p><em>DGS-6600:15#configure terminal</em></p><p><em>DGS-6600:15(config)#interface eth24</em></p><p><em>DGS-6600:15(config-if)#ip access-group deny_vlan in</em></p><p><em>The maximum available entry of IP ACL bind to interface in ingress direction is:</em></p><p><em>1278</em></p><p><em>The maximum available port operator (gt/lt) is:16</em></p><p><em>DGS-6600:15(config-if)#end</em></p><p>It’s important to note that there is a inferred (hidden) deny all rule at the end of the ip-access list. To allow all traffic, add the commend “permit any any” which permits any source to any destination address.</p><h3>What have we done here?</h3><p>We have denied the source address range 192.168.200.0/24 from accessing the destination address range 192.168.100.0/24. Then, we have permitted 192.168.300.0/24 to access VLAN 100 and 200 IP ranges.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57e4bdafa6a7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beyond-the-helpdesk/quickly-improve-your-vlan-security-with-vacls-57e4bdafa6a7">Quickly improve your VLAN security with VACL’s</a> was originally published in <a href="https://medium.com/beyond-the-helpdesk">Beyond the Helpdesk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>