Fast 802.11n Wi-Fi is going to take off slowly in the enterprise, but all the vendors want to get in the race, as they can see a big increase coming 802.11n does take off. They are getting ready to compete hard - and it starts with the specifications of their new 802.11n equipment.

So who has what?

The first vendor off the starting blocks, Meru, is a special case. Its "channel blanket" architecture puts all the access points on the same channel, and is difficult to compare with the other vendors' approaches.

Apart from Meru, the other significant vendors mostly use an architecture with "thin" access points whose radio channels are planned and managed by a central controller. They are all in the process of introducing 802.11n access points, and upgrading their switches as necessary.

In terms of market share, Cisco is the leader by far with more than 60 percent of the enterprise Wi-Fi market, and is also the first to have its access points certified as meeting the draft 802.11n specification, has the fullest specifications online.

Compared to Cisco, the other players are minnows, with less than ten percent each. The next leading player is Aruba with something like 9.5 percent, followed by Motorola, whose Symbol division launched the Wi-Fi controller sector, established it in its home markets of retail and warehousing, and has been losing market share ever since.

Motorola has announced plans for 802.11n, but not yet delivered, so we won't talk about it further here.

Irritatingly, Trapeze refuses to quote figures to analysts, but is probably still the next largest in share, given its OEM agreements with Nortel (due to end) and 3Com.

Trapeze and Aruba have both announced 802.11n products, and taken potshots at each other, claiming technological leadership over each other and over Cisco. We've spoken to all of them trying to sort out any real points of comparison.

Which silicon is in which AP?

Cisco uses silicon from Marvell, while both Trapeze and Aruba use Atheros silicon in their MP-432 and AP-124/5 access points. Aruba announced its product later than Trapeze, claiming to be using a newer generation of silicon, with better performance, but we doubt this. Products launched within a month or two of each other are almost certainly on the same generation and, as far as we can tell, both companies are using the Atheros 9160 Wi-Fi silicon. (Meru, we're told uses Atheros also but, with products out before the others, it is very likely an older version).

In one or two measurable ways then, Trapeze and Aruba's APs seem likely to outperform Cisco's. The Cisco 1250 AP will handle 2x3 MIMO (two antennas at the client and three at the AP), while both Trapeze and Aruba can handle 3x3, on a single radio or on two.

Cisco’s 11n Q&A section plays this difference down, saying "Theoretical calculations show that a 3x3 radio will have slightly better performance over a 2x3 radio. However, in our real world performance testing we have not seen any significant performance differences between 2x3 and 3x3 implementations," pointing out that both configurations support the multiple data streams that give MIMO systems better throughput.

Michael Coci, directof of technical marketing at Trapeze, denies this, saying that there are differences, which can be summed up as "a 3x3 will give a higher data rate at longer distances than a 2x3 implementation".

Powering up

But that's not the end of it. The performance of an 802.11n access point depends critically on the ability to power it - and enterprise access points are usually powered over Ethernet, to avoid the labour and expense of running extra power lines into the ceiling cavities where they are installed. We've gone on about powering 802.11n at some length (and here), but it's a crucial issue and more facts are emerging.

Currently, all dual radio access points need more power than can be delivered by the letter of the 802.3af power over Ethernet specification. The 802.3af specification offers 15.4W of power - but may be as low as 12.95W at the end of a cable run; Cisco's 1250 AP requires 12.95W when it has one radio in operation, or 16.9 W when two are in use. Aruba and Trapeze don't publish such dctailed sheets, but they seem to be in the same league, both quoting 17W for a dual-radio AP. If you want to run two radios, it seems you need more power from a local power brick.

It's a problem which will go away in the next year or so. (and this may be the biggest reason why people will hold off on 802.11n). Successive revisions of the silicon may use less power, by integrating the chips more tightly - but more importantly, the 802.3at Power over Ethernet Plus specification, due to be competed in 2008, will deliver more power over a cable. Early drafts suggested around 60W, but more recent sources seem to promise around 30W - but either way, it's plenty to power a dual radio AP.

Till that arrives, however, power is a problem for 802.11n APs, and all vendors are in the same boat. But they all have radically different responses.