Garrett,
the transition plan for a customer that deployed a trunking of qfe's is
not clear to me.
say someone used the Sun trunking software to build a 4 port trunk, with
qfe2 as the head trunk,
defined some load balancing policy, and used the name 'qfe2' in various
config places
(hostname.qfe0, IPFilter config files, third party firewalls, etc ...),
What happens when they upgrade to the new version? who will convert the
trunking configurations
to create aggrs, replace the 'qfe2' names to aggr1 everywhere?
BTW, there was a precedent to this kind of renaming, with the transition
from ipge to e1000g
(the *e1000g* **transition* patch, 123334-01)*
I don't believe documentation is sufficient here.
Kais
>>
>> Sun Trunking Impact
>> -------------------
>>
>> Using the Nemo interfaces means that the owners of QFE will have to use
>> the nemo link aggregation commands with dladm(1M). While this is to be
>> viewed as a good thing, it does represent change that will need to be
>> noted
>> in release notes, and such.
>>
>> The other Sun NIC drivers which are supported by Sun Trunking are the
>> GEM (ge) and Cassini (ce) drivers. We hope to move both of those to
>> Nemo as well, in the near future, and follow up with an EOF of the
>> Sun Trunking product altogether. However, this is out of scope for this
>> particular case.
>
