James Smart wrote:
> FC-LS-2 (r2.11 section 4.2.2 item e) requires ELS timeouts to be 2*R_A_TOV
Thanks, I thought I saw that somewhere!
It says the originator "shall detect an Exchange error ... if the Reply Sequence
is not received within a timeout interval of 2 X R_A_TOV."
I read that as saying the maximum timeout is 2 * R_A_TOV, it doesn't
say we can't detect an error earlier, but the intent is probably that.
That would apply to FLOGI as well, but I'd like to retry FLOGIs
faster, partially because of the auto-mode in FIP. I don't think that
causes a problem.
The other alternative is for FIP not to allow libfc to start fabric
logins until it has either selected an FCF or decided it's time to
try a non-FIP FLOGI. That would make increasing the libfc FLOGI
timeout irrelevant, but it's simpler just to timeout FLOGIs faster.
Joe
> Joe Eykholt wrote:
>> Hi all,
>>
>> We noticed a problem in a complex fabric with IVR - inter-VSAN routing
>> with certain targets.
>>
>> IVR provides a way for a shared device such as a tape drive to appear
>> in multiple VSANs by a sort of proxying/NAT setup. It's available on
>> some MDS switches.
>>
>> What happens is that the switches can delay the PLOGI to the target
>> for longer than the current E_D_TOV (2-second) timeout. When libfc
>> aborts
>> the PLOGI, the abort causes the target to send back a LOGO. This may
>> not cause a problem, when we retry, but it would be nicer if we didn't
>> retry so quickly.
>>
>> Other HBAs use a timeout of 2 * R_A_TOV = 20 seconds, I'm told.
>>
>> Does anyone see a problem with changing libfc accordingly?
>>
>> This shouldn't cause a problem because PLOGI retries should be rare,
>> but if they do occur would delay target setup by a lot.
>>
>> I would keep the FLOGI retry period at 2 seconds, however.
>>
>> Thanks,
>> Joe
>> _______________________________________________
>> devel mailing list
>> [email protected]
>> http://www.open-fcoe.org/mailman/listinfo/devel
>>
>>
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel
