==Overview== There's no feature in xCAT to support the configuration of network interfaces for Windows compute node. Currently, xCAT only uses the default setting of nics for them to get configuration from dhcp server.
This design is used to describe how to use nics table to configure the network cards during Windows deployment.
==Interface== The interface name in Windows is like 'Local Area Connection' (first interface), 'Local Area Connection 2' (second interface) and 'Local Area Connection x' (next interface). Since the ethernet name in Windows compute node includes spaces, both xCAT and PCM need to put effort to handle the ethernet name correctly.
===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=== The installnic will only be set to static when the site.setinstallnic is set to '1' or 'yes', otherwise the installnic will keep to get IP from dhcp server even if it has been set in nics table.
The node.installnic or node.primary is used specify the name of instlalnic. For Windows deployment, it must be specified. Otherwise xCAT will consider all the interfaces in nics table as non-installnic. chdef -t site clustersite setinstallnic=1 chdef installnic='Local Area Connection'
===Set Gateway Attribute=== Only the gateway from the intallnic network will be set to default gateway for Windows compute node. The gateway which is set in other networks will be ignored.
===Generate Configuration=== Run nodeset command will make the setting take effect. nodeset osimage=win2k8r2-x86_64-install-enterprise
Then you can check the setting of component 'Microsoft-Windows-TCPIP in /install/autoinst/x3550m4n03.xml. Refer to http://technet.microsoft.com/en-us/library/ff716228.aspx
==Example==
To generated setting in /install/autoinst/x3550m4n03.xml base on the following setting in nics and networks tables.
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",,,,,,
Configuration of interfaces: false false Local Area Connection 3 192.168.13.250/24 1 192.168.13.254 0/0 false false Local Area Connection 2 192.168.12.250/24
== 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
- Apr 22, 2016: xCAT 2.11.1 released.
- Mar 11, 2016: xCAT 2.9.3 (AIX only) released.
- Dec 11, 2015: xCAT 2.11 released.
- Nov 11, 2015: xCAT 2.9.2 (AIX only) released.
- Jul 30, 2015: xCAT 2.10 released.
- Jul 30, 2015: xCAT migrates from sourceforge to github
- Jun 26, 2015: xCAT 2.7.9 released.
- Mar 20, 2015: xCAT 2.9.1 released.
- Dec 12, 2014: xCAT 2.9 released.
- Sep 5, 2014: xCAT 2.8.5 released.
- May 23, 2014: xCAT 2.8.4 released.
- Jan 24, 2014: xCAT 2.7.8 released.
- Nov 15, 2013: xCAT 2.8.3 released.
- Jun 26, 2013: xCAT 2.8.2 released.
- May 17, 2013: xCAT 2.7.7 released.
- May 10, 2013: xCAT 2.8.1 released.
- Feb 28, 2013: xCAT 2.8 released.
- Nov 30, 2012: xCAT 2.7.6 released.
- Oct 29, 2012: xCAT 2.7.5 released.
- Aug 27, 2012: xCAT 2.7.4 released.
- Jun 22, 2012: xCAT 2.7.3 released.
- May 25, 2012: xCAT 2.7.2 released.
- Apr 20, 2012: xCAT 2.7.1 released.
- Mar 19, 2012: xCAT 2.7 released.
- Mar 15, 2012: xCAT 2.6.11 released.
- Jan 23, 2012: xCAT 2.6.10 released.
- Nov 15, 2011: xCAT 2.6.9 released.
- Sep 30, 2011: xCAT 2.6.8 released.
- Aug 26, 2011: xCAT 2.6.6 released.
- May 20, 2011: xCAT 2.6 released.
- Feb 14, 2011: Watson plays on Jeopardy and is managed by xCAT!
- xCAT Release Notes Summary
- xCAT OS And Hw Support Matrix
- xCAT Test Environment Summary
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.