Yes, /etc/netmasks: 10.16.3.0 255.255.255.0 10.16.118.0 255.255.255.0 10.16.119.0 255.255.255.0 10.16.254.0 255.255.255.0 151.142.223.0 255.255.255.0

I didnt know about the /etc/notrouter option...nothin like learning a little everyday!

Anyway, rebooting.

And...

# traceroute 10.16.118.10 traceroute: Warning: ckecksums disabled traceroute: Warning: Multiple interfaces found; using 151.142.223.53 @ hme0 traceroute to 10.16.118.10 (10.16.118.10), 30 hops max, 40 byte packets 1 *^C#

Still there.

-----Original Message----- From: Tim McCarthy [mailto:tmac@netapp.com] Sent: Monday, July 26, 1999 10:23 AM To: Mohler, Jeff Cc: toasters@mathworks.com Subject: Re: Strange routing problem.

Did you make a /etc/notrouter file on your solaris box? This prevents the Solaris box from becoming a router at boot time.

And how about /etc/netmasks?

I would put two entries in just to be safe: 10.16.118.0 255.255.255.0 10.16.119.0 255.255.255.0

--tmac

Timothy A. McCarthy --> System Engineer, Eastern Region. Network Appliance http://www.netapp.com 301-230-5847 Office \ / Page Me at:@@ 301-230-5852 Fax / 800-654-9619

On Mon, 26 Jul 1999, Mohler, Jeff wrote:

Greetings:

I have a routing problem on a 2.6 box, here is the detail.

I want to send traffic out to 10.16.118.20 on qfe0, which will be a

private

10/100 segment to the NetApp for NFS traffic. I am only using 10.16.118.0 in this message, because 119.0 does the same thing on qfe1.

This is a prototype box to configure and test first, then deploy to the field installed Solaris machines.

The network is like this:

NETAPP-F760:e0 public interface connected to 3/1 on a Cat 5505

Switch, on

VLAN 223 (public addressed traffic) NETAPP-F760:ech1 channel of e1a and e1b on 10.16.118.0 on 5/1-2 (channel) on VLAN 118 - 10.16.118.10 NETAPP-F760:ech2 channel of e1c and e1d on 10.16.119.0 on 5/3-4 (channel) on VLAN 119 - 10.16.119.10

On the sun box I have:

Sun:e0 public interface connected to 3/2 on Cat 5505 on

VLAN 223

Sun:qfe0 10.16.118.23 connected to 3/15 on Cat 5505 on VLAN 118 Sun:qfe1 10.16.119.23 connected to 3/16 on Cat 5505 on VLAN 119 Sun:qfe2 10.16.254.23 not yet connected for ADSM traffic Sun:qfe3 10.16.3.117 connected to management LAN

The interface is up, here is netstat output:

Routing Table: Destination Gateway Flags Ref Use Interface

---

151.142.223.0 151.142.223.53 U 2 282 hme0 10.16.118.0 10.16.118.23 U 2 5351 qfe0 10.16.119.0 10.16.119.23 U 2 0 qfe1 10.16.3.0 10.16.3.117 U 2 3 qfe3 default 151.142.223.1 UG 0 129 127.0.0.1 127.0.0.1 UH 0 4 lo0

A traceroute to 10.16.118.10 shows the machine choosing hme0 for a route...why?

# traceroute 10.16.118.10 traceroute: Warning: ckecksums disabled traceroute: Warning: Multiple interfaces found; using 151.142.223.53 @

hme0

I have an NFS mount on the Sun box to the filer using the 10.16.118.10 address, and it even shows up as the propler hostname:/<path> in the 'df' output.

I can blow large amounts of dd traffic to/from the mount, and I see NO traffic on the correct Channel (ech1) on the Filer.