Each VPLEX FC WAN COM port is hard coded to send up to 160 commands at once.  This isn't configurable by our customers (or really documented anywhere.)  Generally speaking most systems I've seen will use two FC WAN COM ports per director (you can use up to 4, but 4 is kind of excessive), so from one director to the remote cluster you have a maximum of 320 outstanding at once.   VI in my experience (fantastic product by the way. I have nothing but respect for what they can do) generally speaking always mention that the queue depths are too high.   Because this is internal VPLEX director to VPLEX director communication traffic, this is isn't what I would call your normal host initiator to target device type traffic, so the normal rules about ideal queue depths don't apply in my opinion.   If this is something that's causing a performance concern though, I suggest opening a SR or looking at specific WAN performance stats like the latency and bandwidth, and any available switch stats (dropped frames, buffer credit issues, etc.)
Hi. I have been monitoring the statistics of Front-end Queue depth in my local cluster. But I have not been able to find information related to the maximum number of operations that each port can support. Is there any data or documentation where I can corroborate it?
VPLEX Queue Depth