[prev in list] [next in list] [prev in thread] [next in thread] 

List:       npaci-rocks-discussion
Subject:    [Rocks-Discuss]  Public interface gateway problem
From:       "Edmondson, Edward" <e.edmondson () ucl ! ac ! uk>
Date:       2019-04-09 9:39:52
Message-ID: F6C6902A-DF07-46B8-BC80-7F586D18B1C5 () ucl ! ac ! uk
[Download RAW message or body]

Hi all,

I've upgraded a Rocks 6.2 cluster to 7.0 - this didn't go entirely according to plan \
the first time, so I've taken the approach of restoring user data by hand, and \
rebuilding the cluster otherwise rather than using a restore roll. Generally that's \
going well.

The one annoyance so far is with a login node - it's got the private interface on em1 \
and a public interface on em2 (as does the head node which is behaving as expected)

I've got the following set up already (names and IPs changed):

[root@cluster ~]# rocks list host route cluster-login
HOST           NETWORK         NETMASK         GATEWAY      SOURCE
cluster-login: 0.0.0.0         0.0.0.0         128.40.3.245 H
cluster-login: 1.2.3.4      255.255.255.255 10.1.1.1     G
cluster-login: 224.0.0.0       255.255.255.0   em1          G
cluster-login: 255.255.255.255 255.255.255.255 em1          G

On every 'rocks sync host network' I have to go back to the login node and do
route add default gw 1.2.3.254 em2
to add the gateway for the public interface back in.

I've done
rocks add host route cluster-login 0.0.0.0 1.2.3.254 netmask=0.0.0.0
but I keep having to redo things by hand to get the public interface working.

Any advice?

Thanks in advance,


--
Dr Edd Edmondson
HPC Systems Manager
Dept of Physics and Astronomy
University College London

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sdsc.edu/pipermail/npaci-rocks-discussion/attachments/20190409/86923ed3/attachment.html \



[prev in list] [next in list] [prev in thread] [next in thread]