<?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>Vcns on The IT Hollow</title>
    <link>https://theithollow.com/tags/vcns/</link>
    <description>Recent content in Vcns on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 30 Nov 2015 15:08:27 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/vcns/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>vRealize Automation 6 with NSX – Firewall</title>
      <link>https://theithollow.com/2015/11/30/vrealize-automation-6-with-nsx-firewall/</link>
      <pubDate>Mon, 30 Nov 2015 15:08:27 +0000</pubDate>
      <guid>https://theithollow.com/2015/11/30/vrealize-automation-6-with-nsx-firewall/</guid>
      <description>&lt;p&gt;So far we&amp;rsquo;ve talked a lot about using our automation solution to automate network deployments with NSX. But one of the best features about NSX is how we can firewall everything! Lucky for us, we can automate the deployment of specific firewall rules for each of our blueprints as well as deploying brand new networks for them.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Use Case:&lt;/strong&gt; There are plenty of reasons to firewall your applications. It could be for compliance purposes or just a good practice to limit what traffic can access your apps.&lt;/p&gt;</description>
    </item>
    <item>
      <title>vCNS Edge SSL VPN</title>
      <link>https://theithollow.com/2014/05/13/vcns-edge-ssl-vpn/</link>
      <pubDate>Tue, 13 May 2014 14:00:14 +0000</pubDate>
      <guid>https://theithollow.com/2014/05/13/vcns-edge-ssl-vpn/</guid>
      <description>&lt;p&gt;A secured, remote connection to your data is a requirement for almost all network designs these days.  Mobility, telecommuting and late night help desk calls have created an environment that needs to have access to the local network in a secure fashion.  vCNS Edge can provide these services to your virtual infrastructure.&lt;/p&gt;
&lt;p&gt;In previous posts, I’ve walked through &lt;a href=&#34;https://theithollow.com/2014/03/getting-started-vcns/&#34;&gt;installing vCNS Manager&lt;/a&gt; and &lt;a href=&#34;http://wp.me/p32uaN-Tb&#34;&gt;installing vCNS Edge appliances&lt;/a&gt;.  These are prerequisites to setting up SSL VPN on the VMware vCloud Network and Security appliance..&lt;/p&gt;</description>
    </item>
    <item>
      <title>vCNS Edge Network Address Translation</title>
      <link>https://theithollow.com/2014/04/15/vcns-edge-network-address-translation/</link>
      <pubDate>Tue, 15 Apr 2014 14:43:12 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/15/vcns-edge-network-address-translation/</guid>
      <description>&lt;p&gt;VMware vCloud Networking and Security (vCNS) can provide Network Address Translation (NAT) services from the vCNS Edge appliance.&lt;/p&gt;
&lt;p&gt;There are two types of NAT that the edge appliance can provide.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;Destination NAT (DNAT) is used to provide access to a private IP Address from a (usually) public IP Address for incoming traffic.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Source NAT (SNAT) is used to translate a private IP Address into a (usually) public IP Address for outgoing traffic. This type of NAT can also be called &amp;ldquo;masquerading&amp;rdquo;.  (It&amp;rsquo;s a subtle difference that we won&amp;rsquo;t go into in this post.)&lt;/p&gt;</description>
    </item>
    <item>
      <title>vCNS Edge DHCP</title>
      <link>https://theithollow.com/2014/04/10/vcns-edge-dhcp/</link>
      <pubDate>Thu, 10 Apr 2014 13:38:41 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/10/vcns-edge-dhcp/</guid>
      <description>&lt;p&gt;One of the most basic tasks that happens on a network is assigning IP Addresses.  Once a VMware vCNS Edge appliance has been deployed, you can now hand out IP address through Dynamic Host Control Protocol (DHCP).&lt;/p&gt;
&lt;p&gt;In previous posts, I&amp;rsquo;ve walked through &lt;a href=&#34;https://theithollow.com/2014/03/getting-started-vcns/&#34;&gt;installing vCNS Manager&lt;/a&gt; and &lt;a href=&#34;http://wp.me/p32uaN-Tb&#34;&gt;installing vCNS Edge appliances&lt;/a&gt;.  These are prerequisites to setting up DHCP on the VMware vCloud Network and Security appliance.&lt;/p&gt;
&lt;h1 id=&#34;vcns-edge-dhcp-setup&#34;&gt;&lt;strong&gt;vCNS Edge DHCP Setup&lt;/strong&gt;&lt;/h1&gt;
&lt;p&gt;Log into your vShield Manager and click on the Datacenter.  Click the &amp;ldquo;Network Virtualization&amp;rdquo; Tab where you&amp;rsquo;ll find the Edge appliance you&amp;rsquo;ve already deployed.  Go to Actions and click &amp;ldquo;Manage&amp;rdquo;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Deploy vCNS Edge</title>
      <link>https://theithollow.com/2014/04/07/deploy-vcns-edge/</link>
      <pubDate>Mon, 07 Apr 2014 13:32:07 +0000</pubDate>
      <guid>https://theithollow.com/2014/04/07/deploy-vcns-edge/</guid>
      <description>&lt;p&gt;vCloud Networking and Security has the capabilities to provide edge services inside of your virtual environment.  Edge firewalls, network address translation, DHCP, routing are all things that vCNS Edge can do for you.  This post goes into the steps necessary to deploy vCNS Edge.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I should mention that vCNS and the previous name vShield may be used interchangeably in this article.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h1 id=&#34;logical-diagram&#34;&gt;Logical Diagram&lt;/h1&gt;
&lt;p&gt;The picture below is a diagram of what our environment will look like when we&amp;rsquo;re done.  We have production VMs as you might expect, and our new vCNS Edge VM.  We&amp;rsquo;ve also got our new Edge network and a Shielded VM which will not be connected to the production vSwitch directly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
