Although the filers can't be a router, if there are any other alternate paths between your "private" Beowulf network and the "public" network, using routed, the filer could "learn" a poorer route than the one you would like it to do. now.netapp.com does mention that a filer can route it's own packets. (see http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ntapcs1112 )
The safest way to do what you ask is to turn off routed and use static routes for your filer's route table, and let your switches/routers do all the routing outside the network local to the filer interface. This also has the added benefit of saving a tad bit of CPU overhead on the filer. (See System Admin Network Management Guide, Chapter 3)
The answer to your question is YES, you need another "route add" which applies to that interface and tells it how to mask to reach its own network.
JKB
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of ferdberfl@netzero.net Sent: Thursday, November 04, 2004 10:00 AM To: toasters@mathworks.com Subject: re: Routing question
filers don't have any capability to route data between interfaces. There's nothing you need to do to make sure they filer isn't doing any routing. AFIK it is a common use of filers in mixed high security/non secure environments to share common data through filer interfaces connected to both networks.
Note, you will need routing entries to provide paths to networks behind the 2nd interface to the private network. The filer can only point to one gateway for (a 0.0.0.0 entry in the routing table). All other paths off of connected networks have to be pathed via static route table entries.
-----Original Message----- From: Matt Phelps [ mailto:mphelps@cfa.harvard.edu mailto:mphelps@cfa.harvard.edu] Sent: Thursday, November 04, 2004 6:30 AM To: toasters@mathworks.com Subject: Routing question
Hi all, I want to add a second nework interface (actually a vif, but it shouldn't make any difference) and attach it to a private network on a beowulf cluster; but I want to also keep the current interface to our public network up. How do I make sure the filer isn't doing any routing? Currently, the vif setup for our public network looks like this (IP addresses removed to protect the innocent): hostname foo vif create multi vif0 e9a e9b ifconfig vif0 `hostname`-vif0 netmask 255.255.248.0 route add default xxx.xxx.xxx.xxx routed on
So do I just add a foo-cluster (and foo-cluster-vif1) entry to the hosts file with the appropriate private IP address (e.g. 10.1.200.1) and then do: vif create multi vif1 e11a e11b ifconfig vif1 foo-cluster-vif1 netmask 255.0.0.0
Do I need another "route add" for 10.1.1.1 (the gateway to the private network?). I don't understand this stuff.
-- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps@cfa.harvard.edu, http://cfa-www.harvard.edu/ http://cfa-www.harvard.edu