https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/Recent changes to Configuring_IPv6_in_xCAT_ClusterenMon, 18 May 2015 02:25:49 -0000https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v12 +++ v13 @@ -151,7 +151,7 @@ The "-s" flag specified with confignics indicates that the installation nic should be setup as static configuration using the information in the nics table. - nodeset ipv6cn1 osimage=xxx + nodeset ipv6cn1 osimage=&lt;osimagename&gt; rpower ipv6cn1 reset @@ -281,7 +281,7 @@ chdef dx360m3n06 -p postscripts=confignics - nodeset ipv6cn1 osimage=xxx + nodeset ipv6cn1 osimage=&lt;osimagename&gt; rpower ipv6cn1 reset ~~~~ @@ -359,7 +359,7 @@ ~~~~ chdef ipv6cn1 -p postscripts=setroute - nodeset ipv6cn1 osimage + nodeset ipv6cn1 osimage=&lt;osimagename&gt; rpower ipv6cn1 reset ~~~~ </pre> </div>Guang Cheng LiMon, 18 May 2015 02:25:49 -0000https://sourceforge.netc7d8d3ac4636431f63feb832def7f5a153f9d20ahttps://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v11 +++ v12 @@ -97,7 +97,7 @@ ~~~~ [root@ls21n01 ~]# tabdump networks #netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable - "10_1_0_0-255_255_0_0","10.1.0.0","255.255.0.0","eth1","&lt;xcatmaster&gt;",,"10.1.0.218",,,,,,,,,,"clusters.com",, + "10_1_0_0-255_255_0_0","10.1.0.0","255.255.0.0","eth1","&lt;xcatmaster&gt;",,"10.1.0.218",,,,,,,,,,"clusters.com",, "11_1_0_0-255_255_0_0","11.1.0.0","255.255.0.0","eth1",,,,,,,,,,,,,"clusters.com",, "12_1_0_0-255_255_0_0","12.1.0.0","255.255.0.0","eth1",,,,,,,,,,,,,"clusters.com",, "fd56::/64","fd56::/64","/64","eth0","fd56::214:5eff:fe15:1",,,,,,,,,,,,"clusters.com",, @@ -298,7 +298,7 @@ ~~~~ [root@dx360m3n06 ~]# ip addr show dev ib0 - 9: ib0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc pfifo_fast state UP qlen 1024 + 9: ib0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc pfifo_fast state UP qlen 1024 link/infiniband 80:00:00:48:fe:80:00:00:00:00:00:01:00:02:c9:03:00:4e:47:cf brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff inet 11.1.89.10/16 brd 11.1.255.255 scope global ib0 inet 21.1.89.10/16 brd 21.1.255.255 scope global ib0:2 @@ -309,7 +309,7 @@ inet6 fe80::202:c903:4e:47cf/64 scope link valid_lft forever preferred_lft forever [root@dx360m3n06 ~]# ip addr show dev ib1 - 10: ib1: &lt;BROADCAST,MULTICAST,UP&gt; mtu 65520 qdisc pfifo_fast state UNKNOWN qlen 1024 + 10: ib1: &lt;BROADCAST,MULTICAST,UP&gt; mtu 65520 qdisc pfifo_fast state UNKNOWN qlen 1024 link/infiniband 80:00:00:49:fe:80:00:00:00:00:00:00:00:02:c9:03:00:4e:47:d0 brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff inet 12.1.89.10/16 brd 12.1.255.255 scope global ib1 inet 22.1.89.10/16 brd 22.1.255.255 scope global ib1:2 </pre> </div>Lissa VallettaTue, 09 Sep 2014 13:54:12 -0000https://sourceforge.net10e1b7f3963c0379cd45090756ac9a43de3fba54https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v10 +++ v11 @@ -218,7 +218,7 @@ -## Configure IPv6 Addresses on the Compute Nodes for Ethernet Adapters +## Configure IPv6 Addresses on the Compute Nodes for InfiniBand Adapters Here is an example on how to configure the IPv4/IPv6 addresses for the Infiniband adapters using the nics table. </pre> </div>Guang Cheng LiTue, 19 Aug 2014 06:31:32 -0000https://sourceforge.nete7b18933be089ae45dfb2e4f18d8fd8e068730e1https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v9 +++ v10 @@ -1,3 +1,6 @@ + + + Note: this doc only works for xCAT 2.8.1 and above and on a Linux cluster. IPv6 support on Ubuntu is not covered by this doc. </pre> </div>Lissa VallettaTue, 29 Jul 2014 17:20:29 -0000https://sourceforge.net7affab611acc3cd50eed4b667455d3928d4a1582https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v8 +++ v9 @@ -36,7 +36,7 @@ ## Connect to xcatd Through IPv6 -The xCAT remote clients, usually on the login nodes, could connect to the xcatd on the management node. There are not too many differences between connecting to xcatd through IPv4 address and IPv6 address, you could refer to [Granting_Users_xCAT_privileges#Setup_Login_Node_.28remote_client.29] for details on how to setup remote client, here is the summarized procedure of setting up remote client and connecting to xcatd through IPv6: +The xCAT remote clients, usually on the login nodes, could connect to the xcatd on the management node. There are not too many differences between connecting to xcatd through IPv4 address and IPv6 address, you could refer to [Granting_Users_xCAT_privileges/#setup-login-node-remote-client](Granting_Users_xCAT_privileges/#setup-login-node-remote-client) for details on how to setup remote client, here is the summarized procedure of setting up remote client and connecting to xcatd through IPv6: 1\. Install required packages on remote client, including perl-xCAT-*, xCAT-client-* from xcat-core and perl-IO-Socket-SSL*, perl-Net-SSLeay-*, perl-DBI-* from xcat-dep. </pre> </div>Lissa VallettaThu, 24 Jul 2014 17:37:28 -0000https://sourceforge.net0a7c911c83c778e852b84f8359cc388e8eca5defhttps://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v7 +++ v8 @@ -1,6 +1,6 @@ -**Note: this doc only works for xCAT 2.8.1 and above in Linux cluster, configuring IPv6 on AIX will be covered by another doc.** - -**IPv6 support on Ubuntu is not covered by this doc, it will be addressed in a separate work item** +Note: this doc only works for xCAT 2.8.1 and above and on a Linux cluster. + +IPv6 support on Ubuntu is not covered by this doc. [TOC] @@ -27,11 +27,12 @@ ## Prerequisite To configure IPv6 environment, the perl IPv6 packages need to be installed on the management node: - + +~~~~ yum install perl-IO-Socket-INET6 perl-IO-Socket-SSL perl-Socket6 service xcatd stop service xcatd start - +~~~~ ## Connect to xcatd Through IPv6 @@ -43,29 +44,33 @@ 3\. Use environment variable XCATHOST to specify the machine that runs xcatd. The basic syntax of XCATHOST is &lt;nodename or ipaddr&gt;:3001, there are some variants with using IPv6 addresses, and here are some examples: - * Connect to xcatd through global IPv6 address: - +Connect to xcatd through global IPv6 address: + +~~~~ export XCATHOST=[fd57:faaf:e1ab:336:21a:64ff:fee5:aaa]:3001 nodels - +~~~~ * Connect to xcatd through link local IPv6 address: - + +~~~~ export XCATHOST=[fe80::21a:64ff:fe02:c4%eth0]:3001 # the %eth0 indicates the outbound interface nodels - +~~~~ * Connects to xcatd through the the global IPv6 hostname: - + +~~~~ export XCATHOST=mn-ipv6-global:3001 nodels - +~~~~ * Connects to xcatd through the link local IPv6 hostname: - + +~~~~ export XCATHOST=mn-ipv6-ll%eth0:3001 # the %eth0 indicates the outbound interface nodels - +~~~~ ## Configure IPv6 Addresses and Gateway on the Compute Nodes for Ethernet Adapters @@ -76,15 +81,17 @@ 2\. Specify the node ip addresses and gateway configuration in nics table. Here is an example on how to configure the IPv4/IPv6 addresses for the Ethernet adapters in the nics table. - + +~~~~ [root@ls21n01 ~]# tabdump nics #node,nicips,nichostnamesuffixes,nictypes,niccustomscripts,nicnetworks,nicaliases,comments,disable "ipv6cn1","eth0!10.1.89.7|fd56::214:5eff:fe15:849b|2000::214:5eff:fe15:849b,eth1!11.1.89.7|fd57::214:5eff:fe15:849b|2001::214:5eff:fe15:849b,eth2!12.1.89.7|fd58::214:5eff:fe15:849b|2002::214:5eff:fe15:849b","eth0!|-eth0-ipv6-1|-eth0-ipv6-2,eth1!-eth1|-eth1-ipv6-1|-eth1-ipv6-2,eth2!-eth2|-eth2-ipv6-1|-eth2-ipv6-2","eth0!Ethernet,eth1!Ethernet,eth2!Ethernet",,"eth0!10_1_0_0-255_255_0_0|fd56::/64|2000::/64,eth1!11_1_0_0-255_255_0_0|fd57::/64|2001::/64,eth2!12_1_0_0-255_255_0_0|fd58::/64|2002::/64",,, - [root@ls21n01 ~]# - + +~~~~ 3\. Add network entries for the nics in the networks table - + +~~~~ [root@ls21n01 ~]# tabdump networks #netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable "10_1_0_0-255_255_0_0","10.1.0.0","255.255.0.0","eth1","&lt;xcatmaster&gt;",,"10.1.0.218",,,,,,,,,,"clusters.com",, @@ -96,8 +103,8 @@ "2000::/64","2000::/64","/64","eth0",,,,,,,,,,,,,"clusters.com",, "2001::/64","2001::/64","/64","eth1",,,,,,,,,,,,,"clusters.com",, "2002::/64","2002::/64","/64","eth2",,,,,,,,,,,,,"clusters.com",, - [root@ls21n01 ~]# - + +~~~~ In this example, the fd56::214:5eff:fe15:1 is used as the IPv6 default gateway for the compute node ipv6cn1. Please be aware that only one IPv6 default gateway could be specified, if you would like to setup different gateways for different IPv6 subnets, see the section "**Configure IPv6 routing on the compute nodes**" for more details. @@ -106,12 +113,14 @@ The makehosts is able to setup both the IPv4 hostnames and IPv6 hostnames in /etc/hosts based on information stored in the nics table, here is an example: 4.1. Run makehosts to setup the IPv6 entries in /etc/hosts - + +~~~~ makehosts ipv6cn1 - +~~~~ 4.2. Check the IPv6 entries are setup correctly in /etc/hosts - + +~~~~ [root@ls21n01 ~]# cat /etc/hosts | grep ipv6cn1 12.1.89.7 ipv6cn1-eth2 ipv6cn1-eth2.clusters.com fd58::214:5eff:fe15:849b ipv6cn1-eth2-ipv6-1 ipv6cn1-eth2-ipv6-1.clusters.com @@ -122,19 +131,20 @@ 10.1.89.7 ipv6cn1 ipv6cn1.clusters.com fd56::214:5eff:fe15:849b ipv6cn1-eth0-ipv6-1 ipv6cn1-eth0-ipv6-1.clusters.com 2000::214:5eff:fe15:849b ipv6cn1-eth0-ipv6-2 ipv6cn1-eth0-ipv6-2.clusters.com - [root@ls21n01 ~]# - + +~~~~ 5\. Configure IPv4/IPv6 addresses and IPv6 default gateway on the compute node The postscript **confignics** can configure the IPv4 and IPv6 addresses and gateway on the compute nodes. It could be called through whatever possible ways: 5.1 Setup the IPv4/IPv6 addresses and IPv6 default gateway on the compute node during operating system provisioning - + +~~~~ chdef ipv6cn1 -p postscripts=confignics or chdef ipv6cn1 -p postscripts="confignics -s" - +~~~~ The "-s" flag specified with confignics indicates that the installation nic should be setup as static configuration using the information in the nics table. @@ -143,11 +153,12 @@ 5.2 Setup the IPv4/IPv6 addresses and IPv6 default gateway on the compute node through updatenode - + +~~~~ updatenode ipv6cn1 -P confignics or updatenode ipv6cn1 -P "confignics -s" - +~~~~ The "-s" flag specified with confignics indicates that the installation nic should be setup as static configuration using the information in the nics table. @@ -155,7 +166,8 @@ 6\. Verify the configuration on the compute nodes When the confignics finishes setup the IPv4 and IPv6 addresses and gateway on the compute nodes, the following commands could be used to verify the configuration: - + +~~~~ [root@ipv6cn1 ~]# ifconfig eth0 Link encap:Ethernet HWaddr 42:C6:0A:01:59:07 inet addr:10.1.89.7 Bcast:10.1.255.255 Mask:255.255.0.0 @@ -190,29 +202,33 @@ TX packets:17 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3696 (3.6 KiB) TX bytes:1226 (1.1 KiB) - [root@ipv6cn1 ~]# +~~~~ - +~~~~ [root@ipv6cn1 ~]# ip -6 route show default default via fd56::214:5eff:fe15:1 dev eth0 metric 1 mtu 1500 advmss 1440 hoplimit 4294967295 default via fe80::226:88ff:fe57:b7f0 dev eth1 proto kernel metric 1024 expires 0sec mtu 1500 advmss 1440 hoplimit 64 - [root@ipv6cn1 ~]# +~~~~ + ## Configure IPv6 Addresses on the Compute Nodes for Ethernet Adapters Here is an example on how to configure the IPv4/IPv6 addresses for the Infiniband adapters using the nics table. - + +~~~~ [root@ls21n01 ~]# tabdump nics "dx360m3n06","ib0!11.1.89.10|21.1.89.10|fd57::214:5eff:fe15:8496|2000::214:5eff:fe15:8496,ib1!12.1.89.10|22.1.89.10|fd58::214:5eff:fe15:8496|2001::214:5eff:fe15:8496","ib0!-ib0|-ib0-2|-ib0-ipv6-1|-ib0-ipv6-2,ib1!-ib1|-ib1-2|-ib1-ipv6-1|-ib1-ipv6-2","ib0!Infiniband,ib1!Infiniband",,"ib0!11_1_0_0-255_255_0_0|21_1_0_0-255_255_0_0|fd57::/64|2000::/64,ib1!12_1_0_0-255_255_0_0|22_1_0_0-255_255_0_0|fd58::/64|2001::/64",,, - [root@ls21n01 ~]# +~~~~ + 3\. Add network entries for the nics in the networks table - + +~~~~ [root@ls21n01 ~]# tabdump networks #netname,net,mask,mgtifname,gateway,dhcpserver,tftpserver,nameservers,ntpservers,logservers,dynamicrange,staticrange,staticrangeincrement,nodehostname,ddnsdomain,vlanid,domain,comments,disable "11_1_0_0-255_255_0_0","11.1.0.0","255.255.0.0","ib0",,,,,,,,,,,,,"clusters.com",, @@ -223,7 +239,7 @@ "fd58::/64","fd58::/64","/64","ib1",,,,,,,,,,,,,"clusters.com",, "2000::/64","2000::/64","/64","ib0",,,,,,,,,,,,,"clusters.com",, "2001::/64","2001::/64","/64","ib1",,,,,,,,,,,,,"clusters.com",, - [root@ls21n01 ~]# +~~~~ 4\. Setup /etc/hosts for the Infiniband IPv6 entries @@ -231,12 +247,14 @@ The makehosts is able to setup both the IPv4 hostnames and IPv6 hostnames in /etc/hosts based on information stored in the nics table, here is an example: 4.1. Run makehosts to setup the IPv6 entries in /etc/hosts - + +~~~~ makehosts dx360m3n06 - +~~~~ 4.2. Check the IPv6 entries are setup correctly in /etc/hosts - + +~~~~ [root@ls21n01 ~]# cat /etc/hosts | grep dx360m3n06 10.1.0.236 dx360m3n06.clusters.com dx360m3n06 12.1.89.10 dx360m3n06-ib2 dx360m3n06-ib2.clusters.com @@ -247,7 +265,7 @@ 21.1.89.10 dx360m3n06-ib1-2 dx360m3n06-ib1-2.clusters.com fd57::214:5eff:fe15:8496 dx360m3n06-ib1-ipv6-1 dx360m3n06-ib1-ipv6-1.clusters.com 2000::214:5eff:fe15:8496 dx360m3n06-ib1-ipv6-2 dx360m3n06-ib1-ipv6-2.clusters.com - [root@ls21n01 ~]# +~~~~ 5\. Configure IPv4/IPv6 addresses for the Infiniband adapters @@ -255,24 +273,27 @@ The postscript **confignics** can configure the IPv4 and IPv6 addresses for the Infiniband adapters. It could be called through whatever possible ways: 5.1 Setup the IPv4/IPv6 addresses for the Infiniband adapters during operating system provisioning - + +~~~~ chdef dx360m3n06 -p postscripts=confignics nodeset ipv6cn1 osimage=xxx rpower ipv6cn1 reset - +~~~~ 5.2 Setup the IPv4/IPv6 addresses and IPv6 default gateway on the compute node through updatenode - + +~~~~ updatenode ipv6cn1 -P confignics - +~~~~ 6\. Verify the configuration on the compute nodes When the confignics finishes setup the IPv4 and IPv6 addresses for the Infiniband adapters, the following commands could be used to verify the configuration: - + +~~~~ [root@dx360m3n06 ~]# ip addr show dev ib0 9: ib0: &lt;BROADCAST,MULTICAST,UP,LOWER_UP&gt; mtu 65520 qdisc pfifo_fast state UP qlen 1024 link/infiniband 80:00:00:48:fe:80:00:00:00:00:00:01:00:02:c9:03:00:4e:47:cf brd 00:ff:ff:ff:ff:12:40:1b:ff:ff:00:00:00:00:00:00:ff:ff:ff:ff @@ -293,7 +314,8 @@ valid_lft forever preferred_lft forever inet6 fd58::214:5eff:fe15:8496/64 scope global tentative valid_lft forever preferred_lft forever - [root@dx360m3n06 ~]# +~~~~ + **Note: xCAT only covers the IPoIB IPv6 configuration on the compute nodes from the IP layer perspective, the IPv6 in IPoIB configuration depends on the Infiniband IPv6 support structure, like Infiniband switches, operating systems and device drivers, you might need to do more configuration for IPv6 work in IPoIB environment, or even worse, it is possible the IPv6 could not work with some specific IPoIB configuration.** @@ -303,55 +325,64 @@ The IPv6 routing setup on the compute nodes follows the same procedure as the IPv6 routing setup. 1\. Add the network routes in the routes table - + +~~~~ [root@ls21n01 ~]# tabdump routes #routename,net,mask,gateway,ifname,comments,disable "13route","13.1.0.0","255.255.0.0","11.1.89.1",,, "14route","14.1.0.0","255.255.0.0","12.1.89.1",,, "fd59route","fd59::/64","/64","fd56::214:5eff:fe15:1","eth0",, - [root@ls21n01 ~]# - + +~~~~ 2\. Associate the routes to the compute nodes - + +~~~~ [root@ls21n01 ~]# chdef ipv6cn1 routenames=13route,14route,fd59route 1 object definitions have been created or modified. - [root@ls21n01 ~]# +~~~~ + 3\. Setup up the routing To setup the routes on the management node: - + +~~~~ makeroutes -r 13route,14route,fd59route - +~~~~ To setup the routes on the compute nodes during operating system provisioning: - + +~~~~ chdef ipv6cn1 -p postscripts=setroute nodeset ipv6cn1 osimage rpower ipv6cn1 reset - +~~~~ To setup the routes on the compute nodes when the compute nodes are up and running: - + +~~~~ makeroutes ipv6cn1 -r 13route,14route,fd59route - +~~~~ To remove the routes on the management node: - + +~~~~ makeroutes -d -r 13route,14route,fd59route - +~~~~ To remove the routes on the compute nodes: - + +~~~~ makeroutes ipv6cn1 -d -r 13route,14route,fd59route - +~~~~ 4\. Verify the routing setup When the makeroutes finishes the routes setup on the management node or compute nodes, the following commands could be used to verify the routes setup. - + +~~~~ [root@ipv6cn1 ~]# ip route show 14.1.0.0/16 via 12.1.89.1 dev eth2 12.1.0.0/16 dev eth2 proto kernel scope link src 12.1.89.7 @@ -361,16 +392,19 @@ 169.254.0.0/16 dev eth1 scope link metric 1003 169.254.0.0/16 dev eth2 scope link metric 1004 11.1.0.0/16 dev eth1 proto kernel scope link src 11.1.89.7 - [root@ipv6cn1 ~]# - - +~~~~ + + +~~~~ [root@ipv6cn1 ~]# ip -6 route show fd59::/64 fd59::/64 via fd56::214:5eff:fe15:1 dev eth0 metric 1024 mtu 1500 advmss 1440 hoplimit 4294967295 - [root@ipv6cn1 ~]# +~~~~ + On RedHat: - + +~~~~ [root@ipv6cn1 ~]# cat /etc/sysconfig/static-routes # xCAT_CONFIG_START any net 13.1.0.0 netmask 255.255.0.0 gw 11.1.89.1 @@ -380,11 +414,13 @@ # xCAT_CONFIG_START eth0 fd59::/64 fd56::214:5eff:fe15:1 # xCAT_CONFIG_END - [root@ipv6cn1 ~]# +~~~~ + On SLES: - + +~~~~ ipv6cn2:~ # cat /etc/sysconfig/network/routes default fd56::214:5eff:fe15:1 - - # xCAT_CONFIG_START @@ -392,20 +428,22 @@ 14.1.0.0 12.1.89.1 255.255.0.0 fd59::/64 fd56::214:5eff:fe15:1 - - # xCAT_CONFIG_END - ipv6cn2:~ # - + +~~~~ ## Setup the Ipforward for IPv6 on MN If there is any IPv6 network entry is defined in the networks table, when the xCAT is installed on the management node, the IPv6 forwarding will be enabled. To check the IPv6 forwarding on the management node: - + +~~~~ [root@ls21n01 ~]# cat /etc/sysctl.conf | grep net.ipv6.conf.all.forwarding net.ipv6.conf.all.forwarding = 1 [root@ls21n01 ~]# cat /proc/sys/net/ipv6/conf/all/forwarding 1 - [root@ls21n01 ~]# - - -**Note: this is a temporary solution, in some futher xCAT release, the network services setup on the management node will be based on the information in the servicenode table.** +~~~~ + + + +Note: this is a temporary solution, in some future xCAT release, the network services setup on the management node will be based on the information in the servicenode table. </pre> </div>Lissa VallettaThu, 24 Jul 2014 17:36:01 -0000https://sourceforge.nete8dd31ebb233e2a3cb633ab435f261ddfbee4d83https://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v6 +++ v7 @@ -1,4 +1,4 @@ -**Note: this doc only works for Linux cluster, configuring IPv6 on AIX will be covered by another doc.** +**Note: this doc only works for xCAT 2.8.1 and above in Linux cluster, configuring IPv6 on AIX will be covered by another doc.** **IPv6 support on Ubuntu is not covered by this doc, it will be addressed in a separate work item** </pre> </div>Guang Cheng LiMon, 23 Jun 2014 15:24:20 -0000https://sourceforge.net1694e43dda7fe7d32d1ba67b2ed0e85249819f7chttps://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v5 +++ v6 @@ -63,12 +63,9 @@ * Connects to xcatd through the link local IPv6 hostname: - export XCATHOST=mn-ipv6-ll%eth0:3001 + export XCATHOST=mn-ipv6-ll%eth0:3001 # the %eth0 indicates the outbound interface nodels - - - ## Configure IPv6 Addresses and Gateway on the Compute Nodes for Ethernet Adapters </pre> </div>Guang Cheng LiMon, 23 Jun 2014 15:24:20 -0000https://sourceforge.net37f8c510cc5b96a313bb9e948084827a7fa0904chttps://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre>--- v4 +++ v5 @@ -8,6 +8,7 @@ This doc indicates how to configure IPv6 in xCAT cluster, the high level logic of using IPv6 in xCAT cluster is: + * xcat clients can connect to xcatd on the management node using ipv6 * The os provisioning is done through ipv4 network. * The ethernet adapters and Infiniband adapters on the compute nodes could be configured with ipv4 only, or ipv6 only, or both * The compute nodes could use ipv6 default gateway to communicate with the external ipv6 nodes. @@ -16,6 +17,7 @@ The specific support xcat needs to provide: + * xcatd accepts connections through IPv6 * Use makehosts command to setup IPv6 hostnames in /etc/hosts * Use confignics postscript to configure the IPv6 addresses on the compute nodes, for both Ethernet and Infiniband * Use confignics postscript to configure IPv6 gateway on the compute nodes, for both Ethernet and Infiniband @@ -31,7 +33,44 @@ service xcatd start -## Configure IPv6 addresses and gateway on the compute nodes for Ethernet adapters +## Connect to xcatd Through IPv6 + +The xCAT remote clients, usually on the login nodes, could connect to the xcatd on the management node. There are not too many differences between connecting to xcatd through IPv4 address and IPv6 address, you could refer to [Granting_Users_xCAT_privileges#Setup_Login_Node_.28remote_client.29] for details on how to setup remote client, here is the summarized procedure of setting up remote client and connecting to xcatd through IPv6: + +1\. Install required packages on remote client, including perl-xCAT-*, xCAT-client-* from xcat-core and perl-IO-Socket-SSL*, perl-Net-SSLeay-*, perl-DBI-* from xcat-dep. + +2\. Setup credentials on the remote client. For root user, simply copy the ~/.xcat from the management node; for non-root user, run command /opt/xcat/share/xcat/scripts/setup-local-client.sh &lt;username&gt; as root on the management node, then copy the ~/.xcat from the management node to remote clients. + +3\. Use environment variable XCATHOST to specify the machine that runs xcatd. The basic syntax of XCATHOST is &lt;nodename or ipaddr&gt;:3001, there are some variants with using IPv6 addresses, and here are some examples: + + * Connect to xcatd through global IPv6 address: + + export XCATHOST=[fd57:faaf:e1ab:336:21a:64ff:fee5:aaa]:3001 + nodels + + + * Connect to xcatd through link local IPv6 address: + + export XCATHOST=[fe80::21a:64ff:fe02:c4%eth0]:3001 # the %eth0 indicates the outbound interface + nodels + + + * Connects to xcatd through the the global IPv6 hostname: + + export XCATHOST=mn-ipv6-global:3001 + nodels + + + * Connects to xcatd through the link local IPv6 hostname: + + export XCATHOST=mn-ipv6-ll%eth0:3001 + nodels + + + + + +## Configure IPv6 Addresses and Gateway on the Compute Nodes for Ethernet Adapters 1\. Plan the IPv6 addresses for the compute nodes @@ -166,7 +205,7 @@ [root@ipv6cn1 ~]# -## Configure IPv6 addresses on the compute nodes for Ethernet adapters +## Configure IPv6 Addresses on the Compute Nodes for Ethernet Adapters Here is an example on how to configure the IPv4/IPv6 addresses for the Infiniband adapters using the nics table. @@ -262,7 +301,7 @@ **Note: xCAT only covers the IPoIB IPv6 configuration on the compute nodes from the IP layer perspective, the IPv6 in IPoIB configuration depends on the Infiniband IPv6 support structure, like Infiniband switches, operating systems and device drivers, you might need to do more configuration for IPv6 work in IPoIB environment, or even worse, it is possible the IPv6 could not work with some specific IPoIB configuration.** -## Configure IPv6 routing on the compute nodes +## Configure IPv6 Routing on the Compute Nodes The IPv6 routing setup on the compute nodes follows the same procedure as the IPv6 routing setup. @@ -359,7 +398,7 @@ ipv6cn2:~ # -## Setup the ipforward for IPv6 on MN +## Setup the Ipforward for IPv6 on MN If there is any IPv6 network entry is defined in the networks table, when the xCAT is installed on the management node, the IPv6 forwarding will be enabled. </pre> </div>Guang Cheng LiMon, 23 Jun 2014 15:24:20 -0000https://sourceforge.net67e90d738d0157dd7c620df69310a495e6b681fdhttps://sourceforge.net/p/xcat/wiki/Configuring_IPv6_in_xCAT_Cluster/<div class="markdown_content"><pre></pre> </div>Guang Cheng LiMon, 23 Jun 2014 15:24:19 -0000https://sourceforge.netb1c1ea2ce75ed2320493f870b9eeb9d5c133874f