<?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>Central Cli on SneakU</title><link>https://sneaku.com/tags/central-cli/</link><description>Recent content in Central Cli on SneakU</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 17 Sep 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://sneaku.com/tags/central-cli/index.xml" rel="self" type="application/rss+xml"/><item><title>Central CLI Update #1 for NSX 6.2.3/6.2.4</title><link>https://sneaku.com/2016/09/17/central-cli-update-%231-for-nsx-6.2.3-6.2.4/</link><pubDate>Sat, 17 Sep 2016 00:00:00 +0000</pubDate><guid>https://sneaku.com/2016/09/17/central-cli-update-%231-for-nsx-6.2.3-6.2.4/</guid><description>&lt;p&gt;Following on from my previous post in regards to getting the &lt;a href="http://www.sneaku.com/2016/09/06/central-cli-api-update-for-nsx-6-2-36-2-4/"&gt;Central CLI API&lt;/a&gt; working after an upgrade to 6.2.3/6.2.4, it seems that a nice little enhancement has been made which should help verifying and troubleshooting DFW data plane issues.&lt;/p&gt;
&lt;p&gt;When looking at DFW filters and you wanted to view the contents of an address set, on the data plane you would issue the following command:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;vsipioctl getaddrsets -f filter-name
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;And it would display the &lt;strong&gt;complete&lt;/strong&gt; list of address sets for the particular filter.&lt;/p&gt;</description></item><item><title>Central CLI API Update for NSX 6.2.3/6.2.4</title><link>https://sneaku.com/2016/09/06/central-cli-api-update-for-nsx-6.2.3-6.2.4/</link><pubDate>Tue, 06 Sep 2016 00:00:00 +0000</pubDate><guid>https://sneaku.com/2016/09/06/central-cli-api-update-for-nsx-6.2.3-6.2.4/</guid><description>&lt;p&gt;When working on a customer site recently I was made aware that their system to use the NSX Central CLI via the API had stopped functioning. The system had stopped working when the upgrade to NSX 6.2.3 happened.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Click &lt;a href="http://www.sneaku.com/2016/02/22/nsx-v-web-central-cli/"&gt;here&lt;/a&gt; for my previous post on how to use the &lt;a href="http://www.sneaku.com/2016/02/22/nsx-v-web-central-cli/"&gt;Central CLI API&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;When submitting the request, they would always get the following response:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;The resource identified by this request is only capable of generating responses with characteristics not acceptable according to the request &amp;#34;accept&amp;#34; headers.
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;It turns out that there was a change made to the API, and an additional header is required to make it work with NSX 6.2.3 &amp;amp; 6.2.4. You now need to add the following to the existing headers:&lt;/p&gt;</description></item></channel></rss>