<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="3.8.7">Jekyll</generator><link href="https://www.advantec.us/feed.xml" rel="self" type="application/atom+xml" /><link href="https://www.advantec.us/" rel="alternate" type="text/html" /><updated>2020-07-20T11:59:56-04:00</updated><id>https://www.advantec.us/feed.xml</id><title type="html">Advantec Global Services, Inc</title><subtitle>Advantec has provided technology solutions to organizations worldwide since 1994. Our experienced and globally recognized team works with our clients to assist with choosing the right technology for their specific business needs and challenges.</subtitle><author><name>agsi_jwilson</name></author><entry><title type="html">Prevent auto-start of VPX VMs</title><link href="https://www.advantec.us/blog/adc/2020/06/13/citrix-adc-sdx-prevent-auto-start/" rel="alternate" type="text/html" title="Prevent auto-start of VPX VMs" /><published>2020-06-13T00:00:00-04:00</published><updated>2020-06-13T00:00:00-04:00</updated><id>https://www.advantec.us/blog/adc/2020/06/13/citrix-adc-sdx-prevent-auto-start</id><content type="html" xml:base="https://www.advantec.us/blog/adc/2020/06/13/citrix-adc-sdx-prevent-auto-start/">&lt;p&gt;By default all VPX instances hosted on the SDX platform are configured to auto start. During a SDX migration project it was useful to prevent this behavior in the event that the SDX platform rebooted. The primary reason for this was because I used the same IP addresses on the new instances that the old instances had and did not want to cause an IP conflict by ARPing over the new instance if the SDX platform rebooted.&lt;/p&gt;

&lt;h3 id=&quot;process&quot;&gt;Process&lt;/h3&gt;

&lt;ol&gt;
  &lt;li&gt;
    &lt;p&gt;SSH to the underlying XenServer host on your SDX appliance&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Discover the VM UUIDs by executing the following command&lt;/p&gt;

    &lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt; xe vm-list
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;    &lt;/div&gt;

    &lt;p&gt;&lt;em&gt;Note: this command will list all of the VMs on the appliance&lt;/em&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Copy the UUID string from the VM you want to prevent from auto-starting&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Execute the following command to set auto_poweron to false for that VM&lt;/p&gt;

    &lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt; xe vm-param-set &lt;span class=&quot;nv&quot;&gt;uuid&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;yourUUID other-config:auto_poweron&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;&lt;span class=&quot;nb&quot;&gt;false&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;    &lt;/div&gt;

    &lt;p&gt;&lt;em&gt;Note: yourUUID will be populated with the UUID you copied in step 3&lt;/em&gt;&lt;/p&gt;
  &lt;/li&gt;
  &lt;li&gt;
    &lt;p&gt;Verify the parameter was modified by executing&lt;/p&gt;

    &lt;div class=&quot;language-bash highlighter-rouge&quot;&gt;&lt;div class=&quot;highlight&quot;&gt;&lt;pre class=&quot;highlight&quot;&gt;&lt;code&gt; xe vm-list &lt;span class=&quot;nv&quot;&gt;uuid&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;yourUUID &lt;span class=&quot;nv&quot;&gt;params&lt;/span&gt;&lt;span class=&quot;o&quot;&gt;=&lt;/span&gt;other-config
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;    &lt;/div&gt;
  &lt;/li&gt;
&lt;/ol&gt;

&lt;h3 id=&quot;end-result&quot;&gt;End result&lt;/h3&gt;

&lt;p&gt;The selected VPX instance defined by UUID will no longer auto-start if the SDX platform is rebooted.&lt;/p&gt;</content><author><name>agsi_jwilson</name></author><summary type="html">By default all VPX instances hosted on the SDX platform are configured to auto start. During a SDX migration project it was useful to prevent this behavior in the event that the SDX platform rebooted. The primary reason for this was because I used the same IP addresses on the new instances that the old instances had and did not want to cause an IP conflict by ARPing over the new instance if the SDX platform rebooted.</summary><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="https://www.advantec.us/assets/img/twitterCard.png" /><media:content medium="image" url="https://www.advantec.us/assets/img/twitterCard.png" xmlns:media="http://search.yahoo.com/mrss/" /></entry></feed>