The latest switch to gain partitioning capabilities is McData's Intrepid 10000 director, otherwise known as the i10K, which was announced last month. Based on technology the company acquired from Sanera, the i10K's 256 non-blocking ports can be assigned to four separate dynamic partitions in four-port increments.
The only other switch on the market to support hard partitioning is CNT's Ultra-Net Multi-service Director (UMD), announced in June 2004. But on the same day McData announced the i10K, it also announced that it would acquire CNT. That news led many observers to question whether UMD will survive the merger of the two companies.
Functionally, CNT's and McData's approaches to partitioning are very similar, especially when compared to Cisco's VSANs, says Nancy Hurley, senior analyst at Milford, MA-based Enterprise Storage Group. They both give "a [higher] level of isolation than a software-induced partition."
One difference between the CNT and McData products, says Michael Maxey, product marketing manager for McData's director line of business, is the i10K's dynamic resource movement capability, which lets you move ports in and out of a partition. For example,
Meanwhile, Cisco's MDS switch supports partitioning with its virtual storage area network (VSAN) technology but, according to Hurley, VSANs are software-based and if there's a failure "it may affect other parts of the fabric."
Brocade's 240000 director doesn't support partitioning, although customers can isolate SAN fabrics using a separate Brocade product, the Multiprotocol Router, with its Logical SANs feature.
Partitioning a switch is useful to companies that want to consolidate disparate SANs onto a single hardware and management platform, but don't want to give up the physical isolation benefits that separate SAN fabrics offer, says Doug Ingraham, senior director of SAN switching at CNT. Switch partitioning allows a company to isolate a test and development area, and satisfy regulatory compliance requirements or separate different server platforms--for example, mainframe and open systems, Ingraham suggests.
This was first published in February 2005