<?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 Re: Nic Teaming Ip Configuration Script in ProLiant Servers - Netservers</title>
    <link>https://community.hpe.com/t5/proliant-servers-netservers/nic-teaming-ip-configuration-script/m-p/970298#M15282</link>
    <description>uh oh forgot to change the local area connection name - changed in this version&lt;BR /&gt;&lt;BR /&gt;This will also rename the nic team to Public team or whattever you want.</description>
    <pubDate>Tue, 01 Jul 2008 17:46:36 GMT</pubDate>
    <dc:creator>mark q</dc:creator>
    <dc:date>2008-07-01T17:46:36Z</dc:date>
    <item>
      <title>Nic Teaming Ip Configuration Script</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/nic-teaming-ip-configuration-script/m-p/970297#M15281</link>
      <description>Hi Everyone,&lt;BR /&gt;&lt;BR /&gt;I wrote this script because I'm sick of having to re type in all of the ip information and settings every time I setup a team&lt;BR /&gt;&lt;BR /&gt;tested on 32 bit standard, enterprise, 64 bit standard / enterprise&lt;BR /&gt;&lt;BR /&gt;You must build the team before you run this!&lt;BR /&gt;&lt;BR /&gt;this will&lt;BR /&gt;- ask you for the ip address&lt;BR /&gt;- ask you for the subnet mask&lt;BR /&gt;- ask you for the default gateway&lt;BR /&gt;- rename the team to "Public Team" or whatever you want&lt;BR /&gt;- adds whatever dns servers you want (up to 3)&lt;BR /&gt;- adds whatever wins servers you want (up to 2)&lt;BR /&gt;- fills in whatever dns suffixes you want (in the right order)&lt;BR /&gt;- enable netbios over tcpip (or not if you don't want it to)&lt;BR /&gt;&lt;BR /&gt;'first section searches for the team by the adapter type &lt;BR /&gt;'after it finds this adapter it will change the team name to public team (or whatever you want)&lt;BR /&gt;'all you have to do if you want your team named something else just change this line objItem.Name = "Public Team" to whatever you want&lt;BR /&gt;'after that you will get prompted for the ip address and subnet mask and default gateway&lt;BR /&gt;'change strdns1= your dns server&lt;BR /&gt;'change strdns2= your second dns server&lt;BR /&gt;'change strdns3= your third dns server if you have one&lt;BR /&gt;'change strwins1= your wins server&lt;BR /&gt;'change strwins2= your second wins server&lt;BR /&gt;'change the arrDNSSuffixes = Array("somewhere.com", "somewhere.net", "someotherplace.com", "someotherplace.net") to your dns suffixes&lt;BR /&gt;'change iNetBios= your netbios settings&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jul 2008 16:10:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/nic-teaming-ip-configuration-script/m-p/970297#M15281</guid>
      <dc:creator>mark q</dc:creator>
      <dc:date>2008-07-01T16:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: Nic Teaming Ip Configuration Script</title>
      <link>https://community.hpe.com/t5/proliant-servers-netservers/nic-teaming-ip-configuration-script/m-p/970298#M15282</link>
      <description>uh oh forgot to change the local area connection name - changed in this version&lt;BR /&gt;&lt;BR /&gt;This will also rename the nic team to Public team or whattever you want.</description>
      <pubDate>Tue, 01 Jul 2008 17:46:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-netservers/nic-teaming-ip-configuration-script/m-p/970298#M15282</guid>
      <dc:creator>mark q</dc:creator>
      <dc:date>2008-07-01T17:46:36Z</dc:date>
    </item>
  </channel>
</rss>

