Anyone serious about high-availability connects servers to the network with more than one uplink, more so when using converged network adapters (CNA) with FCoE. Losing all server connectivity after a single link failure simply doesn’t make sense.
If at all possible, you should use dynamic link aggregation with LACP to bundle the parallel server-to-switch links into a single aggregated link (also called bonded interface in Linux). In theory, it should be simple to combine FCoE with LAG – after all, FCoE runs on top of lossless Ethernet MAC service. In practice, there’s a huge difference between theory and practice.
Read more ...Thanks for reading my news about FCoE and LAG – industry-wide violation of FC-BB-5? at my blog Bros Droid if you want too share this article, please put the resource, and if you think this article is very usefully dont forget to bookmark this site with CTRL + D on your keyboard to web browser.
More Articles :
Forwarding State Abstraction with Tunneling and Labeling- Virtual Circuits in OpenFlow 1.0 World
- VXLAN runs over UDP – does it matter?
- Easy Virtual Network (EVN) – nothing new under the sun
- FIB update challenges in OpenFlow networks
- IP renumbering in disaster avoidance Data Center designs
- New webinar: DMVPN Designs
- Clearing up the IPv6 Webinar confusion
- Not sure about the yearly subscription? Start slowly!
- Redundant DMVPN designs, Part 2 (Multiple Uplinks)