^C# ifconfig -a lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 151.142.223.53 netmask ffffff00 broadcast 151.142.223.255 ether 8:0:20:9f:61:a6 qfe0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.118.23 netmask ffffff00 broadcast 10.16.118.255 ether 8:0:20:9f:61:a7 qfe1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.119.23 netmask ffffff00 broadcast 10.16.119.255 ether 8:0:20:9f:61:a8 qfe2: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 0.0.0.0 netmask 0 ether 8:0:20:9f:61:a9 qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.3.117 netmask ffffff00 broadcast 10.16.3.255 ether 8:0:20:9f:61:a0
-----Original Message----- From: Rajeev Agrawala [mailto:rajeeva@research.bell-labs.com] Sent: Monday, July 26, 1999 3:37 PM To: Mohler, Jeff Cc: Tim McCarthy; toasters@mathworks.com Subject: Re: Strange routing problem.
What is the output of ifconfig -a on sun machine. Please send that.
rajeev
"Mohler, Jeff" wrote:
Ok, Ive double checked /etc/netmasks (already was there) /etc/notrouter, /etc/defaultrouter (already was there) changed mac addresses on qfe0-qfe3 so the switch doesnt look at all five interfaces on the machine as one MAC, dbl checked VLAN configs on the Cat 5505 ports..
Still, the Sun wants BADLY to route 10.16.118.0 traffic across the public hme0 interface, instead of the up/configured/plugged-in 10.16.118.23 interface.
Darnit..
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.
Hmm! Things look fine here. I am not sure at the moment, what the problem may be. But I would check 2 things
1. The system is patched uptodate. 2. Check the arp table 'arp -a' and if arp for any of the 10.16.11[89].x is set and the device is set to hme0, delete that arp entry
rajeev
"Mohler, Jeff" wrote:
^C# ifconfig -a lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 151.142.223.53 netmask ffffff00 broadcast 151.142.223.255 ether 8:0:20:9f:61:a6 qfe0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.118.23 netmask ffffff00 broadcast 10.16.118.255 ether 8:0:20:9f:61:a7 qfe1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.119.23 netmask ffffff00 broadcast 10.16.119.255 ether 8:0:20:9f:61:a8 qfe2: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 0.0.0.0 netmask 0 ether 8:0:20:9f:61:a9 qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.3.117 netmask ffffff00 broadcast 10.16.3.255 ether 8:0:20:9f:61:a0
-----Original Message----- From: Rajeev Agrawala [mailto:rajeeva@research.bell-labs.com] Sent: Monday, July 26, 1999 3:37 PM To: Mohler, Jeff Cc: Tim McCarthy; toasters@mathworks.com Subject: Re: Strange routing problem.
What is the output of ifconfig -a on sun machine. Please send that.
rajeev
"Mohler, Jeff" wrote:
Ok, Ive double checked /etc/netmasks (already was there) /etc/notrouter, /etc/defaultrouter (already was there) changed mac addresses on qfe0-qfe3 so the switch doesnt look at all five interfaces on the machine as one MAC, dbl checked VLAN configs on the Cat 5505 ports..
Still, the Sun wants BADLY to route 10.16.118.0 traffic across the public hme0 interface, instead of the up/configured/plugged-in 10.16.118.23 interface.
Darnit..
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.
Good advice.
Look at Sun BugID 4143346. It may relate to what you're seeing. http://sunsolve.sun.com/private-cgi/retrieve.pl?type=0&doc=bug%2Fnetwork... nternet-utility%2F4143346&zone_32=4143346
At 05:47 PM 7/26/99 , Rajeev Agrawala wrote:
Hmm! Things look fine here. I am not sure at the moment, what the problem may be. But I would check 2 things
- The system is patched uptodate.
- Check the arp table 'arp -a' and if arp for any of the 10.16.11[89].x is
set and the device is set to hme0, delete that arp entry
rajeev
"Mohler, Jeff" wrote:
^C# ifconfig -a lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232 inet 127.0.0.1 netmask ff000000 hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 151.142.223.53 netmask ffffff00 broadcast 151.142.223.255 ether 8:0:20:9f:61:a6 qfe0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.118.23 netmask ffffff00 broadcast 10.16.118.255 ether 8:0:20:9f:61:a7 qfe1: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.119.23 netmask ffffff00 broadcast 10.16.119.255 ether 8:0:20:9f:61:a8 qfe2: flags=842<BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 0.0.0.0 netmask 0 ether 8:0:20:9f:61:a9 qfe3: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500 inet 10.16.3.117 netmask ffffff00 broadcast 10.16.3.255 ether 8:0:20:9f:61:a0
-----Original Message----- From: Rajeev Agrawala [mailto:rajeeva@research.bell-labs.com] Sent: Monday, July 26, 1999 3:37 PM To: Mohler, Jeff Cc: Tim McCarthy; toasters@mathworks.com Subject: Re: Strange routing problem.
What is the output of ifconfig -a on sun machine. Please send that.
rajeev
"Mohler, Jeff" wrote:
Ok, Ive double checked /etc/netmasks (already was there) /etc/notrouter, /etc/defaultrouter (already was there) changed mac addresses on qfe0-qfe3 so the switch doesnt look at all five interfaces on the machine as one MAC, dbl checked VLAN configs on the Cat 5505 ports..
Still, the Sun wants BADLY to route 10.16.118.0 traffic across the public hme0 interface, instead of the up/configured/plugged-in 10.16.118.23 interface.
Darnit..
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.
-
Jeffrey Skelton -
Mohler, Jeff -
Rajeev Agrawala