Symptom
Various symptoms may be seen such as:
1) host cannot access storage across an FCIP link
2) fcping responds in one direction over an FCIP link, but does not respond in the opposite direction over the same link.
3) zone logging show zone internal event-history error shows frames from the affected device being dropped:
[119] ***** Ifindexes didn't match. SID 0xe80200 In the iuhdr(logical): 0x40000ff, In the iuhdr(physical): 0xa000001, In the Zone Server: 0x0 *****Dropping the frame.. *****
Conditions
This issue occurs when the system is booted with system default switchport mode f configured and the FCIP interface is left in the default port mode of auto.
Workaround
Configure the FCIP interface as switchport mode E.
If the FCIP interface will be placed in a port channel, then also configure the port channel with switchport mode E.
Further Problem Description
The issue can be confirmed by checking the hardware programming of the affected FCIP interface. The ISL permit entry is incorrectly located after the PLOGI trap entry so frames are punted to local supervisor instead of forwarding to the destination.
module-4# show process acltcam fwd-engine 0 input interface fcip 1
Loc cl vsan s_id d_id si up sof at rctl fct fctl sh oxid cc | pri mod ctl adj up vld cw stats ce
-------------------------------------------------------------------------------------------------------
7f89 2 0 0 0 31 0 0 0 22 1 0 0 0 0 | 1 0 0 10 0 0 0 42 0 # ELS redirect entry
7fa8 2 0 0 0 31 0 0 0 0 0 0 0 0 0 | 0 0 0 0 0 0 0 0 0 # EPort permit entry
Note: the rctl = 22 entry matches ELS command or response frames, including PLOGI frames.
Resolution Summary
To be completed when the bug is resolved.
