Cisco’s FabricPath and HP’s FlexNetwork mark a shift in network architectures across the board
Continued from page 1
The Fabric and the Tree
In the next several years, as early adopters put the new equipment and designs into practice, no word is likely to be more used and abused than “fabric.” Both Cisco and HP use fabric as an integral part of their network designs. In both cases, fabric lacks the concrete, limited meaning found in the storage world. Instead, a network fabric is a densely woven high-speed interconnect between compute and storage in an environment where traffic flows and workloads are dynamically relocated based on priority and available resources.
Cisco and HP both recognise that moving from a tree to a fabric-based architecture will be an evolution. Neither company sees network managers ordering a rip-and-replace strategy. And the new network designs aren’t suited for all business needs. For example, Microsoft Exchange or SharePoint client/server traffic will likely still be best served by current designs. Instead of taking a rip-and-replace approach, both companies have made it clear that they will continue to support three-tier designs that use STP. But IT managers can expect a push from equipment makers to purchase switch line cards that enable the gradual transition to a fabric design. The evolution from tree to fabric favors the edge and core and deemphasises the aggregation layer.
Cisco and FabricPath
Cisco opened the attack on STP on a variety of fronts when it launched the Nexus product platform. In short order, OTV and FabricPath were released to deal with the Layer 2 domain limits of STP. Around the same time, the VPC (Virtual PortChannel) was introduced on the Nexus 7000, and that enabled all uplink ports to be used to increase bandwidth but without introducing loops.
Cisco introduced FabricPath as a feature in the Nexus 7000 hardware platform. The FabricPath Switching System combines NX-OS software features with the hard capabilities of the Nexus 7000 F1 series module as the basis of its next-generation network architecture.
Hardware modules incorporating FabricPath enable workload mobility such as VMware vMotion in a much larger resource pool, while also gaining significant bandwidth and N+1 redundancy and fast network convergence after a link failure. FabricPath-enabled modules use active-active links between devices — losing the idle ports that spanning tree required — and instead use ECMP (equal-cost multipath) to direct traffic.
First-generation modules can support up to 16-way ECMP, which can be combined with 16-port 10G bps PortChannels, for a total of 2.56T bps between switches. FabricPath builds on technologies that Cisco developed to create OTV and increases performance for enterprises moving to the Nexus 7000 and NX-OS.
HP Releases FlexNetwork
After being a Cisco partner for many years, HP became a fierce rival. Its acquisition of 3Com last year was aimed at shoring up its position against Cisco. HP’s release of the FlexNetwork architecture last month is among its latest competitive salvos.
The data centre heart of the architecture is FlexFabric and the HP A10500. In keeping with its legacy, HP has placed unified management at the heart of the FlexNetwork architecture, which is also a distinguishing characteristic of the design. Although the much-worn “single pane of glass” metaphor is central to the IMC5 release, it is useful to know that more than 10 separate modules can be implemented as needed. The network element manager is a basic requirement that IT managers should place at the top of their evaluation list.
The A10500 is one of the main hardware components of the FlexNetwork design but is not expected in the United States until sometime in the third quarter, although the chassis is shipping in China. Thus, I have not yet seen the “proof in the pudding” as it were. Even so, HP appears to have all the basic ingredients to support the FlexNetwork architecture with the hardware and software components that were announced in mid-May.
All told, it’s clear that in the coming decade an evolutionary change in enterprise networks will happen. It’s easy to let the incremental changes slip by. However, it’s unmistakable that virtualisation, mobility and cloud computing will soon place stresses on networks that forward-thinking IT managers must consider today.