Oxy, you might be interested in the following:
http://ttoulliu2002.blogspot.com/2006/06/t1-and-e1000g.html
/dale
Oxy Hazard wrote:
oh,that's it. thanks both of you....
oxy
"David Edmondson" <[EMAIL PROTECTED]> ????
news:[EMAIL PROTECTED]
On 28 Jul 2006, at 9:46am, Oxy Hazard wrote:
I tried to install solaris 10 on a T2000 boxes (T1 8 cores,32
multi-threading CPU) in recent days, after installation, I tried
dladm to
test the 802.3 link aggregation,but failed, error msg is :
bash-3.00# dladm create-aggr -d ipge0 -d ipge1 1
dladm: create operation failed: No such file or directory (invalid
interface
name)
bash-3.00# dladm show-link
ipge0 type: legacy mtu: 1500 device: ipge0
ipge1 type: legacy mtu: 1500 device: ipge1
ipge2 type: legacy mtu: 1500 device: ipge2
ipge3 type: legacy mtu: 1500 device: ipge3
Anyone can give me a hint?
dladm can currently only create aggregations from interfaces that
have drivers written to the newer "Nemo" driver model. ipge isn't
one of those (you can tell because the 'type' field of show-link says
'legacy').
When the ClearView project completes this restriction will be
removed. There is also discussion of replacing the ipge driver with
e1000g (given that the underlying hardware is very similar), which
would also help you out (as the e1000g driver is Nemo based).
I'm unsure of the overall timescales for either of these activities -
perhaps someone else can comment.
p.s. if I configurate the link aggregation successfully, can I
configurate
the several zones on this new aggregated link? just like
ipge1:1....ipge1:n?
Yes - if you are able to create an aggregation then you can use the
aggregated interface within zonecfg.
dme.
_______________________________________________
networking-discuss mailing list
[email protected]
_______________________________________________
networking-discuss mailing list
[email protected]
