<?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 Auto NIC failover scripts for Windows &amp;amp; Linux? in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/auto-nic-failover-scripts-for-windows-amp-linux/m-p/5564157#M32150</link>
    <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Stan was looking for a NIC failover test script:&lt;/STRONG&gt;&lt;/FONT&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;Looking for a simple solution for a large financial company…&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They have many C7000 enclosures, win2kX, and linux with teamed NICs, dual paths, redundant switches, &amp;nbsp;etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are asking if we have a script or (semi)automated method, to cause a failover on the NICs, ( Network A -&amp;gt; Network B) to validate, test in-frequently, to verify that all failover networks are working correctly?&amp;nbsp; This would include doing the failover and verifing network conectivity on Network B, for example….&lt;/P&gt;&lt;P&gt;An automated or manually kicked off script would be the ideal, vs manual intervention on the various servers….&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wondering if someone has tackled this?&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;FONT color="#000000"&gt;&lt;STRONG&gt;From Chris:&lt;/STRONG&gt;&lt;/FONT&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 don’t have a script, nor had anyone request this.&amp;nbsp; However, just thinking off the top of my head, you can use NETSH in Windows to disable a specific connection, and &lt;EM&gt;ifconfig down eth#&lt;/EM&gt; (or &lt;EM&gt;if-down&lt;/EM&gt; if the distro is Red Hat based) in Linux.&amp;nbsp; I wouldn’t suggest a customer do this during production hours, but rather during maintenance windows (if possible.)&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;FONT color="#000000"&gt;&lt;STRONG&gt;And from Mike:&lt;/STRONG&gt;&lt;/FONT&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;As part of our Network Configuration Utility, we ship a utility called SetLACState.exe. It can be used to disable/enable a Local Area Connection (LAC) in windows.&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;FONT color="#000000"&gt;&lt;STRONG&gt;Any other suggestions?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 27 Feb 2012 03:26:14 GMT</pubDate>
    <dc:creator>chuckk281</dc:creator>
    <dc:date>2012-02-27T03:26:14Z</dc:date>
    <item>
      <title>Auto NIC failover scripts for Windows &amp; Linux?</title>
      <link>https://community.hpe.com/t5/bladesystem-general/auto-nic-failover-scripts-for-windows-amp-linux/m-p/5564157#M32150</link>
      <description>&lt;P&gt;&lt;FONT color="#000000"&gt;&lt;STRONG&gt;Stan was looking for a NIC failover test script:&lt;/STRONG&gt;&lt;/FONT&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;Looking for a simple solution for a large financial company…&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They have many C7000 enclosures, win2kX, and linux with teamed NICs, dual paths, redundant switches, &amp;nbsp;etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;They are asking if we have a script or (semi)automated method, to cause a failover on the NICs, ( Network A -&amp;gt; Network B) to validate, test in-frequently, to verify that all failover networks are working correctly?&amp;nbsp; This would include doing the failover and verifing network conectivity on Network B, for example….&lt;/P&gt;&lt;P&gt;An automated or manually kicked off script would be the ideal, vs manual intervention on the various servers….&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Wondering if someone has tackled this?&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;FONT color="#000000"&gt;&lt;STRONG&gt;From Chris:&lt;/STRONG&gt;&lt;/FONT&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 don’t have a script, nor had anyone request this.&amp;nbsp; However, just thinking off the top of my head, you can use NETSH in Windows to disable a specific connection, and &lt;EM&gt;ifconfig down eth#&lt;/EM&gt; (or &lt;EM&gt;if-down&lt;/EM&gt; if the distro is Red Hat based) in Linux.&amp;nbsp; I wouldn’t suggest a customer do this during production hours, but rather during maintenance windows (if possible.)&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;FONT color="#000000"&gt;&lt;STRONG&gt;And from Mike:&lt;/STRONG&gt;&lt;/FONT&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;As part of our Network Configuration Utility, we ship a utility called SetLACState.exe. It can be used to disable/enable a Local Area Connection (LAC) in windows.&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;FONT color="#000000"&gt;&lt;STRONG&gt;Any other suggestions?&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Feb 2012 03:26:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/auto-nic-failover-scripts-for-windows-amp-linux/m-p/5564157#M32150</guid>
      <dc:creator>chuckk281</dc:creator>
      <dc:date>2012-02-27T03:26:14Z</dc:date>
    </item>
  </channel>
</rss>

