Communication is via IP addresses and ports over an IP network. There can be a varied IP network in between the FCIP endpoints. FCIP is best suited for asynchronous type replication because your not going to be dealing with the same latency and bandwidth as FCP, not to mention you have more overhead.
FCIP is not a server to storage protocol. Its a switch to switch protocol. Its used to extend your SAN over a WAN. If you wish to use server to storage IP technology, than that is iSCSI and/or FCoE. You really don't want to be doing iSCSI over the WAN however, and FCoE requires layer 2 adjacency, once again, not ideal for over the WAN. Storage is generally local to the servers. Over the WAN you might replicate storage to another storage, and FCIP or CWDM/DWDM/SONET technologies are good for this type of traffic (SAN Extension).
Hello,I understand that Contracts in ACI that are enfored by the leafs are stateless ACL. When is an ACI Contract stateful?- as far as I know when using AVS/AVE?- what about when using Kubernetes/Openstack integration with ovs?
*This event has been rescheduled for causes beyond our control, we appreciate your understanding.
[ The link to the discussion will be published on December 7th ]
This event is an opportunity to have your questions answered on tools available for Nexus 30...
I'm having a strange problem redistributing iBGP routes to OSPF on Nexus 9000. Initially I had an open prefix list to get things working. Some of the routes weren't being redistributed to OSPF and I found this article which helped which said you nee...