Skip to content

Windows_Multiple_Nics_Configuration

ligc edited this page May 5, 2015 · 14 revisions

Design_Warning

==Overview==

==Interface==

===Set nics Attributes=== You need to specify the IP for the network interfaces in nics table like following. (xCAT will support to set it by chdef command.) nics table #node,nicips,nichostnamesuffixes,nictypes,niccustomscripts,nicnetworks,nicaliases,comments,disable "x3550m4n03","Local Area Connection 3!192.168.13.250,Local Area Connection 2!192.168.12.250",,,,,,,

networks table
#netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable "192_168_13_0-255_255_255_0","192.168.13.0","255.255.255.0",,"192.168.13.254",,,,,,,,"1",,,,,,

PCM configures the bmc interface in the nics table with ethernet name 'bmc', since the 'bmc' interface should not configured in windows compute node, xCAT will ignore the ethernet name 'bmc' when creating the unattend.xml.

In this example, the IP of interface 'Local Area Connection 2' will be set to '192.168.12.250'. And IP of interface 'Local Area Connection 3' will be set to '92.168.13.250'. Since no setting for 'Local Area Connection' (first interface) is specified, it will keep to use dhcp (this is the default setting in Windows node).

'''Note:''' the network for the interfaces must be set correctly in networks table, otherwise the interface will be ignored if cannot find correct netmask for the ip from networks table.

===Set Installnic===

chdef -t site clustersite setinstallnic=1 chdef installnic='Local Area Connection'

===Set Gateway Attribute===

===Generate Configuration=== Run nodeset command will make the setting take effect. nodeset osimage=win2k8r2-x86_64-install-enterprise

==Example==

nics table #node,nicips,nichostnamesuffixes,nictypes,niccustomscripts,nicnetworks,nicaliases,comments,disable "x3550m4n03","Local Area Connection 3!192.168.13.250,Local Area Connection 2!192.168.12.250",,,,,,,

networks table
#netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable "192_168_13_0-255_255_255_0","192.168.13.0","255.255.255.0",,"192.168.13.254",,,,,,,,"1",,,,,,

<component name="Microsoft-Windows-TCPIP" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   <Interfaces>
          <Interface wcm:action="add">
                 <Ipv4Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv4Settings>
                 <Ipv6Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv6Settings>
                 <Identifier>Local Area Connection 3</Identifier>
                 <UnicastIpAddresses>
                        <IpAddress wcm:action="add" wcm:keyValue="1">192.168.13.250/24</IpAddress>
                    </UnicastIpAddresses>
                 <Routes>
                        <Route wcm:action="add">
                               <Identifier>1</Identifier>
                               <NextHopAddress>192.168.13.254</NextHopAddress>
                               <Prefix>0/0</Prefix>
                           </Route>
                    </Routes>
             </Interface>
          <Interface wcm:action="add">
                 <Ipv4Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv4Settings>
                 <Ipv6Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv6Settings>
                 <Identifier>Local Area Connection 2</Identifier>
                 <UnicastIpAddresses>
                        <IpAddress wcm:action="add" wcm:keyValue="1">192.168.12.250/24</IpAddress>
                    </UnicastIpAddresses>
             </Interface>
      </Interfaces>

== Other Design Considerations ==

  • '''Required reviewers''':
  • '''Required approvers''': Bruce Potter, William, Jarrod
  • '''Database schema changes''': N/A
  • '''Affect on other components''': N/A
  • '''External interface changes, documentation, and usability issues''': N/A
  • '''Packaging, installation, dependencies''': N/A
  • '''Portability and platforms (HW/SW) supported''': N/A
  • '''Performance and scaling considerations''': N/A
  • '''Migration and coexistence''': N/A
  • '''Serviceability''': N/A
  • '''Security''': N/A
  • '''NLS and accessibility''': N/A
  • '''Invention protection''': N/A

News

History

  • Oct 22, 2010: xCAT 2.5 released.
  • Apr 30, 2010: xCAT 2.4 is released.
  • Oct 31, 2009: xCAT 2.3 released. xCAT's 10 year anniversary!
  • Apr 16, 2009: xCAT 2.2 released.
  • Oct 31, 2008: xCAT 2.1 released.
  • Sep 12, 2008: Support for xCAT 2 can now be purchased!
  • June 9, 2008: xCAT breaths life into (at the time) the fastest supercomputer on the planet
  • May 30, 2008: xCAT 2.0 for Linux officially released!
  • Oct 31, 2007: IBM open sources xCAT 2.0 to allow collaboration among all of the xCAT users.
  • Oct 31, 1999: xCAT 1.0 is born!
    xCAT started out as a project in IBM developed by Egan Ford. It was quickly adopted by customers and IBM manufacturing sites to rapidly deploy clusters.
Clone this wiki locally