On 11/15/10 11:41 PM, Bhanu Gollapudi wrote:
> On Mon, 2010-11-15 at 23:09 -0800, Zou, Yi wrote:
>>>
>>> Hi,
>>>
>>> I have a question of how fcoemon/fcoeadm handles vlan id change in the
>>> switch.
>>>
>>> When I change vlan_id in the switch, I expected the fcoeadm/fcoemon to
>>> handle the CVL by calling fcoe_destroy, followed by vlan discovery and
>>> call fcoe_create with the new vlan_id that was discovered. However, I
>>> didnt observe this behavior when I tested this.
>>>
>>> Once the vlan_id is changed, the targets disappeared after dev_loss_tmo.
>>> I had to manually call fcoeadm -d followed by -c to rediscover the
>>> targets.
>>>
>>> Is it currently implemented this way, or did I miss something?
>>>
>>> Thanks,
>>> Bhanu
>>
>> AFAIK, the current implementation should work. Do you have AUTO_VLAN
>> set to "yes" in your corresponding fcoe cfg?
>
> Thanks for your response, Yi. I have AUTO_VLAN set to "yes".
>
>> As I recall, that will allow
>> fcoemon to automatically create vlan interface for the vid from the VLAN
>> descriptor of the newly received VLAN notification. Also, I think we are
>> doing lport reset only in libfcoe, can't say for sure if we are doing -d or
>> not
>> on a vlan that's gone...
>
> Is fcoemon handling CVL, and in the process calling fcoe_destroy before
> doing vlan discovery and calling fcoe_create? I didnt see this
> happening, will verify it again tomorrow. BTW, similar handling should
> be done even for FC_MAP change.
With an FC_MAP change (and no VLAN change), a CVL would be enough, and it
would be handled by libfcoe. fcoemon wouldn't do anything, and wouldn't
need to, since the same fcoe instance would exist before and afterwards.
The old advertisements, with the old FC_MAP value would time out and be
replaced by the new advertisements with the new FC_MAP value, and after
the old ones timed out, the new ones would be used for FLOGI.
Joe
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
