<?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>Vra on SneakU</title><link>https://sneaku.com/categories/vra/</link><description>Recent content in Vra on SneakU</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 07 Sep 2015 00:00:00 +0000</lastBuildDate><atom:link href="https://sneaku.com/categories/vra/index.xml" rel="self" type="application/rss+xml"/><item><title>NSX-v Security Policy Applied To Considerations</title><link>https://sneaku.com/2015/09/07/nsx-v-security-policy-applied-to-considerations/</link><pubDate>Mon, 07 Sep 2015 00:00:00 +0000</pubDate><guid>https://sneaku.com/2015/09/07/nsx-v-security-policy-applied-to-considerations/</guid><description>&lt;p&gt;When working with the Service Composer in NSX-v, by default, when a firewall rule is created in a Security Policy, the firewall rule, when applied, uses the default &lt;strong&gt;Applied To&lt;/strong&gt; value of &lt;strong&gt;Distributed Firewall&lt;/strong&gt;. This means that even though the firewall rule is part of a security policy which is then applied to a specific security group, the rule would be pushed down to every vNIC within the clusters that have been prepared for NSX DFW capabilities and have the firewall enabled.&lt;/p&gt;</description></item><item><title>vRA: Network and Security Inventory Data Collection Errors</title><link>https://sneaku.com/2015/03/26/vra-network-and-security-inventory-data-collection-errors/</link><pubDate>Thu, 26 Mar 2015 00:00:00 +0000</pubDate><guid>https://sneaku.com/2015/03/26/vra-network-and-security-inventory-data-collection-errors/</guid><description>&lt;p&gt;Whilst working on a vCloud Automation Center integration with NSX-v this evening, I noticed a strange error which had appeared in the logs in regards to the data collection for Network and Security Inventory.&lt;/p&gt;
&lt;p&gt;The Network and Security Inventory data collection was displaying the time the data collection last completed, which looked fine to me, as it was inline with what I was expecting, but the status was showing as Failed.&lt;/p&gt;</description></item></channel></rss>