UDCECC  ChemE 

Formulaic Approach to Cluster Private Networking

DateWho
2009-05-06jtfInitial draft

When I originally began running clusters for the College of Engineering I set them up with default network configurations in warewulf and perceus. This usually meant using 172.16.0.0/16 private address space, with addresses chosen anywhere within that range (and not sequentially). This essentially meant that every cluster was more or less running the same IP subnets on its private network.

The first flaw in this plan came when we started getting clusters with multiple network interfaces (gigabit ethernet plus AMSO RDMA ethernet, for example). I need to assign each compute node more than one IP address, and since the interfaces were running on different (non-chained) switches, those addresses needed to come from a unique subnet.

Partitioning of private IP address space

None of the clusters are large enough to use more than 200 addresses per subnet, so rather than use the full 10.0.0.0/8 address space (cluster number in second digit, last two digits partitioned into local subnet and host) I’ve opted to restrict myself to 10.0.0.0/16. The third digit is partitioned into a 5-bit cluster number and a 3-bit local subnet – that’s 32 clusters with 8 local subnets each. That’s plenty 8-)

Cluster Assignments

ClusterCluster NumberSubnet #SubnetSubnet Description
squidward.che1010.0.8.0/24Gigabit ethernet
110.0.9.0/25Myrinet 10G
110.0.9.128/26AMSO LAN, CCIL
110.0.9.192/26AMSO LAN, RDMA
210.0.10.0/24Maintenance (switches, PDUs)
gibbs.che2010.0.16.0/24Gigabit ethernet
110.0.17.0/24Maintenance (switches, PDUs)
darkstar.coastal3010.0.24.0/24Gigabit ethernet
110.0.25.0/24Myrinet 2G
210.0.26.0/24Maintenance (switches, PDUs)
venus.mseg4010.0.32.0/24Gigabit ethernet
110.0.33.0/24Maintenance (switches, PDUs)
cluster/network.txt · Last modified: 2009/09/21 17:04 by zeus
Back to top
Copyright © 2006-2007, College of Engineering, University of Delaware