Kais Belgaied wrote:
> 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.
To be quite honest, I had not considered to manually convert the old
Trunking product configuration.
Obviously renaming a head trunk to aggrX will cause some consternation
amongst customers of the old product, although I still think it is a net
win.
I'd recommend that we follow the path of using the old trunk's head, as
the primary interface (which should still work, although the device is
no longer a trunk), along with guidance to the customer about how to
rebuild the trunk. (With these new versions, it maybe the case that the
customer will have other options for trunk members that he couldn't
consider before, since any GLDv3 10/100 NIC can now be part of an aggr.)
We could also try to "port" the aggr's, though, as you point out, we can
only update the configuration pieces that we know about (specifically
/etc/hostname*, /etc/dhcp*, maybe ipfilter configs.)
I really am not sure what the best policy here is. I hope that an
answer can be found though, because otherwise there is little point in
doing any of these hme/qfe updates; we should just leave them alone and
keep shipping the product until it dies. This also would mean that
updates to make CE and GE work with GLDv3 will hit the same problems.
-- Garrett
>
> 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.
>>
>
