Here’s how to enable jumbo frames under both NX-OS 4.0 and NX-OS 4.1 on a Nexus 5000 series switch.

VMware, Cisco, and EMC made their official announcement of the VCE Coalition and the joint venture Acadia this morning. Acadia is interesting, but it really isn’t the meat of the announcement, in my opinion. The real substance of the matter is the nature of the coalition.

Fibre Channel over Ethernet (FCoE) is receiving a great deal of attention in the media these days. Fortunately, setting up FCoE on a Nexus 5000 series switch from Cisco isn’t too terribly complicated, so don’t be too concerned about deploying FCoE in your datacenter (assuming it makes sense for your organization). Configuring FCoE basically consists of three major steps:

Much ado has been made—some of it by yours truly—about the current lack of ability to create a multi-hop Fibre Channel over Ethernet (FCoE) fabric. After digging in deeper with Cisco during my recent Unified Computing System (UCS) class, I have some additional information to share about the different forms of multi-hop FCoE and why multi-hop FCoE still isn’t available.

Voice network were monofunction. Data networks are multifunction. Storage Networks are monofunctional, want to bet Data Networks will handle Storage ?

Despite months of hyperbolic warnings, Cisco’s release today of their Unified Computing System blade servers (code named Project California) is gentle and evolutionary. The networking giant is challenging HP, IBM, and Dell, to be sure, but not with a slap in the face. Cisco is easing into the server pool with their UCS servers.

Omar Sultan from Cisco is wishing that FCoE would actually get some sales. You see, Cisco bought Nuova Systems to rush FCoE to market as the Nexus 5000 switch. But someone forgot to complete the standards work, and now this is causing problems. Customers are obviously concerned that FCoE has NOT been standardised.