Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Within each of these configuration files, you can put whatever parameters are specific to that chassis.  Usually Usually, each chassis should be configured exactly the same, but in the case we are discussing, you want to assign the networking parameters in the form below:

[root@c-csn2 nodeconfigs]# cat sn000c290ac7a2.cfg
ipaddress = 192.168.202.84 192.168.202.85 192.168.202.86
gateway = 192.168.202.3
netmask = 255.255.255.0
processes = 3

There is a script  in in the support bundle swarm-support-tools.tgzcalled csn-create-nodeconfigs.sh that will allow you to create the appropriate files assuming your current ip-assignments output is the desired MAC to IP binding.

...

[root@c-csn2 ~]# cat /var/opt/caringo/netboot/content/nodeconfigs/sn000c290ac7a2.cfg
ipaddress = 192.168.202.84 192.168.202.85 192.168.202.86
gateway = 192.168.202.3
netmask = 255.255.255.0
processes = 3

These node-specific files only take effect after a reboot of the nodes.NOTE:

Info
titleNote
  • The Swarm Reporter function in the CSN requires ip-assignments to be up-to-date and accurate.  If you use Swarm Reporter (which is removed in CSN 8.3), using node-specific configuration files may break your reporting.

...

  • You can run the script against a file that had been previously created with ip-assignments command.  Please use the -h flag for an example.

...

  • If the underlying chassis hardware configuration changes, that will not be reflected in this script output.  Ie, if you remove a CPU and boot the chassis again, you may have too many processes defined for the underlying hardware.

...

  • If you change the internal network in the CSN UI, these files will not automatically change.  You would need to delete the files, boot the cluster normally, then run this script again to generate node-specific configuration files that reflect the new networking changes.