From: Josh Glover (jmglov@wm.edu)
Date: Mon Jun 17 2002 - 11:40:49 EDT
I am trying to bring up the second ethernet interface on an Enterprise
4500 (hereafter referred to as "foo"), and seeing some severe network
performance degradation when I do.
Here is how I am bringing the interface up:
:jmglov@foo; sudo ifconfig hme1 plumb
:jmglov@foo; sudo ifconfig hme1 192.168.1.2 broadcast 192.168.1.255 \
netmask 255.255.255.0 up
And as soon as I do this, I start seeing some serious lag in my ssh
session. The remote machine will seem to stop responding for 30 seconds
or so at a time.
The file /etc/notrouter does exist, which I thought would disable IP
forwarding, but just in case:
:jmglov@foo; sudo ndd -set /dev/ip ip_forwarding 0
And sure enough:
:jmglov@r2; ndd /dev/ip ip_forwarding
0
Things seem pretty normal:
:jmglov@foo; ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232
index 1 inet 127.0.0.1 netmask ff000000
hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 2 inet xxx.xxx.xxx.xxx netmask ffffff00
broadcast xxx.xxx.xxx.xxx
hme1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500
index 3 inet 192.168.1.2 netmask ffffff00 broadcast 192.168.1.255
I can ping hosts on both networks just fine, and there never seems to be
any serious lag there, responses are coming back at around 300 us.
But I cannot seem to ping the Solaris box from another box on the
192.168.1.0 network (masta). Strangely enough, when I ping the broadcast
address for that network, I *do* get a response from the Solaris box, .2:
:jmglov@masta; ping -b 192.168.1.255
WARNING: pinging broadcast address
PING 192.168.1.255 (192.168.1.255) from 192.168.1.1 : 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=0 ttl=255 time=61 usec
64 bytes from 192.168.1.112: icmp_seq=0 ttl=255 time=183 usec (DUP!)
64 bytes from 192.168.1.105: icmp_seq=0 ttl=255 time=209 usec (DUP!)
64 bytes from 192.168.1.107: icmp_seq=0 ttl=255 time=212 usec (DUP!)
64 bytes from 192.168.1.104: icmp_seq=0 ttl=255 time=187 usec (DUP!)
64 bytes from 192.168.1.109: icmp_seq=0 ttl=255 time=236 usec (DUP!)
64 bytes from 192.168.1.103: icmp_seq=0 ttl=255 time=223 usec (DUP!)
64 bytes from 192.168.1.110: icmp_seq=0 ttl=255 time=246 usec (DUP!)
64 bytes from 192.168.1.106: icmp_seq=0 ttl=255 time=249 usec (DUP!)
64 bytes from 192.168.1.102: icmp_seq=0 ttl=255 time=279 usec (DUP!)
64 bytes from 192.168.1.108: icmp_seq=0 ttl=255 time=265 usec (DUP!)
64 bytes from 192.168.1.101: icmp_seq=0 ttl=255 time=268 usec (DUP!)
64 bytes from 192.168.1.2: icmp_seq=0 ttl=255 time=297 usec (DUP!)
^^^^^^^^^^^
I *can* NFS mount an exported share from the Solaris box, but access
times are terrible. Simply doing an 'ls' on the mounted share takes
several minutes, but does return the listing eventually.
I *must* be missing something. I looked through the archive of this
list, as well as searching BigAdmin and doing some Googling. But nada.
Ideas?
TIA and WS.
-- Josh Glover <jmglov@incogen.com> Associate Systems Administrator INCOGEN, Inc. _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:24:30 EDT