<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Virtual Connet (VC) uplinks reallocation question in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/virtual-connet-vc-uplinks-reallocation-question/m-p/5931467#M31808</link>
    <description>&lt;P&gt;&lt;STRONG&gt;Hoa needed to move some uplink on a VC module:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*****************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need to move VC Ethernet uplinks from X7/X8 to X2/X3 for an ESX4.x environment where firmware/drivers are up to date.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I plan to add X2/X3 first before deleting X7/X8, can this action be done with the servers up and running?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; At the minimum a VCM reset OR server reboot would be great to avoid downtime.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Nick:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;***************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It’s been a while since I’ve done anything like this but I’d try the following process;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Add in the new uplinks&lt;/LI&gt;
&lt;LI&gt;Change the failover from auto to manual specifying the new uplinks as active and the old as standby&lt;/LI&gt;
&lt;LI&gt;Test connectivity&lt;/LI&gt;
&lt;LI&gt;Remove X7/X8&lt;/LI&gt;
&lt;LI&gt;Set failover back to auto&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can’t see any reason why you’d have to reboot the modules or take any servers down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, I would do it out of hours.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Hoa replied with his actual experiences:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;***************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We added X2 &amp;amp; &amp;nbsp;X3 10G uplinks to VC Flex-10 Bay 1 &amp;amp; 2, removing X7s 10G uplinks from Bay 1 &amp;amp; 2 in Active/Standby configuration.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Leave uplinks in Auto vs. Failover mode, let VC to handle LACP as Cisco admin made the changes.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; No impact to live production environment in Tokyo.&amp;nbsp;&amp;nbsp;&amp;nbsp; I appreciate all your advice.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Comments?&lt;/STRONG&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 14 Jan 2013 22:16:08 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2013-01-14T22:16:08Z</dc:date>
    <item>
      <title>Virtual Connet (VC) uplinks reallocation question</title>
      <link>https://community.hpe.com/t5/bladesystem-general/virtual-connet-vc-uplinks-reallocation-question/m-p/5931467#M31808</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Hoa needed to move some uplink on a VC module:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;*****************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I need to move VC Ethernet uplinks from X7/X8 to X2/X3 for an ESX4.x environment where firmware/drivers are up to date.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; I plan to add X2/X3 first before deleting X7/X8, can this action be done with the servers up and running?&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; At the minimum a VCM reset OR server reboot would be great to avoid downtime.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Input from Nick:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;***************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It’s been a while since I’ve done anything like this but I’d try the following process;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;UL&gt;
&lt;LI&gt;Add in the new uplinks&lt;/LI&gt;
&lt;LI&gt;Change the failover from auto to manual specifying the new uplinks as active and the old as standby&lt;/LI&gt;
&lt;LI&gt;Test connectivity&lt;/LI&gt;
&lt;LI&gt;Remove X7/X8&lt;/LI&gt;
&lt;LI&gt;Set failover back to auto&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I can’t see any reason why you’d have to reboot the modules or take any servers down.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;That said, I would do it out of hours.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Hoa replied with his actual experiences:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;***************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We added X2 &amp;amp; &amp;nbsp;X3 10G uplinks to VC Flex-10 Bay 1 &amp;amp; 2, removing X7s 10G uplinks from Bay 1 &amp;amp; 2 in Active/Standby configuration.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;Leave uplinks in Auto vs. Failover mode, let VC to handle LACP as Cisco admin made the changes.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; No impact to live production environment in Tokyo.&amp;nbsp;&amp;nbsp;&amp;nbsp; I appreciate all your advice.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;**************&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Comments?&lt;/STRONG&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2013 22:16:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/virtual-connet-vc-uplinks-reallocation-question/m-p/5931467#M31808</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2013-01-14T22:16:08Z</dc:date>
    </item>
  </channel>
</rss>

