Hi Daniel,
Don't have anything to go by, but in general, these types of problems
are due to naming or other configuration problems, which can manifest
themselves because each zone has its own name space. I have run zones
on systems with bge, eri, hme, nge, e1000g, and other interfaces, and
haven't seen problems like that due to zones.
What are some of the differences between the 220 and 240, for starters?
Steffen
Daniel Synnott wrote On 10/12/06 15:20,:
I am encountering network performance issues, which I believe may be
related to network
drivers. I am observing an unresponsive network configuration on a Sol
10 host configured
with 3 whole root zones. Outside connections to global and non-global
zones are demonstrating
'lag' time when connecting with ssh, telnet, or remote dtlogin.
Internal connections from any
zone to another are equally impacted and are more of a concern at the
moment. In a current
configuration, pings from zones are dropped. What makes this a bit
more confusing is that
different hardware platforms display a wide range of performance
charactoristics, from no
issues with lag time observed to extremely long response times.
I've configured three servers, ( a v240, a 220R, and a v880), with very
similar
whole root zone configurations and each displays different network
responsiveness.
The configuration involves initial installation 6/06 version and
recommended patching, 9/29/2006,
a single shared interface, all zone ip addresses on same subnet, and
all zones have netmasks,
default router, and dns configured. Each system has a very light load
because of early stages
of installation.
The 220R with its internal hme port is very responsive, no problem at
all. I can ping each
zone internally, I can remote dtlogin from global zone to non-global
zones, ssh and telnet
work as expected.
The v240 with its bge port configured is significantly worse. remote
dtlogin from global zone
connectivity is intermittant requiring several attempts to login.
ping, ssh, and telnet display a 'lag' time.
The v880 non-global zones, with the eri network port, is very
unresponsive and almost unusable.
telnet and ssh demonstrate significant lag time. remote dtlogin from
global zone is impossible.
I've found references to bge driver issues and bge driver patch, but
nothing for the eri driver.
I'd like to collect information but would need suggestions on DTrace
scripts that would shed
light on the issues. Any suggestions?
Daniel Synnott
_______________________________________________
networking-discuss mailing list
[email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
