SAN access and converged storage transport
Separate SAN login, communication, and volume access
A visible adapter is not proof of complete storage access. Trace the actual initiator identity and intended fabric, then inspect login and name-server observations, active zoning, target availability, array presentation, and host multipath state. Read-only FLOGI and FC name-server commands answer related but different questions. A target can be reachable while the desired LUN remains masked or incorrectly selected in the boot policy.
Configured zoning and active zoning are distinct. Identify the correct VSAN and effective zoneset rather than assume every saved zone permits traffic. A pWWN-based rule follows the configured identity, so a replacement adapter with a different pWWN needs deliberate policy reconciliation. Device aliases aid management but do not make a wrong identity correct. Independent SAN fabrics require topology and failure-domain separation, not merely different labels.
Understand fabric roles and capacity
NPV and NPIV describe complementary virtualization roles. An NPV edge relies on appropriate upstream NPIV behavior for multiple attached identities rather than participating exactly like another ordinary full switching domain. Trunks and PortChannels must carry the intended VSAN and use supported roles. Physical link-up alone does not establish all logical fabric membership.
Throughput can be limited by credit behavior, distance, frame characteristics, or backend service. A bandwidth-delay calculation needs clear units and overhead assumptions; a management TCP window is not the native FC credit mechanism. Aggregation can improve total capacity across diverse exchanges without guaranteeing that one exchange consumes every member link. Validate operational counters against the configured distribution method.
Treat converged transport as more than reachability
FCoE carries FC semantics over a supported Ethernet environment. It is not simply ordinary TCP storage, and it does not erase identity, fabric, or access requirements. RoCEv2 uses routed IP/UDP transport, but a usable IP route is only part of a suitable RDMA path.
Classification and marking must lead the intended traffic into the intended queues consistently at hosts and switches. PFC provides link-level priority pause behavior; it is not encryption or a universal end-to-end fairness mechanism. ECN and the applicable endpoint congestion control use congestion feedback to adapt sending. Excessive pause propagation, queue contention, and shared-priority effects need observation and design review rather than an assumption that no-drop labeling makes every workload healthy.
Use the selected platform and software guidance for exact features and thresholds. Test representative throughput, queue behavior, packet loss, and approved path-failure scenarios. A single successful read cannot certify multipath recovery or application continuity.