Hi,

this is usually caused by misconfigured FA flag settings, either set globally on the FA ports or vie symaccess on a per hba base.

Regards,

Ralf

From same FA port, to same server many other Luns are given and they doesn't show like this.

only few Luns show like i mentioned before.

Hi,

are you using cascading initiator groups?

Especially for clustered environments it's possible to use cascading initiator groups, and the proper flagsettings need to be applied on any initiator or initiator group accessing the clustered devices.

Another possible reason for this behavior might be that these devices are presented as pRDM's to a virtual W2K8 (or later) MSCS node.

These devices are protected by SCSI 3 persistent reservations which could prevent proper discovery from an ESX host.

Regards,

Ralf

Yes, using cascaded initiator group.

In vcenter, if FA port setting is not proper, when i try to check the configuration, it should show same in all servers.

But this type of identity is against very few Luns.

Could you please advise what should be the bit settings ?

If changing bit doesn't affect, i would check it now itself.

Its vmax 5875 code

Hi,

This is usefull. Out of 4 ports on 2 FA ports SPC-2 bit is disabled and for rest 2 it is enabled.

Will try to enable on remaining 2 ports.