Network Configuration¶
Subnet¶
All cluster equipment (head node, computing nodes, NAS) shares the same /24 subnet within the IST co-location facility.
| Equipment | IP | Note |
|---|---|---|
| Head node | xxx.xx.134.102 |
User login, job scheduler |
| NAS (nas10g) | xxx.xx.134.103 |
Also serves as internal DNS |
| NAS (nas10g) | xxx.xxx.xxx.104 |
Secondary LAN port |
| Computing nodes (t01~t14) | xxx.xxx.xxx.* range |
Same subnet |
DNS¶
| Nameserver | Role |
|---|---|
xxx.xx.134.103 (NAS) |
Primary — internal hostname resolution for *.cluster.tml |
8.8.8.8 |
Secondary — Google public DNS |
xxx.xxx.xxx.xxx (SNU) |
Tertiary — campus DNS |
Search domain: cluster.tml
InfiniBand¶
The cluster uses Mellanox InfiniBand (100 Gbps) for inter-node communication via RDMA (Remote Direct Memory Access). RDMA allows nodes to directly read/write each other's memory over the network, bypassing the OS — this is critical for MPI parallel jobs.
- IPoIB is not used. All InfiniBand traffic is RDMA only.
- Subnet manager runs on the head node (
mlnx-smservice). - All nodes except t02 are connected.
Firewall (Co-location Rules)¶
The IST co-location facility applies a whitelist-based firewall. Only traffic matching a specific (source IP, destination port) pair is allowed inbound to the cluster.
- Default policy: All inbound traffic is blocked (including campus IPs)
- Whitelisted IPs: Only two IPs are registered — one for the 12F lab (Bldg 301) and one for the 14F lab (Bldg 301)
- Outbound: Not restricted
To access the cluster, you must be connected through the router in either the 12F or 14F lab room. Direct connections from other networks (e.g. campus Wi-Fi, VPN, personal hotspot) will be blocked.
To request access from a new IP, contact the cluster admin.