<?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>Powercli on SneakU</title><link>https://sneaku.com/tags/powercli/</link><description>Recent content in Powercli on SneakU</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://sneaku.com/tags/powercli/index.xml" rel="self" type="application/rss+xml"/><item><title>Working with NSX-T 3.0 and VDS 7.0 - Duplicate Port Group Names</title><link>https://sneaku.com/2020/04/15/working-with-nsx-t-3.0-and-vds-7.0-duplicate-port-group-names/</link><pubDate>Wed, 15 Apr 2020 00:00:00 +0000</pubDate><guid>https://sneaku.com/2020/04/15/working-with-nsx-t-3.0-and-vds-7.0-duplicate-port-group-names/</guid><description>&lt;p&gt;When working with a colleague recently on an NSX-T 3.0 environment that utilises VDS 7.0 rather than N-VDS, we came across something which initially stumped me.&lt;/p&gt;
&lt;p&gt;If you were to try and create 2 Distributed Port Groups with the same name on the same vCenter&lt;/p&gt;
&lt;p&gt;&lt;img loading="lazy" src="https://sneaku.com/2020/04/15/working-with-nsx-t-3.0-and-vds-7.0-duplicate-port-group-names/images/image-7.png"&gt;&lt;/p&gt;
&lt;p&gt;the following error is displayed, which is expected.&lt;/p&gt;
&lt;p&gt;&lt;img loading="lazy" src="https://sneaku.com/2020/04/15/working-with-nsx-t-3.0-and-vds-7.0-duplicate-port-group-names/images/image.png"&gt;&lt;/p&gt;
&lt;p&gt;So what would happen if we created a NSX-T Segment with the same name as one already created through vCenter?&lt;/p&gt;</description></item></channel></rss>